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?
Brian Fleming (1.6k●1●19●28)
| asked May 06 '13, 5:03 p.m.
retagged May 08 '13, 12:17 p.m. by Lisa Caten (342●9●13)
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?
|
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 Brian Fleming selected this answer as the correct answer
|
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 Comments Thanks Anthony, you could be right. The statement below, from http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_upgrade_rqm_overview.html made me think it would be possible to merge an RQM 2.x Jazz Server to an existing 3.0.1 JTS
The second scenario assumes that you have already upgraded to Jazz Team Server version 3.0.1 for one of several reasons:
1
It is possible Brian. I'm brushing up my memory and knowledge of the 2x to 3x upgrade scenarios and will reply with some more details soon.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Brian, what, if any, reporting is configured for this environment? Was RQM 2.x using what is called Rational common reporting? Is RTC 3011 and JTS 3011 configured with a data warehouse at this time? Please see this topic for more information: Reporting and the Upgrade Process
Thanks for the information Rosa. They don't use Insight yet, but plan to after these upgrades. Current reporting is done through csv exports and Excel.