What is the best approach to consolidate disparate RQM 2.x and RTC 3.0.1.1 instances onto a single CLM instance on WAS?
Assuming the existing environment is RQM 2.0.1.x on qmserver.com/jazz, RTC 3.0.1.1 on ccmserver.com/ccm, and JTS 3.0.1.1 on ccmserver.com/jts what is the suggested way to consolidate these to a common CLM 4.0.1 server? Are there drawbacks or alternatives to the high level approach below?
- Upgrade RQM from 2.0.1.x to 3.0.1.1 on qmserver.com/jazz, pointing to JTS on ccmserver.com/jts
-
Upgrade JTS and RTC on ccmserver.com from 3.0.1.1 to 4.0.1
- Upgrade RQM from 3.0.1.1 to 4.0.1 on qmserver.com/jazz
- Perform server rename on qmserver.com/jazz to ccmserver.com/qm
Accepted answer
I have reviewed the 301 infocenter and you can use an existing JTS 301 for your 2x to 3x QM migration. Be careful what parameters you use for the upgrade scripts or the repotools scripts so that you do not overwrite the JTS tables. Basically, do not use the 'createTables' parameter.
Leave the QM server in its existing physical server, until you have upgraded all apps to 40x. Then tackle the reverse proxy issue.
Quoting from Moving Jazz Servers and URI Stability with CLM 2011:
Setting up a reverse proxy server will allow you to retain the previous public server root URI, while hosting the application on a server with a different name.
In your case, preserve QM public URI 'http://qmserver.com/jazz', but host the application on ccmserver.com/qm or ccmserver.com/jazz, the host URI choice doesn't matter, as long as the reverse proxy redirect is accurate. You want to preserve the ability to handle incoming requests to the existing public URI for QM but have the reverse proxy handle the redirect.
References of Interest: Configuring Enterprise CLM Reverse Proxies, Part 2: WebSphere and IHS Plugin method
Configuring Enterprise CLM Reverse Proxies: WebSphere and IHS Plugin method Separating JTS and CCM where the JTS and CCM were originally deployed using different ports
Leave the QM server in its existing physical server, until you have upgraded all apps to 40x. Then tackle the reverse proxy issue.
Quoting from Moving Jazz Servers and URI Stability with CLM 2011:
Setting up a reverse proxy server will allow you to retain the previous public server root URI, while hosting the application on a server with a different name.
In your case, preserve QM public URI 'http://qmserver.com/jazz', but host the application on ccmserver.com/qm or ccmserver.com/jazz, the host URI choice doesn't matter, as long as the reverse proxy redirect is accurate. You want to preserve the ability to handle incoming requests to the existing public URI for QM but have the reverse proxy handle the redirect.
References of Interest: Configuring Enterprise CLM Reverse Proxies, Part 2: WebSphere and IHS Plugin method
Configuring Enterprise CLM Reverse Proxies: WebSphere and IHS Plugin method Separating JTS and CCM where the JTS and CCM were originally deployed using different ports
One other answer
You may have a problem here. There is no way to merge a JTS with another one - so unless Step 1 can point to an existing JTS and merge in the data - you will not be able to do this.
It may be worth talking to support about this too.
anthony
It may be worth talking to support about this too.
anthony
Comments
1 vote
Comments
Rosa Naranjo
FORUM MODERATOR / JAZZ DEVELOPER May 07 '13, 10:54 a.m.Brian Fleming
May 08 '13, 2:35 p.m.