IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page ]


Installing IBM Tivoli Monitoring for Transaction Performance 5.2 Fix Pack 1

This section describes the fix pack installation utilities and provides the recommended installation procedure.

ISMP launcher and AutoUpdate

The fix pack provides the following utilities for installing the upgrade code on all supported platforms:

You are required to uninstall and reinstall existing J2EE monitoring components after upgrading the management server and management agents. This ensures that the J2EE monitoring components use the fix pack code.

Installation procedure

  1. Perform the following steps to install the fix pack:
    1. On the management server, insert the CD labeled 5.2-WTP-FP01.
    2. Launch one of the following executable files to run the installation program for your operating system:
      Table 2. ISMP-based installers for management server upgrades
      Management server installer file names Management server operating systems
      setup_MSFixpack_w32.exe Microsoft Windows 2000
      setup_MSFixpack_sol.bin Solaris Operating Environment
      setup_MSFixpack_lin390.bin zLinux
      setup_MSFixpack_lin.bin Intel-based Linux platforms, including Red Hat Linux, SuSE Linux, and TurboLinux
      setup_MSFixpack_aix.bin AIX
  2. Follow the instructions in the Install wizard to install the management server.
    Note:
    WebSphere Application Server is stopped and restarted during the procedure. If your management server is currently set up to use port 9449, change the management server port number to use a different port number (such as the default port of 9445) when prompted for port numbers in the management server. Port 9449 is used by an IBM Tivoli Monitoring for Transaction Performance listening function.
  3. Perform the following steps from an upgraded management server to upgrade the management agents:
    1. (If you are updating management agents on which the J2EE monitoring component is installed) Run the updateprops command if any of the following circumstances exists:
      • The J2EE monitoring component is running on an application server where security is enabled, and the user ID or password has changed.
      • The J2EE monitoring component is running on an application server where security was not enabled when the component was installed, and security is now enabled.
      • The J2EE monitoring component is running on an application server using an administrative port number that has changed.

      Additional information: The updateprops command enables you to change the user ID, password, or administrative port number that the fix pack uses to connect to the application server. For more information about the upgradeprops command, see Command for uninstalling the J2EE component.

    2. Start IBM Tivoli Monitoring for Transaction Performance using the following steps:
      1. Launch Microsoft Internet Explorer.
      2. Access the management server by typing in the management server URI.

        Additional Information: The following examples show URIs for a nonsecure and a secure installation of a management server called myhost.ibm.com, using the default port numbers:

        • For HTTP (nonsecure):
          http://myhost.ibm.com:9081/tmtpUI
        • For HTTPS (secure):
          https://myhost.ibm.com:9445/tmtpUI
    3. Select System Administration -> Work with Agent Updates to display the Work with Agent Updates window.
    4. Select all of the management agents on which you want to install the fix pack.
    5. Select Install Update from the drop-down list, and click Go.

      Additional information: The selected management agents download the required software and update with the required files. For more information about the AutoUpdate function, see the online help information. To access online help, click the question mark (?) in the upper-right corner of the window. See also AutoUpdate feature for upgrading management agents.

  4. (If you have active J2EE monitoring components in your environment) Perform the following steps to ensure the correct operation of the J2EE monitoring component:
    1. Navigate to System Administration -> Work with Agents, and select the agents on which the J2EE component is running.
    2. Select Remove component from the drop-down list, click Go, and specify the J2EE component for removal.
    3. Stop the J2EE-instrumented application servers.
    4. Stop the management agent process.
    5. Open the <MA_root>/app/instrument directory, and delete all the files and directories in the directory.
    6. Delete the files and shared libraries that were installed on your application server when the J2EE component was installed.

      Additional information: Following is a list of the files and libraries installed with the J2EE component, listed by application server platform and operating system:

      WebSphere Application Services Versions 4 and 5:

      <APP_SERVER_HOME>/lib/ext/armjni.jar
      <APP_SERVER_HOME>/lib/ext/copyright.jar
      <APP_SERVER_HOME>/lib/ext/core_util.jar
      <APP_SERVER_HOME>/lib/ext/ejflt.jar
      <APP_SERVER_HOME>/lib/ext/eppam.jar
      <APP_SERVER_HOME>/lib/ext/jffdc.jar
      <APP_SERVER_HOME>/lib/ext/jflt.jar
      <APP_SERVER_HOME>/lib/ext/jlog.jar
      <APP_SERVER_HOME>/lib/ext/probes.jar

      WebLogic:

      <APP_SERVER_HOME>/server/lib/ext/armjni.jar
      <APP_SERVER_HOME>/server/lib/ext/copyright.jar
      <APP_SERVER_HOME>/server/lib/ext/core_util.jar
      <APP_SERVER_HOME>/server/lib/ext/ejflt.jar
      <APP_SERVER_HOME>/server/lib/ext/eppam.jar
      <APP_SERVER_HOME>/server/lib/ext/jffdc.jar
      <APP_SERVER_HOME>/server/lib/ext/jflt.jar
      <APP_SERVER_HOME>/server/lib/ext/jlog.jar
      <APP_SERVER_HOME>/server/lib/ext/probes.jar

      WebSphere windows platforms:

      <APP_SERVER_HOME>/bin/ijitipi.dll
      <APP_SERVER_HOME>/bin/jitipi.dll  

      WebSphere UNIX platforms:

      <APP_SERVER_HOME>/bin/libjitipi.so
      <APP_SERVER_HOME>/bin/libijitipi.so

      WebLogic windows platforms:

      <APP_SERVER_HOME>/server/bin/ijitipi.dll
      <APP_SERVER_HOME>/server/bin/jitipi.dll

      WebLogic AIX platforms:

      <APP_SERVER_HOME>/server/lib/aix/libjitipi.dll

      WebLogic xLinux platforms:

      <APP_SERVER_HOME>/server/lib/linux/i686/libjitipi.dll
      <APP_SERVER_HOME>/server/lib/linux/i686/libarm.so
      <APP_SERVER_HOME>/server/lib/linux/i686/libarmjni.so

      WebLogic Solaris platforms:

      <APP_SERVER_HOME>/server/lib/solaris/libjitipi.dll
    7. Start the management agent process and application servers.
    8. Navigate to System Administration -> Work with Agents, and select the agents on which the J2EE component was running before you uninstalled the component.
    9. Select Deploy J2EE Monitoring Component from the drop-down list to redeploy the J2EE component on the specified agents.
  5. (For new management agent installations only, excluding Windows 2003 and z/OS): Perform the following steps to install a new management agent (not upgrade):
    1. Perform a management agent installation using the IBM Tivoli Monitoring for Transaction Performance, Version 5.2 installation images as described in the IBM Tivoli Monitoring for Transaction Performance Installation and Setup Guide.
    2. Update the Version 5.2 agent.jks key file by performing the following steps:
      1. Access the installation files for Fix pack 1.
      2. Replace the Version 5.2 agent.jks key file with the Fix pack agent.jks key file.

[ Top of Page | Previous Page | Next Page ]