SAP HANA Cloud Integration For PI: Ankaiah Yerraboina (M.Tech) +91-7993388825

1.
SAP HANA Cloud Integration for PI
Ankaiah Yerraboina (M.Tech)

+91-7993388825 Page 1
1. SAP HANA Cloud Integration for PI
Getting Started:
SAP HANA Cloud Integration (SAP HCI) for process integration facilitates the integration of business
processes spanning different companies, organizations, or departments within an organization.
Provides an overview of the capabilities and security features of the

Product Overview
product.
What's New Provides an overview of the new features avaiable with the current release of SAP HCI.
Covers the tasks required to connect a customer system to SAP HCI.

Connecting a Customer System to SAP
HCI
These tasks are also subsumized under the term onboarding.
Managing Integration Content Covers the processes and concepts related to the design and maintenance of integration
content.
Integrating business processes using SAP HCI implies the exchange of data
(messages) between the involved participants. How messages are exchanged is
specified by integration content.
Operating and Monitoring SAP HCI Covers the processes and concepts relevant to operate SAP HCI.
Getting Started
Understanding the Key Concepts
Check out the Product Overview section of this documentation.
To learn about the key concepts and terms in a nutshell, read this topic: Elements of a Cloud-Based Integration
Scenario

+91-7993388825 Page 2
Product Profiles
The SAP HANA Cloud Integration Web application allows you to design Cloud integration content for different
target integration platforms. Accordingly, different product profiles are available.
To learn more, read this topic: Product Profiles.
Requesting Access to an Account
Prerequisite for all activities related to SAP HANA Cloud Integration (SAP HCI) is that you have access to an
SAP HCI account.
Table 1: Getting Started
Your Role and Prerequisites First Steps
You have no access to an Contact your account representative or go to the following

account yet. page: http://www.sap.com/pc/tech/cloud/software/cloud-applications/index.html .
If you like to get a trial account, mail to: hci.trial@sap.com.
When an account and tenant have been provided by SAP, you will receive a mail from
SAP with the subject text SAP HANA Cloud Integration – Notification. This mail contains
information on your account and test and productive tenant and a number of URLs. For
more information on the purpose of the URLs, see the table below.
Do not reply to the SAP HANA Cloud Integration – Notification mail. This is an
unmonitored mailbox. If you have any further questions, create a ticket
(component LOD-HCI).
You have been provided with You have received a mail from SAP with the subject text SAP HANA Cloud Integration –
an account. Notification. This mail contains information on the account.
Note Based on the edition of SAP HANA Cloud Integration that you have licensed, you
will receive access to one (SAP HCI-PI prod) tenant or two (SAP HCI PI prod and SAP
HCI-PI non-prod) tenants.
You (for example, in your role as the main responsible for the HCI account in your
organization or department) are in charge of defining who in your organization is to get
access to the account.
You need to define the right permissions for each of these people.

+91-7993388825 Page 3
Table 1: Getting Started
Your Role and Prerequisites First Steps
1. If you do not have an SCN user yet, register

at https://www.sdn.sap.com/irj/scn/register .
2. Manage the user and role assignments for those people who will be working on
the tenant (for example, as integration developers or as tenant administrators).
Perform these tasks using the SAP HANA Cloud Account Cockpit (see table
below).
More information: User Management for SAP HCI

You have been provided with the
required permissions (for example, You are in charge of performing specific tasks on your tenant (for example, as tenant
to perform integration developer administrator or integration developer).
tasks).
You have received the information on your account from the main account responsible.
1. If you do not have an SCN user yet, register

at https://www.sdn.sap.com/irj/scn/register .
2. To request access to your tenant, create a ticket (component LOD-HCI).
In the ticket, provide tenant ID and SCN user ID (from step 1).
3. If you are not yet familiar with SAP HCI, familiarize yourself with the main
components.
More information: Elements of a Cloud-Based Integration Scenario
4. Check out the URLs provided to you by your main account responsible (as
described in table below).
Access Points to Get Started with SAP HCI
The SAP HANA Cloud Integration – Notification mail contains three URLs that are specific to your tenant. The
following table explains which URL to use when. Each URL enables you to connect to SAP HCI in a different
way.
The following table lists the first access points to SAP HANA Cloud and SAP HCI.
Table 2: Access Points

