Move the CCM or RMM application to a new location

Edit online

You can move the Change and Configuration Management or IBM Engineering Systems Design Rhapsody - Model Manager application to a new location.

About this task

To perform the migration of the Change and Configuration Management (CCM) and IBM Engineering Systems Design Rhapsody - Model Manager (RMM) applications that are installed into the same IBM® Installation Manager group, two instances of the CCM application must be installed into a target folder. However, Installation Manager does not allow to install two or more instances of the same application into the same group. You can use server rename to move either the CCM or RMM application into a separate installation folder.

Examples:

Examples in this topic are for moving the RMM application.
In the following examples, the installation folder corresponding to the existing RMM 6.x is referred to as old_install_dir, and the new RMM 6.x that you will be installing for server rename, is referred to as new_install_dir.
Examples below do not provide steps that should be performed in an environment that uses Jazz Authorization Server. See Server rename and the Jazz Authorization server for more information.
Also, the code snippet examples are for UNIX platforms.

This topic is for an installation topology without the use of a reverse proxy. If you are using a reverse proxy in your deployment, see the following resources:

In order to perform a server rename procedure, you must install a separate RMM application along with your old RMM installation. There are two options for installing the RMM application:

Install the RMM application on the same server as the old application: In this case, you must change the port number during the rename process. For details, see Changing the port numbers for the application server.
Install the RMM application on a separate server as the old application: In this case, you must change the fully qualified hostname during the rename process.

This topic is divided into two sections:

WebSphere Application Server Liberty Profile
WebSphere Application Server

WebSphere Application Server Liberty Profile

Edit online

About this task

The following procedure is for the WebSphere Liberty basic registry to manage users. For LDAP, see Configuring an LDAP or an LDAP/SDBM connection.

Procedure

Install RMM 6.x (the same version as the existing RMM installation) into a new folder (new_install_dir). Ensure to select Install with WAS Liberty Profile.
Prepare a mapping file for the server rename procedure:
1. Ensure the existing server is up and running.
2. Open a command window and enter the following commands:
  - For Windows:
    cd old_install_dir\server repotools-jts.bat -generateURLMappings toFile=MAPPINGS.TXT adminUserId=adminUserId adminPassword=adminPassword repositoryURL=https://hostname:port/jts
  - For Linux:
    cd old_install_dir/server ./repotools-jts.sh -generateURLMappings toFile=MAPPINGS.TXT adminUserId=adminUserId adminPassword=adminPassword repositoryURL=https://hostname:port/jts
3. Update the generated MAPPINGS.TXT file: Comment out or remove the source and target lines for applications that should not be renamed and keep only one pair related to the RMM application:
```
source=https://hostname:old_https_port/am
target=https://hostname:new_https_port/am
```
  Note: new_https_port is a random port number that should manually be changed since it is not automatically added to the generated mapping file.

Verify the MAPPINGS.TXT file by entering the following command:

./repotools-jts.sh -verifyURLMappings mappingFile=MAPPINGS.TXT adminUserId=adminUserId adminPassword=adminPassword repositoryURL=https://old_hostname:port/jts

Go to old_install_dir/server and stop the server.
Back up the existing source environment.
Go to new_install_dir/server and enter the following command to create the WebSphere Liberty server.
```
./repotools-am.sh -help
```
This command creates the new_install_dir/server/liberty/servers/clm folder.

Copy the RMM application indices and configuration files into the new_install_dir folder:

cp -R old_install_dir/server/conf/am/indices new_install_dir/server/conf/am/indices
cp old_install_dir/server/conf/am/teamserver*.properties new_install_dir/server/conf/am
cp old_install_dir/server/conf/am/am.properties new_install_dir/server/conf/am

For Apache Derby database only: Copy the Apache Derby database:
First, enter the following command to delete the new_install_dir Apache Derby database:
```
rm -rf new_install_dir/server/conf/am/derby/repositoryDB
```
Then, enter the following command to copy the Apache Derby database:
```
cp -R old_install_dir/server/conf/am/derby/repositoryDB new_install_dir/server/conf/am/derby/repositoryDB
```

