Upgrading Sun Cluster HA for WebSphere MQ Integrator

Additional configuration parameters for Sun Cluster HA for WebSphere MQ Integrator were introduced in Sun Cluster 3.1 9/04. If you need to set a value for a parameter, you must upgrade Sun Cluster HA for WebSphere MQ Integrator.

You might deploy a WebSphere MQ queue manager's qmgr files and log files on a global file system. In this situation, rename the strmqm program and the endmqm program to prevent the queue manager from being manually started on another node. If you rename these programs, the Sun Cluster framework manage the startup of WebSphere MQ queue manager. For more information, see Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS.

The following parameters for enabling Sun Cluster to manage the startup of WebSphere MQ queue manager were introduced in Sun Cluster 3.1 9/04. Null values are defined for these parameters.

START_CMD=start-program

Specifies the full path name and filename of the renamed strmqm program.

STOP_CMD=stop-program

Specifies the full path name and filename of the renamed endmqm program.

How to Upgrade Sun Cluster HA for WebSphere MQ Integrator

If you need to set a value for a parameter , you must remove and reregister the Sun Cluster HA for WebSphere MQ Integrator resource for which you are changing the parameter.

The parameters that are introduced in Sun Cluster 3.1 9/04 apply to the resources for all components, namely:

• Broker component

• User Name Server component

Perform this task for each WebSphere MQ Integrator resource that you are modifying.

Perform this task only if you are setting or modifying parameters that are introduced in Sun Cluster 3.1 9/04.

Steps

1. Save the resource definitions.

   # scrgadm -pvv -j resource > file1

2. Disable the resource.

   # scswitch -n -j resource

3. Remove the resource.

   # scrgadm -r -j resource

4. Configure and register the resource.

   1. Go to the directory that contains the configuration file and the registration file for the resource.

      # cd /opt/SUNWscmqi/prefixutil

   2. Edit the configuration file for the resource.

      vi prefix_config

   3. Run the registration file for the resource.

      # ./prefix_register

   prefix denotes the component to which the file applies, as follows:

   • sib denotes the Broker component.

   • siu denotes the User Name Server component.

5. Save the resource definitions.

   # scrgadm -pvv -j resource > file2

6. Compare the updated definitions to the definitions that you saved before you updated the resource.

   Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.

   # diff file1 file2

7. Amend any resource properties that were reset.

   # scrgadm -c -j resource -x|y resource

8. Bring online the resource.

   # scswitch -e -j resource