Consuming SAP Integration Advisor Artifacts

Create and export CI runtime artifacts from IA.

1. In the Mapping screen of the SAP Integration Suite Integration Advisor capability, choose ... → Export → SAP Cloud Integration Runtime Artifacts.

   

2. Find the downloaded zip file on your computer and locate the OData preprocessing, OData to SOAP mapping and SOAP postprocessing files. You will use these next. Alternatively you can also use the IA mapping files in the provided_integration_content folder.

   See the Prerequisites area of this exercise, where to find the files.

   

Consume mapping.

1. Navigate back to your CI tenant and the iFlow PurchaseOrder. To continue, you must be in Edit mode.

2. Select XSLT Mapping from the mapping menu and position it adjacent to the Request Reply process step.

   

3. Connect both process steps as previously shown via drag and drop from Request Reply. Select the XSLT Mapping step and expand the configuration bar from the bottom right. Under General, provide OData PreProcessing as Name.

   

4. Switch to the Processing tab and choose Select to provide a resource. Choose Upload from File System in the bottom-left corner of the Resource screen.

   

5. Locate the OData preprocessing file you previously prepared. If you followed the naming conventions of this course, the file is named OData_source_PO_preproc.xsl.

   

6. Return to the iFlow editor and create another XSLT Mapping from the mapping menu. Position it adjacent to the previous process step. Connect both process steps as previously shown via drag and drop. Select the new XSLT Mapping step and expand the configuration bar from the bottom right. Under General, provide OData to SOAP Mapping as Name.

   

7. Switch to the Processing tab again and choose Select to provide a resource. Choose Upload from File System in the bottom-left corner of the Resource screen. Locate the OData-SOAP mapping file you previously prepared. If you followed the naming conventions of this course, the file is named Mapping_OData_source_PO_to_SOAP_target_PO.xsl.

   

8. Return to the iFlow editor and create another XSLT Mapping from the Mapping menu. Position it adjacent to the previous process step. Connect both process steps as previously shown via drag and drop. Select the new XSLT Mapping step and expand the configuration bar from the bottom right. Under General, provide SOAP PostProcessing as Name.

   

9. Switch to the Processing tab again and choose Select to provide a resource. Choose Upload from File System in the bottom left corner of the resource screen. Locate the SOAP postprocessing file you previously prepared. If you followed the naming conventions of this course, the file is SOAP_target_PO_postproc.xsl.

   

10. Choose Save to secure your progress.

    Please note that instead of manually adding the CI runtime artifacts, they can also be injected automatically from IA. For this, a CI destination must be configured beforehand in your SAP BTP tenant on Cloud Foundry which you created as a prerequisite for this course.

    Note

    At the moment, you can not test this iFlow, because the required End Message event is missing. This will be added in the exercise: Configure Outbound Communication.