Creating a Cloud Integration IFLOW using an HTTP flow Connector to SAP Gateway System On-Premise. - SAP Cloud Integration (2023)

Purpose

This WiKi will show howhow to create an IFLOW and a HTTP Connector and connect to an SAP Gateway Systemto retrieve Data from the Gateway Services.

Overview

Creating an HTTP Flow Connection thru an SAP Cloud Connector to an SAP Gateway System to Read Data from the Gateway Services Flight. This can lead to other
development to consume other Gateway Services.

Prerequisites

• Access to Flights Service in the SAP Gateway Server.
• SAP Cloud Neo, For Cloud Connector to connect to.
• SAP Cloud Integration IFLOW.
• Cloud Connector Configuration please refer to the WIKI Post
  https://wiki.scn.sap.com/wiki/x/2AW0Ig

Step 1 Creating Login reference.

The user credentials(username/password) need to be provisioned to connect to SAP Gateway Server thru Cloud Connector.

1-1 Login to Integration tenant and go to Manage Security as illustrated below.

1-2 From the Menu select Create and then select User Credentials.

Figure 2 Menu option to create User Credentials.

1-3 A popup screen prompts for Create User Credentials. The Name can be anything in this case Name is set to “GW1”
and Description as “SAP Gateway Server”. The authentication Type is set to “User Credentials” with User and Password.

Figure 3 Creating our USER ID and Password Reference GW1.

The following steps to create the IFLOW.

Step 2: Creating an IFLOW.

Figure 4 The Main Screen of the Cloud Platform Integration.

2-1 Login to you Tenant and go to the main screen.
2-2 Select the Pencil.

Figure 5 Find your Container or create one to store your IFLOWS.

Figure 6 Here is the Screen show other IFLOW Project We can create IFLOWS.

2-5 From the pull-down Menu Select Add.
2-6 Select Integration Flow.

Figure 7 Steps to create our IFLOW Project.

After clicking Integration Flow there will be a popup

Figure 8 Adding an Integration IFLOW giving it a unique name.

Figure 9 Showing the created IFLOW.

Now our project IFLOW is created to open click on ABAP_HTTP.

Figure 11 Deleting the Start and replace with a Timmer.

Figure 12 Steps to add a Timmer to the Project.

2-12 From the Menu select the Target Icon.
2-13 Scroll down and select Timer.
2-14 Drag and drop the Timer on the IFLOW.
2-15 Select The timer connector the line with the Arrow.

Figure 13 Clicking on the Arrow to connect to the End Flow.

2-16 Drag the arrow to the End Icon.

Figure 14 Now the timer is connected to the End Event or End Process.

In the next step will need to add a Request Response Flow to our IFLOW.
Files
2-17 From the menu Bar select the right and left arrow icon this is call
scroll down and select External Call.

Figure 15 This the Parent menu External Call Flow.

2-18 When selecting External call open it.
2-19 Then from the sub menu select Request Reply.

Figure 16 Showing the Sub Menu of the External call here we select Request Reply Flow.

2-20 Drag and drop the Request Reply on to the IFLOW

Your IFLOW should look like Figure 17.

Figure 19 All connectors need a Reference Protocol In the case HTTP.

2-23 Select HTTP.

Figure 20 The Request Reply is now connected to the Receiver and will use HTTP.

2-25 Go to the Connection.
2-26 We need to add the following.
2-27 Address Your HTTP URL that points to a Cloud Connector.
2-28 Proxy Type change to On-Premise.
2-29 Location ID is a reference to the Location ID of the cloud Connector.
2-30 Method select GET.
2-31 Authentication Select Basic Auth.
2-32 Credential Name this the predefined Credential Add GW1.
2-33 For the Request Header add an asterisk.
2-34 For the Response Header add an asterisk.

Figure 22 populating the Connections.

2-35 click Save

Your IFLOW should look like this.

Figure 23 Completed IFLOW.

Step 3 Adding Groovy Script to Log the IFLOW HTTP Request.

Figure 24 Show how to add a Flow the Project in this case we are adding a Groovy Script.

3-4 Select the Create Icon, this action will bring up the Groovy Script Editor.

Figure 25 Creating the Groovy Script

3-3 Replace the default content with the following Groovy Script for creating a log file.

import com.sap.gateway.ip.core.customdev.util.Message;

import java.util.HashMap;

def Message processData(Message message)

{

def body = message.getBody(java.lang.String) as String;

def messageLog = messageLogFactory.getMessageLog(message);

if(messageLog != null)

{

messageLog.setStringProperty("log1","Printing Payload As Attachment")

messageLog.addAttachmentAsString("log1",body,"text/plain");

}

return message;

}

The Groovy Script should look like the Following Screen in Figure 26..

Figure 26 Groovy Script editor

3-4 Click Ok to save.

Step 4 Deploying the IFLOW.

The IFLOW configuration is completed we now need to deploy the IFLOW

4-1 From Menu top right select Deploy

Step 4

The IFLOW configuration is completed we now need to deploy the IFLOW

4-1 From Menu top right select Deploy

Figure 28 Menu to Deploy.

Your will get a pop message.

Figure 29 Pop Menu asking if you want to deploy.

4-2 Select Yes

The Next screen

Figure 30 Finial message Successful Deployment.

Figure 31 Select the Operate and Monitor.

4-3 Click Ok.

Next

4-4 Select the Eye Icon top Lest.

Next

4-5 Select the Manage Integration Content Tile.

Figure 32 The Main Integration menu.

Figure 33 Showing the Deployed IFLOW ABAP_HTTP.

From the Menu

4-6 Go to Artifact Details.
4-7 Click on Monitor Message Processing.

After clicking on Monitor Message Processing.

You will see the next Screen.

Figure 34 Reviewing the logs.

From the meu we can see the LOG and the LOG1.

The Log was created during the deployment of the IFLOW.

The Log1 Is the log that was created by the Groovy.

4-8 Select the Open Text View.

Figure 35 Deployment Log

The our put of the successful deployment.

4-8 form the same screen select Log1.

You will notice that the output is a continues string
to see the details in a better format simply download the file.

Figure 36 Groovy Script Log1 out put.

4-9 Select Down load.

After downloading the log1 out put
open the file with a text utility like Note pad or Note Pad ++.

4-10 Open the file.

Figure 37 The Downloaded file.

The Log1 out put clearing is connecting and has sent a query to the SAPGateway Server.

Summary

This document explained in detail how to setup an HTTP connection thru the SAP Cloud Connector to the
SAP Gateway Server On-Premise. The development of an IFLOW Consume Flights Data, As described the steps are very easy and can help to improve future development consideration.
As demonstrated the IFLOW can use HTTP as well as an ODATA Connect to connect and query Data from the SAP Gateway System.
As with any project testing should be done before fully implementing and deploying, also make necessary changes if needed.
Connection using HTTP through the Cloud Connector works very well in this environment and will provide an easy integration to an on-premise SAP Gateway System.

Setting up Cloud Connector to an On-Premise SAP Gateway System to connect SAP Cloud Integration - SAP Cloud Integration - Community Wiki.

Connecting to SAP Gateway Server to consume ODATA data from SAP Cloud Integration iFlow.