Skip to Content
Product Information
Author's profile photo Vishakha Deshmukh

How to use the Migration Assessment Application to get ready to migrate your SAP Process Orchestration Scenarios?

The purpose of this blog is to guide you through Migration Assessment, a new capability of the SAP Integration Suite. The Migration Assessment feature allows you to evaluate your SAP Process Orchestration system prior to migrating to the SAP Integration Suite.

Migration assessment assists you to estimate the technical efforts required for the migration process and determines how various integration scenarios can be migrated. It focuses on extraction and assessment of your current landscapes design time artifacts. This capability serves as the basis for your overall migration planning.

Key Benefits

  • Automatic process to extract and assess integration scenarios from SAP Process Orchestration.
  • Reduces the effort of an assessment to hours instead of days or weeks vs. manually.
  • Proactively reduces the risk of a migration project.
  • Helps in decision-making of integration scenarios in a phased manner.
  • Provides upfront transparency on estimated migration costs.

You can also find more introductory information about the Migration Assessment capability in the SAP announcement blog for Migration Assessment.

 

Availability

It is important to note that the Migration Assessment capability is currently available in the standard and premium editions of the SAP Integration Suite.

Which versions of SAP Process Orchestration are supported?  

The Migration Assessment capability is currently supported only for SAP Process Orchestration 7.5 SP06 and above. It is expected to support older versions of SAP Process Orchestration, including SAP Process Orchestration 7.4 and 7.3x, in the future.

For more information on this, navigate to the RoadMap Explorer here

Activating the Migration Assessment capability

Before utilizing the Migration Assessment tool, it must be activated within the SAP BTP cockpit and appropriate access rights must be granted to users. This can be achieved by following the steps outlined in the blog: Enablement guide for SAP Integration Suite Migration Assessment Capability.

Configurations and Connectivity

To establish the connectivity between migration assessment application and SAP Process Orchestration, you can use Cloud Connector to securely expose the endpoints (listed below):

  • Create a new HTTP destination (cloud to on-premise) with back-end type SAP Process Integration. For more information, refer Configure Access Control (HTTP)

  • Make sure that your SAP Cloud Connector is exposing correctly the following API paths. These are used to extract data from your SAP Process Orchestration system:
    • Directory Content
      • /CommunicationChannelInService
      • /IntegratedConfigurationInService
      • /SenderAgreementInService
      • /AlertRuleInService
      • /IntegratedConfiguration750InService
      • /ValueMappingInService
      • /ConfigurationScenarioInService
      • /BPMFacadeBeanImplService
      • /ReceiverAgreementInService
    • ESR Content
      • /rep/read/ext
      • /dir/read/ext
      • /rep/support/SimpleQuery

The endpoints are constructed according to the pattern <protocol>://<hostname>:<port>/<endpoint>.

  • Limit access to the previously mentioned endpoints and subpaths by changing Access Policy to Path and All Sub-Paths.

You can also refer to the Prerequisites documentation for more details before adding a SAP Process Orchestration system.

To connect  SAP Process Orchestration system with the Migration Assessment application, consider following steps, in your subaccount in SAP BTP cockpit.

Step 1: Logon to the SAP BTP cockpit and navigate to your subaccount to configure the required destinations.

Step 2: On SAP BTP side, Destination service is used to store your connectivity configuration.

Step 3: Navigate to Connectivity > Destinations and choose New Destination.

Step 4: For general information on creating destinations in your subaccount, see Create a Destination

 

Step 5: Configure a new destination with following details specific to your system:

Field Content
Name

PO_<systemname>_DIR

Important: It’s mandatory to follow this naming convention, otherwise the destination will not be recognized on the Migration Assessment.

Type HTTP
Description Add a meaningful description
URL Add your system URL
Proxy Type OnPremise
Authentication Basic Authentication
Location ID Add your location ID
User

­­­ This should be a technical user – do not use personal credentials.

Please note: The user must be assigned to the following roles in your SAP Process Orchestration system:

·       SAP_XI_API_DISPLAY_J2EE

·       SAP_XI_API_DEVELOP_J2EE

·       SAP_XI_MONITOR_J2EE

·       SAP_XI_MONITOR_J2EE

Password Add the user’s password
Property systemname Add the name of the system that you want to create on the Migration Assessment
Property esrdestination Optional: If you use a central ESR and need to create an ESR destination, add the destination’s name here

Step 6 (Optional): If you’re not using a central ESR, you only need the Integration Directory destination. If you’re using a central Enterprise Services Repository (ESR), create a second destination with the details listed in the following table.

Field Content
Name PO_<systemname>_ESR
Type HTTP
Description Add a meaningful description
URL Add your system URL
Proxy Type OnPremise
Authentication Basic Authentication
Location ID Add your location ID
User

