Skip to content

Latest commit

 

History

History
117 lines (76 loc) · 6.62 KB

README.md

File metadata and controls

117 lines (76 loc) · 6.62 KB

Exercise 2 - Migrate and Test SOAP to SOAP Scenario

After having finished the assessment of the current SAP Process Orchestration landscape and having estimated the effort needed to migrate with the Migration Assessment capability, the next step is the actual migration. The goal of the Migration Tool is to provide a semi-automated migration where interfaces in Cloud Integration will be automatically created so ideally 60-70% of technical migration efforts are automated. The migration of scenarios is based on a template approach, which means that integration flow templates are used as a skeleton to migrate the content and create the final integration flows.

Create a Cloud Integration package

As a prerequisite, you first need to create an integration package where the automatically generated integration flows are created and then we will migrate SOAP to SOAP interface.

  1. Switch back to the SAP Integration Suite landing page.

  2. Navigate to Design > Integrations, and select Create.

  3. Fill in the Name, e.g. Demo_<userxx> where xx is your user number from 00 to 99, and a short description eg . Then click Save.

Migrate SAP Process Orchestration Artifacts (SOAP to SOAP scenario)

Every ICO that can be migrated has an associated template in the migration tooling. It's based on these templates, the migration tooling creates equivalent integration flows in the SAP Integration Suite. Let's start with the actual migration.

  1. In the package you just created, you should be already in Edit mode. If not, on the top right click Edit.
    image

  2. Switch to tab Artifacts and click on Migrate to start the migration wizard.

  3. Select the SAP Process Orchestration system for which the assessment was previously done. For this, expand the Name section and select your system from the drop-down menu. Click Next Step to proceed with configuring the scenario.

  4. Currently, only Integrated Configuration Objects (ICO) are supported. You can use the filter to filter out the list of ICOs and choose the appropriate scenario. Click on Show Filters and fill in “http://pi-elevation.bootcamp.com“ as Namespace. Choose the interface “SI_NumberConversion_Out” from the drop-down list. Click Next Step.
    image

  5. The best-fit template is identified by the migration framework and will be automatically filled in for you. In this case, it will be “P2P_SYNC_0001”. Click Next Step.

  6. Maintain any Name for your integration flow, e.g. following the pattern: soap_to_soap_sync_<userxx> where xx is your user from 00 to 99. Note, that the ID of your integration flow needs to be unique across all integration flows on the tenant. Click on Review.

  7. Verify the information and then click on Migrate.

  8. A new integration flow has been generated within your package. Click on the artifact to take a closer look at each individual step. The required information is automatically populated such as the connection information. Click on View Artifact.
    image

Deploy migrated artifacts

After completing these steps you will be able to deploy the Integration flow and monitor your scenario

  1. Click on the SOAP Adapter and view the Connection details. You can see that the endpoint address has been automatically set based on the integration flow name that you have entered.

  2. For this particular scenario, no manual steps need to be carried out. It should run as is. Select Deploy to get the integration flow deployed on the tenant runtime.

  3. You can check the deployment status via the monitor dashboard. Navigate to Monitor > Integrations, and select the Manage Integration Content tile.

  4. 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.

Now you are all set to test your scenario!

Verify the Interface via Insomnia

After completing these steps you will be able to test the interface and get the desired result of converting a number into a text.

  1. Open Insomnia and click on Use the local Scratch Pad

    image

  2. Create a New HTTP-Request.
    image

  3. Change the Request Method from GET to POST, by clicking the dropdown icon next to GET.

    image

  4. Paste the endpoint from you integration flow as URL.

    image

  5. Add a Body of type XML.


    image

  6. Provide following payload:

<soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:pi="http://pi-elevation.bootcamp.com">
  <soapenv:Header />
  <soapenv:Body>
      <pi:MT_NumberConversion_REQ>
          <number>1389</number>
      </pi:MT_NumberConversion_REQ>
  </soapenv:Body>
</soapenv:Envelope>


image

  1. Switch to tab Auth and choose Basic Auth
    image

  2. Provide following credentials:
    Username: sb-f6c12e3b-5fb8-43b5-8b73-94a86058e8be!b212998|it-rt-asug23-01!b56186
    Password: c44f99a4-2bf3-4512-b8dc-eca19ee92904$VD-H8nyOnEr4TywlCMPUhDmkC6aQZXL9soJeLHLpwIk=
    image

  3. Press Send. The request should return HTTP code 200 and a response with the converted text.
    image

Summary - Congratulations You have successfully tested your scenario now.

Continue to - Exercise 3 - Migrate and Test SOAP to REST Scenario