This document describes SAP directory content migration which is used for migration and mass change functionality for PI scenarios and channels from Dual Stack to Single Stack system. This document explains how to do Scenario migration, Channel migration, Renaming Rules with some exceptional cases along with Security and Authorizations required.
TABLE OF CONTENTS INTRODUCTION... 3 SCENARIO MIGRATION... 3 CHANNEL MIGRATION... 3 1. System Selection:... 4 2. Channel Selection:... 4 3. Object Creation:... 5 CONFIGURATION... 5 1. Systems:... 5 2. Renaming Rules:... 6 SECURITY AND AUTHORIZATIONS... 8 SCENARIO MIGRATION STEP-BY-STEP... 9 1. System Selection... 9 2. Scenario Selection... 10 3. Scenario Matcher... 10 4. Preview and Renaming... 11 a. Renaming... 11 b. Channel properties... 11 c. Channel migration... 12 5. Object Creation... 12 1. System Selection... 13 2. Scenario Selection... 14 3. Scenario Matcher... 14 4. Preview and Renaming... 14 5. Object Creation... 15 FAQ... 16 2
INTRODUCTION The Directory content migration tool provides migration and mass change functionality for PI scenarios and channels. The tool supports all releases from XI 3.0 on i.e. 3.0, 7.0, 7.1, 7.11, 7.3, 7.31 and 7.4. The tool can be accessed via http(s)://<host>:<port>/pimon -> Configuration and Administration -> Migration Tool where host & port is of target system can be AEX,PO or AE of dual stack system. SCENARIO MIGRATION The wizard allows to select one or multiple classical scenarios (Integration Engine) and to migrate these to Integration Configurations(ICO), running in a Java only environment. The selection of the scenarios is performed through selecting either of sender agreement, receiver determination or configuration scenario for the corresponding integration scenario. Scenarios with or without sender agreement are also supported. The tool automatically detects the objects participating in the scenarios, such as receiver determination, interface determinations and receiver agreements. It provides an option to preview and rename the object which will be created in the target system. If some of the used business components, parties, business systems and communication channels are missing in the target system, they will be created as well. CHANNEL MIGRATION The tool allows to select multiple channels from a source system to adapt the adapter engine, metadata version, channel attributes and module properties and create or update these channels in the target systems. Depending on the type of channels selected, properties have shown in Channel Selection step to edit in different sections. Click on Channel Migration link in Integration Directory Migration Tool page. Road map displays with steps. 3
1. System Selection: Select the source system name from drop down. If system is not present in dropdown list user can add by clicking Add/Change System button. Enter the username and password. User can select Use Secure URL checkbox option. Target system name is selected by default in which user has opened pimon(pi monitoring) page. 2. Channel Selection: User can search the channel/s either using channel name or Component or Party. Drop down option available to search the channel based on Sender or Receiver. Click on Search. User can search by using regular expression if the complete name is not known. e.g. Abcd* Select the channel which you wanted to migrate. Channel(s) Basic, Common Properties, Common Table Properties and Module Properties are shown. User can select the checkbox to edit the specific property of the channel. Click on next. 4
3. Object Creation: Click on Create button. Processing will be done and the status will be displayed. Like Ok, Warning or Error. A new change list created in the target system. After activating, channel will be available. CONFIGURATION 1. Systems: The tool needs to connect to a source system for reading directory configuration objects. The tool automatically recognizes all integration directories registered with the SLD, in addition the source system can be defined manually by specifying name and secure and/or nonsecure HTTP addresses. Create System: o Click on Create System button. o Enter the System Name, System URL and/or System secure URL. o Click on Save. Modify System by clicking on Modify button for already existing system. Delete the systems using Delete System button. 5
2. Renaming Rules: User can use the Renaming Rules to rename directory objects (Communication channels, Business components, Parties, Routing expressions and Business Systems). Directory configuration objects can be renamed, when migrated. In order to define reusable renaming patterns, the tool provides the possibility to define renaming rules. Currently there are 2 rule types supported, adding a suffix and value map. In addition the rules can be applied to Directory Objects or Expression Constants. Creation of Renaming Rule: o To define a Renaming Rule in the Migration tool, click on tab Renaming Rules - >Create Rule -> enter the Rule Name (for e.g., Rule2) -> Rule Type as Add suffix -> Applies for as Directory Objects -> Suffix as _<text> -> Save. o Valid characters permits while defining rule of Suffix are a(a)-z(z),0-9 and _. o If user wants to modify the Rule, select the rule name under tab Renaming Rules. Click on Modify button. o User can also select rule type as Value Map where user can define rule for more than one object to the corresponding renaming rule in target system. Also user can import defined rules from external file. 6
Apply the rule during scenario migration: o In the step Preview and Renaming user can rename the objects using rule which he/she created. o In the below screen shot, rule is applied for communication channels. User can also apply the rule for other objects by selecting the rule from dropdown. o Once the rule applied, channels name got changed according to the rule defined. 7
SECURITY AND AUTHORIZATIONS The tool is based on Integration Directory Programming Interface and requires corresponding security roles depending on the source system release in order to read data, e.g. SAP_XI_API_DISPLAY_J2EE. For the target system SAP_XI_API_DEVELOP_J2EE role is required. 8
SCENARIO MIGRATION STEP-BY-STEP 1. System Selection In the Integration Directory Migration Tool click on Scenario Migration link. a. Select the source system from which the tool will read the configuration scenarios to be migrated. b. Select Use Secure URL checkbox if secure communication should be used. c. Provide user name and password for the source system, having the authorization to use the directory API for display purpose. d. Provide user and password for the target system. Target system is always the local PI system. e. Click on next Example 1: Scenario (without sender agreement) Idoc to Proxy. 9
2. Scenario Selection a. Select Scenario By dropdown contains the options to search the scenario are Sender Agreement, Scenario Name and Receiver Determination. b. Search the scenario and select the scenario for migration. c. User can migrate multiple scenarios. Search criteria s are regular expression, Sender Agreement or Receiver Determination for searching multiple scenarios. d. Filter option provided for selecting the name of the configuration scenario you want to migrate, alternatively if no filtering is provided all the configuration scenario objects will be read from the source system. A progress bar is provided as this can take up to several minutes, depending on the number of scenarios. e. Also you can use wild card (*), substring for searching the particular scenario. f. Click on next. 3. Scenario Matcher a. The tool search through the complete directory of the source system for matching scenario objects: receiver determinations, interface determinations, receiver agreements. The matched objects are presented in this step. As the retrieval of the objects from the source system can take some time, a progress bar is provided before actually showing this step. b. Migration feasibility check: The tool will check if the scenarios can be migrated. Feature like receiver rules available in the classical PI scenarios is not available for integrated configurations. c. Excluded: The excluded check box is available to remove any content selected for scenario migration. d. Click on next 10
4. Preview and Renaming At this step it is possible to preview the integrated configuration to be created in the target system. In addition all the objects the integrated configuration depends on the source system are displayed. Also objects will be created in the target system if they are missing in source system. a. Renaming o o Directory object renaming: you can define different renaming rules for the different types of integration objects that are involved. If you rename one object then all dependent object are renamed accordingly, e.g., if you rename a party all the communication components and channels for this party will be renamed. Interface name and namespace cannot be renamed as these are often referring to ESR objects. Business System renaming based on SLD transport targets: business system can only be created in the target system if the corresponding business system exists in the SLD. The tool provides a built in renaming function that will rename the business systems from the source system, according to the SLD transport targets defined in SLD, similar to Integration Directory import. b. Channel properties You can define the target adapter engine and the adapter metadata version for, to be created channels. If the user wants the message flow on de central adapter engine user can select by clicking on Channel Properties button and selecting de central adapter engine. 11
c. Channel migration If the scenario which is migrated refers to ABAP based adapter channels, the channels are transformed into the corresponding Java adapter channels and the properties are preserved it also includes manual rework. Example in case of security related properties like user name and password will not get migrated. Here manual entry is required. ABAP IDOC adapter -Java IDOC AAE adapter(default mode) ABAP XI adapter -Java SOAP adapter with XI 3.0 message protocol ABAP HTTP adapter -Java HTTP AAE adapter ABAP WS Adapter -not implemented If the channels already exist in the target system, migration tool will not create those but existing channels will be reused. Click next. 5. Object Creation The object creation is triggered using the create button. The details from the object creation can be seen in the details text area. All messages from the directory API invocation are shown in the text area. 12
a. The tool first creates a new change list for each configuration scenario to be used. b. The tool attempts to create the required party, communication component, business system and communication channels objects. c. The tool deletes any conflicting sender agreement object (used when source and target system are the same). The integrated configuration object cannot be created if a sender agreement exists with the same message header. d. The tool creates the integrated configurations objects. e. The tool creates the configuration scenario object. f. The channel list is not activated. It is required that the person performing the migration to review the objects created by the migration tool and activate the change lists. g. Click on finish. Log on to target system and activate the change list. Example 2: Scenario (with sender agreement) - File to File. 1. System Selection 13
2. Scenario Selection 3. Scenario Matcher 4. Preview and Renaming 14
5. Object Creation Click on finish. Log on to target system and activate the change list. 15
FAQ 1. Does migration tool support migration of objects without sender agreement? Yes. 2. Does migration tool creates channels which are already in target system?(in case of different properties including activating objects) If the channel already exists in the target system they are not created. But for certain channels the names are same and properties are different (for e.g. the adapter type) even in this case the channels are not created and hence is not available in the change list (along with other objects). Hence activating the other objects like Integrated Configuration and scenario is not possible. 3. Why does the migration tool not overwrite the existing objects? In general, the tool does not provide 100% migration in all cases. So in some cases it is a mixture of what the tool creates and what would be done manually by the person doing the migration. So, we do not like to modify always and existing objects will not be overwritten. But we do have the option of defining renaming rules (suffix rules) and use it for the channels, now when the names do not clash new channels will be created. 4. Does the tool support migration of scenario like multiple senders and one receiver? Yes. It creates multiple ICO s. 5. Does tool support migration of multiple scenarios at a time? Yes. User can search scenarios by using common character in scenario selection step or using other options like sender agreement or receiver determination. 16
6. Does migration tool supports migration of scenarios where wild cards are used? e.g. * Tool supports the scenarios migration which contains wild character with some exceptional case. Example tool doesn t support the migration of scenario if * for sender system in receiver determination where sender agreement is missing (IDOC) Example tool supports below cases: a. Sender system is * in receiver determination, has single/multiple sender agreement/s which fit to receiver determination. b. Sender system is * in interface determination and receiver agreement, has single/multiple sender agreement/s and receiver determination/s which fit to configuration scenario. 17
www.sap.com 2013 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 18