Upgrading your server when connected to a remote Db2 server

If you are completing a side-by-side upgrade, and the V8.1.3 Cloud APM server that you are upgrading from is connected to an existing remote Db2 server instead of the default local Db2 server, you must back up the databases separately to avoid any issues between the existing V8.1.3 server and the new V8.1.4 server that use these databases.

Complete the following steps as a root user to clone the WAREHOUS, SCR32, and DATAMART databases before the upgrade and to back up these databases separately.

1. Download the Cloud APM server installation image. Extract the server installation files for your offering. Complete steps 1 to 4 in Upgrading the server side-by-side.
2. Copy the backup.sh, rename.sh, and restore.sh scripts from the tools directory and the setup-dbconfig-linux_64.bin script from the packages/SCR directory on the V8.1.4 Cloud APM server installation image to the remote Db2 server system. You can connect to the existing Db2 server that was configured for Cloud APM V8.1.3.
3. Run the backup.sh script on the remote Db2 server system. If you are using the default Cloud APM administrator user IDs and passwords, run the backup.sh without parameters.
   For example:

   [root]# /root/min/tools/backup.sh
   Performing a backup...
   Processing the "install" component...
   Processing the "db2" component...Backup operation completed.
   Creating the backup file...All tasks finished successfully.
   Your backup is available in the following file:
   /tmp/backups/backup_20160824_061708.tar
   

   If you are using non-default user IDs and passwords, run the script with these parameters. For example,

   [root]# /root/min/tools/backup.sh  -u username -p password -z external_db2_instance

   where:

   username

   The non-default Cloud APM administrator user ID.

   password

   The non-default Cloud APM administrator password

   external_db2_instance

   The remote Db2 server instance user name.

   The script outputs the name of the backup file.
4. Run the script setup_dbconfig-linux_64.bin on the remote Db2 server system to set up the V8.1.4 SCR database. Run the script as the same Db2 instance user db2apm who ran the script during the creation of the V8.1.3. SCR database. Do not run the script as user root.

   su - db2apm
   /path/setup-dbconfig-linux_64.bin -i console
   exit

   Follow the console prompts:

   1. When you are prompted to choose a locale, enter 2 to select English.
   2. Enter 1 to accept the license agreement.
   3. Enter the absolute path to the installation folder or press Enter to accept the default path. The default path is the setup-dbconfig installation path for V8.1.3. Do not change this path, unless the path is incorrect. In this procedure, the path is referred to as /opt/ibm/db2/tbsmdb.

      The Cloud APM SCR database configuration tools installed by the setup_dbconfig-platform_64.bin script should not be installed into the same directory as the Tivoli Business Service Manager database configuration tools if the databases for both products reside on the same remote Db2 server.

   4. Enter 1 to select IBM Cloud Application Performance Management(APM) as the product that uses the database.
   5. Enter 1 to select Simple as the type of installation to run.
   6. Enter 2 to instruct the installer not to create the database schema, including the tables, table spaces, and views.
   7. Enter the following database configuration details when you are prompted:
      • Database Name (maximum 8 characters) (DEFAULT: SCR32): S1
      • Database host name or IP address (DEFAULT): host_name_or_IP_address
      • Database Port (DEFAULT: 50000): port
      • Database Path (DEFAULT): default_path
      where:

      port

      The port number that was specified when the SCR database was created. If you don't know the value, see the port number that is specified for the db2c_db2apm service in the /etc/services file.

      default_path

      The file system where the database was created. The default path is the home directory of the db2apm user. If a different file system was specified when the database was created, that file system should be specified instead.

   8. Enter 2 to specify not to encrypt the database.
