SAP NetWeaver Application Server

It is not possible to add the new link because it would replace an existing, longer link.

Line 2:

The architecture of SAP Web Application Server can be separated into 5 areas:

; Presentation layer : In the presentation layer, the user interface can be developed with [[JavaServer Pages]] (JSP), Business Server Pages (BSP), or with [[Web Dynpro]] technology. The underlying business layer provides the business content in Java or ABAP.

; Business layer : The business layer consists of a [[J2EE]] certified run-time environment that processes the requests passed from the Internet Communication Manager (ICM) and dynamically generates the responses. The business logic can be written either in ABAP or in Java based on the J2EE standard. Developers can implement business logic and persistence with [[Enterprise JavaBeans]] (EJB) using the J2EE environment. Developers can also access the business objects of applications running in the ABAP environment to benefit from their business logic and persistence.

; Business layer : The business layer consists of a [[J2EE]] certified run-time environment that processes the requests passed from the Internet Communication Manager (ICM) and dynamically generates the responses. The business logic can be written either in ABAP or in Java based on the J2EE standard. Developers can implement business logic and persistence with Enterprise [[JavaBeans]] (EJB) using the J2EE environment. Developers can also access the business objects of applications running in the ABAP environment to benefit from their business logic and persistence.

; Integration layer : The local integration engine is an integral part of SAP Web AS and allows instant connection to [[SAP NetWeaver Process Integration]] (SAP PI; formerly called SAP Exchange Infrastructure). The local integration engine provides messaging services that exchange messages between the components that are connected in SAP PI.

; Connectivity layer : The Internet Communication Manager (ICM) dispatches user interface requests to the presentation layer and provides a single framework for connectivity using various communication protocols. Currently, modules are available for [[Hypertext Transfer Protocol]] (HTTP), [[HTTPS]] (extension of HTTP running under the [[Secure Sockets Layer]] (SSL)), [[Simple Mail Transfer Protocol]] (SMTP), [[Simple Object Access Protocol]] (SOAP), and [[FastCGI|Fast Common Gateway Interface]] (FastCGI).

@@ Line 2: / Line 2: @@
 The architecture of SAP Web Application Server can be separated into 5 areas:
 ; Presentation layer : In the presentation layer, the user interface can be developed with [[JavaServer Pages]] (JSP), Business Server Pages (BSP), or with [[Web Dynpro]] technology. The underlying business layer provides the business content in Java or ABAP.
-; Business layer : The business layer consists of a [[J2EE]] certified run-time environment that processes the requests passed from the Internet Communication Manager (ICM) and dynamically generates the responses. The business logic can be written either in ABAP or in Java based on the J2EE standard. Developers can implement business logic and persistence with [[Enterprise JavaBeans]] (EJB) using the J2EE environment. Developers can also access the business objects of applications running in the ABAP environment to benefit from their business logic and persistence.
+; Business layer : The business layer consists of a [[J2EE]] certified run-time environment that processes the requests passed from the Internet Communication Manager (ICM) and dynamically generates the responses. The business logic can be written either in ABAP or in Java based on the J2EE standard. Developers can implement business logic and persistence with Enterprise [[JavaBeans]] (EJB) using the J2EE environment. Developers can also access the business objects of applications running in the ABAP environment to benefit from their business logic and persistence.
 ; Integration layer : The local integration engine is an integral part of SAP Web AS and allows instant connection to [[SAP NetWeaver Process Integration]] (SAP PI; formerly called SAP Exchange Infrastructure). The local integration engine provides messaging services that exchange messages between the components that are connected in SAP PI.
 ; Connectivity layer : The Internet Communication Manager (ICM) dispatches user interface requests to the presentation layer and provides a single framework for connectivity using various communication protocols. Currently, modules are available for [[Hypertext Transfer Protocol]] (HTTP), [[HTTPS]] (extension of HTTP running under the [[Secure Sockets Layer]] (SSL)), [[Simple Mail Transfer Protocol]] (SMTP), [[Simple Object Access Protocol]] (SOAP), and [[FastCGI|Fast Common Gateway Interface]] (FastCGI).

SAP NetWeaver Application Server – link to JavaBeans