IBM Performance Management

Installing MongoDB v3.0.6 on a separate remote system

You can install MongoDB v3.0.6 on a separate remote system. Update the backup script that you will use for the Performance Management server upgrade to include the host name or IP address of the new version of MongoDB. This procedure does not require you to stop the Performance Management server.

About this task

The system where you install MongoDB cannot be any of the following systems:

The system where the v8.1.2 Performance Management server is installed.
The remote system that is running MongoDB v2.x.
The system where you plan to install the v8.1.3 Performance Management server.

Procedure

Complete the following steps as a root user:

Install MongoDB v3.0.6 on a remote system. Follow the steps in Installing a remote MongoDB.
Download the Performance Management server installation image, extract the server installation files for your offering, extract the v8.1.2 patch, 8.1.2.0-IBM-IPM-IF0014.tar, and run the apmpatch.sh patch script.
- If you are planning to upgrade the server side-by-side, see steps 1 to 4 in Upgrading the server side-by-side.
- If you are planning to upgrade the server on a single system, see steps 1 to 5 in Upgrading the server on the same system.

Run the backup.sh script without parameters from the tools directory on the system where the v8.1.2 Performance Management server is installed. The script outputs the name of the backup file. For example:

[root]# /root/min/tools/backup.sh
The server is configured with a remote DB2. This script must additionally be run on the DB2 machine to backup the database.
The log file was created at "/opt/ibm/ccm/logs/backup_20160424_005922.log".
Starting components of the IBM Performance Management server and verifying the passwords...
Performing a backup...
Processing the "install" component...
Processing the "oslc" component...
Processing the "ccs" component...
Processing the "apmui" component...
Processing the "spark" component...
Processing the "min" component...
Processing the "min_config" component...
Processing the "cscs" component...
Processing the "oidc" component...
Processing the "oauth2" component...
Processing the "scr" component...
Processing the "mongodb" component...
Processing the "itmcdp" component...
Processing the "supports" component...
Processing the "biagent" component...
Backup operation completed.
Starting the components...
Creating the backup file...
All tasks finished successfully. Your backup is available in the following file:
/opt/ibm/backups/backup_20160424_005922.tar

For more information about running the backup script when a non-default user name is configured for the Performance Management UI administrator user name, see step 6 of Upgrading the server on the same system.

Copy the backup file to the system where you plan to install the v8.1.3 Performance Management server.
Update the backup file to use the MongoDB v3.0.6 host name or IP address during the upgrade procedure.
1. Go to the directory where your backup file is stored.
```
cd directory_with_your_backup_file
```
2. Create a new directory, backup.extracted.
```
mkdir backup.extracted
```
3. Go to your new directory.
```
cd backup.extracted
```
4. Extract the backup tar file.
```
tar -xf ../backup_timestamp.tar 
```
5. Open the ./min_config/ibm_min_config_backup.json file.
6. In the JSON file, find the line that contains the host name or IP address of your v2.x MongoDB.
```
\"service\":\"com.ibm.tivoli.ccm.mongo\",\"name\":\"hostname\",\"value\":\"Remote_MongoDB_v2.x_IP_address_or_hostname\"
```
  Tip: Search for the text com.ibm.tivoli.ccm.mongo and move your cursor forward character by character until you locate the IP address or host name of your v2.x MongoDB.
7. Update the host name or IP address with the value for your v3.0.6 MongoDB. For example:
```
\"service\":\"com.ibm.tivoli.ccm.mongo\",\"name\":\"hostname\",\"value\":\"mongodb3.example.net\" 
```
8. Edit the ./mongodb/mongo.properties file. Change the property
```
mongo.hostname=Remote_MongoDB_v2.x_IP_address_or_hostname
```
  to
```
mongo.hostname=Remote_MongoDB_v3.x_IP_address_or_hostname
```
  For example:
```
mongo.hostname=mongodb3.example.net
```
9. Create a backup file in the backup.extracted directory.
```
tar -cf ../backup_timestamp.updated.tar *
```

Results

MongoDB v3.0.6 is running on another remote system and the backup file includes the IP address or host name of the new version of MongoDB.

What to do next

Upgrade the Performance Management server:

If you are upgrading the Performance Management server on a single system, start from step 6 of Upgrading the server on the same system.
If you are performing a side-by-side upgrade of the Performance Management server with a local DB2® server, start from step 5 of Upgrading the server side-by-side.
If you are performing a side-by-side upgrade of the Performance Management server with a remote DB2 server, start from step 2 of Upgrading your server when connected to a remote DB2 server.

When the upgrade of the Performance Management server is complete, you can uninstall the 2.0 version of MongoDB from the remote system. To uninstall, from the command line, enter:

opt/ibm/mongodb/bin/uninstall-mongodb.sh