You are here

How to Consume Backend SOAP APIs from Frontend RAML APIs

SOAP is a messaging protocol that provides remote access to Web services. SOAP stands for Simple Object Access Protocol, and it uses XML and HTTP to open communications between two programs for sharing information.
 
The rigidity of this protocol and its use of XML to make a request meant that large batches of code needed to be written even for simple tasks. This cumbersome nature paved the way for the REST (REpresentational State Transfer) protocol that uses URLs in many cases, rather than XML, making it a popular choice for APIs.
 
In this tutorial on Appnation, Bahman explains the steps it took to integrate elements of these protocols and create a proof of concept that accesses an existing SOAP API backend from a RAML (RESTful API Modelling Language) API frontend. The author reverse engineers a Web Service Consumer example with a JSON over HTTP APIs frontend provided by MuleSoft, converting it to a RAML-based API using APIKit.
 
Followers are expected to have working experience with RAML, APIKit and DataMapper. The author gives step-by-step notes on exactly what has been reverse engineered. Some of the key changes include HTTP response builders not being used anymore, and HTTP inbound connector is replaced with HTTP listener.
 
The Web Services Consumer example is referenced throughout and links to the APIKit Console for the source code on CloudHub are provided.

Disclosure: MuleSoft is the parent company to ProgrammableWeb.

Be sure to read the next Integration article: 4 Lessons to Learn When Integrating With Third Party APIs

Original Article

Consuming Backend SOAP APIs from Frontend RAML APIs

 

Comments