SAP Internet Transaction Server On Linux

SAP ITS 6.
20 on LINUX: Installation, Administration, Security, and Tuning

Arno Esser SAP AG
Learning Objectives
As a result of this workshop, you will be able to:

Understand the concepts of SAP ITS Install an ITS 6.20 with multiple virtual instances Configure and loadbalance your ITS landscape Administer your ITS server Tune your ITS instances
SAP AG 2003, PA351, Arno Esser, Page 2
Agenda
1 1
Introduction Web Servers & Platform Matrix SAP ITS Installation SAP ITS Administration & Configuration Additional Information
2 2 3 3 4 4
5 5
SAP System & The Web
Browser Browser Intranet Browser
Firewall Internet Web Server ITS

SAP System
Browser
PC
Browser
PC
GUI
SAP Internet Transaction Server

Extends the reach of SAP Systems into the Web
Maps SAP screens to HTML, WML or similar web formats Using web transfer protocol HTTP(S)
Drives transactions within the SAP System or calls function modules, BAPIs, etc. in the backend system
Application Server sees a SAP GUI for Windows
Separation of Business Logic and Visual Appearance Downward compatible (towards ITS and Web Application Server releases)
ITS 6.20 can be used to access SAP products based on SAP Web Application Server releases 6.20 and below. ITS 6.10 and 4.6D C4 can be used to connect to SAP products based on SAP Basis 4.6D and below.
How to offer a Service on the Web?

SAP ITS SAP System
Web Browser
Web Server WGate AGate
Service Files MIME Files SAP@Web Service description Images Studio or ABAP HTML Templates Stylesheets Language Resource Javascripts Workbench Files Multimedia Outside SAP System Flow Files HTML Visualization
Application ABAP ABAP Dynpro Screens Workbench Customization
Inside SAP System Business Logic
ITS Architecture Details

Load Load Service File Service File
User Request User Request
Call WGate Call WGate
Send Prepared Send Prepared Request Request
Service Files
Input Input WGate Browser Web Server

HTML Templates
SAP System
SAP Internet Application Component
AGate Output Output

Flow Files
BAPI
HTML Page HTML Page
HTML Page HTML Page

SAP Data
Load Load HTML Templates // Flow Files HTML Templates Flow Files
Agenda
1 1
2 2 3 3 4 4
5 5
Web Server Web Server software

Listens on a specific TCP port for requests Replies to HTTP requests from HTTP clients Can only send data after receiving a request
Sends request
Replies with data

Web Browser
Web Server
Web Browsers Software used to access the Internet

Requests data from a specific port of a specific Web Server (client/server structure) Presents the information received (such as text and pictures) Sends data to the Web Server
Sends data
Receives data
Web Browser
Web Server
ITS 6.20 Server Platforms

WGate
Microsoft Windows 2000 and 2003 Server
Microsoft Web Server (ISAPI) Apache HTTP Server (Apache Module) SUN One Web Server (NSAPI)
AGate
Microsoft Windows 2000 Server Microsoft Windows 2003 Server SUSE Linux Enterprise Server 8 RedHat Enterprise Linux 2.1 ES/AS
Solaris
SUN One Web Server
SAP@Web Studio
Microsoft Windows 2000 Workstation
Linux / Intel
SUSE Linux Enterprise Server 8
Apache HTTP Server (Apache Module)
RedHat Enterprise Linux 2.1 ES/AS

Apache HTTP Server (Apache Module)
Virtual Web Servers

On a single computer, multiple Web Servers (so-called virtual Web Servers) can be installed without having to repeat the entire installation process. A request to a host with multiple virtual Web Servers installed is directed to the correct virtual Web Server by differentiating by
IP address (each virtual Web Server may have its own IP address) Port number (each virtual Web Server may listen on a different port)
Responses are either generated dynamically or are taken from a predefined directory structure belonging to the Web Server
This structure usually is created before the Web Server itself is set up. The default Apache file directory is /srv/www/htdocs. If you dont specify a file to be accessed the Web Server may return a default document.
Each virtual Web Server should have its own directory structure
This is necessary to install multiple SAP ITS instances with different application contents on the same computer
Apache Web Server Directory Structure

