Sap @web 6.20 Installation Guidepatchlevel 23 or Higher

PUBLIC
Installation Guide
SAP @WEB 6.20

Installation
GuidePatchlevel 23
or higher
Including Installation of SAP ITS on Windows,
Linux (AGate/WGate) and SAP@Web Studio
Target Audience
n System administrators
n Technology consultants
Document version: 1.0 ‒ 11/29/2006

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2007 SAP AG. All rights reserved. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services mentioned
No part of this publication may be reproduced or
herein as well as their respective logos are trademarks or
transmitted in any form or for any purpose without the
registered trademarks of SAP AG in Germany and in several
express permission of SAP AG. The information contained
other countries all over the world. All other product
herein may be changed without prior notice.
and service names mentioned are the trademarks of their
Some software products marketed by SAP AG and its
respective companies. Data contained in this document
distributors contain proprietary software components of
serves informational purposes only. National product
other software vendors.
specifications may vary.
Microsoft, Windows, Outlook, and PowerPoint are These materials are subject to change without notice.
registered trademarks of Microsoft Corporation. These materials are provided by SAP AG and its affiliated
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, companies (“SAP Group”) for informational purposes
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, only, without representation or warranty of any kind, and
pSeries, xSeries, zSeries, System i, System i5, System p, SAP Group shall not be liable for errors or omissions with
System p5, System x, System z, System z9, z/OS, AFP, respect to the materials. The only warranties for SAP Group
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, products and services are those that are set forth in the
i5/OS, POWER, POWER5, POWER5+, OpenPower and express warranty statements accompanying such products
PowerPC are trademarks or registered trademarks of IBM and services, if any. Nothing herein should be construed as
Corporation. constituting an additional warranty.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
This document was created using stylesheet 2006-12-31
are either trademarks or registered trademarks of Adobe
(V5.1) and XSLT processor SAXON 6.5.2 from Michael Kay
Systems Incorporated in the United States and/or other
(http://saxon.sf.net/), XSLT version 1.
countries.
Oracle is a registered trademark of Oracle Corporation.
Disclaimer
UNIX, X/Open, OSF/1, and Motif are registered trademarks
Some components of this product are based on Java™. Any
of the Open Group.
code change in these components may cause unpredictable
Citrix, ICA, Program Neighborhood, MetaFrame,
and severe malfunctions and is therefore expressively
WinFrame, VideoFrame, and MultiWin are trademarks or
prohibited, as is any decompilation of these components.
registered trademarks of Citrix Systems, Inc.
Any Java™ Source Code delivered with this product is
HTML, XML, XHTML and W3C are trademarks or registered
only to be used by SAP’s Support Services and may not be
trademarks of W3C®, World Wide Web Consortium,
modified or altered in any way.
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
Documentation in the SAP Service
JavaScript is a registered trademark of Sun Microsystems,
Marketplace
Inc., used under license for technology invented and
You can find this document at the following address:
implemented by Netscape.
https://service.sap.com/instguides
MaxDB is a trademark of MySQL AB, Sweden.
2/84 PUBLIC 11/29/2006

Typographic Conventions
Example Description
< > Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
Example Textual cross-references to an internet address, for example, http://www.sap.com
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11/29/2006 PUBLIC 3/84

Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You
can find the latest version on SAP Service Marketplace http://service.sap.com/instguides.
The following table provides an overview on the most important document changes:
Version Date Description
1.0 11/29/2006 Initial version
4/84 PUBLIC 11/29/2006

Table of Contents
Chapter 1 SAP@Web Installation Guide: Release 6.20 Patch 23 and higher . . . 7
Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Required Documentation . . . . . . . . . . . . . . . . . . . 9
2.2 ITS Security . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 ITS Installation Options . . . . . . . . . . . . . . . . . . . . 11
2.4 Hardware and Software Requirements . . . . . . . . . . . . . . . 14
2.5 IAC Packages . . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 ITS with LDAP and WLBS (Windows only) . . . . . . . . . . . . . 18
2.7 Upgrade from a pre-620 ITS to Release 6.20 . . . . . . . . . . . . . 21
Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1 Creating the ITS Administrator Account (Windows only) . . . . . . . . 23
3.2 Creating Web Server Instances . . . . . . . . . . . . . . . . . 24
3.3 Preparing the System for SAPinst . . . . . . . . . . . . . . . . . 28
Chapter 4 Installation Procedure . . . . . . . . . . . . . . . . . . . . 31

4.1 Installation on Windows . . . . . . . . . . . . . . . . . . . . 31
4.1.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 31
4.1.2 Installing an ITS instance on Windows . . . . . . . . . . . . . . . 33
4.1.3 Installing additional ITS Instances on Windows . . . . . . . . . . . 35
4.2 Installation on Linux . . . . . . . . . . . . . . . . . . . . . 36
4.2.1 Running SAPinst on Linux . . . . . . . . . . . . . . . . . . . 36
4.2.2 Installing an ITS Instance on Linux . . . . . . . . . . . . . . . . 38
4.2.3 Starting and stopping an ITS Instance on Linux . . . . . . . . . . . 39
4.3 Patch Installation . . . . . . . . . . . . . . . . . . . . . . 40
4.4 Compilation 4 / Patch Level 4: Script-Based Installation . . . . . . . . 40
Chapter 5 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . 43

5.1 Starting an ITS Service from a Web Browser . . . . . . . . . . . . . 43
5.2 Checking the ITS Installation . . . . . . . . . . . . . . . . . . 44
5.3 IAC Publishing with IACOR . . . . . . . . . . . . . . . . . . 47
5.3.1 Managing IACOR . . . . . . . . . . . . . . . . . . . . . . 47
5.3.2 Publishing the IACs from a SAP system . . . . . . . . . . . . . . 50
5.4 Watchdog Configuration (Windows only) . . . . . . . . . . . . . 51
11/29/2006 PUBLIC 5/84

5.4.1 Configuring Watchdog for WLBS . . . . . . . . . . . . . . . . . 51
5.4.2 Registering ITS in an LDAP Directory . . . . . . . . . . . . . . . 53
5.4.3 Monitoring with Watchdog . . . . . . . . . . . . . . . . . . . 55
5.4.4 Registry Configuration . . . . . . . . . . . . . . . . . . . . 56
5.4.5 Watchdog: Additional Information . . . . . . . . . . . . . . . . 58
Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 61

6.1 SAP ITS Specific Information . . . . . . . . . . . . . . . . . . 61
6.2 Uninstalling the ITS . . . . . . . . . . . . . . . . . . . . . 63
6.3 SAP@Web Studio Installation . . . . . . . . . . . . . . . . . . 64
6.3.1 SAP@Web Studio — Overview . . . . . . . . . . . . . . . . . 64
6.3.2 SAP@Web Studio Installation Requirements . . . . . . . . . . . . 65
6.3.3 Preparing the SAP@Web Studio Installation . . . . . . . . . . . . . 66
6.3.4 Installing the SAP@Web Studio . . . . . . . . . . . . . . . . . 66
6.3.5 Post-Installation for SAP@Web Studio . . . . . . . . . . . . . . . 67
6.4 General Information about ITS . . . . . . . . . . . . . . . . . 68
6.4.1 ITS Instances . . . . . . . . . . . . . . . . . . . . . . . . 69
6.4.2 ITS File Types and Locations . . . . . . . . . . . . . . . . . . 74
6.4.3 Backup Strategy (Optional) . . . . . . . . . . . . . . . . . . . 77
6.5 General Information about SAPinst . . . . . . . . . . . . . . . . 78
6.5.1 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 78
6.5.2 Remote Installation with SAPinst . . . . . . . . . . . . . . . . 79
6.5.3 Starting SAPinst on the Remote Host (Optional) . . . . . . . . . . . 80
6.5.4 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 81
6.5.5 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 82
6/84 PUBLIC 11/29/2006

1 SAP@Web Installation Guide: Release 6.20 Patch 23 and higher
1 SAP@Web Installation Guide: Release

6.20 Patch 23 and higher
Purpose
This documentation describes how to install the SAP Internet Transaction Server (ITS) and related
tools on released Windows and Linux platforms:
Note
For more information
n About released platforms, see http://service.sap.com/platforms SAP NetWeaver in Detail
Application Platform User Interfaces SAP GUI Family SAPGUI for HTML/InternetTransaction Server
Platforms Supported and SAP Note 325616 ITS System Requirements.
n SAP Internet Transaction Server (ITS)

n SAP Internet Transaction Server Administration
n Internet Application Components Object Receiver (IACOR)
n ITS Watchdog (Windows only)
n SAP@Web Studio
Implementation Considerations
n If you want to give Internet and intranet users direct access to the SAP system by enabling them
to start SAP Internet applications based on the ITS infrastructure from a Web browser, you must
install the Internet Transaction Server (ITS).
n If you want to monitor or tune all existing ITS instances via SAP’s delivered, Web-based user
interface you must install ITS Administration.
n If you want to publish files directly from the SAP system to the ITS and the Web server, and enable
an automatic update of these files whenever the SAP system is updated by a transport, you
should install the IACOR.
If you have an SAP system 6.10 or higher, you must publish all IACs directly from the SAP system
to your ITS instances via the IACOR. You can publish IACs since SAP systems of Release 4.6C.
n If you want to monitor the connections from WGate via AGate to a SAP system you may install the
ITS Watchdog service. It is a simple Windows service running on a Web host.
n If you want to develop your own ITS services or if you want to modify existing ITS services you
may use the SAP@Web Studio as a complete ITS development environment.
11/29/2006 PUBLIC 7/84

1 SAP@Web Installation Guide: Release 6.20 Patch 23 and higher
Integration
You must have installed the released Web server and Web browser software.
Features
Once you have installed the ITS, Internet and intranet users can access the SAP system by starting
applications, which are Internet-enabled transactions, function modules and reports, from a Web
browser.
SAP GUI for HTML automatically maps the screen elements in SAP transactions to HTML using
HTMLBusiness functions available within the SAP Internet Transaction Server. As a result, SAP Internet
Transaction Server can dynamically generate an HTML version of an SAP screen.
Note
The SAP@Web Studio has its own installation tool that is not integrated into SAPinst.
New ITS Feature

With Release 6.20, the AGate can now be installed on released Linux platforms.
8/84 PUBLIC 11/29/2006

2 Planning
2 Planning
Activities for Windows
1. Check the required documentation [page 9].

2. Check ITS Security [page 10].
3. Check the ITS Installation Options [page 11].
4. Check what kind of Internet Application Components (IACs) you need: IAC Packages [page 15].
5. If you install the current ITS on a host with a installed pre-4.6D ITS Release, check: Upgrade from a
pre-6.20 ITS to Release 6.20 [page 21].
6. Check the installation requirements [page 14].
7. Decide whether you want to use the ITS in an SAP environment with Lightweight Directory Access Protocol
(LDAP) and/or Microsoft Windows Load Balancing Service (WLBS) [page 18].
Activities for Linux
1. Check the required documentation [page 9].

2. Check ITS Security [page 10].
3. Check the ITS Installation Options [page 11].
4. Check what kind of Internet Application Components (IACs) you need: IAC Packages [page 15].
5. If you install the current ITS on a host with a installed pre-4.6D ITS Release, check: Upgrade from a
pre-6.20 ITS to Release 6.20 [page 21].
2.1 Required Documentation
SAP Notes
Read the ITS installation notes before beginning the installation. These notes contain the most recent
information regarding the installation, as well as corrections to the installation documentation. Make
sure that you have the most recent version of each note. You can find the SAP Notes in SAP Service
Marketplace at https://service.sap.com/notes.
Installation Notes for SAP@Web
SAP Note Description

889588 Installation of SAP Internet Transaction Server 6.20
Patch 20 or higher
491781 ITS Updates in Release 6.20
11/29/2006 PUBLIC 9/84

2 Planning
2.2 ITS Security
SAP Note Description

325616 ITS System Requirements
375810 Installing the ITS for SAP Employee Self-Service
197746 Maintenance strategy: Internet Transaction Server
(ITS)
325149 Publishing IAC objects
336884 IACOR in ITS Dual Host Installations
537320 ITS Standards — Recommended Web browser
settings
Special Linux-related SAP Notes:
671766 Supported platforms for ITS on Linux
Additional Information
For information about:
n General information on ITS, Windows Service, monitoring and configuration, see
https://service.sap.com/sap-its Media Center Literature .
n ITS Sizing, see the Sizing the Internet Transaction Server guide at: https://service.sap.com/sizing.
n Security issues, see the SAP NetWeaver Security Guide at https://service.sap.com/securityguide.
n Platforms released for SAP ITS AGate and WGate see https://service.sap.com/platforms
SAP NetWeaver in Detail Application Platform User Interfaces SAP GUI Family SAPGUI for
HTML/Internet Transaction Server Platforms Supported .
2.2 ITS Security
Enabling Internet users to communicate directly with the SAP system via the Internet Transaction
Server (ITS) has obvious advantages for business users, but it also raises a number of security issues.
You can secure your ITS installation by
n Separating WGate and AGate
n Protecting ITS files
n Restricting access to the SAP system
Separating WGate and AGate

To minimize unwanted access by unauthorized users, it makes sense to separate SAP system-related
information (particularly passwords and connection information) from the Web server and restrict
generally available functionality to a bare minimum. This means installing WGate and AGate
on different machines.
For more information, see ITS Installation Options [page 11].
10/84 PUBLIC 11/29/2006

2 Planning
2.3 ITS Installation Options
Restricting Access to the SAP system

To run SAP Internet applications - known to the ITS as services - from a Web browser, users need an
SAP system user account. To set this up, you can do any of the following:
n Create a global SAP system user account for all services.
In this case, users can start any service.
n Create a specific SAP system user account for each individual service.
In this case, users can only start those services for which they have a user account.
n Create no static SAP system user account.
In this case, users are prompted for a user name and password in a logon procedure each time a
service is started.
The ITS handles security very strictly. If you enter user data into a service file to allow anonymous
access to the SAP system, you should encrypt the password using SAP@WebStudio, ITS
Administration or ABAP Workbench.
Note
Using one global SAP system user account with extensive authorizations can be a security risk.
Although SAPinst may use one global user account, we strongly recommend that you apply
security settings for each service. Your SAP system administrator must set up service-specific
user accounts.
Note
For more information about security issues, see the SAP NetWeaver Security Guide at
https://service.sap.com/securityguide.
One of the most critical factors you must take into account when deciding how to install the Internet
Transaction Server (ITS) is security.
Linking the SAP system to the Internet via the ITS raises obvious security issues, because it exposes
data to unauthorized or illegal access. For this reason, it is advisable to separate sensitive data in a SAP
system from the Web server and restrict available functions to a bare minimum.
The security risks posed by the WGate and AGate components of the ITS vary:
n WGate is small and functionally simple. Its sole function is to pass requests back and forth between
the Web server and the AGate, so there are few possible targets of attack.
n AGate, however, handles most of the processing required to run a transaction over the Internet
and is connected directly to a SAP system, so security is critical.
You can install WGate and AGate:
n On the same machine in a single host installation
11/29/2006 PUBLIC 11/84

2 Planning
n On separate machines in a dual host installation

It is best to install the components on separate machines, especially when setting up production
systems. This allows you to place a firewall between them and increase the level of protection.
Single Host Installation

A single host installation places the Web server, WGate and AGate on the same host machine:
Figure 1: Single Host Installation
The AGate instance may consist of more than one AGate process. For more information, see ITS
Instances [page 69].
The single host installation is appropriate for development and test systems where security is less
critical and may also be sufficient for some intranet applications. In this case, you can just place a
firewall between the Web server and the client PCs.
Dual Host Installation

A dual host installation places WGate and AGate on separate host machines - WGate on the Web
server host and AGate on a different host:
12/84 PUBLIC 11/29/2006

2 Planning
Figure 2: Dual Host Installation
There may be one AGate instance running one or more AGate processes on the same machine or
multiple AGate instances running on different machines. For more information, see ITS Instances
[page 69].
The dual host installation is appropriate for production systems where security is vital. In this case, a
firewall between WGate and AGate is indispensable.
To maximize security, you could install a firewall between the Web browser and the Web server, a
firewall between WGate and AGate, and a firewall between AGate and SAP system:
Figure 3: Dual Host Installation with Firewall
11/29/2006 PUBLIC 13/84

2 Planning
2.4 Hardware and Software Requirements
IAC Installation Using the Package Manager

The tool Package Manager allows you to easily apply additional IAC packages to existing ITS instances,
for example if you have missed installing a package or if a patch for an installed package is delivered.
2.4 Hardware and Software Requirements
Hardware Requirements
The tables below specify the minimum hardware you need to run the ITS, depending on whether
you are performing a single host installation or a dual host installation.
However, remember that memory and disk space requirements can vary, depending on factors such
as the number of users concurrently accessing the system.
For more information on ITS Sizing, see the Sizing the Internet Transaction Server guide at
https://service.sap.com/sizing.
Minimum Hardware Requirements for AGate (Single or Dual Host Installation)
Component Requirement
Hardware Intel Pentium compatible architecture
Backup (optional) Either over network or tape drive
Hard disk 1 GB
Memory (RAM) 256 MB
Hardware systems with 256 MB RAM are only
recommended for non-production purposes such as
development and testing.
For WGate (in dual host installation environments), see the Web server vendor information for
hardware requirements.
Software Requirements
For information about ITS software requirements (including supported platforms, Web servers,
and Web browsers), read the section SAP Internet Transaction Server in SAP system Requirements for Networks,
Frontends, Communication Interfaces at https://service.sap.com/platforms Platform Strategy for Front
End & Middleware Components .
See also SAP Note 325616.
Requirement Checklists
The following tables specify all the information you need to install the ITS. Make sure that you have
this information available before running SAPinst.
SAP Parameters
n SAP system name
14/84 PUBLIC 11/29/2006

2 Planning
2.5 IAC Packages
n Client
n User (global user for all services)
n Password matching user and client
You only need to provide values for client, user, and password in the case you want to allow
anonymous logins to the SAP system. SAPinst places this encrypted information in the global service
file that contains settings for all services.
SAP Parameters (Load Balancing or Single Application Server)
Option Load Balancing Single Server Application

SAP message server name X Not applicable
Port number for SAP message X Not applicable
server
Login group used by ITS X Not applicable
SAP application server name Not applicable X
SAP system number Not applicable X
SAProuter string X (optional) X (optional)
WGate Installation
Options WGate Installation on Separate Single Host Installation

Host
Name or IP address of AGate host X Not applicable
Number of ports X Not applicable
(sapavw00_<virtual ITS> and
sapavwmm_<virtual ITS>) on
AGate host
You can find the ports on the
AGate host in the file
<drive>:\<winnt>\system32
\drivers\etc\services
where <drive> is the system's hard
drive and <winnt> is your Windows
directory on the AGate host.
2.5 IAC Packages
Internet Application Components (IACs) are applications that consist of one or more ITS service(s)
(including a number of related ITS files (HTML templates, Language Resource files, Mimes etc.) and
SAP business applications (transaction, function call, or BAPI).
11/29/2006 PUBLIC 15/84

2 Planning
2.5 IAC Packages
They allow Internet and Intranet users to start SAP transactions, function modules and reports from
a Web browser via the Internet Transaction Server (ITS).
Until SAP release 4.6D, SAP created an own standard IAC package for each SAP release that contains
all the files you need to run IACs for this release. Furthermore, there are special packages for running
SAP ITS Administration etc. integrated into SAPinst. All these packages are delivered with the ITS and
SAP@Web Studio on the Server Components CD (part of the SAP NetWeaver Presentation DVD).
SAPinst allows you to install the ITS system packages as part of the standard installation procedure.
To access other, application-dependent IAC packages, you can browse the file system.
Note
For more information about developing your own IACs, see SAP@Web Studio Installation [page 64].
How SAPinst Handles IAC Packages

Prior to SAP release 6.10, all the ITS files needed to run IACs for a specific SAP release were shipped
separately from SAPinst in IAC packages.
If you have an SAP system of release 6.10 or higher, you must publish all IACs directly from the SAP
system to your ITS instances via the IACOR. You can publish IACs as of SAP systems of Release 4.6C.
As stated above, SAPinst allows you to select the IAC packages you want to install with a particular ITS
instance. Packages are either integrated into the setup or located in a file system or other network
location:
n Packages integrated into the setup
The packages dialog contains a list of packages that are available for installation with the current
ITS release. You can select the packages you want to install from this list.
The list does not include the standard IAC packages.
Standard IAC packages for the ITS
IAC Package Description

system ITS System services and templates
Integrated into SAPinst and installed automatically.
webgui SAP GUI for HTML package
You need this package if you are installing the SAP
GUI for HTML. You need this IAC also, if you use
an IAC for the standard Releases (4.6C_all.sar, for
example).
its_adm ITS Administration package
Integrated into the SAPinst of an administration
instance and installed automatically.
16/84 PUBLIC 11/29/2006

2 Planning
2.5 IAC Packages
IAC Package Description

Watchdog ITS Watchdog package
Integrated into the SAPinst of an administration
instance and installed automatically, if required.
All of the above packages and the additional IAC packages you select for installation are copied by SAPinst
to the directory <ITS_InstDir>\install\packages.
Note
The ITS is downward compatible to all currently supported SAP releases.
For more information on supported SAP releases, see SAP Note 197746.
n Packages on the Server Components CD:

The application-specific IAC packages for SAP systems of Release ≤ 4.6D can be found on the
Server Components CD.
For a SAP system of Release ≥ 6.10 you have to publish the application-specific IACs directly from
the SAP system to the corresponding ITS instance (AGate and WGate) via the tool Internet
Application Components Object Receiver (IACOR).
For more information, see IAC Publishing with IACOR [page 47].
Example
If you want to integrate the SAP Web Application Server ≥ 6.20 or a SAP CRM ≥ 3.0 System (based
on Release 6.10), you must use IACOR.
During the installation, SAPinst displays all available IAC packages of the Server Components CD
(if starting the installation from CD). For each SAP system that you want the ITS to connect
to, you can select the corresponding application packages in addition to your selected standard
ITS IAC package (see above).
Note
Location (Server Components CD-ROM Path):
its/common/packages/<application>/<release>
Example
You want to integrate an R/3 4.6B and an SAP BW 2.0B System. In this case you should install
l an ITS instance for the SAP system with the IACs in directory its/common/packages/R3/46b
l another ITS instance for the SAP BW System with the IACs in directory
its/common/packages/BW/20b
n Packages located in a file system or other network location
11/29/2006 PUBLIC 17/84

2 Planning
2.6 ITS with LDAP and WLBS (Windows only)
The packages dialog allows you to browse for packages that are not integrated into the setup. This
is useful if you want to store several packages on a central file server and allow users to install these
packages over the network.
n Packages concatenated in the extrapkg.txt file
You can specify IAC packages in the file extrapkg.txt. These packages will then be listed during
installation. Thus, a simplified installation procedure can be achieved for the person who should
install IACs for a specific purpose.
How Installed IAC Packages Interact

You can install several IAC packages at the same time. All the packages you select are installed
together for one ITS instance. However, if you install packages that contain different versions of the
same IACs, one version overwrites the other.
Note
IACs should never occur simultaneously in more than one package.
When ITS has been set up in a dual or multiple host environment, you must make sure that identical
IAC packages (webgui, application-specific IACs, etc.) are installed on all WGate instances and all
AGate instances that are interlinked.
IAC Package File Names

The file names of IAC packages do not observe specific naming conventions, but the nature of the
package is usually clear:
n 46c_all.sar is a cross-application package for an SAP R/3 4.6C system.
n 46d_bas.sar is a package of Basis services for an SAP system with Basis Release 4.6D.
IAC package file names are not case-sensitive.
High availability solutions and very sophisticated administration tools (CCMS, MMC SnapIn) are
available for all components of a traditional SAP system. Since Release 4.6C SAP administration
has been further enhanced with automatic registration of all installed SAP components in LDAP
directories.
As of Release 4.6D the ITS WGate can connect to multiple AGates thus greatly increasing the ITS
fault tolerance.
Nevertheless, WGate failures are not covered by the mechanism. To achieve fault tolerance for the
WGate, one has to install multiple WGates and install an http router. Since the http router itself may
become a single point of failure, it may be necessary to use at least two http router devices.
18/84 PUBLIC 11/29/2006

2 Planning
ITS Watchdog is an optional tool for monitoring and managing ITS WGate instances in a LDAP
environment as well as obtaining high availability for several WGate instances using Windows
Network Load Balancing Service (WLBS).
You can install ITS Watchdog during an ITS Administration installation if you want.
The ITS Watchdog is a simple Windows Service running on a WGate host offering the following
functionality:
n Monitoring of all ITS instances running on the local host via a dual DCOM interface.
n Registration of ITS instance in LDAP directories (optional).
n High availability solution using Microsoft WLBS for the complete processing queue including
WGate (optional).
Why Using ITS Watchdog for LDAP?

Enabling ITS LDAP registration allows the integration of ITS WGate monitoring and administration
into the SAP MMC SnapIn.
If LDAP registration is enabled you can use an updated version of the SAP MMC SnapIn (running in
LDAP mode) to monitor and administer the ITS instances. It provides status information on all URLs,
integrates this information into the overall system status, periodically refreshes the information
and integrates with other administration tools like Microsoft IIS administration, Windows Service,
Terminal Server and Symantec pcAnywhere.
For more information about using the ITS Watchdog service after LDAP registration, see the online
help of SAP MMC.
So far the following problems have been noticed:
n The current load distribution that connects multiple AGates to a single WGate recognizes if an
AGate fails but it does not recognize when an AGate cannot connect to an SAP system. In the
latter case, for example, the login URL sometimes works (when directed to a working AGate)
and sometime fails (when directed to the AGate in trouble). This confuses The ITS Watchdog
availability check. So as long as the AGate load distribution is not enhanced you should not use it
together with The ITS Watchdog.
n The registration of the ITS Release in the LDAP directory (Attribute SAP-R3-ITSRelease)
currently does not work as it should. Instead of registering the ITS instance release, the ITS
Watchdog registers its own release for all monitored ITS instances. This is because there is no
reliable way of finding a WGate DLL for a given ITS instance.
Enabling ITS LDAP registration might impose a security problem. The ldapreg.srvc service needs
to be able to start the SAP function module WWW_LDAP_REGISTER_ITS. Therefore SAP user and
password must be specified in ldapreg.srvc. Even if you encrypt the password by using SAP@Web
Studio or ITSAdministration it is possible to start other Web enabled function modules in the SAP
system via the registration URL by overriding “_FUNCTION” in the URL.
11/29/2006 PUBLIC 19/84

2 Planning
Why Using ITS Watchdog for WLBS?

The basic idea of WLBS is to share an IP address with several hosts in a so-called cluster for some ports
(defined by so-called port rules). WLBS provides the following features:
n Each request addressing the cluster IP address is handled by exactly one server in the cluster.
n It is possible to specify an affinity model for each port rule. This can guarantee that the same server
in the cluster handles all requests of one client.
n WLBS automatically detects network or hardware failures of cluster servers and redistributes
the clients among the remaining servers. It also detects if a server becomes available again and
will add the server to cluster.
Therefore WLBS can be used to achieve both high availability and load balancing for TCP/IP services.
Nevertheless WLBS has some limitations that must be taken into consideration:
n WLBS cannot detect software failures by itself. For example, it does not recognize IIS, ITS WGate,
ITS AGate or SAP system failure. Watchdog will notice these software failures and enable/disable
the corresponding port rules.
n The WLBS load distribution algorithm seems to be rather simple. If client affinity is enabled (as
required for ITS) the distribution algorithm seems to be a simple function of the client IP address.
This enables each cluster server to rapidly decide which server is responsible for handling the
request (for example without any additional server interaction), but it requires that the client IP
addresses are statistically equal distributed. If for example, all clients connect via a proxy server
to the Web server WLBS load distribution does not work, since all clients seem to use the same
IP address.
n By enabling/disabling port rules on a cluster server, servers can join or leave the cluster.
Nevertheless, in both cases clients will be redistributed among the available servers. So some ITS
clients will loose the session context during the redistribution process.
ITS Watchdog with other LBS

In principle, ITS Watchdog can be used with other load balancing products or for a different purpose,
for example sending notification emails if ITS fails.
Nevertheless, the default installation parameters will support WLBS.
Can I use ITS Watchdog without having a LDAP or WLBS environment?

You can use ITS Watchdog as a very simple monitoring service for displaying the status and availability
of the WGate host via a Web browser.
This simple functionality is only available with Microsoft Internet Information Server (IIS).
20/84 PUBLIC 11/29/2006

2 Planning
2.7 Upgrade from a pre-620 ITS to Release 6.20
2.7 Upgrade from a pre-620 ITS to Release 6.20
The most important new feature is the support of the Linux platform for AGate and WGate. To
adapt all ITS components (AGate, WGate, and IACOR) for Windows and Linux, we provide now
the following developments for Release 6.20:
n A new cross-platform registry file: ItsRegistry<ITS_instance_name>.xml (default path:
<ITS_InstDir>/config).
n Scripts to start the ITS instances on Linux: Its<ITS_instance_name>.sh (default path:
<ITS_InstDir>/programs)
n A new cross-platform configuration file for the WGate: ItsRegistryWgate.xml (default path:
<ITS_InstDir>/config)
The file wgate.conf that has formerly configured the WGate instances now contains only a
reference to the WGate instance name. The default path for wgate.conf is:
l Apache: <WebServer_InstDir>/conf
l iPlanet, and Netscape Enterprise Web Server: <WebServer_InstDir>/config
l Internet Information Server: <ITS_InstDir>/programs
11/29/2006 PUBLIC 21/84

This page is intentionally left blank.
3 Preparation
3 Preparation
Before you install SAP ITS on a host, you have to prepare the host accordingly:
Windows only
1. Make sure that the Windows 2000/2003 Server software is properly installed.
Note
For security reasons, use the Windows File System NTFS to store ITS files. NTFS fully supports
Windows 2000/2003 security and long file names. To check that you are using NTFS:
a) Select the hard drive icon in the Windows Explorer.
b) From the context menu (secondary mouse click), choose Properties.
c) Choose the General tab.
d) Check that the specified file system is NTFS.
2. Create the ITS administrator account [page 23].

