Distributed Setup of CLM - struggling to find the right steps to register apps
we are moving from a single server to a distributed server topology. Struggling to find a full installation guide with steps to install and configure individual applications.
We have JTS on its own server - CCM, RM and RQM also on separate application servers.
Ran JTS setup, and one set of instructions seems to implicate that we have to registered the applications with JTS by using the "register step" and fill the parameters out manually ?? e.g. https://servername:port/ccm/scr
Looking for input if there's a full step by step to get from single to distributed.
This raised another question, can we have the same common uri for all distributed or do they have to have their own names.
One answer
If you are moving to a distributed system, you really need an HTTP server to front end it all. That will allow you to have a common hostname, and only change root context between applications.
See this article:
When you setup the server, and if you are using Liberty, it will generate a web plugin configuration file for you, which you can copy to the Web Plugin directory for IBM HTTP Server (which I recommend using). That will allow it to act as a proxy for the other servers. The file is typically written to /opt/IBM/JazzTeamServer/server/liberty/servers/clm/logs/state/plugin-cfg.xml.
You will also have to have SSL keys exchanged between the HTTP server and the liberty server. SSL keys for liberty are found in /opt/IBM/JazzTeamServer/server/liberty/servers/clm/resources/security/ibm-team-ssl.keystore.
Comments
Thanks Kenny .. question however, you state in this document "Really. Its quick, its easy to setup. Here are the instructions:" but there is no link to instructions.
Also, as we're moving from a single server to distributed, we had one common URI do we need to ideally rename so that each application server has its own common name
Thanks
Not sure what happened to my instructions! You can install HTTP server from an archive (which is MUCH easier):
So, yes you will need to rename if you have the port number in the URI currently (i.e. https://<hostname>;:9443/ccm. You want to point it to your HTTP server's hostname and ports. Thus traffic will hit your HTTP server through port 443 (which you don't have to
For updating the SSL certs, here's another guide:
Download 9.0.0-WS-IHS-ARCHIVE-linux-x86_64-FP006.zip from Fix Central (https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm%2FWebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=All&platform=All&function=fixId&fixids=9.0.0-WS-IHS-ARCHIVE-linux-x86_64-FP008&includeRequisites=1&includeSupersedes=0&downloadMethod=ddp)