One of the IBM Rational Team Concert (RTC) users, having an integration with Focal Point (FP) were planning to move the production database
to test. On refreshing the test database, as they had RTC-FP integration in production, the same links would be preserved in the artifacts in test.
They had a concern if these links will be preserved in RTC, even in the test area after refresh. Of course, they would edit the Friends connection,
to point to the Test.
Here are the steps that I suggested and one of which was successfully used by the customer to isolate production from test (step 2).
The RTC links will be preserved in the Test area after refresh.
If the plan is to have a Test environment without the RTC links (in test database) to point to the production data, there are 2 options one can choose from.
Isolate the production and the test environment at network level.
Below are the details of each of these options:
1. Server Rename
Server rename is one of the approaches to achieve this. However, this has it's drawbacks and risks, explained in the links below:
This should definitely be the last approach one can take, after raising a Problem Management Record (PMR) with IBM Rational Support.
a. Server rename and the things to be aware before proceeding:
b. Impact of server rename and integrated products:
One should read through the details in these links before proceeding.
2. Isolate the production and the test environment at network level.
If one needs to isolate the Test environment from the production environment and avoid the server rename process, then this is
another way to go ahead with.
The following link gives a brief on the steps to stage the test environment:
NOTE: One needs to make sure that there are no possibilities of communication exchange between the test and production servers at all.
a. First, ensure that production and test servers are isolated at the network level so that any communication attempt is blocked.
This is to make sure the Test environment should not insert or update anything on the production environment.
b. Install CLM applications, Websphere Application Server (WAS), database on the test server following the usual methods.
c. Restore the copy of production databases in the test server.
d. Ensure the password of the database user (which is used in the CLM applications to connect to the database) is different than in
production. This can be the DB instance user, if one has used so.
e. Configure the Websphere and Deploy CLM applications as documented in IBM Infocenter.
Now, one needs to tell the server on how to connect to the new databases (the ones which were restored in Test environment), where the password
To get the encrypted password:
f. Run the jts/setup till Step 3 - Configure Database and
look at the jts/teamserver.properties file (which should now be in the process of getting regenerated) for the encrypted password.
Copy it in a word editor. The property name to look for the password is
g. Copy over the entire .../server/config directory from the production server to the Test server and open each of the teamserver.properties
file and update the password as noted in the above step.
i. Create an entry for production server in /etc/hosts file of test server.
Start the application in WebSphere and test.
NOTE: It is best to test this when production environment is offline or down for maintenance to avoid any unforeseen problems.
At this stage, the Test environment can only be accessed from test server and not from any clients, as the DNS is unaware of the alias in
To access the Test Environment, users can put a similar entry in their respective machines /etc/hosts file to point it to the Test environment.
I welcome any comments, suggestions on this note.