Sie sind auf Seite 1von 50

Week 2 Unit 1: Enriching Content

by Calling OData Services

Enriching Content by Calling OData Services


Retrieve data via OData call (1)
Goals
Based on the incoming message, call an OData service to retrieve order data.
Fill the message body with the data returned from the OData service.
Input Message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Output Message

Public

Enriching Content by Calling OData Services


Retrieve data via OData call (2)
Goals
Based on the incoming message, call an OData service to retrieve the respective data.
Fill the message body with the data returned from the OData service.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


Retrieve data via OData call (3)
Goals
Based on the incoming message, call an OData service to retrieve the respective data.
Fill the message body with the data returned from the OData service.

Address of OData service


Query being executed by the
OData service.
Created either manually or with
the help of the Query Editor.
EDMX: XML file describing the
service entities (Order,
Customer, Product,)
(EDM = Entity Data Model)
2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


Retrieve data via OData call Query Editor (1)

Choose Operation and Fields

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


Retrieve data via OData call Query Editor (2)

Filtering by Defining Where Clause

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


Retrieve data via OData call Query Editor (3)

Final Query String


Sorting by Defining Order-By Clause

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


Demo

DEMO

Enriching Content by
Calling OData Services

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Enriching Content by Calling OData Services


What youve learned in this unit
How to benefit from the Content Enricher
pattern to build a reply message by calling an
external data source
How to use the Request-Reply step for
retrieving additional data from an OData
source
How to use the Query Editor to conveniently
formulate the query string being sent to the
OData service for data retrieval

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Thank you

Contact information:
open@sap.com

2016 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

11

Week 2 Unit 2: Message


Translation Using Mappings

Message Translation Using Mappings


Mapping (1)
Goals
Map the result of the OData service to a predefined XML format

Input Message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Output Message

Public

Message Translation Using Mappings


Mapping (2)
Goals
Map the result of the OData service to a predefined XML format

Mapping Step

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Message Translation Using Mappings


Mapping (3)
Goals
Map the result of the OData service to a predefined XML format

OData result structure


defined as XSD file
2016 SAP SE or an SAP affiliate company. All rights reserved.

Mapping
functions

Target XML format


defined as WSDL file
Public

Message Translation Using Mappings


Demo

DEMO

Message Translation
Using Mappings

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Message Translation Using Mappings


What youve learned in this unit
The prerequisites for mapping: data
structures available either in XSD or WSDL
format
How to apply the graphical mapping editor
How to benefit from mapping functions for
more sophisticated mapping requirements

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Thank you

Contact information:
open@sap.com

2016 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Week 2 Unit 3:
Content-Based Routing

Content-Based Routing
Expected messages
Goals
Routing messages
based on their content

2016 SAP SE or an SAP affiliate company. All rights reserved.

Input Message

Output Message

Public

Content-Based Routing
Integration flow with content-based router
Goals
Routing messages based on their content

Click

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Content-Based Routing
Configuration of content-based router (1)
Goals
Routing messages based on their content

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Content-Based Routing
Configuration of content-based router (2)
Goals
Routing messages based on their content

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Content-Based Routing
How to resolve overlapping conditions
Goals
Routing messages based on their content

Overlapping
Conditions

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Content-Based Routing
Demo

DEMO
Content-Based Routing

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Content-based Routing
What youve learned in this unit
How to apply the content-based router (CBR)
step in your SAP HANA Cloud Integration
(HCI-)based scenarios
What is necessary to configure the CBR step
in your message processing chain correctly
How to use either XML or non-XML
expressions to formulate the criteria by which
the selection of the right execution path is
calculated
How to influence the execution sequence of
the expressions to find the right path

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Thank you

Contact information:
open@sap.com

2016 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

10

Week 2 Unit 4: Splitter/Gather


Working with Lists

Splitter/Gather Working with Lists


Expected messages
Goals
Split a list into individual items, process items individually, and collect results for final reply message
Input Message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Output Message

Public

Splitter/Gather Working with Lists


Integration flow with Splitter/Gather steps
Goals
Split a list into individual items, process items individually, and collect results for final reply message

Important: Steps between Splitter and Gather


are always executed as many times as the list has entries!

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Configuration of the Splitter/Gather integration flow (1)
Goals
Split a list into individual items, process items individually, and collect results for final reply message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Configuration of the Splitter/Gather integration flow (2)
Goals
Split a list into individual items, process items individually, and collect results for final reply message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Configuration of the Splitter/Gather integration flow (3)
Goals
Split a list into individual items, process items individually, and collect results for final reply message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Configuration of the Splitter/Gather integration flow (4)
Goals
Split a list into individual items, process items individually, and collect results for final reply message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Enriching each item with real data (1)
Goals
Split a list into individual items, enrich with real data, and collect results for final reply message
Input Message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Output Message

Public

Splitter/Gather Working with Lists


Enriching each item with real data (2)
Goals
Split a list into individual items, enrich with real data, and collect results for final reply message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Splitter/Gather Working with Lists


Demo

DEMO

Splitter/Gather
Working with Lists

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

10

Splitter/Gather Working with Lists


What youve learned in this unit
How to apply list handling in your
SAP HANA Cloud Integration-based scenarios
What is necessary to configure the Splitter
and Gather steps in your message processing
chain correctly
How Splitter and Gather form a pair,
where all steps in-between the pair are
executed for every single item (iteration over
the list)
How the Splitter/Gather pattern can be used
to enrich each individual list item with data
coming from an external data source

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

11

Thank you

Contact information:
open@sap.com

2016 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

13

Week 2 Unit 5: Asynchronous


Communication

Asynchronous Communication
Expected messages
Goals
Run the Splitter/Gather scenario asynchronously (using real data) and store reply on SFTP server
Input Message

2016 SAP SE or an SAP affiliate company. All rights reserved.

Output Message

Public

Asynchronous Communication
Asynchronous integration flow
Goals
Run the Splitter/Gather scenario asynchronously (using real data) and store reply on SFTP server

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Asynchronous Communication
Configuration of an asynchronous scenario
Goals
Run the Splitter/Gather scenario asynchronously (using real data) and store reply on SFTP server

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Asynchronous Communication
Demo

DEMO

Asynchronous
Communication

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Asynchronous Communication
What youve learned in this unit
How to benefit from asynchronous message
processing in your SAP HANA Cloud
Integration-based scenarios
What is necessary to configure the SOAP
channel correctly to deliver messages
asynchronously to the SAP HCI server
How to add an asynchronous receiver to your
integration flow
How to track message handling within
SAP HANA Cloud Integration using the
Message Monitor

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Thank you

Contact information:
open@sap.com

2016 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Public