5. As user root, run the restore.sh script on the remote Db2 server system to restore the backup that you created in step 3. This backup file is restored with the new V8.1.4 database names W1, S1, and D1.
   Run the restore.sh with the following options and values:

   [root]# min/tools/restore.sh -f backup_file
   -j metric_db_name -k scr_db_name -l datamart_db_name -z external_db2_instance
   

   For example:

   [root]# min/tools/restore.sh -f /tmp/backups/backup_20150824_061708.tar 
   -j W1 -k S1 -l D1 -z db2apm
   Restoring the data...Processing the "db2" component...
   Restore operation completed.
   All tasks finished successfully.

   where:

   backup_file

   The backup file name that you created in step 3.

   metric_db_name

   The optional new name for the metric database.

   scr_db_name

   The optional new name for the topology database.

   datamart_db_name

   The optional new name for the DATAMART database.

   external_db2_instance

   The remote Db2 server instance user name.

6. Upgrade the database schema and Java™ UDF routines in the restored Db2 SCR database.
   Enter:

   
   cd install_path/tbsmdb/tools/XMLtoolkit/bin
   ./scr_restore.sh -U db2apm -P passw0rd -n
   

   where install_path is the path that you entered when you set up setup-dbconfig.

   If you do not want the password visible on the command line, you can omit the -P flag and the script prompts for the password. For example:

   ./scr_restore.sh -n
   Enter the database password:

7. Enter the following command as the db2apm user for each database to adjust the buffer pool and transaction log after you determine the size of your environment.

   su - db2apm
   db2 connect to W1
   db2 alter bufferpool IBMDEFAULTBP IMMEDIATE size 
   W1_PAGE_COUNT
   db2 disconnect W1
   db2 connect to D1 
   db2 alter bufferpool IBMDEFAULTBP IMMEDIATE size D1_PAGE_COUNT
   db2 disconnect to D1 
   db2 connect to S1
   db2 UPDATE DATABASE CONFIGURATION FOR S1 USING LOGSECOND 25 
   db2 alter bufferpool IBMDEFAULTBP IMMEDIATE size 5000
   db2 alter bufferpool TBSMCFG16KBP IMMEDIATE size 1000
   db2 alter bufferpool TBSM4KBP IMMEDIATE size 1000
   db2 alter bufferpool TBSM32KBP IMMEDIATE size 1000
   db2 alter bufferpool TBSMSCR16KBP IMMEDIATE size 
   S1_PAGE_COUNT
   db2 disconnect to S1
   exit

   where:

   W1_PAGE_COUNT

   The buffer pool page count (8 K page sizes): 50000 for small; 100000 for medium; or 200000 for large.

   D1_PAGE_COUNT

   The buffer pool page count (8 K page sizes): 100000 for small; 200000 for medium; or 300000 for large.

   S1_PAGE_COUNT

   The buffer pool page count (16 K page sizes): 30000 for small; 50000 for medium; 100000 for large.

   Estimate the size of your environment (small, medium, or large) from the server requirements table in Cloud APM server hardware requirements.

8. Install the IBM Data Server Client on the virtual machine or computer system that you are using for the upgrade to Cloud APM server V8.1.4 by completing step 3 in Connecting to a remote Db2 server.
9. Install the 8.1.4 version of the Cloud APM server. Complete steps 5 to 13 in Upgrading the server side-by-side.
   Use the information in steps 10 and 11 in this procedure to guide your responses.
10. After the installation script detects that the backup of the V8.1.3 Cloud APM server information is configured with an existing remote Db2 server, respond to the prompts to provide or accept default values for the following configuration parameters to establish a connection with the remote Db2 database:
    1. hostname/IP address to the DB host or accept the default [localhost]:
    2. port number of the DB2 instance or accept the default [50000]:
    3. password for the user "itmuser":
    4. remote DB2 instance name or accept the default [db2apm]:
    5. password for the instance user "db2apm":
