Invoking an OData Service with SAP HANA Cloud Integration

  • by Dr. Volker Stiehl, Professor, Ingolstadt Technical University of Applied Sciences
  • November 16, 2015
See how to use SAP HANA Cloud Integration (SAP HCI) to model the invocation of an external Open Data Protocol (OData) service. You apply the Request-Reply step in your integration flow and use the Query Editor to generate the URI for the actual OData invocation.
Learning Objectives

By reading this article you will:

  • Know how to model a synchronous call of an integration flow that in turn invokes an Open Data Protocol (OData) service to retrieve detailed data for an order business object
  • Learn how to apply the Request-Reply step in an integration flow correctly and how to connect it with an external receiver pool
  • Understand the benefits of using the Query Editor to efficiently construct the Representational State Transfer (REST)-based URI to actually invoke the OData service
  • Understand the difference between the Request-Reply and the Content Enricher steps, and when to apply which of the activities to achieve certain results
Key Concept

Several best practices have been developed for the handling of messages within an enterprise service bus. These best practices are known as Enterprise Integration Patterns (EIP). In this article two patterns are used: the Request-Reply and the Content Enricher. The Request-Reply pattern is used for scenarios in which a two-way communication is needed (e.g., when the sender expects a response from its communication partner). The Content Enricher pattern, on the other hand, takes care of extending the sender’s message with additional information (e.g., retrieving it from a database) that is needed for the receiver to work on the data. The Content Enricher pattern is typically used if the source system can’t provide all the information.

SAP HANA Cloud Integration (SAP HCI) allows for the development of sophisticated integration scenarios. In this article I provide an example of such a scenario: a synchronous call to an Open Data Protocol (OData) service for retrieving details of an order for a given order number. The order number is sent by the client to SAP HCI using a standard Simple Object Access Protocol (SOAP) call.

The example dives into the details of the communication with external data sources and how to use them in synchronous scenarios. Finally, I explain the Query Editor, a tool that helps you generate the sometimes quite complex Representational State Transfer (REST) URIs for actually invoking the external OData sources.

Dr. Volker Stiehl

Prof. Dr. Volker Stiehl studied computer science at the Friedrich-Alexander-University of Erlangen-Nuremberg. After 12 years as a developer and senior system architect at Siemens, he joined SAP in 2004. As chief product expert, Volker was responsible for the success of the products SAP Process Orchestration, SAP Process Integration, and SAP HANA Cloud Integration (now SAP HANA Cloud Platform, integration service). He left SAP in 2016 and accepted a position as professor at the Ingolstadt Technical University of Applied Sciences where he is currently teaching business information systems. In September 2011, Volker received his Ph.D. degree from the University of Technology Darmstadt. His thesis was on the systematic design and implementation of applications using BPMN. Volker is also the author of Process-Driven Applications with BPMN as well as the co-author of SAP HANA Cloud Integration and a regular speaker at various national and international conferences.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.