Veritas High Availability Solution for WebSphere Message Broker and IBM Integration Bus. AIX, HP-UX, Linux, Solaris

Transcription

1 Veritas High Availability Solution for WebSphere Message Broker and IBM Integration Bus AIX, HP-UX, Linux, Solaris

2 Veritas InfoScale Availability Agents Last updated: Legal Notice Copyright 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third party ( Third Party Programs ). Some of the Third-Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the third-party legal notices document accompanying this Veritas product or available at: The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Veritas Technologies LLC 500 E Middlefield Road Mountain View, CA

3 Technical Support Technical Support maintains support centers globally. All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policies. For information about our support offerings and how to contact Technical Support, visit our website: You can manage your Veritas account information at the following URL: If you have questions regarding an existing support agreement, please the support agreement administration team for your region as follows: Worldwide (except Japan) Japan Documentation Make sure that you have the current version of the documentation. Each document displays the date of the last update on page 2. The latest documentation is available on the Veritas website: Documentation feedback Your feedback is important to us. Suggest improvements or report errors or omissions to the documentation. Include the document title, document version, chapter title, and section title of the text on which you are reporting. Send feedback to: You can also see documentation information or ask a question on the Veritas community site: Veritas Services and Operations Readiness Tools (SORT) Veritas Services and Operations Readiness Tools (SORT) is a website that provides information and tools to automate and simplify certain time-consuming administrative tasks. Depending on the product, SORT helps you prepare for installations and upgrades, identify risks in your datacenters, and improve operational efficiency. To see what services and tools SORT provides for your product, see the data sheet:

4 Veritas High Availability Solution for WebSphere Message Broker and IBM Integration Bus This document includes the following topics: Introduction Supported software Prerequisites for configuring WebSphere Message Broker Prerequisites for installing Agent Builder Installing the ACC library Installing AgentBuilder in a VCS environment WebSphere Message Broker agent attributes Configuring the agent for WebSphere Message Broker or IBM Integration Bus with Agent Builder Removing the agent for WebSphere Message Broker or IBM Integration Bus Configuring the MonitorProcessPatterns attribute Sample WebSphereMessageBroker resource attributes Sample VCS configuration

5 Introduction 5 Introduction This document describes the procedure to configurewebsphere Message Broker or IBM Integration Bus for high availability in an InfoScale Availability or a Cluster Server (VCS) environment using the Agent Builder tool. Supported software For information on the software versions that the Veritas InfoScale Availability (or Cluster Server VCS) agent for WebSphere Message Broker or IBM Integration Bus supports, see the Services and Operations Readiness Tools (SORT) site: Prerequisites for configuring WebSphere Message Broker Ensure that you meet the following prerequisites before you configure the agent for WebSphere Message Broker. WebSphere Message Queue application must be installed and configured for high availability. For information on configuring WebSphere Message Queue, see the Cluster Server Agent for WebSphere MQ Installation and Configuration Guide. The database with which WebSphere Message Broker is configured should be running before the broker is started. VCS agents for Sybase, Oracle, DB2, or a custom database agent can be used to configure the respective database for high availability. Depending on the database that you have selected, review one of the following documents for information on configuring the database for high availability. Veritas Cluster Server Agent for Oracle Installation and Configuration Guide Veritas Server Agent for Sybase Installation and Configuration Guide Veritas Server Agent for DB2 Installation and Configuration Guide If you have selected any other database, refer to the appropriate documentation for configuring the database for high availability. Prerequisites for installing Agent Builder You must meet the following prerequisites before you install Agent Builder.

