CLM 4.0.5 to CLM 5.0.2 server rename/upgrade strategy
Hello,
We are preparing for an upgrade of CLM_4.0.5 to CLM_5.0.2 Our topology is all of the applications are on one tomcat server. Our goal is to first upgrade the CLM version to establish a development environment om tomcate and then upgrade tomcat to WAS. We have a dev machine and dev instance of a database waiting. We have backup the current CLM 4.0.5 Oracle database and are re-instantiating it as a temp database to use for the upgrade so we do not need to stop our prod servers again. As a prepare and verification step, would it be worthwhile to get an instance of CLM_4.0.5 operational on the dev machine before the upgrade? If so, that would require a server rename before the upgrade to CLM_5.0.2. This raises a number of questions. 1.) the production machine went through a server rename some time ago. It is possible to do a rename again or is there a limit on the number of times a CLM instance can be renamed? 2.) Is our thinking correct that with a working copy, there no need to take the real production instance down for any of this? In other words, can we do the upgrade from working copy as if it were the production instance? 3.) If we do rename this on a staging (dev) machine, will it interfere with our prod machines? 4.) Is this working copy approach necessary or is it enough to have the database re-instantiated for an upgrade? David |
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Mar 06 '15, 3:20 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Having a test system to test an upgrade is, in general a good idea.
If you can't or don't want to isolate the test system from the other systems e.g. by using host file entries, you have to make sure the systems can't see each other. You can use a server rename to do that. You can do multiple server renames as far as I know, however this would affect the performance. As this is probably irrelevant for the test system that should be no problem. I don't know what working copy means in this context. However https://jazz.net/wiki/bin/view/Deployment/BackupCLM explains how backup restore works. You definitely want to use a complete copy/backup of the system and the database. You can't use the same database from two different systems and you need to have the systems isolated or one of them being down during server rename to avoid them to connect. |
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.