After completing the necessary setup tasks, use the following steps to define the WebSphere MQ resource hierarchy.
- From the LifeKeeper GUI menu, select Edit, then Server. From here, select Create Resource Hierarchy.
The Create Resource Wizard dialog box will appear with a drop-down list box displaying all recognized Recovery Kits installed within the cluster.
- Select IBM WebSphereMQ and click Next.
- You will be prompted to enter the following information. When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is helpful should you encounter an error requiring you to correct previously entered information. You may click Cancel at any time to cancel the entire creation process.
| Choose either Intelligent or Automatic. This dictates how the WebSphere MQ instance will be switched back to this server when the server comes back up after a failover. The switchback type can be changed later from the General tab of the Resource Properties dialog box.
Note: The switchback strategy should match that of the IP or File System resource to be used by the WebSphere MQ resource. If they do not match the WebSphere MQ resource, creation will attempt to reset them to match the setting selected for the WebSphere MQ resource.
|Select the Server on which you want to create the hierarchy.
|Queue Manager Name
|Select the WebSphere MQ queue manager you want to protect. The queue manager must be created prior to creating the resource hierarchy. Queue managers already under LifeKeeper protection are excluded from this list. The queue managers are taken from the global mqs.ini configuration file.
| Select “YES” to protect and manage the WebSphere MQ queue manager listener. Select “NO” if LifeKeeper should not manage the WebSphere MQ listener.
Note: You can change this setting later. See Editing Configuration Resource Properties for details.
|Server Connection Channel
| Select the server connection channel to use for connection tests. By default, the channel SYSTEM.DEF.SVRCONN will be used; however, beginning with MQ Version 7.1, changes in MQ’s Channel Authentication require that a channel other than the default be used and that the MQADMIN user be enabled for the specified channel.
Note: Make sure the Server Connection Channel has been created PRIOR to creating your resource. For more information, see Configuring WebSphere MQ for Use with LifeKeeper.
Note: This setting can be changed later. See Editing Configuration Resource Properties for details.
| Select the LifeKeeper virtual IP resource to include in the hierarchy. Select “None” if you do not want to include a LifeKeeper virtual IP in the WebSphere MQ hierarchy.
Note: The virtual IP must be ISP (active) on the primary node to appear in the selection list.
|IBM WebSphere MQ Resource Tag
|Either select the default root tag offered by LifeKeepe, or enter a unique name for the resource instance on this server. The default is the queue manager name. Letters, numbers and the following special characters may be used: – _ . /
- Click Create. The Create Resource Wizard will then create your WebSphere MQ resource hierarchy. LifeKeeper will validate the data entered. If LifeKeeper detects a problem, an error message will appear in the information box.
- An information box will appear indicating that you have successfully created a WebSphere MQ resource hierarchy and that hierarchy must be extended to another server in your cluster in order to achieve failover protection. Click Next.
- Click Continue. LifeKeeper will then launch the Pre-Extend Wizard. Refer to Step 2 under Extending a WebSphere MQ Hierarchy for details on how to extend your resource hierarchy to another server.