Add the user’s ID

Please note: The user must be assigned to the following roles in your SAP Process Orchestration system:

·       SAP_XI_API_DISPLAY_J2EE

·       SAP_XI_API_DEVELOP_J2EE

·       SAP_XI_MONITOR_J2EE

Password Add the user’s password
systemname   Add the name of the system you created in Migration Assessment

Add a SAP Process Orchestration System

After saving your destinations, open the Migration Assessment application and navigate to Settings. In the Process Orchestration Systems table, choose Add and enter the System Name (according to the system name defined on the destination) and Description.

In the Migration Assessment application, refresh the page. The page now displays information about the Integration Directory and, optionally, the Enterprise Services Repository you connected to your previously created system.

 

Note: In future, you will be able to maintain the connection details and the SAP Process Orchestration system information directly on the Migration Assessment.

Now, let’s take a tour of the Migration assessment application.

Rules

In the Migration Assessment application, navigate to  Configure Rules. Here you will find a list of predefined Rules by SAP. Rules are a set of characteristics according to which the application evaluates whether an integration scenario can be migrated and what effort you can expect.

It is important to note, that currently it is not possible to add custom rules or change the standard rules. You are able to only view the standard rules.

 

Let’s select the Rule SenderAdapterType for example. Here, you can see all the parameters of the Rules such as Rule Match Value, Assessment Category, weight assigned to each Rule Match Value. Based on these weights, the application calculates the estimated effort, which means that some parameters, and therefore rules, have a bigger influence on the final estimation than others.

 

Create a Data Extraction Request

Using Data extraction request, you are now ready to retrieve data from the connected SAP Process Orchestration system.

Step 1: In the Migration Assessment application, navigate to  Request Data Extraction.

 

Step 2: Enter a Request Name and select the System you want to connect to and click on create.

The data extraction starts. Once the extraction finishes, the new request appears in the list of data extraction requests with the status Completed.

It’s important to note that currently we have a size limitation of 2 GB on the data extraction. If the data extraction causes any issues regarding size, please contact SAP support.

Note: It is recommended to re-run an extraction, only if you have done any changes in the SAP PO system such as changed an existing ICO or added a new ICO or IFlow. During the migration project, you should avoid adding more scenarios to the PO system and create new scenarios directly on Cloud Integration. In this case, there will be no need to run an extraction again for the SAP PO system.

Step 3: Choose Log to view the data extraction log, which provides you with details about the data extraction.

 

Step 4: After extracting the necessary data from your system, you can assess the integration scenarios associated with your data using scenario evaluation requests. See Create a Scenario Evaluation Request.

You can also delete unwanted extractions by clicking on that extraction and then clicking on Delete. Refresh the page and the extraction gets deleted.

 

Create a Scenario Evaluation Request

To evaluate your integration scenarios using the information from data extraction requests at least one data extraction request should be created.

Step 1: In the Migration Assessment application, navigate to Request Scenario Evaluation.

Step 2: Choose Create.

Step 3: Enter a Request Name and choose a Data Extraction Request that you created previously.

Step 4: For this specific run of your scenario evaluation, enter an Evaluation Run Name and a Description. You can start a new evaluation run anytime, for example, for the purpose of comparing new and old data. This can be achieved with the help of Trigger analysis (described in ‘Trigger analysis’ section).

Step 5: Choose Create.

Step 6: The new request appears in the list of scenario evaluation requests and the evaluation runs.

By clicking Delete, you can delete the unwanted scenario evaluation.  Refresh the page and the evaluation gets deleted.

 

The following additional actions can be performed for a scenario evaluation request:

  •  Open Dashboard: It displays an analysis of your scenario evaluations with details specific about your integration flows such as assessment categories, adapters, and an overview of the rules used in the evaluation, which can be accessed and downloaded. You can switch between the data of all runs performed for the scenario evaluation request so far.

 

  • Under the Overview tab on the dashboard page you may find different types of views, such as:

Scenarios by Assessment Categories:

 

Assessment Categories: A classification that indicates if your integration scenarios are ready to be migrated to the SAP Integration Suite or if they need some significant changes and how you can proceed.

  • Ready to migrate: These integration scenarios match to the scenarios offered in SAP Integration Suite. They can be moved to SAP Integration Suite manually or semi-automatically. No manual changes or minor configuration steps might be required to get to a running state.
  • Adjustment required: These integration scenarios partially match to the scenarios offered in SAP Integration Suite. They can be moved to SAP Integration Suite manually or semi-automatically. Further adjustments to the end-to-end integration process based on best practices are required (e.g., File to SFTP conversion, external JMS connection).
  • Evaluation required: The integration scenarios cannot be migrated to the SAP integration Suite at the moment. Evaluation is needed to see if the interfaces are still required, or if they can be modified to run in the SAP Integration Suite (e.g., B2B scenarios). Analyze interfaces that are categorized as “Evaluation required” and verify what aspects of these interfaces were identified as current limitations on the SAP Integration Suite. Check on possible solutions using the SAP Integration Suite documentation or Best Practices Guides. Also check out the roadmap to find out if and when potential limitations might be resolved.

    Scenarios by Effort Estimation:

 

