How to send a message on to a queue with JMS. Sending a SOAP message onto JMS using the "SOAP over Java Message Service" proposal, or as a Text Message

Did you know that you can use Vordel SOAPbox to send a SOAP message onto a JMS message queue? You can choose to send it as a normal TextMessage, or an ObjectMessage. But you can also choose to use the "SOAP over JMS Message Service" proposal to place the message.

How to send a message on to a queue with JMS. Sending a SOAP message onto JMS using the "SOAP over Java Message Service" proposal, or as a Text Message

Did you know that you can use Vordel SOAPbox to send a SOAP message onto a JMS message queue? You can choose to send it as a normal TextMessage, or an ObjectMessage. But you can also choose to use the "SOAP over JMS Message Service" proposal to place the message.

One of my favorite Web APIs to use in demos is SalesForce.com . SalesForce has a ton of information about their API on their developer site. The Vordel API Sever can be used to connect up to SalesForce, including sending up the API Key and caching the Session Identifier which is returned back by SalesForce.

One of the neat things is that all traffic from the app to the SalesForce API is now monitored by the Vordel API Server. There are many advantages to this, which I will delve deeper into in later posts. But, one key advantage is that "rogue cloud service usage" is stamped out, since it appears on the Real-Time Monitoring of the Gateway:

The popular advantages of REST over SOAP are well known: It's easier to write a REST client, the messages are smaller, you can cache REST traffic using standard Web infrastructure. But what if you have SOAP Web Services and your clients are crying out for REST Web Services instead?

Here is how you create REST Web Services in front of SOAP services using Policy Studio and the Vordel XML Gateway...(http://www.vordel.com/products/API-Server.html)

To do this, create a policy which reads parameters from the REST URL and then inserts those parameters into a SOAP message which it creates on-the-fly.

Pro tip: Running Vordel API Server analytics as a Windows service

If you've downloaded the Vordel API Server v7.1 from the Vordel website and want to configure it to run analytics as a Windows service, it's quite simple to do this. The command is:

JSON is a very popular choice for transmitting data on the wire, especially since it is widely used for Apple iPhone app development. The usage of JSON allows a developer to skip the step in the browser where incoming XML must be parsed and read into an object. Instead, a serialized JavaScript object is sent, often including the data it needs already. So, no need for XML. But, in order to create this JSON structure in the first place, it is a good idea to offload this task onto an appliance such as an XML Gateway. The XML Gateway then serves up the JSON (to an iPhone for example), dynamically converting it from the source XML.

Here's a guide to setting up throttling in the Vordel Gateway:

If you've already registered a WSDL, skip forward to step 4.

Step 1: Open Policy Studio. Connect to the Gateway you wish to configure your policy on.

One of the neat features of the Axway/Vordel API Server is the fact that you can extend it using Java. There are a number of ways of doing this, but a really neat way is to run your Java class through a Scripting Filter. Here is a guide to calling your own, or third-pary, Java classes from the Axway/Vordel API Server.

My use case is that I want to use OpenID for single-sign-on using a Google login. I found a nice implementation of OpenID called JOpenID and downloaded it as a jar file.