/srv /www /ftp (default web area) (default web root directory) (default ftp root directory)
Example: Root directories for virtual Web Servers

/srv /www/WEBGUI (Web area for SAP ITS WEBGUI) /www/ADM (Web area for SAP ITS ADM)
Agenda
1 1
2 2 3 3 4 4
5 5
SAP ITS Installation

You can get the installation files from
The Server Components CD (directory ITS/UNIX/LINUXINTEL). http://service.sap.com/patches web site for the latest patches.
The setup program is based on SAPInst Installation tool which provides

Easy user friendly dialogs A scripting interface for installations without user interaction The chance to continue a failed installation after resolving the cause of the problem Simplified update process for ITS servers (only one installation for all instances) Installation tool known from SAP WebAS
SAP@Web Installation Guide

Detailed step by step instructions and matrix of necessary parameters Print and read these instructions before starting an installation
SAP ITS Installation Requirements

Windows 2000 Server (not Professional)
Running on an Intel or compatible processor Recommended minimum Service Pack 3
Windows 2003 Server

Running on an Intel or compatible processor (32-bit)
Linux Server
Running on an Intel or compatible processor (32-bit) SUSE Linux Enterprise Server 8 (SLES8) Red Hat Enterprise Linux 2.1 (AS/ES)
A minimum of 256 MB physical memory is recommended (productive installations may require a lot more than this). 1GB Hard Drive space will suffice for several SAP ITS installations.
SAP ITS Installation Parameters

Landscape - Type of installation
Single Host Dual Host (Recommended for Security and Scalability) AGate installed on one host WGate installed on another host together with the Web Server
SAP ITS installation type Typical or Administration

Typical installations can run SAP GUI for HTML and other applications Administration installations exclusively run ITS Administration
(virtual) Web Server to connect the SAP ITS to Application packages (IAC packages) to be installed SAP System Connection information and Logon Data (optionally)
Single Host Installation
ISAPI
WGate
HTTPS
NSAPI APACHE
TCP/IP
AGate
HTTP
DIAG RFC
Web Server
ITS
SAP Application Server
Windows 2000 Server Windows 2003 Server 32-bit SUSE Linux Enterprise Server 8 RedHat Enterprise Linux 2.1
Dual Host Installation
ISAPI
WGate
NSAPI HTTPS APACHE
TCP/IP
AGate
HTTP
DIAG RFC
Web Server
ITS
Wgate & Agate OS platforms: Windows 2000 Server Windows 2003 Server 32-bit SUSE Linux Enterprise Server 8 RedHat Enterprise Linux 2.1
Security Additional Protection

Firewalls
ISAPI
WGate
HTTPS
NSAPI APACHE
TCP/IP
AGate
DIAG RFC
Web Server
SNC, (SAPRouter possible) SAPRouter These security measures are strongly recommended for productive installations. The firewall between AGate and WGate is only possible in Dual Host mode!
Virtual instances
ISAPI
WGate
NSAPI APACHE
AGate
TCP/IP
Virt. Web Server
ITS 1
With a certain number of virtual Web Servers installed, you can create the same number of SAP ITS environments on a single host. Several ITS installations (also called virtual instances) can operate independently on the same server.
ISAPI
WGate
NSAPI APACHE
TCP/IP
Virt. Web Server
ITS 2
One physical server

AGate
SAP ITS Installation

On the following pages you can find screenshots from an installation of a SAP ITS 6.20 (patch level 4)
Different SAP ITS versions have different screens A Dual Host Installation requires more information (e.g. the name of the server the AGate is installed on)
The required information is almost identical for all ITS versions. Therefore the installation concepts basically are the same for all releases. ITS 6.20 uses SAPInst, the new SAP Web Application Server installation tool. SAPInst consists of an installation engine and a JAVA based GUI. It allows remote installation of servers without a graphical window system where the engine runs on the server and the GUI on a desktop workstation. SAPInst supports unattended installations. Engine and GUI can run on different operating systems.
Preparing the SAP ITS Installation

