Virtualization Authors: Elizabeth White, Michelle Drolet, Pat Romanski, Manuel Weiss, Gilad Parann-Nissany

Blog Feed Post

Video blog: Service composition / orchestration to SaaS with the Vordel API Server

Ross Mason from Mulesoft recently wrote an article entitled "With SaaS, it’s not just about your apps — it’s how you connect those apps, too". This is very true. APIs are what are used to connect apps together, and, as Ross explains, it frequently makes sense to orchestrate them, to achieve a greater business purpose.

For this reasons, a frequently-asked question about the Vordel API Server is "Can you orchestrate or compose two APIs using it?". Indeed this is possible, and quite easy to setup. Frequently, you wish to call one API and then use the output of that API as an input into another API, for example a SaaS API like SalesForce.com. 

In this video blog, I'm showing how to call an email verification API, to check the validity of an email address, prior to calling the SalesForce API. The Vordel API Server orchestrates the calls to both APIs as part of one "circuit" or policy. Below, I have put a diagram of the flow:

First let's walk through at the scenario. It's a familiar scenario where an organization has a web form which is filled out, and the information is inserted as a lead into Salesforce.com. We wish to check, firstly, if the email entered into the form is valid. Here's the scenario explained:

So, firstly lets see how a policy is configured on the Vordel API Server, using drag and drop, to connect directly to SalesForce, to send information from a Web form up to SalesForce, using the SalesForce API. Notice how this policy makes use of a "Policy Package", placed into a grouping in Policy Studio called "Cloud":

Once we have made our simple policy, we wire it up to a path on the API Server so that requests from the Web form result in a call to the SalesForce API:

Now we are in a position to post our Web form, which results in the information from the form being sent up to SalesForce through its API. Remember we haven't orchestrated in the email verification API yet. So, the bogus email makes it through fine.

Next we do the actual API orchestration. We add in the callout to the email verification API. Let's see how that is done:

At this point, we now have our service orchestration in action. The Vordel API Server has composed the two APIs together. If the response from the email verification API is a success, then we call the Salesforce API.

Let's see it in action:

Now let's take a closer look at how the response from the callout to the email verification API is used to check if the email is valid or not:

Finally, one of the most important aspects of orchestrating APIs is that you can apply SLAs (Service Level Agreements) and reporting to the APIs you are calling. This is especially important for SaaS services which you're paying for, such as Salesforce.com. Let's see how this is done with the Vordel API Server:

In this video blog, we saw application orchestration to a SaaS service via APIs, using the Vordel API Server. If you want to test this in action yourself, you can get your own free copy of the Vordel API Server from the Vordel website.

Read the original blog entry...

More Stories By Mark O'Neill

Mark O'Neill is VP Innovation at Axway - API and Identity. Previously he was CTO and co-founder at Vordel, which was acquired by Axway. A regular speaker at industry conferences and a contributor to SOA World Magazine and Cloud Computing Journal, Mark holds a degree in mathematics and psychology from Trinity College Dublin and graduate qualifications in neural network programming from Oxford University.