WebSphere MQ Resources

More documents

Recommendations

Info

RequirementsRequirementsYour LifeKeeper configuration must meet the following requirements prior to the installation ofthe WebSphere MQ Recovery Kit. Please see the LifeKeeper for Linux Planning and InstallationGuide for specific instructions regarding the configuration of your LifeKeeper hardware andsoftware.Hardware Requirements• Servers. The Recovery Kit requires two or more servers configured in accordance with therequirements described in the LifeKeeper for Linux Planning and Installation Guide. See theRelease Notes for supported Linux distributions.• Data Storage. The WebSphere MQ Recovery Kit can be used in conjunction both withshared storage and with replicated storage provided by the LifeKeeper Data Replicationproduct or DRBD. It can also be used with network-attached storage (NAS).Software Requirements• LifeKeeper software. You must install the same version of LifeKeeper software and anypatches on each server.• LifeKeeper IP Recovery Kit. You must have the same version of the LifeKeeper IPRecovery Kit on each server.• IP network interface. Each server requires at least one Ethernet TCP/IP-supported networkinterface. In order for IP switchover to work properly, user systems connected to the localnetwork should conform to standard TCP/IP specifications.Note: Even though each server requires only a single network interface, you should usemultiple interfaces for a number of reasons: heterogeneous media requirements, throughputrequirements, elimination of single points of failure, network segmentation, and so forth.• TCP/IP software. Each server also requires the TCP/IP software.• WebSphere MQ software. IBM WebSphere MQ must be ordered separately from IBM. Seethe LifeKeeper Release Notes for supported WebSphere MQ versions. The WebSphere MQSoftware must be installed on each server of the cluster prior to installing the WebSphereMQ Recovery Kit. The following WebSphere MQ packages must be installed to successfullyinstall the WebSphere MQ Recovery Kit:MQSeriesServer, MQSeriesSamples, MQSeriesClient, MQSeriesRuntime, MQSeriesSDK• Optional C compiler. The WebSphere MQ recovery kit contains a modified amqsget0.csample program from the WebSphere MQ samples package. This program has been modifiedto work with a timeout of 0 seconds instead of the default 15 seconds. It is used to performPUT/GET tests for the queue manager. This program is compiled during RPM installationand therefore a C compiler must be installed and must be located in the PATH of the “root”user.• Syslog.pm. If you want use syslog logging for WebSphere MQ resources, the Syslog.pmPERL module must be installed. This module is part of the standard PERL distribution and isnot required to be installed separately.6 WebSphere MQ Recovery Kit Administration Guide
RequirementsRecovery Kit InstallationPlease refer to the LifeKeeper for Linux Planning and Installation Guide for specific instructionson the installation and removal of the LifeKeeper for Linux software.Upgrading a LifeKeeper Cluster to IBM WebSphere MQ V71. Upgrade LifeKeeper on all nodes in the cluster including the WebSphere MQ Recovery Kitfollowing the instructions documented in the Upgrading LifeKeeper section of the LifeKeeperPlanning and Installation Guide.2. Unextend each IBM WebSphere MQ resource hierarchy from all its standby nodes in the cluster(nodes where the Queue Manager is not currently running). This step will leave each IBMWebSphere MQ resource running on only its primary node (there will be no LifeKeeperprotection from failures at this point until completing step 5).3. Upgrade IBM WebSphere MQ software on each node in the cluster using the following steps:A. If one or more LifeKeeper IBM WebSphere MQ resource hierarchies are in service onthe node, they must be taken out of service before the upgrade of the IBM WebSphereMQ software.B. Follow the IBM WebSphere MQ V7 upgrade instructions. This includes the followingsteps at a minimum (but is not limited to this):a. Ensure no queue managers or listeners are runningb. Uninstall all IBM WebSphere MQ v6 upgrades/updates/patchesc. Uninstall all IBM WebSphere MQ v6 base packages using the rpm "--nodeps"option to avoid the LifeKeeper MQ Recovery Kit dependency.d. Install IBM WebSphere MQ V7 (including all upgrades/updates/patches)4. Once the IBM WebSphere MQ V7 software has been installed on each node in the cluster, bringthe LifeKeeper IBM WebSphere MQ resource hierarchies in service (restore) and verifyoperation of each Queue Manager.5. Re-extend each IBM WebSphere MQ resource hierarchy to its standby nodes.LifeKeeper for Linux 7
Page 1 and 2: LifeKeeper ® for LinuxWebSphere MQ
Page 3 and 4: Table of ContentsIntroduction .....
Page 5 and 6: WebSphere MQ Recovery KitAdministra
Page 7: IntroductionAbbreviationsThe follow
Page 11 and 12: WebSphere MQ Recovery Kit OverviewF
Page 13 and 14: WebSphere MQ Configuration Consider
Page 19 and 20: Configuring WebSphere MQ for Use wi
Page 21 and 22: Configuring WebSphere MQ for Use wi
Page 23 and 24: Configuration Changes After Resourc
Page 25 and 26: WebSphere MQ Configuration Examples
Page 33 and 34: LifeKeeper Configuration TasksLifeK
Page 35 and 36: LifeKeeper Configuration TasksChann
Page 37 and 38: LifeKeeper Configuration TasksUnext
Page 39 and 40: LifeKeeper Configuration Tasks6. On
Page 41 and 42: LifeKeeper Configuration Tasksa. No
Page 43 and 44: LifeKeeper Configuration TasksThe p
Page 45 and 46: LifeKeeper Configuration TasksLifeK
Page 47 and 48: LifeKeeper Configuration TasksSever
Page 49 and 50: LifeKeeper Configuration TasksChang
Page 57 and 58: WebSphere MQ TroubleshootingWebSphe
Page 59 and 60:
WebSphere MQ Troubleshootingnot exi
Page 61 and 62:
WebSphere MQ Troubleshooting119039
Page 63 and 64:
119004 Some orphans of queue manage
Page 65 and 66:
WebSphere MQ Troubleshooting119209
Page 67 and 68:
Appendix B - Sample qm.ini Configur
show all

WebSphere MQ Resources

Create successful ePaper yourself

Delete template?

Save as template?