The Role, Function and Use of ITS (Internet Transaction Server) in mySAP.com Solutions

Technical Brief

Enterprise Systems Group (ESG)

Storage Systems Group (SSG)

Dell White Paper

By Dell SAP CC Walldorf


August 2001


Contents

Executive Summary 3

Introduction 4

Target Audience 4

Introduction 4

Description of Internet Transaction Server (ITS) 5

Overview 5

Description of a request cycle with HTTP/SAPgui protocol transition 6

Planning the System 10

Sizing Fundamentals And Recommendations 10

Calculation of Active Users for One Service 11

Hardware Recommendations 12

Conclusions/Recommendations 14

Contacts 14

Appendix A: Reference Documents 16

Appendix B: Glossary of Terms and Acronyms 17

Appendix C 18

Vendor Information 18

SAP 18

Dell Computer Corporation 18

Intel Corporation 19

Section 1

Executive Summary

When implementing a mySAP.com solution from SAP, the link between the Internet and the SAP system itself is accomplished with SAP’s Internet Transaction Server (ITS). The purpose of this paper is to explain the role, function and use of ITS within the SAP solution and how to leverage Dell’s architecture to construct a resilient ITS environment.

As a pioneer in using Internet technology to create e-commerce success, Dell is well positioned, as a mySAP.com Global Technology Partner, to probe the use of ITS and how it can be best implemented for Dell’s customers’ benefit in an optimized SAP landscape.

Further, proven solutions are the key to any IT strategy. The results contained in this paper are the result of extensive testing done at Dell’s SAP Competence Center and Dell personnel working in SAP’s LinuxLab at SAP headquarters in Walldorf, Germany as well as drawing on the expertise of Dell’s Solution Engineering team at Dell’s worldwide headquarters in Round Rock, Texas, USA. Customer feedback and experience from the field in over 1,500 SAP installations running on Dell™ PowerEdge™ servers and PowerVault™ storage worldwide have also been incorporated into this report.

Section 2

Introduction

Target Audience

This paper is targeted toward Dell technical sales representatives, systems consultants and field technical personnel, and customers who have a need to deploy an SAP Internet Transaction Server as part of their SAP solution on Dell PowerEdge server and PowerVault storage systems.

Introduction

SAP customers wanting to harness the power of the Internet, may use SAP Internet Transaction Server (ITS) as the gateway between SAP and the Web. This allows for interactive Web access to the SAP system.

The purpose of this paper is to outline the roles, functions and use of ITS in an SAP environment. This is of particular importance as more SAP customers upgrade their systems’ active users to SAP’s Web-enabled functionality. Dell has already seen a huge increase in demand for PowerApp appliances and PowerEdge servers necessary to build the Internet infrastructure for SAP systems.

Particular attention will be paid to the manner in which a resilient, redundant ITS configuration is created, as the scalability of the ITS product allows for many possible scenarios.

Section 3

Description of Internet Transaction Server (ITS)

Overview

HyperText Transfer Protocol (HTTP) is the main protocol used on the World Wide Web for the communication between Web Browsers and Web Servers for the transfer of documents such as HTML (HyperText Markup Language) documents. HTML is an authoring language used to describe a document’s representation on the Internet. HyperText Markup Language documents refer, or connect, to other documents by hyperlinks. These inter-linked documents form the structure of the World Wide Web.

As stated earlier, ITS acts as a gateway between the SAP application server layer and HTML Web technology, thereby allowing interactive Web access to an SAP system. The conventional method of accessing the SAP system interactively is by using an SAP GUI (Graphical User Interface), which is available in different “flavors” such as “SAP GUI for Windows”, “SAP GUI for Java” and “SAP GUI for HMTL”. An SAP GUI displays SAP transaction screens and allows the user to interact directly with the system. It communicates with the SAP System by using a special SAP GUI protocol. Without ITS, a user would need additional middleware to access the SAP System with a Web browser in order to make the connection between SAP technology, such as SAP application servers and SAP GUIs, and Web technology, including Web servers and browsers. This necessary connection is accomplished by ITS and the need for additional middleware is eliminated. ITS dynamically maps the SAP transaction screen elements to HTML and does not do any transaction processing itself. Instead, it hands all business processing over to the SAP system on an application level. The ITS is merely a presentation front end.

