Configuring Sametime Community Chat Logging with MongoDB
This topic guides you through the steps for configuring HCL Sametime Community server chat logging with MongoDB.
About this task
Note: These steps are required to support Persistent Chat. HCL Sametime Web and Mobile clients will not function without Persistent Chat enabled.
Procedure
Procedure
-
Review the values in the chatlogging.ini to ensure they are correct. If the
MongoDB is installed on a diffrent server than the HCL Sametime Community
server, these values will need to be updated.
Note: If you followed the examples in the Install MongoDB section, the defaults should work without any modifications. If you used a different username or password or installed MongoDB on a separate machine, you must update the following settings in sametime.ini and chatlogging.ini as appropriate.Example:
CL_MONGO_HOST=127.0.0.1 CL_MONGO_PORT=27017 CL_MONGO_USER=sametimeUser CL_MONGO_PASSWORD=sametime
- In the sametime.ini file, locate the MONGO_URI parameter and correct or confirm the IP address of the MongoDB server.
- If any changes were made, save the sametime.ini file.
-
Start the HCL Community Server for these changes to take effect.
Note: If the LDAP document in stconfig.nsf has "The attribute of the person entry that defines the internal ID of a Sametime user" set to a value that is not a distinguished name value, set CL_USE_USER_DN=1 in the sametime.ini under [Config]. If this setting is not found, the server defaults to using the Sametime user ID as the user's identifier for a chat log. This flag should be used if your Sametime user ID is not a distinguished name.
- CL_USE_USER_DN=0 uses the Sametime user ID as the user's identifier
for a chat log.
Announcement originators and recipients can only be identified by their Sametime user IDs, so logging must also use the Sametime user IDs.
- CL_USE_USER_DN=1 uses the person's distinguished name (from the LDAP
directory) as the user's identifier for a chat log.
If a distinguished name is not found, it instead uses the Sametime user ID. The distinguished name attribute can be either the Sametime user ID or another attribute.
- CL_USE_USER_DN=0 uses the Sametime user ID as the user's identifier
for a chat log.