Skip to Content

Mapping as a Service in HCI

Those who are familiar with PI would know that we could expose an operation mapping as a service by enabling AEX on BPM with NetWeaver 731 on wards. In this blog, I will show how to expose a mapping as a service in HCI

A little bit of background. I have more than a decade of experience with SAP NetWeaver PI, was fortunate enough to work on all most all releases starting with XI 2.0 to the latest 7.5. Since last couple of years, I have been working with HCI and I am primarily responsible for Cloud for Customer integration content for PI and HCI. From my limited experience, I can say from a developer and an end user perspective HCI really signs mainly with its ease of use and a very flexible pipeline. I am totally in love with HCI 🙂 , Sorry NetWeaver PI/PO.  More on this bit later

So now, how do I expose a mapping as a service? Turns out to be very simple, I just need to have an Integration Flow with a sender and a mapping as shown below


The sender system here is the tenant on which I will deploy the Integration Flow project.  The sender system uses a SOAP sender adapter with message protocol set to 1.x and a service path over which we can later consume the mapping as a service.

iFlow Sender Channel.png

Import to note do not specify a WSDL in the sender channel else it will be treated as an asynchronous scenario and the consumer will not receive a response back.

For the mapping, I am using Groovy script, another reason I am in love with HCI. Groovy makes building and parsing XML very simple. Once you are familiar with Groovy trust me you will not use JAVA for working with XML. Groovy is shorter and dynamic. Add to it you can run any java code inside Groovy

For this demo, I am using a very simple mapping, which will simply add two values and return us the result. But same can be done via a message/graphical mapping as well.

The Script code to achieve the same is:


import java.util.HashMap;

import groovy.xml.StreamingMarkupBuilder

def Message processData(Message message) {

  def body = message.getBody(java.lang.String);

  def root = new XmlSlurper().parseText(body);

  def outputBuilder = new StreamingMarkupBuilder()

  outputBuilder.encoding = “UTF-8”

  def outxml = {



  outarg(root.arg1.toInteger() + root.arg2.toInteger())



  String result = outputBuilder.bind(outxml)


  return message;


As you can see here in Groovy, we have a nearly 1:1 ratio of code to XML.

As a last step, we deploy the Integration Flow project and test it. The result of a test run from SoapUI is, shown below for reference.


To call this mapping from another integration project we can simply configure a service call as we call any other SOAP service.

Now why do we need to expose a mapping as a service, well simple answer is reusability. In 1611 release, we plan to ship a new way of replication employees from SuccessFactors employee central to SAP Hybris Cloud for Customer and there we are using this mapping as a service to convert the source format to target format. I will explain this later in a different blog once we have the official release in place.

As a disclaimer, the views expressed here are based on my personal experience.

You must be Logged on to comment or reply to a post.
  • Hi Abhinash,

    I had used a similar technique to call one Integration Flow of HCI from another Integration Flow ( as they were independent pieces ) in my blog series on HCI & SFDC Integration to segregate my Login Integration Flow to get sessionID from my Business Processing Integration Flow HCI -Integrating SalesForce (SFDC) using HCI -Part 1

    What I am wondering is - considering that the ServiceCall makes the call from HCI over the internet back to HCI it would be great if there is an option of a "Local Service Call". Something between the Process Call / Service Call to enable one HCI Integration Flow trigger another HCI Integration Flow ( possibly using SOAP Adapter as you have defined )..

    Are you aware of any such functionality in planned releases?



    • Hello Bhavesh,

      I will check on this and get back. But as far as I know when we call a URL on the same system it it not routed via the whole Internet infrastructure, the proxy/DNS servers are smart enough to know the source and target system in the call are same system. Still the traffic leaves the teant to the proxy before it is routed back to the tenant. I will update my comment here when I have an answer for you.

      Best regards, Abinash

      • Thanks Abhinash! The reason I thought this authentication happens via the Internet is because I had to provide the Basic Authentication details in my SOAP Receiver Adapter ( Service Call ) else the message would not invoke the additional service!

        Look forward to your feedback from the inside! Thanks!



        • Hello Bhavesh, a quick update. For iFlow to iFlow communication within the same Tenant we are developing ‘Direct’ Adapter. As of now the tentative plan is, development to be done in the next 2 months and should be available for public usage by the end of the year.

          Best regards, Abinash