Binding Collaborative Services to LDAP for support of automatic mail detection and server selection lists

The bind user ID is used by Lotus^® Collaborative Services to retrieve user attributes required for authentication from the selected LDAP directory. Setting the bind user ID to use the LDAP server for Collaborative Services supports automatic detection of users' mail files for any of the collaborative portlets that use a Lotus Domino back-end server for messaging (Lotus Notes View and Domino Web Access). If the server is a Lotus Domino LDAP, setting the bind user also supports the server or database drop-down lists that appear in Lotus Domino portlets.

Wait! The Domino-WebSphere Portal Express Integration Wizard can set up the bind user for you.

Before you set up the bind user, the WebSphere Portal Express server must be configured to recognize Collaborative Services (a previous task in this sequence).

Note: If you choose not to configure Collaborative Services to bind to the Lotus Domino LDAP, you can, instead, enable access to certain Lotus Domino fields by anonymous users. For information on setting the HTTP-HostName and HTTP-Port fields as queriable fields in the Configuration Settings document on the Lotus Domino LDAP server, see the topic on setting a Domino LDAP server to allow anonymous access.

To set the bind user, you must edit the CSEnvironment.properties file.

Perform the following steps:

Use the following commands to stop WebSphere Portal Express:
1. Open a command prompt and change to the following directory:
  - Windows: wp_profile_root\bin
  - Linux: wp_profile_root/bin
  - i5/OS: wp_profile_root/bin
2. Enter the following command to stop the WebSphere_Portal server:
  - Windows: stopServer.bat WebSphere_Portal -user admin_userid -password admin_password
  - Linux: ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password
  - i5/OS: stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example wp_profile.
Note: The default name of the application server is the profile name.

Locate the CSEnvironment.properties file in the following directory:

Windows:

portal_server_root\shared\app\config

Linux:

portal_server_root/shared/app/config

i5/OS:

portal_server_root_user/shared/app/config

Open the file in a text editor.
Note: Make a backup copy of the file before making changes.
Locate the following section in the file:
```
# Add Default IIOP/SSL Port
```
Under the heading in the previous step, remove the comment tag (#) from the beginning of the line that contains CS_SERVER_DOMINO_DIRECTORY_1.userid=.
At the end of the line, add a user ID that has appropriate access in the LDAP directory that supports Collaborative Services. Type the Lotus Domino LDAP fully qualified (for example, cn=domino admin,ou=orgunit,o=org) name for the user.
Note: On a Lotus Domino LDAP server, this user ID must have at least reader access to the address book names.nsf file. For a non-Lotus Domino LDAP directory, ask the LDAP administrator to provide a user with appropriate access to search the mailserver, mailfile, http-hostname, and http-port attributes.
Go to the line that contains CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.
Remove the comment tag (#) from the beginning of this line.
Copy the line that contains CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd= and paste it into a new file.
In the new file, at the end of the line, add the internet password for the user ID (that was entered for CS_SERVER_DOMINO_DIRECTORY_1.userid=).
Save this new file as dominobind.txt in the was_profile_root directory.
Open a command prompt to the following directory:
- Windows or Linux: was_profile_root/bin
- i5/OS: app_server_root/bin
In the same directory, run the following command (type as one line with a space character separating it):
```
PropFilePasswordEncoder dominobind.txt 
CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd
```
In the same directory, open the dominobind.txt file, and copy the encrypted password after CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.
Go back to the CSEnvironment.properties file.
Paste the encrypted password after CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.
Save and close the CSEnvironment.properties file.
Close the dominobind.txt file, and then delete dominobind.txt and dominobind.txt.bak from the was_profile_root/bin directory.
Use the following commands to start WebSphere Portal Express:
1. Open a command prompt and change to the following directory:
  - Windows: wp_profile_root\bin
  - Linux: wp_profile_root/bin
  - i5/OS: wp_profile_root/bin
2. Enter the following command to start the WebSphere_Portal server:
  - Windows: startServer.bat WebSphere_Portal
  - Linux: ./startServer.sh WebSphere_Portal
  - i5/OS: startServer WebSphere_Portal -profileName profile_root