How to Deploy SAP NetWeaver

Dual Stack vs. Separated Stacks

Dirk Anthony, SAP NetWeaver Product Management Boris Zarske, SAP NetWeaver Product Management December 2008

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 2

01 Date 2008-08-20 2008-12-15 Description Initial Version Slide 22 added regarding dual stack installation of SAP Business Suite application systems © SAP 2008 / Dual Stack vs. Separated Stacks/ Page 3 .00 1.Document History The following table provides an overview on the most important document changes Version 1.

Separated Stacks/ Page 4 . General Recommendations © SAP 2008 / Dual Stack vs. Technical Comparison 2.Agenda 1.

Separated Stacks/ Page 5 .Dual Stack – Single Stack Systems Definition for Dual Stack: SAP system that contains installations of both Application Server ABAP and Application Server 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) Examples: ABAP single stack ERP Portal 7.0* ECC ABAP Mandatory Dual stack Process Integration Legende capability based on ABAP capability based on JAVA PI capability based on ABAP & JAVA JAVA single stack Portal EP EP-C Java Optional Dual stack Business Intelligence BI ABAP BEx Web BI Java EP Java Single system (SID) © SAP 2008 / Dual Stack vs.

this is an advantage for setups that require this consistency Con Dual Stack • Flexibility concerning SP Stacks/releases • Tightly coupled versions of the ABAP and the Java stack have different technological innovation speed • Coupling multiple capabilities with different roles in the system landscape can be detrimental © SAP 2008 / Dual Stack vs.Comparison Dual Stack vs. Separated Stacks: Integration / Coupling Pro Dual Stack • Always one consistent version for ABAP and Java parts . Separated Stacks/ Page 6 .

Separated Stacks/ Page 7 . update. Separated Stacks: Lifecycle Management Pro Dual Stack • Integrated installation. if load characteristics are different for ABAP and Java • It is not possible to stop/start ABAP independent from Java © SAP 2008 / Dual Stack vs. upgrade.Comparison Dual Stack vs. system copy procedures • Common operations handbook (at least for basis operation) • One integrated view on the system in the SAP Management Consoles – can be started and stopped consistently with one click • Reuse of local ABAP-only based tools like database monitoring/management or CCMS • Common and consistent backup/restore for ABAP and Java Con Dual Stack • Specialized administration skill set for ABAP and JAVA still required • Compared to single stack systems • more resources are consumed • installation efforts and maintenance downtimes are greater • ABAP and Java stacks cannot be isolated from each other with respect to failures and resource consumption • No separate scale-out possible.

