Persistent cache file needs to be recreated when internal ID is changed on Sametime server

Technote (troubleshooting)


Problem

Sametime server configuration requires to define an organization Directory attribute used as a internal Sametime ID (for example, user's email, distinguished name, etc.).

The internal Sametime ID is shown on the Sametime Community Servers->Community Services panel of the SSC:


The blank field means that DN is defined as Sametime internal ID.

If a persistent cache file is created prior to the Sametime ID changing, the resolved names from the cache are not valid in Sametime Community. The Sametime Community is not able to pass correct user status to the PresenceAdapter


Resolving the problem

If Sametime ID is changed (it means another attribute is chosen) and the persistent cache already exists, the administrator should remove the existing cache and initialize the new cache.

The persistent cache files are located on TAS machine according to the following key in the /enterprise/ibm/st.cached.resolve.properties file:

cache.persistent.file.path=/enterprise/persistent

The following actions need to be done:
1. Stop TAS.
2. Delete all existing cache files from the /enterprise/persistent folder.
3. Start TAS.

The new persistent cache should be created according to the "Initializing the persistent cache with the Java Toolkit CachedResolveBatchMode application" topic in the Sametime Unified Telephony 8.5.1 Installation chapter of the 8.5.1 Info Center.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Sametime Unified Telephony
Other Server Issues

Software version:

8.5.1, 8.5.2

Operating system(s):

Linux

Reference #:

1439489

Modified date:

2012-05-31

Translate my page

Machine Translation

Content navigation