Skip to Content

Since the availability of AEX with PI 7.3, many questions have been asked on how to migrate integration scenarios from PI 7.1 to AEX and if there are any tools to assist in the process. In this blog and an assocated article, I will compare the features and functions of the different releases and provide a guideline based on them. In addition, a java program can be download that can assist in the process by determining the potential tasks invovled in the migration.

AEX is a java-only installation of PI 7.3. Due to the advantages of a java-only deployment, such as improved performance, lessened hardware requirement and simplified installation process, many companies are seriously considering replacing the existing PI system with AEX. But, as we know, there are many ABAP features in the dual-stack installation that are being used today. Migrating to AEX will need to go through an evaluation process to determine feasibility and complexity.

An article has been written to discuss this very topic (the material is too much for a blog). This article contains the following:

  • Feature comparisons of the different releases.
  • How to identify which integration scenarios can be migrated, which cannot, and which can be but requires additional work.
  • Migration process.
  • A downloadable java program which will provide a report of all the scenarios identifying the migration tasks needed for each scenario.
  • References to other articles and papers relating to the migration process.

The article, Migration Guide to AEX of PI 7.3x for Integration Scenarios , can be referenced at:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0c92caf-3e44-2f10-169c-838b94d6fd0a

To report this post you need to login first.

27 Comments