To begin the installation change to root directory of the ITS installation, e.g. /usr/sap/its, and extract the patch file. Jump to a clean temporary installation directory, e.g. /usr/sap/its/install, and start the installation with /usr/sap/its/ITS/UNIX/LINUX/INSTALL.
To setup SAPInst installation tool please confirm all dialogs. The ITS installation will start automatically after SAPInst has been successfully installed
SAP ITS 6.20 Installation

All files and directories of the ITS installation belongs to the user itsadm. If it does not exist the installation creates it automatically.
The installation of ITS on LINUX needs to know the installation directory. Accept the default here and click Next. Please accept following license agreement.

If you already have installed one or more ITS instances on your server you will get this screen instead of the one on the previous slide. Here you can decide whether to install an additional ITS instance or to refresh the installation (e.g. to repair a corrupted installation or to apply a patch).

System number
Uniquely identify system resources Unique number for IACOR,wgate and per instance No alignment with already installed R3-system Cleanipc per instance possible
Tooltips
Context sensitive help for input fields

Type of installation
Basic choice of instance usage
Port definition
Avoid confusion with network based mgmt, e.g. YP, NIS Doesnt override definitions No influence on sapms*, sapiacor* Define ports
sapdp[00-99] to 3200 - 3299 sapgw[00-99] to 3300 - 3399

Development Env.
Change some registry keys, e.g. StaticTemplates, AdminEnabled Reduces resource consumption
Streamline
Set default in global.srvc Not supported on linux clients yet Templates and mimes are always installed
Additional dialogs
Ease up installation for seldom used options

Location
Linux specific Several installations are possible Apache 1.3 and 2.0 can be installed in parallel Several subversions of 1.3/2.0 can be installed in parallel Standard locations are:
SLES8, Apache 1.3.26: /usr/sbin/httpd; /etc/httpd SuSE8.1,Apache 2.0.40: /usr/sbin/apache2; /etc/apache2

Virtualhost list List is extracted from httpd.conf Port- / hostbased configuration supported
Portbased:
Listen 1080 Listen 8080 <VirtualHost _default_:1080> DocumentRoot /srv/www/its/1080 </VirtualHost> <VirtualHost _default_:8080> DocumentRoot /srv/www/its/8080 </VirtualHost>
Hostbased:
Listen 80 NameVirtualHost www.xxx.yyy.zzz <VirtualHost hostname1:80> DocumentRoot /srv/www/hostname1 </VirtualHost> <VirtualHost hostname2:80> DocumentRoot /srv/www/hostname2 </VirtualHost>

Select connection mode Message Server and confirm the connection data as shown on the screenshot by pressing click Next. Type in PUBLIC as Login Group and click 'Next'.
Select 'YES' to start ITS instance after installation and click 'Next'.

Check installation overview page and click 'Start'.
SAPInst now starts the installation process and finishes if nothing went wrong with the upper success dialog. Click Ok.

Start
Agate,iacor:
For each instance including iacor a scripts is created in <ITS installation directory>/bin. The scripts are named its<VITS>.sh The scripts should be link in runlevel directory, e.g. /etc/init.d/rc3.d
Wgate:
export LD_LIBRARY_PATH=<ITS installation directory>/programs Start apache
Test
Set registry key StatusMonitorEnabled in ItsRegistryWGATE.xml and request wgate status with http://<host>:<port>/scripts/wgate/wgate-status? Test wgate-agate communication with http://<host>:<port>/scripts/wgate/itsping/!
Remark: Upgrade of an older ITS installation