+91-7993388825 Page 4
You want to ... Use this URL ...
Perform user management tasks for your SAP HANA SAP HANA Cloud Account Cockpit URL (more
Cloud account information: Adding Members to an Account)
Go to SAP HANA Cloud Account Cockpit to specify which

roles are to be assigned to the users of the account.
If this function is not available for your account, ask your SAP
contact or create a ticket (component LOD-HCI) to activate
it.
Access the Web-based SAP HCI tools Web UI URL (as contained in the SAP HANA Cloud
Integration – Notification mail)
The Web application is the first point of entry for customers
using SAP HCI. It provides access to the available SAP-
defined integration content, which can be used out of the box
to configure message processing on the integration platform.
In addition, it provides functions to configure your own
integration content and to monitor the message processing
during runtime.
Use Eclipse-based tools Management URL (as contained in the SAP HANA Cloud
Integration – Notification mail)
The Eclipse-based Integration Designer and Integration
Operations features provide additional functions for designing
integration content and for operating and monitoring a cluster.
You install these applications locally on your computer as
additional software in an Eclipse instance.
More
information: https://tools.hana.ondemand.com/#hciInformation
After you have installed the Eclipse tools locally on your

computer, you need the management URL to connect them to
your tenant.
Configure the components in your landscape that are to Runtime node URL (as contained in the SAP HANA Cloud
be connected to the tenant Integration – Notification mail)
The HCI runtime that processes the exchanged messages is

implemented on virtual machines, referred to as runtime
nodes. Each tenant comes with one or more runtime nodes
exclusively reserved for the associated customer. In order to

+91-7993388825 Page 5
Table 2: Access Points
You want to ... Use this URL ...
enable a system or application to exchange data with other

systems (through the SAP HCI platform), your system or
application has to know the address of your SAP HCI runtime
node. Therefore, you need the URL of the runtime node in
order to set up the connection between your system and SAP
HCI.
The following figure illustrates the different ways to connect to SAP HCI.
Product Profiles
The SAP HANA Cloud Integration Web application allows you to design Cloud integration content for different
target integration platforms. Accordingly, different product profiles are available.

+91-7993388825 Page 6
A product profile defines a set of capabilities for Cloud integration content design supported by a specific
target integration platform. For example, a specific product profile supports the configuration of a specific set of
adapter types and integration flow steps.
The following product profiles are available:
Table 1: Product Profiles
Product Profile Target Integration Platform
SAP HANA Cloud Integration Cloud-based integration runtime of SAP HANA Cloud
Integration
SAP Process Orchestration 7.5, SP0 On premise integration runtime of SAP Process Integration
SAP Process Orchestration 7.5, SP1 (for the specified release)
SAP Process Orchestration 7.5, SP2
SAP Process Orchestration 7.5, SP3
Prior to start working with Cloud integration content, you need to know on which target integration platform(s)
the Cloud integration content is to be deployed and executed.
If you encounter use cases where both on premise and Cloud-based integration platforms are involved, you
might like to have several options and, accordingly, both product profiles are of interest for you.
The following figure illustrates the use case for the product profiles SAP HANA Cloud Integration and SAP
Process Orchestration 7.5 SP0.

+91-7993388825 Page 7
When you have decided on the product profiles in question, the process is as follows:
Based on your choice, you request an SAP HANA Cloud Platform account and tenant at SAP.
As soon as the tenant is available, you connect to it using the SAP HCI Web application (using the Web UI
URL provided in the mail you received from SAP).
Under Settings, you choose the default product profile. When you create a new integration flow, this choice
will be applied by default.
The integration flow editor shows the options and executes checks based on the chosen product profile. The
reason for this is that the target integration platform imposes specific restrictions on the Cloud integration
content.
You have the option to configure a product profile also for an individual integration flow (under Runtime
Configuration).
Operating Model
An operation model clearly defines the separation of tasks between SAP and the customer during all phases of
an integration project.
SAP HANA Cloud Platform, SAP HANA Cloud Platform, integration service (also known as SAP HANA Cloud
Integration), and SAP Financial Services Network have been developed on the assumption that specific
processes and tasks will be the responsibility of the customer. The following table contains all processes and
tasks involved in operating the aforementioned services and specifies how the responsibilities are divided
between SAP and the customer for each individual task. It does not include the operation of systems and
devices residing at operational facilities owned by the customer or any other third party, as these are the
customer's responsibility.
Changes to the operating model defined for the services in scope are published using the What's New (release
notes) section of the respective product documentation on SAP Help Portal. Customers and other interested
parties must review the product documentation on a regular basis. If critical changes are made to the operating
model, which require action on the customer side, an explicit notification is sent by e-mail to the affected
customers. If customers want to receive such notifications, they can subscribe to the relevant communication
channels offered by SAP (for example, by opening a customer incident on component LOD-HCI).
It is not the intent of this document to supplement or modify the contractual agreement between SAP and the
customer for the purchase of any of the services in scope. In the event of a conflict, the contractual agreement
between SAP and the customer as set out in the Order Form, the General Terms and Conditions of SAP Cloud

