Synchronize user identification data between the news feature and the LDAP directory

Home

Synchronize user identification data between the news feature and the LDAP directory

Use the NewsMemberService command to synchronize member IDs between the Home page and the LDAP databases. These commands do not require a file check out or a server restart to take effect.

To synchronize member IDs, use wsadmin. See Start the wsadmin client for information about how to start the wsadmin command-line tool.

When users are migrated to a new LDAP or a user is removed and reentered in the LDAP and their unique identifier changes, these users are not able to log in to the Home page until the user record is updated with the NewsPersonService command.
To synchronize member IDs between the news feature and LDAP databases...
Start wsadmin so that you can access the news configuration file:

After the wsadmin command environment has initialized, use one of the following commands to initialize the news environment and start the news script interpreter:

Standalone deployment:
execfile("newsAdmin.py")

Network deployment:
execfile("WAS_HOME\profiles\Dmgr01\config\bin_lcadmin\newsAdmin.py")

If you are asked to select a server, you can select any server.
Use one of the following commands to update member IDs in the Home page database:
NewsMemberService commands
Option Description
NewsMemberService.syncAllMemberExtIds() Updates all member IDs in the Home page database. This service queries the LDAP server for each user by login name to retrieve the updated member ID (unique identifier).
If an update was not completed successfully, check your server logs for any additional information.
NewsMemberService.syncBatchMemberExtIdsByLogin("loginName")
Updates member IDs in the Home page database using user IDs stored in a text file. This command expects a file with one user ID 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. For example:
NewsMemberService.syncBatchMemberExtIdsByLogin("/opt/Homepage/update.txt")
If an update is not completed successfully, check your server logs for any additional information.
NewsMemberService.syncBatchMemberExtIdsByEmail(emailFile)
Updates member IDs using e-mail addresses stored in a text file. This command expects a file with one e-mail address on each line.
E-mail addresses are case sensitive.
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. For example:
NewsMemberService.syncBatchMemberExtIdsByEmail("/opt/Homepage/update.txt")
If an update is not completed successfully, check your server logs for any additional information.
NewsMemberService.syncMemberExtIdByLogin("loginName")
Updates a single member ID using a single login name as input.For example:
NewsMemberService.syncMemberExtIdByLogin("John Smith")
NewsMemberService.syncMemberExtIdByEmail(emailAddr)
Updates a single member ID. The command expects a single e-mail address as input.For example:
NewsMemberService.syncMemberExtIdByEmail("john_smith@acme.com")
E-mail addresses are case sensitive.
Depending on the size of data being synchronized, if the execution of one of these commands takes longer to complete than the value of the com.ibm.SOAP.requestTimeout property in the soap.client.props file in WAS_HOME\profiles\PROFILE_NAME\properties\soap.client.props, an error displays on the wsadmin console, and any return value from the method invoked is lost. The command continues to be processed to completion, but the connection between the feature and wsadmin that invoked it is gone. To change this behavior so that the client does not terminate the connection, increase the value of the com.ibm.SOAP.requestTimeout property or set the property to 0 for no timeout. If you reset the property, restart the application server for the change to take effect.
Administer the news repository

Related tasks

Synchronize IDs between LDAP and the feature databases

+
Search Tips | Advanced Search

Option	Description
NewsMemberService.syncAllMemberExtIds()	Updates all member IDs in the Home page database. This service queries the LDAP server for each user by login name to retrieve the updated member ID (unique identifier). If an update was not completed successfully, check your server logs for any additional information.
NewsMemberService.syncBatchMemberExtIdsByLogin("loginName")	Updates member IDs in the Home page database using user IDs stored in a text file. This command expects a file with one user ID 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. For example: NewsMemberService.syncBatchMemberExtIdsByLogin("/opt/Homepage/update.txt") If an update is not completed successfully, check your server logs for any additional information.
NewsMemberService.syncBatchMemberExtIdsByEmail(emailFile)	Updates member IDs using e-mail addresses stored in a text file. This command expects a file with one e-mail address on each line. E-mail addresses are case sensitive. 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. For example: NewsMemberService.syncBatchMemberExtIdsByEmail("/opt/Homepage/update.txt") If an update is not completed successfully, check your server logs for any additional information.
NewsMemberService.syncMemberExtIdByLogin("loginName")	Updates a single member ID using a single login name as input.For example: NewsMemberService.syncMemberExtIdByLogin("John Smith")
NewsMemberService.syncMemberExtIdByEmail(emailAddr)	Updates a single member ID. The command expects a single e-mail address as input.For example: NewsMemberService.syncMemberExtIdByEmail("john_smith@acme.com") E-mail addresses are case sensitive.