Upgrading from the Flat Directory Layout to Default Layout

This section outlines the steps required to update the installation that is using the Flat Directory Layout. This might be an installation from an earlier release or the current release and you have chosen to change to the Default Layout.

  1. Verify that the MQS_HOME system environment variable has been configured (see Configuring the MQS_HOME system environment variable for the Default layout).
  2. Outages now begin for this TMTM Extensible Agent.
  3. Stop stand-alone extensions; see Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions.
  4. Stop the technologies with embedded extensions.
  5. Stop the TMTM Configuration Agent if installed. See Basic command parameters to control the TMTM Configuration Agent.
  6. Stop the TMTM Extensible Agent. See Basic command parameters for controlling the TMTM Extensible Agent.
  7. If you have start up scripts, ensure none activate the TMTM Extensible Agent, TMTM Configuration Agent or extensions or technologies with embedded extensions during this upgrade.
  8. Backup the current installation.
  9. The directory structure of simple layout differs from the default layout. However, keep the existing installation as several files are copied from the existing installation to the new installation. This includes eaa.xml, checkpoint.bin, rtsp.xml, eaapi.ini and QPLog.ini if modified from the one provided.
  10. On Windows, uninstall the TMTM Extensible Agent and stand-alone extensions as Windows services.
    • qpea --remove
    • qpmon --remove
    • qpcfg --remove

    If the TMTM Configuration Agent is installed, execute Agent -–remove from the bin directory of its installation.

    See Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions if you have other stand-alone extensions to uninstall as Windows services.
  11. Distribute the TMTM Extensible Agent to (see TMTM Extensible Agent and extension files to distribute) and install in a different location from your existing install. For details concerning the default layout directory structure, see Creating environment directories on the agent system for the default layout and ensure that the appropriate directories exist in the new agent installation directory.
  12. Copy the eaa.xml file from the existing agent installation to the new agent installation directory.
  13. Copy the checkpoint.bin file from the existing agent installation to the new agent installation directory.
  14. Copy the rtsp.xml file if one exists from the existing agent installation to the new agent installation directory.
  15. You might have an eaapi.ini file if you have chosen to change the ports used by the TMTM Extensible Agent. If you have a single TMTM Extensible Agent installation and your existing TMTM Extensible Agent installation has an eaapi.ini file, copy it to the directory specified by the MQS_HOME environment variable. If you have multiple TMTM Extensible Agents on this system, copy the eaapi.ini file from the existing agent installation to the new TMTM Extensible Agent installation directory and the new qpmon installation directory.
  16. If you modified the standard QPLog.ini or qplog.ini file in the agent installation directory, copy it from the existing agent installation to your new agent installation directory.
  17. z/OS only:
    • Existing z/OS customers should migrate any customized parameter files (e.g. ENVINI, QMAPINI) to the new installation, usually located in HLQ.INSTALL.CNTL.
    • For existing z/OS customers, the BTM intercept is resident in memory and must be removed prior to upgrading. Do this using:

      F <BTM extension job name>,REM
      For example: F QPBTM,REM

      This can also be accomplished by doing an IPL on the mainframe.
  18. Start the TMTM Extensible Agent. See Basic command parameters for controlling the TMTM Extensible Agent.
  19. Start the TMTM Configuration Agent. See Basic command parameters to control the TMTM Configuration Agent.
  20. Refer to the Distributing Packages section and distribute the extension packages being upgraded. On all platforms the bootstrap contained the TMTM Monitoring and Configuration extensions for IBM WebSphere MQ packages and does not need to be re-installed.
  21. Upgrade the stand-alone extensions. See Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions.
  22. Upgrade the embedded BTM extensions. See Running application transaction tracing (transaction monitoring) extensions.
  23. Start stand-alone extensions. See Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions.
  24. Start technologies with embedded extensions. See Running application transaction tracing (transaction monitoring) extensions.
  25. The outage has now ended for this agent.
  26. If you are using startup scripts, adjust them to start the agent and extensions from their new installation directories.
  27. Retain the backup of the older installation until the new installation has been verified to be working.

Was this page helpful? Yes No Submitting... Thank you

Comments