In upgrade from PI 7.1 to PI 7.5 ( dual- usage) , is there is any connectivity issue of ECC 5.0

[Former Member]

Hello,

We are in the process of upgrade of our PI 7.1 to PI 7.5 ( dual- usage) Current connecting systems are:

ECC 5.0 - SAP_BASIS - 640 level 0013

SCM 5.0 - SAP_BASIS - 700 level 0014

Do any one has any idea ,if there is any connectivity issue of ECC 5.0 with PI 7.5 ( dual-usage) or is there any specific support pack we need to consider for this?

In case of Dual Usage ( 1 SID for ABAP + 1 SID for JAVA), do we need to connect ECC system to both SID seperately? or connecting to any one SID would suffice to take care of all scenarios for all adapater types (ABAP + JAVA stack).

If we decide to route our scenarios to JAVA stack(ie only to connect to JAVA SID), do we need to re-write all ABAP stack scenarios e.g. ccBPM. and vice-versa?

[MarioDeFelipe]

Hello Anshu

your ECC looks quite old, I assume that your connections to PI 7.1 will be based on proxy and Idoc mostly.

in PI 7.5 there is no dual stack, there is one ABAP and one JAVA systems, all separate. for PI only ABAP is optional, all the Java scenarios are based on ICOs, so you should reconfigure your idocs to use AAE, but I dont think that systems based on 640 can use AAE idocs.

so, my assumption is your only option will be to have ABAP (integration engine) and JAVA PI enviroments

[Former Member]

Thanks Mario,

My issue is if we are going to Dual Usage ( 1 SID for ABAP + 1 SID for JAVA), do we need to connect ECC system to both SID seperately? or connecting to any one SID would suffice to take care of all scenarios for all adapater types (ABAP + JAVA stack).

Also if we are going to connect ECC 5.0 system to dual-usage PI system( 1 SID for ABAP + 1 SID for JAVA) with any of SID(java or ABAP ), will our ABAP based mapping and ccBPM scenarios will work as it is currently working, and will JAVA SID receive calls SOAP adapter calls as it is currently sending to PI 7.1?

Thanks,

Anshu

[MarioDeFelipe]

Hello Anshu

what do you connect ECC to? basically;

a: you connect your ECC to your SLD (rz70 and sldapicust), probably PI SLD, this will be Java part

b: you connect ECC to PI for standard Idoc adapter, WE21 idoc ports and SM59, this is the PI ABAP part

c. you connect ECC to PI for proxies, transaction SXMB_ADMIN and SM59, this is the PI ABAP part, integration engine.

your abap mappings and ccbpm (based on abap) should work in your upgraded PI abap system but this is what you need to test. your PI java system will indeed receive your incoming SOAP calls and so on, the thing you do is separating SIDs, no more than that, you will have to adapt ports.

One of the PI upgrade post-steps is to configure your AS Java to talk to your AS ABAP. that part is in the upgrade guide.

Some calls will go to Java, and some calls will go to ABAP, similar as it was working in PI 7.1