Upgrade support:
4.6D/6.10 to 6.20 6.20 does not share registry keys or other resources with older installation with 1 exception Information from existing instances is used to setup a new installation in parallel Old installation is not manipulated in any way, e.g. services are not disabled The webserver points to the new installation after upgrade
Unattended installation
Features
Script-based Fully automatic installation without user interaction, e.g. ports are determined automatically Provides the same functionality as manual gui-based installation, i.e. single/dual host, admin/non-admin, additional packages etc. No GUI capabilities are required, no JAVA Any number of instances with individual installation types can be performed through one call
Repeating an installation
Repeating a previously successfully executed installation unattended Part of a backup scenario Not customizable See note 526835
Restart of the installation

Normal installation
SAPinst require reinitialization after a successfull or broken installation before next start W32 program menu:
Start: SAPinst Server with GUI Reinit: Prepare new installation
W32 command line in installation directory, e.g. C:\SAPinst

Start: sapinst.exe Reinit: newinstall.cmd
ITS 620:
Linux command line in installation directory, e.g. /usr/sap/its/install:

Start: ./sapinst Reinit: ./newinstall
Procedure
Steps:
Create example .ini file with:
sapinst SAPINST_SMART_COMPONENT=ITS_BATCH_PROCESSING SAPINST_SMART_CONFIGFILE=ITS_PARAMETER.ini
The normal installation starts. Abort it on first welcome screen. An exemplary file with comments has been created. Edit ITS_PARAMETER.ini to meet your requirements Restart unattended installation with:
sapinst SAPINST_SMART_COMPONENT=ITS_BATCH_PROCESSING SAPINST_SMART_CONFIGFILE=ITS_PARAMETER.ini SAPINST_SKIP_DIALOGS=true
Example
[ITS_MAIN] ACTIONS= INSTALL INSTANCE_IT1 [INSTALL] PROGRAM_DIRECTORY=/usr/sap/its/6.20 [INSTANCE_IT1] ADMIN_INSTANCE=false TYPE=* NAME=IT1 DEVELOPER_MODE=true SYSTEM_NUMBER=41 WEBGUI=true FLOW_DEBUG=false APPLY_ADDITIONAL_PACKAGES=false WATCHDOG=false SAP_SYSTEM_NAME=BCE USE_ANOYMOUSLOGIN=false MESSAGE_SERVER=bcemain.wdf.sap.corp START_AFTER_INSTALLATION=true RUN_MULTIPLE_AGATE_PROCESSES=false WEBSERVER_INSTANCE=Apache (virtual host: _default_:1080) APACHE_CONFIG_DIRECTORY=/etc/httpd APACHE_EXECUTABLE=/usr/sbin/httpd
Exercise 1
Install a typical SingleHost SAP ITS instance to port 1080:
Use SAP System data provided during class. Use the Development Configuration. Check with url 'http://basel03:1080/scripts/wgate/webgui_start/!
Install an administrative instance to port 8080

Notice the differences in the installation dialog. Check with url 'http://basel03:8080/scripts/wgate/admin/!
Install a second 'typical' instance unattended:

Copy ITS_PARAMETER.ini from /archive to /usr/sap/its/install Start unattended installation as described during class Check with url 'http://basel03:1082/scripts/wgate/webgui_start/!
Note: Before you can check the ITS connection, apache has to be restartet and LD_LIBRARY_PATH has to be set once:
export LD_LIBRARY_PATH=/usr/sap/its/6.20/programs Restart apache with the command: "rcapache restart"
SAP ITS Scalability

SAP ITS offers several Scalability and Load Balancing options:
Scale up the Web Server infrastructure Scale up the number of AGate servers / AGate processes Use Load Balancing via SAP Messageserver Use SAP ITS Load Balancing Make use of an HTTP Router Use more than one AGate process
Web Server / SAP ITS Scalability

SAP System
WGate Web Server AGate
Web Browser
WGate Web Server Web Browser
One AGate can be connected to several Web Servers/WGates
SAP ITS - SAP System Scalability

SAP System
Appl. Server
WGate Web Server
AGate
Web Browser
Message Server
One SAP ITS can use several Application Servers of one SAP System via: Load Balancing Separate selection of a specific Application Server
SAP ITS Load Balancing

