PI43621: (DOC) ADDING RESOURCE LINKS FROM RAM TO RTC/CLM IS NOT WORKING BECAUSE OF HTTP REDIRECTION - JSESSIONID

Rational Asset Manager 7.5.3.1
Rational Asset Manager 7.5.3.2
Rational Asset Manager 7.5.3.3
Rational Asset Manager 7.5.4
Rational Asset Manager 7.5.4.1
Rational Asset Manager 7.5.4.2
Rational Asset Manager 7.5.4.3
Rational Asset Manager 7.5.4.4
Rational Asset Manager 7.5.4.5
Rational Asset Manager 7.5.4.6
Rational Asset Manager 7.5.4.7
Rational Asset Manager 7.5.4.9
Rational Asset Manager 7.5.4.8
Rational Asset Manager 7.5.4.10

APAR status

• Closed as documentation error.

Error description

• After upgrading to RAM 7.5.2.2, a Rational Asset Manager (RAM)
  repository administrator opens an asset and clicks on
  Discussion. They are able to create a link to an existing CCM
  (Change and Configuration Management )/RDNG (Rational DOORS Next
  Generation)  or create a new work item in CCM/RDNG. The list is
  populated and they are able to take all actions. However, the
  link does not stay as a related link. It will disappear on
  refresh. It has happened after upgrading to RAM 7.5.2.2 even
  though CLM (Collaborative Lifecycle Management ) stayed at 4.0.6
  ( also reproducible with CLM 5.0.2).
  
  
  Answer:
  
  
  It was necessary to rename the JSESSIONID for the RAM server to
  something else like JSESSIONIDRAM, as was the case prior to the
  upgrade. When the upgrade to the new RAM version was done, the
  settings in WAS had to be recreated from scratch, as they were
  not carried over due to the way RAM (and the rest of the
  Rational Tools at this site) were installed with WAS. This not
  so obvious detail on the need to change JSESSIONID name change
  for the cookies in RAM, was not captured in the client's
  internal
  documentation and upgrade notes.
  
  The RAM Knowledge Center (KC) needs a topic or information
  similar to this IBM Connections 4.5.0  knowledge center topic:
  - Changing the name of the session cookie ID
  http://www-01.ibm.com/support/knowledgecenter/SSYGQH_4.5.0/admin
  /admin/t_admin_common_change_jsessionid.dita
  , explains the steps to do this and explains:
  
  "...The session cookie ID for IBM Connections is named
  JSESSIONID by default. Other products hosted by the
  WebSphere Application Server 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. .."
  
  This is similar to this RAM and RTC product scenario, with each
  on separate servers and behind a PROXY IHS (IBM HTTP Server)
  Server. For example, after completing the setup of a brand new
  Rational Tools, with multiple distributed servers for RAM,
  RTC/CLM, RRC, etc, all behind a PROXY IHS server or on the same
  WAS server. It may be necessary to change the JSESSIONID for
  RAM, unless your specific RAM INSTALLATION for this particular
  environment configuration differs from the other
  applications/servers.
  
  In the case of upgrading  a RAM server it is always necessary to
  do a complete backup as per this RAM 7.5..2 Knowledge Center
  topic:
  - Creating a backup of a Rational Asset Manager repository
  http://www-
  01.ibm.com/support/knowledgecenter/SSUS84_7.5.2/com.ibm.ram.inst
  allguide.doc/topics/t_ram_backup_restore.html
  , with the emphasis on  application server settings and the ned
  to run the backupConfig script for WebSphere Application
  Server. The backupconfig script/command will save the
  information in the WAS admin console settings for the Web
  Container server.xml file. The information is in the server.xml
  file for a server profile if it is a property of the Web
  Container, and has been saved. Example:
  {WAS85_HOME)\profiles\AppSrv01\config\cells\{hostname}Node03Cell
  \nodes\{hostname}Node03\servers\server1\server.xml
  
  The information about JSESSIONID should be documented in the
  above backup topic and also in the post
  install configuration topic:
  - Configuring the Rational Asset Manager server application
  http://www-01.ibm.com/support/knowledgecenter/SSUS84_7.5.2/com.i
  bm.ram.installguide.doc/topics/postconf.html
  , and anywhere else that may be useful.
  

Local fix

• change JSESSSIONID for RAM
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Multiple Products deployed on same Application Server        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Adding resource links from RAM to RTC/CLMis not working      *
  * because of HTTP redirection - JSESSIONID                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• In Rational Asset Manager 7.5.3.1 , the post install
  configuration article  has been updated to add a note providing
  the resolution to the issue.
  https://www.ibm.com/support/knowledgecenter/SSUS84_7.5.3.1/com.i
  bm.ram.installguide.doc/topics/postconf.html
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels