How to upgrade & Migrate existing Jazz CLM 3.0.1.1 setup to CLM 4.0.4
Hello,
We are currently using Jazz CLM 3.0.1.1, and want to upgrade to the latest available CLM version of 4.0.4.
Our existing setup is described below.
Jazz CLM 3.0.1.1, All applications on 1 server per domain.(We have 2 domains where CLM is deployed).
Application Server: Tomcat 5
One database server for every domain, which hosts data for all CLM application deployments. We have seperate CLM deployment for each engagement.
Now we want to deploy CLM 4.0.4 for one engagement, which will be hosted on single server, and application server to be used is Websphere. i.e. topology will be as it is, but with CLM upgrade we also want to migrate the application server to Websphere.
What would be the best strategy to implement this upgrade & migration? I came to know that data can be migrated between CLM versions using repotools. I'm doing a test deployment first, is it a good strategy to Install the latest CLM 4.0.4 with Websphere application server, and only migrate the data using repotools?
Please help on this upgrade & migration.
Thank you in advance for your help.
Amar Shinde
2 answers
Comments
Hello Milan,
Thank you for the response. I've gone through Interactive Upgrade Instructions. Since it involves upgrading to latest version on existing environment. What I'm interested to know is; Is it possible that I install the CLM 4.0.4 on a new server and only upgrade the database using repotools. I don't know much about repotools.
In that way I will have all the latest CLM server applications installed & deployed on Websphere, and only task will remian to upgrade the database. Is that the right approach?
Thanks again!
Amar
Keep in mind that you are not just installing CLM 4.0.4 on a new server, but copying all the configuration files, adjusting any database connection information, creating a new location and reference for the database driver (if applicable), and configuring the etc/hosts and/or DNS lookup to retain the public URI mapping.
Lastly, I would suggest testing the migration sticking with Tomcat as the application server, then doing all the application testing, and then migrating to WebSphere, as a phased approach.