Updating the installation by applying individual packages

The common packages and those included in the bootstrap package are:

• MVMMExtensible Agent
• MVMMMonitoring and Configuration extensions for IBM WebSphere MQ
• MVMMConfiguration Agent if supported on that platform
• MVMMExtensible Agent Preference Tool if supported on that platform
• JRE if supported on that platform

The steps below are for updating these common components regardless of which layout is being used. Note that the Open VMS platform does not support automatic distribution of individual packages.

To update the installation by applying individual packages

1. Refer to the Distributing Packages section and distribute one or more of the common packages. The maintenance updates applied to the server should indicate which packages have been updated. Packages are distributed to the Agent_Distribution sub-directory of the directory specified by the MQS_HOME environment variable.
2. Outages now begin for this MVMMExtensible Agent.
3. Stop any stand-alone extensions. Even though some of the extensions are not updated by the common packages, they might be using the JRE. See Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions.
   
   It is not necessary to stop the technologies with embedded extensions when updating the common packages.
4. Stop the MVMMConfiguration Agent if installed. See Basic command parameters to control the MVMM Configuration Agent.
5. Stop the MVMMExtensible Agent. See Basic command parameters for controlling the MVMM Extensible Agent.
6. If you have start up scripts, ensure none activate the MVMMExtensible Agent, MVMMConfiguration Agent or extensions or technologies with embedded extensions during this upgrade.
7. If you have sufficient disk space it is recommended to back up the installation directory. The bootstrap distribution does not overlay the following files:
   • eaa.xml
   • eaapi.ini
   • checkpoint.bin
   • rtsp.xml
   
   However, if you have modified any other files, those are replaced and the changes need to be re-applied. For example, logging changes made to the MVMMConfiguration Agent. A full back up allows you to refer to those files as needed. Otherwise, back up any files that have been changed.
8. Change to the agents directory (or the directory where you installed).
9. If the distribution directory contains a zip file, unzip it in the current directory. If the distribution directory contains individual files, change to the appropriate subdirectory and copy the files from the distribution directory to the installation directory.
10. Re-apply the edits to files. Note that files that are replaced are not guaranteed to have the same format as before. Consult BMC Support if you are unsure you should re-apply any changes.
11. Start the MVMMExtensible Agent. See Basic command parameters for controlling the MVMM Extensible Agent..
12. Start the MVMMConfiguration Agent if installed. See Basic command parameters to control the MVMM Configuration Agent.
13. Start any stand-alone extensions. See Running performance and availability monitoring extensions and Running application transaction tracing (transaction monitoring) extensions.
14. The outage has now ended for this agent.
15. If you are using startup scripts, you can now allow them to activate.
16. Retain the backup of the installation until the updated installation has been verified to be working.