As depicted in this above chart, there are 1,535 small (S) integration scenarios and 85 medium (M) integration scenarios. An estimation of efforts required to migrate these integration scenarios from the SAP Process Orchestration system to SAP Integration Suite needs to be performed. This sizing classification (i.e., S, M, L, XL), effort estimation you will get to know in more details below in Evaluation Results section under .pdf file.

Sender Adapters:

This section shows the number and the types of Sender adapters in your on-premise system.

Receiver Adapters:

This section shows the number and the types of Receiver adapters in your on-premise system.

On the dashboard under Integration Scenarios tab, you can see the list of all the integration scenarios from your SAP Process Orchestration system. You can also download from here all the integration scenarios, size of the integration scenarios (S, M, L, XL), assessment category assigned to each integration scenario either in .pdf format or in .xslx format.

 

  • Trigger Analysis:  With this functionality, you can schedule an additional evaluation run based on current extracted data. Trigger analysis is recommended only when there is change/update in SAP predefined rules. By clicking Trigger analysis, you can rerun the evaluation, without going through the complete procedure of creating Scenario evaluation request. With this you can have multiple evaluation runs for one evaluation request. If a new extraction request is created, then you will have to run another evaluation request.

Also, when you want to compare the old and new evaluations, best practice would be to add the date on the evaluation run name (see below screenshots), so that it will distinguish between the two evaluation which helps to compare in the dashboard later on.

 

 

Under Scenario Evaluation Run dropbox you can see all the evaluation runs which were triggered for the same extracted data .

  • Download: Evaluation Reports can be downloaded either in English or Simple Chinese language. It is possible to download the reports in .xslx file and .pdf file formats:

Evaluation Results

  • The .xslx file contains all the integration scenarios that were part of the request with migration effort according to the sizing classification, rules applied to them, weight, assessment categories and status.

The Full Evaluation Results sheet displays information about rules that were applied for each integration scenario as defined by SAP. Each line includes the rule ID, the value assigned to it, the weight considered for it, and the evaluation assessment category.

In Eval by Integration scenario sheet, you can see the list of integration scenarios summarized by total weight evaluated, the T-Shirt size and the overall assessment category. The overall assessment category is classified based on the set of rules triggered to the respective integration scenario. For example, if the integration scenario has at least one rule with the assessment category as “Evaluation required”, then the overall category for that integration scenario is also “Evaluation required”.

The option as .pdf file features the previously mentioned details about the integration scenarios while also providing a written summary of adapters and the assessment in general, with charts and tables. This file is suited as a report that can be used for example for management. Below screenshots shows the contents of the pdf report.

Explanation of the Effort Estimation:

  • Sizing classification, which is a project estimation and capacity planning tool that helps you track how much time or effort the migration of interfaces will take. Here, the sizing classification is Small(S), Medium(M), Large(L), Extra Large (XL).
  • An overall estimation in days of the effort according to the sizing classification (Small(S), Medium(M), Large(L), Extra Large (XL)) required to technically migrate the integration scenarios to the SAP Integration Suite.
  • The learning curve or repeatable factor is reducing the effort based on the consideration that in general a group of interfaces, from the same size, system or module are similar and therefore the migration of the subsequent interfaces is performed quicker than the first ones.
  • An assessment result that gives information regarding functional readiness to move those scenarios to the SAP Integration Suite for each integration scenario.

Important Links:

  • To understand step by step process of Migration refer to SAP Blog Migration tool

SAP Help Pages

  • To get all the information on why you should move to SAP Integration Suite, preparation for Migration process, and the Migration process itself refer this guide Migration Guide for SAP Process Orchestration
  • To get information on Migration Tool, refer Migration Tooling
  • To explore in more detail about the Migration Assessment application in product documentation

For further references, you can also refer to the below links:

 

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Richard Kleibl
      Richard Kleibl

      thanks for this very informative blog.

      Author's profile photo Chetan Anguralia
      Chetan Anguralia

      Is this Migration assessment Applicable only to PO ?? not PI (Dual Stack)?

      Author's profile photo Richard Kleibl
      Richard Kleibl

      You can run it on the Dual Stack as well, but currently, we only evaluating ICOs and PO iFlows.