Moving Integration Directory Artifacts from dual stack to single stack
Directory Content Migration Tool
Introduction
The Directory Content Migration Cockpit is an automated tool that provides migration and mass change functionality for PI scenarios and channels. It is a Java Web Dynpro web application based on the Directory Program Interface API. It is delivered as a standard monitoring component for PI.
The tool significantly reduces the efforts of migrating directory artifacts when the system is upgraded.
Its key value is realized through the automation of:
- The conversion of classical scenario configuration to Integrated configuration
- Migration of scenarios between releases having no direct upgrade path
- Migrating from dual stack to single stack
-
The conversion of ABAP based channels to their Java equivalent
-
ABAP IDOC adapter converts to Java IDOC AAE adapter
-
ABAP XI adapter converts to Java SOAP adapter with XI 3.0 message protocol
-
ABAP HTTP adapter converts to Java HTTP AAE adapter
-
ABAP WS Adapter conversion is not implemented
-
- Mass updation of channel properties
- Mass movement of channels
The directory content migration tool automates the steps of the above stated activities, thereby reducing the number of manual steps.
The tool runs on the target, and needs no installation/settings on the source.
The target system should be a 7.3X or higher system. It supports all source system releases starting from XI 3.0.
All scenario migrations are based on Sender Agreements. Those scenarios that do not have a sender agreement are out of scope.
It allows selecting one or multiple classical scenarios and converts them to Integrated Configuration before moving to the target system.
The tool also allows renaming the artifacts during scenario migration, either in the tool or through pre-constructed renaming rules.
Additionally, in case the migration is happening to a fresh system, the tools automatically also creates the dependent artifacts; like channel, service and party.
Accessing the tool
The Directory Content Migration tool runs on the target system and can be accessed via:
Authorizations
In order to execute the Directory Content Migration tool, we need a user on the source and target system with the following authorizations:
Source System:
SAP_XI_API_DEVELOP_J2EE
SAP_XI_API_DISPLAY_J2EE
Target system:
SAP_XI_API_DEVELOP_J2EE
Availability
The Directory Content Migration tool will be available from:
NW Process Integration 7.30 SP9: Q4 2012
NW Process Orchestration 7.31 SP7: Q2 2013
UI
The screenshots below give a brief idea about the look and feel of the Directory Content Migration tool.
Please double-click on the image to see the enlarged version 
Hi Meghna,
excellent blog thank you.
All the best,
Andy.
Hi,
Nice tool...Does this tool includes
i. Any connectivity test options ?
ii. Copy all the properties of the channels (e.g passwords, certificates, Module parameters etc,..) ?
iii. Hope the Value Mapping objects also can be migrated as is
What is the approach to be followed for the objects not having sender agreements ..
Thanks
Rajesh
Hello Rajesh,
great support from SAP!
seems it will ease migration headache ... very nice tool, awaited since long...
Very nice tool indeed. We're actually developing (in-progress) for this type of tool (external tool) using Directory API. But for this tool, it's for dual stack to single stack. I wonder if SAP will do the same for dual stack and probably I can disregard the plan we had for this kind of tool.
Great gob SAP for making it simpler for us to do migration.
I wonder if SAP will release it ahead of time or probably release a separate SCA for this that I can use for my upcoming project (XI 3.0 to PI 7.31 migration)
Let me take this on behalf of Meghna.
The tool will be actually supported on a dual stack PI system as well as on the Java-only installation options Advanced Adapter Engine Extended (AEX) and Process Orchestration (PO). So, you can either use it to migrate your classical configuration objects from a PI dual-stack system to an AEX or a PO, or you can run it on a PI dual-stack system to move your scenarios to the Adapter Engine of the PI dual-stack system running there as Integrated Configuration Objects (ICO).
Alex
Hi Meghna,
Our client has migrated to SAP PI 7.31 SP4.Is there any other tool for the SAP PI 7.31 SP4?
Hello Somil,
There is no other similar migration tool on SP4. You will need to wait until NW Process Orchestration 7.31 SP7 is released in Q2 2013 (15th April to be precise).
Answer to the other question from you:
The URL for the tool has to be updated with the host and port of the target system:
http://<server>:<port>/webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd/DirectoryCockpit.
Thanks and Regards,
Meghna
Hi Meghna,
We are planning to split our current PI 7.1 dual stack and move to Java only stach NW 7.31 SP7. As per the blog it appears that it going to be released in Q2 2013.
We would like to implement at Coke beforehand and test the migration/upgrade from PI7.1 to PI 7.31 sometime FEB or March 2013. Could you let us know how to approach for participating in the ramp of the PI 7.31 SP7?
Regards,
Raja Sekhar Kothapalli
Thanks
Question... We are preparing migration 7.1 to 7.5 now. But we have a abap mapping scenario on 7.1 . it will be supported mass migration on 7.5? in this case what is the best solution for it? Re-build for abap mapping -> Java mapping on 7.5.
Thanks
Young
Hi Meghna,
Thank you for the blog.
Since the migration tool depends on the Directory API, will this tool support migration from PI 7.10? Because creating interfaces with multiple operations was introduced in PI 7.10. These new interfaces cannot be read by the Directory API available on PI 7.10. The newer version of the Directory API was introduced in PI 7.11. Will the new Directory API be downported to PI 7.10? If so, is there a date?
Thanks,
William Li
Dear Meghna and Alexander,
First of all excellent move by SAP to support this tool . Is really helpful.
One question though , we are planning to make a move from PI 7.11 SP9 to PI 7.31 SP7 DS.And I see a comment from Alexander Bundschuh here that we can use this tool for Dual Stack to dual stack migration running there as Integrated Configuration Objects (ICO).
Is there is a possibility of using this tool for migration from Classical Configuration scenario to Classical configuration? Or do we have to use the ICO option?
We want to migrate all the scenarios along with all the Communication channel contents from one 7.11 IB to 7.31 IB. Is there any other tool we can use for this, if not this one?
Thanks in advance,
Ravindra Hegde
Hi,
The tool is only from classical to ICO. For other migrations, e.g. comm chans and classical configurations, you can use the standard export/import process.
Regards,
William Li
Hello, William,
Thanks for being so faithful in supporting the PI/PO community. Nice to see your response here in addition to our e-mail communications. My client is using Migration Tools to migrate the objects from dual stack to single stack ICO. For the most part, the migration was very smooth, but we did run into the issue where an interface has multiple operations. Does ICO support multiple operations?
Regards,
Annie
Hi Annie,
yes ICOs do support multiple operations
if you face issues with the migration tools for interfaces having multiple operations, please raise a support ticket
Alex
Hello,
then we can use this tool to migrate from classical to ico. Do you know if there is a tool to migrate from ico to iflow in PI 7.31 ?
Regards,
Albert
Hi Albert,
not yet, but we plan to provide such a capability
would you like to have this included into the migration tool or will a separate tool (maybe in Eclipse) do as well?
Alex
Hi Alex,
This will be good to have. Do we have any dates when such an option might be available?
It will help customers who would be migrating and would also help customers who have already migrated but would like to convert the ICO to iFLOW.
So probably having it outside of the migration tool will be better.
Regards,
Sumit
Alex,
we think that best place is in Eclipse as contextual ico option ("generate iflow from ico").
We will start migrating from classical to ico and when this tool will be available we will create all iflows.
Thanks
Albert
Hi Meghna,
is there any detailed documentation about the renaming rules? The directory migration works fine, but somehow my renaming rules are not applied even though they were explicitly assigned for the channel object as part of the scenario migration.
When checking the official SAPHelp page (http://help.sap.com/saphelp_nw73ehp1/helpdata/en/3e/d34a2ebe0443879f9f71d1d04742ab/content.htm?frameset=/en/f1/544ad104f6494c9eb0a8a87a601549/frameset.htm) the renaming rules are mentioned, but their syntax is not explained in detailed. The SAP Note 1806772 referenced on SAPhelp is currently not released.
Regards, Holger
Hello,
we started using this tool in order to migrate from PI 7.1 to PO 7.31 single stack. It was perfect with first four scenarios: automatic, fast and easy. After these first scenarios we started having always same error: "Cannot migrate scenario. Details: Cannot find a sender agreement object for this scenario; sender agreement object might not be activated in the Integration Directory". Did you have this error message? Do you know how to solve it? Do you know is there is a workaround?
Thanks,
Albert Dalmau
Hello Albert,
this is a known restriction with 7.1, actually it is a restriction of the Directory API that the migration tool relies on. We have already implemented a fix which will be released soon. We can provide you a patch in the mean time. Please open an incident ticket on component BC-XI-IBC.
Regards
Alex
Hi Alexander,
I'm getting the same problem that Albert reported.
We are migrating from PI 7.1 to PO 7.4 single stack. I started with the first scenario, in the migration tool and I'm getting the next error: "Cannot migrate scenario. Details: Cannot find a sender agreement object for this scenario; sender agreement object might not be activated in the Integration Directory".
I found SAP Note 1947444, Is it necessary upload PI 7.1 components before using migration tool?
Is it safe to apply that upgrade in PI 7.1, can we experience some problem ? It is our productive system.
Thanks,
Jessica
Hi,
I believe the tool has a limitation due the the Directory API, which is used by the tool. There are 2 versions of the Directory API, one for PI 7.0 and below, and the other is for PI 7.11 and above. PI 7.10 is not supported by either versions. This is why I think the problem occurred.
Development is working on a solution, but I do not know the status.
Regards,
William
Hello Meghna,
thanks a lot for the great blog!
Are there plans that the content migration tools supports a migration to iFlows?
Thanks.
Best regards,
Jochen
Hi Jochen,
yes, converting Integrated Configuration Objects into Integration Flows is on our roadmap, not necessarily as part of the migration tool, this hasn't been decided yet, but more likely as part of the Eclipse plugin.
Alex
Hi Meghna, great article.
Combined this with others written by WIlliam Li helped us a lot planning our migration process.
However, we are facing an error during migration. The ABAP dependent channels are not automatically converted even with channel properties configured to SAPBASIS 740.
Have someone faced the same problem?
I have created a discussion in the forum if you want to comment there!
Thank you very much.
Hi Meghna,
Its very informative.
Can you please let me know how to migrate Seeburger design objects and scenarios from SAP PI 7.0 to SAP PO 7.4(Single stack) using the tool.
Hi Chiranjeevi,
Presently I am doing migration for Seeburger objects. in my experience, we can migrate the Seeburger classical objects to Integrated configuration objects. but the migration tool is not converting Spilt997 adapter to PO EDISeparator adapter so once the object got migrated to PO, manually we need to change this Split997 adapter to EDISeparator.
Hi Meghna,
Thank you o much for writing this blog.
This is an excellent blog, very well explained.
Regards
Anupam
Hi Meghna,
I have question to ask that is it possible to migrate Classical objects to ICO when we are going for migration from SAP 7.0 SP12 to SAP PO 7.4 ?
Both are on Dual Stack.If no is there is any other tool which help me out to do this activity.
Hi,
Yes, you can migration the classical configuration to ICO when both systems are dual-stack. The migration tool can be used for both dual and java-only stack.
Regards,
William Li
I dont have a doubt for dual stack migration infact I have a doubt that is it possible when we are migrating from PI &7.0 to PO 7.4 ?
Please reference: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0d7c7e4-af05-3110-f3a5-a6686fd3a0c9?QuickLink=index&…
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.
Hi Rajesh - Actually Bill was the one who designed this functionality (when it was a custom development APIs for Integration Directory - basically for moving objects from one system to another system specially for adapters). So echoing his reply above, it will work when both systems are dual stack). When he says it will work, it will work.
Cheers,
R-jay
Is the tool strictly for scenarios that are configured? We have a content that was developed in PI 7.1.1 and delivered in a tpz file by a third party. Is there a tool to perform the migration prior to configuring the scenarios?
HI Naiem,
do you refer to ERS content? Here you don't need any migration tool, this can be imported into the new system's ESR anyway
Alex
I have already done that, i guess the next step is to perform he migration.
Thanks
-Naiem
Meghna
We have installed NW 7.5 SP01 Java only PO. I am trying to use migration tool. I am able to establish the connection and search the objects using sender agreement option using drop down. I got list of objects and when try to perform next step am getting following error "No scenario passed migration checks; further processing not possible" I have tried on the scenario which has sender agreement. Please do you have any info on this error.
Please let me know.
Regards
HS
Hi Hari,
Did you try using "Scenario Name" option? are you facing issue with this as well?
Any specific reason you wanted to migrate using "Sender agreement".
Note: Issues should be raised in separate discussion 🙂 .
Thanks,
Binod
Binod-
Apologies to ask my query in this forum. I have got it resolved.
Thanks
HS
Hello All,
In fact, for the migration of PI system using Directory Migration Tools, I think that there are two scenarios. Number one, migrate from dual-stack to dual-stack. Number two, migrate from dual-stack to single-stack.
For dual-stack to dual-stack, the ABAP adapter (WS,IDOC etc.) will be automatically changed to WS and IDOC , or WS_AAE and IDOC_AAE ? Because the ABAP stack supports WS and IDOC. Java stack supports WS_AAE and IDOC_AAE. This is my confusing.
For dual-stack to single-stack, the ABAP adapter(WS, IDOC etc.) will be automatically changed to WS_AAE/SOAP and IDOC_AAE? Whether we need to manually change the CC to WS_AAE and IDOC_AAE?
Please kindly give some advises.
Appreciate your input.
Many thanks & best regards,
Hubery
Hi @ll
in Migration tool there is the in the area of rename rules there is an Import Option.
Does anyone has an clue how the structure of the Import file has to look like?
file Extension and file structure
I tried different formats without success.
thanks in advance.
Best regards
Jochen
Please do not resurrect old threads.
By all means create a NEW discussion and add a hyperlink to the old thread.
When you add to old threads you are very unlikely to get an answer... especially one as convoluted as this.
Hi Jochen,
Like Jocelyn mentioned create a new thread to get answers.
However the import file has to follow the format (the separator has to be "=").
Old Value = New Value
You can give a .txt for the file extension(shouldn't matter also).
Regards,
Sumit Khetawat
Thank you Meghna for precise information.
We are moving from PI 7.0 to 7.5, How do we migrate ESR objects ? The name changes for message to service interface etc. would be taken care by file transport or not ?
Regards,
Sachin Dhingra
I don't think you can migrate directly from 7.0 to 7.5 as it is not supported. Please check in SAP PAM. Migration of ESR will be TPZ dump and you can't rename the objects according to new naming conventions but can change naming conventions of configuration objects through SAP migration tool.
Hope this helps!
Let me know if you have any questions.
Regards
HS
Hi all,
Currently we are upgrading PI system from 7.0 Dual stack to 7.5 Dual stack.
I have some queries about the Integration directory Migration tool,
2. Can we create ICO’s in PI7.5 Dual Stack? in this case is it necessary integration directory migration tool?
Note:Please don’t suggest me to go for PO7.5 Single stack. It’s (7.5 Dual) already decided by management people because of ABAP custom tables, programs, stock holder etc.
Regards
Govind
Hello,
We want to migrate our PI system from MSSQL to Hana.
DMO doesn’t support ABAP/JAVA stack upgrade/migration to Hana in one step.
What options we have to migrate the DB to Hana?
1) Upgrade to PI 7.4 / 7.5 and after that, split instances and classical migration to Hana
2) Upgrade to PI 7.4 / 7.5, and install a fresh installation PI 7.5 on Hana, and after that migrate the objects to the new system.
Which is the best/recommended option?
Any suggestion?
Regards
Â
Â
Â
Great Tool for Migration...Blog is excellent and well explained... Thank you..
Hi,
Just wanted to link a description of the SAP Test Tool available from SP14 which can help with any migration scenarios:
https://goo.gl/vbqJ8x
Best Regards,
Michal Krawczyk