Upgrading from Response Time Tracking 6.1

You can upgrade to Transaction Tracking from Response Time Tracking 6.1 by using the RTT migration tool.

The tool is used to migrate ARM filter configuration data from an Response Time Tracking 6.1 environment to Transaction Tracking. It converts the Response Time Tracking filter configuration data into an Application Management Console profile. Migrate the data before or after you installing Transaction Tracking.

Note: Before migrating the data, ensure that Application Management Console (t3 agent) is installed.

To migrate filter configuration information from Response Time Tracking 6.1:

  1. Export policies from the Response Time Tracking 6.1 Management Server:
    1. Ensure that JAVA_HOME is set to your Java™ installation. If Java was installed by IBM Tivoli Monitoring, the default locations are:
      • For Windows systems, C:\Program Files\IBM\Java50\jre\bin
      • For UNIX systems, /opt/IBM/ITM/JRE/platform/bin where platform is the code for the platform on which IBM Tivoli Monitoring is installed. For example, sol283 for Solaris version 8, 32 bit.
    2. Change directory to a temporary location such as /tmp/rttexport.
    3. Run the command: /opt/IBM/itcam/RTT/MS/scripts/cli/tmptcli.sh -GetAllAgentGroups
    4. Run the command: /opt/IBM/itcam/RTT/MS/scripts/cli/tmptcli.sh -GetAllPolicyGroups
    5. Run the command: /opt/IBM/itcam/RTT/MS/scripts/cli/tmptcli.sh -GetAllManagementPolicies

    A set of export directories are saved to the location you specified in step 1b. In this case /tmp/rttexport/dat/*.

    See Response Time Tracking 6.1 documentation for more detailed information.

  2. Run the RTT migration tool:
    • On Windows systems, run the RTT migration tool batch file, %CANDLE_HOME%\tmaitm6\tuspport\RTTMigrationTool.bat policy_file agentgroups_dir userID password
    • On Linux systems, run the RTT migration shell script file, $CANDLE_HOME/tmaitm6/arch/tu/tuspport\RTTMigrationTool.sh policy_file agentgroups_dir userID password
    Where:
    • policy_file is the full path to the policy. For example, /tmp/rttexport/dat/policies/MyListener.xml
    • agentgroups_dir is the full path to the agentgroups directory. In this case, /tmp/rttexport/dat/agentgroups
    • arch is the architecture product code
    • userID and password are the system administrator username and password for IBM Tivoli Monitoring

    This imports the configuration into the Application Management Console. You can view the policy as a profile in the Application Management Configuration Editor.

    Note: Ensure that the computer on which you run the RTT migration tool also has the Tivoli Enterprise Portal installed.
  3. Repeat step 2 for each policy in the export directory /tmp/rttexport/dat/policies/. For example, if there are five policies in /tmp/rttexport/dat/policies/*.xml, run the RTT migration tool five times.
  4. Log in to the Tivoli Enterprise Portal and in the Application Management Configuration Editor, edit the filters for the profile if required.

    In particular, policies with complex regular expressions that were valid in Response Time Tracking 6.1, may not be valid profiles in Transaction Tracking. Transaction Tracking supports literal characters and asterisk (*) wildcards.

    See Response Time Administrator's Guide at http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itcamt.doc_7.1.0.2/welcome.htm for valid expressions for filters.

Parent topic: Installing Transaction Tracking