Redpaper - IBM Redbooks

More documents

Recommendations

Info

e compromised while the failing component recovers, but recovery should be automatic. This paper describes a resilient HA Message Broker architecture based on an Active-Active Message Broker configuration using a WebSphere MQ queue sharing group (QSG) and a DB2 data sharing group (DSG) across two Logical Partitions (LPAR). Testing revealed that this configuration provides for sustained Message Broker services through a variety of failover scenarios. For a complete overview of HA concepts, refer to the <strong>IBM</strong> Redbook Highly Available WebSphere Business Integration Solutions, SG24-6328. The individual component failures that we tested in the research for this paper include: ► A Message Broker execution group failure ► A Message Broker failure ► A queue manager failure ► A DB2 sub-system failure In our testing, we restarted each of these components in place on the LPAR on which they failed using Automatic Restart Management (ARM). We also tested a complete LPAR failure in which we restarted the queue manager and Message Broker from one LPAR on the active LPAR. There are countless other individual component failures that we could not test due to time constraints. We used ARM to restart all failing components. Appendix A, “Sample code” on page 49 provides the ARM policy that was in effect at the time of the failure. Some organizations may prefer NetView® automated recovery to ARM. You can achieve similar restart functionality using NetView. A coupling facility (CF) failure is categorized as a catastrophic failure. To achieve continuous availability on z/OS, a CF failover has to be accounted for, specifically, by duplexing the WebSphere MQ admin and list structures. The only single point of failure in our tested configuration was the CF. CF failover testing is outside the scope of this paper. For further information refer the following information: ► MVS Setting up a Sysplex: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2F132/ CCONTENTS?SHELF=IEA2BK34&DN=SA22-7625-06&DT=20030423145429 ► The WebSphere MQ System Administration Guide - Part 5, “Recovery and Restart” at: http://publibfp.boulder.ibm.com/epubs/html/csqsaw02/csqsaw02tfrm.htm 4 High Availability z/OS Solutions for WebSphere Business Integration Message Broker V5
1.2 Testing methodology Because the goal of this paper is to evaluate Message Broker service availability, we obtained measurements from both the Message Broker and the application that was using the Message Broker. The WebSphere Business Integration Broker - Sniff test and performance on z/OS (<strong>IBM</strong> Category 2 SupportPac IP13) provided an elegant solution. For details on downloading the SupportPac, see: http://www-306.ibm.com/software/integration/support/supportpacs/ Note: We recommended that you install the most current version of the SupportPac before using the techniques described in this paper. SupportPac IP13 consists of documentation, programs, and message flows designed to help you measure application throughput on Message Broker on z/OS. SupportPac IP13 provides statistics at the end of the job, including the total number of round trip messages that the SupportPac IP13 application processed. You can find the specific SupportPac IP13 parameters that we used for testing in Chapter 4, “Failover scenarios” on page 33. We ran the application on both LPARs during several of the tests to simulate a realistic production environment. Figure 1-2 on page 6 illustrates our testing environment topology. Chapter 1. Introduction and technical overview 5
Page 1: High Availability z/OS Solutions fo
Page 4 and 5: Note: Before using this information
Page 6 and 7: 3.7 Automatic Restart Management co
Page 8 and 9: Trademarks The following terms are
Page 10 and 11: From left: Dean, Steve, and Jon Dea
Page 12 and 13: Become a published author Join us f
Page 14 and 15: 1.1 Project overview This paper exp
Page 18 and 19: Figure 1-2 Test environment topolog
Page 20 and 21: Message Broker is a WebSphere MQ an
Page 22 and 23: 2.1 Considerations when designing f
Page 24 and 25: Table 2-1 Advantages and disadvanta
Page 26 and 27: Advantages Disadvantages Uses the a
Page 28 and 29: In this instance, you should consid
Page 30 and 31: of messages making up a transaction
Page 32 and 33: 20 High Availability z/OS Solutions
Page 34 and 35: 3.1 High Availability configuration
Page 36 and 37: 3.3 The z/OS LPARs There are three
Page 38 and 39: ► Review actual structure sizes r
Page 40 and 41: pool is not available, errors occur
Page 42 and 43: 3.7 Automatic Restart Management co
Page 46 and 47: 4.1 Test environment setup As previ
Page 48 and 49: ► In a production environment, yo
Page 50 and 51: The batch jobs provided work for th
Page 52 and 53: IP13 Statistics MVSM0 MVSM2 Total B
Page 58 and 59: z/OS DB2 (DSG) QMGR (QSG) Message B
Page 62 and 63: ARM policy Example A-1 displays the
Page 66 and 67:
Using the Web material The addition
Page 68 and 69:
56 High Availability z/OS Solutions
Page 70 and 71:
How to get IBM Redbooks You can sea
Page 72:
U UNIX System Services (USS) enviro
show all

Redpaper - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?