Interoperabilty of SOA Expressway with JMS Message Queues

Its been a busy summer for me, especially around creating proof-of-concepts utilizing SOA Expressway. Interaction with JMS Message Queues (MQ) within SOA Expressway applications has been a frequent theme. As you have seen in prior posts, SOA Expressway’s protocol mediation is remarkable – interoperability with JMS Message Queues is no exception.

For example, a couple of weeks ago I held a conference call with a potential customer that wanted a demonstration of creating and deploying a SOA Expressway applications that, among other things, would interoperate with a JMS Message Queue. Utilizing an existing Message Queue in my lab, the entire time to build, deploy, and successfully test an application took just under 15 minutes!

 

Overview of the Process

Assuming you have a running JMS Message Queue and the client drivers needed to interact with it, here are the steps.

    1.  

      Using the web interface, the JMS client drivers are uploaded into a Java Provider which can be utilized by any application running in SOA Expressway.

       

 

    1. In Services Designer, create a new workflow that utilizes an invoke step to a JMS Message Queue.

      workflow.jpg

       

 

    1.  

      Supply the input to and JMS parameters the invocation step.

       

       

 

    1.  

      Export the application bundle an upload to SOA Expressway.

    1.  

      Supply the JMS credentials required for JNDI Lookup of the MQ Service.

       

       

 

    1.  

      Save or Activate the configuration the application was loaded to.

Additional Thoughts

SOA Expressway works with any standard JMS MQ provider. To date, I have personally configured SOA Expressway to work with Apache Active MQ, Websphere MQ, Sun Java System Message Queue, and Progress’ Sonic MQ, all without a hitch. Customers have been really impressed on how easy it is to do, as well how powerful their applications become when integrated with other built-in services like JDBC, FTP, File, HTTPS, data transformation, etc. [The workflow illustration in step 2 above actually illustrates this.] My future posts will delve into these more, however, you can check out additional use cases right now! These use cases not only showcase SOA Expressway as an integration appliance, but as a Service Gateway, for SOA Edge Security, for Runtime Governance, a BPMS id Broker, Cross Domain Sharing, as a Cloud Gateway and much more! For additional information please see:

 

Comments are closed.