ITS consists of two main program components: WGate (Web Gateway) and AGate (Application Gateway), which may exist on the same host or on separate hosts, with or without an intermediate firewall, connected by a TCP/IP network.

Figure 1 provides an overview of the ITS architecture including WGate, AGate and the communication protocols used between them. Figure 1 also details a user request cycle using an HTTP/SAP GUI protocol transition.


August 2001 Page 15 Dell ESG Worldwide Marketing

Figure 1: SAP Internet Transaction Server Architecture

Description of a request cycle with HTTP/SAPgui protocol transition

The following steps depict a request cycle with an HTTP/SAPgui protocol transition as seen above.

  1. A user request is received via Web browser (Internet Explorer, Netscape® Navigator™, etc.).

2.  The Web server (e.g. Microsoft® Internet Information Server (IIS), Netscape Enterprise™, Apache) redirects to WGate.

  1. WGate sends a prepared request to AGate on the other side of the firewall.
  2. A service file is loaded automatically and processed by AGate (interpretation and composition).
  3. Transmitted data is received by the Internet application component and executed in the SAP application server (using BAPI methods).
  4. Results are transmitted back to the AGate component in ITS.
  5. By loading HTML templates and pages and inserting the application results into defined fields, the HTML output page is composed by AGate output processing.
  6. The HTML page is sent back to the WGate and the Web server.
  7. Data is displayed on the Web browser screen as a true HTML document.

When looking at the ITS server(s) in a real SAP environment, it becomes clear that these servers are the “glue” that holds together the Internet Application mySAP.com. The AGate especially, is not just a data repository. Rather, its built-in functions and responsibilities, which include screen mapping by translation and interpretation, and session and connection management with an underlying SAP application server, make it the most essential part of the Internet Transaction Server. Figures 2, 3 and 4 are examples of the SAP ITS look, feel and functionality.

Figure 2: Example of ITS Administration Overview Screen

In general, the ITS is a multi-threading gateway service. Threads are assigned per request/response cycle (not per user session), which results in better performance because threads are re-usable after they have been released of the former user request. In order to provide fast context switching and low latency, ITS has its own memory management, which is very efficient, thus enabling the management of many simultaneous sessions per period.

One of the main functions of the WGate component is to provide the establishment of a “stateful” session with an SAP system via the “stateless” communication channel (“per-request-connection”) of a typical Web server/browser combination. Internal Web server APIs such as Netscape Enterprise Server, Microsoft IIS, and Apache Web Server are supported in addition to the standard CGI (Common Gateway Interface) functions. The WGate portion of ITS resides on the same system as the WEB server.

Figure 3: Example of ITS Administration Process View Screen

With ITS release 4.6D, WGate is capable of communicating with more than one AGate simultaneously via IP link, regardless of where the AGate is physically installed – on the same host or on a different one. It is not necessary to have a dedicated virtual Web server per virtual ITS. Additionally, with release 4.6D compilation 3, ITS is patchable, which means, in order to apply improvements to an ITS installation, it is no longer necessary to uninstall the former ITS and then have the revised server newly installed.

Figure 4: ITS Control Screen

Section 4

Planning the System

In order to provide the resilience and redundancy necessary for productive use, at least two Internet Transaction Server instances on different hosts should be used for the implementation of SAP ITS. This recommendation applies to the ITS as well as to the Web server instances associated with WGate.

Figure 5: Example of ITS topology in an SAP configuration

The whole ITS environment is scalable by means of additional server systems with ITS and Web server instances. Depending on the size of the SAP system to be implemented, new ITS instances can be established and connected as needed. Load balancing on the Web side can be provided by a PowerApp.BIG-IP solution (sessions are maintained in the AGate), whereas the AGate must not reside in the WGate/Web server system.

Sizing Fundamentals And Recommendations

Note: The following specifications and numbers are mainly based upon SAP’s experience with on-site installations and benchmark tests using standard SAP business applications.

