ITS 6.20 Installation - Part 2

SAP TechEd 03 Las Vegas
2003 SAP Labs, LLC PA351, Edgar Chuang, Dr. Klaus Layer 1
SAP ITS 6.20: Installation,
Administration, Security,
and Tuning
Edgar Chuang & Klaus Layer
SAP AG
SAP AG 2003, PA351, Edgar Chuang & Dr. Klaus Layer, Page 2
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
Agenda
Introduction
1
1
Web Servers & Platform Matrix
2
2
SAP ITS Installation
3
3
SAP ITS Administration & Configuration
4
4
Additional Information
5
5
SAP System & The Web
Intranet
Browser
Browser
GUI
PC
PC
Internet
Web
Server
Browser
Browser
Browser
ITS
Firewall
SAP System
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 System
Web Server
AGate
Service Files
Service description
HTML Templates
Language Resource
Files
Flow Files
SAP ITS
Application
ABAP
Dynpro Screens
Customization
Web Browser
Inside SAP System
Business Logic
WGate
MIME Files
Images
Stylesheets
Javascripts
Multimedia
ABAP
Workbench
Outside SAP System
HTML Visualization
SAP@Web
Studio or
ABAP
Workbench
SAP@Web
Studio or
ABAP
Workbench
SAP Internet
Application Component
BAPI
SAP Data
SAP System
ITS Architecture Details
Browser
WGate
Web Server
User Request
User Request
Send Prepared
Request
Send Prepared
Request
Input
Input
Output
Output
HTML Page
HTML Page
Call WGate
Call WGate
Load
Service File
Load
Service File
HTML
Templates
HTML Page
HTML Page
AGate
Load
HTML Templates / Flow Files
Load
HTML Templates / Flow Files
Flow
Files
Service
Files
Agenda
Introduction
1
1
2
2
3
3
4
4
5
5
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 Server
Web Browser
Web Server
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
Web Server
Web Browsers
Web Browser
Sends data
Receives data
ITS 6.20 Server Platforms
AGate
Microsoft Windows 2000 Server
Microsoft Windows 2003 Server
SUSE Linux Enterprise Server 8
RedHat Enterprise Linux 2.1 ES/AS
SAP@Web Studio
Microsoft Windows 2000 Workstation
WGate
Microsoft Windows 2000 and 2003
Server
Microsoft Web Server (ISAPI)
Apache HTTP Server (Apache Module)
SUN One Web Server (NSAPI)
Solaris
SUN One Web Server
Linux / Intel
RedHat Enterprise Linux 2.1 ES/AS
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 IIS 5.0 file directory is C:\INETPUB\WWWROOT.
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
Microsoft IIS Web Server Directory Structure
C:
\INETPUB (default web area)
\WWWROOT (default web root directory)
Example: Root directories for virtual Web Servers
C:
\INETPUB
\WWWWEBGUI (Web area for SAP ITS
WEBGUI)
\WWWADM (Web area for SAP ITS ADM)
Web Site creation
Start the Internet Services Manager (Control
Panel Administrative Tools). Right-click on
the name of your computer in the left frame of
the window and select New Web Site.
Type WEBGUI, click Next.
Select TCP Port 1080 and click Next.
Provide the path to the
virtual Web Server root
directory and click Next.
Deselect all options
except Read and
click Next. On the
next screen click
Finish.
Exercise 1
Create the directories and the corresponding virtual Web
Servers for your SAP ITS installation
Create 2 directories under C:\INETPUB for your virtual Web Servers
named
WWW-WEBGUI
WWW-ADM
Each of these will serve as a root directory for a virtual Web Server
instance
Create two virtual Web Servers using the Microsoft Management
Console (Start Programs Administrative Tools Internet Services
Manager)
Create the first virtual Web Server and call it WEBGUI
Use the directory C:\INETPUB\WWW-WEBGUI
Set it up on port 1080
Create the second virtual Web Server and call it ADM
Use the directory C:\INETPUB\WWW-ADM
Set it up on port 2080
Agenda
Introduction
1
1
2
2
3
3
4
4
5
5
You can get the installation files from
The Server Components CD (directory \\its\nt\i386).
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)
Web Web
Server Server
SAP SAP
Application Application
Server Server
ITS
ITS
W
G
a
t
e
A
G
a
t
e
TCP/IP TCP/IP
Windows 2000 Server
Windows 2003 Server 32-bit
RedHat Enterprise Linux 2.1
RFC RFC
DIAG DIAG
Single Host Installation
NSAPI NSAPI
APACHE APACHE
ISAPI ISAPI
HTTP HTTP
HTTPS HTTPS
Dual Host Installation
Web Web
Server Server
SAP SAP
Server Server
ITS
ITS
W
G
a
t
e
A
G
a
t
e
RFC RFC
DIAG DIAG
TCP/IP TCP/IP
HTTP HTTP
HTTPS HTTPS
NSAPI NSAPI
APACHE APACHE
ISAPI ISAPI
Wgate & Agate OS platforms:
Windows 2000 Server
Windows 2003 Server 32-bit
RedHat Enterprise Linux 2.1
These security measures are strongly recommended for productive
installations. The firewall between AGate and WGate is only possible in Dual
Host mode!
Web Web
Server Server
SAP SAP
Server Server
W
G
a
t
e
A
G
a
t
e
SAPRouter SNC, (SAPRouter possible)
Security Additional Protection
NSAPI NSAPI
APACHE APACHE
ISAPI ISAPI
Firewalls
DIAG DIAG
RFC RFC
TCP/IP TCP/IP HTTPS HTTPS
ITS ITS
1 1
W
G
a
t
e
Virt Virt. Web . Web
Server Server
ITS ITS
2 2
W
G
a
t
e
Virt Virt. Web . Web
Server Server
A
G
a
t
e
A
G
a
t
e
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.
TCP/IP TCP/IP
TCP/IP TCP/IP
Virtual instances
NSAPI NSAPI
APACHE APACHE
ISAPI ISAPI
NSAPI NSAPI
APACHE APACHE
ISAPI ISAPI
One physical server
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 start
the program
\its\nt\SETUP.CMD. You will
see a command shell and a
graphical user interfaces. If
your JAVA_HOME
environment variable is not
set, the command shell
window will warn you. Just
press any key. Normally
installation will find the Java
directory. Java is required by
SAPInst GUI.
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 (1)
When installing ITS for the first
time on a server you have to
enter (or browse for) an
installation directory. Accept
the default and click Next.
Accept the legal conditions
by choosing Yes and click
Next.
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).
On the IACOR Ports definition page normally nothing has to be
done. Please just confirm this page by clicking Next
Confirm the default setting and click Next.
Enter WEBGUI as the name of your ITS and the SAP system name
provided during class. Click Next.
Select web server Microsoft IIS 5.0 (WEBGUI) and click Next.
Select connection mode Application Server, enter the connection
data provided during class and click Next.
Confirm Application Server Port definition dialog.
Select yes to start ITS instance 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.
Remark: Upgrade of an older ITS installation
If SAP ITS 6.20 Installation detects a previous version of ITS, it will
offer a take over of the detected instance definitions. Please note
that it will only deactivate the services of the old ITS. You have to
remove them manually.
Remark: Instance/System Number
During the Installation your are asked for an IACOR System
Number and a instance number for each ITS instance. Hey, whats
that?
The system/instance number is something like a namespace to
avoid shared memory clashed between different applications (i.e.
R/3, ITS, Gateway, IACOR). Changing this number is *ONLY*
needed when ITS and SAP system or gateway run on the same
server. In that case you have to check the system numbers of
previous installed R/3 or gateway and adjust the proposed
numbers during ITS installation.
If you use the same system/instance number for ITS and R/3
system, the first one you start will catch the number while the
other will fail to start.
ITS Installation will always start with 40 for IACOR and then will
count up for each instance.
Adding an addition ITS 6.20 instance
To create an additional instance after a successful installation
select:
1. Start Programs SAP Inst ITS 6.20Prepare new Installation
Will clean up installation and write logs for later usage to backup directory
2. Start Programs SAP Inst ITS 6.20SAPInst Server with GUI
Will start installation engine and GUI to add another ITS instance
Exercise 2
Install a typical SingleHost SAP ITS instance to your WEBGUI Web
Server instance
Use SAP System data provided during class.
Use the Development Configuration.
Install an administrative instance to your ADM Web Server instance
Notice the differences in the installation dialog.
Start the SAP ITS application webgui (SAP GUI for HTML) by opening
a Web Browser and requesting the URL
http://<yourServer>:1080/scripts/wgate/webgui_start/!
where <yourServer> is replaced by the IP address or DNS name of
your computer. Use the logon data supplied in class.
If webgui does not respond please check if your webserver instance is
running.
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
One AGate can be connected to several Web Servers/WGates
Web Server
Web Browser
Web Browser
SAP System
WGate
Web Server
WGate
AGate
SAP ITS - SAP System Scalability
One SAP ITS can use several Application Servers of one SAP
System via:
Load Balancing
Separate selection of a specific Application Server
SAP System
Web Browser
Message
Server
Appl.
Server
Web Server
WGate AGate
SAP ITS Load Balancing
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
SAP System
Web Browser
Web Server
WGate
AGate
AGate
AGate
HTTP Router
HTTP Routing / High Availability
Web Browser
Web Server
WGate
Web Server
WGate
AGate
AGate
AGate
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
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
Web Browser
Web Server
WGate
SAP ITS AGate
Mapping
Manager
AGate
processes

