Clustered Trade3 application and the Embedded JMS server
The main purpose of this example topology is to demonstrate how to use multiple Embedded JMS servers in a cell to spread the workload imposed on them by the appservers.
To make this example realistic some basic non-functional requirements have been set.
These requirements need to be specified as it is important to recognize that this example topology is not the best topology to use when using embedded JMS, nor is it the best one for Trade3. It is one of a many that could provide what is needed. Each topology benefits certain criteria and needs to be chosen based on those as well as function.
The requirements are:
- Performance is more important than availability. The application does not have to be available for use continuously. Outages occurring will be tolerated. However, when the system is available it must perform to a high standard.
- Hardware restriction. The cost of the hardware for this application needs to be kept to a minimum.
- No licenses of WebSphere MQ will be purchased. This decision has been driven by the fact that Trade3 only uses messaging for asynchronous communication within the WAS cluster. Also there is a reduced need for high availability and management of the messaging system.
There would normally be many other influences in choosing the topology, like workload patterns, but this is just to give some real world justification for this example.
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.