Tim D'haeyer

A very common scenario for any API management tools is to expose an (older) back end SOAP service as a REST JSON service. In this post I will explain how you can do this in Azure API Management. I'm not an API management expert, this is just my experience. The service The case I will be using is a WCF-basicHttp service hosted on a BizTalk 2010 machine and IIS. The service to list customers in the ERP (SAP). The SOAP request and response look like this. Request <CustomerList xmlns="http://www.mydomain.com/schemas/"> <SalesOrganizations> <SalesOrganization>XXXX</SalesOrganization> </SalesOrganizations> <WebshopRelevant>true</WebshopRelevant> </myp:CustomerList> Response <CustomerListResponse xmlns="http://www.mydomain.com/schemas/"> <Customer> <CustomerNumber>0000000001</CustomerNumber> <SalesOrganization>XXXX</SalesOrganization> <Lastname>Customer 1...

About 2 years ago we started the implementation of SuccessFactors in our company. This is a Saas tool to store all your HR related data with extra modules for recruiting, learning, compensation, ... The company was bought by SAP in 2011 and is sold as a replacement for the SAP HR module on premise. The first meeting we had about integrating it with other applications, the consultants told us everything is very easy. Being a SaaS tool I was expecting some kind or REST API or at least a web service we could use to do the basic CRUD operations. I was quite surprised when the consultant (which was an expert in SuccessFactors integration) started talking about CSV and SFTP. The first impression I had after that meeting was "Is this really the only way we can integrate with a modern SaaS tool?" Since we were on a really short timeline and had no experience ourselves, we trusted the consultants and went ahead with the implementation. My colleague and I couldn't believe t...