If you are just stepping into SAP BTP Integration Suite (Formerly known as CPI), this guide is for you. We will walk through creating a simple iFlow that- accepts HTTP request, logs the incoming messages, sends back a static response.
What is an iFlow ?
So let us understand first what is an iFlow and components of an iFlow.
An iFlow defines how data is moving from one system to another, it’s like a visual blueprint where we can connect, transforms and routes messages between application.
Prerequisites:
SAP BTP Global account (link- https://account.hana.ondemand.com/#/home/welcome)
Access to SAP Integration Suite (formerly known as CPI)We need “IntegrationDeveloper” and other roles as per our requirement.
Step-by-Step guide how to create an iFlow.
Step 1: Log in to SAP Integration Suite
Go to SAP BTP CockpitNavigate to your Subaccount > Instance and Subscription (Check if Integration suite is subscribed or not, if not then we have to subscribe)
Step 2: Create a New Integration Flow (iFlow)
Open Integration Suite (Click on Integration Suite)
Go to Design tab (1)
Integration and APIs (2)
Click on Create (3) (It will create a Package)
Package– A package is a container where we can group together related integration artifacts to organize and manage them as a cohesive unit. Like- iFlows, value mapping, and scripts.In Header part give – (Name>Technical name>Short Description) > Save
Go to Artifacts > Add > Select -Integration Flow.
Give Name > ID > Runtime Profile > Description > Click on Add
Now we successfully created an iFlow under the package “Simple_iFlow”.
Step-3: Design the iFlow
First click on the created iFlow—✔️
We can see one Sender, one Receiver out of the box and inside the box Start and End message.
Start Event:
Click on Edit > Drag and drop a connection from ‘Sender’ to ‘Start’ message > choose ‘HTTPS’ Click on Connection and Configure: Connection: ‘Address’— ‘/simpletest’, ‘Authorization:’ ‘User Role’, ‘User Role:’ ‘ESBMessaging.send’Click on Save.
Add a Content Modifier— A content modifier enables users to modify message headers, properties, and payload. We can find it under Message Transformer option. Place the content modifier between ‘Start’ and ‘End’.
Configure —- Message Body > Keep type as ‘constant’ and in Body we can give payload, as given in the screenshot (We can add any message as per wish in the Body section of the content modifier).
Click on Save.Now we need a “Request Reply” to send the message to an external system (i.e Receiver) and we use it for getting a response from external system before proceeding. Go to Call > External Call > Select Request Reply
Now we will bring the Receiver below the Request Reply (Just for proper alignment) and we are making a connection with the Receiver using HTTP type.
From drop down expand the HTTP connection after selecting, and provide details like—
In Connection—
Address- (Provide the address from where we want to fetch the data)
Proxy Type- Internet, Method- Post, Authentication- None.
Now connect the End with Request Reply to complete the iFlow. The final iFlow looks like this–
Step-4: Save and deploy the iFlow
In the first step Save the created iFlow and click on Deploy button.
After clicking on the Deploy button we can see this option–
Click on Yes and then Ok we will get success message if the iFlow is successfully deployed.
Step-5: Testing the iFlow
We can test the iFlow in different ways, mainly we will test if we are getting the message which we are sending.
Open a new integration suite.
Go to Monitor> Integrations and APIs > Manage Integration Content (Click)
Here we can find our deployed iFlow name and its status, deployment success message and the iFow end point which is very much important. We can change our log configuration from info to trace and re-deploy to check how much information is logged during the execution of an integration suite.
Copy the iFlow end point and now we will test in Postman. Before we proceed, we need to setup the postman and we have to create new request. Make the request as Post and paste the iFlow endpoint in the marked place.
Set Authorization as Basic Authentication, we have to give our logging credentials, like –username and password for authentication.
In Body select raw-Json data and give a message payload. The sample payload is-
{
“message”: “Test from Postman”,
“data”: “Sample data”
}
Now we will send the request and if we get 200 OK success messages then the request is successful, and we are getting the message.
Now go to the Integration Suite > Monitor > Integration and APIs > Monitor message processing-— here we can see 1 message as we send the POST request in Postman using the iFlow endpoint.
Open the Monitor Message Processing and we can find the status and processing time taken by the iFlow to execute and message processing completed successfully or not.
Now if we want to see the iFlows response directly we have to do little modifiction in the iFlow.
Edit the iFlowRemove the HTTP receiver connectionConnect the content modifier directly to the end event.Save and deploy.
Now copy the iFlow end point and send the Post request in Postman, we will get the same format of payload which we gave in the content modifier body.
Conclusion:
Creating your first iFlow in SAP BTP Integration Suite might seem difficult initially, but as we can see it’s straight forward once you understand the basics. This step-by-step guide covered all the essential concepts from package creation to testing and troubleshooting.
#SAPIntegrationSuite #SAPBTP #iFlow #CloudIntegration #SAP #API #Postman
Did the blog help you? Please like, share, and leave a comment with your thought and questions. Your feedback helps me create better content for the community!
If you are just stepping into SAP BTP Integration Suite (Formerly known as CPI), this guide is for you. We will walk through creating a simple iFlow that- accepts HTTP request, logs the incoming messages, sends back a static response.What is an iFlow ?So let us understand first what is an iFlow and components of an iFlow.An iFlow defines how data is moving from one system to another, it’s like a visual blueprint where we can connect, transforms and routes messages between application.Prerequisites:SAP BTP Global account (link- https://account.hana.ondemand.com/#/home/welcome)Access to SAP Integration Suite (formerly known as CPI)We need “IntegrationDeveloper” and other roles as per our requirement.Step-by-Step guide how to create an iFlow.Step 1: Log in to SAP Integration SuiteGo to SAP BTP CockpitNavigate to your Subaccount > Instance and Subscription (Check if Integration suite is subscribed or not, if not then we have to subscribe) Step 2: Create a New Integration Flow (iFlow)Open Integration Suite (Click on Integration Suite)Go to Design tab (1)Integration and APIs (2)Click on Create (3) (It will create a Package) Package– A package is a container where we can group together related integration artifacts to organize and manage them as a cohesive unit. Like- iFlows, value mapping, and scripts.In Header part give – (Name>Technical name>Short Description) > SaveGo to Artifacts > Add > Select -Integration Flow.Give Name > ID > Runtime Profile > Description > Click on AddNow we successfully created an iFlow under the package “Simple_iFlow”. Step-3: Design the iFlowFirst click on the created iFlow—✔️We can see one Sender, one Receiver out of the box and inside the box Start and End message.Start Event: Click on Edit > Drag and drop a connection from ‘Sender’ to ‘Start’ message > choose ‘HTTPS’ Click on Connection and Configure: Connection: ‘Address’– ‘/simpletest’, ‘Authorization:’ ‘User Role’, ‘User Role:’ ‘ESBMessaging.send’Click on Save.Add a Content Modifier– A content modifier enables users to modify message headers, properties, and payload. We can find it under Message Transformer option. Place the content modifier between ‘Start’ and ‘End’. Configure —- Message Body > Keep type as ‘constant’ and in Body we can give payload, as given in the screenshot (We can add any message as per wish in the Body section of the content modifier).Click on Save.Now we need a “Request Reply” to send the message to an external system (i.e Receiver) and we use it for getting a response from external system before proceeding. Go to Call > External Call > Select Request ReplyNow we will bring the Receiver below the Request Reply (Just for proper alignment) and we are making a connection with the Receiver using HTTP type.From drop down expand the HTTP connection after selecting, and provide details like— In Connection—Address- (Provide the address from where we want to fetch the data)Proxy Type- Internet, Method- Post, Authentication- None.Now connect the End with Request Reply to complete the iFlow. The final iFlow looks like this–Step-4: Save and deploy the iFlowIn the first step Save the created iFlow and click on Deploy button.After clicking on the Deploy button we can see this option–Click on Yes and then Ok we will get success message if the iFlow is successfully deployed. Step-5: Testing the iFlowWe can test the iFlow in different ways, mainly we will test if we are getting the message which we are sending.Open a new integration suite. Go to Monitor> Integrations and APIs > Manage Integration Content (Click) Here we can find our deployed iFlow name and its status, deployment success message and the iFow end point which is very much important. We can change our log configuration from info to trace and re-deploy to check how much information is logged during the execution of an integration suite.Copy the iFlow end point and now we will test in Postman. Before we proceed, we need to setup the postman and we have to create new request. Make the request as Post and paste the iFlow endpoint in the marked place.Set Authorization as Basic Authentication, we have to give our logging credentials, like -username and password for authentication.In Body select raw-Json data and give a message payload. The sample payload is-{ “message”: “Test from Postman”, “data”: “Sample data”}Now we will send the request and if we get 200 OK success messages then the request is successful, and we are getting the message. Now go to the Integration Suite > Monitor > Integration and APIs > Monitor message processing— here we can see 1 message as we send the POST request in Postman using the iFlow endpoint.Open the Monitor Message Processing and we can find the status and processing time taken by the iFlow to execute and message processing completed successfully or not.Now if we want to see the iFlows response directly we have to do little modifiction in the iFlow. Edit the iFlowRemove the HTTP receiver connectionConnect the content modifier directly to the end event.Save and deploy.Now copy the iFlow end point and send the Post request in Postman, we will get the same format of payload which we gave in the content modifier body.Conclusion:Creating your first iFlow in SAP BTP Integration Suite might seem difficult initially, but as we can see it’s straight forward once you understand the basics. This step-by-step guide covered all the essential concepts from package creation to testing and troubleshooting.#SAPIntegrationSuite #SAPBTP #iFlow #CloudIntegration #SAP #API #PostmanDid the blog help you? Please like, share, and leave a comment with your thought and questions. Your feedback helps me create better content for the community! Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