+91-7993388825 Page 8
Services, the supplemental terms and conditions, and any resources referenced by those documents always
takes precedence over this document.
Responsibilities for operating the following services are listed in the table below:
 SAP HANA Cloud Platform (referred to as Platform)

 SAP HANA Cloud Platform, integration service (referred to as SAP HANA Cloud Integration or briefly
as SAP HCI)
 SAP Financial Services Network (referred to as SAP FSN)
Key Features
SAP HANA Cloud Integration (SAP HCI) supports end-to-end process integration across cloud-based and on-
premise applications (cloud-cloud and cloud-on-premise integration).
It comprises the following key features:
 Core runtime for processing, transformation, and routing of messages to be exchanged between the
involved customer systems
Message processing at runtime is performed by a cluster of virtual machines running on SAP HANA
Cloud. Here, the platform ensures that data related to different customers connected to SAP HCI is
isolated. This is important, for example, when using SAP HCI for business-to-business scenarios.
 Out-of-the-box connectivity support (IDoc, SFTP, SOAP/HTTPS, SuccessFactors, OData, HTTPS)

 Security features such as content encryption and certificate-based communication
The current version of SAP HCI is available for customers and partners as an Application Edition, especially
for a dedicated set of SAP OnDemand solutions (SAP Customer OnDemand, SuccessFactors BizX, SAP
Financial Services Network). Upon purchase, predefined, ready-to-use prepackaged integration content can be
made available by SAP without the immediate need for additional hardware or integration skills on the
customer’s side. This drastically reduces integration project lead times and lowers resource consumption
significantly.
SAP HCI offers full flexibility in how messages can be exchanged between customer systems by the following:
 Leveraging preconfigured integration patterns. These integration patterns provide different options for
configuring the data flow between participants, for example, by using routing rules.
 Using various connectivity options. This covers a set of adapters (or endpoint types) that allow
participants to connect with different communication protocols to SAP HANA Cloud Integration.

+91-7993388825 Page 9
You - as an SAP HCI customer - can make use of the integration capabilities without the need to install an
integration middleware on your own – as it would be the case with an on premise integration solution.
SAP HCI works that way that you and your partners that you like to collaborate with make use of the integration
capabilities deployed in the SAP Cloud. That means: one platform (hosted by SAP centrally) is used by
independent customers in order to get their systems exchanging data with each other.
Integration Capabilities
There is a wide range of integration capabilities that define different ways how messages can be processed on
a the integration platform and exchanged between sender and receiver systems.
The following figure illustrates, as one example, the routing capability, that allows you to forward a message
from one participant to multiple receivers.

+91-7993388825 Page 10
Integration capabilities are configured within integration flow steps (in the Integration Designer).
The following table lists the available integration capabilities, arranged by the related integration flow step
types.
 Participant
o Sender: Specifies a sender of a message (to be processed on the tenant).
o Receiver: Specifies a receiver of a message (processed on the tenant).
 Process
o Integration Process: Specifies how messages are to be processed on a tenant.
o Local Integration Process: Fragments an integration process into smaller processes.
 Event
o Start Message
o Start Event
o Timer: Sets a date and time when the integration process should run once or repetitively.
o End Message
o End Event
o Terminate Message
o Escalation: Stops message processing; for synchronous messages, an error messages is sent to
the sender.
 Mapping: Transforms the data structure and format used by the sender into a structure and format
