Change the name of the session cookie IDThe session cookie ID for IBM 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.
- If multiple products are hosted on the IBM WAS cell, by default the other application and WAS servers will have conflicting use of the JSESSIONID session ID cookie. For each WAS that uses the same virtual host (hostname) as the one that hosts Lotus Connections applications, do the following:
- In the WAS admin console, expand Servers in the navigation pane, and then select Server Types -> WebSphere application servers.
- Click the first clustered server.
- Expand Web Container Settings under Container Settings, and then select Web container.
- Under Additional Properties, click Session management.
- Select Enable cookies.
- Enter a different cookie name in the Cookie name field, for example, LCSESSIONID.
- Click OK, click Save, and then click Save again.
- Repeat with each clustered server.
- Restart the WAS or servers.
- Regenerate the plugin-cfg.xml file for the IBM HTTP Server in the WAS admin console. To do so...
- Open the WAS admin console.
- Expand Servers, and then select Server Types -> Web servers.
- Select the check box beside the IBM HTTP Server name. For example: webserver1.
- Click Generate Plug-in to regenerate the plugin-cfg.xml file.
- If necessary, click Propagate Plug-in to copy the plugin-cfg.xml file from the local directory where the Application Server is installed to the remote machine.
- Restart the IBM HTTP Server.
Parent topicAdminister applications
November 28, 2011
Nov 28, 2011 2:45:21 PM Added "Under Additional Properties" to Step 1d. 1