Home

 

Synchronize user identification data between Activities and the LDAP directory

Use administrative commands to synchronize member records in the Activities database with the LDAP


If you are using the Profiles service, first synchronize the ExtId values in the Profile database with LDAP before you can run the commands that synchronize external IDs described in this topic. See Synchronizing user datat between Profiles and LDAP for more details.

Use wsadmin

Only perform this procedure if users were deleted and then added back into LDAP or if you switch from one LDAP server to another, for example, during a migration from a pilot installation to a production installation. To synchronize user IDs between Activities and the LDAP..

  1. Start the Activities Jython script interpreter.

    1. Access the Activities configuration file:

    2. Network deployment: 

        execfile("profile_root/config/bin_lc_admin/activitiesAdmin.py")

      If prompted to specify which server to connect to, type 1.

      The information about which server to connect to is only used by wsadmin when you are running administrative commands to collect statistics.

  2. Use any of the following commands:

    • To synchronize all of the users and groups in the oa_memberprofile table in the Activities database with the LDAP based on their login names: 

        ActivitiesMemberService.syncAllMemberExtIds()

  3. To synchronize a list of users whose login names are provided in a text file that has one name per line: 

      ActivitiesMemberService.syncBatchMemberExtIdsByLogin(filename)

    In a stand-alone deployment, the text file must be stored in a local to the server where you are running wsadmin. In a network deployment, the file must be local to the server that you connect to.

  4. To synchronize a list of users or groups whose e-mail addresses or group names are provided in a text file that has one e-mail address per line: 

      ActivitiesMemberService.syncBatchMemberExtIdsByEmail(filename)

    In a stand-alone deployment, the text file must be stored in a local to the server where you are running wsadmin. In a network deployment, the file must be local to the server that you connect to.

  5. To synchronize records in the Activities database oa_memberprofile table with the LDAP using a secondary key. You might want to use this command when the primary key values of LDAP objects have been altered. For example, if you have deleted a person object, and then recreated it. You can use one of the following commands: 

      ActivitiesMemberService.syncMemberExtIdByEmail(emailAddress)

    where emailAddress is the person's e-mail address or a group name enclosed in quotes. 

      ActivitiesMemberService.syncMemberExtIdByLogin(loginName)

    where loginName is the person's login name enclosed in quotes.


Manage membership

 

Related tasks

Synchronize user data between Profiles and the LDAP directory

Start wsadmin

Synchronize IDs between LDAP and the feature databases

+

Search Tips   |   Advanced Search