RTC 5.0.2 - Migrating from Single server to Enterprise topology
Hello All,
We have the below CLM setup
OS : Suse Linux Enterprise Server 11 Sp3
CLM Apps : JTS+CCM 5.0.2
App Server: WAS 8.5.5 Base server (Single profile for both jts & ccm)
DB2 Server: IBM DB2 10.5
It is all in one single server topology.
Now we would like to move to CLM - E1 Enterprise - Distributed /Linux /DB2 as illustrated in Deployment/RecommendedCLMDeploymentTopologies5
Please let me know if my understanding is correct.
Migration Overview Steps:
*Setup 4 VM Servers
VM Server 1 for Reverse Proxy Server (IHS)
VM Server 2 for JTS +WAS
VM Server 3 for CCM +WAS
VM Server 4 for DB2 Server (JTS + CCM + DW)
*Install IHS & WAS 8.5.5 in VM Servers 1 , 2 & 3 (As JTS & CCM will require it's own profile in respective servers)
*Configure Reverse proxy settings
Now how do I move my DB2 server to the new location ? Do I install DB2 in the new VM Server 3 machine.. Backup the databases and restore them and if I update the teamserver.properties of jts ,ccm and dw later with the new location url for connection. Will they automatically pick up ?
and I know all my CLM artifacts will have my old server URLs. How do I change my public URI now?should I also do a server rename ?
Please advice.
Thanks in advance!
Vishnu M
One answer
You can do that by introducing a reverse proxy at the machine that hosts the public URI and then moving and redirecting to the servers, where you put the applications. See Rational solution for Collaborative Lifecycle Management 2012 Administration Workshop where we describe this.
The Databases can be moved to other servers, you just have to change the connection strings in the teamserver.properties or during a setup. That is no problem.
In general you should always plan your initial deployment and pick a public URI that is fully qualified not machine dependent and does not have to change ever. I can only emphasize how important that is, especially because you end up having the URI's everywhere in external documents in web sites, in other tools.
If the public URI can't stay, you have to do a server rename. Please note that multiple server rename will have a performance impact. If you have to contact support to get a key and choose a public URI that can stay as it is.
The Databases can be moved to other servers, you just have to change the connection strings in the teamserver.properties or during a setup. That is no problem.
In general you should always plan your initial deployment and pick a public URI that is fully qualified not machine dependent and does not have to change ever. I can only emphasize how important that is, especially because you end up having the URI's everywhere in external documents in web sites, in other tools.
If the public URI can't stay, you have to do a server rename. Please note that multiple server rename will have a performance impact. If you have to contact support to get a key and choose a public URI that can stay as it is.
Comments
Comments
Kevin Ramer
May 06 '15, 11:38 a.m.