this can be achieved also for separate systems) Con Dual Stack • The mapping between ABAP entities and Java entities is unintuitive (such as between ABAP roles and JEE groups) • Limited flexibility. Separated Stacks: User Management Pro Dual Stack • Integrated user management (however.Comparison Dual Stack vs. not all Java user management options can be used © SAP 2008 / Dual Stack vs. Separated Stacks/ Page 8 .

Dual Stack – Separated Stacks: Appraisal Dual Stack System Single Stack System Conclusion • Advantages for the dual stack in some areas of life-cycle management. only some goals reached on expense of other areas. such as installation + configuration effort (one-time activities!) • Benefits for database administration could also be achieved by MCOD • In some other areas tools & procedures have to be provided on landscape level like central monitoring. Separated Stacks/ Page 9 . such as flexibility or scalability © SAP 2008 / Dual Stack vs. change management or user management • Altogether.

if you have a landscape with both ABAP and Java parts. Separated Stacks/ Page 10 .The Way Forward: Unified Life-Cycle Management Spanning Multiple Systems Example: Unified Software Logistics  For example. …) Simplified transport management. Java. SAP NetWeaver Portal)    Combined transport requests for mixed sets of objects (ABAP. avoids inconsistent system states Central administration of all transports (ABAP. Java. …) in one UI Synchronized updates of mixed processes (ABAP/Java applications) Available as of SAP NetWeaver 7. you are looking for a solution for unified software logistics  Using dual stack systems does not address this challenge at all  Proposed solution: Enhanced Change & Transport System (CTS)  Enhancement of existing ABAP CTS to transport also non-ABAP objects: – – Java objects (J2EE.0 Support Package Stack (SPS) 12   Address challenges of mixed technologies by improved tool support on system landscape level © SAP 2008 / Dual Stack vs. Java EE) SAP-specific non-ABAP technologies (such as Web Dynpro Java.

one or multiple applications. multiple schemas “MCOD” © SAP 2008 / Dual Stack vs. multiple systems. such as SAP ERP and SAP CRM possible Migration of existing systems is possible All systems use same DB release One or multiple hosts. one database.Additional Deployment Option: MCOD Multiple Components in One Database (MCOD): Multiple independent and different applications are located in one database with separate schemas SAP ERP SAP SCM SAP CRM Optionally installable on one physical host SAP SRM SAP PLM Administrative opportunity      Multiple independent and different applications are located in one database One logical and physical database instance Point in time recovery of semantically related systems. Separated Stacks/ Page 11 .

Example: How MCOD Could Be Used To Compensate Dual Stack Systems Reduced database administration effort  Possible without explicit dual stack deployment by using the same database for separated systems  Even dual stack systems already use separate database schemas for ABAP and JAVA like MCOD Example: Enterprise Data Warehousing  Our general recommendation is to have two systems. one for BI ABAP. both systems could use one database with MCOD MCOD Database © SAP 2008 / Dual Stack vs. Separated Stacks/ Page 12 . one for BI Java  Nevertheless.

Separated Stacks/ Page 13 . General Recommendations © SAP 2008 / Dual Stack vs.Agenda 1. Technical Comparison 2.

Separated Stacks/ Page 14 • Higher flexibility by separating systems . JAVA) 2. Decision Integrated Technology Stacks • Combined usage of duties by dual stack system Distribution Model 1. Decision Deploy product capabilities Local Redundant Use • Individual usage by multiple local systems Centrally Shared • Reuse of platform capabilities within a central system Separated Technology Stacks • Separation of duties by separated technology stacks (ABAP. Decision Jointly Deployed • Less landscape complexity by using different capabilities in the same system Separately Deployed © SAP 2008 / Dual Stack vs.Deployment Of SAP Systems Within A Solution Landscape Architectural decisions to be taken 3.

Ease Landscape Setups By Stronger Guidance Clear recommendations by categorization of deployment options Possible Exception   Only useful for specific use cases Supported by SAP. Separated Stacks/ Page 15 • Alternative deployment options might have different benefits • Customer individual assessment not be compensated . but limitations might occur Option III General Recommendation   Option II Reasonable Alternative   Option I  Best choice for majority of typical landscape use cases Recommended by SAP’s strategy Accepted by a wide base of customers Useful choice for certain use cases or customer scenarios Supported and confirmed by SAP’s strategy Goal • Outlining main important aspects to be considered • Best considered trade-off between flexibility and simplicity • Applied to main building blocks of SAP products Consider © SAP 2008 / Dual Stack vs.

General Recommendation (I): Dual Stack vs. Separated Stacks/ Page 16 . Separated Stacks General Recommendation Generic Use Case  ABAP and JAVA based capabilities are deployed on single stack systems Approach  In general install ABAP + Java stacks in separate systems (where offered by SAP) Benefits     Separation of duties Independent scalability & performance Optimal resource consumption Maintenance downtime only for used stack Separated Single Stack Systems Considerations   Additional technical system to be administrated Additional <SID> appears in the landscape © SAP 2008 / Dual Stack vs.

1 a dual stack is no longer required © SAP 2008 / Dual Stack vs. Separated Stacks Reasonable Alternative Generic Use Cases   SAP NetWeaver capabilities require explicitly a dual stack installation (like PI today) SAP Solution Manager Approach  Mobile* Process Integration MI* PI Solution Manager Install a dual stack where this is required by the application or related SAP NetWeaver capability Benefits   Direct support by the installation procedure Automated connectivity ABAP Java Considerations Mandatory Dual Stack System * Starting with SAP NetWeaver Mobile 7.General Recommendation (II): Dual Stack vs. Separated Stacks/ Page 17  Future deployment layout might be changed to single stack by SAP with the next release .

g. Separated Stacks/ Page 18 .General Recommendation (III): Dual Stack vs. BI and BEx Web scenario) Approach  Install ABAP and JAVA stack in the same system Benefit   Setup and configuration effort only for one system Administration and software maintenance effort only for one system Optional Dual Stack System Considerations   No need to change existing systems today. dual stack systems might still be a valid solution (e. Separated Stacks Possible Exception Generic Use Case  In individual cases only. dual stack systems will still be supported Installation options for dual stack will be limited © SAP 2008 / Dual Stack vs.

dual stack systems might still be a valid solution (e. dual stack systems will still be supported  Installation options will be limited © SAP 2008 / Dual Stack vs.1 a dual stack is no longer required No need to change existing systems today.g. Separated Stacks/ Page 19 . Separated Stacks General Recommendation Reasonable Alternative Process Integration PI Solution Manager Mobile* Possible Exception MI* Separated Single Stack Systems ABAP Java Optional Dual Stack System Mandatory Dual Stack System Generic Use Case  Generic Use Cases  Generic Use Case  ABAP and JAVA based capabilities are deployed on single stack systems In general install ABAP + Java stacks in separate systems (where offered by SAP) Approach  SAP NetWeaver capabilities require explicitly a dual stack installation (like PI today)  SAP Solution Manager In individual cases only. BI and Bex Web scenario) Install ABAP and JAVA stack in the same system Approach  Approach  Benefit  Separation of duties  Independent scalability & performance  Optimal resource consumption  Maintenance downtime only for used stack Install a dual stack where this is required by the application or related capability Benefit  Benefits  Direct support by the installation procedure  Automated connectivity Setup and configuration effort only for one system  Administration and software maintenance effort only for one system Considerations  Considerations  Considerations  Additional technical system to be administrated  Additional <SID> appears in the landscape Deployment layout might be changed to single stack by SAP with the next release * Starting with SAP NetWeaver Mobile 7.General Recommendation (Summary): Dual Stack vs.

Separated Stacks/ Page 20 .Example: General Deployment of BEx Web Application General Recommendation System 1 Business Intelligence BI ABAP Possible Exception System 1 Business Intelligence & BEx Web BI Java BI ABAP EP Java System 2 BEx Web BI Java EP Java Separated Single Stacks Integrated Dual Stack Generic Use Case  Generic Use case  Execute web-template based BI queries within a simple infrastructure Execute web-template based BI queries within a highly flexible and scalable infrastructure Approach  Approach  Deployment of BI and BI JAVA on the same system Deployment of BI and BI JAVA on separated systems Benefit    Benefit  Automatic configuration of user management during installation  Combined maintenance and Start/Stop  Reduced number of systems High scalability (server itself can scale or easy split to two servers possible) ABAP and Java could be scaled independently Reduced database administration effort by MCOD possible © SAP 2008 / Dual Stack vs.

Separated Stacks/ Page 21 . default installation option for BI as offered by SAP installer is to install BI ABAP and BI Java on separate systems Latest version of installation already reflects this recommendation:  Installation of SAP NetWeaver 7. considering experiences from existing customer landscape layouts  Example of Enterprise Data Warehousing mentioned before:  SAP’s general recommendation to deploy BI and BEx Web capabilities as provided by SAP NetWeaver usage types BI and BI Java is to install two separate systems rather than installing one dual stack system  Therefore. existing BI dual stack installations will still be supported  SAP Note 1181025 describes how to install a BI dual stack system to stick to an existing landscape layout © SAP 2008 / Dual Stack vs.0 Enhancement Package 1 (EHP1) offers the following options for SAP systems:  Dual stack installation options for SAP NetWeaver PI and SAP NetWeaver Mobile only  Single stack installation options for AS ABAP systems  Single stack installation options for AS Java systems  Dual stack  Dual stack  ABAP only  Java only  Nevertheless.Consequence of Recommendation: Installation Options Offered by SAP Installation Tools SAP is going to provide clear recommendations for customers how to deploy different SAP NetWeaver capabilities in a solution landscape  Based on SAP’s product strategy.

0. Install the required Java components in a separate Java-based SAP system. SAP SRM 7. you have to proceed as follows: 1.0.0 ABAP © SAP 2008 / Dual Stack vs.0 ABAP SAP CRM CRM Server 7. SAP CRM 7.0 ABAP SAP SCM SCM Server 7. SAP PLM 7. you can no longer install Dual Stack Application Systems (ABAP+Java).0. Separated Stacks/ Page 22 .0 SAP ERP EHP4 for ECC Server 6. Install a separate ABAP-based SAP Business Suite system.0 ABAP SAP SRM SRM Server 7.0. SAP SCM 7. Configure the connection of the Java-based SAP system to the ABAP-based SAP Business Suite back-end system The SAP Business Suite 7 comprises: EHP4 for SAP ERP 6. If you want to use both SAP Business Suite ABAP and Java Components in your system landscape.SAP Business Suite in 2008 As of SAP Business Suite 7. 3. 2.

Feedback Boris Zarske Product Strategist Product Management SAP NetWeaver Dirk Anthony Product Strategist Product Management SAP NetWeaver SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Phone Fax E-Mail +49/6227/745546 +49/6227/78-29035 boris.com SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Phone Fax E-Mail +49/6227/765224 +49/6227/78-19164 dirk.anthony@sap.com .zarske@sap.

Sign up to vote on this title
UsefulNot useful