Skip to Content

Dual-Stack Split



SAP Business Suite 7i2011 is the last SAP Business Suite release with dual-stack support:

  • That is, as of SAP Business Suite 7i2011, it will no longer be possible to upgrade a dual-stack SAP Business Suite system to a higher release.
  • Please be aware that also SAP NetWeaver sytems that have SAP Business Suite components deployed might be treated as SAP Business Suite systems in this regard.
  • Already as of SAP Business Suite 7, you can no longer install dual-stack SAP Business Suite application systems.
  • For more information, see SAP Note 1816819 (SMP login required).

The same applies for SAP NetWeaver 7.31: you won't be able to upgrade optional dual-stack SAP NetWeaver systems to SAP NetWeaver 7.4 or higher and as of SAP NetWeaver 7.0 Enhancement Package 1, you can no longer install optional dual-stack SAP NetWeaver application systems - for more information, read the roadmap document SAP NetWeaver Discontinues Dual-Stack.

Therefore, SAP recommends you to move away from dual-stack SAP systems where possible, for which SAP is offering a corresponding procedure as outlined below - only in very few cases, dual-stack is still mandatory:

  • SAP Process Integration:
    • SAP Process Integration with a release ≤ 7.4 remain mandatory dual-stack systems - so, you can install new dual-stack SAP Process Integration systems with such a release and you can upgrade dual-stack SAP Process Integration systems to 7.4.
    • As of SAP Process Integration 7.5, dual stack is no longer supported. The standard installation of SAP Process Integration system with this release comprises of two installation procedures, one for the ABAP stack and one for the separate Java stack. After upgrading to SAP Process Integration 7.5 SP1, you have to split your dual-stack system before you can use it productively - for this, the standard dual-stack split procedure (as outlined below) now also supports SAP Process Integration systems as of release 7.5 SP1. For more information, also the this blog.
    • Starting with SAP NetWeaver 7.3x, there are also the Java-only offerings Advanced Adapter Engine Extended (covering stateless message processing) and SAP Process Orchestration (covering in addition also SAP BPM capabilities).
  • SAP Solution Manager:
    • SAP Solution Manager 7.1 systems remain mandatory dual-stack systems - you can install new dual-stack SAP Solution Manager 7.1 systems and upgrade dual-stack systems to this release.
    • SAP Solution Manager 7.2 is no longer dual-stack - therefore, the standard installation consists of two activities, the installation of an ABAP system and the installation of a separate Java system.
    • Systems upgraded to SAP Solution Manager 7.2 have to be split.
  • SAP NetWeaver systems with product instance Mobile Infrastructure (MI) are mandatory dual-stack systems. SAP NetWeaver Mobile Infrastructure is not part of SAP NetWeaver 7.31 or SAP NetWeaver 7.4 - therefore, dual-stack deployments of SAP NetWeaver Mobile Infrastructure cannot be upgraded anyhow, but have to be migrated.
  • For more information (also concerning the migration options for SAP Process Integration and SAP NetWeaver Mobile Infrastructure), see the dual-stack split overview presentation also linked in the Further Information section below.

While existing dual-stack systems remain supported in their current release, you can adapt your system setups to the recommendation from SAP and prepare future upgrades with the help of the dual-stack split procedure.



With the release of SL Toolset 1.0 SPS09, the dual-stack split procedure got integrated into the software provisioning manager 1.0. Improvements to the dual-stack split procedure are no longer available as standalone tool.

The dual-stack split procedure being offered as option in software provisioning manager 1.0 provides three main features to make the procedure easy and reliable for customers:

  1. The separation of the Java stack of a dual-stack source system into a new SAP system (by copying the Java parts into a new Java system)
  2. The automated post-configuration re-establishing the connectivity between the separated Java system and ABAP system for certain scenarios
  3. Removal of the Java stack from the source system, reducing it to an ABAP-only system

The following video shows a demo of the end-to-end dual-stack split process (using the old standalone tool version - latest handling will differ slightly) - including split, installation of a new Java system and removal of the Java stack from the former dual-stack system (duration: 12 minutes - video only, no audio!):

How to Get It?

The procedure is available for many platforms and scenarios already today.  It is provided as part of software provisioning manager 1.0 with Software Logistics Toolset 1.0.

Feature Requests

Influence the future of the dual-stack split procedure by collaborating on ideas for new features in SAP Idea Place, the public channel to participate in innovation at SAP. Dual-stack split belongs to the idea session Software Logistics, category System Transformation. Submit new ideas, vote for existing ideas and connect directly with the team that builds the dual-stack split procedure!

Further Information

  • This presentation provides an overview of SAP's approach for dual-stack systems and the dual-stack split procedure
  • This presentation provides technical details about the dual-stack split procedure

  • This blog provides more overview information about the dual-stack split
  • This Wiki page provides screenshots of a dual-stack split procedure

  • For more information about dual-stack support for systems with SAP Business Suite components installed, see SAP Note 1816819 (Dual-Stack support for Business Suite systems – SMP login required) and the PDF file attached to the SAP Note with tables providing detailed information about supported deployments. Below, you can find an example screenshot from this PDF file (for the latest version, see the SAP Note):
  • For more information about use cases for splitting dual-stack systems, see SAP Note 1655335 (Use Cases for Splitting Dual-Stack Systems – SMP login required)
  • For more information about current coverage and restrictions, see SAP Note 1797362 (Dual-Stack Split for Systems Based on SAP NetWeaver – SMP login required)
  • For more information about the procedure and how to perform it, see the Dual-Stack Split Guide - SAP Systems based on SAP NetWeaver ABAP + Java on <Platform> available at: Software Logistics Toolset 1.0 (SMP login required) under System Provisioning.
  • For more information about follow-up activities in the system landscape directory of SAP NetWeaver, see the corresponding blog Dual-Stack Split – How to Ensure Correct Technical System Data in SLD and LMDB after the Split from Wolf Hengevoss and the Landscape Management page.
  • For troubleshooting information, see the list of Troubleshooting documents for Software Provisioning Manager