SAP NetWeaver dual stack (ABAP stack and Java stack installed as a so called "addin") has been adapted to improve life cycle management operations .
dual stack or dual-stack system
SAP system that contains installations of both Application Server ABAP ( and Application Server Java (AS Java).
A dual-stack system has the following characteristics:
- Common SID for all application servers and the database
- Common startup framework
- Common database (with different schemas for ABAP and Java)
Note: SAP does not recommed to setup Dual Stack Systems except if necessary (e.g. Solution Manager)
Please note the following:
Today dual stack is required for
- PI/XI
- Solution Manager
- Mobile up to NW 7.0
Optional Use case
- BI 7
- ESS scenarios in dual stack
- Java Usage Types in NetWeaver Systems (e.g. Enterprise Portal)
SAP strategy
- Running SAP NetWeaver application components in single stack
- Exception: Solution Manager will stay dual stack
SAP Application Server Setup recommendations
- Setup SAP systems as single stack whenever possible
Please see also note 1181025 .
Comments (2)
Oct 29, 2009
Doug Steckel says:
Oliver, Thank you for this excellent Wiki. I've been looking for a defina...Oliver,
Thank you for this excellent Wiki. I've been looking for a definative statement regarding dual stack architecture as it pertains to ESS and have not found it. At a ESS/MSS seminar recently Jack Xu said dual stack was officially unsupported for ESS as of EhP2 I believe. In your entry you list it as optional but later mention that it is strongly reccomended that dual stack only be used for officialy supported scenarios like solution manager.
So can I officially rule out dual stack for ESS/MSS?
Thanks again,
Doug
Jan 15, 2010
Jim Boyden says:
Hi, I'd also like to know what the difference between a dual-stack installation...Hi,
I'd also like to know what the difference between a dual-stack installation and a Java Add-in installation is. For example, I had an issue when installing SolMan in a distributed system. The only way I could get around it was to delete the Java schema and then re-install the Java Add-In separately on top of the existing ABAP Stack. So what I now have is an ABAP Stack with a Java Add-In rather than the clean standard dual stack installation.
Cheers,
Jim.