You must be Logged on to comment or reply to a post.

  1. Gayatri Deshpande
    Hi WIlliam,

    Its just excellent!!

    I have a few questions as a curious developer

    1.What is the procedure for migrating the ESR objects in PI7.1 to PI7.3 and are there any restrictions on any ESR objects to be transported or all the objects can be transported without any restrictions?
    2.Is the migration procedure same for the te dual stack SAP PI7.3 upgrade scenerio as well?
    3.Is the report that is mentioned in the article is the replacement of manually finding the receivr determinations?Does it find the receiver determinations for the ccBPM,WS adapter,receiver rule,IDoc and HTTP adapters as well?
    4.Where to run that report and how?
    5.The second migration option that is Upgrade In place from PI7.1 to PI7.3,means we can directly upgrade the existing PI7.1 system to PI7.3 without actual installation of new PI7.3 ?Also after this upgrade can we access both PI7.1 and PI7.3 from the same system?
    6.As per the article what exactly do we transport,Integrated Configurations or Receiver Determinations.?Also,can you please put some focus on the Alerts and the ccBPM(not in details)objects transports?Also what kind of transport is recommended in this upgrade like File transport or CTS+ or any othere transport?

    As there may be a lot of questions from my side as I am very curious about this upgrade,please dont mind me.

    Thanks and regards,
    Gayatri

    (0) 
    1. William Li Post author
      Hi,
      Please see comments below:
      1.What is the procedure for migrating the ESR objects in PI7.1 to PI7.3 and are there any restrictions on any ESR objects to be transported or all the objects can be transported without any restrictions?
      ==> All ESR objects can be transported without problem.  However, objects such as “Integration Process”, which is ccBPM, cannot be used.

      2.Is the migration procedure same for the te dual stack SAP PI7.3 upgrade scenerio as well?
      ==> Dual-stack can be exported and imported directly, nothing more will need to be done.

      3.Is the report that is mentioned in the article is the replacement of manually finding the receivr determinations?Does it find the receiver determinations for the ccBPM,WS adapter,receiver rule,IDoc and HTTP adapters as well?
      ==>  Yes to all.

      4.Where to run that report and how?
      ==>  Run the report in the CMD window.  Direction is in the article.

      5.The second migration option that is Upgrade In place from PI7.1 to PI7.3,means we can directly upgrade the existing PI7.1 system to PI7.3 without actual installation of new PI7.3 ?
      ==>  No, you go through the upgrade process, which is to install PI 7.3 on top of PI 7.1.

      Also after this upgrade can we access both PI7.1 and PI7.3 from the same system?
      ==>  No, once you upgraded PI 7.1 to PI 7.3, PI 7.1 will no longer be available.  It is replaced by PI 7.3.

      6.As per the article what exactly do we transport,Integrated Configurations or Receiver Determinations.?
      ==>  When transporting from PI 7.1 to AEX of PI 7.3, you transport the Integrated Configuration.  Receiver Determination does not exist in AEX.

      Also,can you please put some focus on the Alerts and the ccBPM(not in details)objects transports?
      ==>  Alerts is not covered in this article.  Please reference the Related Content section at the end under PI 7.30.

      Also what kind of transport is recommended in this upgrade like File transport or CTS+ or any othere transport?
      ==>  Depends on you environment and governance.  For testing, you can use File transport, which is the easiest to do.

      (0) 
      1. Gayatri Deshpande
        Hi WIlliam,

        Thanks for the quick reply.

        I have a few questions

        1.As per the article ,we are finding the receiver determination,why,if we are migrating the integrated configuration?Also,this is applicable to Single Java stack only,right?

        2.If there is dual stack upgrade,then can we directly create the /tpz of the PI7.1 objects and on local system and import those .tpzs in the PI7.3?

        3.Also,how to run the report mentioned in the article ?On local system or server system and how?Do I do it the following way
        -create .jar file of the code on loacal system
        -run it in DOS

        Please let me know.

        Thanks once again,
        Gayatri

        (0) 
        1. William Li Post author
          Hi,
          Please see replay:
          1.As per the article ,we are finding the receiver determination,why,if we are migrating the integrated configuration?Also,this is applicable to Single Java stack only,right?
          ==> Integrated Configration (ICO) is for AAE, which is used by AEX.  In moving ICO, we just need to export and import.

          2.If there is dual stack upgrade,then can we directly create the /tpz of the PI7.1 objects and on local system and import those .tpzs in the PI7.3?
          ==> Yes, you can do this for dual-stack installation.  This is one of the migration options, to import everything into PI 7.3 dual-stack, then take the time to move the “classical” configuration to ICO, then to AEX.

          3.Also,how to run the report mentioned in the article ?On local system or server system and how?Do I do it the following way
          -create .jar file of the code on loacal system
          -run it in DOS
          ==>  Report can be used on your local PC as long it has access to the PI server.  Yes, you run the report in the DOS CMD mode.

          Regards,
          Bill

          (0) 
          1. Gayatri Deshpande
            Hi WIlliam,

            Thanks once again!!

            As I am supposed to work on the PI7.1 to PI7.3(single or dual stack) shortly I have following questions.

            1.Are there any prerequisites for this PI7.1 to PI7.3(single or dual stack) upgrade process like use of maintainence optimizer in Solution Manager or use of any other tool,any prerequisites?
            2.We will have to install the PI7.3 on PI7.1 before doing so we can store the PI7.1 objects as .tpz files on local desktop as well,right?
            3.After installing the PI7.3 dual stack we can directly import the objects stored on local desktop to PI7.3 dual stack,right?
            4.But for migrating/transporting those objects on PI7.3 dual stack to PI7.3 single stack we will have to installl PI7.3 single stack on some other system or PI7.3 dual stack also serves the purpose of PI7.3 single stack,is it?If not how to move objects from PI7.3 dual stack to PI7.3 single stack?

            Thanks once again,
            Gayatri

            (0) 
            1. William Li Post author
              Please see comments below:

              1.Are there any prerequisites for this PI7.1 to PI7.3(single or dual stack) upgrade process like use of maintainence optimizer in Solution Manager or use of any other tool,any prerequisites?
              ==>  Upgrade is not possible from dual-stack to single-stack.  Dual-stack to single-stack will have to be a migration.

              2.We will have to install the PI7.3 on PI7.1 before doing so we can store the PI7.1 objects as .tpz files on local desktop as well,right?
              ==>  If you are doing an upgrade-in-place, you should not need to export anything, but it is always a good practice to do so, for backup purposes.  If you install a separate PI 7.3 system, then, yes, you will have to export/import the ESR and ID objects.  Please reference the installation documentation for details. 

              3.After installing the PI7.3 dual stack we can directly import the objects stored on local desktop to PI7.3 dual stack,right?
              ==>  Yes, for dual-stack.

              4.But for migrating/transporting those objects on PI7.3 dual stack to PI7.3 single stack we will have to installl PI7.3 single stack on some other system or PI7.3 dual stack also serves the purpose of PI7.3 single stack,is it?If not how to move objects from PI7.3 dual stack to PI7.3 single stack?
              ==>  Please reference the article for the gaps between the dual-stack and single-stack of the different releases.  This will give you an idea on what can be migrated and what cannot, and the work involved.  You cannot just import the objects from dual-stack to single stack.  Many of the objects in the dual-stack (e.g. receiver determination, interface determination, etc) will not be there for the single-stack.  You will have to convert the integration scenarios to Integrated Configuration before you can do export/import from dual-stack to single-stack.

              (0) 
  2. Martin Sommer
    Hi William, I was awaiting such a document, well done! And even a report, great job! Thanks

    Can you please help me with an issue regarding the program?

    When I run the report directly on the PI server, I get a “javax.xml.ws.WebServiceException: Unsupported endpoint address: / [long stacktrace…]
    at com.migration.pi71.rcvrdeter.RcvrDeter.query(RcvrDeter.java:40)
    at com.migration.pi71.main.Report.GetReport(Report.java:29)
    at com.migration.pi71.main.Report.main(Report.java:226)”

    When I run on my PC, I get a “Exception in thread “main” com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 404: Not Found [long stacktrace…]
    at com.migration.pi71.rcvrdeter.RcvrDeter.query(RcvrDeter.java:40)
    at com.migration.pi71.main.Report.GetReport(Report.java:29)
    at com.migration.pi71.main.Report.main(Report.java:226)”

    Java version is 1.6 on both machines.

    What is the problem here? Thanks, best regards, Martin

    (0) 
    1. William Li Post author
      What is the PI release?

      The java program is using the web services on the PI 7.1 server. This error indicates that the web service cannot be found.

      Try to verify by using WSNavigator:
      http://:/wsnavigator

      Then, search the “Provider System” for the search string “receiver”. You should see the interface name “ReceiverAgreementIn”.

      If not, then this web service is not available, but it should be.

      (0) 
      1. Martin Sommer

        Hi William, the release is 7.10.

        I only see the service sap.com/com.sap.xi.directory.webservices640_com.sap.aii.ibdir.sbeans.api.receiverAgreement_ReceiverAgreementServiceVi, not ReceiverAgreementIn.

        If not, then this web service is not available, but it should be.

        Is there any configuration or content missing?

        Thanks for your help, best regards, Martin

        (0) 
          1. Martin Sommer

            Hi William & thanks for the quick answer. Any possibility to make your great program work with the 7.10 webservices? Best regards, Martin

            (0) 
            1. William Li Post author

              Hi Martin,

              The web service in PI 7.1 can only work with configuration objects using the interfaces defined as “XI30-Compatible”.  Therefore, it will have very limited application.

              “XI30-Compatible” interfaces were carried over from PI 7.0 and XI 3.0.  If you have been using PI 7.1 for a while, it is most likely you no longer used this option during your design.

              Regards,

              Bill

              (0) 
  3. Martin Sommer

    Hi William, will SAP provide a migration tool which generates PI 7.3 integrated configurations from PI 7.1 objects (collaboration agreements, receiver/interface determination)? This would considerably speed up migration.

    Best regards, Martin

    (0) 
    1. William Li Post author

      Hi Martin,

      Yes, SAP plans to have a migration tool which will configure the ICO using the “classical” configurations.  The tool is planned for release in PI 7.31 SP7, which is scheduled for end of Q1/2013.

      Regards,

      Bill

      (0) 
  4. Martin Sommer

    Hi again William, I have 2 questions regarding routing…

    1) receiver rule on AEX:

    – is there any appropriate replacement (besides extended receiver determination using value mapping groups)?

    – when will it be available functionality on AEX?

    2) there aren’t any context objects for the IDoc_AAE adapter yet, when will that be available?

    Thanks and best regards, Martin

    (0) 
    1. William Li Post author

      Hi,

      I am looking at PI 7.31 SP4.

      With Extended Receiver Determination, I can use Operations Mapping for determining routing.

      I can use Context Objects when I configure rules for receivers.

      Regards,

      William

      (0) 
      1. Martin Sommer

        Hi William, I was wondering when the following features will be available for PI 7.31 AEX:

        1) receiver rules

        2) context objects for IDoc_AAE adapter

        Thanks for your help and best regards, Martin

        (0) 
        1. William Li Post author

          Hi,

          As far as I know, Receiver Rule is on the list for AEX, but nothing planned.

          For Context Object, not sure what you mean for IDoc_AAE adapter.

          Regards,

          William

          (0) 
          1. Martin Sommer

            Hi again William, it would be extremely useful to have receiver rules on AEX in order to decouple the actual condition values from the receiver determination. We have an ORDERS IDoc scenario being routed to 10 different vendors (more vendors to come). It is cumbersome to maintain the conditions in the receiver determination due to different vendor numbers in dev, test & prod and the fact that the condition values are overwritten when transport the integrated configuration.

            The traditional IDoc adapter of the ABAP integration engine e.g. has RCVPRN | http://sap.com/xi/XI/System/IDoc as a Technical context object. This does not work for IDoc_AAE, resulting in that we have to use an XPath //RCVPRN as workaround. The main advantage of context objects for us is that they can be reused.

            Regards, Martin

            (0) 
  5. sudhakar babu

    Hi Experts,

    In My project i have todo secuirty upgrade in PI(7.1 to 7.1) , solman systems….so Iam new to this upgrade… I request you to please provide som Upgarde activity plan templates…and i want knnow how we have to start upgarde activites from Security perspectuive.Iam looking for the help..anyone can you please help onthat

    Thanks,Sudhakar

    (0) 
  6. Daniel KIng

    William–

    After significant digging, I have been unable to find any official documentation whether the migration from dual-stack (7.1/7.11/7.3/7.31) to PI 7.4 AEX (Java-only) is technically the same as to 7.31.  The OSS notes indicate that 7.31 and 7.4 share the same code base for PI, and I see evidence that some people have in fact been trying to go from 7.3x dual-stack to 7.4 single-stack without upgrading the 7.3 dual-stack system first.  Are you aware if this is a supported procedure?

    Regards,

    –Dan King

    (0) 
    1. William Li Post author

      Hi Dan,

      Yes, the migration from any dual-stack PI to AEX is the same, including the use of the Migration Tool.

      Regards,

      William

      (0) 
  7. Federico del Bagno

    Hi William,

        I have tried to execute the Migration Tool Report without success. This is the error I get:

    javax.xml.ws.WebServiceException: Unsupported endpoint address: /

    I’m trying to execute it with a SAP PI 7.11 SP8. I have checked and confirmed the roles required. In my local machine I’m using JRE jdk1.6.0_10

    I have also confirmed thru the WSNavigator that the service ReceiverDeterminationQuery returns information as excepted.

    I even launched the .jar from thw NWDS in debug mode, the url is correctly formed, the problem seems to be with the method getReceiverDeterminationIn_Port.

    Any idea what else could I try to make it work.

    We are evaluating to migrate to PI 7.4 and install a java only single stack enviroment. This tool would help us a lot, we have over 450+ interfaces in our PI.

    Thanks in advance.

    (0) 

Leave a Reply