Collaborative Services environment properties

If your collaborative site requires optional configuration that is not accomplished by the tasks that you run on the WebSphere Portal server to integrate 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 server.

The file is installed in the following directory:

Windows:

profile_root\PortalServer\config\config

UNIX:

profile_root/PortalServer/config/config

i5/OS:

profile_root/PortalServer/config/config

This file contains the following information about the portal environment:

• A flag to indicate whether the Collaborative Services are being used within the portal context

• Location, protocol, port, and version of Lotus Domino Directory server

• Location, protocol, port, and version of IBM Lotus Sametime server

• Configuration and performance tuning settings specific to Collaborative Services

• A flag to indicate the type of token that is being used: lpta token or ltpa token2

• Edit the CSEnvironment.properties file

  To modify any Lotus Collaborative Services environment properties, 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.

• Set 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.

• Customize 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.

• Enable 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.

• Configure people awareness to work across Domino Directory and a non-Domino portal LDAP directory

  Lightweight Third-Party Authentication (LTPA) is the recommended way to enable single sign-on (SSO) between WebSphere Portal and IBM Lotus Sametime and synchronize users' distinguished names (DN) when each product uses a different user or LDAP directory.

• Auto-detecting user mail information from a secondary LDAP server

  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.

• Customize Collaborative Services user credentials for eTrust SiteMinder

  If you protect the portal and any of the Domino and Extended Products Portlets or Common Mail portlet with Computer Associates eTrust SiteMinder, 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 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

  For Domino Directory as the primary (and only) LDAP server for WebSphere Portal, you can set the following property in the CSEnvironment.properties file to false to improve the performance of Domino Directory.

• Use LtpaToken2 for user login

  By default, the credential settings in the CSEnvironment.properties file are set to use an LTPA token for user login. If your environment is configured with LtpaToken2 only, modify the CSEnvironment.properties file to use LtpaToken2 instead of LtpaToken.

Parent topic:

Integrate with collaboration software

---