Redpaper - IBM Redbooks

More documents

Recommendations

Info

Become a published author Join us for a two- to six-week residency program! Help write an IBM redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will team with IBM technical professionals, Business Partners, and customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: Comments welcome ibm.com/redbooks/residencies.html Your comments are important to us! We want our papers to be as helpful as possible. Send us your comments about this Redpaper or other Redbooks in one of the following ways: ► Use the online Contact us review redbook form found at: ibm.com/redbooks ► Send your comments in an e-mail to: redbook@us.ibm.com ► Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 662 P.O. Box 12195 Research Triangle Park, NC 27709-2195 x High Availability z/OS Solutions for WebSphere Business Integration Message Broker V5
Chapter 1. Introduction and technical overview 1 This paper is divided into four chapters: ► This chapter, Chapter 1, “Introduction and technical overview” on page 1, describes the scope of this book and provides an overview of a high availability environment for WebSphere Business Integration Message Broker (Message Broker) on z/OS. ► Chapter 2, “Design decisions that affect high availability” on page 9, provides considerations, hints, and tips for the Message Broker in a high availability environment and developing message flows and publish and subscribe applications in a high availability environment. ► Chapter 3, “Topology and system setup” on page 21, describes how to achieve a high availability environment with Message Broker and contains specific configuration information for the software components used during failover testing. ► Chapter 4, “Failover scenarios” on page 33, describes the procedures to create a testing environment and details the results of the failover testing. © Copyright IBM Corp. 2004. All rights reserved. 1
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 14 and 15: 1.1 Project overview This paper exp
Page 16 and 17: e compromised while the failing com
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 64 and 65:
52 High Availability z/OS Solutions
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?