Copy the WebSphere Liberty basicUserRegistry.xml file:

cp old_install_dir/server/liberty/servers/clm/conf/basicUserRegistry.xml new_install_dir/server/liberty/servers/clm/conf

Copy the lpta.keys file:

First, make a backup and delete the lpta.keys file from the new_install_dir server.

rm new_install_dir/server/liberty/servers/clm/resources/security/ltpa.keys

The copy the lpta.keys file to the new server:

cp old_install_dir/server/liberty/servers/clm/resources/security/ltpa.keys new_install_dir/server/liberty/servers/clm/resources/security

Go to the new_install_dir/server/liberty/servers/clm folder and open the server.xml file for editing.
Modify the HTTP and HTTPS ports:
```
<httpEndpoint id="defaultHttpEndpoint"
host="*"
httpPort="<new_http_port>"
httpsPort="<new_https_port>" />
```
Note:
The <new_http_port> is a random port number for HTTP protocol.

The <new_https_port> is a random port number for HTTPS protocol defined in step 2.
Uninstall the RMM application form the old_install_dir. Ensure that am.war and am.war.zip files are deleted from the following folders: old_install_dir/server/liberty/servers/clm/apps and old_install_dir/server/liberty/clmServerTemplate/apps.
Go to the old_install_dir/server folder and create a file called serverConf.txt with the following content:
```
#RMM

new_install_dir/server/conf
```
Copy the ImportUMLMappings.activate file to the old_install_dir/server/conf folder. The ImportUMLMappings.activate file must be obtained from IBM Software Support. See Moving a pilot or full production deployment by using server rename for more information.
RMM version 6.x does not contribute to LQE and LDX. This step should be performed if required by other applications. For the Lifecycle Query Engine and Link Index Provider applications, ensure that you completed the During server rename section of Impact of server rename on Lifecycle Query Engine and Link Index Provider.

Open a command window and enter the following commands:

cd old_install_dir/server
./repotools-jts.sh -importURLMappings fromFile=MAPPINGS.TXT serverConfFile=serverConf.txt

Verify that the rename is successful by checking the console output and the jazz_install_dir/server/repotools-jts_importURLMappings.log file.

Start both servers:

cd old_install_dir/server
./server.startup

cd new_install_dir/server
./server.startup

Log in to Jazz Team Server and open the following URL in a browser:
```
https://hostname:old_https_port/jts/serverRenameStatus
```
Verify that the rename process completed successfully by going through all the RMM project areas that are in read only mode. Check that all application friend URLs are correct.
After verifying everything, select the checkbox to remove the read only mode and complete the rename process.

WebSphere Application Server

Edit online

About this task

The following scenario is for the installation of multiple applications installed into different Installation Manager groups on different servers.

Server 1: JTS, CCM, RMM
Server 2: DCC
Server 3: LQE

The goal is to move the RMM application from server 1 into a new server 4 along with the CCM application and Architecture Management Domain Extension for CCM in a new instance of WebSphere Application Server.

Procedure

Install the version 6.x RMM application on server 4.
Install and configure WebSphere Application Server on server 4.
Prepare a mapping file for the server rename procedure:
1. Ensure the existing server is up and running.
2. Open a command window and enter the following commands:
```
cd old_install_dir (server 1)/server
./repotools-jts.sh -generateURLMappings toFile=MAPPINGS.TXT adminUserId=adminUserId adminPassword=adminPassword repositoryURL=https://hostname:port/jts
```
3. Update the generated MAPPINGS.TXT file: Comment out or remove the source and target lines for applications that should not be renamed and keep only one pair related to the RMM application:
```
source=https://old_hostname:ort/am
target=https://new_hostname:port/am
```
  Note: new_hostname corresponds to the host name of server 4.

