Upgrading to OMEGAMON XE for DB2 PE V4.1

OMEGAMON XE V4.1 monitoring agents require Tivoli Management Services version 6.1 FP3.

If you have already installed Tivoli Management Services, but you are not at V6.1 FP3, you must, at a minimum, upgrade the Tivoli Enterprise Portal desktop client, the Tivoli Enterprise Portal Server, and the hub Tivoli Enterprise Monitoring Server before you install your first V4.1 monitoring agent. In addition, any remote monitoring server through which a V4.1 OMEGAMON XE monitoring agent reports to the hub monitoring server must also be upgraded to TMS 6.1 FP3.

The OMEGAMON XE V4.1 products support a staged migration. This means as you are migrating from OMEGAMON XE V3.1 products to OMEGAMON XE V4.1 products, you may have a combination of V3.1 and V4.1. monitoring agents installed in your environment. For example, you may have an OMEGAMON XE for Mainframe Networks 4.1 monitoring agent and an OMEGAMON XE on z/OS 3.1 monitoring agent running on the same z/OS system during the migration period. Support of a mixed environment is provided as a migration aid. Operators working in such a transitional environment should be aware of the following issues.

The product information you see in the Tivoli Enterprise Portal reflects the level of code running on the Tivoli Enterprise Portal (V4.1), not the level of code running on the monitoring agent. This means if you are monitoring a system running a V4.1 monitoring agent, the workspaces and attributes available for monitoring and for creating situations accurately reflect V4.1. However, when you are monitoring a system running a V3.1 monitoring agent, the information you see in the Tivoli Enterprise Portal still reflects V4.1. This potentially misleading information can be seen in flyovers, full-text help, and information provided in the situation editor.

You can use the predefined dynamic workspace links provided by V4.1 agents to link from an OMEGAMON XE V4.1 workspace to the workspace of another OMEGAMON XE V3.1 product as long as the target workspace exists in the version 3.1.0 product. If the target workspace does not exist, you will receive message KFWITM081E.

In cases where the V4.1 version of the target workspace has been modified (for example, to accept link parameters to limit the data displayed) you may notice different behavior when you migrate the target product from version 3.1 to version 4.1. For example, the 3.1 version of the DB2 thread ID workspace does not filter the data. As a result, if you link to the 3.1 version of the DB2 thread ID workspace, all threads will be displayed. This same workspace was modified in version 4.1 to accept link parameters to display data for a specific thread ID. Once you update the OMEGAMON XE for DB2 product to version 4.1, you will notice that the data will be filtered to display data for a specific thread ID.

All user interfaces (except for the Configuration Tool and Install Shield ) provided with Tivoli Enterprise Portal version 6.1 and the OMEGAMON XE 4.1 monitoring agents are globalized. As a result, OMEGAMON XE 4.1 workspaces will be displayed in the specified language (for example, Spanish or Chinese). Since previous versions of the OMEGAMON XE monitoring agents were not globalized, OMEGAMON XE 3.1 workspaces will be displayed in English only.