Collaborative Services environment properties

 

+

Search Tips   |   Advanced Search

 

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

WP_PROFILE/shared/app/config/CSEnvironment.properties

...which 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

 

Steps

1. CSEnvironment.properties file
2. Set Lotus Sametime to use a Lotus Sametime token for user login
3. Customize communication between Lotus Sametime and Collaborative Services for name resolution and clustering
4. Resolve the portal user's log-in name with the user name on the Lotus Sametime server
5. Enable awareness when Lotus Sametime authenticates with a native Domino Directory
6. Configure people awareness to work across Domino Directory and a non-Domino portal LDAP directory
7. Auto-detect user mail information from a secondary LDAP server
8. Support automatic mail detection with an LDAP directory other than Lotus Domino
9. Customize Collaborative Services user credentials for eTrust SiteMinder
10. Tune performance of the Domino Directory
11. Use LtpaToken2 for user login

 

Parent topic

Reference topics for collaboration

 

Related reference

Collaborative Services API