Skip to Content

Clarifications on PI 7.0 to PI 7.5 AEX Migration

Hi Experts,

We got a requirement with one of our customer to migrate from PI 7.0 to PI 7.5 AEX Java stack alone.

Reason for choosing PI 7.5 AEX is based on licencing and cost associated.

We are planning to go with new installation for PI 7.5 AEX.

Existing landscape has no BPM's.

Clarifications Required:

1. What is the approach we can prefer to migrate, is it a phased manner or single shot migration.

Brief count of Interfaces:

totally around 70+ interfaces to migrate from PI 7.0 to PI 7.5 AEX Java stack.

we have 15+ complex java mappings and few XSLT mappings.

2. Will migartion of JAVA mappings will work or do we need to do any changes to fit in PI 7.5 AEX.

3. ESR object to be exported as tpz file from existing production and should be imported into PI 7.5 AEX ( Any other best practice to be followed, please suggest)

4. Regarding with migrating Integration directory objects, can we still use SAP Directory content migration tool to move existing classic scenarios from PI 7.0 dual stact to PI 7.5 AEX java stack ICO scenarios

What kind of config is required for this tool to be accessed.

Request your valuable inputs please

Many Thanks,

--Kishore

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Aug 14, 2016 at 08:00 AM

    1. As you have just 70+ scenarios and i feel this is not a big number you can go in one shot instead of phase/wave wise.

    2.No need to do any changes in java mapping , you can go ahead and migrate them.

    3.ESR -7.0--->Dev PO-7.5--->.....--->Prod 7.5

    4.You may use migration tool but note this tool wont migrate the scenarios which doesn't has sender channel/agreement. This has to be done manually.

    Regarding the tool check below inks :

    https://help.sap.com/saphelp_nw74/helpdata/en/7e/717ce013624facafa76683099a56d5/content.htm

    Moving Integration Directory Artifacts from dual stack to single stack

    SAP tool to migrate dual stack ID objects to Integrated Configuration Objects (ICO) - PI 7.3 EHP1, SP07

    Br,

    Manoj

    Add a comment
    10|10000 characters needed characters exceeded

    • Manoj K Kishore Kumar N.T

      Kishore,

      Even we are currently under migration process now from 7.1 dual to 7.5 , for which we have done with almost interface go-live successfully and below are the points so far which we discovered so far.

      1.for inbound IDOC interfaces you need to map constant '1' to all the attributes(BEGIN,SEGMENT).

      2.Migration tool cant be used for interfaces which doesn't has sender channel/agreement you need to do the configuration manually in your new PO system.

      3.No need to re-compile java mapping , we didn't re-compile as 7.0 = JDK 1.4 and 7.5 = 1.8 so as you have compiled jars with 1.4 <1.8 there wont be any issues.

      4.IDOC_AAE setup configuration need to done for inbound/outbound interfaces , you will find a lots of bogs in SCN on this.

      5.SLD migration is usually take care by Basis team

      6.in case if you are using any interfaces with see-burger these need to migrated using SAP B2B Addon.

      Br,

      Manoj

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.