Running the name conversion utility in RESOLVE mode

Running the name conversion utility in RESOLVE mode updates user contact and privacy lists with the new Sametime® user ID.

Before you begin

The IBM® Sametime Community Server must be running. Name change in RESOLVE mode differs from running other name conversion modes, because in RESOLVE mode, the Sametime Community server must be running, so that the name change utility can access StResolve. IBM recommends running the name conversion utility at off-peak hours.

Complete all the previous steps outlined in the parent topic, "Migrating older user IDs to a unique directory attribute:

  1. Prepare user IDs for RESOLVE mode. The LDAP directory contains a unique and constant attribute in each person entry. The attribute needs to be added to the directory schema if it does not exist, and needs to be populated with a unique value in each person entry. The value needs to be set with a string that will not change when the person's name changes.
  2. Create a CSV file with the RESOLVE mode indicated.
  3. Create a name change task.

About this task

Running the name conversion utility in RESOLVE mode migrates the old user ID to a new user ID that is a directory attribute that is not likely to change. The tool looks up every user ID in the database against the directory and replaces the old user ID with the directory user ID.

Run the name change task on all the servers in the community. In a clustered environment, run the task for only one server per cluster. The task should run once on the selected server and then be replicated to other servers in the cluster.

Procedure

  1. Change your Sametime Community Server configuration to use a unique user ID, so you run the name change utility in RESOLVE mode. This is controlled in the LDAPServer document in the StConfig.nsf file.
  2. Gather diagnostic trace information during the task in case it is necessary for future verification. See Gathering name conversion utility diagnostic data.
  3. Stop the Sametime Proxy Server. See Starting and stopping servers running on WebSphere Application Server.
  4. Follow these steps to run the name conversion utility in RESOLVE mode for your operating system:
  5. Disable diagnostic traces that you set in step 2.
  6. Restart Sametime Community Server.
  7. Restart all Sametime Community Servers in your deployment so they can detect the modified name. If your deployment includes Sametime Unified Telephony, restart all Telephony Application Servers as well. Restart the Sametime Proxy server as needed.