|

SAP WAS (Web Application Server)
Architecture
Page 2 of 7
3.0 Understanding Web Application Server
Architecture
SAP integrates a J2EE environment into the Web
Application Server and supports Java and ABAP in parallel within one
server using a common database. The functions of a SAP Web
Application Server consists of four major building blocks:
3.1 The Internet Communication Manager (ICM)
It is an independent
process responsible for communications between the Web Application
Server and external supporters over intranets or the Internet using
standard protocols like HTTP, HTTPS, and Simple Mail Transfer
Protocol (SMTP). The communication is carried out using a
high-performance, memory-based communication channel named memory
pipe. ICM also significantly improves Web site performance and
scalability using dynamic and active content caching technology.

Figure 1: Detailed Architecture: SAP Web
Application Server
Image Source: SAP® White paper "Web Application Server: Building
Reliable Business Applications"
3.2 Business Environment
The environment is the component
responsible for the business content and underlying logic of the
enterprise that is published using the BSP/JSP.
ABAP Environment
is based on SAP’s application server development and deployment
environment. All existing components, such as business objects, can
be used for the business logic.
J2EE Environment consists of a
full-featured, J2EE-certified runtime environment that processes the
request passed from the ICM and dynamically generates the response.
This enables Web application developers to create Web applications
that include the presentation and the business logic by using
standard Java or J2EE technology. The SAP Java Connector (SAP JCo)
enables method calls between Java applications and ABAP applications
(and vice versa). The SAP Java Connector also meets the J2EE
standard specification for the integration of enterprise information
systems i.e., the J2EE Connector Architecture.
F The
connectivity hiccups between different application servers and
Enterprise Information Systems can be solved by the J2EE Connector.
The J2EE Connector architecture is part of the J2EE 1.3 platform,
which is based on the standardized technology of the J2EE.
3.3 Connectivity
To integrate third-party products,
tools, and applications, the Web Application Server supports several
open connectivity standards. As a result, the Web Application
Server provides complete technical interoperability across all SAP
and third-party components. The Web Application Server supports
Simple Object Access Protocol (SOAP), XML-based protocol for
exchanging information.
3.4 Relational Database
Web Application Server uses an
exhaustive repository for exchanging sensitive enterprise data. In
order to deploy successful Web Services, a set of Enterprise
Application Integration (EAI) tools are also required.


|