1 was architecure

7/30/2019 1 WAS Architecure

http://slidepdf.com/reader/full/1-was-architecure 1/8

IBM India, GBS GD

BASIS for Develop ers

- Web Appl icat ion Server Architecture



I BM I ndia, GBS -GD

Multi – Channel Access

Portal Collaboration

Integration Broker Business Process Management

Business IntelligenceKnowledge Management

Master Data Management

DB and OS Abstraction

Process Integration

C

o m p o s i t e A p p l i c a t i o n F r a m

e w o r k

L i f e C y cl eM an a g em en t

People Integration

Information Integration

Application Platform

J2EE ABAP

SAP Netweaver ………

Microsoft .NetIBM WebSphere




Evolution of mySAP ERP

SAP Netweaver

SAP BASISSAP Web

Application Server

SAP R/3 EnterpriseApplication

Self Services

Self Service Procurement

Internet Sales

Strategic Enterprise Management

…. and more …

SAP R/3 enterprise


Internet Sales

Self Services


…. and more …

Composite Applications

SAP ECC 5.00



Internet Sales

Self Services

SAP R/3 up to 4.6c

SAP R/3 Enterprise

mySAP ERP 2003

mySAP ERP 2004




Architecture – Web Enabling in 4.6c

Internet Transaction Server

ABAP

Application Server

Browsers

User access was based

upon a web browser or

certain mobile devices

and access to the

system was via the

Internet Transaction

Server (ITS).

To provide this

access the ITS

required a

connection to a

web server. Also,

the ITS was not

platform

independent as it

had services that

were tied to

Microsoft Windowstechnology.

The only

programming

language available

was ABAP and

user interfaces

were programmed

with a front-end

modeling approach

called the Dynpro,

or dynamic

program.

Connections to

external systems

or other 3rd party

and legacy

systems weremade via custom

connectors,

gateways, or a

Remote Function

Call (RFC) to

another SAP

system.

These connectors

could be expensive

to develop and

maintain as they

were specific to each

system.

A change or an

upgrade to the

connected system

could require a

complete re-

development cycle

of the connector.

1 2

654

3




Web Enabling - Changes in Architecture in WAS 6.10

ABAP

Web Application Server

Internet Communication Manager (ICM)

Browser

SMTP HTTP(S) SOAP/XMLWith release 6.10 of the SAP Web AS (the successor to

SAP Basis 4.6), a major architecture change occurred for

web connectivity.

ICM is new functionality that is part of the core kernel.

It manages the communication between browsers(and other external requests) and the SAP Web AS

similar to the way the dispatcher in the system

handles requests from the SAPGui.

The ICM also handles connections made over

various protocols such as SMTP for mail, HTTP(S)

and SOAP/XML.

Since the ICM is integrated into the SAP Web AS

architecture, platform independence for web

connections is realized.

Business Server Pages (BSP), a mixture of ABAP

and HTML for user interface programming, are also

introduced in this release.

The SAP Web AS 6.10 did not have a Java

engine.

1

2

3

4




Web Enabling - Changes in Architecture in WAS 6.20

ABAP

Web Application Server

Internet Communication Manager

(ICM)

Browser

SMTP HTTP(S) SOAP/XML

JAVA

The first version of the SAP Java engine was released with SAP

Web AS 6.20.

The engine is fully

compliant with the 1.2

J2EE standards

making it a J2EE

certified application

server.

This enables thedevelopment and

deployment of ABAP-

based or J2EE-based

applications on the same

instance.

With Java nowavailable as a

programminglanguage, rich and

dynamic web pages

can be built with Java

Server Pages (JSP).

In addition,

customer’s can createtheir own Java web

applications to run on

the SAP Web AS.

43

21




Architecture

changes in

WAS 6.30 &

6.40

With the SAP Web AS

6.30 major changes to

the architecture of the

Java engine are

introduced. The overall

architecture of the SAP

Web AS is no differentthan in release 6.20

So, the SAP Web AS

6.30 only contains

changes to Java

functionality was

changed – the ABAP is

at the 6.20 level.

6.30 is also a

Ramp-up only

release that was

never released to

mass shipment.

SAP Web AS 6.40 is

the mass ship

release.

There are no overall

architecture changes

since SAP Web AS 6.30

in WAS 6.40.

The main feature

introduced with 6.30/6.40

is the Web Dynpro, a

runtime and development

environment for creating

easily adaptable Web

based user interfaces.

Java Stack Changes

- A central database

was added for the

Java engine as well

as central services

such as a message

server and enqueue

server

The Java and ABAP

stacks each create their

own schema in a single

database and there is

no direct, cross-stack

access of data in the

other schema.

87

6

5

43

21

The ABAP engine cannot directly

access the Java database

schema and vice-versa.

Communication can occur

between the stacks at the

application level through

interfaces such as the Java

Connector (JCo) ,




Insight into WAS as a technical platform for NW

DATABASE Server

SAP DB

MS SQL Server

ORACLE

Informix

DB2

DB6

DB4

Database System

Linux Unix Windows OS/390OS/400Operating System

Internet Communication Manager

SAP J2EE

Engine

ABAPJCo (Fast

RFC)

RFC

DIAGExternal Systems

SAP GUI

SAP Web AS

Browser SMTP HTTP(S)SOAP/

XML

SAP Web AS is the

logical result of further

development of the

SAP Application Server

Technology (formerly

also known as “SAPBasis”), with particular

attention being paid to

Web-based

applications.

1 was architecure

Documents