Skip to Content
0

SAP PI upgrade from 7.02 to 7.4

Oct 19, 2016 at 10:36 AM

308

avatar image
Former Member

Hello All,

We are curently running on PI 7.0 EHP 2 and thinking of an upgrade as it will reach end of support in Dec '17. We also have the SAP NFe GRC component running within PI. (NFe-GRC is on one client and PI is in another).

We have around 200 interfaces which involves only 1 or 2 ccBPMs (apart from NFe asynch-synch mechanism). Need your helpful suggestions on which will be the best approach.

A -> Direct upgrade of PI system from 7.02 to 7.4 dual stack (I believe no much work from development perspective)

B -> Fresh installation of 7.4 single stack and migration of interfaces from 7.02 to 7.4 in a staged manner. So that exisitng PI installation will only be used as NFe GRC box and PI will be on a separate host. I have read SAP provides standard content (adapter modules) to achieve async-sync bridge for single stack.

Thanks!

Indudhar

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

avatar image
Former Member Oct 19, 2016 at 11:09 AM
2

Hi Indudhar,

The best option is option B which is fresh installation of PI 7.4 system and migrate the interfaces in a staged manner because future it will be only single stack PI system, SAP is going away from dual stack. In PI 7.5 they introduced dual usage which is java stack is on one system and ABAP stack is on one system. Check below document for decision making factors when you upgrade.

Decision Making Factors when Moving to SAP NetWeaver Process Integration 7.3 - Upgrade or New Installation with Phase-out

Yes PI single stack or dual stack you can use adapter modules for async/sync bridge. Check below link for more details.

Generic PI Async-Sync Bridge Configuration for Any Adapters

Regards,

Praveen.

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Indudhar,

I would second what Praveen has said as that is how we also did our migration from 7.11 to 7.4 last year. We knew that SAP's future strategy for PI is single stack so we didn't want to miss the train on that. We also took the staged approach as he has suggested and migrated things in several waves until everything was off the old PI system.

Regards,

Ryan Crosby

0

HI Indudhar,

One thing I forgot to mention was that taking the fresh installation approach we were also able to review naming conventions, organization of content and lean down the system from about 250+ individual interfaces to closer to 200 interfaces. The reason being is because there were many copies of custom interfaces that were essentially the same - so we were able to focus on generating more reusable content instead of point to point solutions. As a result our system is in a much better state as far as maintenance and support.

Regards,

Ryan Crosby

2
avatar image
Former Member Nov 11, 2016 at 01:03 PM
0

Thanks a lot Praveen and Ryan for this. We might go for the traditional dual stack option as a fresh installation / migration will definitely cost more, not to mention the additional project / resource cost. Yes, someday we again might need to go through all this as JAVA only is the solution of the future. However, currently we are running a bit tight on the budget and one of the main reasons we are going for the upgrade is to be within SAP's mainstream support window.

Thanks,

Indudhar

Share
10 |10000 characters needed characters left characters exceeded