that the receiver can handle.
 Transformation
o Content Modifier: Modifies the content of the incoming message by providing additional
information. This step allows you to modify a message by changing content of the data containers

+91-7993388825 Page 11
that are involved during message processing (message header, message body or message
exchange).
o Converter: Transforms an input message to another format.You can also specify some conditions
that are used as reference to transform the message.
o XML-to-JSON (JSON-to-XML) Converter: Transforms messages in XML format to JSON
format (or vice versa).
Decoder: Decodes the incoming message to retrieve original data (for example, when a base64-
encoded message has been received).
Encoder: Encodes the message using an encoding scheme to secure any sensitive message
content during transfer over the network.
Filter: Filters information by extracting a specific node from the incoming message.
Message Digest: Calculates a digest of the payload or parts of it and stores the result in a
message header.
Script: Executes custom Java script or Groovy for message processing.
Call
External Call: Calls an external system.
o Request-Reply: Accesses external resources in a synchronous step.
o Send
Calls a receiver system for use cases where no reply is expected.
o Content Enricher: Accesses external resources and merges the returned content with the
original message.
Local Call
o Process Call: Calls a local integration process. Local processes allow you to fragment an
integartion flow into smaller elements.
o Looping Process Call
Calls a local integration process in a loop.
Routing
Gather: Combines multiple incoming messages into a single message.
Router: Routes a message to one or more receivers.
The platform also supports routing that depends on the content of the message (content-based
routing).
For example, the tenant detects that a message has a particular field value, and forwards it to the
specific receiver participant that handles requests from the sender participant.

+91-7993388825 Page 12
Splitter: Decomposes a composite message into a series of individual messages and sends them
to a receiver.
Multicast (can only be configured with Eclipse tooling): Sends the same message to more than
one receiver.
This step provides the option to define the sequence in which the message transfer is initiated to
the receivers.
Join (can only be configured with Eclipse tooling): Brings together the messages from different
routes before combining them into a single message.
Is used in combination with the Gather element. Join only brings together the messages from
different routes without affecting the content of messages.
Persistence
Persist Message: Stores a message payload so that you can access the stored message and
analyze it at a later point in time.
Data Store Operations: Specifies a transient data store that temporarily stores messages for
later processing.
Write Variables: Specifies values for variables required during message processing.
Security
Encryptor: Digitally encrypts the content of a message.
Decryptor: Decrypts the content of a message.
Signer: Digitally signs a message.
Verifier: Verifies a signature.
Validator
XML Validator: Validates the message payload in XML format against the configured XML
schema.
Note
For mappings, XSLT (Extensible Stylesheet Language Transformations) 2.0 is supported.
Note: Automatic stream caching mechanism is enabled to support streaming of large data and to avoid out-
of-memory problems. This caching mechanism adds an interceptor between two processors, and caches
streams either in memory or, if the stream is larger than 64 KB, in the file system. Hence enabling the streams
to be read several times from the cache with reduced memory consumption.
Mapping
Mapping transforms (maps) sender into receiver data structures.

+91-7993388825 Page 13
In scenarios spanning different application systems or different organizations and enterprises, it is very likely
that the structure of the data exchanged between two participants will differ on both sides of a connection due
to business-related reasons. To enable a seamless exchange of data, the data structures on both sides of a
connection have to be transformed (or: mapped) into each other. There is the option to apply structural
mapping of XML documents.
You can re-use existing on-premise content (service interfaces / message mappings / operation mappings /
XSLT based mappings) from an SAP Enterprise Services Repository (EHP 1 for SAP NetWeaver 7.3).
Value mappings allow you to map different representations of an object to each other.
Value mappings are useful when performing a dynamic value lookup of an object that has different
representations in different contexts. In value mappings, you map these different representations of an object to
each other by setting mapping rules in a value mapping table.
Note: For example: You can use a value mapping to map a Merchant ID to a Customer ID, where Merchant
ID is an external application representation of a customer, while Customer ID is an internal SAP representation.
Connectivity (Adapters)
You have the option to specify which technical protocols should be used to connect a sender or a receiver to
the tenant.
The following adapters are available:
 Ariba sender or receiver adapter
