In this exercise, we will create and migrate a SOAP to REST scenario. For this particular scenario, not all attributes of the ICO on SAP Process Orchestration could be mapped to the parameters in the integration flow on Cloud Integration, so a couple of manual adjustments will need to be carried out which we will do as a part of the exercise.
-
Open your previously created package, and switch to the Artifacts tab, then switch to Edit Mode.
-
Configure the SAP Process Orchestration system as before. For this expand the Name section and choose your system. Lastly, click Next Step to proceed with configuring the scenario.
-
Click on Show Filters and fill in “http://pi-elevation.bootcamp.com“ for Namespace. Choose the interface “SI_Employee_Out” from the drop-down list. Click Next Step.
-
The template “P2P_SYNC_JSON_REC_0001” should already be selected. Click Next Step.
-
Maintain a Name for your integration flow, e.g., following the pattern soap_to_rest_sync_<userxx> where xx is your user number from 00 to 99. Then, click on Review.
-
Again, the integration flow will be generated within your integration package. As you can see from the summary page, the REST receiver adapter on SAP Process Orchestration has been mapped to the HTTP adapter in Cloud Integration. Click on View Artifact to take a closer look.
-
For this particular scenario, not all attributes of the ICO on SAP Process Orchestration could be mapped to the parameters in the integration flow on Cloud Integration, so a couple of manual adjustments need to be carried out.
Note, the attribute mapping will be improved with future increments of the migration tool so that manual interaction is reduced to a bare minimum.
Click on Configure -
Switch to tab More and select "XML to JSON Converter" as Type.
-
Enable "Suppress JSON Root Element" make sure the "Use Namespace Mapping" is not checked and press Save.
-
Press Close to close the Message box and close the configure Pop-Up as well.
-
Add the Namespace Mapping “xmlns:ns0=http://pi-elevation.bootcamp.com” in the Runtime Configuration of the integration flow.
-
In the HTTP connection of the “Request Reply”, verify that the Authentication is set to “Basic”. The credential name is automatically mapped from the REST receiver adapter on SAP Process Orchestration. This needs to be changed to the credential name maintained on the tenant, here maintain the Credential Name “PIMAS_Demo”.
-
Next, click on the JSON to XML Converter and switch to the Processing details. Enter “MT_Employee_RESP” as <b<Name and select the namespace you created earlier.
-
You can check the deployment status via the monitor dashboard. Navigate to Monitor > Integrations, and select the Manage Integration Content tile.
-
Your integration flow should be in status Started. From here, you get the endpoint that you need to call to test the scenario. Copy the endpoint as we will use it in the next step.
-
Open Insomnia and duplicate the Request you created in exercise 2.
-
Replace the URL with the endpoint of your new integration flow.
-
Replace the XML Payload to following value:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:pi="http://pi-elevation.bootcamp.com">
<soapenv:Header />
<soapenv:Body>
<pi:MT_Employee_REQ>
<employee_name>John Doe 124</employee_name>
<employee_salary>320800</employee_salary>
<employee_age>60</employee_age>
<profile_image></profile_image>
</pi:MT_Employee_REQ>
</soapenv:Body>
</soapenv:Envelope>
You've now successfully completed the migration assessment and migrated scenarios from PI/PO to SAP Integration Suite using the migration assessment and migration capability of SAP Integration Suite.