Configure SAP Cloud Platform for on-premises systems

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Integrating external applications from Bizagi > SAP integration > SAP Cloud Platform using OData >

Configure SAP Cloud Platform for on-premises systems

Overview

First, you need to configure your SAP Cloud Platform, so all the integration services are set in your Cloud Platform sub-account. Because Bizagi uses the SAP Cloud Platform as an intermediary integration, you need to set a connection between the Cloud Platform and the on-premises SAP system. This connection is done using the SAP Cloud Connector. This connector allows redirecting requests to the SAP on-premises system. The connector includes authentication of systems, so adds security for the integration of systems.

 

SAP Services

To integrate Bizagi with SAP S/4 HANA on-premises (or other on-premises versions), you need to create and set SAP services within the Cloud Platform, that help systems to integrate instances. The services needed are described according to the following flow:

 

1.Router: When Bizagi calls the SAP Cloud Platform, it is redirected to the Rotuer, which is the entry point for all business applications.

2.Authorization and Trust: As a security layer, SAP provides an authorization service, so the Bizagi can get an authorization token to do invocations of SAP functions. If the authentication fails, Bizagi displays an error sent by the Authorization and Trust service.

3.Buildpack: To get the proper route to the on-premises system, there is a Destination service that holds the information of the location of the SAP on-premises system. Once the Buildpack gets the destination information, it uses the Connectivity service, to establish a secure connection.

4.Destination: This service holds the information of the SAP system backend configuration.

5.Connectivity: This service establishes a connection between the SAP Cloud Platform and your SAP systems with isolated networks.

6.Cloud Connector: It is a link with on-premises systems, so the Cloud Platform and its services can access through the connector  For further information about the Cloud connector, click here.

 

The following diagram shows the flow described.

 

SAPCloud_4

 

Before you start

You need the following components:

1. Having configured the SAP Cloud Foundry. For further information click here.

2. Having an instance of the SAP Cloud Connector. To see a guide to install the Cloud Connector, click here.

3. A SAP S/4 HANA, ECC or R/3  on-premises system with the OData layer exposed.

4. Having the Cloud Foundry Command Line Interface installed.  To learn how to install the CLI, click here.

 

Configuration Steps

1. Set the Cloud Connector

2. Define a new destination configuration

3. Set the Authorization and Trust Service

4. Set the Destination Service

5. Set the Connectivity Service

6. Install the Router and Buildpack

 

1. Set the Cloud Connector

Get the information of your Cloud Foundry sub account. Access the SAP Cloud Platform Cockpit, and click your sub account:

 

SAPCloud_6

 

Get the following information:

Sub account ID.

Region of the API endpoint: For example, this is located in US East (va) -AWS (see previous picture).

 

SAPCloud_7

 

