Clustered Trade3 application WebSphere MQ and WebSphere Business Integration Event Broker
The main purpose of this example is to show how WAS, WebSphere MQ and WebSphere Business Integration Event Broker can be used to create a scalable infrastructure. This is to be done through the use of both WAS clustering and WebSphere MQ clustering. This section is aimed at WAS users who have had minimal exposure to WebSphere MQ and WebSphere Business Integration Event Broker.
As with the previous example, to make this realistic some requirements have been set:
A new functional requirement has been requested. When stock is bought or sold it needs to be processed by a back-end system first. A response message will then be generated by the back-end and the Trade3 database will be updated as normal. The reason this new requirement has been specified is because WebSphere MQ clustering only workload manages the sending of messages to remote clustered queues. If the back-end processing is not needed then WebSphere MQ clustering does not aid asynchronous communication between two parts of the same application.
This is explained further in Initial WebSphere MQ configuration.
Performance, reliability, and availability are of equal importance. The system must perform well, have minimal outages, and should an outage occur it needs to be able to recover. The application must link into an existing messaging system which is based on WebSphere MQ. Again, as with the previous example there would normally be other factors that influence the choice of topology, but this should be enough to justify the following topology.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.