Connect a tenant to the Ariba network (this allows SAP and non-SAP cloud applications to send and
receive business-specific documents in cXML format to and from the Ariba network).
 Facebook receiver adapter
Access and extract information from Facebook based on certain criteria such as keywords or user
data.
 HTTP receiver adapter
Connect to a receiver system using the HTTP protocol.
 HTTPS sender adapter
Connect to a sender system using the HTTPS protocol.

+91-7993388825 Page 14
 IDoc sender or receiver adapter
Exchange IDoc messages with another system.
 LDAP receiver adapter
Connect to LDAP directory service
 Mail sender adapter
Receiver e-mails from an e-mail server.
 Mail receiver adapter
Send e-mails to an e-mail server.
 OData sender and receiver adapter
Connect to systems exposing OData services (OData service providers).
OData stands for the Open Data Protocol.
 ODC receiver adapter
Connect to SAP Gateway OData Channel
 SFTP sender adapter
Connect to a remote system using the SSH File Transfer protocol (also referred to as Secure File
Transfer protocol) to read (poll) files from the system.
 SFTP receiver adapter
Connect to a remote system using the SSH File Transfer protocol to write files to the system.
 SOAP /SOAP 1.x sender and receiver adapter
Exchange messages with another system that supports SOAP 1.1 or SOAP 1.2.
 SOAP / SOAP RM sender and receiver adapter

+91-7993388825 Page 15
Exchange messages with another system based on the SOAP communication protocol and SAP RM
as the message protocol.
 SuccessFactors sender and receiver adapter
Connect to a SuccessFactors system using the SOAP, OData, and REST message protocol.
 Twitter receiver adapter
Access Twitter and either read or post tweets.
Elements of a Cloud-Based Integration Scenario

In a cloud-based integration scenario, different customer components exchange messages with each other,
and SAP HANA Cloud Integration (SAP HCI) acts as an integration hub. Each customer component is securely
connected to the SAP HCI runtime.
In a nutshell, an integration scenario relies on a general landscape and component setup as illustrated in the
following figure.
 Secure connections between SAP HCI and the involved remote components
The SAP HCI integration platform is fragmented into different tenants. A tenant represents the
resources of the platform allocated to a customer and must be securely connected to the associated
component in the customer landscape. The chosen transport protocol allows for specific transport-level
security options (for example, HTTPS). On top of this, SAP HCI supports various message-level
security options, which allow you to digitally sign and encrypt the transferred data. The security setup
relies on digital keys, which are stored in keystores; the creation and management of keystores is part
of the security configuration of each component. The type of keystore and digital key used depends on
the chosen security option. Therefore, we refer to these elements generally as security artifacts.

+91-7993388825 Page 16
In order to enable a tenant to securely communicate with a customer component, you have to
configure the required security artifacts and deploy them on the tenant. On the other side of the
communication, the customer component has to be configured accordingly by the responsible system
administrator.
 Integration knowledge specified and accessible to the runtime components
During the operation of an integration scenario, SAP HCI acts as an integration hub for the message
exchange. To ensure a seamless process and data flow during the operation of the scenario, the SAP
HCI runtime needs to access the information on how messages are to be processed. This information
is also referred to as integration knowledge and is contained in the integration content for each
tenant. A key part of the integration content is the integration flow, which specifies step-by-step how
a message is to be processed on a tenant. For example, a mapping step transforms the data
contained in a message so that it can be processed by a receiver system, whereas a routing step
defines one or more receivers of a message.
During the design time of an integration scenario, you define the required integration flows.
To activate an integration flow, you have to deploy it on the associated tenant.
Integration Flows
An integration flow allows you to specify how a message is processed on a tenant.
The following figure provides a simplified and generalized representation of an integration flow.
Tenant Isolation

+91-7993388825 Page 17
For each customer system connected to SAP HANA Cloud Integration, separate resources in terms of memory
and CPU are allocated in the SAP HANA Cloud. These resources are referred to as tenants.
At runtime, SAP HANA Cloud Integration (SAP HCI) processes the data that is exchanged between the
involved participants on a cluster of different virtual machines hosted in the SAP HANA Cloud. A cluster
associated with a specific tenant is referred to as a tenant cluster.
Note: A virtual machine (VM) is a software implementation of a machine that executes a program like a
physical machine.
SAP HCI is designed so that the involved virtual machines are strictly separated from each other with regard to
the related customers. In other words, separate resources ( memory, CPU, and file system) of the cloud-based
integration platform are allocated to each customer – although all customers might share the same hardware.
In addition, each tenant uses a separate database schema, which guarantees that the data of the different
customers is strictly separated. This separation is also referred to as tenant isolation.
The following figure illustrates this concept for two customers communicating with each other using SAP HCI.
Using Predefined Integration Content

