PI Upgrade from 7.0 to 7.3

[Former Member]

Hi,

We are planning for the upgrade of our PI system from PI 7.0 to PI 7.3.

The details of the PI system currently being used are as follows : -
1. The PI version used in the ABI landscape is 7.0 Service pack 21
2. The PI server is running on the Linux operating system
3. There are in total 1327 Interfaces that include 1334 mappings, in which 1198 are Graphical Mappings, 61 Java and 75 XSLT mappings approx.).
4. There are around 9 types of adapters being used in the PI system.

Our plan is to upgrade to PI 7.3 by performing a new installation of PI 7.3 package consisting of Dual stack (Both ABAP and JAVA) as we have 60%of interfaces running on BPM, we cannot go for a single stack (only JAVA) PI upgrade. Choosing of Single Stack (only JAVA) will result in rebuilding of all the interfaces which are running on BPM, as there willbe no BPM present in JAVA stack.

Please consider our system landscape, and suggest us which method needs to be adopted by us in order to perform the PI upgrade from 7.0 to 7.3

1. New installation of PI 7.3 Package Consisting of Dual Stack (Both ABAP and JAVA) or
2. Upgrading the existing version of PI 7.0 to PI 7.3 Package Consistingof Dual Stack (Both ABAP and JAVA) or
3. New installation of PI 7.3 Package Consisting of Single Stack (Only JAVA) or
4. Upgrading the existing version of PI 7.0 to PI 7.3 Package Consistingof Single Stack (Only JAVA).

We will be eagerly waiting for your valuable suggestion.

Regards,
Sowmya

[AndyK · Accepted solution]

Hi Sowmya,

we recently did an upgrade from 7.1 to 7.31 (dual stack). In this case the changes were minor and we only had some issues with some JDBC drivers since the java version changed.

Upgrading from 7.0 to 7.3 is a bigger step since the adapter framework core changes. This means that if you have any self developed adapter modules running you will have to adapt their coding.

XSLT and Graphical mappings will be no problem and can be kept 1:1 as well as your ccBPM in case of dual stack.

Since you have 60% ccBPM a JAVA only is not an option if you want to upgrade in a reasonable time in addition with Java only you would have to replace IDOC with IDOC_AAE, HTTP with HTTP_AAE, Proxy with SOAP communication channels. In addition all scenarios need to be configured as integrated configuration fo the JAVA only to support them.

So JAVA only for you in short term is not an option.

A new installation of 7.3 and then finally moving the interfaces manually from 7.0 to 7.3 involves quite some effort and showed a long duration till al is on 7.3 in the last upgrade we did. 

So I would suggest you option 2 with following approach:

1. Copy your production environment to a Sandbox system

2. Take some interfaces and make sure that they are working. Best would be to have diversity in interfaces used for testing to cover lots of PI functionality

3 Upgrade the system and then check these interfaces again

4. Finally decide on the upgrade approach form you test,quality and production environment (still can decide for a 7.3 new installation at this point if to many problems come up)

Perform the same step on test quality and production.

Hope this helps

Andreas

[pohian_koh · Accepted solution]

Hi Andreas,

Currently we are doing integration test on the PI7.31. Have you encountered any problem during the integration test? In our case, the processing stopped completely when it tries to call up the ABAP class and failed with error no receiver could be determined (the receiver will be determined after executing the ABAP class).

Your feedback is highly appreciated.

Thanks

Meavy

[Former Member]

Hi All,

Thanks for your suggestions.

We did a little more study on this by searching blogs and forums and found that Dual-stack will be supported till 2020 but any more enhancements on features will be done only for Java and not for ABAP.

We have 140 ccBPMs used. Anybody who has worked on Process Orchestration in PI 7.3.1 version can tell me:

1. Are SAP BPM and ccBPM similar in such a way that if we go for new installation of Java stack PI7.31, then we just need to look at the existing BPM and do a same copy in new version of PI (i.e., whole interface will be transported but we just have to do the blind copy of the IPs in PO) or

2. Are SAP BPM and ccBPM are different so that the BPMs have to be re designed and re built(i.e., we have to redevelop the entire interface)

I understood thet we have to build the BPMs from scratch but want to know will it be re designing or just copying...

Thanks

Sowmya

[Former Member]

Hi Sowmya,

you have to redesign the ccBPM interfaces in SAP BPM

Cheers

Hidayat

[Muniyappan]

Hi,

i would go for option one.

you can have separate server to install sap pi7.3 dual stack.

move the interfaces from dev to new system. and test it.

upgrading from 7.0 to 7.3 will be complex for this many interfaces.

Regards,

Muniyappan.

[vijay_kumar133]

Hi,

Option 1 is preferred and keep a note of all java mappings as they need may get effect after upgrade to new version of JDK.

As the interfaces are high and time is shot still its better go with option 1.

Regards

Vijay

[naveen_chichili]

Hi Sowmya,

I would suggest you to go with option 1 as there is lot of major changes upgrading from PI 7.0 to 7.3.

option 2 would be the alternative but you will have to do lot of groundwork for a smooth upgradation.

Thanks and Regards,

Naveen.

[baskar_gopalakrishnan2]

If you are preferring to go for dual stack (abap and Java) from 7.0 to 7.3,  I think the option one is the better. Reason you are upgrading the jdk and 7.3 supports 64 bit os.  So, IMO, doing the first option seems better. We upgraded from 7.1 to 7.3 with the upgrade like option2.  But in your case there is a big change from 7.0 to 7.3.

[former_member194612]

Hi Sowmya,

Please choose your 2nd option , it will enhance your performance and avail all other new functionality.

Because all your scenario's and users are already availble , so go with upgrade option 2

Thanks,

Satish