Running Migration Assessment

Course sap-int-301 explains why Contoso Motor Co. is leaving SAP Process Orchestration and in what order. This course is the hands-on half: the screens, settings, files and evidence. It follows Theo's integration team through the 64 integrated configurations on PO system XP1, from the first data extraction to the last wave switch. Lesson 1 gets the assessment running.

Two capabilities, two jobs

SAP splits the work across two tools that are easy to confuse. Migration Assessment is its own capability of SAP Integration Suite, running in the SAP BTP Cloud Foundry environment. It extracts configuration and usage data from a PO system, evaluates every integration scenario against SAP's rules, and estimates effort. It migrates nothing. Migration Tooling is a feature of the Cloud Integration capability that turns PO objects into integration flows (lesson 3). Both depend on your Integration Suite service plan; SAP Note 2903776 lists which plans include which features.

Migration Assessment supports two kinds of PO content: integrated configurations, which run on the Java-only Adapter Engine, and dual-stack scenarios. The supported releases are 7.31 SP28, 7.40 SP23 and 7.50 SP06 and above. For 7.50 SP06 to SP09, SAP Help asks for the patch in SAP Note 2456339 first. Sam, Contoso's Basis lead, confirms XP1's support package level before anyone requests access.

Prerequisites, in the order you will hit them

The endpoint list in SAP Help is specific, and it is worth exposing nothing more. It includes the Integration Directory services (for example /IntegratedConfiguration750InService, /CommunicationChannelInService and /ValueMappingInService), the ES Repository paths such as /rep/read/ext and /rep/query/ext, message monitoring at /mdt, channel monitoring at /AdapterFramework/ChannelAdminServlet, and /CPACache. Copy the current list from SAP Help into the Cloud Connector change request rather than from an old blog.

Step 1: Add the PO system

1. In the Migration Assessment application, open Settings. In the SAP Process Orchestration Systems table, choose Add.
2. Enter a System Name (Contoso uses XP1) and pick the System Version, or choose Auto-Detect.
3. Under Integration Directory, enter the Address (the Cloud Connector virtual host), the technical User ID and the Password.
4. Under ES Repository, tick Same as Integration Directory unless you run a central ES Repository on another host. Choose Create.
5. Select the system and choose Test Connection. Do this even if the Cloud Connector and destination checks were green: only this test checks that the PO resources the extraction needs are reachable.

Step 2: Create a data extraction request

Go to Request > Data Extraction and choose Create. Enter a Request Name, select the system, and pick Complete Extraction (every integration scenario) or Custom Extraction (deselect scenarios you want to leave out). The extraction pulls integration scenarios, communication channels, sender and receiver agreements, alert rules and value mappings from the Integration Directory; operation mappings, message mappings and service interfaces from the ES Repository; and processed messages from the message monitor. Disk storage per tenant is limited, so delete extractions you no longer need.

Step 3: Create a scenario evaluation request

Go to Request > Scenario Evaluation, choose Create, enter a Request Name, pick the Data Extraction Request, and give this run an Evaluation Run Name and Description. Each request then offers Open Dashboard, Trigger Analysis (a new run on the same data), Export (the full spreadsheet) and Generate Report (a PDF summary). SAP updates the rule set over time, and an older extraction may not carry what new rules need, so plan a fresh extraction before each formal re-evaluation. Put the date in every run name so runs can be compared later.