SQL Server DB usage with CLM
I have SQL Server DB for RQM and RTC. If I do a new installation of CLM v3 and map this to the existing SQL Server DB of RQM and RTC, would this be fine and allowed without any issues.
|
3 answers
It is fine as long as you are installing it on the same machine. The idea is to have the same public uri as it was in your earlier installation.
Best Regards
Rajat |
Hi Abhijith,
The answer depends on what your intent is. Is this an upgrade from 2.x to 3.x? Or are you adding more RQM and RTC applications to an existing 3.x JTS? If this is an upgrade from 2.x to 3.x, you can use the same DB. But the upgrade process from 2.x to 3.x is complex and has many steps. You need to be careful. If you are upgrading, see the Upgrade Reference for CLM 2011 and the CLM 2011 Upgrade Workshop. If you are adding more RQM and RTC applications to an existing 3.x JTS, you'll probably want to create new databases for them (for example QM2, CCM2). I'm not sure if you could use the existing databases for the new CLM apps. But even so, using new databases will give you more flexibility in the future to change your CLM topology. Comments Let me rephrase or fine tune the requirement. Currently I have RQM and RTC version 2. RTC is not used at all. Both have database in SQL server. We are migrating RQM to version 3 and later 4. RTC migration is not in current roadmap but will come soon. RQM and RTC have their own servers. We have another server with 16GB RAM. I was thinking whether I can directly install CLM version3 in that server. Use the same DB of the existing RQM and RTC so that data are not lost and can be used continously. Is this a good idea or should I go ahead with the upgrade of RQM and RTC and do an integration later? Also if I can use the 16GB RAM server with CLM version 3 or 4, can I use the same URI of RQM server? |
|
Hi Abhijith,
You must use the same public URI for RQM (or any CLM app) even if you move it to another server (the exception is if you use the 4.x server rename feature, though you might want to only use that as a final option). So you can migrate to your new server, but that server name must be the same as the original server. You can re-map the IP address in the DNS. There are also ways to use a reverse proxy to keep the same public URI externally, but have different server names for the machines hosting the CLM apps inside the reverse proxy. The easiest and safest approach would be to upgrade to 3.x first on your current server. When you're confident the upgrade has been successful, you could move to the new server (maintaining the public URI). You can do this by installing the apps on the new server, then pointing the database locations in teamserver.properties to the appropriate DB server. See Moving Jazz Servers and URI Stability with CLM 2011 for more info. |
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.