3. Configure Released Web Server Instances [page 24] on Windows.
Linux only
n Configure Released Web Server Instances [page 24] on Linux.
Activities for both operating systems
n Prepare the system for SAPinst [page 28].
3.1 Creating the ITS Administrator Account (Windows only)
You use this procedure to create the ITS administrator account.
Procedure
1. Log on to the Windows system as an administrator.
2. Choose Start Programs Administrative Tools Computer Management .
3. Choose System Tools Local Users and Groups Users .
4. Choose Action New User .
5. Enter the following values:
11/29/2006 PUBLIC 23/84

3 Preparation
3.2 Creating Web Server Instances
a) User Name: ITSadm

b) Full Name: SAP ITS Administrator
c) Description: <description>
d) Password: <password>
e) Confirm Password: <password>
6. Choose Create.
7. Choose Close.
When you create an ITS instance, you need to attach it to a Web server.
You can attach several ITS instances (AGates) to a single Web server instance (WGate).
Nevertheless, even despite the fact that all ITS instances on a single machine now use the same
WGate executable, we still recommend creating an own virtual Web server instance for each ITS
instance (WGate).
Thanks to the WGate configuration (see ITS Administration Guide), WGate knows which AGate it
should be communicating with in multiple instance configurations, so there is no need to run each
Web server instance in its own memory space. This improves performance considerably.
However, if you are creating an ITS instance to run ITS Administration, you should still create a
separate Web server instance. Running ITS Administration under its own dedicated ITS instance and
Web server instance makes sense, because you are then free to start and stop other ITS instances
whenever you want.
Note
For more information on ITS released Web Server Software, see Platform Strategy for Front End &
Middleware Components at https://service.sap.com/platforms.
Note
The following documentation for configuring released Web server software is only a quick guide to
creating your Web Server instances. For more details, see the vendor's documentation.
Configuring Released Web Servers on Windows

