sap-tutorials · jmmargo · Jun 5, 2023 · Jun 5, 2023 · Jun 5, 2023
diff --git a/.gitignore b/.gitignore
@@ -48,4 +48,3 @@ Thumbs.db
 # VSCode specific files
 *.vr
 *.code-workspace
-
diff --git a/tutorials/migration-assessment-enablement/Images/CapabilityOverview_1.png b/tutorials/migration-assessment-enablement/Images/CapabilityOverview_1.png
diff --git a/tutorials/migration-assessment-enablement/Images/CapabilityOverview_2.png b/tutorials/migration-assessment-enablement/Images/CapabilityOverview_2.png
diff --git a/tutorials/migration-assessment-enablement/Images/CapabilityOverview_3.png b/tutorials/migration-assessment-enablement/Images/CapabilityOverview_3.png
diff --git a/tutorials/migration-assessment-enablement/Images/CapabilityOverview_4.png b/tutorials/migration-assessment-enablement/Images/CapabilityOverview_4.png
diff --git a/tutorials/migration-assessment-enablement/Images/CapabilityOverview_5.png b/tutorials/migration-assessment-enablement/Images/CapabilityOverview_5.png
diff --git a/tutorials/migration-assessment-enablement/Images/Step2AssignRoleCollection_1.png b/tutorials/migration-assessment-enablement/Images/Step2AssignRoleCollection_1.png
diff --git a/tutorials/migration-assessment-enablement/Images/Step2AssignRoleCollection_1_1.png b/tutorials/migration-assessment-enablement/Images/Step2AssignRoleCollection_1_1.png
diff --git a/tutorials/migration-assessment-enablement/migration-assessment-enablement.md b/tutorials/migration-assessment-enablement/migration-assessment-enablement.md
@@ -0,0 +1,78 @@
+---
+author_name: Sriprasad S Bhat
+author_profile: https://github.com/vishu2804
+parser: v2
+auto_validation: true
+time: 10
+tags: [  software-product>sap-integration-suite, software-product>cloud-integration, software-product>sap-process-integration, software-product>sap-process-orchestration, tutorial>license, tutorial>beginner  ]
+primary_tag: software-product>sap-integration-suite
+---
+
+
+# Enable Migration Assessment Application
+<!-- description --> Learn how to enable the Migration Assessment Application, a new capability of SAP Integration Suite. With the Migration Assessment Application, you can assess your existing SAP Process Orchestration landscape before starting the migration to the SAP Integration Suite.
+
+## Prerequisites
+
+- You’ve set up your global account and at least one subaccount on SAP BTP. See [Getting Started in the Cloud Foundry Environment](https://help.sap.com/docs/btp/sap-business-technology-platform/getting-started-in-cloud-foundry-environment).
+- You’re subscribed to SAP Integration Suite in your subaccount. See [Subscribing to SAP Integration Suite](https://help.sap.com/docs/integration-suite/sap-integration-suite/8a3c8b7a6b1c4f249bb81d11644ef806.html).
+
+## You will learn
+- How to enable the Migration Assessment Application
+
+---
+### Enable Migration Assessment capability
+
+1. Navigate to the **SAP Integration Suite** home page and choose **Manage Capabilities**.
+
+    <!-- border -->![Image](Images/CapabilityOverview_1.png)
+
+2. Choose **Add Capabilities**.
+
+    <!-- border -->![Image](Images/CapabilityOverview_2.png)
+
+3. Select **Assess Migration Scenarios**. Then choose **Next** and **Activate** to proceed with the activation of the capability.
+
+    <!-- border -->![Image](Images/CapabilityOverview_3.png)
+
+    <!-- border -->![Image](Images/CapabilityOverview_4.png)
+
+
+    Wait until the capability is enabled. Refresh your page to see the successfully activated capability.
+
+    <!-- border -->![Image](Images/CapabilityOverview_5.png)
+
+---
+### Assign role collection to user
+
+In Migration Assessment, there are two role collections that cover different personas and responsibilities:
+
+- The **PIMAS_Administrator** performs administrative tasks, like configuring system settings.
+- The **PIMAS_IntegrationAnalyst** performs executive tasks, like reading and running evaluations as well as downloading results. 
+
+
+1. In your subaccount, navigate to **Security** and then to **Users**.
+
+2. Select your user and choose **Assign Role Collection**.
+
+    <!-- border -->![Image](Images/Step2AssignRoleCollection_1_1.png)
+
+3. Select the role collection relevant for your user, then choose **Assign Role Collection**.
+
+    <!-- border -->![Image](Images/Step2AssignRoleCollection_1.png)
+
+
+To get a detailed overview of the role templates and role collections users need to accomplish the various tasks related to Migration Assessment, see [Tasks and Permissions](https://help.sap.com/docs/integration-suite/sap-integration-suite/2714db1701114de4ab5ffd1bebd0c4de.html).
+
+Once you're done, you're all set to access and configure the Migration Assessment application.
+
+### Test yourself 
+
+
+
+
+
+
+
+
+---
diff --git a/tutorials/migration-assessment-enablement/rules.vr b/tutorials/migration-assessment-enablement/rules.vr
@@ -0,0 +1,15 @@
+
+[VALIDATE_3]
+###Rule
+multiple-choice
+
+###Question
+Which role collections are required to enable Migration Assessment capability?
+
+###Match
+[X] PIMAS_Administrator
+[ ] PI_Administrator
+[X] PIMAS_IntegrationAnalyst
+[ ] PI_Integration_Developer
+
+[VALIDATE_3]
diff --git a/tutorials/migration-assessment/Images/2023-01-23_23-54-52.jpg b/tutorials/migration-assessment/Images/2023-01-23_23-54-52.jpg
diff --git a/tutorials/migration-assessment/Images/Picture1.png b/tutorials/migration-assessment/Images/Picture1.png
diff --git a/tutorials/migration-assessment/Images/Picture10-1.png b/tutorials/migration-assessment/Images/Picture10-1.png
diff --git a/tutorials/migration-assessment/Images/Picture11-1.png b/tutorials/migration-assessment/Images/Picture11-1.png
diff --git a/tutorials/migration-assessment/Images/Picture12-2.png b/tutorials/migration-assessment/Images/Picture12-2.png
diff --git a/tutorials/migration-assessment/Images/Picture13-1.png b/tutorials/migration-assessment/Images/Picture13-1.png
diff --git a/tutorials/migration-assessment/Images/Picture14-1.png b/tutorials/migration-assessment/Images/Picture14-1.png
diff --git a/tutorials/migration-assessment/Images/Picture15-1.png b/tutorials/migration-assessment/Images/Picture15-1.png
diff --git a/tutorials/migration-assessment/Images/Picture16-1.png b/tutorials/migration-assessment/Images/Picture16-1.png
diff --git a/tutorials/migration-assessment/Images/Picture17-2.png b/tutorials/migration-assessment/Images/Picture17-2.png
diff --git a/tutorials/migration-assessment/Images/Picture18-1.png b/tutorials/migration-assessment/Images/Picture18-1.png
diff --git a/tutorials/migration-assessment/Images/Picture19-1.png b/tutorials/migration-assessment/Images/Picture19-1.png
diff --git a/tutorials/migration-assessment/Images/Picture2.png b/tutorials/migration-assessment/Images/Picture2.png
diff --git a/tutorials/migration-assessment/Images/Picture20-1.png b/tutorials/migration-assessment/Images/Picture20-1.png
diff --git a/tutorials/migration-assessment/Images/Picture21-1.png b/tutorials/migration-assessment/Images/Picture21-1.png
diff --git a/tutorials/migration-assessment/Images/Picture22-1.png b/tutorials/migration-assessment/Images/Picture22-1.png
diff --git a/tutorials/migration-assessment/Images/Picture25.png b/tutorials/migration-assessment/Images/Picture25.png
diff --git a/tutorials/migration-assessment/Images/Picture26.png b/tutorials/migration-assessment/Images/Picture26.png
diff --git a/tutorials/migration-assessment/Images/Picture27.png b/tutorials/migration-assessment/Images/Picture27.png
diff --git a/tutorials/migration-assessment/Images/Picture28.png b/tutorials/migration-assessment/Images/Picture28.png
diff --git a/tutorials/migration-assessment/Images/Picture29.png b/tutorials/migration-assessment/Images/Picture29.png
diff --git a/tutorials/migration-assessment/Images/Picture3.png b/tutorials/migration-assessment/Images/Picture3.png
diff --git a/tutorials/migration-assessment/Images/Picture30.png b/tutorials/migration-assessment/Images/Picture30.png
diff --git a/tutorials/migration-assessment/Images/Picture31.png b/tutorials/migration-assessment/Images/Picture31.png
diff --git a/tutorials/migration-assessment/Images/Picture32.png b/tutorials/migration-assessment/Images/Picture32.png
diff --git a/tutorials/migration-assessment/Images/Picture33.png b/tutorials/migration-assessment/Images/Picture33.png
diff --git a/tutorials/migration-assessment/Images/Picture34.png b/tutorials/migration-assessment/Images/Picture34.png
diff --git a/tutorials/migration-assessment/Images/Picture35.png b/tutorials/migration-assessment/Images/Picture35.png
diff --git a/tutorials/migration-assessment/Images/Picture36.png b/tutorials/migration-assessment/Images/Picture36.png
diff --git a/tutorials/migration-assessment/Images/Picture37.png b/tutorials/migration-assessment/Images/Picture37.png
diff --git a/tutorials/migration-assessment/Images/Picture4-4.png b/tutorials/migration-assessment/Images/Picture4-4.png
diff --git a/tutorials/migration-assessment/Images/Picture4.png b/tutorials/migration-assessment/Images/Picture4.png
diff --git a/tutorials/migration-assessment/Images/Picture5.png b/tutorials/migration-assessment/Images/Picture5.png
diff --git a/tutorials/migration-assessment/Images/Picture8-1.png b/tutorials/migration-assessment/Images/Picture8-1.png
diff --git a/tutorials/migration-assessment/migration-assessment.md b/tutorials/migration-assessment/migration-assessment.md
diff --git a/tutorials/migration-tool/Images/2023-04-20_10-11-24.png b/tutorials/migration-tool/Images/2023-04-20_10-11-24.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_10-12-54.png b/tutorials/migration-tool/Images/2023-04-20_10-12-54.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_10-26-04.png b/tutorials/migration-tool/Images/2023-04-20_10-26-04.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_10-58-27.png b/tutorials/migration-tool/Images/2023-04-20_10-58-27.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_12-49-26.png b/tutorials/migration-tool/Images/2023-04-20_12-49-26.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_12-53-04.png b/tutorials/migration-tool/Images/2023-04-20_12-53-04.png
diff --git a/tutorials/migration-tool/Images/2023-04-20_15-02-16.png b/tutorials/migration-tool/Images/2023-04-20_15-02-16.png
diff --git a/tutorials/migration-tool/Images/Image-00.jpg b/tutorials/migration-tool/Images/Image-00.jpg
diff --git a/tutorials/migration-tool/Images/Image-02.png b/tutorials/migration-tool/Images/Image-02.png
diff --git a/tutorials/migration-tool/Images/Image-1-1.png b/tutorials/migration-tool/Images/Image-1-1.png
diff --git a/tutorials/migration-tool/Images/Image-10-1.png b/tutorials/migration-tool/Images/Image-10-1.png
diff --git a/tutorials/migration-tool/Images/Image-11-1.png b/tutorials/migration-tool/Images/Image-11-1.png
diff --git a/tutorials/migration-tool/Images/Image-12-1.png b/tutorials/migration-tool/Images/Image-12-1.png
diff --git a/tutorials/migration-tool/Images/Image-3.png b/tutorials/migration-tool/Images/Image-3.png
diff --git a/tutorials/migration-tool/Images/Image-4.png b/tutorials/migration-tool/Images/Image-4.png
diff --git a/tutorials/migration-tool/Images/Image-5.png b/tutorials/migration-tool/Images/Image-5.png
diff --git a/tutorials/migration-tool/Images/Image-6.png b/tutorials/migration-tool/Images/Image-6.png
diff --git a/tutorials/migration-tool/Images/Image-7.png b/tutorials/migration-tool/Images/Image-7.png
diff --git a/tutorials/migration-tool/Images/T03_Regex-Filter-option.png b/tutorials/migration-tool/Images/T03_Regex-Filter-option.png
diff --git a/tutorials/migration-tool/migration-tool.md b/tutorials/migration-tool/migration-tool.md
@@ -0,0 +1,164 @@
+---
+author_name: Kamlesh Zanje
+author_profile: https://github.com/vishu2804
+parser: v2
+auto_validation: true
+time: 30
+tags: [  software-product>sap-integration-suite, software-product>cloud-integration, software-product>sap-process-integration, software-product>sap-process-orchestration, tutorial>license, tutorial>beginner  ]
+primary_tag: software-product>sap-integration-suite
+---
+# Use the Migration Tooling 
+<!-- description --> The migration tooling is a feature in the Cloud Integration capability of the SAP Integration Suite. It enables you to semi-automate the migrations of integration scenarios from SAP Process Orchestration to SAP Integration Suite.
+
+## Prerequisites
+- You can refer to the [documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/add-sap-process-orchestration-system) to learn how to establish a connection between your SAP Process Orchestration system and the SAP Integration Suite migration tool so to fetch the SAP Process Orchestration objects from Integration Directory and Enterprise Service Repository.
+
+> Optionally, before you migrate an integration scenario, you can assess the migration of the integration scenarios using the Migration Assessment capability of SAP Integration Suite. For more information, see the [Migration Assessment documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/5c5e50ee2d644cc59d864409d5b7871c.html) and the blog [How to use the Migration Assessment Application to get read to migrate your SAP Process Orchestration Scenarios](https://blogs.sap.com/2023/02/28/how-to-use-the-migration-assessment-application-to-get-ready-to-migrate-your-sap-process-orchestration-scenarios/).
+  
+
+For more introductory information, benefits of the migration tool, and roadmap items, see the SAP blog [Migration tool in Cloud Integration Capability of SAP Integration Suite](https://blogs.sap.com/2023/01/27/migration-tool-in-cloud-integration-capability-of-sap-integration-suite/).
+
+
+## You will learn
+- How to use the migration tool
+- How to connect to SAP Process Orchestration system and migrate an integration scenario
+
+> After running the assessment, each integration configuration object is assigned a migration status. The possible migration statuses for integration configuration objects are **Evaluation required**, **Adjustment required**, and **Ready to migrate**. Currently, only integration configuration objects in status **Adjustment required** or **Ready to migrate** can be migrated.
+> Integration scenarios in the SAP Process Orchestration system map to integration scenario patterns. Each pattern has been analysed and matched against scenario templates delivered as part of the migration tool in Cloud Integration.
+> Every integration configuration object that can be migrated has an associated template in the migration tool. Based on the information provided in the templates, the migration tool creates the equivalent integration flows in SAP Integration Suite.
+
+Now let’s go through the process of a scenario migration using the migration tool.
+
+In the following steps, we'll migrate a point-to-point asynchronous scenario, which has SOAP adapters and mapping steps in the form of message mapping and XSLT mapping.
+
+You can migrate the integration scenario of your choice, but be aware of the supported [components](https://help.sap.com/docs/integration-suite/sap-integration-suite/supported-components), [templates](https://help.sap.com/docs/integration-suite/sap-integration-suite/supported-templates) and [known limitations](https://help.sap.com/docs/integration-suite/sap-integration-suite/known-limitations).
+
+---
+### Migrate SAP Process Orchestration artifacts
+
+1. Open the SAP Integration Suite launchpad, navigate to the design workspace of integrations, and create or open any existing integration package.
+
+    <!-- border -->![Image](Images/Image-00.jpg)
+
+2. **Edit** the integration package. The **Migrate** appears, so you can migrate the integration scenarios from SAP Process Orchestration to SAP Integration Suite.
+
+    <!-- border -->![Image](Images/Image-1-1.png)
+
+    <!-- border -->![Image](Images/Image-02.png)
+
+3. Choose **Migrate**. The migration tool opens as a wizard that guides you through the scenario migration.
+
+    <!-- border -->![Image](Images/Image-3.png)
+
+---
+
+### Connect to SAP Process Orchestration System
+
+1. Select the SAP Process Orchestration system and establish the connection. The SAP Process Orchestration systems added as part of **Add an SAP Process Orchestration System** are listed.
+
+    <!-- border -->![Image](Images/Image-4.png)
+
+2. Choose **Connect** to establish the connection. Once the connection has been established, continue with **Next Step**.
+
+    <!-- border -->![Image](Images/Image-5.png)
+
+---
+
+### Select the integration scenario to be migrated
+
+1. In step **Process Orchestration Artifacts**, select the integration configuration object you want to migrate. All the integration configuration objects are fetched from the Integration Directory of the SAP Process Orchestration system. The **Type** selected is **Integration Configuration Object**, which is the only SAP Process Orchestration object currently supported. 
+
+    <!-- border -->![Image](Images/Image-6.png)
+
+2. As the list can be rather long, filter the integration configuration objects using the regular expression in the search parameters. 
+
+     Regular expression **(*)** is enabled in the search parameters to search the integration configuration objects. In the following example, **(*)** is used in the Sender Communication Component to filter integration configuration objects. You can use **(*)** in either of the search parameters to ease the filtering task.
+
+    <!-- border -->![Image](Images/T03_Regex-Filter-option.png)
+
+    In this example, the integration configuration objects are filtered by applying the **Sender Communication Component** parameter. Once an integration configuration object is selected for migration, choose **Next Step**.
+
+    <!-- border -->![Image](Images/Image-7.png)
+
+---
+
+### Select the template applicable for the scenario
+
+Templates associated with the integration configuration object are available for the selection from the drop-down list. You can select a template for the scenario migration. If you want to learn more about the template and what the resultant integration flow model will look like after the migration, use the context-sensitive help. 
+
+<!-- border -->![Image](Images/2023-04-20_10-11-24.png)
+
+Every integration configuration object that is ready for migration also has a default template. If there are no associated templates available and yet the integration configuration object is ready for migration, the migration tooling falls back to the default template. Basically, default template creates a point-to-point integration flow; this template has neither the integration scenario nor the communication channels from the source integration configuration object. However, mapping objects such as message mapping, XSLT mapping etc. are copied and maintained in the point-to-point integration flow.
+
+<!-- border -->![Image](Images/2023-04-20_10-26-04.png)
+
+---
+
+### Name the integration flow
+
+In the **Integration Flow** tab, enter a meaningful integration flow name and ID and choose **Preview**.
+
+The description field is automatically filled with the SAP Process Orchestration system name, scenario type and name, and template details for future reference.
+
+<!-- border -->![Image](Images/Image-10-1.png)
+
+---
+
+### Review details 
+
+In the **Review** tab, check the details of your migration, then choose **Migrate**.
+
+   <!-- border -->![Image](Images/Image-11-1.png)
+
+
+After the integration scenario is successfully migrated from SAP Process Orchestration to SAP Integration suite, an integration flow is created in the artifact list of the package overview page.
+
+  <!-- border -->![Image](Images/Image-12-1.png)
+
+---
+
+### View artifact
+
+After the migration, a success page displays useful information and guidance on the next steps. In the success page, you can also see the equivalent channel/adapter mappings between SAP Process Orchestration and SAP Integration Suite, supported components and known limitations in the migration tool. 
+
+Open the anticipated integration flow which is created after a successful migration by clicking on **View Artifact**.
+
+<!-- border -->![Image](Images/2023-04-20_10-12-54.png)
+
+ In this example, a point-to-point integration flow is created having SOAP Adapter, two message mappings and one XSLT mapping.
+
+<!-- border -->![Image](Images/2023-04-20_10-58-27.png)
+
+---
+
+### Verify the configurations
+
+All supported adapters are externalized to leverage the benefit of the externalized parameters.
+
+1. Some configuration changes are required to ensure an integration flow is deployable. For example, in the Receiver SOAP Adapter, configure the proxy type as **On-Premise** and provide the associated **Location Id**.
+
+    <!-- border -->![Image](Images/2023-04-20_15-02-16.png)
+
+2. Select the XSLT mapping step and open the corresponding resource for verification. You can also verify the resources of the message mapping steps.
+
+    <!-- border -->![Image](Images/2023-04-20_12-49-26.png)
+
+---
+
+### Deploy the integration flow
+
+Process the messages by deploying the integration flow and triggering the endpoints as usual. Check if the security artifacts, like credential name and key alias, that are used in your integration scenario are correctly configured in the integration flow. Deploy the necessary security artifacts before you deploy the integration flow.
+
+<!-- border -->![Image](Images/2023-04-20_12-53-04.png)
+
+Congratulations! You've successfully migrated an integration scenario from SAP Process Orchestration to SAP Integration Suite.
+
+### Test yourself 
+
+
+
+
+
+
+
+---
Original file line number	Diff line number	Diff line change
Expand Up		@@ -48,4 +48,3 @@ Thumbs.db
		# VSCode specific files
		*.vr
		*.code-workspace