Skip to Content
Author's profile photo Amber Badam

SAP HCP-IS(HCI): Dynamically configure the Address field of the HTTP adapter

Some times it is required that we need to dynamically configure the HTTP address field while using an HTTP receiver adapter. HCI enables flexibility in declaring variables in Address URL and also in Query which is transferred with HTTP request.

In the following flow, we call a Product Search service REST API on an on-premise Hybris system which is called from HCI using Hana Cloud Connector. The products fetched differs  based on the variable User Group we pass in the Request Path of the URL.

Let discuss how we can configure this dynamically in Target URL. In my case I have the following URL to fetch products.${header.UserGroup}/products/search

As of now SAP HCI only supports using header.variable in the Address field. i.e. ${} in address field would get the value of header foo ( as contained in the  incoming message ) and will be written to  Camel header CamelHttpUri.

In Query of the HTTP adapter, we could use both header.variable and property.variable for defining parameters in Query which will be written to Camel header CamelHttpQuery..

SAP standard documentation about the HTTP Receiver adapter is quite detailed and covers most of the properties we could define on the adapter.

In the above Iflow before calling the Products Search API, below subflow to fetch the User Groups is defined.

Again here a call to Hybris is made to get Customer Groups using HTTP receiver adapter.

The response from the call is JSON which is further converted to  XML by introducing an Root element using a content modifier.

<?xml version="1.0" encoding="UTF-8"?>
<Root xmlns:xs="">
        <name>B2B Group</name>
        <name>B2B Customer Group</name>

From the above XML, we need to pick value of the element value contained in tag <uid>UG_US02_01<uid> which is under element <userGroups>.

For this we could define a Header variable “UserGroup” using content modifier with XPATH value substring(//uid[starts-with(.,’UG_’)],4) which returns value US02_01.

This value is further passed to mainflow from where this subflow was called. Eventually header.UserGroup replaces the following URL${header.UserGroup}/products/search


Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jens Schwendemann
      Jens Schwendemann

      Unfortunately I cannot get this working. Neither for Address nor for Query (which according to should be possible as of now also. Could you verify this is (still) working?


      I'll have open a discussion on this.