MS Internet Information Server Instances (IIS instances)
1. Make sure to use a version of IIS that is released for the ITS.
Note
The IIS 5.0 is integrated on the Windows 2000 Server.
2. In the folder C:\InetPub\wwwroot you have to create a new directory for each ITS instance.
24/84 PUBLIC 11/29/2006

3 Preparation
Recommendation
We recommend that you name the new directory according to the SAP system name you want to
connect to, for example C:\InetPub\wwwroot\P30.
3. Perform the following actions:

a) Choose Start Programs Administrative Tools Internet Services Manager .
The Internet Information Services dialog box is displayed.
b) Select your host.
c) Choose Action New Web Site .
The Web Site Creation Wizards starts.
d) Choose Next.
Enter a description in the Web Site Description field and choose Next.
Recommendation
We recommend that you name the new Web Site according to the SAP system name you
want to connect to.
e) Choose Next. Enter an unused port (for example, 81 or 82) in the TCP Port this Web Site should
use (Default: 80) field.
f) Choose Next. Choose a directory in the Enter the path for your home directory field (see step 2 above).
g) Choose Next. Define your Web Site Access Permissions.
h) Choose Next and then Finish.
i) Repeat the steps above for all further needed IIS instances.
Enterprise Server Instances
1. Make sure to use a version of Netscape Enterprise Server that is released for the ITS.
2. Choose Start Programs Netscape SuiteSpot Administration .
3. Choose Create New Enterprise Server and configure the parameters:
a) Server Port:
Set this value to an unused port (for example, 81 or 82).
b) Server Identifier:
Set this value to <Hostname>adm.
4. Repeat the steps above for all necessary Web server instances.
IPlanet/Sun One Web Server Instances
1. Make sure to use a version of iPlanet Web Server that is released for the ITS.
2. Choose Start Programs iPlanet Web Server Administer Web Server .
3. Choose Create New Enterprise Server and configure the parameters:
a) Server Port:
Set this value to an unused port (for example, 81 or 82).
11/29/2006 PUBLIC 25/84

3 Preparation
b) Server Identifier:
Set this value to <Hostname>adm.
Apache HTTP Server Instances
1. Make sure to use a version of Apache HTTP Server that is released for the ITS.
Note
On a Windows 2000 Web Host you can install Apache via binary win-32 install shield with option
Typical. This includes the Dynamic Shared Objects functionality (DSO) that is needed as WGate is
built as a loadable module requiring the Apache DSO functionality.
For more information about the DSO strategy, see http://www.apache.org/docs/dso.html.
2. You can now install Apache as Windows service by typing the following command:
apache -i -n <service name>
3. If you want to install more than one WGate instance, you have to edit the file httpd.conf: in the
following way:
a) Section Listen:
Add the ports on which the WGate instances should listen, for example:
#Listen example: Allows you to bind Apache to specific IP addresses and/or# ports, in addition
to the default. See also the <VirtualHost> directive.
Listen 81
Listen 82
b) Section Virtual Host:
Add virtual hosts for each of your WGate instances and define at least one separate
DocumentRoot, for example:
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
#
<VirtualHost hostname.domain:81>
# ServerAdmin webmaster@dummy-host.example.com
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocsAT3"
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
</VirtualHost>
<VirtualHost hostname.domain:82>
26/84 PUBLIC 11/29/2006

3 Preparation
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocsCSR"

</VirtualHost>
c) Creating separate Section Document Roots.
You have to create manually the Document Root as specified in the virtual host sections
above, for example:
htdocsAT3 and htdocsCSR
d) Repeat the steps above for all necessary Web server instances.
Configuring Released Web Servers for Linux

Apache HTTP Server Instances
1. Make sure to use a version of Apache HTTP Server that is released for the ITS.
2. If you want to install more than one WGate instance you have to edit the file httpd.conf: in the
following way:
a) Section Listen
Add the ports on which the WGate instances should listen, for example:
#Listen example: Allows you to bind Apache to specific IP addresses and/or ports, in addition to
the default. See also the <VirtualHost> directive.
Listen 80
b) Section Virtual Host:
Add virtual hosts for each of your WGate instances and define at least one separate
DocumentRoot, for example:
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
#
<NameVirtualHost 10.xx.yy.zz>
<VirtualHost hostnameAIO.domain:80>
DocumentRoot /usr/local.orig/httpd/htdocsAIO
</VirtualHost>
<VirtualHost hostnameCSR.domain:80>
11/29/2006 PUBLIC 27/84

3 Preparation
3.3 Preparing the System for SAPinst
DocumentRoot /usr/local.orig/httpd/htdocsCSR
</VirtualHost>
c) Creating separate Section Document Roots.
You have to create manually the Document Root as specified in the virtual host sections
above, for example:
htdocsAIO and htdocsCSR
Result
You have installed the necessary Web server instances.
Now you can start the ITS installation.
Prerequisites
You can find the JRE versions that are released for a SAP system in the SAP Service Marketplace at:
https://service.sap.com/pam SAP NetWeaver 2004s JSE Platforms .
Note
JRE is not part of the SAP shipment.
Note
n Make sure that your JAVA_HOME environment variable is set to <JAVA_HOME>.

n Make sure that $JAVA_HOME/bin (Linux) respectively %JAVA_HOME%\bin (Windows) is included
in your system path.
n On Windows, you have to reboot your system after setting the system environment variable.
This section describes preparations for a local installation with SAPinst. However, you can perform
a remote installation [page 79] using a standalone SAPinst GUI on a separate Windows or Linux host.
This enables you to perform the installation on a remote host while monitoring it with SAPinst
GUI from a local host.
To avoid an error when starting SAPinst GUI, you must make sure that there are no .jar files from an
XML parser tool, such as Xerces or Xalan, in the JDK ext directory, as described in the procedure below.
28/84 PUBLIC 11/29/2006

3 Preparation
Procedure
To check the JDK ext directory, proceed as follows:
1. Log on to the host on which you intend to run the SAPinst GUI.
2. Check whether there are already <parser_name>.jar files, for example, xerces.jar in your ext
directory.
The default path is:
n Windows: <JAVA_HOME>\JRE\lib\ext
n Linux: <JAVA_HOME>/JRE/lib/ext
3. If you find any .jar files, rename them to, for example, xerces.xxx.
Caution
Do not forget to rename the files back to their original names after the installation procedure is
complete.
11/29/2006 PUBLIC 29/84

4 Installation Procedure
4.1 Installation on Windows
Note
For more information on SAPinst GUI, see Using SAPinst GUI [page 78].
Installation Process — Single Host Installation
1. Run SAPinst on Windows [page 31].

2. Install an ITS instance on Windows [page 33].
3. Install additional ITS Instances on Windows [page 35].
4. Check the installation [page 44].
Installation Process — Dual Host Installation
1. Make sure that both computers are on the LAN and can ping each other.
To test this, log on to the Web host and enter the command ping <AGate host> from the
command prompt. Use the equivalent ping command on the AGate host.
2. Install the AGate first. That means, on your AGate host
a) Run SAPinst on Windows [page 31].
b) Install an ITS Instance on Windows [page 33].
3. Install the WGate. That means, on your WGate host,
a) Run SAPinst on Windows [page 31].
b) Install an ITS Instance on Windows [page 33].
4.1.1 Running SAPinst on Windows
This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUI
and a GUI server, which both use Java.
This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running
on the same host. If required, you can instead perform a remote installation with SAPinst [page 79], where
SAPinst GUI is running on a separate host from SAPinst and the GUI server.
Note the following about SAPinst:
11/29/2006 PUBLIC 31/84

n When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a
secure SSL connection to the GUI server and the GUI server connects to SAPinst.
n SAPinst normally creates the installation directory sapinst_instdir where it keeps its log
files, and which is located directly below the Program Files directory. If SAPinst is not able to
create sapinst_instdir directly below the Program Files directory, SAPinst tries to create
sapinst_instdir in the directory defined by the environment variable TEMP.
n SAPinst creates a subdirectory for each installation service, called
<sapinst_instdir>\<installation_service> which is located below
%ProgramFiles%\sapinst_instdir.
n The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or
SystemRoot). These executables are deleted after SAPinst has stopped running.
Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary
directory. You can safely delete them.
In the temporary directory you can also find the SAPinst Self-Extractor log file dev_selfex.out,
which might be useful if an error occurs.
Caution
If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.
n If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:
l Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit.
l Click the icon for the SAPinst output window located in the Windows tray and choose File
Exit .
Prerequisites
n You are logged on as user with the required rights and privileges that authorize you to install
the SAPinst tool and the SAP system.
n Each SAP instance requires a separate installation directory.
Recommendation
We recommend that you keep all installation directories until the system is completely and
correctly installed.
Procedure
1. Insert the SAP Server Components CD in your DVD drive or mount it locally.
2. Start SAPinst from the SAP Server Components CD (from now on called <Installation_CD>) by
double-clicking sapinst.exe from the following path:
<DVD drive>:\SERV1\ITS\NT\I386\
32/84 PUBLIC 11/29/2006

