SAP NetWeaver Application Server: Difference between revisions

Revision as of 04:20, 16 October 2008

Latest revision as of 00:37, 18 July 2025

(48 intermediate revisions by 33 users not shown)

Line 1:

{{Short description|Component of SAP NetWeaver}}

SAP NetWeaver Application server is a component of the [[NetWeaver]] solution which works as a web application server to [[SAP AG|SAP]] solutions. From the [[SAP AG|SAP]] point of view the Web AS is the foundation on which most of their product range runs.

'''SAP NetWeaver Application Server''' or '''SAP Web Application Server''' is a component of [[SAP NetWeaver]] which works as a web application server for [[SAP AG|SAP]] products.

All [[ABAP]] application servers including the message server represent the application layer of the [[multitier architecture]] of an ABAP-based SAP system. These application servers execute ABAP applications and communicate with the presentation components, the database, and also with each other, using the message server.

==OverviewArchitecture==

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

Its basic function is to allow [[World Wide Web|web]] development based on SAP standard solutions (usually developed under the [[ABAP]] programming language, but in the newer versions also in [[Java (programming language)|Java programming language]]). With Web AS, it is possible - for example - to publish queries, programs and ABAP applications in a web environment but linked to and based in a SAP solution infrastructure. Since 2003 the newer versions of the (WAS or WEB AS) also support open standards like [[Java (programming language)|Java programming language]]. From the versions 6.20 and higher it is possible to create [[ABAP]] only, [[Java Platform, Standard Edition]] only or mixed environments.

; Presentation layer : In the presentation layer, the user interface can be developed with [[Java ServerJavaServer 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 JavaBeanJavaBeans]]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 XINetWeaver 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 XIPI.

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

; Persistence layer : The persistence layer supports database independence and scalable [[Database transaction|transaction]] handling. Business logic can be developed completely independent of the underlying database and operating system. Database independence is also made possible by support for open standards. The database interface ensures optimized data access from within the ABAP environment through [[Open SQL]]. SAP propagates the outstanding capabilities of Open SQL for ABAP to Open SQL for Java and offers a variety of standard [[Application Programming Interface]]s (APIs) to application programmers, such as [[SQLJ]]. Other technologies, such as [[Java Data Objects]] (JDO) and [[containerContainer-Managed managed persistencePersistence]] ([[Container-Managed Persistence|CMP]]) for EJB, or the direct use of the [[Java Database Connectivity]] (JDBC) API, are also supported.

==Security==

===Authentication===

Version:

The SAP NetWeaver AS can accept multiple forms of authentication:

* [[SAP Logon Ticket]] with appropriate configuration.<ref>[http://help.sap.com/erp2005_ehp_04/helpdata/EN/61/42897de269cf44b35f9395978cc9cb/frameset.htm Configuring SAP Web AS ABAP to Accept Logon Tickets from the J2EE Engine]</ref>

* Other [[single sign-on]] technology that utilizes [[x.509]] certificates and the combination of [[Secure Network Communications]] (SNC) and [[Secure Sockets Layer]] (SSL) for one standardize authentication platform.

===Communications===

Web AS 6.20

The SAP NetWeaver Application Server's connectivity layer supports [[HTTPS]] which is required for encrypted communications via [[Secure Sockets Layer]]. It is possible to enable SSL using the [[SAP Cryptographic Library]].<ref>{{Cite web |url=https://cw.sdn.sap.com/cw/docs/DOC-27593?treeid=DOC-8319 |title=Enabling SSL in the SAP NetWeaver Application Server |access-date=2010-11-05 |archive-date=2011-07-16 |archive-url=https://web.archive.org/web/20110716004915/https://cw.sdn.sap.com/cw/docs/DOC-27593?treeid=DOC-8319 |url-status=dead }}</ref> If a company is running with traditional SAP systems that only uses [[Remote function call|RFC]] and [[DIAG]] protocols, [[Secure Network Communications]] is required for encrypted communications as well<ref>[http://help.sap.com/saphelp_46c/helpdata/EN/4f/992d65446d11d189700000e8322d00/content.htm Secure Network Communications]</ref>

Web AS 6,40

==Architecture==

The architecture of SAP Web Application Server can be separated into five 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 [[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).

; Persistence layer : The persistence layer supports database independence and scalable [[Database transaction|transaction]] handling. Business logic can be developed completely independent of the underlying database and operating system. Database independence is also made possible by support for open standards. The database interface ensures optimized data access from within the ABAP environment through [[Open SQL]]. SAP propagates the outstanding capabilities of Open SQL for ABAP to Open SQL for Java and offers a variety of standard [[Application Programming Interface]]s (APIs) to application programmers, such as [[SQLJ]]. Other technologies, such as [[Java Data Objects]] (JDO) and [[container managed persistence]] ([[CMP]]) for EJB, or the direct use of the [[Java Database Connectivity]] (JDBC) API, are also supported.

==See also==

* [[Comparison of application servers]]

* [[Secure Network Communications]]

* [[Secure Sockets Layer]]

* [[x.509]]

* [[Single Sign-On]]

==References==

{{reflist}}

* http://help.sap.com

==External links==

[[Category:SAP NetWeaver]]

* [http://scn.sap.com/community/abap ABAP Development] discussions, blogs, documents and videos on the [http://scn.sap.com/welcome SAP Community Network (SCN)]

* [http://scn.sap.com/community/java SAP Netweaver Capabilities - Java Development] discussions, blogs, documents and videos on the [http://scn.sap.com/welcome SAP Community Network (SCN)]

[[de{{DEFAULTSORT:SAPSap NetWeaverNetweaver Application Server]]}}

[[Category:SAP NetWeaver|Application Server]]

[[Category:Web server software]]

[[Category:ApplicationWeb server software programmed in Java]]

[[de:SAP NetWeaver Application Server]]

[[zh:SAP Web应用服务器]]