6 Installing the ACC library 6 Ensure that you have the latest Agent Pack software. Install and configure InfoScale Availability or Cluster ServerCluster Server (VCS). For details, see the Veritas InfoScale Installation Guide. or the Veritas Cluster Server Installation Guide for your platform. Installing the ACC library Install the ACC library on each system in the cluster that runs an agent that depends on the ACC library. To install the ACC library 1 Log in as a superuser. 2 Download ACC Library. You can download either the complete Agent Pack tar file or the individual ACCLib tar file from the Veritas Services and Operations Readiness Tools (SORT) site ( 3 If you downloaded the complete Agent Pack tar file, navigate to the directory containing the package for the platform running in your environment. AIX HP-UX Linux Solaris cd1/aix/vcs/application/acc_library/version_library/pkgs cd1/hpux/generic/vcs/application/acc_library/version_library/pkgs cd1/linux/generic/vcs/application/acc_library/version_library/rpms cd1/solaris/dist_arch/vcs/application/acc_library/version_library/pkgs

7 Installing AgentBuilder in a VCS environment 7 4 If you downloaded the individual ACCLib tar file, navigate to the pkgs directory (for AIX and Solaris), or rpms directory (for Linux). 5 Install the package. Enter Yes, if asked to confirm overwriting of files in the existing package. AIX HP-UX Linux Solaris # installp -ac -d VRTSacclib.bff VRTSacclib # swinstall -s pwd VRTSacclib # rpm -i \ VRTSacclib-VersionNumber-GA_GENERIC.noarch.rpm # pkgadd -d VRTSacclib.pkg Note: The LogDbg attribute should be used to enable debug logs for the ACCLib-based agents when the ACCLib version is or later and VCS version is 6.2 or later. Installing AgentBuilder in a VCS environment Install AgentBuilder on each node in the cluster. To install AgentBuilder in a VCS environment 1 Download AgentBuilder from the Services and Operations Readiness Tools (SORT) site: 2 Uncompress the file to a temporary location, say /tmp.

8 WebSphere Message Broker agent attributes 8 3 If you downloaded the complete Agent Pack tarball, navigate to the directory containing the package for the platform running in your environment. AIX cd1/aix/vcs/application/agentbuilder/ vcs_version/version_agent/pkgs HP-UX cd1/hpux/generic/vcs/application/agentbuilder/ vcs_version/version_agent/pkgs Linux cd1/linux/generic/vcs/application/agentbuilder/ vcs_version/version_agent/rpms Solaris cd1/solaris/dist_arch/vcs/application/agentbuilder/ vcs_version/version_agent/pkgs where, dist_arch is sol_sparc If you downloaded the individual AgentBuilder tarball, navigate to the pkgs directory (for AIX, HP-UX, and Solaris), or rpms directory (for Linux). 4 Log in as superuser. 5 Install the package. AIX # installp -ac -d VRTSappab.rte.bff VRTSappab.rte HP-UX # swinstall -s 'pwd' VRTSappab Linux # rpm -ihv \ VRTSappab-AgentVersion-GA_GENERIC.noarch.rpm Solaris # pkgadd -d. VRTSappab WebSphere Message Broker agent attributes Table 1-1 lists the agent attributes. In the following example configuration, WebSphere Message Broker is installed in /opt/ibm/mqsi/6.1 directory.

9 Configuring the agent for WebSphere Message Broker or IBM Integration Bus with Agent Builder 9 Table 1-1 Attribute User StartProgram StopProgram CleanProgram MonitorSequence WebSphere Message Broker agent attributes Description OS user running the WebSphere Message Broker component Start script provided by WebSphere Message Broker component Stop script provided by WebSphere Message Broker component Stop script provided by WebSphere Message Broker component MonitorProcessPatterns PidFilesPatterns ListenAddressPort Note: Default values need not be changed. Configuring the agent for WebSphere Message Broker or IBM Integration Bus with Agent Builder Perform the following steps on each node in the cluster.

10 Removing the agent for WebSphere Message Broker or IBM Integration Bus 10 To configure the agent for WebSphere Message Broker or IBM Integration Bus with Agent Builder 1 Identify the cluster nodes on which WebSphere Message Broker or IBM Integration Bus will run as a VCS resource. 2 Navigate to the installed location of the Agent Builder tool and run it. For example, on Solaris, run the following commands: VCS 5.1 and later VCS 5.0 # cd /opt/vrtsagents/ha/bin/agentbuilder #./agentbuilder WebSphereMessageBroker rsh system node1 system node2 # cd /opt/vrtsagents/ha/bin/agentbuilder #./agentbuilder WebSphereMessageBroker base vcs5 platform solaris rsh system node1 system node2 VCS 4.1 # cd /opt/vrtsvcs/bin/agentbuilder #./agentbuilder WebShereMessageBroker base vcs4 platform solaris rsh system node1 system node2 3 This command deploys the WebSphere Message Broker or IBM Integration Bus agent on cluster nodes node1 and node2 via rsh. Make sure that passwordless rsh or ssh communication is configured across the cluster nodes on which you want to deploy the agent. Removing the agent for WebSphere Message Broker or IBM Integration Bus Perform the following steps to remove the agent for WebSphere Message Broker or IBM Integration Bus created using Agent Builder. To remove the agent for WebSphere Message Broker or IBM Integration Bus 1 Log in as superuser. 2 Remove all the resources of the resource type to be deleted.

11 Configuring the MonitorProcessPatterns attribute 11 3 Delete the resource type that was created using Agent Builder. 4 Remove the agent directory from all nodes in which the agent is deployed. #hatype -delete <AgentName> VCS 4.1 VCS 5.0 / VCS 5.1 and later # /opt/vrtsvcs/bin/agent directory # /opt/vrtsagents/ha/bin/agent directory Configuring the MonitorProcessPatterns attribute You can configure the MonitorProcessPatterns attribute of the WebSphere Message Broker or IBM Integration Bus resource by identifying WebSphere Message Broker or IBM Integration Bus service processes. # ps aef grep bipservice grep broker_name For example: # ps aef grep bipservice grep broker5 mqm Oct17? 00:00:00 bipservice broker5 The processes matching this pattern can be used to configure the MonitorProcessPatterns attribute of the WebSphere Message Broker or IBM Integration Bus VCS resource. Sample WebSphereMessageBroker resource attributes Table 1-2 lists the WebSphereMessageBroker resource attributes. Table 1-2 Attribute User StartProgram StopProgram CleanProgram WebSphereMessageBroker resource attributes Description mqm "/opt/ibm/mqsi/6.1/bin/mqsistart broker5" "/opt/ibm/mqsi/6.1/bin/mqsistop broker5" "/opt/ibm/mqsi/6.1/bin/mqsistop broker5"

12 Sample VCS configuration 12 Table 1-2 Attribute ResLogLevel MonitorSequence WebSphereMessageBroker resource attributes (continued) Description INFO MonitorProcessPatterns PidFilesPatterns ListenAddressPort MonitorProgram MonitorProcessPatterns "bipservice broker5" Sample VCS configuration The following figure shows a sample VCS resource group dependency for WebSphere Message Broker and Sybase database. Figure 1-1 Sample VCS resource group dependency The following figure shows a VCS group having resources for WebSphere Message Broker and WebSphere Message Queue.

13 Sample VCS configuration 13 Figure 1-2 Sample resource configuration The /var/mqsi directory can be made highly available by either using Cluster File System (CFS) or with a shared filesystem available on the node on which the broker is running. In the above example, the /var/mqsi directory is configured via broker_mnt and broker_dg resources. The directory /var/mqm is configured via mq_mnt and mq_dg resources. For information on configuring WebSphere Message Queue, refer to Cluster Server Agent for WebSphere MQ Installation and Configuration Guide. The following figure shows a sample configuration of the WebSphere Message Broker resource.

14 Sample VCS configuration 14 Figure 1-3 WebSphere Message Broker resource sample configuration The following figure shows a sample configuration of the WebSphere Message Queue resource.

15 Sample VCS configuration 15 Figure 1-4 WebSphere Message Queue resource sample configuration