Blog 10: Importing PI content in Integration Flows
In this blog, we shall look at a connecting link between the on-premise Process Orchestration and SAP Cloud Platform Integration (f.k.a HCI). Although, it is a goal to run on-premise based integrations on SAP Cloud Platform Integration, we started with the first step – mappings. On our discussions with customers and partners, we realised that mappings are one of the most important business asset that consultants wanted to reuse.
We support downloading the artifacts from Process Orchestration version 7.10 and above.
How to import artifacts from Process Orchestration ?
Downloading Message Mappings
Step 1: Configure the settings to the Enterprise Service Repository (ESR) from the Eclipse tool-set
Step 2: From the integration project, click on Import PI content. You can import Message mappings, Operation mappings, and WSDLs.
Let’s talk about the example of downloading a message mapping. We want to re-use a message mapping in our integration flow project of SAP Cloud Platform Integration. You have to select it from the wizard. The mappings are then downloaded in a SAP Cloud Platform Integration – native format.
Check the file format – It has been downloaded as an .mmap file. You can then edit the downloaded mappings using the mapping editors.
- WSDLs/XSDs corresponding to Message Types and Fault Message Types are placed under src.main.resources.mapping folder
- Other interfaces get placed under src.main.resources.wsdl
Downloading Operation Mappings
Operation mappings have a slightly unique behaviour. They can currently downloaded only as a .jar file. The functionality of the operation mapping can be used, but you cannot modify the mapping in SAP Cloud Platform Integration.
The imported operation mapping has the following features:
- If operation mapping contains message mapping, then the message mapping is downloaded as a jar under src.main.resources.mapping package
- If the operation mapping contains XSLTs, then the files are downloaded as .xsl under src.main.resources.mapping
- Imported source or target WSDLs are not supported in integration flows
Note: There are certain restrictions in downloading the mappings. We remove them as time goes. The limitations are documented in the guide; so, do make a check on the documentation from time-to-time.
Process Orchestration customers who are adopting SAP Cloud Platform Integration could do well to reuse the mapping components. Before the start of a project, check if the interfaces and mappings have already been defined in Process Orchestration. Message mappings are more easily imported into SAP Cloud Platform Integration. You can also modify them and adapt them in the project.
Do you mean we can import ESR content from PI7.10 and above?
That is correct! However, do note - not all ESR content, but quite a few.
If you have xslt maps written outside of / not used in PI, can these be used/imported into an HCI flow?
I need to export HCI content into SAP PO. what can I do for it or which steps I should follow.
Did you tried deploying onto SAP PO Server using NWDS? In the latest versions, we have an option to deploy the Cloud Integration Content ( Integration content), see this screenshot.