Review the topology diagram, which shows how the adapter
web application works with Change and Configuration Management, Requirements
Management, and HP ALM. As the adapter web application is deployed
to its own application server, either Apache Tomcat or WebSphere® Application Server, there are
several considerations.
In the following topology, the adapter is installed on its own
application server. That server can be either Apache Tomcat or WebSphere Application Server.
HP ALM is on its own application server. Change and Configuration
Management (CCM), Jazz™ Team
Server (JTS), and Requirements Management (RM) are also on their own
server. The adapter resolves links from the Change and Configuration
Management work items, and Requirements Management work items back
to HP ALM changes on these servers.

Deploying the adapter web application (hpqm.war)
includes the selection of an application server. That server can be
either Apache Tomcat or WebSphere Application
Server. Based on your choice of application server, there are several
considerations:
- Installing the adapter web application on its own application
server, is suggested.
- It is necessary to change the HTTP session management cookie name
under several circumstances:
- The adapter is installed on the same WebSphere Application Server as CLM
- The adapter is behind the same reverse proxy as CLM
CLM and the adapter both use the same JSESSIONID cookie in an
HTTP session. CLM sometimes resets the cookie when you log in, which
causes the adapter to lose its session in some linking scenarios.
- Apache Tomcat is configured to use ports 9080 and 9443 in the HPInstallDir/server/tomcat/conf/server.xml file.
If necessary, change the port assignments as appropriate for your
system. For example, running the adapter on the same server that is
used by CLM requires a change to the port assignments. For more information,
see Changing the port numbers for the application server.