SAP NetWeaver offers a comprehensive set of different capabilities as described in the respective sections of the Technology Map. Based on the determined list of required capabilities and the individual considerations of your planned solution landscape layout, you have to decide, how to deploy these capabilities such as SAP NetWeaver Business Intelligence or SAP NetWeaver Process Integration within your system landscape.
- Architechtural Decisions
- Deployment Options
- Getting Started
- Deployment Recommendations
- Related Information
To derive the right deployment option three architectural decisions have to be taken:
1. Decision: Centrally Shared vs. Local Redundant Use
Providing a certain set of SAP NetWeaver capabilities centrally and shared by multiple application systems is a typical pattern that is seen in system landscapes. The following advantages are related to this strategy:
- Achieve cost reduction by sharing the set of capabilities
- Drive standardization and consolidation by deploying the capabilities centrally rather than locally in multiple application systems
- Combine innovation and stability by providing new or updated functionality centrally that might or might not to be consumed by the multiple local application systems
2. Decision: Jointly vs. Separately Deployed
SAP NetWeaver in general provides the possibility to jointly deploy different capabilities, such as SAP NetWeaver Portal or SAP NetWeaver Business Intelligence in the same system. By contrast, you can also deploy capabilities in separate systems, if this flexibility is needed by your landscape design.
3. Decision: Integrated vs. Separated Technology Stacks
Some SAP NetWeaver capabilities are pure JAVA based, some require pure ABAP, some require both (such as SAP NetWeaver Process Integration). All three technical deployment options are supported by the SAP NetWeaver Application Server today. However, if you have the flexibility to choose an option among these three possibilities, the pros and cons have carefully to be considered.
SAP NetWeaver supports a high level of flexibility for different deployment options with respect to the mentioned architectural decisions. However, the optimal landscape layout is mostly a trade-off between flexibility and simplicity. Dependent on the specific situation and the kind of capabilities that should be deployed, SAP is going to provide clear recommendations, how to deploy SAP NetWeaver within your solution landscape. Categorization of deployment options will provide a quick and easy overview of typical landscape setups, based on main customer needs and in line with SAP's product strategy. Definition and usage of a consistent framework for deployment recommendations helps to provide a comprehensive overview across the complete SAP NetWeaver platform and underlines SAP's approach for driving system landscape governance. Detailed information will be published below.
SAP has developed a framework to provide consistent deployment recommendations for the complete SAP NetWeaver platform. The presentation describes the framework and the generic approach, how to design the best solution landscape.
The SAP NetWeaver Application Server can be installed as dual stack or single stack system. This presentation contains a technical comparison of both deployment options, resulting in clear deployment recommendations based on the framework mentioned above.
Customers upgrading to the SAP Business Suite 7 have to decide, how SAP NetWeaver should be deployed within their solution landscape to achieve the best trade-off between flexibility and simplicity. The presentation outlines recommendations for landscape setups for some of the main SAP NetWeaver integration capabilities used by the SAP Business Suite.
Dependent on the targeted use cases there are several possibilities, how to design a portal landscape. Considering these facts and also reflecting SAP's actual portal strategy, this presentation provides a clear message about the recommended landscape setups for the portal with SAP NetWeaver 7.0. In addition recommendations for the deployment of Adobe Document Service are attached.
How should SAP NetWeaver Business Warehouse capabilities deployed within a SAP Business Suite 7 solution landscape ? Should the Java-based BW web template functionality be deployed separately from the ABAP-based Business Warehouse ? This presentation answers these questions, describes the typical deployment patterns of Business Warehouse capabilities in SAP NetWeaver 7.0 and provides clear recommendations, when to use which pattern.
Starting with SAP NetWeaver Process Integration 7.1 or SAP NetWeaver Composition Environment 7.1 new SOA middleware capabilities like the Enterprise Service Repository or Services Registry are available. Based on the established recommendation framework, the presentation provides clear guidance, how these capabilities should be deployed within a system landscape, dependent on the SOA use case the customer is focusing on. Furthermore recommended landscape setups for SAP NetWeaver PI are enclosed.
- Guiding Principles for reshaping your SAP ERP Landscape
- Upgrading to the Latest Release of SAP NetWeaver? What You Need to Know About the Interoperability of Old and New SAP Systems
- System landscape directory - planning guide
- Best practice for Implementing CTS+
- SAP Netweaver based System Landscapes - Architectural Principles