SAP Netweaver Architecture and Instances

SAP Netweaver Architecture

SAP NetWeaver Applicatio Server Structure (version 7.1 or higher) A SAP application runs on a SAP application server (AS) platform. A SAP AS platform can have a few installed seniors: 1) ABAP stack only, or A container 2) JAVA stack only, or J container 3) ABAP+JAVA dual stacks, or AJ container Depending upon the implementation of AS platform, a SAP AS platform can have a set of instances for ABAP, a set of instances for JAVA, or a set of instances for ABAP+JAVA. A SAP instance is a group of processes that are started/stopped at the same time. SAP NetWeaver is a product of AS server. With NetWeaver AS 7.x, it has the following instances: Primary Central Instance (PCI) Central Services Instance (CSI) Database Instance (DBI) Dialog Instance (DLI) However, the structure of NW AS 7.x is in a transit stage. The features or components of instances from v7.0, 7.1, 7.2 to 7.3 are varying. A summary is given below: (see more info at https://cw.sdn.sap.com/cw/docs/DOC-115506): Primary Central Instance (PCI)

ABAP primary central instance (DVEBMGS??) JAVA primary central instance (JC??) Every SAP AS server must have one primary central instance. for a server with A container, its PCI includes: Internet Communication Manager (ICM) ABAP dispatcher Work processes (dialog, batch, spool, update) Gateway Internet Graphics Service (IGS) message server /*moved to ASCS if ASCS exists or NW 7.2+ */ enqueue server /* moved to ASCS if ASCS exists or NW 7.2+ */for a server with J container, its PCI includes: Internet Communication Manager (ICM) /* only with NW 7.1+ */ Java dispatcher /* only with NW 7.1-, is replaced with ICM after */ Server processes Software Deployment Manager (SDM) /* only with NW 7.1-, and no longer used for 7.1+ */ Internet Graphics Service (IGS) for a server with AJ container, its PCI includes: ABAP: Internet Communication Manager (ICM) /* shared by JAVA stack */ ABAP: dispatcher ABAP: Work processes(dialog, batch, spool, update) ABAP: Gateway ABAP: Internet Graphics Service (IGS) /* shared by JAVA stack */ ABAP: message server /*moved to ASCS if ASCS exists or NW 7.2+ */ ABAP: enqueue server /*moved to ASCS if ASCS exists or NW 7.2+ */ JAVA: dispatcher /* only for NW 7.1- */ JAVA: server processes JAVA: Software Deployment Manager (SDM) /* only for NW 7.1- */ Central Services Instance (CSI) ABAP Central Services Instance (ASCS??) JAVA Central Services Instance (SCS??) A Central Services Instance (ASCS or SCS) consists of a message server and an enqueue server, and forms a basis of communication and synchronization for the Java or ABAP clusters. for a server with A container (i.e. A or AJ): NW 7.3- with HA feature: may have an ASCS NW 7.3+: always have an ASCS It includes: message server enqueue server /* handles only locks on data objects */ for a server with J container (i.e. J or AJ) : there is always an SCS instance. It includes: message server enqueue server /* handles logical database locks plus infrastructure locks */

 gateway Optionally, every CSI (ASCS or SCS) can have an enqueue replication server instance (ERS) ERS is a copy or backup for CSI lock table. When CSI instance fails, ERS can be used to resume its service. Normally, ERS just get incremental changes from CSI. Database Instance (DBI) database instance is a mandatory instance. Its a separate product that holds data for NW AS system. Logically, A container and J container each has its own data repository. Physically, their data are in the same database, but separated with its own schema. For A container, the schema name: SAP<sapSID> for J container, the schema name: SAP<sapSID>DB Dialog Instance (DLI) Dialog instances are optional, and thus treated as additional application server instances. Those additional dialog instances can be installed on separate hosts. A DLI or an additional application server instance, can be installed and act as a standalone gateway. That is, the server has just gateway process (gwrd) started, without activating other work processes. A standalone gateway is needed to enable the SLD to receive RFC calls from ABAP data suppliers. for a server with A container, its DLI includes: Internet Communication Manager (ICM) Dispatcher Work Processes (dialog, batch, spool, update) Gateway Internet Graphics Service (IGS) for a server with J container, its DLI includes: Internet Communication Manager (ICM) /* only with NW 7.1+ */ Java dispatcher /* only with NW 7.1-, is replaced with ICM after */ Server processes Internet Graphics Service (IGS) for a server with AJ container, its DLI includes: ABAP: Internet Communication Manager (ICM) /* shared by JAVA stack */ ABAP: dispatcher ABAP: Work processes(dialog, batch, spool, update) ABAP: Gateway ABAP: Internet Graphics Service (IGS) /* shared by JAVA stack */ JAVA: dispatcher /* only for NW 7.1- */ JAVA: server processes