Note
n During the installation, the default ports 21200 and 21212 are used for communication between
SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error
message if one of these ports is already in use by another service.
In this case, open a command prompt and change to the required directory as follows:
<DVD drive>:\SERV1\ITS\NT\I386\.
Enter the following command in a single line:
sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>
GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>
n For a list of all available SAPinst properties, enter the following command:
sapinst —p.
3. If SAPinst prompts you to log off from your system, log off and log on again. SAPinst restarts
automatically.
4. Follow the instructions in the SAPinst dialogs and enter the required parameters.
Note
For more information about the input parameters, position the cursor in the field of the
respective parameter and press F1 .
After you have entered all required input information, SAPinst starts the installation and displays
the progress of the installation. If the installation was successful, the screen Finished installation
successfully is displayed.
5. We recommend that you delete all files in the directory %userprofile%\.sdtgui\.
4.1.2 Installing an ITS instance on Windows
If you install an ITS instance with SAPinst for the very first time on a host, you have to start SAPinst
once from the <Installation_CD>.
Afterwards, you can use the Start Menu to install your ITS instance(s): Installing additional ITS instances on
Windows [page 35].
Prerequisites
If you start SAPinst GUI on your host, your JAVA_HOME environment variable must be set correctly.
If you want to perform a remote installation, that is, SAPinst GUI is started on another host to
monitor the installation, you do not need to set the JAVA_HOME environment variable on your instance
host. For more information on remote installation, see Starting SAPinst on the Remote Host [page 80].
11/29/2006 PUBLIC 33/84

Procedure
1. Run SAPinst [page 31] and follow the screens.
Depending on the situation, you will first see one of the following screens:
n If you install the ITS for the first time on this host, the following two windows are displayed
(otherwise SAPinst omits the dialogs):
l Accepting Conditions
You must accept the conditions.
l Defining SAP ITS Installation Directory
Enter your SAP ITS installation directory (<ITS_InstDir>).
n If you have already installed the same ITS version or a lower one on this host, the following
screen appears, asking you whether to install only another instance or to upgrade the whole
ITS (otherwise SAPinst omit this dialog):
l Checking ITS Version
If you choose to refresh the ITS, SAPinst will upgrade the ITS (if a lower release or patch level
is installed) or refresh the installed version (suitable if the already installed version is corrupt)
without touching already installed ITS instances. SAPinst then finishes after installing the
up-to-date kernel. To install new instances, you have to choose Upgrade to the new version.
If you choose to install another instance, SAPinst creates an additional instance on this host,
keeping the already installed ITS release.
n If you have already installed a higher ITS version on this host, the following screen appears,
asking you whether to install only another instance or to downgrade the ITS from the current
SAPinst:
Downgrading an ITS version may be suitable if you have installed a more recent ITS, for
testing or development purposes, and need to go back to the version of your productive ITS.
If you choose to install another instance, SAPinst creates an additional instance on this host
based on the already installed ITS release.
2. Follow the instructions in the SAPinst dialogs.
If you have entered all required information during the input phase, SAPinst starts the installation
and displays installation progress during the processing phase.
Result
A successful ITS instance installation creates the following Windows services:
Service Name Description
SAP ITS Manager - <name of virtual instance> ITS service for this specific virtual instance installation,
if selected
SAP ITS Manager ‒ ADM ITS Administration, if selected
34/84 PUBLIC 11/29/2006

Service Name Description

ITS Watchdog ITS Monitoring tool, if selected during the ITS
Administration installation.
SAP IACOR Manager Automatically installed with the ITS.
4.1.3 Installing additional ITS Instances on Windows
Prerequisites
n If you install an ITS instance with SAPinst for the very first time on a host, you have to start SAPinst
from the <Installation_CD>: Run SAPinst on Windows [page 31].
n If you want to install an ITS instance whereas another instance installation on this host was not
completed successfully (and you want to continue the installation later), you must run SAPinst
again from the <Installation_CD> to create a new installation directory for the SAPinst log and
command files: Run SAPinst on Windows [page 31].
n If you want to perform a remote installation, see Remote Installation with SAPinst [page 79].
n You are logged on as ITS Administrator.
n All other programs are closed.
n For every additional ITS instance you want to install on a host (after the successful installation of
another instance), proceed as described below.
Procedure
1. To start the installation run SAPinst [page 31] .
Note
SAPinst uses the ports 21212 and 21213 during the installation for communication with SAPinst
GUI. You get an error message if one of these ports is already in use. In this case, you must do
the following:
a) Open a command prompt.
b) Change to your <SAPinst_INSTDIR> and run:
.\sapinst.exe SAPINST_DIALOG_PORT=<port>
where <port> is an unused port on your host.
SAPinst GUI now starts and the Welcome screen is displayed.

2. Select ITS Installation on Windows and choose Next.
3. The next steps are the same as described in Installing an ITS Instance on Windows [page 33], beginning
with step 5.
11/29/2006 PUBLIC 35/84

4.2 Installation on Linux
Note
For more information on SAPinst GUI, see Using SAPinst GUI [page 78].
Installation Process — Single Host Installation
1. Run SAPinst on Linux [page 36].

2. Install an ITS Instance on Linux [page 38].
3. Start and stop an ITS Instance on Linux [page 39].
Installation Process — Dual Host Installation
1. Make sure that both computers are on the LAN and can ping each other.
To test this, log on to the Web host and enter the command ping <AGate host> from the
command prompt. Use the equivalent ping command on the AGate host.
2. Run SAPinst on Linux [page 36].
3. Install the WGate. That means, on your WGate host,
n Install an ITS Instance on Linux [page 38].
4.2.1 Running SAPinst on Linux
This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUI
and a GUI server, which both use Java.
This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running
on the same host. If required, you can instead perform a remote installation with SAPinst [page 79], where
SAPinst GUI is running on a separate host from SAPinst and the GUI server.
When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secure
SSL connection to the GUI server and the GUI server connects to SAPinst.
Procedure
1. Log on to your host as user root.
Caution
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. Start SAPinst from the SAP Server Components CD (from now on called <Installation_CD>) in one of
the following ways:
36/84 PUBLIC 11/29/2006

n Using the default installation directory (recommended)

Enter the following commands:
cd <Installation_CD>/SERV1/ITS/UNIX/LINUX_32
./sapinst
Caution
Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.
n Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.
Note
n During the installation, the default ports 21200 and 21212 are used for communication between
SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error
message if one of these ports is already in use by another service.
In this case, you must execute sapinst using the parameter
SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>
GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> .
n For a list of all available SAPinst properties, enter the following command:
sapinst —p.
3. If SAPinst prompts you to log off from your system, log off and log on again. SAPinst restarts
automatically.
4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
Note
To find more information on each parameter during the input phase of the installation, position
the cursor on the field of the respective parameter and press F1 .
After you have entered all required input parameters, SAPinst starts the installation and displays
the progress of the installation.
When the installation has successfully completed, the screen Finished successfully is displayed.
5. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.
11/29/2006 PUBLIC 37/84

Note
If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log file
dev_selfex.out in the temporary directory.
Recommendation
We recommend that you keep all installation directories until you are sure that the system is
completely and correctly installed.
6. We recommend that you delete all files in the directory <user_home>/.sdtgui/.
4.2.2 Installing an ITS Instance on Linux
Prerequisites
n If you start SAPinst GUI on your host, your DISPLAY and JAVA_HOME environment variables must
be set correctly.
n This section describes a local installation. For more information on remote installation, see Starting
SAPinst on the Remote Host [page 80].
Procedure
1. Run SAPinst [page 36] and follow the screens.
Depending on the situation, you will first see one of the following screens:
n If you install the ITS for the first time on this host, the following two windows are displayed
(otherwise SAPinst omits the dialogs):
l Accepting Conditions
You must accept the conditions.
l Defining SAP ITS Installation Directory
Enter your SAP ITS installation directory (<ITS_InstDir>).
n If you have already installed the same ITS version or a lower one on this host, the following
screen appears, asking you whether to install only another instance or to upgrade the whole
ITS (otherwise SAPinst omit this dialog):
If you choose to refresh the ITS, SAPinst will upgrade the ITS (if a lower release or patch level
is installed) or refresh the installed version (suitable if the already installed version is corrupt)
without touching already installed ITS instances. SAPinst then finishes after installing the
up-to-date kernel. To install new instances, you have to choose Upgrade to the new version.
If you choose to install another instance, SAPinst creates an additional instance on this host,
keeping the already installed ITS release.
38/84 PUBLIC 11/29/2006

n If you have already installed a higher ITS version on this host, the following screen appears,
asking you whether to install only another instance or to downgrade the ITS from the current
SAPinst:
Downgrading an ITS version may be suitable if you have installed a more recent ITS, for
testing or development purposes, and need to go back to the version of your productive ITS.
If you choose to install another instance, SAPinst creates an additional instance on this host
based on the already installed ITS release.
2. Follow the instructions in the SAPinst dialogs.
If you have entered all required information during the input phase, SAPinst starts the installation
and displays installation progress during the processing phase.
4.2.3 Starting and stopping an ITS Instance on Linux
Starting the Instances

You can start the instances manually after the installation:
n If you want to start an ITS virtual instance (<VITS>), enter the following command:
<ITS_InstDir>/bin/its<VITS>.sh start
Example
l Starting the IACOR: itsIACOR.sh start
l Starting the instance: IT1: itsIT1.sh start
n If you want to start a WGate instance:

1. Set the LD_LIBRARY_PATH environment variable to the ITS programs directory.
Shell Command
bash or ksh export
LD_LIBRARY_PATH=<ITS_InstDir>/programs
csh setenv
LD_LIBRARY_PATH=<ITS_InstDir>/programs
2. Enter the following command:

<apache_serverroot>/bin/apachectl start&
Note
With SuSE Linux use the command rcapache.
Stopping the Instances

To stop an instance, enter the following command:
11/29/2006 PUBLIC 39/84

4.3 Patch Installation
<ITS_InstDir>/bin/its<VITS> stop
Example
n Stopping the IACOR: itsIACOR.sh stop

n Stopping the instance IT1: itsIT1.sh stop
n WGate instance: <apache_serverroot>/bin/apachectl stop&
Automating the Start

You can also automate the ITS instances start during reboot of the ITS host by using the runlevel
directory (/etc/rc3.d or /etc/rc5.d, for example).
4.3 Patch Installation
Instead of installing the ITS from the installation CD, you can also install the ITS by executing a patch.
Procedure
1. Download the installation patch from https://service.sap.com/patches SAP ITS SAP
ITS 6.20
2. Doubleclick on the package.
The installation starts automatically.
Note
If the installation does not start automatically, proceed as follows:
n Windows:
You download the package to the directory <extract_dir>.
To start the installation, doubleclick the file sapinst.exe in the directory
<extract_dir>\ITS_CD\ITS\NT\I386\.
n Linux:
You download the SAR archive and unpack it to the directory <extract_dir>.
To start the installation, run the file sapinst in the directory
<extract_dir>\ITS_CD\ITS\UNIX\LINUX_32\.
4.4 Compilation 4 / Patch Level 4: Script-Based Installation
With patch level 4 you can now install several ITS instances in a row on the same host by using
an ini file that is created by SAPinst.
40/84 PUBLIC 11/29/2006

4.4 Compilation 4 / Patch Level 4: Script-Based Installation
Caution
Exception (Windows only):
Do not activate the Watchdog installation. This installation service does not work here.
Procedure
If you want to use this script-based installation, proceed as follows:
1. Download patch level 4 from https://service.sap.com/patches SAP ITS SAP ITS 6.20 .
2. After extracting the exe file, run the installation.
Note
For further information, see
n Installing an ITS instance on Windows [page 35]
n Installing an ITS instance on Linux [page 39]
n Windows:
Run <drive>:\ITS\NT\I386\setup.cmd.
n Linux:
Run <mount_point>/ITS/UNIX/LINUX_32/INSTALL.
After SAPinst is installed, the ITS installation starts automatically.
3. Cancel the ITS installation exactly at the point, where the Welcome screen offers the ITS installation.
4. Start the installation from command line as follows (one line!):
sapinst SAPINST_SMART_COMPONENT=ITS_BATCH_PROCESSING
SAPINST_SMART_CONFIGFILE=ITS_PARAMETER.ini
SAPinst now starts again and creates the file ITS_PARAMETER.ini after you have confirmed the
license agreement.
5. Cancel the installation again and maintain the file ITS_PARAMETER.ini (see documentation in file
ITS_PARAMETER.ini).
6. After maintaining the ini file, start SAPinst as follows (one line!):
sapinst SAPINST_SMART_COMPONENT=ITS_BATCH_PROCESSING
SAPINST_SMART_CONFIGFILE=ITS_PARAMETER.ini SAPINST_SKIP_DIALOGS=true
SAPinst now installs the ITS instances as configured in the file ITS_PARAMETER.ini.
11/29/2006 PUBLIC 41/84

5 Post-Installation Steps
After the installation has successfully finished, you need to perform the following post-installation
steps.
1. Start an ITS Service from a Web Browser [page 43].
2. Check the ITS Installation [page 44].
IAC Publishing with IACOR

If you have connected an ITS instance to an SAP system ≥ 6.10, you must use the IACOR to publish the
IACs (You can publish IACs from SAP systems as of Release 4.6C):
1. Start IAC Publishing with IACOR [page 47].
2. Manage the IACOR [page 47] (optional).
3. Publish the IACs [page 50] from the SAP system.
ITS Watchdog (Windows only)
1. Configure Watchdog for Load Balancing Service [page 51].

2. Register ITS in an LDAP Directory [page 53].
3. Monitor WGate hosts with Watchdog [page 55].
5.1 Starting an ITS Service from a Web Browser
Prerequisites
When you have installed the Internet Transaction Server (ITS) and checked the installation, you can
start a service directly from a Web browser by entering the relevant URL.
Procedure
To start an ITS service from a Web browser, enter a URL with the following syntax:
<protocol>://<server>:<port>/<scriptpath>/<service>/!
Summary of the URL elements
URL Element Description Example Value(s)

