Collaborative Services environment properties

If your collaborative site requires optional configuration that is not accomplished by the tasks that you run on the IBM^® WebSphere^® Portal Express server to integrate IBM Lotus^® Domino^® and the Extended Products, you can modify the operation of the collaborative servers and portlets in various ways by manually editing the Lotus Collaborative Services environment properties file (CSEnvironment.properties) on the WebSphere Portal Express server.

See the list of related topics for the instructions on editing this properties file, and a number of use cases in which the solution is a modification to the file.

• Editing the CSEnvironment.properties file
  To modify any Lotus Collaborative Services environment properties, you must stop the portal server, locate the file in a location specific to your platform, back up the file before editing it, use a text editor to open and modify it, and then restart the server.
• Setting Lotus Sametime to use a Lotus Sametime token for user login
  By default, the credential settings in the CSEnvironment.properties file are set to use an LTPA token for user login. You can override the settings to use an internal IBM Lotus Sametime token instead.
• Customizing communication between Lotus Sametime and Collaborative Services for name resolution and clustering
  You can change the port through which the Lotus Sametime server should connect, the reconnect interval, and the timeout value.
• Resolving the portal user's log-in name with the user name on the Lotus Sametime server
  The following setting is used for resolving name formats between two different types of user registries that use different schemas.
• Enabling awareness when Lotus Sametime authenticates with a native Domino Directory
  You can customize the CSEnvironment.properties file to support awareness when Sametime authenticates against a native (non-LDAP) Domino Directory, by specifying the delimiter character for distinguished names.
• Configuring people awareness to work across Domino Directory and a non-Domino portal LDAP directory
  You can edit the CSEnvironment.properties file to support Sametime-based people awareness features in a portal site in which Lotus Sametime uses a native Domino Directory as the repository for Lotus Sametime user names, and the WebSphere Portal Express user repository is in a non-Domino LDAP, such as IBM Tivoli^® Directory Server.
• Auto-detecting user mail information from a secondary LDAP server
  You can set the Lotus Collaborative Services in the portal to detect users' mail file information from an additional (secondary) non-Domino LDAP user directory. For example, you may need to configure two directories if your organization has one for customers and one for employees.
• Customizing Collaborative Services user credentials for eTrust SiteMinder
  If you protect the portal and any of the Domino and Extended Products Portlets or Common PIM portlets with Computer Associates eTrust SiteMinder, you must set the Lotus Collaborative Services to use the eTrust SiteMinder token instead of the default LTPA token.
• Supporting automatic mail detection with an LDAP directory other than Lotus Domino
  If the LDAP directory configured for the portal and for Lotus Collaborative Services is not IBM Lotus Domino, and you want the automatic mail detection feature in Lotus Domino messaging portlets, you can modify the CSenvironment.properties file to support the feature.
• Tuning performance of the Domino Directory
  If you are using Domino Directory as the primary (and only) LDAP server for WebSphere Portal Express, you can set the following property in the CSEnvironment.properties file to false to improve the performance of Domino Directory.