Skip to content
CA Application Performance Management - 10.5
Documentation powered by DocOps

Upgrade the Transaction Impact Monitor for CEM

Last update February 13, 2018

The Transaction Impact Monitor (TIM) is a network sniffer. The TIM passively listens on the network to all unfiltered traffic. The TIM configuration defines the filters and business services that it monitors. The metrics are based on the data flowing across a specific port that meet filter and business service criteria. The EM connected to the TIM Collector correlates the data with Agent data and stores the data in Postgres or Oracle. The Application Triage Map tab in the Workstation Investigator uses this data. 

Because the TIM installation is software, you must maintain and upgrade the software and not the hardware.

Important! The following procedures apply to any TIM upgrade to the latest version. For the complete steps for installing and uninstalling TIM , see Install and Configure TIM for CA CEM .

View Top Questions about a TIM Upgrade

This video answers the top questions regarding your CA APM TIM upgrade:

Disconnect the Software Appliance Computer and Shut Down the Enterprise Manager 

On your Enterprise Manager, disconnect the software appliance computer before you upgrade.

Follow these steps:

  1. From Customer Experience Manager (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

      Where <IP_Address> is the IP address or the DNS name for the Manager of Mangers (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.
    3. Close the page.
    4. Observe that the TIM stops.
  3. Verify that no extra accounts exist for the APM cemdb Database.
    For example, if a guest user account exists, the upgrade fails.
  4. Determine the size of the existing APM Database to assess time duration. The database size affects how long the upgrade process takes.
  5. (Linux only) If the Enterprise Manager is on a Linux computer, use a command-line terminal login. Define psql from the Postgres installation. 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"

    Where:

    • PGUSER: admin

    • PGPASSWORD: quality

  6. (Unix only) Switch to the BIN directory where PostgreSQL is installed.
    For example, if Postgres commands are installed under /opt/database/bin, 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"

    Where:

    • PGUSER: admin
    • PGPASSWORD: quality

    The command output looks similar to this example:

    ts_defect_meta_values | 1.90366e+07 | 2693
    ts_defects | 386284 | 87

  7. Shut down Enterprise Manager and all other Introscope components.
  8. 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.

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 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 the root with a console or SSH.
  2. Save the TIM configuration.
    Example: Save the configuration to /tmp/timconfig.tar file by running the following commands:

    cd / ; tar cf /tmp/timconfig.tar <TIM_Installation_Directory>/CA/APM/tim/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, 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. (Optional) Save a copy of the Evidence Collection scripts that are located here: <EM_Install>/cem/customer/evidencecollectors. 

    Tip: Save the Evidence Collection scripts to a remote server.

Prepare for the New TIM Installation on Linux Computers

Consider the following information before you install the TIM:

  • TIM supports RHEL 5 Update 5 and later versions from CA APM release 9.x to the latest version.
  • TIM supports RHEL 5 Update 9 and RHEL 6 Update x and later versions from CA APM release 9.x to the latest release.

Follow these steps:

  1. Depending on the RHEL operating system version, download one of these 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, 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:

    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 status httpd is stopped
      Start 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. 

Was this helpful?

Please log in to post comments.