User inbound interface is designed to load data into the following DB tables:
- PACE_MASTERDBO.PACE_USERS – user fields
- PACE_MASTERDBO.PACE_USER_GROUPS – business group fields
- PACE_MASTERDBO.STARSEC_USER_GROUP – application group fields
- PACE_MASTERDBO.EGL_CENTER_ROLE – center role fields
- PACE_MASTERDBO.EGL_CENTER_ROLE_USER – center role for user fields
- PACE_MASTERDBO.PACE_USERS_CONTACT_INFO or PACE_MASTERDBO.PACE_MAIL_USER_INFO (only 1 exists in a database) – email field
Stream name: eagle_ml-2-0_default_in_xml_user
Rule name: xml-user_user.xml
If Business and/or Application group is not specified, the new User will be loaded by stored procedure with values GROUP_ID = -1 and/or STARSEC_GROUP_ID = -1. In other case for loading will be used the panel.
If the Role Name and Center Code are specified, the User will be assigned to Center Roles specified in the group section with groupCode = ‘CenterRole’.
Microstrategy Model Processing Details
microstrategyRole can get the following valid values (MSTR_ROLE code category):
- 1 - Consumer;
- 2 - Writer;
- 3 - Administrator.
microstrategyUserStatus can get the following valid values (MSTR_USR_STATUS code category):
- 1 - ACTIVE;
- 2 - INACTIVE;
- 3 - DELETED.
Deleting User
To delete a user, make sure you have set header/action = ‘DELETE’, the User will be deleted, and the followings elements:
- userId
- updateSource
Switch Off Password Encryption
If you load data thru the panel, user password is encrypted by default. To switch off encryption, you should add a header/processingOptions element with "APPLY_NO_RULE_password" value:
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="UserAdministrationTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="UserAdministrationTransactionMessage"> <userAdministrationTransaction> <header> <objectType>User</objectType> <processingOptions>APPLY_NO_RULE_password</processingOptions> </header> <user> <objectType>User</objectType> <objectId>User</objectId> <objectDescription>User</objectDescription> ...