SAP NetWeaver Application Server: Difference between revisions

Revision as of 12:26, 2 May 2013

Revision as of 12:29, 2 May 2013

Line 6:

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 [[Java Server 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 JavaBean]]s (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 XI]]. The local integration engine provides messaging services that exchange messages between the components that are connected in SAP XI.

; 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 Socket Layer]] (SSL)), [[Simple Mail Transfer Protocol]] (SMTP), [[Simple Object Access Protocol]] (SOAP), and [[FastCGI|Fast Common Gateway Interface]] (FastCGI).