Home

 

Synchronize user identification data between Bookmarks and LDAP

Use the PersonService or DogearMemberService command to update external member IDs in the LDAP database for your Bookmarks deployment. These commands do not require a file check out or a server restart to take effect.


Use the PersonService or DogearMemberService command to synchronize member external IDs in the Bookmarks database. For example, if users are migrated to a new LDAP or a user is removed and re-entered in the LDAP and their unique identifier changes, these users will not be able to login to Bookmarks until the user record is updated with the PersonService or DogearMemberService command.

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 member externalIDs described in this topic. See Synchronizing user data between Profiles and the LDAP directory for more details.

  1. See the topic Running Bookmarks administrative commands for information on using administrative commands.

  2. Use these methods with the PersonService command to update user data:

    Option Description
    PersonService.updateAllMemberIds()

    Updates all user IDs in the Bookmarks database. This service queries the LDAP server for each user by login name to retrieve the updated user ID.

    Update time will vary, depending on the number of people in your database. On average, 8 minutes per 500 users is the norm. For large databases, run this process overnight.

    There should be no output in wsadmin console. Be sure to check the SystemOut.log file as email addresses of Bookmarks users that were not successfully updated will be logged there.

    PersonService.updateMemberId("[single email address]")

    This command updates a single member external ID. This command expects a single e-mail as input.

    There should be no output in wsadmin console if successful. Example:

      PersonService.updateMemberId(
       "john_smith@acme.com")
      

    PersonService.updateMemberIdBatch("[emailaddressfile]")

    Updates member external IDs using e-mail addresses stored in a text file. This command expects a file with one e-mail address on each line.

    In a stand-alone deployment, create this text file and save it in a local to the server where you are running the wsadmin processor. In a network deployment, the file needs to be local to the server that you connect to. Example:

      PersonService.updateMemberIdBatch(
       "/opt/Bookmarks/update.txt")
      

  3. Use these methods with the DogearMemberService command to synchronize user data:

    Option Description
    DogearMemberService.syncAllMemberExtIds()

    Updates all external user IDs in the Bookmarks database. This service queries the LDAP server for each user by login name to retrieve the updated user ID.

    Update time will vary, depending on the number of people in the Bookmarks database. On average, 8 minutes per 500 users is the norm. For large databases, run this process overnight.

    There should be no output in wsadmin console. Be sure to check the SystemOut.log file as login names of Bookmarks users that were not successfully updated will be logged there, as well as any error messages.

    DogearMemberService.syncMemberExtIdByEmail(emailAddr)

    Specify the email address of one user to sync. This command will update the user's external user ID. For example,

    DogearMemberService.syncMemberExtIdByEmail("mary_brown@renovations.com")

    DogearMemberService.syncMemberExtIdByLogin(loginName)

    Specify the login name of one user to sync. This command will update the user's external user ID. For example,

    DogearMemberService.syncMemberExtIdByEmail("mbrown")

    DogearMemberService.syncBatchMemberExtIdsByEmail(emailFile)

    Specify the path and name of a text file that contains one or more email addresses of users to sync. Specify one email address per line in the text file. This command will update the user's external user ID. For example,

    DogearMemberService.syncBatchMemberExtIdsByEmail("d:/temp/userEmails.txt")

    In a stand-alone deployment, create this text file and save it in a local to the server where you are running the wsadmin processor. In a network deployment, the file needs to be local to the server that you connect to.

    Sample of the userEmail.txt file:

    • ajones@ibm.com

    • joseph_smith@ibm.com

    • eric.warner@ibm.com

    DogearMemberService.syncBatchMemberExtIdsByLogin(loginFile)

    In this command, the user needs to specify the path and name of a text file that contains one or more Login Names of users who they want to sync. Specify one login name per line in the text file. This command will update the user's external user ID. For example:

    DogearMemberService.syncBatchMemberExtIdsByLogin("/opt/userLoginNames.txt")

    In a stand-alone deployment, create this text file and save it in a local to the server where you are running the wsadmin processor. In a network deployment, the file needs to be local to the server that you connect to.

    Sample of the userLoginNames.txt file:

    • ajones

    • joseph smith

    • ericwarner


Administer Bookmarks

 

Related tasks

Synchronize IDs between LDAP and the feature databases


+

Search Tips   |   Advanced Search