Redpaper - IBM Redbooks
Redpaper - IBM Redbooks
Redpaper - IBM Redbooks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
1.2.1 HTTP Listener<br />
then consumed by the SupportPac IP13 batch application program in a<br />
request-reply model.<br />
This testing methodology was sufficient to evaluate component failover.<br />
However, the statistics supplied in Chapter 4, “Failover scenarios” on page 33 are<br />
insufficient to evaluate Message Broker performance or capacity for the following<br />
reasons:<br />
► The z/OS environment was not tuned. The main purpose of SupportPac IP13<br />
is to provide a way to begin to tune the Message Broker environment, but we<br />
did not use it for this purpose in this exercise.<br />
► The LPARs did not have identical hardware resources. For instance, LPAR0<br />
was configured with two logical processors, while LPAR2 was configured with<br />
one logical processor.<br />
► The loads that we placed on the configuration were designed to provide a<br />
continuous stream of messages for the duration of the individual tests, but the<br />
steady-state load did not stress available resources. A single instance of the<br />
SupportPac IP13 message flow was used for each broker.<br />
Although HTTP Listener support in Message Broker is expected to makes its<br />
debut on z/OS shortly (FixPack 4), the current version does not support it.<br />
Therefore, configuration and testing using HTTP Listener was beyond the scope<br />
of this paper.<br />
It is essential for the system administrator to consider dynamic VIPAs for a high<br />
availability environment. WebSphere MQ and WebSphere Business Integration<br />
Message Broker rely on TCP/IP stack for communicating with other systems.<br />
For further information, on this subject, there is an <strong>IBM</strong> white paper entitled<br />
Leveraging z/OS TCP/IP Dynamic VIPAs and Sysplex Distributor for higher<br />
availability, GM13-0026, at:<br />
http://www-1.ibm.com/servers/eserver/zseries/library/techpapers/<br />
gm130165.html<br />
1.3 Environment overview<br />
For our testing environment, we kept the software configuration as simple as<br />
possible to achieve a HA environment. The goal was to build a resilient Message<br />
Broker server capable of providing a very high degree of availability. Because<br />
Chapter 1. Introduction and technical overview 7