How to do content-based routing with conversion

Content-based routing with conversion for SOAP to REST in the Vordel API Server

The Vordel API Server has some really neat features which make it very easy to do content-based routing based on parameters in a SOAP message, and to use these parameters to construct a REST request. Here is an example of how this is setup. First, I register the WSDL service (a Parlay-X AmountCharging Service) in the Web Service Repository in the Vordel Policy Studio, as shown below:






How to create a WS-Security Username Token

How to create a WS-Security UsernameToken without a password

I've seen the "API Key" pattern also crop up in SOAP messages before. It's reasonably common practice to use a WS-Security block as the way to encapsulate the API Key, rather than, say, coming up with a new custom token.

First load in your SOAP message (or generate one from WSDL). Next, in the "security" menu, choose "Insert WS-Security Username":






How to convert SOAP to REST with Parameterized URLs

How to convert SOAP to REST with Parameterized URLs. SOAP-to-REST with Parameterized URLs and content-based routing using the Vordel API Server

The world is moving from SOAP to REST. Many applications continue to send old-style SOAP messages. Therefore, a very common usage of the Vordel API Server is to convert from legacy SOAP messages into REST API calls. This provides the best of both worlds: (1) Existing SOAP apps continue to work and don't have to be re-coded, and (2) going forward, REST APIs are used instead.






How to orchestrate a REST API with SOAP

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 create a RESTful Security Token Service

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

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 monitor Salesforce

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:






How to validate a SAML 2.0 assertion

It's simple to setup the validation of a signed SAML 2.0 assertion in a Vordel XML Gateway. In a circuit, chain together (1) an "XML Signature Verification" filter (which you can find in the "Integrity" group on the right-hand-side of Policy Studio), and (2) a "SAML Authentication" filter (which you can find in the "Authentication" group).

With XML Signature Verification filter, make sure that the SAML assertion is selected under "What must be signed". In the filter to validate the SAML assertion, make sure that it's a SAML 2.0 assertion.






How to convert from REST to SOAP

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.






How to run the API Server as a Windows Service

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: