Perform the following steps to configure the WebSphere MQ Queue Manager for high availability on a virtual machine.
To configure the WebSphere MQ Queue Manager for high availability
You can use the Search box to search for the WebSphere MQ application.
In the Environment File field, enter the path where the environment file is located. The environment file must be accessible on the node from which you invoke the wizard.
If you want to monitor the related queue manager listener, check the Monitor Queue Manager Listener check box and select one of the following options to proceed:
Select the Along with Queue Manager radio button to monitor the queue manager listeners along with WebSphere MQ Queue Manager instances. The MonitorListener attribute of the WebSphere MQ resource is enabled.
Select the Independent of Queue Manager radio button to monitor the queue manager listeners separately from queue manager instances. In the Listener Port field, enter the listener port number. A separate resource for the listener is created using the Application agent.
Cluster systems lists the systems included in the cluster configuration. Application failover targets lists the systems to which the application can fail over. Move the required systems to the Application failover targets list. Use the up and down arrow keys to define the priority order of the failover systems. The local system is selected by default for both, the cluster operations and as a failover target.
To add a system to the VCS cluster, click Add System. In the Add System dialog box, specify the following details of the system that you want to add to the VCS cluster and click OK.
On the Network Details panel, select the type of network protocol to configure the VCS cluster network links and then specify the adapters for network communication.
The wizard configures the VCS cluster communication links using these adapters. You must select a minimum of two adapters per system.
Select Use MAC address for cluster communication (LLT over Ethernet) or Use IP address for cluster communication (LLT over UDP), depending on the IP protocol that you want to use and then specify the required details to configure the VCS cluster communication network links. You must specify these details for each cluster system.
To configure LLT over Ethernet, select the adapter for each network communication link. You must select a different network adapter for each communication link.
To configure LLT over UDP, select the type of IP protocol and then specify the required details for each communication link.
Depending on the IP protocol, specify the following:
By default, one of the links is configured as a low-priority link on a public network interface. The second link is configured as a high-priority link. To change a high-priority link to a low-priority link, click Modify. In the Modify low-priority link dialog box, select the link and click OK.
In the Virtual Network Details panel, specify the IP protocol and virtual IP address for the application.
Depending on the IP protocol, specify the following:
If you want to add another virtual IP address for your application, click Add virtual IP address.
If you select multiple instances for the same virtual IP address, those instances are configured in the same service group.
On the Target ESX Details panel, specify all the ESX hosts to which the virtual machines can fail over. Each ESX host must be able to access the required shared datastores that contain visible disks. Enter the administrative user account details for each ESX host and click Next.
To specify the ESX hosts, click Add ESX Host and in the Add ESX Host dialog box, specify the following details:
The wizard validates the user account and the storage details on the specified ESX hosts.
If the network contains multiple clusters, the wizard verifies the cluster ID with the IDs assigned to all the accessible clusters in the network. The wizard does not validate the assigned ID with the clusters that are not accessible during the validation. Symantec recommends you to validate the uniqueness of the assigned ID in the existing network. If the assigned ID is not unique or if you want to modify the cluster name or cluster ID, click Edit. In the Edit Cluster Details dialog box, modify the details as necessary and click OK.
The wizard displays the status of each task. After all the tasks are complete, click Next.
If the configuration task fails, click View Logs to check the details of the failure. Rectify the cause of the failure and run the wizard again to configure application monitoring.
This completes the application monitoring configuration.
If the application status shows as not running, click Start to start the configured components on the system.