Upgrading the agent and extensions

This section includes:

During these procedures, the following outages occur:

  • Monitoring stops for hosts being upgraded.
  • No events fire for information from these hosts.
  • No history is collected.
  • No SLA data is collected.
  • Technology outages can also occur. For example, for WebSphere MQ, you need to take down the Queue Manager to change the exit share objects.

Before you begin

  • During these procedures, the following users should be available:
    • Users with authority and permissions to distribute and configure agents.
    • Users with authority and permissions to stop technologies with embedded extensions (WMQ BTM Extension, WMB BTM Extension, Sun Java System Web Server BTM Extension, Apache BTM Extension, IIS BTM Extension, Java EE BTM Extension, any of the BTM API Extensions).
    • Users with authority and permissions to deploy transaction pathways.
  • If you are updating secured agents on a UNIX system, you must have root access so that you can overwrite the secured files. Delete or rename the secured agent and then distribute the new version of the agent. Re-secure the agent after you have distributed the new version. See Defining user access and security settings for more information.
  • RACF configuration changes might be required so that QPCFG can use the authentication and authorization API. For more details, see Running performance and availability monitoring extensions.
  • Refer to the Planning section and determine the installation layout required for each of your agents.

To upgrade the TMTM Extensible Agent and BTM extensions

If you wish this agent to retain the Flat Directory Layout, refer to the section on Updating or upgrading the Flat Directory Layout installation.

If you wish this agent to be upgraded to the Default Layout, refer to the section on Upgrading from the Flat Directory Layout to Default Layout.

To upgrade the agent and the WebSphere MQ monitoring and configuration extensions

The quickest method to upgrade the agent and the WebSphere MQ monitoring and configuration extensions is a two-step process:

  1. From the <AGENT INSTALL> directory, run the command: rm -rf jre
    This command removes the existing JRE directory (this must be done before you proceed to Step 2).
  2. Run the command: unzip pkg-linux-x86-64-bootstrap.zip (change the platform package accordingly to suit your environment)
    This command actually does the upgrade and overwrites the existing installation (you will be prompted with a message similar to: "replace agent/scripts/Telnet/default_qpea_Stop.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: A").

To upgrade the WebSphere Message Broker monitoring extension

Before you begin

  • Use the source mqsiprofile command to execute the shell you will be working with for the update. 
  • Ensure you can run commands such as:
    • mqsiservice -v
    • mqsilist
      If mqsilist returns the status of your integration nodes, you can proceed.
  • Distribute the correct pkg_unix_qpwmb.zip from the TMTM server; you can use the package distribution feature or transfer the file manually from the AGENT_DIST folder that corresponds to your operating system.

For additional information, see Installing the WebSphere Message Broker monitoring extension and Running the WebSphere Message Broker monitoring extension.

Updating the extension

  1. From <AGENT INSTALL>/qpwmb, run the following commands:
    • ./bin/qpwmb.sh --stop
    • ./bin/qpwmb.sh --status
  2. Run the ps -ef | grep java command to see if any stray qpwmb JVMs are still running.
  3. Run the following commands from <AGENT INSTALL>.  These commands will back up the existing installation, then create and populate a new install.
    1. mv qpwmb qpwmb_backup
    2. mkdir qpwmb
    3. cd qpwmb
    4. unzip <file location>/*.zip 
  4. Review and restore any customized JVM parameters from the old qpwmb.sh.  

Upgrade Tips

If you customized the qpwmb.sh install, make sure you carry these customizations over to your new qpwmb.sh install. For example: the D path for the Java configuration. 

In addition, if you are upgrading from version 7.0 or 8.0, see Deprecated configuration property files.

Installing the OSGI bundle

Run install.sh from /var/mqm/bmc/qpwmb: ./bin/install.sh

If the bundle installs properly, the upgrade is complete.

To upgrade the DataPower monitoring extension

  1. From <AGENT INSTALL>/datapower, run the following commands:
    • ./bin/datapower.sh --stop
    • ./bin/datapower.sh --status
  2. Run the ps -ef | grep java command to see if any stray datapower JVMs are still running.
  3. Run the following commands from <AGENT INSTALL>.  These commands will back up the existing installation, then create and populate a new install.
    1. mv datapower datapower_backup
    2. mkdir datapower
    3. cd datapower
    4. unzip <file location>/*.zip 
  4. Review and restore any customized JVM parameters from the old datapower.sh.  

Note

When configured to run with SSL, ensure that the com.bmc files also get updated.

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

Comments