Change the name of the session cookie ID

The session cookie ID for Connections is named JSESSIONID by default. Other products hosted by the WAS often use the same name for their session cookie. If IBM HTTP Server is hosting multiple web servers, you might want to change the cookie name of one of them to prevent the cookie from being lost when the user is redirected from one product to another.

1. If multiple products are hosted on the WAS cell, by default the other application, and WAS servers will have conflicting use of the JSESSIONID session ID cookie. For each WebSphere Application Server that uses the same virtual host (hostname) as the one that hosts Lotus Connections applications:

   1. In the WAS console, select...
      Servers | Server Types | WebSphere application servers | first_clustered_server | Web Container Settings | Web container | Container Settings | Additional Properties | Session management | Enable cookies

   2. Enter a different cookie name in the Cookie name field, for example...
      LCSESSIONID

   3. Click OK, click Save, and then click Save again.

   4. Repeat with each clustered server.

2. Restart the WAS or servers.

3. Regenerate the plugin-cfg.xml file for the IBM HTTP Server in the WAS console. To do so:

   1. Open the WAS console.

   2. Regenerate the plugin-cfg.xml file.
      Servers | Server Types | Web servers | webserver_name | Generate Plug-in

   3. To copy the plugin-cfg.xml file from the local directory where the appserver is installed to the remote machine, click...
      Propagate Plug-in

4. Restart the IBM HTTP Server.

Parent topic:
System maintenance