Redpaper - IBM Redbooks

More documents

Recommendations

Info

z/OS DB2 (DSG) QMGR (QSG) Message Broker Execution Groups Message Flows Figure 4-6 LPAR failover Because the OEMPUTX batch job running on MVSM2 ended when the system went down, there are no statistics for this test. However, to test the operation of the moved broker, the job was resubmitted on MVSM0, and it was observed that both brokers functioned normally on the one surviving z/OS image. Once MVSM2 was brought back into the sysplex with its DB2 subsystem active, the MVSM2 queue manager and broker were shut down on MVSM0 and restarted on MVSM2. Once again, the OEMPUTX batch job was submitted and normal operation was verified. 46 High Availability z/OS Solutions for WebSphere Business Integration Message Broker V5 IP13 Coupling Facility Configuration Manager z/OS IP13 DB2 (DSG) QMGR (QSG) Message Broker Execution Groups Message Flows
4.8 Summary Conclusions Though collection of statistics was not appropriate for this scenario, the scenario demonstrated that: ► With the ARM policy provided in Appendix A, “Sample code” on page 49, when the host z/OS system failed, the Message Broker and its pre-requisite subsystems were automatically restarted on the chosen surviving z/OS system in the sysplex. ► Successful operation of the moved Message Broker was verified. ► On moving the Message Broker back to its original z/OS system its successful operation was again verified. We performed various failover tests to demonstrate high availability solutions for WebSphere Business Integration Message Broker on z/OS. Our goal was to observe that none of the messages were lost, despite the loss of statistics in some of the failover scenarios. Chapter 4. Failover scenarios 47
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 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 62 and 63: ARM policy Example A-1 displays the
Page 66 and 67: Using the Web material The addition
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

Create successful ePaper yourself

Delete template?

Save as template?