Shulou(Shulou.com)06/01 Report--

This article shows you how to carry out SAP CPI analysis, the content is concise and easy to understand, can definitely brighten your eyes, through the detailed introduction of this article, I hope you can get something.

Recently, due to the needs of the project, Jerry has to learn a new tool: SAP Cloud Platform Integration, referred to as CPI, formerly known as HCI-HANA Cloud Platform Integration Service.

Although it is less than 48 hours since Jerry first came into contact with CPI, I still want to share my first-hand experience of using this tool with friends who have used SAP CRM middleware, but I haven't had a chance to get in touch with CPI yet.

The reason why SAP CRM middleware and SAP CPI are associated in the title of the article is that both of them play the role of middleware in system integration in a broad sense.

SAP ERP and CRM synchronize business data through qRFC, while middleware can provide queuing mechanism, error handling, retry, transmission monitoring and other functions. For the sharing of Jerry's work experience on SAP CRM middleware, please refer to my article Jerry's collection of CRM Middleware (middleware) articles.

As the name implies, SAP CPI is a cloud middleware solution for the integration of SAP products and third-party cloud products recommended by SAP in the cloud era. The scenario mentioned in the previous article on the integration of S/4HANA Service Management and SAP Field Service Management by Tong Dan, a colleague of Jerry, is a typical integration application of SAP CPI.

As a study note, Jerry here records a Hello World-level exercise step I did when I was learning SAP CPI.

The scenario for this exercise is to assume that there is an OData service deployed on a third-party cloud platform that provides the ability to query the product master data. We need to consume this OData service in the SAP system. SAP developers do not want to directly consume OData services on third-party cloud platforms, but expect SAP CPI to expose a more accessible API endpoint. For example, after sending a Product ID to CPI,CPI through postman to get the ID, CPI initiates an OData request to the third-party cloud platform. After receiving the request response, CPI returns the result to the consumer end of the SAP product.

OData service address for this scenario: https://espmrefapps.hana.ondemand.com/espm-cloud-web/espm.svc/$metadata

SAP CPI is a SaaS application that is subscribed and accessed in the Subscriptions panel of the SAP cloud platform console. Click Go to Applications to go to the main operation page.

In order to implement this integration scenario, we need to develop an integration stream-integration flow (hereinafter abbreviated as iFlow) in CPI to define what it should do when it receives an incoming product ID from the consumer.

Just as programs in ABAP need to be stored in a development package, iFlow needs to be stored in a package called Content package.

After entering CPI, create a Content package here:

Then click the Artifacts in the figure above to enter the iFlow creation interface:

Name it Jerry first integration flow and click to enter the graphical editing interface of iFlow.

The default interface after a new iFlow is created is as follows:

Click the Sender icon on the far left of the image above and drag it into the Start icon in the integration process rectangle in the middle of the image above. This action will help us create an inbound adapter. We choose HTTPS, which means that the way the iFlow expects it to be consumed is HTTPS.

Maintain a url fragment / CloudIntegrationTrials in the Address of Adapter, and when the iFlow is finally deployed, the generated endpoint ends with this fragment, and then we can use the endpoint to consume the iFlow in tools such as postman.

Considering that popular Restful API implementations expect their consumers to transmit request content in JSON format, we also follow this best practice, so first drag and drop a JSON to XML Converter into a rectangular box in the iFlow integration process modeling area to JSON

The user input in the format is converted to XML format:

Then use Content Modifier to extract the value of product ID in the XML format.

The following figure shows that Content Modifier extracts the value of the productIdentifier field from the input in XML format through XPath.

With product ID, you can make OData calls. Drag an External Call from the iFlow modeling toolbox:

Select the type as OData V2:

Specify the url of the OData service mentioned earlier:

Select the Products node of the OData service as the object of consumption:

Bind the ProductId field of the OData Product node to the productIdentifier field that contains the user input parsed through Content Modifier in the previous step.

Just like children building blocks, we combine the elements provided in the iFlow toolbox into a graphical process by dragging and dropping. Click Deploy to deploy:

After the deployment is successful, copy down the generated endpoint:

Send a GET request to the endpoint in Postman:

After the CPI iFlow deployed on SAP Cloud Platform receives the request, it parses the Product ID according to the logic maintained by us, invokes the OData service, and returns the Product details of the ID to the consumer as a result.

Just as SAP CRM middleware has various monitoring applications accessed through transaction codes such as SMW01, SAP CPI has similar monitoring programs:

The above content is how to analyze SAP CPI. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.