It is not possible to add the new link because it would replace an existing, longer link.
Line 5: | Line 5: | ||
; 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. |
; 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). |
; 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). |
||
; 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 |
; 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]] ([[Container-Managed Persistence|CMP]]) for EJB, or the direct use of the [[Java Database Connectivity]] (JDBC) API, are also supported. |