Google+ My SAP Web Application Server What it is - SAP ABAP

My SAP Web Application Server What it is

SAP Web Application Server is amongst the primary technical foundations of the mySAP.com strategy and it is named as SAP WAS. It fully integrates Internet and Internet connectivity into the suite of the mySAP.com e-business platform. The SAP WAS is the platform of alternative for creating dynamic, scalable, and collaborative Net applications primarily based on the mySAP.com infrastructure.

The World Vast Internet know-how has utterly changed the business panorama in the final a number of years. With the intention to preserve tempo with this consistently altering environment, SAP has been providing Web-enabling applied sciences to its suite of products because the beginning of the Net era. But this is the first time that the Net method of doing issues will get totally built-in in the traditional SAP software server architecture. This achievement is of such importance that the main part of the SAP system, previously called SAP Foundation, is now known as the SAP WAS.

What Is a Internet Software Server?

When you consider all the elements of a Internet set up, it is easy to see that holding a very good development mannequin is form of a posh task. The ample selections of server operating programs, web page format kinds,Net embedded programming languages, database access and more, whereas giving an important vary of flexibility, have an implicit set of issues quite troublesome to take care of effectively. This is the purpose when an internet utility server comes to help us. It is common to speak about a three-tiered or three-layered structure as the muse of Net software servers. Those three layers may very effectively be summarized as follows:

  1. A presentation layer
  2. An application layer
  3. A database layer

For every of these layers, there must be a special program supposed to fulfill every process:

  1. A Net server program
  2. An utility server program
  3. A relational database administration system

This division of duties is often thought-about a nice way of separating different parts of a growth project as an alternative of an precise set up of software program (even if there are numerous products available in the market that attempt to mimic this division). The applying layer is the place where it is greatest to put the business program logic. The concept behind this separation is the easing of maintenance of programming and layouts and the avoiding of interference between the designing staff and the event team. Designs and layouts change fairly often within the Web, so a modification within the design should never affect the business logic within the application.

The database system offers the idea for knowledge storage and retrieval using some kind of query language, normally the SQL (Structured Question Language) if a relational database management system is in use. Different kinds of databases in widespread use at this time are techniques based mostly on directories, just like the LDAP (Light-weight Listing Entry Protocol).

Internet utility server usually as a system that integrates an surroundings to serve and develop Internet applications whereas separating program logic and presentation structure and providing a uniform and consistent methodology for data access.

The SAP WAS has the next traits with a purpose to fulfill this definition:

  1. A generic TCP/IP multithreaded server that is ready to implement different protocols with the utilization of plug-ins. The HTTP, HTTPS (HTTP over Secure Sockets Layer), and SMTP (Simple Mail Switch Protocol) protocols can be found in the meanwhile of this writing, but the hooks to program other protocols are there as a approach to depart the system open to additional enhancements.
  2. An entire development environment (the Object Navigator) based mostly on the SAP 4.6 Development Workbench that gives version management, transport requests, and concurrent work in a project.
  3. A improvement mannequin that gives a transparent separation between page structure design and program logic. The ABAP (Superior Enterprise Software Programming) language has been prolonged and now has objects that directly take care of HTTP requests and could be embedded inside HTML tags. The Server Facet JavaScript language for embedding inside HTML tags has been made obtainable; for the primary time, it's attainable to create an utility running inside a SAP system in a programming language aside from ABAP.
  4. A MIME (Multipurpose Web Mail Extensions) Repository offers easy tracking and maintenance of static documents and binary objects which can be related to a Net project. The MIME repository is used to add photos, sound or video files, PDF or Microsoft Workplace paperwork to a given venture, and so are components of its transports requests.
  5. The highly effective time-confirmed and well-established SAP Basis system provides the inspiration for reliable knowledge management. In conclusion, the SAP WAS is a whole system specifically optimized for the growth of Net-oriented purposes and is absolutely compliant with the accepted requisites for an optimum Internet application server design.
The Architecture of the SAP WAS

The know-how behind SAP Net Application Server may be thought-about as an improvement on the SAP application server know-how basis. Its aim is to offer a framework that will allow the SAP technological basis to process HTTP requests and requests coming from other Web protocols. This converts any SAP application server right into a full-featured Internet server that may immediately accept connections from Web shoppers and send responses to them. The SAP WAS can also work as a Net consumer, producing requests to other Internet servers and processing the responses sent again by them.

