Skip to Content

SAP PI dual stack split and then use only Java

Hello experts,

we've got an SAP PI dual stack installation 7.31, with many ccBPMs. In order to minimize risk we are planning to do an upgrade to 7.5 with split.

After we are planning to move ccBPM to AEX (BPM), in 2021. After all ccBPM are migrated, we don't need ABAP stack anymore, so how can we "uninstall" ABAP system? Is there any restriction? Is there a guide for uninstallation of ABAP stack on a split installation of PI?

Regards.

Add a comment
10|10000 characters needed characters exceeded

  • Hi Antonio,


    May I know what you mean by "minimizing risk" to have an in-place upgrade from SAP PI 7.31 dual-stack to SAP PI 7.5 Dual Usage Type? Is it less risky to have an in-place upgrade instead of migrating the PI 7.31 scenarios/objects to new installations of either SAP PI 7.5 Dual Usage Type or SAP PO 7.5?

    Regards

Assigned Tags

Related questions

5 Answers

  • Best Answer
    Posted on Jul 13, 2020 at 09:47 AM

    Dear customers,

    It is not supported to uninstall the Abap Part from the Dual Usage Type of PI 7.5 and use the Java Part standalone. The Problem is, that the User Management is still on the Abap side and there is no way to get it migrated to the Java Part.

    Best Regards,

    Elke Döring

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 10, 2020 at 12:46 PM

    Currently this seems not supported, see https://launchpad.support.sap.com/#/notes/1515223. There's no in place upgrade from an dual stack (read that again) to an PI AEX or PO. There is (and you are doing just that) an in-place upgrade from PI 7.x dual stack to PI dual usage (read that again, too :-) 7.5.

    However, there is also currently (at least looking at the documentation I found) no path from dual usage to SAP PI AEX or SAP PO.

    An in-place upgrade from SAP PI Dual Stack to AEX is not supported, this can only be done via migration, i.e., side-by-side installation of AEX and migration of ESR and Directory content. When moving from SAP PI Dual Stack 7.3/7.31 to the recommended version of SAP PO, an in-place upgrade is not supported; this requires a migration. The move from SAP PO 7.31 to the highest version of SAP PO can be done directly in one step; there are no intermediate steps required.

    (disclaimer: the above text is in a paragraph titled "Customers of SAP Process Integration 7.3 and 7.31 / SAP Process Orchestration 7.31:" but within the text, SAP also states "For SAP PI / SAP PO, releases 7.31 and 7.4 do share the same Java code line. Since we do not invest in the ABAP part of SAP PI any more, i.e., all new features mainly go into the Java part, both releases do not differ from functionality point of view.")

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 13, 2020 at 12:28 PM

    We have no plans to support this in future as the Dual Usage in NW 7,5 is also supported until 2027.

    Best Regards,

    Elke Döring

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 13, 2020 at 05:54 PM

    Many thanks Elke!!

    Now it is clear for me.

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 16, 2020 at 10:40 AM

    Hello Francis, I meant to less effort, because we have several options:

    - Split

    - go to PI AEX - migrate all ccBPM to iflows or Java developments

    - go to PO - migrate all ccBPM to iflow or BPM

    I think split is less risky, but has other disadvantages.

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

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.