To get the best sizing results possible, it is necessary to identify the number of concurrent users who will access the SAP system over ITS in each of the different components of the mySAP solution used. The types of users can be distinguished by the kind of load they generate:

·  Continuous load - e.g. order entry and address changes

·  Peak load services - e.g. time sheet services and other Employee Self Services (ESS), which are active per user for short periods of time (once a week for instance)

For more information on sizing in a mySAP.com environment, refer to the Dell Technical Brief, Effectively Sizing a mySAP.com Solution. (See http://www.dell.com/downloads/us/pedge/sap_sizing_wp.doc)

For continuous load applications, an average load per time frame can be used, such as number of documents per day, or orders per week. This transactional load can also be broken down into simple, more characteristic dimensions.

For peak load services, the characteristic high load period has to be identified. For instance, the top, or high load period for Time Sheet service may be found early Friday afternoon at one o’clock for four hours. Other services may have a different time point for their peak load.

For all the services, the average time per user transaction has to be estimated or measured. This will be dependant on the number of transaction steps, the duration of each step, and a “think time” of approximately 30 seconds.

For a specific SAP module, the following formula describes the characteristics of the system load:

Active users = (Number of transactions / time frame) * average transaction time.

This calculation has to be done iteratively for each module that will be accessed via Internet Transaction Server. The following example demonstrates how to calculate the number of active users for one service. In this particular example, the service application is a peak load service being used during a high load period.

Calculation of Active Users for One Service

Number of active users for the service application Time Sheet (peak load service)

Formula: Active users = (number of transactions / time frame) * average transaction time.

Calculation example:

·  Number of transactions = 1,000 per week (1,000 employees have to make a time sheet entry every week)

·  Time frame (High load period) = 4 hours, or 240 minutes, on Fridays from 1 p.m. to 5 p.m. (worst case)

·  Average transaction time = 15 minutes, based on 30 transaction steps with 30 seconds “think time” per step

Number of active users = (1,000 named users / 240 minutes) * 15 minutes

= 63 active users (medium activity) for Time Sheet Application.

Hardware Recommendations

The following table gives a high level overview of server configurations for specific numbers of active users for ITS. When the Internet Transaction Server is divided into separate systems, one for WGate and a second one for AGate, the proposed configurations apply to the server hardware with the AGate component. The WGate resides on the Web server system, whose configuration can be determined by an adequate Web server sizing taking into account an added CPU performance requirements for the WGate service. Table 1 provides a high level overview of server configurations for ITS based on the number of active ITS users. The recommended system configurations assume a dual host ITS landscape for redundancy and resilience, as mentioned earlier.


August 2001 Page 15 Dell ESG Worldwide Marketing

Table 1: Recommended System Configurations Based on the Number of Active ITS Users

Size / Number of Active ITS Users / (Quantity) Platform
A / 0 - 250 / (2) PowerEdge 2450/2550
(1) Intel Pentium III, 866 MHz
256 MB RAM
(2) HDSK 18 GB, RAID-1 (OS+Swap)
B / 251 - 500 / (2) PowerEdge 4400
(1) Intel Pentium III XEON
512 MB RAM
(2) HDSK 18 GB, RAID-1 (OS+Swap)
C / 501 - 1000 / (2) PowerEdge 4400
(2) Intel Pentium III XEON
1 GB RAM
(2) HDSK 18 GB, RAID-1 (OS+Swap)
D / 1001 - 3000 / (2) PowerEdge 6450
(4) Intel Pentium III XEON w/ 1 MB L2 Cache
2 GB RAM
(2) HDSK 18 GB, RAID-1 (OS+Swap)
E / > 3000 / (n)* PowerEdge 6450
(4) Intel Pentium III XEON with 2 MB L2 Cache
2 GB RAM
(2) HDSK 18 GB, RAID-1 (OS+Swap)

* The number of PE 6450’s will depend on an exact sizing.

Section 5

Conclusions/Recommendations

In this paper, Dell has outlined the vital role, function, and use of the SAP Internet Transaction Server in mySAP.com solutions. Without the careful and planned implementation of the ITS server, no SAP solution today can be effectively Web enabled.