SAP System
AGate
WGate Web Server
AGate
Web Browser
AGate
WGate passes prepared requests on to AGate AGate does the actual work Session management HTML page generation CPU utilization of AGate is much higher than WGates This scenario offers additional fault tolerance for AGate
HTTP Routing / High Availability
AGate WGate Web Server AGate WGate Web Server AGate
Web Browser
HTTP Router
This scenario offers additional fault tolerance for both AGate and WGate When HTTPS is used the load on the WGate server can be fairly high
Multiple AGate processes

SAP ITS AGate
WGate Web Browser Web Server
Mapping Manager
AGate processes
The load is distributed between the AGate processes It is always useful to have several Agate processes per instance due to failover, locking and the 2GB memory limit per process
Wgate Configuration Tool

Configuration tool to completely administrate Wgate Add new URL section Setup connection to multiple agates No need to restart your web server (in most cases) Connectivity test to Agate and Mapping manager available SNC version displayed SNC environment displayed After activating no need to edit ItsRegistryWGate/Wgate.conf by hand Changing of Wgate trace level without web server restart
Wgate configuration tool: Activation

Edit ItsRegistryWgate.xml with you favorite editor and change ConfigMonitorEnabled in global section to yes
Wgate configuration tool

Global Parameters
URL Section
Logical Instances
Activation/ Reload
Wgate Configuration Tool Dos and Donts

Make sure you stay in the same webserver process (loadbalancing) Switch off (or overtake) reverse-proxies, loadbalancers Start web servers as single process e.g.: /usr/sbin/httpd X The tool manipulates registry files ItsRegistryWGATE.xml in config directory. Make them writeable for the low-priviliged apache user, i.e. wwwrun. Proposal: switch to itsadm in httpd.conf temporarily. Switch off the tool after configuring Wgate, otherwise your Wgate will be open to anyone for configuring
Wgate Status Monitor

Status Monitor:
Provides statistical information about ITS instances Enabled by setting the key StatusMonitorEnabled in ItsRegistryWGATE.xml Start with http://<host>:<port>/ scripts/wgate/wgate-status?
Exercise 2
Enable the Wgate Config tool. Open the ItsRegistryWgate.xml with the editor of your choice. Search for the Global Section and change the value for ConfigMonitorStatus from no to yes. Restart the Web server instance. Start the Wgate Configuration Tool using URL: http://localhost:1080/scripts/wgate/wgate-config? Create a second AGate section for instance WEBGUI that points to the DEMO instance (result of the unattended installation). Start the SAP GUI for HTML and try to find out which SAP ITS AGate server you are connected to.
IACOR Installation & Configuration

IACOR (IAC Object Receiver)
Windows/Linux based tool that was designed to allow publishing IAC contents from a SAP System to a virtual SAP ITS instance Registers SAP ITS instances at a gateway of the SAP System (release 4.6C or higher) and waits for files to receive The publication process can be started from transactions SE80 (Web Application Builder) and SE38 in the SAP System From SAP System release 6.10 on, IACOR can also be used to publish IAC files to SAP ITS landscapes in addition to single SAP ITS instances
IACOR Setup
IACOR demon:
Is installed as a services automatically during initial setup Can be started via
W32: ServiceManager LINUX: "Installation directory"/bin/itsIACOR.sh start|stop
Connections can be managed with iacorcmd, e.g:

./iacorcmd add \ /itsname:DEMO \ /gwhost:"<auto>" \ /gwservice:"<auto>" \ /desturlits:"/usr/sap/its/6.20/DEMO" \ /desturlwww:"/srv/www/its/1082/sap/its/mimes" \ /r3name:BCE \ /group:PUBLIC \ /msgsrv:"bcemain.wdf.sap.corp" \ /client:"000" \ /r3user:<****> \ /r3password:<****>
Using IACOR
To publish IAC files to your SAP ITS instance start the SAP GUI for HTML, launch transaction SE38 and execute the program W3_Publish_Services. Skip the screen asking for a transport request by clicking on Execute. After selecting the IACs to be published click on Workbench settings to choose the ITS instance to receive the files.
Using IACOR
Select the SAP ITS instance named <ITS host name>/<SAP ITS instance name> and click the button with the green tick to return to W3_Publish_Services. Start the process by clicking the Publish button.
Agenda
1 1
2 2 3 3 4 4
5 5
SAP ITS Administration and Monitoring

