Upgrading from previous versions of Response Time to V7.3

Describes how to upgrade your Response Time monitoring environment.

This chapter provides the information you need to collect before you begin an upgrade, the steps involved in the upgrade, and any follow-up tasks that you might need to perform.

Note: After you complete the upgrade, data from previous versions of the Response Time agent is available only in the Tivoli Data Warehouse. You can see this information by looking at BIRT reports (described in the IBM Tivoli Composite Application Manager for Transactions Administrator's Guide) or from the ITCAM for End User Response Time Dashboard, version 6.2.

Before you begin

This section provides information about decisions and actions you should take before you begin an upgrade.

Check the prerequisites information about the required hardware and software. See Prerequisites in the ITCAM for Transactions Information Center.
Do not upgrade the Java™ version on a system running Response Time 6.2 Robotic or Dashboard agents to Java 1.5 until you upgrade those agents to version 7.1 or later. If you do, you cannot start the monitoring agents.
For any custom situations that you created from product-provided situations, you must make a copy of the product provided situation and give it a different name. All product provided situations are reset after an upgrade and you lose any customized situations that still have the name of the product provided situations.
Know the product codes for the monitoring agent that you are installing. See Response Time product codes.
Collect the information you need to know before you begin the upgrade. See Information to collect before you begin installation and configuration.
You cannot have different versions of either Client Response Time (t4) or Robotic Response Time (t6) installed on the same computer, because the agents will not correctly generate data. For example, you cannot have Client Response Time 6.2 FP1 and Client Response Time V7.3 on the same computer.
If you are upgrading to the Application Management Console monitoring agent, copy the robotic scripts and the Rational® Performance Tester runtime from the version 6.2 environment to the current environment.
Copy the robotic scripts located at <ITM>/kt1depot/T3, where <ITM> is the directory where IBM Tivoli Monitoring is installed, into the <ITM>/kt1depot/T3/<type> folder, where <type> is one of the following directories, based on the type of robotic script:
- Command Line: CLI_PLAYBACK
- LoadRunner: LOADRUNNER
- Robot GUI: ROBOT_GUI
- Rational Performance Tester: RPT
- Robot VU: ROBOT_VU
Install theApplication Management Console agent before you install any other Response Time agent.
If the scripts are copied directly from a previous version of the Application Management Console agent to the V7.3 agent, the scripts will be missing the subtransaction information when viewed in the Application Management Configuration Editor. The subtransaction information is added to scripts in V7.3 and the scripts must be uploaded again from the Rational Performance Tester workbench using the export wizard. When these scripts are uploaded again, meta-information about the subtransactions is included in the exported script. This subtransaction meta-information is only applicable to Rational Performance Tester scripts. All other scripts can be directly copied from a previous Application Management Console agent.

Process overview of upgrade

Upgrading a monitoring agent involves the same steps as installing an agent. This section provides an overview of the upgrade process with references to sections in this document where you can find additional information:

Table 1. Task overview of upgrade
What to do	Where to find more information
Obtain the installation software. Note: There is not a separate upgrade image; it is included in the regular installation software.	Either download the software from Passport Advantage® (see the Download Document in the ITCAM for Transactions Information Center) or use a product CD. Talk to your Tivoli® System Administrator.
Install the latest versions of Rational products: Rational Performance Tester (Required for Robotic Response Time) Rational Performance Tester is only required on systems where the scripts are recorded and developed, but is not required on systems where the agents are located. The export wizard must be at the latest version to support the latest versions of Rational Performance Tester. If you intend to reuse an existing installation of Rational Performance Tester version 8.0 or later, run the Integration Support installer to update the export wizard to the latest version. The Integration Support installer also applies additional hotfixes that are mandatory in ITCAM environments. Rational Robot (Optional) Rational Robot is also required if you intend to deploy Rational Robot scripts on Robotic Response Time agents.	Installing integration support for Rational Performance Tester Installing Rational Robot
Install the Tivoli Enterprise Monitoring Agent on a computer by itself without Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal. Agent specific application support on these components is installed on a different computer.	Install a monitoring agent on Windows systems Installing a monitoring agent on Linux or UNIX computers Performing a silent installation
Install Tivoli Enterprise Monitoring Agent specific application support on a computer other than where the monitoring agent is installed.	Install application support for Windows systems Install application support for Linux and UNIX
Enable file transfer to ITCAM for Transaction agents.	Enabling File Transfer (UNIX and Linux)
Configure the monitoring agent.	Configuring Application Management Console Configuring Client Response Time Configuring Robotic Response Time Configuring Web Response Time
Verify the installation of a Tivoli Enterprise Monitoring Agent.	Verify installations of Response Time monitoring agents
Configure the Eclipse help server.	Configuring the Eclipse help server
Setup remote deployment. (Optional) Response Time supports remotely deploying the monitoring agent across your environment from a central location, the Tivoli Enterprise Monitoring Server.	Working remotely
Configure IBM Tivoli Monitoring to forward events to Tivoli Enterprise Console. (Optional)	Tivoli Enterprise Console event mapping
Reboot the computer on which you installed and configured the agent.
Start the monitoring agent.
Configure for historical data collection. (Optional)	Setting up historical data collection with Response Time in the Administrator's Guide
Install a language pack. (Optional) You can install local language support on each computer on which the Tivoli Enterprise Portal is located	Installing and uninstalling the language pack

Follow-up or related tasks

The following are tasks for after you finish the upgrade:

Upgrading situations to profiles: You can run a command-line utility to migrate Response Time 6.2, FixPack1, configuration situations to Response Time V7.3 client, transaction and profile XML files. See Upgrading situations to profiles automatically.

Historical data collection

If you enabled historical data collection, you should disable warehouse data collection for the over time tables after completing an upgrade.

Web Response Time workspaces are empty after an upgrade.

All workspaces are blank until new data collection occurs. The V7.3 workspaces use a different set of queries and tables than 6.2.

After upgrading to the Application Management Console (t3), some previous clients and servers appear as gray entries in the Tivoli Enterprise Portal Navigator.

This is because they are no longer displayed in this location; they are now displayed under each specific Application under the Clients and Servers sub-nodes. You must clean up any offline entries in the TEP by doing the following:

Right-click Enterprise → Workspaces → Managed System Status.
Select all OFFLINE entries.
Right-click and select Clear Offline Entry.

If the monitoring agents fail to start immediately after an upgrade from 6.2.1 to V7.3 and

you receive error messages similar to the following one in the agent logs :

(486AA0F5.0000-E78:kt2sjni.cpp,1065, "SimpleJNI::runInitialization") Error: Unable to find AgentJNI (486AA0F5.0001-E78:kt2sjni.cpp,523,"SimpleJNI::loadVM") Exiting ...

Agent logs are located in <ITM>/tmaitm6/logs/ (for Windows) or <ITM>/logs for (UNIX).

<ITM> is the directory where IBM Tivoli Monitoring is installed.

If this occurs, do the following:

Configure the agent again. See the following chapters:
Restart the agent. See Starting or stopping monitoring agents in the Administrator's Guide.

If you install the RT 7.1 Application Management Console on Red Hat Enterprise Linux AS release 4 and run the agent configuration command itmcmd config -A t3

The following error is written to stdout: KCIIN0231E Could not update file : java.lang.IllegalArgumentException: Unknown section name: ttdbconfig. The following exception is written to itm_config.trc:

Do the following tasks:

Delete the log file, agent_t3.log, located in the ITM/config directory on UNIX systems, and ITM/TMAITM6 on Windows systems.
ITM is the directory where IBM Tivoli Monitoring is installed.
Run the agent configuration again. See Configuring Application Management Console from the GUI (UNIX and Linux)

Summarization behavior for the RRT_Playback_Status table has changed to be more accurate

If you collect Summarization (S&P) data for the RRT_Playback_Status tables, do the following after upgrading your Tivoli Enterprise Monitoring Server andTivoli Enterprise Portal support for Robotic Response Time.

Note: This procedure applies only if you summarize PLAYBACK status.

Upgrade the Robotic Response Time Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal support for yourIBM Tivoli Monitoring environment.
Stop the Warehouse Proxy, the Summarization and Pruning Agent, theTivoli Enterprise Monitoring Server, and the Tivoli Enterprise Portal.
Inside the Tivoli Data Warehouse database, drop the RRT_Playback_Status Summary tables and views. You do not have to drop the original source table. These tables have names like RRT_Playback_Status_H. For example to drop the hourly summary table issue the following command:
```
drop table "RRT_Playback_Status_H";
drop view "RRT_Playback_Status_HV";
commit;
```
Restart the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal, and Warehouse Proxy and Summarization and Pruning Agent.

The Summary tables are recreated the next time the Summarization and Pruning agent runs.

Re-configuring and restarting agents that are not upgraded

If after upgrading from a previous version you still have Response Time agents in your environment for a previous version that were not upgraded, be sure to manually re-configure and restart those agents to operate correctly.