restoring CLM environment from backup
Hi,
we are using CLM 4.0.0.1 and we have two environments for CLM: production and pre-production which have different host names. So, when we tried to test production data on our pre-production environment, we found out on jazz help site that we need to prepare mapping files etc etc to change the server name. So, we followed instructions, created backups, and replaced them to our pre-production environment, together with all application files and folders (teamserver.properties, indices...). We created mapping file on production environment, tried to copy it to pre-production, we changed all url to new target environment, and we tried to import mapping file, and we got this message: CRJAZ2459E Error: To enable this feature you must obtain a key file from IBM sup port. Server Rename is a complex and potentially disruptive operation because i t may be difficult or impossible to correct the stored links into the server fro m other applications and systems. It is supported only for a limited set of sce narios, requires careful advance planning, and should generally be used only as a last resort when other approaches are unworkable. Please refer to the product documentation, and contact your IBM support representative for more information . CRJAZ2275I The import has been cancelled. So, what this mean? That we can't do server rename without IBM support? Can anyone help, please. Thanks, |
Accepted answer
Fariz Saracevic (874●6●13)
| answered Oct 12 '12, 10:40 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Oct 12 '12, 10:41 a.m.
Hi/Pozdrav Milane,
Server rename is a highly complex capability with significant impact not just on the core CLM applications, but also any applications connected to and interacting with the CLM products. For CLM 4.0, we are supporting two very specific, limited scenarios including Pilot to Production and Production to Staging. The first involves a scenario where customers want to take small evaluation deployments and scale up into deployment without losing data created during the pilot. The second is where customers replicate production environments to create isolated testing configurations where they can test using production data. Additional server rename scenarios are being planned for future release. Therefore, in order to ensure that customers like yourself understand what is and is not supported, and to make sure you are successful, you will need to call support for a key file in order to unlock this capability. They will guide you to see if server rename is applicable for your situation by asking you number of questions. For more information about server rename, please see Renamingyour Rational solution for CLM. Geoffrey Clemm selected this answer as the correct answer
|
Comments
yeah that really bad