Upgrading the Agent and Extensions

This section includes:

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 MVMMExtensible 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 MVMMExtensible Agent and Extensions on z\os platform

Before you begin:

1. Backup the agent.
2. Stop the agent.
3. Stop qpea
4. Stop qpmon
5. Stop qpcfg
6. Copy all your existing agent libraries and datasets: 
   
   •  YOURHLQ.INSTALL.CNTL
   • YOURHLQ.EAAXML,
   • YOURHLQ.EAAXML
   • YOURHLQ.LOADLIB
   • YOURHLQ.RECV.JCL
   • YOURHLQ.RTSPCHCK
   • YOURHLQ.RTSPXML.
7. If 90% of objects are to be monitored, consider turning queue manager and object discovery on. Use the following command to turn on object discover:
   agentpref --host < Hostname of the agent machine, your mainframe> --port <agent port, usually 2612> --set "WebSphere MQ Monitor" DiscoverObjects on
8. Verify that EAAXML has enough space to hold the definitions for discovered objects. You may choose to double the primary and secondary sizes if the total number of objects will number in the thousands. 
   For more information regarding HEAP fine tuning see Tuning the z/OS operating system to optimize MainView Middleware Monitor applications.

Upgrading the MVMMExtensible Agent and the WebSphere MQ configuration and monitoring extensions on z/OS :

There are two way to perform the upgrade, to use same HLQ as the install and overwrite existing agent datasets or create a new agent dataset for the new install.

Overwriting the existing agent dataset:

1. Install the new agent files. To install the new agent files, see step 1 to step 7 in Installing the bootstrap package on z/OS. 

   Note

   In step 7, make sure to use the same existing dataset name instead of YOURHLQ, in the commands that transfer the files to MVS.

2. Edit the RECV.JCL to use the same existing dataset name instead of YOURHLQ. 
   Run the new RECEIVE job (RECV.JCL), which will take the INSTALL.XMIT file as an input to create a new INSTALL.CNTL PDS. This will overwrite the old INSTALL.CNTL for the existing agent dataset and populate it. Note: you must add storage details to the JCL.
3. Edit the member JALLOC in HLQ.INSTALL.CNTL to use same existing agent dataset name instead of YOURHLQ.
4. Delete or rename the old load library that is using the same HLQ.  Run JALLOC to create the new load library.  
5. Modify and save PLINK in HLQ.INSTALL.CNTL. This is the proc for JLINK .
6. Modify JLINK in HLQ.INSTALL.CNTL to use same existing agent dataset name instead of YOURHLQ. Run JLINK to populate the new load library.
7. Stop the agents, except QPBTM, with the STOP (P) command.
   Skip this step if QPBTM is not in use: Stop QPBTM using the "F QPBTM,REMOVE" command. This will remove the intercept from memory.
8. You can restore YOURHLQ.RTSPCHCK and  YOURHLQ.RTSPXML from the agent backup, by copying them using same YOURHLQ of the existing agent dataset or you can run job JRTSPXML to create new RTSPCHCK and RTSPXML dataset. Edit the JRTSPXML job in HLQ.INSTALL.CNTL to use the same existing dataset name instead of YOURHLQ and submit it.
9. Identify any updated members in the new INSTALL.CNTL PDS,. You can copy them from the backup of the agent dataset that was created in the beginning.
10. Restore EAAXML from the agent backup. Copy the previous EAAXML that you backed up to the existing agent dataset. Use the same YOURHLQ.
11. Check the CEEOPTS DD and edit the DD to reflect the time zone where the extension is running.
    For more information about Setting TZ environment variable see Controlling the MVMM Extensible Agent on z/OS platforms.
12. Customize the new JCL procedures, QPEA, QPCFG, QPMON, and QPBTM as each member instructs. You must install them into a system procedure library (e.g. SYS1.PROCLIB). Most environments require RACF, ACF2 or Top-Secret access to update system libraries such as SYS1.PROCLIB. To run the agent and extensions as batch jobs, customize and submit the JCL members, JQPEA, JQPCFG, JQPMON, and JQPBTM. See details in each member
13. Start the agent and all extension STCs.
14. After agent is running and all object are monitored correctly in MC, you can delete the backup of the agent .

Creating new agent dataset:

1. Perform a fresh install of the new agent. Follow the steps described in Installing the bootstrap package on z/OS.

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 these commands do not give you good results, the mqsi profile may not have been sourced properly.
• Distribute the correct pkg_unix_qpwmb.zip from the MVMMserver; 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.
   • mv qpwmb qpwmb_backup
   • mkdir qpwmb
   • cd qpwmb
   • mv ../pkg_unix_qpwmb.zip
   • unzip *.zip 
4. Review and restore any JVM parms from the old qpwmb.sh.