<protocol> Communication protocol http or https
<server> Web server name or IP address MyWebServer
11/29/2006 PUBLIC 43/84

5.2 Checking the ITS Installation
URL Element Description Example Value(s)

<port> Port number on which your Web 81
server is listening The default value is 80.
<service> Name of ITS service to be started webgui
<scriptpath> Pattern used by the Web Server The default value is scripts/wgate
to recognize a request directed to
the ITS. Can be defined in WGate
configuration
! Final element !
This is an integral part of the URL
and must be included
Example
http://MyWebServer1/scripts/wgate/webgui/!
This URL calls the service webgui (SAP GUI for HTML) via the protocol http, using a Web server called
MyWebServer1 that is supported by Microsoft IIS, Netscape NES or Apache and listens on port 80.
In this example, the port number is omitted, because 80 is the default value.
Prerequisites
You have performed either a single host installation or a dual host installation.
When you have completed the ITS installation, you should do the following:
n Check that the installation was successful.
n Ensure that the SAP system is available.
n Verify that the ITS connection between the Web browser and the SAP system.
Was the installation successful?

To check whether the installation ran successfully, log on to the host(s) that contains the ITS
components (WGate and AGate) and follow the procedures in the tables below according to the
installation type.
44/84 PUBLIC 11/29/2006

Check Procedure
On the Web host, check the Web server status. Windows 2000/2003 Server
1. Choose Start Programs Administrative Tools
Computer Management .
2. Choose Services and Applications.
3. Choose Services.
4. Find the Web server in the list of Services and
check that the values in the Status and Startup Type
columns are set to Started and Automatic.
On the Web host, check that the WGate component is Windows 2000/2003 Server
present. The location depends on the Web server you are
using:
n • If you are using the Microsoft Internet
Information Server (IIS), you can find WGate.dll
in <ITS_InstDir>\programs.
n • If you are using the Netscape Enterprise Server
(NES) or the iPlanet Web Server, you can find
Wgate<xx>.dll in <ITS_InstDir>\programs.
n • If you are using the Apache HTTP Server, you can
find apwgate13<xx>.dll or apwgate20<xx>.dll in
<ITS_InstDir>\programs
To see .DLLs files, make sure that your Windows
Explorer displays all file types.
UNIX Server
n • If you are using the Apache HTTP Server, you
can find apwgate13<xx>.so or apwgate20<xx>.so
in <Apache installation directory>\modules.
Both Operating Systems
n Check if the file wgate.conf exists under
l Apache: <WebServer_InstDir>/conf
l IPlanet and Netscape Enterprise Web Server:
<WebServer_InstDir>/config
l Internet Information Server:
<WebServer_InstDir>/programs
l Internet Information Server:<ITS_InstDir
>/programs
n • Check if the following files exist under
<ITS_InstDir>/config:
l ItsRegistryWgate.xml
l ItsRegistry<ITS_instance_name>.xml
On the AGate host, check that the ITS Manager is Windows 2000/2003 Server
started and that startup is set to automatic. 1. Choose Start Programs Administrative Tools
Computer Management .
2. Choose Services and Applications.
3. Choose Services.
4. Find the SAP ITS Manager in the list of Services
and check that the values in the Status and Startup
11/29/2006 PUBLIC 45/84

Check Procedure
Type columns are set to Started and Automatic. The
SAP ITS Manager is listed as SAP ITS Manager -
<instance>..
Windows and UNIX
Check if the following file exist under
<ITS_InstDir>/config:
n ItsRegistry<ITS_instance_name>.xml
Is the SAP system available?

If you have the SAP GUI for Windows or SAP GUI for Java and you have installed an IAC package that
corresponds to a release of the SAP system, you can check that the SAP system is available by starting a
transaction referenced by one of the installed Internet Application Components:
1. Make sure that you have SAP system Release 3.1I or higher installed and operating.
2. Look for a service file <service>.srvc that contains the entry ~transaction <transaction>
where <transaction> is the name of a transaction in the SAP system.
Unless you specified a different path during the installation, you can find the services under:
<ITS_InstDir>\<ITS instance>\services
Note
If you have connected the ITS to a SAP system of Basis Release ≥ 6.10 keep in mind that you must
publish the services via IACOR to the ITS host [page 47].
3. Log on to the SAP system via the SAP GUI and start the transaction <transaction>.
n To log on to the SAP system, you use a standard dialog user.
n To start the transaction, use the value specified in the ~transaction parameter of the
service-specific service file
Does the ITS connection work?

To test the ITS connection, start the ITS service its_ping from a Web browser
1. Start a Web browser.
2. Enter the relevant URL:
The syntax for starting the its_ping from a Web browser via a URL is:
<protocol>://<server>:<port>/<scriptpath>/its_ping/!
For full details about what values to enter for these URL elements, see Starting an ITS Service from a
Web Browser [page 43].
Unless you have set up a global user by defining values in the global service file, or all the required
information is available in the service-specific service file, you see a logon screen for the service
<service>.
46/84 PUBLIC 11/29/2006

5.3 IAC Publishing with IACOR
For information about troubleshooting the ITS installation, see the ITS Tuning and Troubleshooting Guide at
help.sap.com/NW04 SAP NetWeaver Application Platform UI Technology ITS / SAP@Web Studio
SAP ITS Standalone .

This process describes how to configure the IAC Object Receiver (IACOR) and to publish the IACs.
To publish files from a SAP system, you have to register each IACOR connection as an RFC
destination. Also, the automatic registration of IACOR as an SAP RFC destination requires you
to log on to the source SAP system.
Prerequisites
n You have installed the ITS, because the IACOR files are automatically installed at the same time as
the Internet Transaction Server (ITS).
n You have installed the ITS Administration instance.
The ITS setup procedure for an administration instance includes installation of the ADM instance,
which is required by ITS to drive the ITS Administration tool. ADM contains the service admin for
managing ITS instances hosted on local and remote machines.
To do this, open your Web browser and start the ITS Administration tool with the following URL:
<protocol>://<server>:<port>/<scriptpath>/<service>/!
Example
If you have a Web server called MyWebServer1 on port 80 and you want to manage
instances hosted on remote and local machines, you have to enter the following URL:
http://MyWebServer1:80/scripts/wgate/admin/!
5.3.1 Managing IACOR
Use this procedure to

n start/stop IACOR
n see the status of the IACOR service and the status of each IACOR connection
n see IACOR traces
n modify registry settings of IACOR
n add, modify and delete IACOR connections
1. Log on with the administrator's account into the ITS Administration tool.
2. Choose IACOR from the tree structure on the left.
A sub-structure opens that contains the following nodes:
11/29/2006 PUBLIC 47/84

n Overview
n Registry
n Traces
n Logs
Start and stop IACOR

1. Choose Overview.
2. To start IACOR, choose Start.
The screen refreshes and in the line IACOR the green traffic light is enabled while the red one is
disabled. The Stop and Restart buttons have replaced the Start button.
3. To stop IACOR, choose Stop.
The green traffic light in the line for IACOR is now disabled whereas the red traffic light is enabled.
A Start button has replaced the Stop and Restart buttons.
If the status of the connection has not been refreshed, choose Refresh.
See the status of the IACOR service and the status of each IACOR
connection
1. Choose Overview.
2. For the status of the IACOR service, see the Current Status Iacor- Service column in the Iacor Service pane.
3. For the status of the IACOR connection, see the Status column in the Iacor Connections pane.
Display traces
Choose Traces.
All trace files are listed in the right frame. You can display a trace file by choosing its name.
Modify registry
1. Choose Registry.
The IACOR specific part of the ITS registry displays in the right frame.
2. Choose a value.
A new page is displayed in the right frame that contains the old value and an input field for the
new value.
3. Enter the new value in the New Value field and choose Save.
Add a new site connection

1. Choose Overview.
2. Under Add new IACOR Connection, choose Add.
A new screen is loaded, where you can enter the connection data.
3. Select your ITS instance from the combo box.
48/84 PUBLIC 11/29/2006

Usually this is the name of virtual ITS instance to which ITS files should be published. The next
fields will be filled automatically after selecting the ITS instance. Check and modify these entries if
required.
Note
If you want the gateway host and the gateway service to be determined automatically when
registering the connection with a SAP system, leave the default <auto>.
4. Enter all required information for the SAP system server.
Note
You can specify a single application server (optional with a SAP Router String) or use load
balancing. For information about the SAP system server, look in the SAP Logon of the
corresponding host:
n The Group is the name in square brackets after the SAP system name.
n You can find details such as System Number and SAP Router String by right-clicking on the SAP
system name and choosing Properties.
n For load balancing, you can define a Message Server or a SAP Router String. You can find the
message server by clicking on the SAP system, choosing Groups and entering the SAP system
name in field System ID. In R/3 Default User, specify the SAP system logon information.
Note
You must enter the data of a user that has authorization to create RFC destinations in the
relevant SAP system.
5. Choose Save.
IACOR now configures an RFC connection on the SAP system.
The message Success - Connection(s) added. is displayed on the bottom of the page. If there are
problems, an error message is displayed.
Note
You can view the resulting RFC TCP/IP destinations in SAP transaction SM59 on the SAP system.
The program ID of these destinations has the following format:
IACOR_<IACOR host name>_<ITS instance>_ITS
IACOR_<IACOR host name>_<ITS instance>_WWW
Modify a site connection

1. Choose Overview.
2. Choose an ITS instance from the right frame under IACOR Connections.
11/29/2006 PUBLIC 49/84

A new page opens that displays all information about this connection. You can now change
ItsUrl and/or WebUrl.
Note
If you modify connection settings, keep in mind that these changes are made on the IACOR host
and not on the SAP system server.
3. Choose Save.
The Success - Connection(s) modified. message shows that the new entries are stored in the registry.
4. Depending on your changes you may restart IACOR to take effect.
Delete a site connection

1. Choose Overview.
2. In the right frame, under IACOR Connections, choose Delete.
A new page opens that displays all information about this connection.
3. Choose Delete.
The Success - Connection(s) deleted. message is shown and the connection is deleted from the ITS
registry and from the SAP system.
5.3.2 Publishing the IACs from a SAP system
Use this procedure to publish IACs from a new installed SAP system of Release ≥ 4.6C.
You can publish IACs from SAP systems as of Release 4.6C.
Do not use this procedure if you are upgrading to a SAP system of Release ≥ 6.10. In this case, refer to
topic Meeting the Requirements for the SAP Internet Solutions in the corresponding SAP system upgrade guide.
Prerequisites
You have started and configured the IACOR for the specific SAP system.
Procedure
1. Logon to the SAP system from which you want to publish the IAC.
2. Execute the report W3_PUBLISH_SERVICES (transaction SE38).
a) Leave the fields Transport Request and Package empty and choose Execute.
A new dialog box appears.
b) Choose Workbench Settings.
A new dialog box appears.
c) Choose the Internet Transaction Server tab.
d) Choose On Selected Site under the Publish tab.
e) Use the input help to select the site where you want to publish, and confirm.
50/84 PUBLIC 11/29/2006

5.4 Watchdog Configuration (Windows only)
If the selection menu is empty, the IACOR and its corresponding sites in the SAP system have
not yet been configured correctly.
f) Choose Enter .
g) Choose Select All or select a subset of services by using the checkboxes and then choose Publish.
The publishing process can take several minutes. A message appears when the publishing
process was successful.
h) If you have configured multiple sites where you want to publish, repeat steps b. to g.
Your selected IAC will now be published from the SAP system to your ITS instances of the specific site.
After successful publishing you can start an ITS Service from a Web Browser [page 43].
Note
A log box is displayed after the publishing procedure.
You can also watch the publishing progress in the IACOR trace files on the ITS host.
Prerequisites
You have installed the ITS Watchdog service on the ITS host (AGate and WGate).
5.4.1 Configuring Watchdog for WLBS
To achieve high availability and load balancing via Microsoft Windows Load Balancing Service(WLBS) you
have to:
1. Install WLBS on every WGate host.
2. Adapt the service its_ping.srvc.
3. Configure Watchdog in the Windows registry.
Installing WLBS
Note
The following procedure is just an example for a Windows 2000 System.
For full details, see your Windows 2000 documentation. You should also read the Microsoft
documentation Network Load Balancing Technical Overview.
1. Open the network properties dialog for the network adapter and enable Network Load Balancing.
2. Configure the Properties of Network Load Balancing.
11/29/2006 PUBLIC 51/84

Enter the new cluster IP address as Primary IP address and specify the Subnet mask. You may also need to
enable Multicast support and you may want to enable Remote control.
3. Enter the host's ordinary IP address as Dedicated IP address, specify the Subnet mask and assign a Priority
(Unique host ID).
You need to assign a different ID to every server in the cluster, for example starting with 1 for the
first server, 2 for the second server and so on.
4. 4. Create a Port Rule for every port used by the Web server. Specify the Port range and use Affinity Single.
5. Add the cluster IP address to the network adapter using the Advanced TCP/IP Settings.
Caution
Be very careful when specifying the port rule parameters. For example, the WLBS convergence
algorithm will not work if the port rules differ on the used cluster servers. WLBS will write
diagnostic messages to the NT system event log. In addition wlbs.exe offers a command line
interface. The most useful commands are:
n Wlbs enable <Port>
n Wlbs disable <Port>
n Wlbs query <Cluster IP address>
n Wlbs display
Now you can use the cluster IP address in your URLs to connect to ITS. In the example above you can
use http://155.56.93.4:80/scripts/WGate/webgui/!. WLBS automatically directs this URL to one
of the cluster servers and it will notice hardware or network failures.
Adapting the service its_ping.srvc

