Migrating RTC 2.0.0.2 iFix 5 and RQM 2.0.1.1 iFix 1
Hello,
I'm planning to migrate my RTC 2.0.0.2 iFix 5 and RQM 2.0.1.1 iFix 1 into a single server v.3.0.1.
I have DB2 9.5.x and WebSphere Application Server 7.0.0.17
Both RTC and RQM use the same context root " /jazz " and each has their
own URI. The new Server will have his own hostname and IP address.
Can I migrate both into a 1 JTS, 1 CCM and 1 QM ?
Is there a guide I can follow?
Thanx in advance and Best Regards, Adriano
I'm planning to migrate my RTC 2.0.0.2 iFix 5 and RQM 2.0.1.1 iFix 1 into a single server v.3.0.1.
I have DB2 9.5.x and WebSphere Application Server 7.0.0.17
Both RTC and RQM use the same context root " /jazz " and each has their
own URI. The new Server will have his own hostname and IP address.
Can I migrate both into a 1 JTS, 1 CCM and 1 QM ?
Is there a guide I can follow?
Thanx in advance and Best Regards, Adriano
One answer
Hello,
I'm planning to migrate my RTC 2.0.0.2 iFix 5 and RQM 2.0.1.1 iFix 1 into a single server v.3.0.1.
I have DB2 9.5.x and WebSphere Application Server 7.0.0.17
Both RTC and RQM use the same context root " /jazz " and each has their
own URI. The new Server will have his own hostname and IP address.
Can I migrate both into a 1 JTS, 1 CCM and 1 QM ?
Is there a guide I can follow?
Thanx in advance and Best Regards, Adriano
Hi Adriano,
we spent a lot of effort to provide many information in the product help. As a starter see the Interactive Upgrade Guide here: http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html . There are also articles in the Library such as https://jazz.net/library/article/669 and the workshop that would be a good source for your case https://jazz.net/library/article/669 it follows the upgrade guide.
Back to your question: As mentioned in the links above it is currently possible to migrate products to a shared JTS. However, if the products are distributed across several servers it is currently not not possible to migrate them to a single server. It is not possible to change the context root you are using /jazz and it is also not possible to change the hostname in the links. Please see the above links for details.
You could keep the products on the servers they are running today and use the new server as JTS server. You could also colocate the JTS server with one of the applications. I would suggest to use a virtual host for the JTS server, even if colocating it with an application. That gives you the flexibility to move t to a separate server later.