11. When you are prompted to enter the names of the new V8.1.4 databases (W1, S1, and D1) that you created when you specified the restore.sh command previously, accept the default values or enter the new values depending on your requirements.
    If you plan to use the V8.1.3 server, enter the names of the new databases (W1, S1, and D1) that you created when you ran the restore.sh command in step 5. Otherwise, if you accept the default values, you corrupt the databases that continue to be used by V8.1.3 of the Cloud APM server.

    Important: If you are entering the new database names, these names must match the names that are used with the restore.sh script in step 5 on the remote Db2 server:

    
    name of Metric database or accept the default [WAREHOUS]: W1
    name of Topology database or accept the default [SCR32]: S1
    name of Metric database or accept the default [DATAMART]: D1

    The V8.1.4 Cloud APM server installation continues.

    If the installer detects any agent configuration packages in install_dir/ccm/depot from a previous installation of the Cloud APM server, it warns you that it renamed the old packages and created new agent packages. The old packages are named install_dir/ccm/depot.old.

    If the installer detects a keyfiles directory in install_dir from a previous installation of the Cloud APM server, it warns you that it renamed the old keyfiles directory and created a new directory. The old keyfiles directory is named install_dir/keyfiles.old.

    A prerequisite scan of your environment starts and takes a few moments to complete. When the installation finishes, V8.1.4 of the Cloud APM server is configured with the existing remote Db2 server, which is the same instance as V8.1.3 but it is using different databases. It is using the databases that were created in step 5.
12. If you are not continuing to use the V8.1.3 Cloud APM server, you can use the V8.1.3 default database names with your V8.1.4 system by completing the following steps:
    1. When the V8.1.4 installation is complete, shut down the V8.1.3 and V8.1.4 Cloud APM server systems by entering the following command from any directory on both systems:

       apm stop_all

    2. On the remote Db2 server system, run the rename.sh script. Include the database names that you created in step 5 as arguments.
       For example, the following command renames the V8.1.4 databases from W1 to WAREHOUS, S1 to SCR32, and D1 to DATAMART:

       ./rename.sh W1 S1 D1

    3. On the V8.1.4 Cloud APM server system, start the kafka and server1 components by entering the following commands:

       
       apm start kafka
       apm start server1

    4. On the V8.1.4 upgraded system, enter the following command:

       install_dir/ccm/db_common.sh restore_original_db_names

       where install_dir is the Cloud APM server installation directory.

    The V8.1.4 Cloud APM server is reconfigured to use the original databases: WAREHOUS, SCR32, and DATAMART.

13. Shut down the V8.1.3 Cloud APM server system if it is running by entering the following command from any directory:

    shutdown -P now

14. Reassign the V8.1.3 Cloud APM server IP address or both the IP address and host name to the V8.1.4 server. Whether you reassign the IP address only or both the IP address and host name depends on your configuration.
    • If you use the Cloud APM server IP address to connect your agents to your server, complete the steps in Reassigning the server IP address to another server.
    • If you use the Cloud APM server host name to connect your agents to your server, complete the steps in Reassigning the server IP address and host name to another server.
15. Migrate your Hybrid Gateway configuration:
    • To migrate the Hybrid Gateway immediately after a restore, run these commands on the Cloud APM server as the root user:
      1. Copy the restored config.properties file to the ccm directory:

         cp install_dir/ccm/properties/config.properties.restored install_dir/ccm/properties/config.properties

      2. Update the date and time of the config.properties file so that any Hybrid Gateways already running will reload their configuration:

         touch config.properties

      3. Copy the updated config.properties file to the Central Configuration Services component:

         cp install_dir/ccm/properties/config.properties install_dir/wlp/usr/servers/min/dropins/CentralConfigurationServer.war/common/config.properties

    • If any configurations were done on the upgraded system after the restore, complete these steps:
      1. Copy these two lines from theinstall_dir/ccm/properties/config.properties.restored file:

         com.ibm.tivoli.ccm.encryption\:key= 
         com.ibm.tivoli.ccm.gaian.connect\:gaianReq=

      2. Replace the same lines in install_dir/ccm/properties/config.properties with the lines that you just copied.
      3. Copy config.properties to the Central Configuration Services component:

         cp install_dir/ccm/properties/config.properties install_dir/wlp/usr/servers/min/dropins/CentralConfigurationServer.war/common/config.properties

    To verify that the config.properties file in install_dir/wlp/usr/servers/min/dropins/CentralConfigurationServer.war/common/ was replaced, check that the modified date and time are current.