Compare regular upgrade and ehpi upgrade in dual-stack

[Former Member]

We did several regular upgrades to BI 7.0 which has ABAP and JAVA with 2 different SIDs on seperate servers.

Now we plan to apply enhp2 on above BI7.0 using SAPehp tool on which we have no experience at all ( because we did it before uing SPAM and SAINT -- now we have to use SAPehp tool as required by the client).

In the regular upgrade for the synchronization of the dual stack, we follow this SAP doc:

If you run an ABAP-based server and a Java-based server in the same system, you have to upgrade

+them in parallel. The two upgrade processes require a synchronization

The upgrades for both parts, the ABAP-based server and the Java-based server , have to be synchronized.

For a proper synchronization, it is essential that you first start the upgrade of the ABAP-based server ,

that is, you start the upgrade program SAPup . SAPup then detects that there is a Java server installed in

the same system and prompts you to start the Java server upgrade as well.

The Java server upgarde can only be started after the configuration roadmap step of the ABAP server upgrade is done.

SAPup and SAPJup sync themselves at 3 different points: begining of the downtime; profile about to change;end of downtime.

My question is how similar is the ehpi upgrade to the regular upgrade in terms of above synchronization steps? Does

SAPehp tool detect the standalone JAVA system and wait for us to start the SAPehp tool on the JAVA side at some point?

Thanks if you can share your experience.

[sunny_pahuja2 · Accepted solution]

Hi Chirsty,

EHP upgrade is not like that. You should upgrade first your ABAP system and then Java system.

As you said both are on different server with separate SID then you can also run both upgrades in parallel.

Thanks

Sunny