cancel
Showing results for 
Search instead for 
Did you mean: 

question on PI 7.1 release restrictions

Former Member
0 Kudos

Hello folks, we are going to be upgrading to PI 7.1 EHP1 from PI 7.0 in our environment soon. Our DEV environment is on a unix server that also hosts EP and MDM usage types (on same physical server although on different filesystems alltogether). I came across SAP Note 1004107 that says, "

Upgrade: source system must be a dedicated PI system

Prerequisite for an Upgrade to SAP NetWeaver PI 7.1 is that the PI source system runs exclusively the following usage types and standalone engines: Integration Server, PI (PI Process Integration), AS (AS Java Application Server Java), AAS (AS ABAP Application Server ABAP), PCK (Partner Connectivity Kit ), PI-PCK (PI PCK Partner Connectivity Kit), Adapter Engine (J2EE). Prerequisite for an Upgrade to EHP 1 for SAP NetWeaver PI 7.1 is that the PI source system runs exclusively the following usage types and standalone engines: Integration Server, PI (PI Process Integration) , AS (AS Java Application Server Java), AAS (AS ABAP Application Server ABAP), PCK (Partner Connectivity Kit ), DI (DI Development Infrastructure), PI-PCK (PI PCK Partner Connectivity Kit), Adapter Engine (J2EE).

In that case, does the "system" count as a dedicated PI system since other usage types are on their own filesystems or is this considered a shared environment. This is important since it will determine the upgrade strategy we follow (upgrade vs. new install). Or does anyone have similar experience.

Thanks in advance!

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_grube
Active Contributor
0 Kudos

> In that case, does the "system" count as a dedicated PI system

Yes. It is not important, that other systems or on the same server.