We are migrating our RTC 6.0.2 production server (single server environment) from an OLD server running SLES Linux/Oracle 11.2/Liberty, to a NEW server running Red Hat Linux/Oracle 12.2/Liberty. To perform this server migration, we want to confirm that the following steps are correct. We have tested this approach on a separate RTC test server, and the approach seems to work well, but we want to be sure that we have not missed anything.

Note that

• Our RTC 6.0.2 production environment uses Jazz Team Server (JTS) and Change and Configuration Management (CCM) only
• We use LDAP for user authentication
• Our network is part of a secure enclave that does not have direct access to the Internet, but does allow us to manually transfer IBM packages needed to install RTC into the secure enclave
• RTC URLs are:

RTC JTS URL: https://clm.seg.org:9443/jts

RTC CCM URL: https://clm.seg.org:9443/ccm

Migration Steps

Step 1 below is run by our Oracle manager Linux user (oracle user), and all other steps below are run by our RTC manager Linux user (rtcmgr user).

Below, $RTC=<RTC installation directory>

Copy data from OLD server to NEW server:

1.       As Oracle manager Linux user (oracle user), export/clone RTC Oracle database from OLD server (Oracle 11.2) to NEW server (Oracle 12.2)

• On NEW server, create empty Oracle 12.2 database with one container database (CDB) and one pluggable database (PDB)
• On NEW server, create jts, ccm, and dw tablespaces
• On NEW server, create jts, ccm, and dw users
• On OLD server, export jts, ccm, and dw tablespaces from Oracle 11.2 database using expdp
• On NEW server, import jts, ccm, and dw tablespaces into Oracle 12.2 PDB using impdp

2.       As RTC manager Linux user (rtcmgr user), copy the following five files from OLD server to a temporary holding area on NEW server:

• $RTC/server/liberty/servers/clm/conf/ldapUserRegistry.xml
• $RTC/server/liberty/servers/clm/server.xml
• $RTC/server/liberty/servers/clm/apps/clmhelp.war.zip (large full-help version, 1588456976 bytes)
• $RTC/server/conf/jts/teamserver.properties
• $RTC/server/conf/ccm/teamserver.properties

On NEW server:

3.       Modify /etc/hosts to allow RTC URLs to reference NEW server, while OLD server is still active

• /etc/hosts: add a line: <IP address of NEW server> clm.seg.org

4.       Install new clean version of IBM Installation Manager (IBMIM), version 1.8.7

• unzip agent.installer.linux.gtk.x86_64_1.8.7000.20170706_2137.zip and run userinst

5.       Run IBMIM, add JTS-CCM-QM-RM-JRS-RELM-repo-6.0.2.zip as a repository, and install a new clean version of RTC 6.0.2, installing only JTS and CCM

BEFORE running RTC on NEW server:

6.       Copy the five OLD server files from Step 2 to the following locations, respectively, on the NEW server (note that the first three locations use clmServerTemplate):

• $RTC/server/liberty/clmServerTemplate/conf/ldapUserRegistry.xml
• $RTC/server/liberty/clmServerTemplate/server.xml
• $RTC/server/liberty/clmServerTemplate/apps/clmhelp.war.zip (large full-help version, 1588456976 bytes)
• $RTC/server/conf/jts/teamserver.properties
• $RTC/server/conf/ccm/teamserver.properties

7.       Perform the following steps to finalize preparation of clmhelp.war.zip (large full-help version, 1588456976 bytes)

• cd $RTC/server/liberty/clmServerTemplate/apps
• rm –rf clmhelp.war    # remove existing clmhelp.war directory
• mkdir  clmhelp.war    # create empty clmhelp.war directory
• cd     clmhelp.war    # change directory into the empty clmhelp.war directory
• cp  ../clmhelp.war.zip .
• unzip  clmhelp.war.zip
• rm     clmhelp.war.zip
• # In the existing clmhelp.war directory, there should now be two subdirectories: META-INF and WEB-INF
• # Leave the large full-help zip file ../clmhelp.war.zip alone

8.       Perform the following steps to prepare JTS and CCM teamserver.properties files:

• Modify old Oracle 11.2 references to point to new Oracle 12.2 references in the files

$RTC/server/conf/jts/teamserver.properties

$RTC/server/conf/ccm/teamserver.properties

--> i.e., verify that the following values in the teamserver.properties files are correct:

com.ibm.team.repository.db.jdbc.location

com.ibm.team.datawarehouse.db.jdbc.location

com.ibm.team.datawarehouse.db.base.folder

Start RTC on NEW server for the first time:

9.       Start RTC on NEW server

• cd $RTC/server
• ./server.startup

10.   Run JTS setup

• Login to NEW server as an RTC administrator user (to be authenticated with LDAP), and run Linux firefox from the NEW server
• Connect to  https://clm.seg.org:9443/jts/setup
• Ensure “Custom Setup” is selected and click “Next”
• All required values should automatically be pulled from teamserver.properties files, and all tests should succeed
• Continue to click “Next” and follow instructions to complete Setup
• Once Setup is complete, connect to https://clm.seg.org:9443/ccm/web from the same firefox browser and verify RTC is functioning correctly on NEW server

Complete Migration

11.   Change global alias for clm.seg.org to point to NEW server

12.   Connect to https://clm.seg.org:9443/ccm/web from any location to access RTC on NEW server

RTC migration is now complete.