Migration of Dual-Stack Configuration Objects ("Classical Scenarios") to Integrated Configuration Scenarios (Java-Only)

Use

The Integration Directory Migration Tool allows you to select one or more classical PI scenarios and migrate them to integrated configurations running in a Java-only environment. You select the scenarios through selection of the sender agreement for the corresponding integrated scenarios. Scenarios without a sender agreement can be selected by the receiver determination object. The tool automatically detects all related objects participating in the scenarios, such as receiver determinations, interface determinations, and receiver agreements. The tool provides an option to preview and rename the object that will be created in the target system. If any of the used business components, parties, business systems, or communication channels are missing in the target system, they will be created as well.

Procedure

System Configuration

  1. To run the Integration Directory Migration Tool, use the following link in the target system:

    Open a browser and go to http://[host]:[port]/pimon to access the Process Integration tools.

    Then choose Start of the navigation pathConfiguration and Administration Next navigation step Common Next navigation step Migration ToolEnd of the navigation path.

  2. To configure the systems you want to use as source systems and to configure renaming rules, choose Configuration .

  3. If the system you want to use is not available in the list of source systems, choose Add/Change System .

  4. Choose Create System .

  5. Enter System Name , System URL , System Secure URL , and choose Save .

  6. To define a renaming rule, go to the Renaming Rules tab. Choose Create Rule and enter the rule name. Choose Save .

    You can use the Renaming Rules to rename directory objects such as Communication channels , Business components , Party , and Routing expressions .

    Business system renaming is done based on SLD (System Landscape Directory) transport targets. The business system can be created in the target system only if the corresponding business system exists in the SLD. The tool provides a built-in renaming function that renames the business systems from the source system according to the SLD transport targets defined in the SLD.

Scenario Migration

  1. On the Integration Directory Migration Tool start page, choose Scenario Migration .

    System Selection

  2. Select the source system from the System Name dropdown list, from which the tool will read the configuration scenario to be migrated.

  3. To use secure communication, select Use Secure URL .

  4. In the User Name and Password fields, provide User and Password for the source system.

    The tool is based on the Integration Directory Programming Interface and requires the corresponding security roles, depending on the source system release, in order to read data, for example, SAP_XI_API_DISPLAY_J2EE. The SAP_XI_API_DEVELOP_J2EE role is required for the target system. To enable accessing of the source and local system via HTTPS, the SSL certificates of the system must be available in the WebServiceSecurity Keystore view in the AS Java Keystore.

  5. In the User Name and Password fields, provide User and Password for the target system.

    The target system is always the local PI system. If the tool is started on a decentral Adapter Engine, it connects to the Integration Directory running on the central PI system. The source and target system can also be the same system.

  6. Choose Next .

    Scenario Selection

  7. To search for the configuration scenario that you want to migrate, enter the name of the configuration scenario in the Scenario field and choose Search . If no filter is provided, all the configuration scenario objects are read from the source system. You can select one or more sender agreements individually or you can select to migrate all sender agreements that are part of particular configuration scenario objects. For scenarios without a sender agreement, you can select one or more receiver determination objects as a starting point. New IDOC AAE or SOAP sender channels are created based on the interface namespace. Only receiver determinations without a sender agreement are shown in the list. A progress bar is provided as this can take up to several minutes, depending on the number of scenarios.

    Scenario Matcher

    The wizard checks if the scenario can be migrated. It searches through the complete directory of the source system for matching scenario objects such as receiver determinations, interface determinations, and receiver agreements.

    With Migrate to IFlow you decide whether the listed scenarios are migrated to integration flows (IFlows) (preselected option) or to Integrated Configurations (ICOs).

    Preview and Renaming

  8. To preview the objects, choose Next .

    You can preview the objects that are going to be created in the target system. In addition, the wizard shows all objects that depend on the integrated configuration in the source system, such as parties, communication channels, business systems, and communication channels. If these objects do not exist in the target system, they will be created. You can switch between an integrated configuration-centric view or an overview mode, which shows all the migrated objects.

  9. Choose Channel Properties . In the popup, select the target Adapter Engine for the channels and the target namespace.

    If the scenario that is migrated refers to ABAP-based adapter channels, the channels are transformed into the corresponding Java adapter channels, and the properties are preserved, where applicable.

    ABAP IDOC adapter is transformed to Java IDoc adapter

    ABAP XI adapter is transformed to Java SOAP adapter with XI 3.0 message protocol

    ABAP HTTP adapter is transformed to Java HTTP adapter

  10. Choose Renaming Rules to rename the objects by choosing a rule defined in the configuration step (see step 6 under System Configuration ).

  11. Choose Next .

    Object Creation

  12. Choose Create . This creates a new change list in the Integration Directory of the target system and adds all new objects to this new change list.

    The log displays the details regarding the objects that are created, not created, or exist already (party, communication components, business systems, communication channels, integrated configuration objects, configuration scenario) with an OK/Error/Warning message. Existing objects are reused and are therefore not created.

    Make sure that the business systems exist in the SLD of the target system.

  13. Choose Finish .

  14. Log in to the Integration Directory of the target system. A new change list has been created. Review all created objects and activate the change list.