SAP ITS Administration is an HTML based Administration and Monitoring tool that can be remotely accessed via Web. Flexible configuration and administration tool designed for Changing SAP ITS settings Monitoring SAP ITS performance data Editing service files Viewing template files Viewing SAP ITS log files and trace files Tuning your ITS server Dedicated to and optimized for SAP ITS Control SAP ITS instances (Start, Stop and Restart) Control Web Server instances (Start, Stop and Restart) Installed on a separate virtual SAP ITS instance.
SAP ITS Administration: Login

URL request for login: http://<server>:<port>/scripts/wgate/ admin/! Default Login: itsadmin Password: init
You can access all features of ITS Administration by using the menu on the left hand side. Note that there is one entry for each ITS instance.
SAP ITS Administration: User Administration

To change the password for the current user select Administration followed by Change Password.
If you want to create SAP ITS Administration users with limited privileges you can do so via Administration User Management. An Administrator can, e.g. change service file parameters, restart and stop instances, while View Only users cannot change settings or restart the SAP ITS. Modifying registry settings except for performance settings is restricted to the user itsadmin.
SAP ITS Administration: System View & Overview

Under System View you can find data on the resources of the host computer (active processes, allocated memory, free disk space).
On the Load Balancing screen the current load balancing situation of all instances can be observed.
SAP ITS Administration: Managing Remote Instances

The full set of SAP ITS Administration features is available for local SAP ITS instances only while for remote instances you can access the performance analysis commands. However there is a command (Go to Native ADM) that lets you switch to a remote Administration instance, so you can conveniently administer all SAP ITS servers.
SAP ITS Administration: Service Files

Configuration Global Services All Settings will give you a list of global configuration parameters for the instance you selected.
You can change the setting of any parameter by modifying its value in the corresponding edit field and clicking SAVE. This kind of change is applied instantly . The configuration of other IACs (Internet Application Components) can be changed with Configuration Services <name of the service>.
SAP ITS Tuning Parameters

These tuning parameters can be set in service files: ~http_use_compression Enables / Disables HTTP compression between SAP ITS and Web Browser. Activating this feature reduces the amount of data sent to the Web Browser thus reducing overall network traffic. ~timeout This parameter specifies the time in minutes after which an idle user session is terminated. Tuning this parameter will help in situations where large numbers of sessions are blocked because of users not logging off but either closing the Web Browser or being idle. Changes to these parameters take effect immediately, but already established sessions are not affected.
SAP ITS Administration: Performance Settings

The most important settings regarding SAP ITS performance can be accessed by selecting Configuration Performance. It is often sufficient to modify one or more of these settings if you want to adjust your SAP ITS according to your needs. Remember that after saving your changes you have to restart the SAP ITS instance in order to apply them.
SAP ITS Tuning Parameters

MaxSessions Maximum number of sessions the SAP ITS instance can support in parallel MinWorkThreads The number of Workthreads created by the SAP ITS instance at startup MaxWorkThreads Maximum number of Workthreads supported by the instance (the ITS will start with MinWorkThreads and increase this number up to a maximum of MaxWorkThreads in case of high load we strongly recommend to set MinWorkThreads = MaxWorkThreads). StaticTemplates When this parameter is set to 1 (default) the SAP ITS will cache all HTML templates used by SAP ITS applications thus improving performance. In development environments this parameter should always be set to 0. ProductionMode Enables caching of data in applications based on SAP ITS Flow Logic. This performance setting improves the speed of module calls considerably, but should not be turned on during development of applications based on Flow Logic
SAP ITS Memory Configuration

