Change the name of the session cookie identifier

By default, the session cookie identifier for IBM® Connections is named JSESSIONID. Other products hosted by WebSphere® Application Server often use the same names as their session cookies. If IBM HTTP Server hosts multiple web servers, you may want to change the cookie name for one of the web servers to avoid losing cookies when redirecting users from one product to another.

Procedure
1. If multiple products are hosted in an IBM WebSphere Application Server cell, by default, other applications and the WebSphere Application Server server will conflict with the use of the JSESSIONID session identification cookie. For each WebSphere Application Server that uses the virtual host (hostname) where the Lotus® Connections application resides, do the following:
a. Expand Servers in the navigation pane in the WebSphere Application Server Integrated Solutions Console and select Server Type > WebSphere Application Server.
b. Click on the first cluster server.
c. Expand Web Container Settings under Container Settings and select Web Container.
d. Under Additional Properties, click Session Management.
e. Check Enable Cookies.
f. Enter a different cookie name, such as LCSESSIONID, in the Cookie Name field.
g. Click OK, click Save, and then click Save again.
h. Repeat the above for each cluster server.

2. Restart the WebSphere Application Server.

3. In the WebSphere Application Server Integrated Solutions Console, regenerate the plugin-cfg.xml file for IBM HTTP Server. To do this, complete the following steps:
a. Open the WebSphere Application Server Integrated Solutions Console.
b. Expand Servers and select Server Types > Web Servers.
c. Select the check box next to the IBM HTTP Server name. For example: webserver1.
d. Click Generate Plugin to regenerate the plugin-cfg.xml file.
e. If necessary, click Propagate Plugin to copy the plugin-cfg.xml file from the local directory where the application server is installed to the remote machine.

4. Restart the IBM HTTP Server.