This enhanced functionality of the SAP WAS is dealt with within the SAP kernel by technique of a further process. This course of is the ICM (Web Communication Manager). From the interior SAP architecture, the ICM might be seen as a special work course of that's answerable for handling connection requests from exterior purchasers and creating requests directed to exterior servers when requested to by a program running in any of the work processes. It is designed as a multi threaded server, and it communicates with the relaxation of the work processes by memory pipes positioned in shared memory.



The ICM is an external course of that is launched by the dispatcher if the system is configured to take action in the occasion profile. The internal server architecture of the ICM is a relaunched pool of employee threads to allow optimum coping with a selection of simultaneous Internet requests. Their description is given as follows.
  1. Thread control. This thread accepts incoming TCP/IP requests and calls a worker thread (or creates one if there aren’t any accessible) to course of the request.
  2. Worker thread. This thread is in cost of dealing with the request and the response of a connection. The method in which a working thread will handle a connection is set by the plug-in. The plug-in will outline the protocol below which the processing of the connection is to be accomplished (HTTP, SMTP, or others).
  3. Watchdog. This thread is responsible of looking ahead to timeouts and idle time of working threads. If a timeout happens (normally when ICM is waiting for a response), the watchdog will grab the connection and inform the thread control that the working thread is free for different tasks and when a connection has been received.
  4. Signal handler. This thread will course of indicators despatched by the working system or from one other process.
  5. Connection info. This table will keep details about the state of every existing network connection, equivalent to reminiscence pipes or plug-in data.
  6. Reminiscence pipes. These are reminiscence-based mostly communication objects. They deal with the communication of knowledge between the ICM and the work processes. There are four pipes for each connection: one for the request, one for the response, one for control data, and one out-of-band pipe.
The SAP WAS Growth Mannequin

The SAP WAS is predicated on a Web-oriented improvement model. This mannequin has the next characteristics:

  1. Web page-based mostly development model. Which means that Web purposes are constructed around Net pages.
  2. Event-pushed model. The events are often generated by navigation actions taken by the user, equivalent to clicking on a hyperlink or pushing Submit buttons.
  3. Server side scripting. That is to say that programming code can be inserted in Internet pages. That is crucial for the dynamic generation of Internet content in response to person input. This code ought to normally be presentation-related code, and no enterprise logic must be in it.
  4. Event-associated programming code. This needs to be in handler programs supposed for that function. This additionally gives a method of eliminating presentation tasks from the programming language by leaving a lot of the presentation to the HTML layout.
  5. Static (non ceaselessly changing) objects and documents in non-SAP format. For example, Microsoft Office documents are saved in a repository so as to maintain monitor of them and to relate them to the application. The combination of all these characteristics is done around the BSP (Enterprise Server Pages). Truly, a BSP software is the conventional method of growing packages within the SAP WAS. BSP applications are normally not display screen (dynpro) based SAP applications; as an alternative, they're meant to be accessible not via the SAPGUI, but by a Internet browser.
The SAP WAS improvement mannequin additionally consists of predefined ready-to-use Net controls that are supposed to ease and provides a consistent side to Internet web page design. These controls are gathered together within the WCF (Net Control Framework) and embody programming constructions to create tables, kinds, buttons, and other presentation elements.

The basis for the Web-oriented growth mannequin inside the SAP system is the enhancement of the traditional ABAP programming setting with objects that enable the direct handling of low-level HTTP requests. This supplies an infrastructure for extending SAP Internet performance even outdoors the BSP application. Truly, the BSP run time is nothing greater than a giant ABAP program (the BSP processor) utilizing these Net objects. This extension of the ABAP language is the ICF (Internet Management Framework).

This development model has been introduced within the SAP system, adopting the applied sciences for Net improvement which were proven in other environments, notably the Microsoft IIS (Internet Info Server) ASP (Software Service Supplier) improvement mannequin and the JSP ( Java Server Pages) technology present in most modern Internet server programs.My SAP Web Application Server GIVES control over the flow in the best ERP.

Related posts

sap internet transaction architecture
SAP internet transaction application components

SAP authorization and client administration in mysap.com
SAP Authorization and ALE
SAP SCRIPTS PART 6
SAP SCRIPTS PART 7
SAP SCRIPTS PART 8

No comments :

Post a Comment