ITSSetup offers two standard configurations in respect to the maximum amount of memory used by the SAP ITS instance. These two configurations differ in the number of Workthreads and Sessions launched upon start:
Default 400 Sessions 40 Workthreads Development Mode 64 Sessions 4 Workthreads
Workthread/Session Model
SAP System
Dispatcher In Port
Pool of Workthreads
Session Pool
AGate
Internal Scalability (AGate)

Increasing the number of Workthreads will result in Higher throughput of your SAP ITS instance A rise in memory consumption as well as processor utilization Increasing the number of Sessions will result in The SAP ITS being capable of serving more users at the same time (as long as the number of Workthreads is sufficient) A rise in memory consumption If you increase the number of Workthreads and/or Sessions you should always make sure that your server can take the new load. An alternative is to increase the number of Workthreads/Sessions by setting up more than one SAP ITS Server and using ITS Load Balancing. It is always useful to have several Agate processes per instance due to failover, locking and memory limit per process
SAP ITS Logs and Trace Files The most important logs and trace files:
access.log: In this file the SAP ITS records whenever an SAP ITS session is started or ended (by timeout or the user logging off). performance.log: This file (and loadstat.log) is used to store basic information on SAP ITS performance as well as the hosts performance. The SAP ITS can be tuned according to the numbers detailing the unused sessions and workthreads. AGateX_*.trc: All information messages, warnings and errors generated by the component AGate are written to these files. Wgate*.trc: These files resides on the Web Server host and are especially useful when communication problems prevent the WGate from connecting to the AGate for some unknown reason.
SAP ITS Administration: Viewing Log & Trace Files

Click WEBGUI View Logs Logs to take a look at the log files for the WEBGUI instance. The traces can be accessed via Traces. Analyzing the log files will help you tuning SAP ITS. If e.g. the number of workthreads or sessions runs low for a longer period of time you should consider increasing the values of these parameters.
SAP ITS Administration: Setting Trace File Parameters

Use Configuration Traces to alter the settings for SAP ITS trace files (likewise for log files).
With ITS 6.20 it is no longer necessary to restart the instance after changing trace level.
SAP ITS Administration: Performance Monitoring

Select Configuration Registry to change the SAP ITS registry settings. In this example we choose CCMS in the frame on the right to have the SAP ITS performance monitoring parameters displayed. To activate the advanced performance monitoring click PerfMonitoring and enter the value 1. Also active the MemoryTuning by setting PerfMemTune to 1. Again you will have to restart the SAP ITS after saving, but of course you dont have to restart once for every single change, one restart after all changes have been made is enough.
SAP ITS 6.20 Tuning: Performance Monitoring

If you suspect a performance bottleneck in your system (consisting of Web Browser, SAP ITS and SAP System), but are not quite sure which component is responsible for the bottleneck, you can get an impression where the processing time is spent by selecting Performance -> Thread Performance for the SAP ITS instance in question. In this example the processing time was equally shared between SAP System and SAP ITS.
SAP ITS 6.20 Tuning: Memory Tuning Tool

If you want to optimize the memory requirements of your ITS installation you can use Performance Memory Tuning for any given ITS instance. The memory tuning tool can be used to find out how much memory your current configuration would consume under worst conditions. This value should always be below the OS-specific limit, e.g. 4GB for linux. You can experiment with the parameters without changing the ITS settings and in conjunction with the performance analysis you can possibly reduce the memory requirements.
Exercise 3
Start SAP ITS Administration with the URL http://<your computer>:8080/scripts/wgate/admin/!. Change the value of the ~timeout parameter in the global service file of your WEBGUI SAP ITS instance. Change the number of sessions on your WEBGUI instance. Change the number of workthreads on your WEBGUI instance. Explore!
Agenda
1 1
2 2 3 3 4 4
5 5
Further Information
Public Web:
http://service.sap.com/sap-its
SAPNet:
Use ALIAS: sap-its
Literature
SAP@Web Installation Guide SAP ITS Tuning & Troubleshooting Guide SAP ITS Administration Guide SAP ITS Service Parameters
Related Lectures at TechEd 2003