+91-7993388825 Page 18
SAP HANA Cloud Integration allows the participating organizations to develop, deploy, and consume services
in a standardized manner. SAP provides a predefined set of integration content that covers most of the
integration needs for a particular scenario. Customers can use the predefined integration content to implement
their integration scenarios with less time and effort. To accomplish this, however, customers need to register
with SAP HANA Cloud Integration and complete the onboarding process as recommended by SAP.
Customers can re-use existing on-premise content (message mappings / operation mappings / XSLT based
mappings) from an SAP Enterprise Services Repository (EHP 1 for SAP NetWeaver 7.3).
What Is Integration Content
Operating business processes using SAP HANA Cloud Integration implies the exchange of data (messages)
between the participants. How messages are exchanged is specified by integration content that is designed
based on the requirements of the business process.
As one key part of integration content, integration flows describe how a message sent from one participant is
processed by SAP HANA Cloud Integration.
In other words, using integration flows, specific integration pattern like mapping or routing can be specified.
For example, a set of integration flows specifies that a message sent from participant A is forwarded by SAP
HANA Cloud Integration to three different receivers B, C, and D, dependent on the business content contained
in message. Integration flows also specify mappings of the data structure between sender and receiver or the
endpoints of sender and receiver participants.
Tool Access
There is set of tools that help you to access and manage integration content and to operate and monitor
integration artifacts and messages at runtime.
The software that implements the process integration capabilities is updated on a regular basis in the SAP
HANA Cloud.
In addition to the runtime components, the following tools are available:
Table 1: Tools
Tool Description
Web-based application that allows you to browse through integration

Web application content predefined by SAP
Public Web The tenant-specific Web application allows you also to design

+91-7993388825 Page 19
Table 1: Tools
Tool Description
application: https://cloudintegration.hana.ondemand.com your own integration content and to monitor the message
exchange and the tenant cluster at runtime.
In addition to that, a tenant-specific Web application is
available for customers who have been provided by a
tenant. The corresponding Web application URL is
provided in the mail from SAP together with the details
on the tenant.
Integration Designer tool Locally installed Eclipse add-on that allows you to design your own
integration content
Integration Operations tool Locally installed Eclipse add-on that allows you to monitor the message
exchange and the tenant cluster at runtime
Make sure that for the Integration Designer and Integration Operations tools (to be locally installed on your
client) you use the same version as for the released runtime components. You will get the actual Integration
Designer and Integration Operations tool version (according to the actually released SAP HCI software)
through this Eclipse update site: https://tools.hana.ondemand.com/luna.
More information: https://tools.hana.ondemand.com/#hci
To administer an account, you use the SAP HANA Cloud Platform Cockpit. The URL depends on the data
center.
Table 2: SAP HANA Cloud Platform Cockpit URLs
Data Center URL
Rot https://account.hana.ondemand.com/cockpit
Ashburn https://account.us1.hana.ondemand.com/cockpit
Sydney https://account.ap1.hana.ondemand.com/cockpit
Software Update
The software is updated monthly by SAP.
The following applies for software updates.
 Software updates are performed by SAP. Customers do not have to take any action here.

+91-7993388825 Page 20
 Software updates do not require any downtime of productive scenarios running on the integration
platform.
 SAP ensures that deployed integration flows continue running after the update.
 In case a tenant is not accessible or shows component failures after an update, SAP is notified by
appropriate alert mechanisms and triggers the necessary recovery processes.
The SAP HANA Cloud Integration Terms and Conditions specify details of service level agreements
and system availability. You can find the SAP HANA Cloud Integration Terms and Conditions
at: http://global.sap.com/corporate-en/our-company/agreements/index.epx .
 If a specific integration flow stops working unnoticed after update, customers are asked to open a