To test an URL, ITS Watchdog utilizes an ITS service called its_ping. An URL is considered to be
available if it can be loaded without any error and the returned page includes a certain search pattern
(see PageSize and PagePattern registry values).
The its_ping service is shipped with the following standard configuration (see its_ping.srvc
service file on each AGate host):
Service Standard configuration
~theme 99
~initialtemplate itsping
~xgateway sapxginet
To enable the its_ping service for The ITS Watchdog you need to adapt the default logon information
in every its_ping.srvc configuration file:
52/84 PUBLIC 11/29/2006

~client <client>
~login <your_user>
~password <your_password>
~language <language>
Recommendation
We recommend that you encrypt the password in this service file by using SAP@Web Studio or
ITSAdministration.
Configuring Watchdog in the Windows registry

See Registry Configuration [page 56].
5.4.2 Registering ITS in an LDAP Directory
To register ITS in a SAP Lightweight Directory Access Protocol (LDAP) environment you have to:
1. Adapt the service file ldapreg.srvc.
2. Enable Watchdog for LDAP registration in the Microsoft Windows registry [page 56].
3. Adapt the service its_ping.srvc.
4. Enable LDAP registration for the SAP system.
5. Install the latest SAP schema extension on the LDAP Server.
6. Update registration tool ldapreg.exe on the SAP system executable directory.
7. Transport the function module WWW_LDAP_REGISTER_ITS into the SAP system by applying a
Support Package.
Adapting the service file ldapreg.srvc

The ITS Watchdog will detect all installed ITS instances and register each instance using a new ITS
service ldapreg.
This service will use webrfc to call a function module in the connected SAP system, which will start the
external LDAP registration program ldapreg to register the instance.
You have to adapt the default parameter of ldapreg.srvc file on each AGate host:
~xgateway sapxgwfc
~client <your_client>
~login <your_user> (must have authorization to execute the

function module WWW_LDAP_REGISTER_ITS)
11/29/2006 PUBLIC 53/84

_FUNCTION WWW_LDAP_REGISTER_ITS
Adapting the service its_ping.srvc

To test an URL, an its_ping ITS service is required. A URL is considered to be available if it can be
loaded without any error and the returned page includes a certain search pattern (see PageSize and
PagePattern registry values).
The its_ping service is shipped with the following standard configuration (see its_ping.srvc service
file on each AGate host):
~theme 99
~initialtemplate itsping
~xgateway sapxginet
To enable the its_ping service for The ITS Watchdog you need to adapt the default logon information
in every its_ping.srvc configuration file:
~client <client>
~login <your_user>
Note
We recommend that you encrypt the password in this service file by using SAP@Web Studio or
ITSAdministration.
Installing the latest SAP schema extension on the LDAP Server

The 6.20 SAP schema extension already includes the necessary information for registering ITS.
If you want to register the ITS for SAP systems lower than 6.20 you have to perform activities as
described in SAP Note 379691.
For example, the following information about ITS will be stored in the directory:
54/84 PUBLIC 11/29/2006

SAP-R3-ITSInstance(cn=<ITSInstanceName>_<Hostname>)
Mandatory: String cn(I) ITS_pcintel8.nt5.sap-ag.de
String SAP-R3-SID(I) BIN

String SAP-R3-Host(I) pcintel8.nt5.sap-ag.de
String SAP-R3-OperatingSys- Windows 2000 5.0 2195 Service Pack 1

tem(I)
String SAP-R3-WebServer(I) iis
String (mul- SAP-R3-URLs(I) http://pcintel8.nt5.sap-ag.de:80/scripts/WGate

tivalued) https://pcintel8.nt5.sap-ag.de:443/scripts/WGate
String SAP-R3-ITSRelease(I) 46D patch 3000

Optional: String SAP-R3-Description
String (mul- SAP-R3-AdminURLs(I) http://pcintel8.nt5.sap-ag.de:81/scripts/WGate
tivalued) /adminremote/!
https://pcintel8.nt5.sap-ag.de:82/scripts/WGate
/adminremote/!
String SAP-R3-COMCLSID(I) {a02a29a8-f272-44e3-9d9c-c4df1e892f10}
More Information
For more information, see SAP Note 379691.
This note contains the most recent information how to enable the ITS LDAP registration for 46B/C/D
SAP systems. Make sure that you have the most recent version of this note.
5.4.3 Monitoring with Watchdog
You can use Watchdog also (beneath LDAP and WLBS functionality) as a simple monitoring tool
using a Web Browser. In addition, it displays information about WLBS, if configured (see Configuring
Watchdog for WLBS [page 51])
Prerequisites
This feature is only available using the Microsoft Internet Information Server as Web Server.
Procedure
You can monitor the ITS Watchdog status by using the URL
http://<wgatehost>:<port>/sap/watchdog/watchdog.asp.
Watchdog Heading Description

Instance ITS instance name
URL Basis URL of the instance
11/29/2006 PUBLIC 55/84

Watchdog Heading Description

Status: enabled, disabled enabled if URL and ITS instance are enabled, else
disabled
Availability: available, unavailable, available (not available if URL worked during the last test, else
checked), unavailable (not checked), not checked unavailable.
If the URL is not checked by the ITS Watchdog
(depending on MonitorLevel) its availability will be
reported as available (not checked) or unavailable
(not checked).
not checked URLs will be reported using the same
availability as the checked URLs of the ITS instance.
WLBS port rule: WLBS not installed, enabling failed, The value describes the last action performed by the
disabling failed, enabled, disabled, unchanged service with respect to the corresponding WLBS port
(if configured) rule.
unchanged: the port status information is considered
unreliable and therefore The ITS Watchdog has not
changed the port rule status.
enabling failed / disabling failed: execution of
the port enabling or disabling command (defined by
PortDisable and PortEnable; see Registry Configuration [page
56]) returned an exit code not equal to 1. This can be
caused by a WLBS failure or by a missing port rule for
the specific port.
The status unavailable or unavailable(not checked) is displayed as red row, all other status are displayed
using green rows.
5.4.4 Registry Configuration
Watchdog can be congured in the Microsoft Windows registry under

HKLM\System\CurrentControlSet\Service\ITS Watchdog\Parameters.
To activate registry changes, the ITS Watchdog service must be restarted.
The ITS Watchdog offers the following features:
n Changes to the WGate configuration file of an ITS instance are detected automatically without
requiring the service to be restarted.
n The service does not monitor disabled ITS instances or disabled URLs and it does not check the
ADM instance (see AdminInstance parameter).
n The service considers a port state as reliable if all related URLs have returned the same result
during at least the last two trials (see Latency parameter).
n The service only enables/disables a port rule for reliable ports.
56/84 PUBLIC 11/29/2006

Overview of the complete Watchdog registry setting
Registry Entry Purpose

WLBS Entries
When WLBSAutoDetect is disabled, watchdog does not search for an installed WLBS. When PortEnable and
PortDisable are changed, The ITS Watchdog uses different commands for controlling ports.
For example, by using a script file you can easily add additional functions (like sending an email to the
administrator) if an ITS failure is detected. By changing PortControl you can completely disable the periodic
availability check.
PortEnable (default wlbs enable #) Specifies the command to enable a port (# will be
replaced with the port number)
PortDisable (default wlbs disable #) Specifies the command to disable a port (# will be
replaced with the port number)
PortControl (default 1) Controls when ports are disabled or enabled:
n 0: Never
n 1: When the port information is reliable and the
status has changed
n 2: Every time the port information is reliable
WLBSAutoDetect (default 1) Enables / disables automatic detection of WLBS:
n 0: If PortControl is enabled, ports are enabled and
disabled even if no WLBS is available
n 1: Automatic detect WLBS. Only if WLBS is
available and PortControl is enabled, ports are
enabled and disabled
WLBS is considered to be available, if
n HKLM\SYSTEM\CurrentControlSet\Services\WLBS
is found in the registry
n HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Enum
\Count exists. Its value must be greater than 0.
If WLBSAutoDetect is enabled, the service will
automatically detect WLBS even if it is installed
after service startup (when a client calls the DCOM
ITSWatchog.GetInstanceList method see Additional
Information [page 58]). The service does not recognize
uninstallation of WLBS without restarting the service.
LDAP Entries
LDAPAutoRegister (default 0) Controls registration of the ITS instances in an LDAP
directory
n 0: do no register
n 1: register
General Watchdog Entries
AdminInstance (default ADM) Specifies the name of the Windows Service instance
that should not be monitored.
TimeInterval (default 60) Specifies the time period in secs for testing the URLs.
11/29/2006 PUBLIC 57/84

Registry Entry Purpose

Latency (default 2) Specifies the number of identical test results before a
URL status is considered as reliable.
PingService (default /its_ping/!) Specifies the ITS service used for testing the URLs.
PagePattern (default R/3 Status - OK) Specifies the string expected in the returned page.
PageSize. (default 8192) Specifies maximum length used when searching for
PagePattern.
MonitorLevel (default 1) Specifies which URLs are tested:

n 0: The first URL of each ITS instance
n 1: The first URL of each port of each ITS instance
n 2: All URLs of each ITS Instance
HttpTimeout (default 15000) Specifies the timeout in msecs for HTTP operations
during URL testing.
5.4.5 Watchdog: Additional Information
This topic describes

n The ITS Watchdog DCOM Interface (for development purposes)
n How to uninstall Watchdog
ITS Watchdog DCOM Interface

The ITS Watchdog provides an easy to use dual DCOM interface IITSWatchdog to access status
information and the WGate configuration.
Both monitoring tools (Active server page and R/3 MMC SnapIn) use this interface to access The
ITS Watchdog service.
n IITSWatchdog: GetInstanceList
Get a list of all monitored ITS instances and URLs
HRESULT GetInstanceList([out] VARIANT *instance,
[out] VARIANT *url,
[out] VARIANT *status,
[out] VARIANT *availability,
[out] VARIANT *wlbs_port_rule)
Return Values
S_OK
Each variant contains a safe array of BSTRs, all safe arrays are of the same length.
n IITSWatchdog: ReadWGateConfig
58/84 PUBLIC 11/29/2006

Read WGate configuration for a given ITS instance. The file content is returned in a single
string, lines end with \r\n.
HRESULT ReadWGateConfig([in] BSTR instance,
[out] BSTR *filename,
[out] BSTR *text)
Return Values
S_OK
n IITSWatchdog: WriteWGateConfig
Write WGate configuration for a given ITS instance. The file content is given by a single string,
lines ended with \r\n.
HRESULT WriteWGateConfig([in] BSTR instance,
[in] BSTR text)
Return Values
S_OK
ERROR_ACCESS_DENIED: Caller does not have write permission on the WGate configuration file.
Uninstalling Watchdog
Currently SAPinst never uninstalls the service.
If you need to uninstall it, run watchdog -u.
11/29/2006 PUBLIC 59/84

6 Additional Information
This section provides information on the following topics:

n SAP ITS-specific information [page 61]
l Installing additional IAC packages using the Package Manager
l Repeating an ITS installation unattended
l Applying patches to the ITS
n Uninstalling the ITS [page 63]
n SAP@Web Studio Installation [page 64]
n General information about ITS [page 68]
n General information about SAPinst [page 78]
Note
You should always perform instance maintenance and other administration tasks with ITS
Administration. To access this tool, you need to install an administration instance of the ITS.
When you have done this, you can start ITS Administration from your Web browser by entering
the URL http://<mymachine:myport>/scripts/wgate/admin/!
admin is the name of the ITS service that drives ITS Administration. For further information about
how to use ITS Administration to perform administration tasks after installation, see the ITS
Administration Guide at help.sap.com/NW04 SAP NetWeaver Application Platform UI Technology ITS /
SAP@Web Studio SAP ITS Standalone .
6.1 SAP ITS Specific Information
Installing Additional IACs

You can add additional IACs to an already existing AGate and/or WGate installation by using the
Package Manager. This requires using SAPinst again.
1. Log on to your ITS host as user <itsadm>.
2. Start SAPinst.
Note
For more information on how to start SAPinst, see Installing an ITS instance on Windows [page 35] or
Installing an ITS instance on Linux [page 39].
3. The window Checking ITS Version is displayed.
11/29/2006 PUBLIC 61/84

6.1 SAP ITS Specific Information
4. Select Apply additional packages.

The window Selecting IAC Packages is displayed.
5. Select the IAC package(s) you want to install and choose Next.
In case of a dual host installation, the selected packages for the AGate and WGate hosts must be
the same.
The window Selecting ITS Instances is displayed.
6. Select the ITS instance(s) to which the IAC(s) should be installed and choose Next.
The system now copies the IAC(s). This may take several minutes.
Repeating an ITS Installation Unattended

You can repeat your ITS installation and your ITS instance installation unattended. This means that
you install the ITS instance with exactly the settings as from the former installation. This may be
very useful in case of
n damaged / missing files or total loss of data in the physical ITS installation directory during
a system breakdown
n repeating an ITS installation on another host
Procedure
Note
Repeating an ITS installation requires the file keydb.xml from the SAPinst_Inst directory of an
already installed ITS instance. Therefore, if you intend to use this feature, we recommend that you
backup each keydb.xml for each ITS instance you want to repeat. You must have exactly the same
Web server configuration as before.
Proceed as follows:
1. Backup the file keydb.xml from an already installed ITS instance.
2. Edit the keydb.xmlas follows:
a) Search for the string table name="SAPINST_INST_STATUS.
b) Delete all <row> tags.
c) Save your settings.
3. On the host where you want to repeat the installation, do the following:
a) Start the installation as described in the installation guide.
b) Cancel the ITS installation at the point, where the Welcome screen offers the ITS installation.
c) Replace the file keydb.xml with your edited keydb.xml.
d) Run SAPinst from the command line from your SAPinst_Inst directory with the following
command:
sapinst
SAPinst now installs the ITS instance.
62/84 PUBLIC 11/29/2006