Future of ITS, PA104, TUE 5:00 pm, L4 UI Clients for SAP NetWeaver, UI101, THU 10:00am+THU 8:00am, L1
SAP Technology: Web Application Development Curriculum

SAPTEC 2 days BC400 5 days NET200 3days
mySAP Technology Solution Overview SAP Web Application Server: Developing Web Applications
ABAP Workbench: Foundation and Concepts
NET100
3 days
Necessary
HTML, CSS Knowledge, Internet Terminology
NET050
3 days
SAP ITS: Developing Screen based Internet Application Comp.
Web Application Development: Foundations
ITS150
2days
SAP ITS: Corporate Identity Design
ITS070
3 days
SAP ITS: Administration
Questions?
Q&A
Feedback
Please complete your session evaluation and drop it in the box on your way out. Be courteous deposit your trash, and do not take the handouts for the following session.
The SAP TechEd 03 Basel Team

Copyright 2003 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Copyright 2003 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die aus-drckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankn-digung gendert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint und SQL Server sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix und Informix Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Lndern. ORACLE ist eine eingetragene Marke der ORACLE Corporation. UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group. Citrix, das Citrix-Logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin und andere hier erwhnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp und weitere im Text erwhnte SAP-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Lndern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.

SAP Internet Transaction Server On Linux

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Internet Transaction Server On Linux

Uploaded by

Copyright:

Available Formats

SAP ITS 6.

20 on LINUX: Installation, Administration, Security, and Tuning

As a result of this workshop, you will be able to:

SAP AG 2003, PA351, Arno Esser, Page 2

SAP AG 2003, PA351, Arno Esser, Page 3

SAP System & The Web

Browser Browser Intranet Browser

Firewall Internet Web Server ITS

SAP AG 2003, PA351, Arno Esser, Page 4

SAP Internet Transaction Server

SAP AG 2003, PA351, Arno Esser, Page 5

How to offer a Service on the Web?

Web Server WGate AGate

Application ABAP ABAP Dynpro Screens Workbench Customization

Inside SAP System Business Logic

ITS Architecture Details

User Request User Request

Call WGate Call WGate

Send Prepared Send Prepared Request Request

Input Input WGate Browser Web Server

AGate Output Output

HTML Page HTML Page

HTML Page HTML Page

SAP AG 2003, PA351, Arno Esser, Page 8

Web Server Web Server software

Replies with data

Web Browsers Software used to access the Internet

ITS 6.20 Server Platforms

RedHat Enterprise Linux 2.1 ES/AS

SAP AG 2003, PA351, Arno Esser, Page 11

Virtual Web Servers

SAP AG 2003, PA351, Arno Esser, Page 12

Apache Web Server Directory Structure

Example: Root directories for virtual Web Servers

SAP AG 2003, PA351, Arno Esser, Page 13

SAP AG 2003, PA351, Arno Esser, Page 14

SAP ITS Installation

The setup program is based on SAPInst Installation tool which provides

SAP@Web Installation Guide

SAP AG 2003, PA351, Arno Esser, Page 15

SAP ITS Installation Requirements

Windows 2003 Server

SAP AG 2003, PA351, Arno Esser, Page 16

SAP ITS Installation Parameters

SAP ITS installation type Typical or Administration

SAP AG 2003, PA351, Arno Esser, Page 17

Single Host Installation

SAP Application Server

Dual Host Installation

NSAPI HTTPS APACHE

SAP Application Server

SAP AG 2003, PA351, Arno Esser, Page 19

Security Additional Protection

SAP Application Server

Virt. Web Server

Virt. Web Server

One physical server

SAP ITS Installation

SAP AG 2003, PA351, Arno Esser, Page 22

Preparing the SAP ITS Installation

SAP AG 2003, PA351, Arno Esser, Page 23

SAP ITS 6.20 Installation