Verify the MAPPINGS.TXT file by entering the following command:

./repotools-jts.sh -verifyURLMappings mappingFile=MAPPINGS.TXT adminUserId=adminUserId adminPassword=adminPassword repositoryURL=https://old_hostname:port/jts

RMM version 6.x does not contribute to LQE and LDX. This step should be performed if required by other applications. For the Lifecycle Query Engine and Link Index Provider applications, ensure that you completed the Preparing for server rename section of Impact of server rename on Lifecycle Query Engine and Link Index Provider.
For Data Collection Component, ensure that you performed all the required actions described in Impact of server rename on the Data Collection Component.
Log in to WebSphere Application Server on server 1 and undeploy the am.war application.
Stop WebSphere Application Server on server 1, 2, and 3.
Back up the existing source environment.

Copy the RMM application indices and configuration files into the new_install_dir folder:

cp -R old_install_dir/server/conf/am/indices new_install_dir/server/conf/am/indices
cp old_install_dir/server/conf/am/teamserver*.properties new_install_dir/server/conf/am
cp old_install_dir/server/conf/am/am.properties new_install_dir/server/conf/am

For Apache Derby database only: Copy the Apache Derby database:
First, enter the following command to delete the new_install_dir Apache Derby database:
```
rm -rf new_install_dir/server/conf/am/derby/repositoryDB
```
Then, enter the following command to copy the Apache Derby database:
```
cp -R old_install_dir/server/conf/am/derby/repositoryDB new_install_dir/server/conf/am/derby/repositoryDB
```
Copy the ImportUMLMappings.activate file to the old_install_dir/server/conf folder. The ImportUMLMappings.activate file must be obtained from IBM Software Support. See Moving a pilot or full production deployment by using server rename for more information.
RMM version 6.x does not contribute to LQE and LDX. This step should be performed if required by other applications. For the Lifecycle Query Engine and Link Index Provider applications, ensure that you completed the During server rename section of Impact of server rename on Lifecycle Query Engine and Link Index Provider.
If you can map the network drives from the Jazz Team Server host, follow these steps:
1. Map a network drive from the Jazz Team Server host to each of the application hosts.
2. Go to the old_install_dir/server folder and create a file called serverConf.txt that contains a list of remote server/conf directories. For example:
```
#Remote DCC
D:/JazzTeamServer/server/conf
#Remote RMM
R:/JazzTeamServer/server/conf
```
3. Open a command window and enter the following commands
```
./repotools-jts.sh -importURLMappings fromFile=MAPPINGS.TXT serverConfFile=serverConf.txt
```
If you cannot map the network drives from the Jazz Team Server host, follow these steps:
1. Open a command window and enter the following command:
```
./repotools-jts.sh -importURLMappings fromFile=MAPPINGS.TXT
```
2. Copy the server/conf/jts/.mappingEvent file to the remote applications configuration directories that participated in server rename.
  
  Note: The event file is generated when you import the mappings. You must copy the .mappingEvent file after you import the mapping file but before you start the server.
Start WebSphere Application Server on server 1, 2, 3, and 4.
Log in to Jazz Team Server and open the following URL in a browser:
```
https://old_hostname:port/jts/serverRenameStatus
```
Verify that the rename process completed successfully by going through all the RMM project areas that are in read only mode. Check that all application friend URLs are correct.
After verifying everything, select the checkbox to remove the read only mode and complete the rename process.
RMM version 6.x does not contribute to LQE and LDX. This step should be performed if required by other applications. For the Lifecycle Query Engine and Link Index Provider applications, ensure that you completed the After server rename section of Impact of server rename on Lifecycle Query Engine and Link Index Provider.
For Data Collection Component, ensure that you performed all the required actions described in Impact of server rename on the Data Collection Component.

What to do next

Use the Interactive Upgrade Guide and select The applications are installed in different package groups radio button to generate a guide to upgrade your RMM application.