6.2 Uninstalling the ITS
Applying Patches for the ITS

You find the patches at https://service.sap.com/patches Entry by Application Group SAP Frontend
Components SAP ITS SAP ITS 6.20
Caution
The sapccmsr service has to be stopped before patching the ITS. Otherwise the installation will
be interrupted.
After copying and extracting the patch file on your ITS host, you have an complete <Installation DVD>
with SAPinst and new ITS patch. You start the patch installation like a normal installation from DVD,
except that you start SAPinst from your extracted <Installation DVD> from your local disk:
n Installing an ITS instance on Windows [page 35]
n Installing an ITS instance on Linux [page 39]
Note
If you want to update your SAP ITS 6.20 (from patch level 3 to patch level 4, for example), you need
to stop the Watchdog service before (if you have run any).
Otherwise, the installation stops with an error message similar to this one:
...ERROR 2003-08-13 07:36:13 MUT-03011 Running the
command "C:/SAPinst ITS 620/SAPCAR.exe '-x' '-v' '-g'
'-i' '-n' '-R' 'C:\Program Files\SAP\ITS\6.20\config\..'
'-f''C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ITS/ITS_SOFT/NT/I386/AGATE.SAR,' 'programs'"
finished with returncode 28. Output:...
6.2 Uninstalling the ITS
Uninstalling with SAPinst
Note
This procedure does not uninstall an IACOR.
1. Log on to your ITS host as user <itsadm>.

2. Start SAPinst.
Note
For more information on how to start SAPinst, see Installing an ITS instance on Windows [page 35] or
Installing an ITS instance on Linux [page 39].
3. The window Checking ITS Version is displayed.
11/29/2006 PUBLIC 63/84

6.3 SAP@Web Studio Installation
4. Select Delete ITS Installation.

5. On the next screen, select Delete complete ITS installation if you want to delete all instances, or
manually select the instances you want to delete.
Uninstalling Manually
To uninstall your ITS, perform the following steps:
1. If you are using the IACOR, stop the IACOR and delete all destinations in the relevant SAP system.
2. If you are using the WATCHDOG service, stop WATCHDOG.
3. Stop all ITS instances
4. On the AGate host, delete the SAP ITS installation directory <ITS_InstDir>.
5. On the WGate host delete the sap and designs subfolders in the Web server root directories.
6. On Windows, run regedit and delete the key SAP_REGISTRY_PATH under
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment.
Note
SAP@Web Studio installation tools must be used in accordance with the instructions given, and for
the purposes described, in this documentation. Improper use can damage existing files and systems.
Prerequisites
You have installed the ITS.
6.3.1 SAP@Web Studio — Overview
The SAP@Web Studio is a PC tool for developing applications that are driven by the SAP Internet
Transaction Server (ITS), access data in the SAP system and users can run from any Web browser.
If you want to give Internet and intranet users direct access to the SAP system by enabling them to
start applications based on the ITS infrastructure from a Web browser, you must install the ITS.
If you want to develop your own applications based on the ITS infrastructure outside the constraints
of the SAP system, you should also install the SAP@Web Studio.
Features
The SAP@Web Studio fully supports the development, testing and source-controlling of the files
that make up the services used by the ITS to drive applications.
When you have created and tested an application, you can publish the files to an ITS site and
source-control them by checking them into the R/3 Repository.
64/84 PUBLIC 11/29/2006

Integration
If you are using the SAP@Web Studio to develop ITS-driven applications you also need:
n ITS
To connect the SAP system to the Internet, test and publish applications, and allow users to run
them from a Web browser, you must install the ITS.
n SAP system
The ITS requires an SAP system, which is Release 3.1I or higher.
If you install the SAP GUI for HTML, your SAP system must be Release 4.0B or higher.
Constraints
The SAP@Web Studio runs on Windows 2000 servers.
6.3.2 SAP@Web Studio Installation Requirements
Before you install the SAP@Web Studio, you need to satisfy the hardware and software requirements,
so take the following steps:
1. Check the hardware requirements specified below.
2. Check the software requirements specified below.
Hardware Requirements
Processor Pentium PC compatible architecture
Backup (optional) Either over network or tape drive
Hard disk 30 MB free space
Memory (RAM) 64 MB
Software Requirements
Operating system Windows 2000
Virtual memory According to Microsoft guidelines
File system NTFS
Network TCP/IP Installed
11/29/2006 PUBLIC 65/84

6.3.3 Preparing the SAP@Web Studio Installation
1. Make sure that the TEMP directory is empty.

2. For security reasons, use the Windows NT File System (NTFS) to store ITS files.
NTFS fully supports Windows NT security and long file names.
To check that you are using NTFS:
a) Select the hard drive icon in the Windows NT Explorer.
b) Click the right mouse button.
c) Choose Properties.
d) Choose the General tab.
e) Check that the specified file system is NTFS.
3. Check that your version of Windows NT is 4.0 or later.
4. If there is no SAP GUI on the system where you have installed the SAP@Web Studio, you need to
copy a saplogon.ini file from a system where a SAP GUI is installed to connect to R/3 instances.
The saplogon.ini file normally resides in <drive:>\Winnt. If you are not using a SAProuter to
access your SAP system, add SAP ports manually to the services file, which you can find under:
<drive:>\Winnt\system32\drivers\etc\
5. Open the file and use your editor to add the following entries:
sapdp<systemnumber> 32<systemnumber>
sapgw<systemnumber> 33<systemnumber>
where <systemnumber> is the two-digit number identifying your R/3 instance.
If you want to connect to a message server as well, copy the appropriate message server port entry,
from the services file on the same machine that you got the saplogon.ini file from, to your local
services file. It has the form
sapms<systemid> <portnumber>
where <systemid> is the three-character long R/3 instance name (SID).
If you append these entries to the end of the services file, make sure that there is an additional line
at the end, that is, make sure that the sapgw<systemnumber> entry is not the last line.
6. Make sure that all other applications are closed.
6.3.4 Installing the SAP@Web Studio
1. Log on to the Windows server with local administrator authorizations.

2. Insert the server components package CD-ROM.
3. On the Windows desktop, choose Start Run .
4. Choose Browse and select the subdirectory studio\NT\i386 on the CD-ROM drive.
5. Double-click setupstu.exe and choose OK.
6. Choose Next.
7. Choose a destination directory or accept the default C:\Program Files\SAP\Studio.
66/84 PUBLIC 11/29/2006

8. Choose Next.
9. Choose Finish to complete setup.
If the setup program states that your computer needs to be restarted, choose OK.
6.3.5 Post-Installation for SAP@Web Studio
Setting up the SAP@Web Studio Environment

When you have installed the SAP@Web Studio, you can start it from the desktop and set up your
environment.
In particular, you need to:
n set up the connections to your SAP systems
n define an ITS site, which is the server location of all the ITS files required to start a service
Note
This documentation briefly describes the main steps you need to take.
For full details, see the SAP@Web Studio documentation:
l In the SAP@Web Studio, choose Help Studio Documentation .
l In the SAP System, choose Help SAP Library SAP Web Application Server Frontend Services
(BC-FES) ITS / SAP@Web Studio (BC-FES-ITS) SAP@Web Studio .
Starting the SAP@Web Studio

To start the SAP@Web Studio from the Windows desktop after installation, choose Start Programs
SAP@Web Studio Studio 6.20 .
Setting up the Environment

The procedures in the following table briefly describe how to connect to the SAP system and define an
ITS site in the SAP@Web Studio. For full details, see the SAP@Web Studio documentation:
Function Procedure
Connect to the SAP system 1. Choose Tools Repository Connect to R/3 .
You see the Select R/3 System dialog box, which
contains a list of all SAP systems currently
maintained in the SAP Logon application.
2. Select an SAP system and choose Logon.
Define an ITS site 1. Choose Project Site Definition .
You see the Site Definitions dialog box.
2. Choose Add.
3. Choose Add Site.
4. Follow the instructions in the Site Definition Wizard.
11/29/2006 PUBLIC 67/84

6.4 General Information about ITS

The Internet Transaction Server (ITS) extends the client/server architecture of the SAP system to
the Internet.
Figure 4:
The ITS is a gateway between one or more Web servers and one or more SAP application servers.
Typically, the Web server is an HTTP server, but other protocols such as FTP or Gopher may also be
supported.
All requests and responses that pass between a Web browser client and an SAP server are managed by
the ITS, which consists of 2 main gateway components:
n Web server gateway (WGate)
n Application server gateway (AGate)
WGate
WGate links the ITS to the Web server.
WGate receives requests from the Web browser via the Web server and forwards them to AGate via
a TCP/IP connection.
WGate always resides on the same machine as the Web server.
WGate is a Web server extension that shields AGate from differences in the various Web server APIs
used. WGate supports the following Web servers:
n Microsoft Internet Information Server (IIS) through the Information Server API (ISAPI)
n Netscape Enterprise Server (NES) through the Network Server API (NSAPI)
n iPlanet Webserver (iWS) through the Network Server API (NSAPI)
n Apache Web Server through the Apache Web Server API
WGate connects a “stateless” Web server, which communicates with Web browsers via single
request/response cycles, to a “stateful” SAP system where business transactions depend on internal
status.
68/84 PUBLIC 11/29/2006

When an Internet or intranet user starts an application from a Web browser and triggers an SAP
transaction, function module or report via the ITS, a server process must be running throughout
the user session (possibly longer) in order to maintain the user's context in a SAP system. Although
communication between the Web browser and the Web server is based on single request/response
cycles, WGate must be able to transfer the browser request to a permanently running server process.
This is the role of the AGate component.
AGate
AGate links the ITS to the SAP application server.
AGate is the core processing component of the ITS.
AGate receives Web browser requests from WGate and communicates with the SAP application
server via the DIAG protocol or the RFC protocol.
AGate is effectively responsible for managing all sessions, services and users, as well as for generating
the HTML documents that are sent back to the Web browser client.
When a connection has been established, AGate processes the requests and sends all relevant details
(including logon information) to the SAP system, which either starts the first dialog step of a new
transaction or submits further data for the next dialog step of a transaction already started. When
a dialog step has finished, AGate retrieves the results from a SAP system, processes them and sends
the response back to WGate.
6.4.1 ITS Instances
An Internet Transaction Server (ITS) installation consists of one or more ITS instances, each running
one or more ITS services.
An ITS instance contains one or more AGate instances and one or more WGate instances. Each AGate
instance may contain one or more AGate processes.
When you have run SAPinst once to create the physical installation, you can create any number of
additional ITS instances on the same hardware by running it repeatedly.
Running multiple ITS instances as part of the same physical installation allows you to minimize
hardware requirements and response times.
11/29/2006 PUBLIC 69/84

Figure 5: ITS Instances
The above graphic shows three ITS instances:

n ADM is used to run ITS Administration
n CON is used for testing
n DEV is used for development
To install these 3 instances, you must run SAPinst three times.
In production systems, security is critical, so you need to be more careful:
n Always run your production instance(s) (together with an ADM instance that runs ITS
Administration) apart from your development and test instances on a separate machine
n Always run WGate and AGate on separate machines in a dual host installation, as described in ITS
Installation Options [page 11].
In most cases, even in production systems, you only need to run one Web server and one WGate
instance against one AGate instance, but larger or more complex setups are sometimes required.
Below are some example configurations, which all assume that ‒ in production systems at least ‒
WGate and AGate are running on different machines.
70/84 PUBLIC 11/29/2006

Web Server ‒ ITS Scalability
Figure 6: WGate Connects to Multiple AGate Processes
This configuration shows one Web server and a single WGate instance running against a single AGate
instance that consists of multiple AGate processes. Multiple AGate processes allow you to handle
large numbers of users, but you should take into account memory limitations.
Figure 7: Multiple Web Servers / WGates Connect to one AGate
This configuration shows multiple Web servers and WGate instances connected to a single AGate
instance. This scenario may be useful if you want to set up separate Web servers for Internet and
Intranet users.
11/29/2006 PUBLIC 71/84

Figure 8: Multiple ITS Instances Connect to the Same SAP system
This configuration shows multiple Web servers and WGate instances, each connected to a separate
AGate instance, but all pointing to the same SAP application server.
WGate ‒ AGate Load Balancing

From Release 4.6D, the ITS supports load balancing by allowing you to attach several AGate instances
‒ each running on a separate machine ‒ to the same Web server and WGate instance.
Figure 9: Single WGate Interconnects With Multiple AGates
72/84 PUBLIC 11/29/2006

This configuration reduces the risk of failure in large-scale implementations, because WGate always
routes the requests to the appropriate AGate instance, according to the load at the time.
Figure 10: Multiple WGates Interconnect With Multiple AGates for High Availability Systems
This configuration reduces the risk of failure in large-scale implementations even further, because
requests can be routed through any WGate instance, which always routes the requests to the
appropriate AGate instance, according to the load at the time. You cannot know in advance how
requests are going to be routed, so it is essential that all WGates are connected to all AGates.
ITS ‒ SAP SYSTEM Scalability
Figure 11: ITS Connects to Single SAP Application Server
11/29/2006 PUBLIC 73/84

Figure 12: ITS Connects to SAP Message Server for Load Balancing
The ITS benefits from SAP system scalability through:

n Efficient transaction management
l Multiple work processes
l Load balancing to multiple application servers using login groups
n Database buffering
Buffering database tables on the application server achieves faster access to data.
6.4.2 ITS File Types and Locations
ITS File Types

