Integrating MagooClient with JMS SOA (3)
Plugging MagooClient into JMS
One of the key advantages of using MagooClient in this scenario is that it’s native JMS transport layer and built-in message store allow it to be dropped directly into a JMS-oriented asynchronous architecture. Unlike a browser-based client, there is no requirement to create a bridge between HTTP and JMS and no polling is required. Therefore the displaying of newly-received messages is instantaneous with no polling-related latency.
The MagooClient JMS capability features:
- Hot configuration of JMS Providers.
- Out of the box transport templates for key JMS implementations from vendors and organizations such as Sonic, IBM, Sun, Apache, Tibco, WebLogic and JBoss.
MagooClient ships with a set of JMS Provider templates with pre-filled information such as the required JMS JAR list and location and default JNDI settings. The list of templates is being continually expanded – for V3.5+, the following templates are provided:
- Progress SonicMQ
- IBM WebSphere MQ
- Sun ONE Message Queue
- BEA Weblogic JMS
- Tibco EMS
- Apache ActiveMQ
A generic JMS template is also provided to cater for JMS Products and/or versions which do not have a pre-filled template. For queries relating to future JMS support, please contact info@magoosoft.com
Configuring a JMS Transport
Select the Configure->Communications… menu item in the main MagooClient menu system. Select Add and choose your appropriate JMS Provider. A configuration dialog similar to that below will be opened and the details of the QueueConnectionFactory and Queue to be used for the RectifierService should be entered.
Make sure your JMS Broker is running and then select Test Connection to ensure that all of the settings are correct and connectivity to the queue can be achieved. Now click on Save to save the JMS Transport settings and activate the transport.
That’s it!! – MagooClient is now ready to receive messages on the Rectify Queue. Any new messages received for the RectifierService endpoint will now appear in the MagooClient inbox for operator attention. Note that as the WSDL has been registered with MagooClient, the received message is automatically validated with the validation status displayed accordingly.
In the next sections we'll look at some of the more advanced aspects of MagooClient message-handling.