How to Upgrade the TIM from 9.5 to 9.7

Because the TIM installation is software, you maintain and upgrade the software and not an appliance.
apmdevops97
Because the TIM installation is software, you maintain and upgrade the software and not an appliance.
The following procedures apply to the TIM upgrade from Release 9.5 to 9.7. To upgrade from Release 9.6 to the 9.7, install the TIM software for the current release.
View Top Questions about a TIM Upgrade
This video answers the top questions regarding your CA Application Performance Management TIM upgrade:

Disconnect the Software Appliance Computer and Shut Down the 9.5 Enterprise Manager
On your 9.5 Enterprise Manager, you disconnect the software appliance computer before you upgrade.
Follow these steps:
  1. From CEM, disconnect the TIM software appliance:
    1. Access CEM directly using the following URL:
      http://<IP_Address>:<Port_Number>/wily/cem/tess/app/admin/monitorList.html?pId=1
      Note: Where <
      IP_Address
      > is the IP address or DNS name for the MOM or a standalone Enterprise Manager.
    2. Select Setup, Monitors.
    3. Select the enabled TIMs.
    4. Click Disable.
    5. Log out.
  2. On the TIM software appliance computer, stop the TIM:
    1. Access the TIM Setup page directly using the following URL:
      http://<TIM_Computer_Name or IP_Address>/cgi-bin/wily/packages/cem/tim/index
    2. Click Start or Stop Tim, and then click Stop Tim. Close the page.
    3. Observe that the TIM stops.
  3. On the 9.5 Enterprise Manager, log in as a user with full read, write, and execute permissions on the Introscope directory, preferably as the root user.
  4. Remove the following SNMP plug-in JAR files in the <
    EM_Home
    >/ext directory if they exist:
    SNMPAlertActionEM.jar SNMPAlertActionWS.jar
  5. Verify that no extra accounts exist for the APM cemdb database. For example, if there is a "guest" user, the upgrade fails.
  6. Determine the size of the existing APM database for update time duration. The size of the database affects how long the upgrade process takes.
  7. If the Enterprise Manager is on a Linux computer, use a command-line terminal login, with psql from Postgres installation defined using a command path. With PGUSER being admin and PGPASSWORD being quality, run the following command:
    [root@tess ˜]# PGUSER=admin PGPASSWORD="quality" psql - t - d cemdb - c 'SELECT relname, reltuples, relpages * 8 / 1024 AS "MB" FROM pg_class ORDER BY relpages DESC;' | egrep "ts_defects | ts_defect_meta_values"
    Otherwise, switch to the bin directory where PostgreSQL is installed. For example, if Postgres commands are installed under /opt/database/bin, with PGUSER being admin and PGPASSWORD being quality, run the following commands in order:
    [root@tess *]# cd /opt/database/bin [root@tess ˜]# PGUSER=admin PGPASSWORD="quality" ./psql - t - d cemdb - c 'SELECT relname, reltuples, relpages * 8 / 1024 AS "MB" FROM pg_class ORDER BY relpages DESC;' | egrep "ts_defects | ts_defect_meta_values"
    The command output looks similar to this example:
    ts_defect_meta_values | 1.90366e+07 | 2693 ts_defects | 386284 | 87
    In this example, there is: 2693 MB, 2.7 GB of data; 87 MB defects. For a pre-4.5.6.1 upgrade, the process can take several days to complete. For a post-4.5.6.1 upgrade, the process depends on available resources, which can take several hours or one day to complete.
  8. Shut down your Enterprise Manager and all other Introscope components.
  9. Ensure the states of the following items:
    • All folders and text files are now closed.
    • No running process is accessing any file in your Introscope installation.
Install the New Enterprise Manager as New or Upgrade
Install the current Enterprise Manager using a new computer or by reusing an existing Enterprise Manager computer.
Follow these steps:
  1. Verify that all computers, virtual machines, and other components meet or exceed the recommended requirements.
    For complete system requirements, see the Product Compatibility Matrix.
  2. Follow the instructions for the procedure you want:
Back Up the TIM Configuration Data on the Software Appliance Computer
Back up all TIM configurations before upgrading in either of these cases:
  • You are reusing an existing 9.5 TIM software appliance computer as a TIM.
  • You are planning to use a new TIM computer.
Follow these steps:
  1. Log in to the TIM as root using a console or ssh.
  2. Save the TIM configuration to a file /tmp/timconfig.tar by running the following commands:
    cd <TIM_Installation_Prefix>/etc/wily/cem/tim tar cf /tmp/timconfig.tar config
  3. Save the /tmp/timconfig.tar file to another computer over the network. If you have a Linux or UNIX computer on your network, you can use scp to copy the file to the remote computer:
    scp /tmp/timconfig.tar remote-user@remote-host:timconfig.tar
    • remote-host
      Specifies the computer on which the file must be saved.
    • remote-user
      Specifies the user name on that computer.
  4. Save a copy of the Evidence Collection scripts located here: <
    EM_Install
    >/cem/customer/evidencecollectors.
Prepare for the New TIM Installation on Linux Computers
Consider the following information before you install the TIM:
  • TIM supports
    RHEL 5 Update 5
    version from CA APM release 9.x to 9.5.
    Note:
    x represents the releases earlier than CA APM release 9.5.
  • TIM supports
    RHEL 5 Update 9
    and
    RHEL 6 Update x
    (0, 1, 2) versions from CA APM release 9.6 to the current release.
Follow these steps:
  1. Depending on the RHEL operating system version, download one of the following TIM RPM files:
    • For
      RHEL 5 update 9
      version, download 5.x install.tar.
    • For
      RHEL6 Update x
      version, download 6.x install.tar.
  2. Verify that all supported configurations include Red Hat or CentOS 5.8 through 6.5.
  3. Install all required Linux packages.
Install the New TIM Software and Restore the Saved Configuration Data
After you install the operating system, you install the TIM software and then restore the saved TIM configuration data.
Follow these steps:
  1. Install and configure TIM software for monitoring transactions.
  2. Copy the previously saved TIM configuration data to /tmp/timconfig.tar on the TIM computer as follows:
    scp remote-user@remote-host:timconfig.tar /tmp/timconfig.tar
  3. Ensure that the web server is started and enabled on your operating system by performing the following tasks. 
    • Check the server status by running this command:
[caadmin@saswattim01 ~]$ chkconfig --list httpd httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
    • Activate the web server by running this command:
[caadmin@saswattim01 ~]$ sudo chkconfig --level 2345 httpd on [caadmin@saswattim01 ~]$ chkconfig --list httpd httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
    • Stop or restart the web service by running the following commands:
Stop the service:  [caadmin@saswattim01 ~]$ sudo service httpd stop httpd is stopped Stop the service: [caadmin@saswattim01 ~]$ sudo service httpd start Starting httpd: [ OK ] [caadmin@saswattim01 ~]$ sudo service httpd status httpd (pid 2133) is running...
Stop the TIM, restore the config files, and restart the TIM by running the following commands:
service tim stop cd <TIM_Installation_Prefix>/CA/APM/tim tar xf /tmp/timconfig.tar service tim start
The TIM configuration data is restored. The TIM upgrade for CEM is complete. 
If you encounter upgrade issues, do the following:
  • Review the schema.log and install.log files for errors. The default directory is: (Linux/Solaris) /database or (Windows) C:\Program Files\CA APM\Introscope<
    version
    >\install\schematools.log.
  • Ensure that Enterprise Managers and RTTM/Discovery are running correctly (Services Tab).