When you install the Internet Transaction Server (ITS), the SAPinst allows you to select the packages
of files you need to run services.
A service is the set of files required by the ITS to drive an Internet application from a Web browser.
Each service can consist of up to five ITS file types:
n A service file
n HTML templates
n Flow files
n Language resources
n Multipurpose Internet Mail Extension (MIME) files
The ITS may also derive some information from the global service file, which contains settings that
apply to all services.
74/84 PUBLIC 11/29/2006

Service File
The service file contains the service description, which is the set of parameters that determines how a
service runs. If this information is incomplete at runtime, the ITS gets some details from the global
service file and/or requires the user to enter logon information. In any case, there is one service file
for each application.
Each service can be divided into one or more themes. Themes are instances of services that may differ
in look and feel (appearance, graphics, layout or language). Each theme has its own set of HTML
templates, flow files (if applicable), language resources, and MIME files, but the functionality of the
service is usually identical.
HTML Templates
HTML templates are one possibility to display application screens in a Web browser when running a
service.
For each screen, there may be one HTML template, which contains standard HTML code and
HTMLBusiness statements. HTMLBusiness is an SAP-specific macro language, which allows you to merge
SAP data dynamically into HTML templates.
Flow Files
Flow files define the dialog flow in applications based on ITS flow logic, depending on what the
user chooses to do.
In flow logic applications, there is one flow file for each HTML template that requires a dialog flow
definition. Each flow file contains Extensible Markup Language (XML) statements, using a predefined
subset of XML elements.
Language Resources
Language resources are language-independent texts used by the ITS to run a service in a particular
language.
Instead of hard-coded texts in a specific language, HTML templates contain placeholders and the
actual texts are stored in language resource files. At runtime, the ITS looks for placeholders in the
templates and replaces them with texts from the relevant language resource file. Not all templates
use language resource files.
MIME Files
MIME files contain the image, sound, and video elements as well as static JavaScripts of an ITS
application that are often included in services to enhance the visual appearance and effectiveness of
Internet applications.
Global Service File

Services also derive information from the global service file, which defines default parameter values
for all services. The values defined in individual service files always override values in the global
service file.
11/29/2006 PUBLIC 75/84

Summary of ITS File Types

The following table summarizes ITS file types and specifies their name format and extension:
File Type File Name Format and Extension
Service file <service>.srvc
HTML templates The name format of HTML templates depends on

the implementation model used to develop the
applications.
Format and extension for Web-enabled SAP
transactions:
n Language-independent templates:
<program>_<screen>.html
n Language-specific templates:
<program>_<screen>_<language>.html
The <program>, t, and <language> elements refer to
the SAP program, screen, and development language
of the associated ABAP transaction.
Format and extension for flow file applications:
n <template name>.html
Flow files <template name>.flow
The flow file is attached to the HTML template with
the same name.
Language resources <service>_<language>.htrc
MIME files Some examples of MIME files are:

n Image files:
l <name>.gif
l <name>.jpg
n Video files
l <name>.avi
n Sound files
l <name>.wav
Global service file global.srvc
ITS File Locations

Unless you specify different locations, the SAPinst installs new versions of the files required to run
Internet applications in the directories specified in the table below. All files are stored on the ITS
AGate server except MIME files, which are stored on the Web server.
ITS File Directory
Services <ITS_InstDir>\<ITS instance>\services
76/84 PUBLIC 11/29/2006

ITS File Directory

HTML templates <ITS_InstDir>\<ITS instance>\templates
n The templates directory contains a subdirectory
for each service under:
<ITS_InstDir>\<ITS instance>\
templates\<service>
n Each service subdirectory may also contain
subdirectories for each theme under:
<ITS_InstDir>\<ITS instance>\
templates\<service>\<theme>
Themes are service instances that differ only in
look and feel.
Flow files See above.
Language resources See above.
MIME files The directory location of MIME files depends on the
Web server configuration. The default is usually the
Web server root directory for each ITS instance.
For Microsoft Internet Information Server (IIS),
the recommended default is:
C:\Inetpub\wwwroot-<ITS
instance>\SAP\ITS\mimes\ <service>\<theme>
For Netscape Enterprise Server, the default is:
C:\Netscape\SuiteSpot\docs\sap\its\mimes\
For iPlanet Web Server, the default is:
C:\Netscape\Server<version>\docs\sap\its\mimes\
For Apache Http Server, the default is:
C:\Program Files\Apache
Group\Apache\htdocs\sap\its\mimes\
6.4.3 Backup Strategy (Optional)
The backup is optional. When updating the ITS, you can choose for every instance, whether a
backup should be done or not.
You can backup the following files:
n Services
n Templates
n Mimes
SAPinst then creates backups of the files in extra directories that indicate day and time of the backup.
11/29/2006 PUBLIC 77/84

6.5 General Information about SAPinst
Note
Imagine you have an already installed ITS instance called CSR. The relevant files will then be
stored in:
<ITS_InstDir>\CSR\services
<ITS_InstDir>\CSR\templates
<Web_Server_root>\sap\its\mimes\
Performing a new ITS installation affecting the CSR instance installation will then backup
automatically the old file versions to
<ITS_InstDir>\CSR\services.bak2001_07_10_12_35_55
<ITS_InstDir>\CSR\templates.bak2001_07_10_12_35_55
<Web_Server_root>\sap.bak2001_07_10_12_35_55
Note
See also: ITS File Types and Locations [page 74]
6.5.1 Using SAPinst GUI
The following table shows the most important functions that are available in SAPinst GUI:
SAPinst GUI Functions
Button / Function Key / Menu Entries Description

F1 Displays detailed information about each input
parameter.
Exit Cancels the installation with the following options:
n Stop
Stops the installation without further changing
the installation files. You can restart SAPinst to
continue the installation later from this point.
n Continue
Continues the installation.
78/84 PUBLIC 11/29/2006

Button / Function Key / Menu Entries Description

Log off Stops the SAPinst GUI, but SAPinst and the GUI server
continue running.
Note
If for some reason you need to log off during the
installation from the host where you control the
installation with SAPinst GUI, the installation
continues while you are logged off. You can later
reconnect to the same SAPinst installation from the
same or another host. For more information, see
Starting SAPinst GUI Separately [page 81].
Retry Performs the installation step again (if an error has
occurred).
Stop Stops the installation without further changing the
installation files. You can continue the installation
later from this point.
Continue Continues with the option you have chosen before.
6.5.2 Remote Installation with SAPinst
You can run SAPinst GUI in standalone mode to perform a remote installation.
Prerequisites
n Make sure that you have performed the preparation activities for your local host (SAPinst GUI
host) and your remote host.
n Both computers are in the same network and can ping each other.
To test this:
l Log on to your remote host and enter the command ping <local host>.
l Log on to the local host and enter the command ping <remote host>.
Process
1. You start SAPinst on the remote host [page 80].
2. You start SAPinst GUI separately [page 81].
11/29/2006 PUBLIC 79/84

6.5.3 Starting SAPinst on the Remote Host (Optional)
You can use this procedure to install your SAP system on a remote host. In this case, SAPinst and the
GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host
from which you want to control the installation with SAPinst GUI.
Prerequisites
n Both computers are in the same network and can ping each other.
To test this:
l Log on to your remote host and enter the command ping <local host>.
l Log on to the local host and enter the command ping <remote host>.
Your Remote Host Runs on a Windows Platform

1. Log on to your remote host as a user who is a member of the local administrators group.
2. Insert the Installation DVD in the DVD drive on your remote host.
3. Open a command prompt, and enter the following commands:
cd <DVD drive>:\SERV1\ITS\NT\I386\
sapinst.exe –nogui
For more information, see Running SAPinst on Windows [page 31].
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at
the command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 81].
Your Remote Host Runs on a UNIX Platform

1. Log on to your remote host as user root.
Caution
database.
2. Mount the SAP Server Components CD (<Installation_CD>.
3. Enter the following commands:
cd <Installation_CD>/SERV1/ITS/UNIX/LINUX_32/INSTALL
./sapinst –nogui
For more information, see Running SAPinst on Linux [page 36].
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at
the command prompt:
80/84 PUBLIC 11/29/2006

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation.
4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 81].
6.5.4 Starting SAPinst GUI Separately (Optional)
You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI
separately in the following cases:
n You have logged off from SAPinst.
If you logged off during the installation and you later want to reconnect to the still running
installation, you can start SAPinst GUI separately.
n You want to perform a remote installation.
If SAPinst GUI runs on a different host than SAPinst and the GUI server, you also have to start
SAPinst GUI separately.
Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.
2. Insert the SAP Server Components CD into your DVD drive.
3. To change to the relevant directory enter the following command:
cd <DVD drive>:\SERV1\ITS\NT\I386\
4. Start SAPinst GUI in one of the following ways:
n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command without additional parameters:
startinstgui.bat
SAPinst GUI uses as default the local host.
n If SAPinst and the GUI server runs on a different host than SAPinst GUI (remote installation),
enter the following command with additional parameters:
startinstgui.bat -host <host_name>
<host_name> is the host name of the installation host.
Note
l If you enter the command without additional parameters, SAPinst GUI uses as default
the local host. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As
SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and
the SAP Installation GUI Connection dialog appears.
In this case, enter the host name where SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
11/29/2006 PUBLIC 81/84

executable and enter the command startinstgui.bat —h.

Starting SAPinst GUI on a UNIX Platform
1. Log on as user root.
Caution
database.
2. Mount the SAP Server Components CD.
Note
Mount the CD locally. We do not recommend that you use Network File System (NFS).
3. To change to the mount directory enter the following command:

cd <Installation_CD>/SERV1/ITS/UNIX/LINUX_32/INSTALL
4. Start the SAPinst GUI in one of the following ways:
n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command without additional parameters:
./startInstGui.sh
SAPinst GUI uses as default the local host.
n If SAPinst and the GUI server runs on a different host than SAPinst GUI (remote installation),
enter the following command with additional parameters:
./startInstGui.sh -host <host_name>
<host_name> is the host name of the installation host
Note
l If you enter the command without additional parameters, SAPinst GUI uses as default
the local host. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As
SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the
SAP Installation GUI Connection dialog appears.
In this case, enter the host name where SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command ./startInstGui.sh —h.
6.5.5 Troubleshooting with SAPinst
The following tells you how to proceed when errors occur during the installation with SAPinst.
82/84 PUBLIC 11/29/2006

If an error occurs, SAPinst:

n Stops the installation
n Displays a dialog informing you about the error
Procedure
1. You can directly view the log file by choosing View Logs.
2. If an error occurs during the dialog or processing phase, you can:
n Try to solve the problem
n Abort the installation with Exit
n Continue the installation by choosing Retry.
3. Windows: We recommend that you check the log and trace files of the GUI server and SAPinst
GUI in the directory %userprofile%\.sdtgui\ for errors.
4. Linux: We recommend that you check the log and trace files of the GUI server and SAPinst GUI in
the directory <user_home>/.sdtgui/ for errors.
5. Windows: If you find error messages in the SDM logs that software components are not available,
you can ignore them. For more information, see SAP Note 828978.
6. Linux: If you find error messages like the following in the SDM logs, you can ignore them:
Error: <SCA name>: Location of software component '<SCA name>' / <SCA vendor>'
/ '<SCA location>' / '<SCA counter> ' unknown./ Error: <SCA name> : system
component version store not updated.
For more information, see SAP Note 828978.
11/29/2006 PUBLIC 83/84

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2007 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.

Sap @web 6.20 Installation Guidepatchlevel 23 or Higher

Uploaded by

Document Information

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 @web 6.20 Installation Guidepatchlevel 23 or Higher

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP @WEB 6.20

Document version: 1.0 ‒ 11/29/2006

2/84 PUBLIC 11/29/2006

11/29/2006 PUBLIC 3/84

1.0 11/29/2006 Initial version

4/84 PUBLIC 11/29/2006

Chapter 1 SAP@Web Installation Guide: Release 6.20 Patch 23 and higher . . . 7

Chapter 4 Installation Procedure . . . . . . . . . . . . . . . . . . . . 31

Chapter 5 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . 43

11/29/2006 PUBLIC 5/84

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 61

6/84 PUBLIC 11/29/2006

1 SAP@Web Installation Guide: Release

n SAP Internet Transaction Server (ITS)

11/29/2006 PUBLIC 7/84

New ITS Feature

8/84 PUBLIC 11/29/2006

Activities for Windows

1. Check the required documentation [page 9].

Activities for Linux

1. Check the required documentation [page 9].

2.1 Required Documentation

Installation Notes for SAP@Web

SAP Note Description

11/29/2006 PUBLIC 9/84

SAP Note Description

2.2 ITS Security

Separating WGate and AGate

10/84 PUBLIC 11/29/2006

Restricting Access to the SAP system

2.3 ITS Installation Options

11/29/2006 PUBLIC 11/84

n On separate machines in a dual host installation

Single Host Installation

Figure 1: Single Host Installation

Dual Host Installation

12/84 PUBLIC 11/29/2006

Figure 2: Dual Host Installation

Figure 3: Dual Host Installation with Firewall

11/29/2006 PUBLIC 13/84

IAC Installation Using the Package Manager

2.4 Hardware and Software Requirements

Minimum Hardware Requirements for AGate (Single or Dual Host Installation)

14/84 PUBLIC 11/29/2006

SAP Parameters (Load Balancing or Single Application Server)

Option Load Balancing Single Server Application

Options WGate Installation on Separate Single Host Installation

2.5 IAC Packages

11/29/2006 PUBLIC 15/84

How SAPinst Handles IAC Packages

Standard IAC packages for the ITS

IAC Package Description

16/84 PUBLIC 11/29/2006

IAC Package Description

n Packages on the Server Components CD:

n Packages located in a file system or other network location

11/29/2006 PUBLIC 17/84

How Installed IAC Packages Interact

IAC Package File Names

IAC package file names are not case-sensitive.

2.6 ITS with LDAP and WLBS (Windows only)

18/84 PUBLIC 11/29/2006