Wgate Configuration Tool (1)
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 (2)
Edit ItsRegistryWgate.xml with you favorite editor and change
ConfigMonitorEnabled in global section to yes
Wgate configuration tool: (3)
URL Section
Logical Instances
Global Parameters
Activation/Reload
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. Apache X
Switch off the tool after configuring Wgate, otherwise your Wgate
will be open to anyone for configuring
Wgate Configuration Tool Dos and Donts
Exercise 3
Enable the Wgate Config tool. Open the ItsRegistryWgate.xml with
notepad. 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://<yourServer>:1080/scripts/wgate/wgate-config?
and to create a second AGate section for instance WEBGUI (use the
connection information provided during class).
Create a second AGate section for instance ADM (use the connection
information provided during class).
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 (1)
Start C:\Program Files\SAP\ITS\6.20\
Programs\IACORAdmin.exe on your
host. In addition to the window on
the right the below popup appears.
IACOR services is not automatically started by installation. Please click
Start to start the IACOR service.
IACOR Setup (2)
Now you can press New to
create RFC destinations for
your ITS instances.
In the field ITS Instance enter
WEBGUI, press TAB and
change the entry for Web
Server to the Web Server
directory belonging to the
instance WEBGUI. Click OK.
Enter the data provided during
class. In the bottommost
section you need to enter the
login data of a user privileged
to create RFC destinations in
the SAP System.
IACOR Setup (3)
Mark the new destination and
click Start to activate it.
The red o in the upper
right corner turns green
and the connection
status is now activated.
IACOR is ready to
receive files.
Using IACOR (1)
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 (2)
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.
In the IACOR
window you can
track the progress
of publishing. Errors
(if any) are reported
both in IACOR and
the SAP System.
Exercise 4
Install IACOR as a Windows Service
(start C:\Program Files\SAP\ITS\2.0\Admin\IACORAdmin.exe).
Create an RFC destination in the SAP System by using the New button. Use
the data provided in class.
Logon to the SAP System using SAP GUI for HTML and start transaction
SE38. Execute the report W3_Publish_Services, skip the first screen, select
the correct SAP ITS instance via Workbench settings, choose to publish the
IAC sysmsg and press Publish.
Logoff from the SAP System.
Start the IAC sysmsg via the URL
http://<yourServer>:1080/scripts/wgate/sysmsg/!
Agenda
Introduction
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
Default Login: itsadmin
Password: init
URL request for login:
http://<server>:<port>/scripts/wgate/
admin/!
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 AGate section
in wgate.conf.
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 Overview screen the
current load on all instances and
the load balancing situation 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.
The configuration of other
IACs (Internet Application
Components) can be
changed with
Configuration Services
<name of the service>.
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 .
SAP ITS Tuning Parameters (1)
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.
The most important settings regarding SAP ITS performance can be
accessed by selecting Configuration Performance.
SAP ITS Administration: Performance Settings
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 (2)
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
Pool of
Workthreads
Session Pool
Dispatcher
In Port
AGate
Workthread/Session Model
SAP System
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 the 2GB 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.
2001/08/29 09:38:33.686: --- log opened ------------------------------------------
2001/08/29 09:39:33.692: H:
2001/08/29 09:39:33.692: H:=======================================================================
2001/08/29 09:39:33.692: H:ID Avai Max Avai Max Hits/ TAT Number Uptime
2001/08/29 09:39:33.692: H: Sess Sess Thrds Thrds Sec Hits (hh:mm:ss)
2001/08/29 09:39:33.692: H:========================================================================
...
2001/08/29 10:19:33.944: D: 0 61 64 4 4 0.000 0.005 0 00000:41:00
2001/08/29 10:20:33.950: D: 0 60 64 3 4 0.000 0.294 0 00000:42:00
2001/08/29 10:21:33.956: D: 0 60 64 4 4 0.000 0.004 0 00000:43:00
2001/08/29 10:22:33.963: D: 0 60 64 3 4 0.000 0.028 0 00000:44:00
2001/08/29 10:23:33.969: D: 0 60 64 4 4 0.000 0.000 0 00000:45:00
This is an excerpt taken from a sample
performance.log:
SAP ITS Administration: Setting Trace File
Parameters
Use Configuration Traces to
alter the settings for SAP ITS trace
files (likewise for log files).
Tracelevel is the level of
detail used to create the
trace file for this SAP ITS
instance. 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.
Controlling SAP ITS 6.20, IACOR and Web Server
instances
To stop an SAP ITS 6.20 instance expand
the node Control for this instance and
click Stop for ITS Manager.
Click Start or mark SAP ITS Manager
<instance name> and push the play button
in the Services Manager to restart this
instance.
You can check the state of
the service via Control
Panel Administrative
Tools Services. Search
for entry SAP ITS Manager
<instance name>.
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. From these
numbers you can also
conclude that the number of
Workthreads on this instance
is suitable since the fourth
Workthread was never used. If
the overall load on the SAP
ITS increases you should
consider to configure more
Workthreads. In a scenario
like this it might also be a
good idea to check the sizing
of the SAP System.
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 2GB).
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 5
Start SAP ITS Administration with the URL http://<your
computer>:2080/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.
Stop and start your SAP ITS instance WEBGUI.
Explore!
Agenda
Introduction
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
Related Lectures at TechEd 2003

