Patch-ID# 116728-06 NOTE: *********************************************************************** READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE. *********************************************************************** Keywords: sunwscmqi Synopsis: Sun Cluster 3.0/3.1 HA-WMQI patch Date: Jan/08/2007 Install Requirements: See Special Install Instructions Solaris Release: 8 9 10 SunOS Release: 5.8 5.9 5.10 Unbundled Product: Sun Cluster Unbundled Release: 3.1/3.0 Xref: Topic: Sun Cluster 3.0/3.1 HA-WMQI patch Relevant Architectures: sparc BugId's fixed with this patch: 4976880 4976885 4979430 4985292 4985294 4992068 4992086 6219059 6492975 6493946 Changes incorporated in this version: 6493946 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /opt/SUNWscmqi/bin/control_wmqi /opt/SUNWscmqi/bin/functions /opt/SUNWscmqi/etc/SUNW.mqi /opt/SUNWscmqi/sib/bin/functions /opt/SUNWscmqi/sib/bin/sc3get /opt/SUNWscmqi/sib/bin/sc3inq /opt/SUNWscmqi/sib/bin/sc3put /opt/SUNWscmqi/sib/bin/start-broker /opt/SUNWscmqi/sib/bin/stop-broker /opt/SUNWscmqi/sib/bin/test-broker /opt/SUNWscmqi/sib/etc/config /opt/SUNWscmqi/sib/util/sib_config /opt/SUNWscmqi/sib/util/sib_register /opt/SUNWscmqi/siu/bin/functions /opt/SUNWscmqi/siu/bin/start-uns /opt/SUNWscmqi/siu/bin/stop-uns /opt/SUNWscmqi/siu/bin/test-uns /opt/SUNWscmqi/siu/etc/config /opt/SUNWscmqi/siu/util/siu_config /opt/SUNWscmqi/siu/util/siu_register Problem Description: 6493946 WebSphere Message Broker doesn't restart the service if bipservice is lost (from 116728-05) 6492975 SC 3.1 WebSphere MQI agent support for Solaris 10 and WebSphere Message Broker v6 (from 116728-04) 6219059 Dummy RTR file requires #% SERVICE_NAME entry for package upgrade (from 116728-03) 4992086 SC3.1 WebSphere MQI agent - can't start broker 4992068 SC3.1 WebSphere MQI agent - start timeout / start failed (from 116728-02) 4985292 SC3.1 WebSphere MQI agent - probe should make message flow test optional 4985294 SC3.1 WebSphere MQI agent - requires dependency check support for multiple db2 instances 4976880 SC3.1 WebSphere MQ Integrator agent - Support for S9RM when issuing su 4976885 SC3.1 WebSphere MQ Integrator agent - Tolerate manual start of application 4979430 Agent requires a dummy RTR file (from 116728-01) Revision skipped. Patch Installation Instructions: -------------------------------- There are three (3) possible procedures for installing patches on Sun Cluster 3.0 and 3.1. The proper method to use and any additional instructions, for this patch are specified below in the "Special Install Instructions" section. Refer to the chapter entitled "Patching Sun Cluster Software and Firmware" in the Sun Cluster 3.0/3.1 System Administration Guide for a description of the different install processes and instructions on how to install Sun Cluster 3.x patches. For Solaris 8-10 releases, refer to the man pages for instructions on using 'patchadd' and 'patchrm' scripts provided with Solaris. Special Install Instructions: ----------------------------- NOTE 1: If this patch is being applied to a Solaris 10 system, the patch must be applied to the global zone only by using the -G option for patchadd, e.g. # patchadd -G 116728-06 To remove the patch from a Solaris 10 system, you must also use the -G option for patchrm, e.g. # patchrm -G 116728-06 NOTE 2: When applying this patch, the files listed within the earlier section will get overwritten. If you are applying this patch to an existing deployment of WebSphere Message Broker within Sun Cluster, you will have previously amended the following file /opt/SUNWscmqi/sib/util/sib_config /opt/SUNWscmqi/siu/util/siu_config If you want to keep the configuration information within these files then save these files somewhere else before applying this patch. If you are reading this after applying the patch, then remove this patch and then save your /opt/SUNWscmqi//util/_config file as required. After doing this, you can then re-apply this patch. NOTE 3: Notes for BugID: 6492975 This patch provides support for WebSphere Message Broker v6, Solaris 10 and support for Resource_dependencies_restart which requires at least Sun Cluster 3.1 09/04 (Update 3). 1. If you are deploying WebSphere Message Broker v6, before applying this patch you must perform the following: 1.1 Create /opt/mqsi You must create /opt/mqsi on each cluster node. This is required even for WebSphere Message Broker v6, and is simply required by the agent for backward compatibility of earlier broker releases. 1.2 Create a symbolic link for /var/mqsi/common/locks You must create a symbolic link from /var/mqsi/common/locks to a local file system on each cluster node. 2. After applying this patch you will need to modify an existing broker resource to use the Resource_dependencies_restart resource property. To do this follow the steps below. 2.1 List the current strong dependencies of the broker resource. scrgadm -pvv -j | grep dependencies The Queue Manager resource and Database resource should be listed and are referenced below as and . 2.2 Set the Resource_dependencies_restart property as required. For WebSphere Business Integration Message Broker v5 ---------------------------------------------------- scrgadm -c -j \ -y Resource_dependencies= scrgadm -c -j \ -y Resource_dependencies_restart=, For WebSphere Message Broker v6 ------------------------------- scrgadm -c -j \ -y Resource_dependencies= scrgadm -c -j \ -y Resource_dependencies_restart= Note that WebSphere Message Broker v6 no longer has a restart dependency on the Broker Database, just a start dependency. NOTE 4: Notes for BugID: 4992086 The following parameters have been added as null values. If you need to change the values then you must remove and re-register the resource. New parameters with null values are: START_CMD= STOP_CMD= After the patch is installed, these parameters can be found in /opt/SUNWscmqi//util/_config where _config is a three-character abbreviation for the various WebSphere MQI components. The parameters are described below: START_CMD= / of renamed strmqm program STOP_CMD= / of renamed endmqm program If a WebSphere MQ queue manager's qmgr/log files are deployed on a global file system, renaming the strmqm/endmqm programs prevents the queue manager from being manually started on another node. Instead, the cluster framework will manage the startup. However, please refer to the "Sun Cluster for WebSphere MQ for Solaris OS" documentation on how to do this. The Broker startup will first try to start the WebSphere MQ manager and as such if strmqm/endmqm have been renamed, the SC3.1 Agent needs to know. Note 1: No changes required --------------------------- If you have no need to change the values to the parameters above, then simply apply this patch and follow "How to Apply a NON-Rebooting Sun Cluster Patch" in the Sun Cluster 3.0/3.1 System Administration Guide. Note 2: Changes required ------------------------ If you need to change the values to the parameters above, then you must remove and re-register the resource as follows. 1. Save the WebSphere MQI resource definitions. scrgadm -pvv -g > 2. Offline the WebSphere MQI resources using scswitch -n -j 3. Remove the WebSphere MQI resources using scrgadm -r -j 4. Add the patch (On all nodes within the cluster) 5. Edit /opt/SUNWscmqs/sib/util/sib_config and set the parameters as required. 6. Run /opt/SUNWscmqs/sib/util/sib_register to register the WebSphere MQ resource. 7. Repeat for other WebSphere MQI components Edit /opt/SUNWscmqs/siu/siu_config Run /opt/SUNWscmqs/siu/siu_register 8. Rerun 1. above to a different file. scrgadm -pvv -g > 9. Check that no resoucre propertry values have been reset, i.e. timeout values diff 10. Amend any resource property values that have been reset. scrgadm -c -j -x|y = 11. Bring Online the resources using scswitch -e -j NOTE 5: Notes for BugID: 4985292 The fix provided in this patch for BugID 4985292 allows you to instruct the probe to not perform a message flow test. If a message flow is not required you must specify, SC3_IN=NONE SC3_OUT=NONE If a message flow is required you must create and deploy a message flow and specify the MQInput and MQOutput queues of your choice: SC3_IN=