IBM Support

Rename of JSESSIONID cookie

Technote (FAQ)


Can the JSESSIONID cookie used by Maximo be changed to prevent conflicts with similar named cookies


Yes, The change is made in WebSphere. The HTTP server and Maximo should require no changes to implement. It is important that all cluster members have the same JSESSIONID cookie to ensure session affinity is maintained.
1. Open the administrative console.
2. Go to Servers -> Server Types -> WebSphere Application Servers -> {ServerName} -> Container Settings > Session management -> Enable Cookies
3. Change the value for session cookie name.
4. Click OK.
5. Save changes.
6. Restart Application Server
7. Regenerate plug-in configuration file.
(a) Go to Servers -> Web Servers.
(b) Select one of the listed Web servers, and click Generate Plug-in
(c) Either manually copy the plugin-cfg.xml plugin or use the propogate option

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Control Desk
Systems and Asset Management Tivoli Service Request Manager
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Change and Configuration Management Database

Document information

More support for: Maximo Asset Management

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1636300

Modified date: 24 August 2015

Translate this page: