It's all about the answers!

Ask a question

What are the steps to move to new CLM application servers?

Ken Murphy (1032934) | asked Jan 11 '15, 4:51 p.m.
We have the CLM 4.0.3 solution installed on SLE-10 servers.  We now want to move them to SLES-11 servers.  What are the steps to accomplish this?

1. Install CLM 4.0.3 on the new servers
2. Copy some properties files over from the SLES-10 servers to the SLES-11 servers.
3. Create aliases for the old server names so that they evaluate to the new server names

2 answers

permanent link
Paul Slauenwhite (8.3k12) | answered Jan 12 '15, 10:38 a.m.
edited Jan 12 '15, 11:03 a.m.
You have a couple of choices:

1. Use a reverse proxy (see
2. Rename the CLM server (see and

You may also have to migrate your DBs over to the new servers (see

Ken Murphy commented Jan 12 '15, 10:59 a.m.

Thanks Paul, but your answer confuses me (as do other posts somewhat related to this question).  We are only moving the CLM tools from one set of servers to another set of servers.  The SQL server database that contains the CLM tools data is on yet another server that is not changing.

We have the JTS and CM solution on "oldserver1" and the QM and RM tools on "oldserver2".  We want to move them to "newserver1" and "newserver2".  Do we just need to install the tools on "newserver1" and "newserver2", move some properties/configuration files from "oldserver1" and "oldserver2" to "newserver1" and "newserver2", and perform your recommended step 1 or 2 above?

Ara Masrof commented Jan 12 '15, 11:13 a.m. | edited Jan 12 '15, 11:13 a.m.


For clarification, once you have moved to a new server, is your intent to keep the same Public URI?

For example if your current Public URI is “”, will that still be valid once the new server is in place?

If not, you'll need to follow the Sever Rename steps (Paul included the links to the documentation in his post)

Paul Slauenwhite commented Jan 12 '15, 11:13 a.m.

Hi Ken,

In your case, you would not migrate your DBs.  I would suggest following the steps in Topologies and mapping files for moving a production deployment to another location (see

Ken Murphy commented Jan 12 '15, 5:28 p.m.

We don't actually plan on changing the public URI.  We are going to keep it the same.  Paul, does the link you provided above still apply?

Paul Slauenwhite commented Jan 13 '15, 7:48 a.m.

If the public root URI is not changing, there is no need to rename the server.  In this case (CLM version is not changing), you would do the new install on the new machine normally except for DB steps (you are reusing your DB server) and prior to bringing up the server they just ensure that is pointing to the existing DB instance.

I would suggest upgrading CLM while you are upgrading your hardware.

permanent link
Abraham Sweiss (2.4k1131) | answered Jan 12 '15, 6:58 p.m.
Hi Kevin,

I am going under the following assumptions:
a. Moving to the new server and keeping the same version of RTC
b. Keeping the same public url and the old server will be sunset
c. This is a TOmcat install

1. Install RTC on the new server. If possible use the same directory since this will make things easier going forward
2. Stop the existing server
3. From the original server, copy the server/conf directory and move it to the new server so to replace the server/conf directory of the new install
4. If the rtc indexes are located in a location outside the server/conf directory, they will also need to be copied and moved over
5. Check the properties files to make sure all the paths are valid for the new install
6. Alias the public url to the IP of the new host and make sure the DNS server is updated

Your answer

Register or to post your answer.