Here comes the revolutionary tool from SAP that can migrate all your dual stack ID objects to Java only ICO objects. Yes, really a true hassle free business converting the dual stack configuration objects to java only objects.
This is possible only from SP07 of PI 7.3 EHP1.
In order to access the tool, PI instance has to be SSL enabled in the first place.
Secondly, the user should have the roles SAP_XI_API_DISPLAY_J2EE, SAP_XI_API_DEVELOP_J2EE in source and target system respectively.
Once it is SSL enabled, access the tool using the URL https://<host>:<port>/webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd/DirectoryCockpit
You end up arriving at the below screen.
This is basically used to migrate all the objects that correspond to a complete Configuration Scenario.
This is used to configure the Systems that are used in the integration and the Renaming rules that you want to use to rename the objects like Communication Channels, Business Components, Party and Routing Expressions etc.
Used for migrating the communication channels.
Let’s how the migration is being done in each of the above cases.
The complete Configuration Scenario Migration is done based on the Sender Agreement (Receiver Determination if a Sender Agreement doesn’t exists as in the case of IDOC or PROXY). The tool gets all the objects of the complete configuration scenario by traversing through the Sender Agreement (Receiver Determination) till the Receiver Agreement of the respective configuration scenario.
Once you enter Scenario Migration, you will get the below screen in which you find the corresponding steps to be carried out.
In System Selection, you need to select the source system (in which you have all your classical dual stack based configuration objects) and the target system (in which you want to create the ICO objects for the respective source ID objects).
After providing the details, you move on to Scenario Selection where you need to select a Sender Agreement / Receiver Agreement (individually or all that exist in a particular configuration scenario). After migration, the respective IDOC AAE and the SOAP AAE will be created automatically.
Once you move on to the next option, Scenario Matcher, the tool validates whether all the involved objects can be migrated to an ICO in the target system.
Next is the Preview and Renaming. Here you can preview all the corresponding objects. You can rename the objects if you want using the renaming rules that we create as part of the Configuration migration. You can also check the adapter engine for the communication channels as part of this task. And as a result, all the ABAP based receiver communication channels will be transformed to JAVA based communication channels (ABAP IDoc to JAVA IDoc, ABAP XI to JAVA SOAP and ABAP HTTP to JAVA HTTP).
And finally, Object Creation. This creates all the objects and will be associated to a change list. You can view this change list in the target system’s integration Directory and can activate the same.
Configuration Migration is used to configure the systems that can be used as the source systems (you can select the available systems or you can add manually) and also to create any renaming rules for renaming the objects like Communication channels, Business components, Party, and Routing expressions.
Renaming the business systems still depend on the transport targets that were defined in the SLD.
We go for this option when we want to migrate many channels from one system to another.
Populate the source and destination system details and move on to the next step.
Choose all the communication channels that you want to migrate. And click on Next.
In the Object Creation, you will confirm to create the objects in the target system. All the objects will be created and associated with a change list in the target system. Log into the target system, change the details and activate them.