Upgrading from previous versions of Response Time
Describes how to upgrade your Response Time monitoring environment.
Before you begin
- Check the prerequisites information about the required hardware and software. See Prerequisites in the Service Management Connect.
- 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 Product codes for more information.
- 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 Robotic Response Time (t6) installed on the same computer, because the agents will not correctly generate data.
- 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 $CANDLE_HOME/kt1depot/T3, where $CANDLE_HOME is the directory where IBM Tivoli Monitoring is installed, into the $CANDLE_HOME/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 the Application 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.4 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.4 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
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® or use a product CD. Talk to your Tivoli® System Administrator. |
Install the latest version of Rational Performance Tester:
|
|
Install the Tivoli Enterprise Management 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 Tivoli Enterprise Management Agent specific application support on a computer other than where the monitoring agent is installed. | |
Configure the monitoring agent. | |
Verify the installation of a Tivoli Enterprise Management Agent. | Verify installation 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. |
|
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 for 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 |
Follow-up or related tasks
- Upgrading situations to profiles
- You can run a command-line utility to migrate Response Time 6.2, FixPack1, configuration situations to Response Time V7.4 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.4 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.4 and you receive error messages similar to the following one in the agent logs:
(486AA0F5.0000-E78:kt2sjni.cpp,1065, "SimpleJNI::runInitialization")
Agent logs are located in %CANDLE_HOME%/tmaitm6/logs/ (for Windows) or $CANDLE_HOME/logs for (UNIX).
Error: Unable to find AgentJNI
(486AA0F5.0001-E78:kt2sjni.cpp,523,"SimpleJNI::loadVM") Exiting ...CANDLE_HOME 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 and stopping servers and 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)
- Delete the log file, agent_t3.log,
located in the ITM/config directory
on UNIX systems, and ITM/TMAITM6 on Windows systems.
- 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 and Tivoli 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.
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.