Now access the Cloud Connector (usually located in http://localhost:8443). On the left-hand side, click the Connector Module, then Add a new Sub Account.

 

SAPCloud_8

 

Register the following information:

 

Region:  Region of the endpoint API obtained in the SAP Cloud Platform cockpit.

Sub Account ID: Cloud Platform sub account ID obtained in the cockpit.

Display Name: Any display name for the connection to a sub account.

Log in Email: SAP Cloud Platform log in email.

Password: SAP Cloud Platform log in password.

 

SAPCloud_9

 

Click Save. After a few seconds you can review the status.

 

SAPCloud_10

 

In the Cloud Connector site, under the sub-account created, click the Cloud To On Premise module. and Add a new system with the ( + ) symbol.

 

SAPCloud_11

Select the ABAP system as the Back-end type.

 

SAPCloud_12

 

Select the HTTP protocol.

 

SAPCloud_13

 

note_pin

No other protocols are supported for the Bizagi SAP Cloud Platform connector.

 

Register the SAP on-premises system host  URL and port.

 

SAPCloud_14

 

Set the Principal Type as None.

 

SAPCloud_15

 

Define the Virtual Host in the Host In Request Header field.

 

SAPCloud_16

 

Set a description, and click Finish.

 

SAPCloud_17

 

If you select the Check Internal Host you can see if the system is reachable by the Cloud Connector.

 

SAPCloud_18

 

Now created a new Resource.

 

SAPCloud_19

 

Include the OData endpoint of your SAP on-premises system.

 

/sap/opu/odata

 

Select the Path and All sub-paths Access Policy.

 

SAPCloud_20

 

Define the on-premises destination in the Cloud Foundry

The Destination Service in the SAP stores the different configurations of services that you want to access from the Cloud Platform. Therefore, you need to register the information related to your on-premises system.

 

The Cloud Platform administrator must access the cockpit, open the Connectivity module, and select Destinations. Add a New Destination.

 

SAPCloud_22

 

Register the following information:

 

Name: Destination name.

Type: HTTP  (other types are not supported with the Bizagi Sap Cloud Platform Connector)

URL:  URL of the on-premises system Virtual Host with Virtual Port.

Proxy Type: OnPremise

Authentication: BasicAuthentication

User: User name of the on-premises system user.

Password: Password of the on-premises system user.

 

Click Save. After the destination is registered, you can check the connection.

 

SAPCloud_23

 

 

2. Define a new Destination configuration for the SAP system

A Destination in SAP holds the backend system configuration, so the Cloud Platform can have the information access to it. You need to configure a new Destination configuration.  To do that open the Sap Cloud Platform Cockpit, select your sub account, open the Connectivity section and click Destinations. Click New Destination.

 

SAPCloud_24

 

Register the following parameters:

 

Name: name of the new destination. If you have multiple systems, make sure you give a clear name.

Type: Select HTTP as the connection to the on-premises system. The Connectivity service and Cloud Connector use HTTP connections.

Description: Brief description of the destination.

URL: This must be the virtual host of the Cloud Connector (previously configured). See Set the Cloud Connector.

Proxy Type: Select OnPremise.

Authentication: You must select the same authentication defined in the Cloud Connector for OData. Therefore, select the BasicAuthentication option.

User: On-premises SAP user with permissions to access the OData services.

Password: User password.

 

Click Save. Then you can Check the Connection.

 

SAPCloud_25

 

3. Set the Authorization and Trust Service

In the SAP Cloud Platform, select the Cloud Foundry, open the Spaces, and select the Foundry's space.

 

SAPCloud_26

 

Now select the Services module, and click Service Marketplace. Search for the Authorization & Trust Management.

 

SAPCloud_27

 

Create a new instance.

 

SAPCloud_28

 

Select the application Service Plan, and register the instance name as xsuaa-dispatcher. Then click Next.

 

note_pin

If you change the name, review the buildpack manifest.

 

SAPCloud_29

 

In step number two, do not upload any JSON, and leave it empty and click Next. In step three review all the information and click Create Instance. After the instance is created you can review it in the Service Instances menu.

 

SAPCloud_30

 

4. Set the Destination Service

In the same Cloud Foundry, open the Service Marketplace again. Now search the Destination service.

 

SAPCloud_31

 

Create a new instance.

 

SAPCloud_32

 

Select the lite Service Plan and register the Instance Name as destination-dispatcher.

 

note_pin

If you change the name, review the buildpack manifest.

 

SAPCloud_33

 

In step number two, do not upload any JSON, and leave it empty and click Next. In step three review all the information and click Create Instance. After the instance is created you can review it in the Service Instances menu.

 

SAPCloud_34

 

5. Set the Connectivity Service

In the same Cloud Foundry, open the Service Marketplace again. Now search the Connectivity service.

 

SAPCloud_35

 

Create a new instance.

 

SAPCloud_36

 

Select the lite Service Plan and register the Instance Name as connectivity-dispatcher.

 

note_pin

If you change the name, review the buildpack manifest.

 

SAPCloud_37

 

In step number two, do not upload any JSON, and leave it empty and click Next. In step three review all the information and click Create Instance. After the instance is created you can review it in the Service Instances menu.

 

SAPCloud_38

 

6. Install the Router and Buildpack

The buildpack contains a node JavaScript module, that integrates all the services configured previously. This buildpack is developed by Bizagi. This pack must be installed in your SAP Cloud Platform.  Before installing the pack you need the following:

 

Download and unzip the following Bizagi dispatcher file. Download the file here.

Having the Cloud Foundry Command Line Interface installed.  To learn how to install the CLI, click here.

Get the Cloud Foundry URL

Review the buildpack Manifest, and make sure that the names of the services are the same installed in the SAP Cloud Foundry.

 

Get the Cloud Foundry URL

To execute the Command Line Interface (CLI) you need to obtain the Cloud Foundry URL where you are going to install the buildpack. Access the SAP Cloud Platform cockpit, select the sub account.

 

SAPCloud_6

 

Get the API endpoint.

 

SAPCloud_7

 

Open the Cloud Foundry CLI, and login using the following command:

 

cf login -a <URL>

 

Where <URL> is the API endpoint obtained previously.

 

SAPCloud_40

 

You will be asked to register the email and password of a user with admin permissions to the Cloud Foundry. Once authenticated, the command looks as follows.

 

SAPCloud_41

 

 

Review the buildpack manifest

In the folder where you unzip the Bizagi buildpack, you can find the manifest. This manifest is a YAML file that containts the name of the SAP Cloud Foundry services that will be used in the cloud integration.

 

SAPCloud_47

 

Review that the names of the services match with the names registered in the manifest:

 

SAPCloud_48

 

Install the Bizagi buildpack in your SAP Cloud Platform

In the same command prompt, change the directory to the folder where you unzip the Bizagi dispatcher file. And execute the following command.

 

cf push

 

SAPCloud_42

 

Finally, you must see that all instances are started and the build pack in installed correctly.

 

SAPCloud_43

 

Access the Cloud Foundry, in the Spaces section, you must see an application running.

 

SAPCloud_44

 

If you click the Space. You can see the application installed.

 

SAPCloud_45

 

 

Clicking the application you can see the details of the Bizagi application installed in the Cloud Foundry. It is important to save the Application Route.

 

SAPCloud_46

 

Finally you must click the start button, and make sure it is started.

 

SAPCloud_49

 

Next Steps

1.Configure the SAP Cloud Platform connector in Bizagi

2.Set the Bizagi process where you want to execute the SAP action