test

Sun Cluster 3.1 9/04 Release Notes for Solaris OS

Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS

Instructions for upgrading Sun Cluster HA for WebSphere MQ are omitted from Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS.

Additional configuration parameters for Sun Cluster HA for WebSphere MQ are introduced in Sun Cluster 3.1 9/04, as explained in the subsections that follow. If you need to modify the default value of a parameter, or set a value for a parameter without a default, you must upgrade Sun Cluster HA for WebSphere MQ.

Parameters for Configuring the MQ User

The following parameters for configuring the MQ user are introduced in Sun Cluster 3.1 9/04. Default values are defined for theses parameters.

CLEANUP=YES

Specifies that unused shared memory segments that mqm creates are to be deleted.

USERID=mqm

Specifies that user ID mqm is to be used to issue mq commands.

Parameters for Configuring XAResourceManager Processing

XAResourceManager processing enables WebSphere MQ to manage global units of work with any combination of the following databases:

The following parameters for configuring XAResourceManager processing are introduced in Sun Cluster 3.1 9/04. Null values are defined for these parameters.

DB2INSTANCE=name

Specifies the DB2 instance name for XAResourceManager.

ORACLE_HOME=directory

Specifies the Oracle home directory for XAResourceManager.

ORACLE_SID=identifier

Specifies the Oracle SID for XaResourceManager.

Parameters for Enabling Sun Cluster to Manage the Startup of WebSphere MQ Queue Manager

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 are 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.

ProcedureHow to Upgrade Sun Cluster HA for WebSphere MQ

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

Only the USERID=mqm applies to the resources for all components, namely:

The remaining parameters that are introduced in Sun Cluster 3.1 9/04 apply only to the resource for the Queue Manager component.

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

Note –

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/SUNWscmqs/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:

    • mgr denotes the Queue Manager component.

    • chi denotes the Channel Initiator component.

    • csv denotes the Command Server component.

    • lsr denotes the Listener component.

    • trm denotes the Trigger Monitor component.

    Note –

    Only the mgr_config file contains all the parameters that are introduced in Sun Cluster 3.1 9/04. The remaining files contain only the USERID=mqm parameter.

  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