Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

SAP had removed optional dual stack as useful deployment option already quite some time ago – but so far, only for optional dual-stack setups, while there were still some exceptions for mandatory dual-stack setups even in higher releases, such as with SAP NetWeaver 7.4. There, SAP Process Integration (SAP PI) still is (and will remain) a mandatory dual-stack system and the system provisioning procedures, such as installation and system copy, offer corresponding procedures also to handle those dual-stack systems.


With SAP NetWeaver 7.5, this now changes: as of this release, also SAP PI no longer is a dual-stack system, so no dual-stack systems are supported in this release – without exception.


This has implications about how you install SAP PI systems with release 7.5 or higher and about how you upgrade to such releases, as outlined below.


Installation of SAP PI 7.5 and higher

As a consequence, compared to previous releases, the standard installation of SAP PI 7.5 and higher does no longer install a dual-stack system, but consists of two installation procedures: one for a separate ABAP stack and one for a separate Java stack (besides the option to install the Advanced Adapter Engine Extended, which is based on AS Java only - for more information about SAP Process Integration release recommendations, see SAP Note 1515223). In detail:

  • First, you perform the installation of ‘Application Server ABAP for SAP Process Integration’, as offered by Software Provisioning Manager: there, also Java users for the Application Server Java (AS Java) for the SAP PI system are created and the ABAP system is prepared to get connected to the AS Java system.

  • Second, you perform the installation of ‘Application Server Java for SAP Process Integration’, also as offered by Software Provisioning Manager: there, the ‘Application Server Java for SAP Process Integration’ system uses the User Management Engine (UME) of the ‘Application Server ABAP for SAP Process Integration‘ system that you must have installed before (as outlined in the previous step).


Upgrade to SAP PI 7.5 SP1

After upgrading to SAP PI 7.5 SP1, you first have to split the still existing dual-stack system before you can use it productively – for this, the standard dual-stack split procedure that exists for quite some time now also supports SAP PI 7.5 SP1 and higher.


For more information about the dual-stack split procedure, see the Dual-Stack Split page in SAP Community Network and the dual-stack split guide available at - Software Logistics Toolset 1.0 - Documentation - Software Provisioning - Dual-Stack Split: Systems Based on SAP NW 7.1 and Higher.



Outlook at SAP Solution Manager 7.2

As you maybe know, also SAP Solution Manager 7.0 and 7.1 systems are mandatory dual-stack systems. With SAP Solution Manager 7.2, this is also planned to be changed. Also for these systems, we plan to extend the support of our reliable dual-stack split procedure. Expect to get more information as soon as the ramp-up of SAP Solution Manager 7.2 has started.