ticket under LOD-PI (priority high).
Product Availability
SAP HCI provides capabilities to process messages in integration scenarios spanning different companies,
organizations, or departments within an organization. The SAP HCI software that implements the process
integration capabilities is updated on a regular basis in the SAP Cloud. In addition to that, SAP HCI provides a
set of tools that help you to access and manage integration content and to operate runtime clusters. This topic
summarizes the required software to use these tools.
Table 1: Product Availability
Tool Runs with ...
Web application The SAP HCI Web application has been tested using the following browsers:
 Windows Internet Explorer (as of version 10)

 Mozilla Firefox (latest version)
 Google Chrome (latest version)
Note
The application can also be used with Safari browser and Internet Explorer 9. However, be
aware of the fact that some features might not work as expected.
Integration Designer/Integration Last and current Eclipse version according to the SAP Release Train for Eclipse (SRTE) (not
Operations tool supported for MAC OS).
More information on SRTE: https://tools.hana.ondemand.com/

+91-7993388825 Page 21
Terms of Use | Copyright/Trademark | Privacy | Legal Disclosure | Disclaimer

+91-7993388825 Page 22

SAP HANA Cloud Integration For PI: Ankaiah Yerraboina (M.Tech) +91-7993388825

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP HANA Cloud Integration For PI: Ankaiah Yerraboina (M.Tech) +91-7993388825

Uploaded by

Copyright:

Available Formats

1.

SAP HANA Cloud Integration for PI

Ankaiah Yerraboina (M.Tech)

Provides an overview of the capabilities and security features of the

Covers the tasks required to connect a customer system to SAP HCI.

Check out the Product Overview section of this documentation.

Ankaiah Yerraboina (M.Tech)

To learn more, read this topic: Product Profiles.

Requesting Access to an Account

Table 1: Getting Started

Your Role and Prerequisites First Steps

You have no access to an Contact your account representative or go to the following

If you like to get a trial account, mail to: hci.trial@sap.com.

Ankaiah Yerraboina (M.Tech)

Table 1: Getting Started

Your Role and Prerequisites First Steps

1. If you do not have an SCN user yet, register

More information: User Management for SAP HCI

1. If you do not have an SCN user yet, register

More information: Elements of a Cloud-Based Integration Scenario

Access Points to Get Started with SAP HCI

Table 2: Access Points

Ankaiah Yerraboina (M.Tech)

You want to ... Use this URL ...

Go to SAP HANA Cloud Account Cockpit to specify which

After you have installed the Eclipse tools locally on your

The HCI runtime that processes the exchanged messages is

Ankaiah Yerraboina (M.Tech)

Table 2: Access Points

You want to ... Use this URL ...

enable a system or application to exchange data with other

Ankaiah Yerraboina (M.Tech)

The following product profiles are available:

Table 1: Product Profiles

Product Profile Target Integration Platform

SAP Process Orchestration 7.5, SP1 (for the specified release)

SAP Process Orchestration 7.5, SP2

SAP Process Orchestration 7.5, SP3

Ankaiah Yerraboina (M.Tech)

Ankaiah Yerraboina (M.Tech)

 SAP HANA Cloud Platform (referred to as Platform)

It comprises the following key features:

 Out-of-the-box connectivity support (IDoc, SFTP, SOAP/HTTPS, SuccessFactors, OData, HTTPS)

Ankaiah Yerraboina (M.Tech)

Ankaiah Yerraboina (M.Tech)

Ankaiah Yerraboina (M.Tech)

Calls a receiver system for use cases where no reply is expected.

Calls a local integration process in a loop.

Ankaiah Yerraboina (M.Tech)

For mappings, XSLT (Extensible Stylesheet Language Transformations) 2.0 is supported.

Mapping transforms (maps) sender into receiver data structures.

Ankaiah Yerraboina (M.Tech)

The following adapters are available:

 Ariba sender or receiver adapter

 Facebook receiver adapter

 HTTP receiver adapter

Connect to a receiver system using the HTTP protocol.

 HTTPS sender adapter

Connect to a sender system using the HTTPS protocol.

Ankaiah Yerraboina (M.Tech)

Exchange IDoc messages with another system.

 LDAP receiver adapter

Connect to LDAP directory service