Database Reference
In-Depth Information
T
ABLE
1-4
Available Usage Types with NetWeaver Installation
NetWeaver usage types are software units that are to be installed and configured as per
the requirement of a given business scenario. Usage types can be combined with others in
one system or can be run separately in different systems. The AS ABAP and AS Java
NetWeaver usage types are also used as a foundation for other units.
Single-Stack System
A single-stack system is defined as a SAP system with either SAP NetWeaver AS ABAP or
AS Java as the foundation usage type. Examples of single-stack systems are SAP Enterprise
portal system running on NetWeaver AS Java as a foundation unit.
Dual-Stack System
A dual-stack system is defined as a SAP system where both SAP AS ABAP and AS Java
are used as foundation units. An example of a dual-stack system is SAP Process Integration.
A dual-stack system has one SID (System Identifier) and exactly one database with two dif-
ferent schema names (one for ABAP and one for the Java stack).
Dual Stacks vs. Separated Stacks
With the introduction of Business Suite 7 the official SAP recommendation is to install AS
ABAP and AS Java capabilities as separate single-stack systems when the installation op-
tions support this. This is referred to as a “separated stack” install. The latest versions of in-
stallation tools starting with SAP NetWeaver 7 Enhancement Package 1 reflect this recom-
mendation. For example, if a customer wants to install a business intelligence (BI) solution,
then it is recommended to install BI ABAP components (BI Content) on a single system
with AS ABAP and BI Java usage types in another separate system. Some solutions (Pro-
cess Integration, Mobile Infrastructure, and Solution Manager) are mandatory dual-stack in-
stallations at this time. Starting with SAP NetWeaver Mobile Infrastructure 7.1, a dual-stack