Future of ITS, PA104, WEN 8:00 am+THU
2:45pm, GB117
UI Clients for SAP NetWeaver, UI101, WEN
1:30pm+THU 8:00am, P1
Literature
SAP@Web Installation Guide
SAP ITS Tuning & Troubleshooting Guide
SAP ITS Administration Guide
SAP ITS Service Parameters
SAP Technology:
Web Application Development Curriculum
SAPTEC
mySAP Technology
Solution Overview
2 days
ITS070
SAP ITS:
Administration
3 days
ITS150
SAP ITS:
Corporate Identity
Design
2days
NET050
Web Application
Development:
Foundations
3 days
HTML, CSS
Knowledge,
Internet
Terminology
BC400
ABAP Workbench:
Foundation and
Concepts
5 days
NET100
SAP ITS:
Developing Screen
based Internet
Application Comp.
3 days
NET200
SAP Web Application
Server:
Developing Web
Applications
3days
Necessary
Q&A
Questions?
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 Las Vegas Team
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 Server
TM
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. All Rights Reserved
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 Server
TM
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.
Copyright 2003 SAP AG. Alle Rechte vorbehalten

ITS 6.20 Installation - Part 2

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ITS 6.20 Installation - Part 2

Hochgeladen von

Copyright:

Verfügbare Formate

SAP TechEd 03 Las Vegas

SAP TechEd 03 Las Vegas

Related Lectures at TechEd 2003

and SQL Server

are registered trademarks of

, DB2 Universal Database, OS/2

, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere

is a registered trademark of ORACLE Corporation.

are registered trademarks of the Open Group.

, the Citrix logo, ICA

, World Wide Web Consortium,

is a registered trademark of Sun Microsystems, Inc.

und SQL Server

sind eingetragene Marken der

, DB2 Universal Database, OS/2

, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere

ist eine eingetragene Marke der ORACLE Corporation.

sind eingetragene Marken der Open Group.

, das Citrix-Logo, ICA

, World Wide Web Consortium,

ist eine eingetragene Marke der Sun Microsystems, Inc.

Das könnte Ihnen auch gefallen