ITSINST

Installation Guide

SAP®

@WEB 6.20

Including Installation of

- SAP ITS on Windows 2000, Linux

(AGate/WGate), Solaris (WGate)

- SAP@Web Studio

Document Version 1.00 - July 01, 2002

SAP AG Neurottstraße 16 69190 WalldorfGermanyT +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

© Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and

SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®,

RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are

registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of IBM Corp.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of

the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,

WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business

Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, and other SAP products

and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. MarketSet and Enterprise

Buyer are jointly owned trademarks of SAP Markets and Commerce

One. All other product and service names mentioned are the

trademarks of their respective owners.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

http://service.sap.com/instguides

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in the system. These include reportnames, program names,transaction codes, table names, and individual keywords of a programminglanguage, when surrounded by body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly as they appear in the documentation.

<Exampletext>

Variable user entry. Pointed brackets indicate that you replace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as

F2) or the ENTER key

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

SAP@Web Installation Guide: Release 6.20

4 Februar/2002


Contents

1 SAP@WEB INSTALLATION GUIDE: RELEASE 6.20 .............................7

2 HOW TO INSTALL YOUR ITS INSTANCES ............................................9Installation Planning.......................................................................................................................10

Installation Preparations.................................................................................................................10

Installation Process.........................................................................................................................11

Post-Installation Activities .............................................................................................................12

2.1 Planning ................................................................................................................................13

2.1.1 Required Documentation................................................................................................13

2.1.2 ITS Security....................................................................................................................15

2.1.3 ITS Installation Options .................................................................................................16

2.1.4 Installation Requirements...............................................................................................20

2.1.5 IAC Packages .................................................................................................................22

2.1.6 ITS with LDAP and WLBS (Windows only).................................................................25

2.1.7 Upgrade from a pre-620 ITS to Release 6.20.................................................................28

2.2 Preparations..........................................................................................................................29

2.2.1 Creating the ITS Administrator Account (Windows only).............................................29

2.2.2 Creating Web Server Instances ......................................................................................30

2.2.2.1 Configuring Released Web Servers on Windows ......................................................30

2.2.2.2 Configuring Released Web Servers for Linux and Solaris.........................................33

2.2.3 Preparing the SAPinst Installation..................................................................................35

2.3 Installation Procedures ........................................................................................................36

2.3.1 Installation on Windows.................................................................................................36

2.3.1.1 Input for the Installation on Windows........................................................................36

2.3.1.2 Installing an ITS instance on Windows......................................................................43

2.3.1.3 Installing additional ITS Instances on Windows ........................................................47

2.3.2 Installation on Linux/Solaris ..........................................................................................48

2.3.2.1 Input for the Installation on Linux/Solaris .................................................................48

2.3.2.2 Installing an ITS Instance on Linux/Solaris ...............................................................53

2.3.2.3 Starting and stopping an ITS Instance on Linux/Solaris ............................................56

2.3.3 Checking the ITS Installation.........................................................................................57

2.3.4 Starting an ITS Service from a Web Browser ................................................................61

2.4 Post-Installation Activities...................................................................................................62

2.4.1 IAC Publishing with the IACOR on Windows...............................................................62

2.4.1.1 Starting the IACOR....................................................................................................63

2.4.1.2 Configuring the IACOR .............................................................................................65

2.4.1.3 Publishing the IACs from a SAP system....................................................................70

2.4.1.4 Managing the IACOR ................................................................................................71

2.4.2 Watchdog Configuration (Windows only) .....................................................................72

2.4.2.1 Configuring Watchdog for WLBS .............................................................................73

2.4.2.2 Registering ITS in an LDAP Directory ......................................................................77

2.4.2.3 Monitoring with Watchdog ........................................................................................80

2.4.2.4 Registry Configuration ...............................................................................................82

2.4.2.5 Additional Information...............................................................................................85

2.4.3 IAC Publishing with the IACOR on Linux ....................................................................87

2.4.3.1 Configuring the IACOR on LINUX...........................................................................87

2.4.3.2 Publishing the IACs from a SAP System ...................................................................91

Februar/2002 5


2.5 Additional Information........................................................................................................92

2.5.1 SAPinst Specific Information.........................................................................................93

2.5.1.1 Continuing an Interrupted Installation........................................................................93

2.5.1.2 Performing a Remote Installation with SAPinst.........................................................95

2.5.1.3 Handling the CD Browser Dialog ..............................................................................99

2.5.2 SAP ITS Specific Information......................................................................................100

2.5.2.1 Installing Additional IACs .......................................................................................100

2.5.2.2 Repeating an ITS Installation Unattended................................................................100

2.5.2.3 Applying Patches for the ITS ...................................................................................101

2.5.2.4 Uninstalling the ITS .................................................................................................102

3 SAP@WEB STUDIO INSTALLATION GUIDE .....................................103

3.1 SAP@Web Studio Installation ..........................................................................................104

3.1.1 SAP@Web Studio Installation Requirements ..............................................................105

3.1.2 Preparing for SAP@Web Studio Installation ...............................................................106

3.1.3 Installing the SAP@Web Studio ..................................................................................107

3.1.4 Setting up the SAP@Web Studio Environment ...........................................................108

4 APPENDIX ............................................................................................109

4.1 General Information about ITS ........................................................................................109

4.2 ITS Instances ......................................................................................................................111

4.3 ITS File Types and Locations............................................................................................117

4.4 ITS Backup Strategy..........................................................................................................120

4.5 ITS Sub-Components.........................................................................................................121

6 Februar/2002


1 SAP@Web Installation Guide: Release 6.20

Purpose

This documentation describes how to install the SAP Internet Transaction Server (ITS) and related tools on released WINDOWS and UNIX platforms:

For more information

- About the SAP ITS availability, see SAP Note 517277 SAP ITS 6.20 availability and restrictions

- About released platforms, see http://service.sap.com/platforms

¶ SAP Internet Transaction Server

¶ SAP Internet Transaction Server Administration

¶ Internet Application Components Object Receiver (IACOR)

¶ ITS Watchdog (Winows only)

¶ SAP@Web Studio

Implementation Considerations

If you want to give Internet and intranet users direct access to the SAP system by enablingthem to start SAP Internet applications based on the ITS infrastructure from a Web browser, you must install the ITS.

If you want to monitor or tune all existing ITS instances via SAP’s delivered, Web-based userinterface you must install ITS Administration.

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 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 since Sap systems of Release 4.6C. For more information about IACOR, see ITS Sub Components[page 121].

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. For more information about ITS Watchdog, see ITS Sub Components [page 121].

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.

Integration

You must have installed the released Web server and Web browser software.

Februar/2002 7


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 HTML

Business 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.

New Featrures

New Installation Tool

For ITS Release 6.20, SAP provides a new installation tool, called System LandscapeImplementation Manager, known for short as "SAPinst". This has a graphical user interface(GUI) called SAPinst GUI that allows you to watch the progress of the installation and see all messages issued by SAPinst.

The main advantages compared with the previous installation tool ITSsetup are:

¶ SAPinst lets you step back to correct your entries during the input phase without restarting the installation.

¶ SAPinst does not abort due to errors. Instead, it stops the installation and you can retry the installation after having solved the problem. Alternatively, you can abort the installation manually if you want.

¶ SAPinst continues an aborted installation directly from the point of failure.

¶ SAPinst records installation progress in a single log file, sapinst.log.

¶ SAPinst has a graphical user interface (GUI) called SAPinst GUI that allows you to watchthe progress of the installation and see all messages issued by SAPinst. As SAPinst GUI is Java based, you need a Java Runtime Environment (JRE) during the installationprocedure.

A What's this? help is integrated in SAPinst GUI. To use this, choose , then click on the field for which you want more information.

You can start SAPinst GUI on a remote computer if you want.

The SAP@Web Studio has an 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 Februar/2002


2 How To Install your ITS Instances

The structure of the installation documentation and therefore the procedure to use it have changed significantly for SAP ITS 6.20.

Use the tables below as a checklist for installing the ITS instances and to navigate through the installation procedures. All necessary installation phases (planning, preparation,installation and post-installation) are listed in these tables. They contain links to the procedures in this documentation. Use the links to the general descriptions of the actions andto any additional information to help you perform the actions. This prevents you missingimportant information.

Throughout this documentation, the following acronyms are used to mark if a section or a prompt is only valid for certain instance installations:SH: Single Host InstanceAI: Dual Host AGate InstanceWI: Dual Host WGate InstanceADM: ITS Administration Instance

We recommend you to proceed as follows to install your SAP ITS:

1. Print out the tables below.

2. Follow the installation sequence exactly as shown in the tables:

a. If a step is required for your installation, follow the link for that step to the corresponding section.

b. Perform the procedure described there.

c. After successfully completing the installation step, mark the corresponding entry in the printed table with ! to log the progress of your installation.

d. Proceed with the next step listed in the table.

Februar/2002 9


Installation Planning ! Action

Activities for both operating systems

Check the required documentation [page 13]

Check ITS Security [page 15]

Check ITS Installation Options [page 16]

Work out what kind of Internet Application Components (IACs) you need: IACPackages [page 22]

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 28]

If you are installing on Windws

Check the installation requirements [page 20]

Work out if you want to use the ITS in an SAP environment with Lightweight Directory Access Protocol (LDAP) and/or Microsoft Windows Load BalancingService (WLBS) [ Page 25].

Installation Preparations Before you install SAP ITS on a host, you have to prepare the host accordingly:

! Action

If you are installing on Windws

Make sure that the Windows 2000 Server software is properly installed.

For security reasons, use the Windows File System NTFS to store ITS files.NTFS fully supports Windows 2000 security and long file names. To checkthat you are using NTFS:

a. Select the hard drive icon in the Windows Explorer.b. Click the right mouse button.c. Choose Properties.d. Choose the General tab. e. Check that the specified file system is NTFS.

Create the ITS administrator account [page 29].

Configure Released Web Server Instances on Windows[page 30]

If you are installing on Linux / Solaris (WGate)

Configure Released Web Server Instances on Linux/Solaris [page 33]


Prepare the SAPinst Installation [page 35]

10 Februar/2002


Installation Process

If you want to perform a Single Host Installation:

! Action

If you are installing on Windows

Check the input for the installation on Windows [page 36]

Install an ITS instance on Windows [page 43]

Install additional ITS Instances on Windows [page 47]

If you are installing on Linux / Solaris(WGate)

Check the input for the installation on Linux/Solaris [page 48]

Installing an ITS Instance on Linux / Solaris [page 53]

Starting and stopping an ITS Instance on Linux/Solaris [page 56]


Check the installation [page 57]

If you want to perform a Dual Host Installation:

! Action


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.


Check the input for the installation on Windows [page 36]

Install the AGate first. That means, on your AGate host

- Run SAPinst on Windows [page 43]

- Install an ITS Instance on Windows [page 47]

Afterwards, install the WGate. That means, on your WGate host

- Run SAPinst on Windows [page 43]

- Install an ITS Instance on Windows [page 47]

If you are installing on Linux / Solaris (WGate)

Check the input for the installation on Linux/Solaris [page 48]

Afterwards, install the WGate. That means, on your WGate host install an ITS Instance on Linux / Solaris [page 53]


Check the installation [page 57]

Februar/2002 11


Post-Installation Activities To complete the installation, you have to perform a number of actions. Some of these actionsare mandatory, others are optional and serve to activate features that might be useful.

! Action


If you have have connected an ITS instance to an SAP system Ó 6.10, you must use the IACOR to publish the IACs (You can publish IACs since SAP systems of Release 4.6C):

Start the IACOR [page 63]

Configure the IACOR [page 65]

Publish the IACs from the SAP system [page 70]

Optionally, you can manage the IACOR [page 71]

If you want to use the ITS Watchdog, you can:

Configure Watchdog for Load Balancing Service [page 73]

Register ITS in an LDAP Directory [page 77]

Monitor WGate hosts with Watchdog [page 80]

If you are installing on Linux

If you have have connected an ITS instance to an SAP system Ó 6.10, you must use the IACOR to publish the IACs (You can publish IACs since SAP systems of Release 4.6C):

Configuring the IACOR on LINUX [page 87]

Publish the IACs from the SAP system [page 91]

12 Februar/2002


2.1 Planning

2.1.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 installationdocumentation.

Make sure that you have the most recent version of each note. You can find the SAP Notesin SAP Service Marketplace at: http://service.sap.com/notes.

Table of Installation Notes for SAP@Web

Note number Title

526835 Installation of SAP@Web 6.20

491781 ITS Updates in Release 6.20

375810 Installing the ITS for SAP Employee Self-Service

197746 Maint. strategy: Internet Transaction Server (ITS)

335521 ITS Patch installation of kernel files

325149 Publishing IAC objects

336884 IACOR in ITS Dual Host Installations

Troubleshooting Guides

There are two important guides:

¶ SAPinst Troubleshooting Guide at: http://service.sap.com/sapinstfeedback

¶ ITS Tuning and Troubleshooting Guide at:http://service.sap.com/sap-its (see -> Media Center -> Literature)

We recommend to have both guides available for the installation.

Additional Information

For information about:

¶ General information on ITS, Windows Service, monitoring and configuration, see at: http://service.sap.com/sap-its (see -> Media Center -> Literature)

¶ ITS Sizing, see Sizing the Internet Transaction Server guide at: http://service.sap.com/sizing

¶ Security issues, see the SAP Security Guide at: http://service.sap.com/securityguide

You can find information about ITS security in Volume II: SAP Security Services in Detail,Chapter 2-10: Special Topics under Internet Application Security.

Februar/2002 13


¶ ITS Technical Infrastructure, see the documentation SAP Internet Transaction Server - Technical Infrastructure at the following address:http://service.sap.com/network

¶ Platforms released for SAP ITS AGate and WGate see http://service.sap.com/platforms (see: Platform Strategy for Front End &

Middleware Components)

14 Februar/2002


2.1.2 ITS SecurityEnabling 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:

¶ Separating WGate and AGate

¶ Protecting ITS files

¶ Restricting access to a SAP system

Separating WGate and AGateTo 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 installingWGate and AGate on different machines.

For further information, see ITS Installation Options [page 16].

Protecting ITS FilesTo safeguard ITS files and passwords against unauthorized users, SAP recommends that you restrict access to this information as much as possible. Dialogs in the SAPinst show you how to achieve this.

Restricting Access to a SAP systemTo run SAP Internet applications - known to the ITS as services - from a Web browser, usersneed an SAP system user account. To set this up, you can do any of the following:

¶ Create a global SAP system user account for all services.

In this case, users can start any service.

¶ 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.

¶ Create no static SAP system user account.

In this case, users are prompted for a user name and password in a logon procedureeach 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 or ITS Administration. Only accounts defined in the ITS administrator group and the ITS user group can access these files.

Using one global SAP system user account with extensive authorizations can be a security risk. Although the SAPinst may use one global user account, SAP strongly recommends that you apply security settings for each service.Your SAP system administrator must set up service-specific user accounts.

Februar/2002 15


See also:

For more information about security issues, see the SAP Security Guide at: http://service.sap.com/securityguide.

You can find information about ITS security in Volume II: SAP Security Services in Detail,Chapter 2-10: Special Topics under Internet Application Security.

2.1.3 ITS Installation Options 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 separatesensitive 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:

¶ 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

¶ 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:

¶ On the same machine in a single host installation

¶ 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.

16 Februar/2002


Single Host InstallationA single host installation places the Web server, WGate and AGate on the same host machine:

ISAPI,NSAPI,Apache

Web server

SAP

System

application

server

TCP/IP

ITSITS

RFC

DIAG

CGIAGateWGate

The AGate instance may consist of more than one AGate process. For further information,see ITS Instances [page 111].

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.

Februar/2002 17


Dual Host InstallationA dual host installation places WGate and AGate on separate host machines - WGate on the Web server host and AGate on a different host:

ISAPI,NSAPI,Apache

Web server

SAP

System

application

server

TCP/IP

ITSITS

RFC

DIAG

CGIAGateWGate

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 further information,see ITS Instances [page 111].

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 Webserver, a firewall between WGate and AGate, and a firewall between AGate and SAP system:

18 Februar/2002


SAP application

server

Web server

(WGate)

ITS server

(AGate)

Web

browser

SSL encryption SNC encryption SNC encryption

SAP System

database serverSSL = Secure Sockets Layer

SNC = Secure Network Communication

Internet

router

External

firewall

Internal

firewall

IAC Installation Using the Package ManagerThe tool Package Manager allows you to easily apply additional IAC packages to an existing ITS instances, for example if you have missed installing a package or if a patch for an installed package is delivered.

Februar/2002 19


2.1.4 Installation RequirementsBefore you install the Internet Transaction Server (ITS), you must satisfy the hardware and software requirements, and check you have all the other necessary information by taking the following steps:

1. Check the hardware requirements specified below.

2. Check the software requirements specified below.

3. Check that you have all the other information you need to perform the installation, as specified in the requirement checklists below.

Hardware RequirementsThe tables below specify the minimum hardware you need to run the ITS, depending onwhether you are performing a single host installation or a dual host installation.

However, please remember that memory and disk space requirements can vary, dependingon factors such as the number of users concurrently accessing the system.

For more information on ITS Sizing, see Sizing the Internet Transaction Server guide at: http://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) 128 MB

Hardware systems with 128 MB RAM are only recommended for non-production purposes such asdevelopment and testing

For WGate (in dual host installation environments) please see the Web server vendorinformation for hardware requirements.

Software RequirementsFor information about ITS software requirements (including supported platforms, Web servers, and Web browsers), read the section SAP Internet Transaction Server in SAPsystem Requirements for Networks, Frontends, Communication Interfaces at:

http://service.sap.com/platforms (see: Platform Strategy for Front End &

Middleware Components)

Requirement ChecklistsThe following tables specify all the information you need to install the ITS. Make sure that you have this information available before running the SAPinst.

AGate Configuration Parameters

Homepage(URL displayed when leaving a service)

20 Februar/2002


SAP Parameters

SAP system name

Client

User (global user for all services)

Password matching user and client

You only need to provide values for client, user, and password in the case you want to allowanonymous logins to the SAP system. The 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 Application Server

SAP message server name Õ Not applicable

Port number for SAP message server Õ Not applicable

Login group used by ITS Õ Not applicable

SAP application server name Not applicable Õ

SAP system number Not applicable Õ

SAProuter string Õ (optional) Õ (optional)

Windows 2000 System Parameters

Options Use NT Security Set up Security Layer

Name of user ITSadm Õ Not applicable

Password of user ITSadm Õ Not applicable

Name of group ITSAdminstrators Õ Not applicable

Name of group ITSUsers Õ Not applicable

WGate Installation

Options WGate Installationon Separate Host

Single Host Installation

Name or IP address of AGate host Õ Not applicable

Number of ports(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

2000 directory on the AGate host.

Õ Not applicable

Februar/2002 21


2.1.5 IAC PackagesDefinition

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 Resourcefiles, Mimes etc.) and SAP business applications (transaction, function call, or BAPI).

Use

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 the SAP GUI for Administration etc. integrated into SAPinst. All these packages are delivered with the ITS and SAP@Web Studio on the Server ComponentsCD.

The SAPinst program allows you to install the ITS system packages as part of the standardinstallation procedure. To access other, application-dependent IAC packages, you canbrowse the file system.

For more information about developing your own IACs, see SAP@Web Studio InstallationGuide [page 103].

How the SAPinst Program 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 the SAPinst program 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 since SAP systems of Release 4.6C."You can publish IACs since SAP systems of Release 4.6C.

As stated above, SAPinst program allows you to select the IAC packages you want to installwith a particular ITS instance. Packages are either integrated into the setup or located in a file system or other network location:

¶ 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.

22 Februar/2002


Standard IAC packages for the ITS

The ITS is downward compatible to all currently supported SAP releases. For more information on supported SAP releases, see documentation The release strategy of mySAP.com components at: http://service.sap.com/releasestrategy.

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).

FlowDbg Flow File debugger package.

You need this package usually on development systems when youwant to debug ITS applications that use ITS Flow Logic technology.

its_adm ITS Administration package.

Integrated into the SAPinst of an administration instance and installedautomatically.

Watchdog ITS Watchdog package

Integrated into the SAPinst of an administration instance and installedautomatically, if required.

All of the above packages and the additional IAC packages you select for installation are copied by the SAPinst program to:

<ITS_InstDir>\install\packages

Februar/2002 23


¶ 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

IAC Packages on the Server Components CD-ROM

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 the IACOR [page 62].

Example: If you want to integrate the SAP Web Application Server Ó 6.20 or a SAPCRM Ó 3.0 System (based on Release 6.10), you must use the IACOR.

During the installation SAPinst displays all available IAC packages of the Server Components CD (if starting theinstallation from CD). For each SAP system that you want the ITS to connect to, you can select the correspondingapplication packages in addition to your selected standard ITS IAC package (see above).

Example: You want to integrate an R/3 4.6B and an SAP BW 2.0B System. In this case you should install

¶ an ITS instance for the SAP system with the IACs in directory its/common/packages/R3/46b

¶ another ITS instance for the SAP BW System with the IACs in directory its/common/packages/BW/20b

Location

Server Components CD-ROM Path:

its /common/packages/<application>/<release>

¶ Packages located in a file system or other network location

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.

For more information about the compressed packages formats, see SAP Note 509796ITS: SAR packages replace CAR packages.

¶ 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.

24 Februar/2002


How Installed IAC Packages InteractYou 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 differentversions of the same IACs, one version overwrites the other.

IACs should never occur simultaneously in more than one package.When ITS has been setup 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 NamesThe file names of IAC packages do not observe specific naming conventions, but the nature of the package is usually clear:

- 46c_all.sar is a cross-application package for a SAP system with

Basis Release 4.6C.

- 46d_bas.sar is a package of Basis services for a SAP system with

Basis Release 4.6D.

IAC package file names are not case-sensitive.

2.1.6 ITS with LDAP and WLBS (Windows only) 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.

Since Release 4.6D the ITS WGate can connect to multiple AGates thus greatly increasingthe ITS fault tolerance.

Nevertheless, WGate failures are not covered by the mechanism. To achieve fault tolerancefor 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.

ITS Watchdog is a optional tool for monitoring and managing ITS WGate instances in a LDAPenvironment 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:

¶ Monitoring of all ITS instances running on the local host via a dual DCOM interface.

¶ Registration of ITS instance in LDAP directories (optional).

¶ High availability solution using Microsoft WLBS for the complete processing queueincluding WGate (optional).

Februar/2002 25


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 statusinformation on all URLs, integrates this information into the overall system status, periodicallyrefreshes 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 theonline help of SAP MMC.

So far the following problems have been noticed:

¶ The current load distribution that connects multiple AGates to a single WGaterecognizes 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.

¶ 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 becausethere 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.

¶ Enabling ITS LDAP registration results in a security problem. The “ldapreg.srvc” serviceneeds to be able to start the SAP function module WWW_LDAP_REGISTER_ITS.Therefore SAP user and password must be specified in ldapreg.srvc. By overriding“_FUNCTION” in the URL it is possible to start other Web enabled function modules in the SAP system via the registration URL.

26 Februar/2002


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 forsome ports (defined by so-called port rules). WLBS provides the following features:

¶ Each request addressing the cluster IP address is handled by exactly one server in the cluster

¶ 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.

¶ WLBS automatically detects network or hardware failures of cluster servers and redistributes the clients among the remaining servers. It also detects if a server becomesavailable again and will add the server to cluster.

Therefore WLBS can be used to achieve both high availability and load balancing for TCP/IPservices. Nevertheless WLBS has some limitations that must be taken into consideration:

¶ WLBS cannot detect software failures by itself. For example, it does not recognizeIIS, ITS WGate, ITS AGate or SAP system failure. Watchdog will notice these software failures and enable/disable the corresponding port rules.

¶ 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 functionof the client IP address. This enables each cluster server to rapidly decide whichserver is responsible for handling the request (for example without any additionalserver interaction), but it requires that the client IP addresses are statistically equaldistributed. If for example, all clients connect via a proxy server to the Web serverWLBS load distribution does not work, since all clients seem to use the same IPaddress.

¶ 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 availableservers. So some ITS clients will loose the session context during the redistributionprocess.

ITS Watchdog with other LBSIn 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 andavailability of the WGate host via a Web browser.

This simple functionality is only available with Microsoft Internet Information Server (IIS).

Februar/2002 27


2.1.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 nowthe following developments for Release 6.20:

¶ A new cross-platform registry file: ItsRegistry<ITS_instance_name>.xml (default path:

<ITS_InstDir>/config).

¶ Scripts to start the ITS instances on Linux: Its<ITS_instance_name>.sh (default path:

<ITS_InstDir>/programs)

¶ 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 onlya reference to the WGate instance name. The default path for wgate.conf is:

- Apache, iPlanet, and Netscape Enterprise Web Server: <WebServer_InstDir>/conf

- Internet Information Server: <WebServer_InstDir>/programs

28 Februar/2002


2.2 Preparations

2.2.1 Creating the ITS Administrator Account (Windows only)

Use

You use this procedure to create the ITS administrator account.

Procedure

1. Log on to the Windows system as an administrator.

2. Perform the following actions:

This documentation uses the ITS administrator account name ITSadm, but you can choose any name you like.

a. Choose Start Programs Administrative Tools Computer Management.

b. Choose System Tools Local Users and Groups Users

c. Choose Action New User.

d. Enter the following values:

i. User Name: ITSadm

ii. Full Name: SAP ITS Administrator

iii. Description: <description>

iv. Password: <password>

v. Confirm Password: <password>

e. Choose Create.

f. Choose Close.

Result

The ITS administrator account ITSadm is created.

Februar/2002 29


2.2.2 Creating Web Server Instances Use

When you create an ITS instance, you need to attach it to a Web server.

¶ In all ITS releases up to and including Release 4.6C, you had to attach each ITS instance(AGate) to a separate Web server instance (WGate).

This is because each Web server instance had to run in its own memory space to enableWGate to communicate with the correct AGate.

¶ From Release 4.6D, you can attach several ITS instances (AGates) to a single Webserver instance (WGate).

Nevertheless, even if all ITS instances on a single machine now use the same WGateexecutable, 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 whichAGate 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 owndedicated ITS instance and Web server instance makes sense, because you are then free to start and stop other ITS instances when you want.

For more information on ITS released Web Server Software, see at http://service.sap.com/platforms (see: Platform Strategy for Front End &

Middleware Components).

Procedure

The following documentation for configuring released Web server software isonly a quick guide to creating your Web Server instances. For more details,see the vendor's documentation.

2.2.2.1 Configuring Released Web Servers on Windows

MS Internet Information Server Instances (IIS instances).

1. Make sure to use a version of IIS that Iis released for the ITS.

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.

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.

30 Februar/2002


2. 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 Side Creation Wizards starts.

d. Choose Next.

Enter a description in the Web Site Description field and choose Next.

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 2above).

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.

IPlant 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).

b. Server Identifier: Set this value to <Hostname>adm.


Februar/2002 31


Apache HTTP Server Instances

1. Make sure to use a version of Apache HTTP Server that is released for the ITS.

On a Windows 2000 Web Host you can install Apache via binary win-32 install shield with option Typical. This includes the Dynamic Shared Objectsfunctionality (DSO) that is needed as WGate is built as a loadable modulerequiring the Apache DSO functionality.For more information about the DSO strategy, see at: 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 separateDocumentRoot, for example:

#

# VirtualHost example:

# Almost any Apache directive may go into a VirtualHost container.

#

<VirtualHost hostname.domain:81>

# ServerAdmin [email protected]

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>



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




32 Februar/2002



</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


2.2.2.2 Configuring Released Web Servers for Linux and Solaris

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 81

Listen 82

b. Section Virtual Host:

Add virtual hosts for each of your WGate instances and define at least one separateDocumentRoot, for example:

#

# VirtualHost example:

# Almost any Apache directive may go into a VirtualHost container.

#



DocumentRoot /usr/local.orig/httpd/htdocsAIO





</VirtualHost>



DocumentRoot /usr/local.orig/httpd/htdocsCSR

Februar/2002 33






</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.

34 Februar/2002


2.2.3 Preparing the SAPinst Installation Use

The SAP J2EE Engine and the Java-based SAPinst graphical user interface (GUI) called SAPinst GUI require a Java Runtime Environment, derived from a JDK™ 2 SDK, Standard Edition. Therefore, you must install JRE on every host on which you want to install an instance, as described in this section.

Prerequisites

¶ You can find the JRE versions that are released for a SAP system in the SAP ServiceMarketplace at: http://service.sap.com/platformsĄ Availability for SAP Basis /

SAP KernelĄ Planned OS / DB / JDK Releases for SAP Web AS 6.20.

SAPinst GUI requires the same JRE version as the SAP Web AS 6.20. JRE is not part of the SAP shipment.

- Make sure that your JAVA_HOME environment variable is set to

<JAVA_HOME>.

- Make sure that $JAVA_HOME/bin (UNIX) respective %JAVA_HOME%\bin

(Windows) is included in your system path.

- On Windows, you have to reboot your system when you have set the system environment variable.

¶ This section describes preparations for a local installation with SAPinst. However, you can perform a remote installation [page 95] using a standalone SAPinst GUI on aseparate Windows or UNIX 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.

Procedure

To check the JDK ext directory:

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:

- UNIX: <JAVA_HOME>/JRE/lib/ext

- Windows: <JAVA_HOME>\JRE\lib\ext

3. If you find any .jar files, rename them to, for example, xerces.xxx.

Do not forget to rename the files back to their original names after the installation procedure is complete.

Februar/2002 35


2.3 Installation Procedures

The following procedures do not follow the exact sequence for an installation.The navigation of the ITS instance installation is provided by the installationprocess table in section How to install your ITS instance [page 11].

2.3.1 Installation on Windows

2.3.1.1 Input for the Installation on Windows To prepare for the input phase of the installation, we recommend you to write down the information you have to enter before starting SAPinst. Having the required information readyin advance helps you avoid unnecessary delays and errors.

The following table shows the window names that will appear during the installationprocedure of the installation types: Single Host / Dual Host (AGate, WGate) / Administrationand their prompts that are required for the installation.

The akronyms indicate which window appears for which installation typ:

Acronym Installation Type

SH Single Host instance

AI AGate instance

WI WGate instance

ADM ITS Administration

Window Name Input

Defining ITS Debugger Port

(SH/AI/WI/ADM)

The port is needed for SAP support activities (connecting and debugging)

Defining Iacor Ports

(SH/AI/WI/ADM)

¶ Iacor input port numberUse the displayed default port number or any other free portnumber.

¶ Iacor output port numberUse the displayed default port number or any other free portnumber.

SelectingInstallation Mode

(SH/AI/WI/ADM)

¶ Typical. Runs your IACs and other applicationsSelect Typical to install your ITS instance for running applications except ITS Administration.

¶ Administration. Runs ITS AdministrationIf you want to install an ITS Administration or The ITS Watchdog tool, select Administration. Like any other ITS instance, the administration instance must run under its own dedicated ITS server.

For further information about all aspects of Windows Service after installation, see the ITS Administration Guide.

36 Februar/2002


Window Name Input

Installing a virtual ITS Instance

(SH/AI/WI)

Any name is valid, but enter a value that is meaningful to you. If you are connecting to an SAP system, SAP recommends you to use the name of the SAP system.

You can display the names of the instances already installed on this host in the dropdown list box. Only choose such a displayedinstance, if you want to override it.

SelectingInstallation Type

(SH/AI/WI/ADM)

Decide, whether to perform a Single Host or Dual HostInstallation. For a Dual Host installation you must first install the AGate (Application Side) on the AGate host and afterwards the WGate (Web Server Side) on the WGate host.

Selecting a WebServer Instance

(SH/WI/ADM)

The list displayed in this dialog depends on the Web server instances already created.

This dialog states also whether a Web server is already in use by an ITS instance.

Selecting the IACPackages

(SH/AI/WI)

Do the following:

- Select the IAC package(s) you want to install.

- In case of a dual host installation, the selected packagesfor the AGate and WGate hosts must be the same.

- You can select packages also by applying the packagepath by choosing Add Row.

Finally a confirmation box displays all selected packages.

For more information on choosing IACs see IAC Packages [page 22]

You can add IAC packages to an existing ITS instance later by running the ITS Package Manager [page 100].

Defining WebServer Parameters

(SH/AI)

Enter the URLs to access your Web Server.

Defining Log OffURL

(SH/AI)

Enter the URL that should be accessed, when the user logs off from the ITS application.

We recommend not use the URL to the logon screen of any ITS application for that purpose, because this might lead to the userlogging on again.

Februar/2002 37


Window Name Input

Defining Memory Configuration

(SH/AI/ADM)

If you select Configuration for productive environments, the ITS isoptimized for performance with a large number of concurrent users,and sized for a server with a minimum of 512 MB of physical memory. This configuration is suitable for production systems.

If you select Minimize memory usage, the ITS is optimized forperformance with a small number of concurrent users, and sized for a server with a minimum of 128 MB of physical memory. This configuration is suitable for development and test systems whereperformance is not critical. It is primarily intended to meet the needsof developers installing the ITS on their local machines.

Defining Number of AGate Processes:

(SH/AI/ADM)

Is displayed only, if you have chosenConfiguration for productiveenvironments (seeabove)

This value defines the maximum number of AGate processes(MaxAGates) for the ITS instance you are installing. You should choose a number higher than 1 if at least one of the followingconditions applies:

- The number of concurrent sessions is likely be higherthan 400.

- The expected memory allocation for the AGate is morethan 2 GB.

For more information about AGate tuning, see the ITS Tuning andTroubleshooting Guide.

Installing the ITSWatchdog Service

(ADM)

You can decide whether to install the ITS Watchdog tool or not.

The ITS Watchdog is a simple Windows service running on a WGate host (see ITS with LDAP and WLBS [page 22])

If you want to use Watchdog on your WGate host you must installit also on the AGate host.

38 Februar/2002


Window Name Input

DefiningConnectionParameters (1)

(SH/AI/ADM)

SAP system: Enter the exact name of the SAP system (3-charactername of the SAP system) with which the ITS instance is meant to communicate

Client to be used: Global client used by the ITS to log on to the SAP system.

R/3 Username: Global user used by the ITS to log on to the SAP system.

R/3 Password: Enter password of the user

For security reasons, SAP recommends that you restrictaccess to services as much as possible.

- If you enter logon information here, the ITS places thevalues in the global service file and uses them as defaults for all services. This means that users can startany service without having to provide logon information.

- If you enter partial or no logon information here, the ITS attempts to get the missing details from the relevant service-specific service file, or sends a logon page for the user to complete.

You should only enter logon information here if you are providing access to a very restricted number of serviceswhere security is not critical. It is difficult to monitor large numbers of services covered by one global user.If you need to define a global user for some services, do one of the following:

- Use ITS Administration to specify the logon information.Enter the global user values that should apply to severalservices in the global service file. For all other services,enter the logon information in the service-specificservice files. This also encrypts the password.

- Enter the global user values that apply to several services above. For all other services, enter the logon information in the service-specific service files using the grid control editor in the SAP@Web Studio. This also encrypts the password.For more information about the SAP@Web Studio, see SAP@Web Studio Installation Guide [page 103].

Februar/2002 39


Window Name Input


(SH/AI/ADM)

There are two ways of defining a connection to the SAP system:

¶ Indirectly using the SAP system message serverSelect Connect to the SAP system via Message Server to guarantee a balanced load on all application servers runningthe selected SAP system. This is the default option, and should be used for all production systems.

Message Server:Host name of the SAP system message server as it is knowneither by the domain name server (DNS) or the SAProuter.

Message Server Port:Port number on which the message server is listening. Neededonly if you do not specify a SAProuter (see SAP Router Stringbelow).

If a port number is displayed, do not change it.

If 0 is displayed, you must enter the correct port number. You will find the port on your message server host by searching for the string sapms<SAPSID> <portnumber> in file services(default path C:\WINNT\system32\drivers\etc).

where <SAPSID> is the three-character long message server

system ID (SAP system name).

¶ Directly using a single application serverSelect Connect to the SAP system via Application Server for development systems only, where performance considerationsare less critical.

Application Server:Host name of the SAP system application server.

System Number:System number of application server.

¶ Additionally, you can also specify a SAP Router String if required.

The syntax used is: /H/<router>/S/<service>

router is the host name of an SAProuter and service is either

the service name or the port number of the SAProuter service.

If sapdp99/S/service is missing, sapdp99 is used as the

default service name.

To define more than one SAProuter, you can concatenate the strings in the same order the routers connect the AGate host to the SAP system. If no SAProuter is used to connect to the SAP system, leave this field blank. If there is a valid saproute.ini file in the Windows directory, you can use the button next to the SAP Router String field to get a list of SAProuters known to thismachine

40 Februar/2002


Window Name Input

Defining AGatePorts

(SH/AI/ADM)

ITS AGate port numberA free port number of your host is displayed, but you can enteranother free port.


Defining a LoginGroup

(SH/AI/ADM)

The following screen is displayed only, if you have chosen a valid message server and either a valid port number or SAProuter (otherwise SAPinst completes the installation, see next step).

If SAPinst can connect to the specified message server you will receive a list of existing Login Groups.

Otherwise you have to enter the Login Group manually. Be aware that the names of the login groups are case sensitive.

Defining AGateConnectionParameters

(WI)

¶ IP Name or IP address: This is the AGate host name or address known to the domain name server (DNS).

¶ ITS Manager port number

Here you must enter the port number as specified on the AGate host in the file


where <drive> is the system's hard drive and <winnt> is

your Windows 2000 directory on the AGate host.

To get the correct value, find the port number for the port sapavwmm_<virtual ITS>.

¶ ITS AGate port number

This is the port number on the AGate host that AGate is listening on.

Here you must enter the port number as specified on the AGate host in the file


where <drive> is the system's hard drive and <winnt> is your Windows 2000 directory on the AGate host.

To get the correct value, find the port number for the port sapavw00_<virtual ITS>.

Defining AGateProcesses (WI)

You should choose Yes if the corresponding AGate is configuredto run multiple processes. That is, during the AGate installation,you have chosen Configuration for productive environments (in window Defining Memory Configuration) with MaxAGates > 1 (inwindow Defining Number of AGate Processes).

ITS release notes Decide wether you want to read the release notes.

Februar/2002 41


Window Name Input

Rebooting

Appears only for the first installedITS instance of the host.

You must reboot the system, otherwise you neither can start the first installed ITS instance nor install an additional instance on this host.

Starting Instanceafter Installation

(SH/AI/ADM)

Appears only if installing an additional ITS instance on the host.

Choose Yes, if the system should start the ITS instanceautomatically after the installation.

Choose No, if not.

42 Februar/2002


2.3.1.2 Installing an ITS instance on Windows

Use

If you install an ITS instance with SAPinst for the very first time on a host, you have to startSAPinst once from the Server Components CD-ROM.

Afterwards, you can use the Start Menu to install your ITS instance(s): Installing an ITSInstance on Windows [page 47]

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 Monitoring a RemoteInstallation [page 93].

Procedure

1. Log on to your host as user with administrator rights.

2. Insert the Server Components CD-ROM in your CD drive.

3. Run Setup.cmd from the following path:

<CD drive>\ITS\NT

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. Copy directory ITS\NT from the Server Components CD-ROM to

your local hard disk.

b. In file ITS\NT\Setup.cmd search for the following string: .\sapinst.exeSAPINST_CONTROL_URL=control_bootstrap.xml

c. Append SAPINST_DIALOG_PORT=<port> to this string:.\sapinst.exeSAPINST_CONTROL_URL=control_bootstrap.xmlSAPINST_DIALOG_PORT=<port>

where <port> is an unused port on your host.

For example, if you enter 60000 as <port>, SAPinst uses the ports

60000 and 60001d. Run Setup.cmd from your local hard disk.

SAPinst asks if you want to perform a Standard or Custom installation.

If you chhose custom installtion, you can define:

- Installation directory for the SAPinst

Every ITS instance must have its own separate SAPinst installation directory every time you start SAPinst. That is, the installation directory is created for this specific ITS instance with important log and command files, that may be useful even after an successful instance installation. You can choose any name for the installation directory. In this documentation,

<SAPinst_INSTDIR> refers to the installation directory.

Februar/2002 43


- SAPinst folder in the Start menu

- Connection parameters (hostname and port number) to connect to your remotehost(s). For more information on remote installation, see Monitoring a Remote Installation [page 93].

The Start menu entry (and the connection parameters) are used to generate unique start menu entries. For example:You enter the following during the installation:Start menu entry: ITS InstallationThen SAPinst creates the following start menu:StartĄ ProgramsĄ ITS Installation Ą …

4. Choose Next.

The system now

- Copies SAPinst to your <SAPinst_INSTDIR> and creates the start menu entries.

- Starts automatically SAPinst and displays the Welcome screen.

If you are asked to perform a reboot, choose Reboot now and then OK. The system reboots and SAPinst starts automatically the Welcome screen.

5. Select ITS Installation on Windows and choose Next.

You must now agree to the SAP License Agreements for STLport.

A CD Browser dialog may be displayed.This dialog only appears if the system wants to check or cannot find the file LABEL.ASC containing the ITS_Software label. The default path is: <Server Components CD>/ITS/ITS_SOFTFor more information on the CD Browser dialog, see Handling the CDBrowser Dialog [page 99].

6. The next steps depend on the following situations:

¶ If you install the ITS for the first time on this host, the following two windows are displayed (otherwise SAPinst omits the dialogs):

- Accepting ConditionsYou must accept the conditions

- Defining SAP ITS Installation Directory

Enter your SAP ITS installation directory (<ITS_InstDir>).

¶ 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 toupgrade the whole ITS (otherwise SAPinst omit this dialog):

- Checking ITS VersionIf you choose to refresh the ITS, SAPinst will upgrade the ITS (if a lower releaseis installed) or refresh the installed version (suitable if the already installedversion 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 start SAPinst again.

If you choose to install another instance, SAPinst creates an additional instance on this host, keeping the already installed ITS release.

44 Februar/2002


¶ If you have already installed a higher ITS version on this host, the following screenappears, asking you whether to install only another instance or to downgrade the ITS from the current SAPinst:

- Checking ITS VersionDowngrading an ITS version may be suitable if you have installed a more recentITS, 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.

7. Follow the instructions in the SAPinst dialogs (see section Input for the Installation [onpage 36])

If you have entered all required information during the input phase, SAPinst starts the installation and displays installation progress during the processing phase.

If an error occurs during the input phase, SAPinst:

- Stops the installation.

- Displays a dialog that informs you about the error.You can now directly view the log file by choosing View Logs.Finally you must abort the installation with O.K. and try to solve the problem.

If an error occurs during the processing phase, SAPinst:


- Displays a dialog that informs you about the error.You can now:

- Directly view the log file by choosing View Logs.

- Try to solve the problemSee SAPinst Troubleshooting Guide at: http://service.sap.com/sapinstfeedback

- Retry the installation by choosing Retry.

- Abort the installation by choosing O.K.

See also Continuing an Interrupted Installation [page 93]

Februar/2002 45


Result

A successful ITS instance installation creates the following Windows services:

Service name Description

ITS Manager - <name of virtual

instance>

ITS service for this specific virtual instance installation, if selected

ITS Manager – ADM ITS Administration, if selected

ITS Watchdog ITS Monitoring tool, if selected during the ITS Administration installation.

IAC Object Receiver (IACOR) Automatically installed with the ITS.

The following menu entries are created:

Start Menu Entry

StartĄ Programs Ą<menu_entry>Ą

Description

Prepare New Installation Prepares SAPinst to install an additional instance on thishost.

Current log and command files are copied to a backupdirectory (under the current SAPinst directory) indicating the date and time of the backup:<SAPinst_Dir>\log<month>_<date><time>

Remove SAPinst Files Deletes the whole SAPinst installation directory

SAPinst GUI Only relevant for a remote installation.Starts SAPinst GUI only. A further dialog then prompts you for parameters (host and port) to connect to the SAPinstserver host.

SAPinst Server only Only relevant for a remote installation.Starts SAPinst server only and waits for connection to the SAPinst GUI

SAPinst server with GUI Starts SAPinst server and SAPinst GUI. The Welcomescreen is displayed and you can perform the installation.

46 Februar/2002


2.3.1.3 Installing additional ITS Instances on Windows

Prerequisites

If you install an ITS instance with SAPinst for the very first time on a host, you have to start SAPinst from the Server Components CD-ROM: Run SAPinst on Windows [page43]

¶

If you want to install an ITS instance whereas another instance installation on this hostwas not completed successfully (and you want to continue the installation later), you must run SAPinst again from the Server Component CD to create a new installation directory for the SAPinst log and command files: Run SAPinst on Windows [page 43]

¶

For every additional ITS instance you want to install on a host (after the successfulinstallation of another instance), you must choose the following befor performing the installation : StartĄ ProgramsĄ <menu_entry>Ą Prepare New Installation

¶

¶ If you want to perform a remote installation, see Monitoring a Remote Installation [page 93].

You are logged on as ITS Administrator. ¶

¶ All other programs are closed.

Procedure

1. To start the installation choose StartĄ Programs Ą <menu_entry> Ą SAPinstserver with GUI.

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 run: <SAPinst_INSTDIR> and.\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.


The next steps are the same as described in the above section, beginning with step 5.

Februar/2002 47


2.3.2 Installation on Linux/Solaris

2.3.2.1 Input for the Installation on Linux/Solaris To prepare for the input phase of the installation, we recommend you to write down the information you have to enter before starting SAPinst. Having the required information readyin advance helps you avoid unnecessary delays and errors.

The following table shows the window names that will appear during the installationprocedure of the installation types: Single Host / Dual Host (AGate, WGate) / Administrationand their prompts that are required for the installation.

The akronyms indicate which window appears for which installation typ:

Acronym Installation Type

SH Single Host instance

AI AGate instance

WI WGate instance

ADM ITS Administration

Window Name Input

Defining Iacor Ports

(SH/AI/WI/ADM)

¶ Iacor input port numberUse the displayed default port number.

¶ Iacor output port numberUse the displayed default port number.

SelectingInstallation Mode

(SH/AI/WI/ADM)

¶ Typical. Runs your IACs and other applicationsSelect Typical to install your ITS instance for running applications except ITS Administration.

¶ Administration. Runs ITS AdministrationIf you want to install an ITS Administration or The ITS Watchdog tool, select Administration. Like any other ITS instance, the administration instance must run under its own dedicated ITS server.

For further information about all aspects of Windows Service after installation, see the ITS Administration Guide.

Installing a virtual ITS Instance

(SH/AI/WI)

Any name is valid, but enter a value that is meaningful to you. If you are connecting to an SAP system, SAP recommends you to use the name of the SAP system.

You can display the names of the instances already installed on this host in the dropdown list box. Only choose such a displayedinstance, if you want to override it.

SelectingInstallation Type

(SH/AI/WI/ADM)

Decide, whether to perform a Single Host or Dual HostInstallation. For a Dual Host installation you must first install the AGate (Application Side) on the AGate host and afterwards the WGate (Web Server Side) on the WGate host.

48 Februar/2002


Window Name Input

Defining ApacheParameters

(SH/WI/ADM)

Apatche Server Executable File (httpd)Enter the exact path and filename (httpd) of the apache web server executable (/usr/sbin/httpd, for example).

Directory of httpd.confEnter the exact path to the directory where the file httpd.conf is located (/etc/httpd, for example).

Selecting a WebServer Instance

(SH/WI/ADM)

The list displayed in this dialog depends on the Web server instances already created.

This dialog states also whether a Web server is already in use by an ITS instance.

Selecting the IACPackages

(SH/AI/WI)

Do the following:

- Select the IAC package(s) you want to install.

- In case of a dual host installation, the selected packagesfor the AGate and WGate hosts must be the same.

- You can select packages also by applying the packagepath by choosing Add Row.

Finally a confirmation box displays all selected packages.

For more information on choosing IACs see IAC Packages [page 22]

You can add IAC packages to an existing ITS instance later by running the ITS Package Manager[page 100]

Defining WebServer Parameters

(SH/AI)

Enter the URLs to access your Web Server.

Defining Log OffURL

(SH/AI)

Enter the URL that should be accessed, when the user logs off from the ITS application.

We recommend not use the URL to the logon screen of any ITS application for that purpose, because this might lead to the userlogging on again.

Defining Memory Configuration

(SH/AI/ADM)

If you select Configuration for productive environments, the ITS isoptimized for performance with a large number of concurrentusers, and sized for a server with a minimum of 512 MB of physical memory. This configuration is suitable for productionsystems.

If you select Minimize memory usage, the ITS is optimized forperformance with a small number of concurrent users, and sizedfor a server with a minimum of 128 MB of physical memory. Thisconfiguration is suitable for development and test systems whereperformance is not critical. It is primarily intended to meet the needs of developers installing the ITS on their local machines.

Februar/2002 49


Window Name Input

Defining Number of AGate Processes:

(SH/AI/ADM)

Is displayed only, if you have chosenConfiguration for productiveenvironments (see above)

This value defines the maximum number of AGate processes(MaxAGates) for the ITS instance you are installing. You should choose a number higher than 1 if at least one of the followingconditions applies:

- The number of concurrent sessions is likely be higherthan 400.

- The expected memory allocation for the AGate is morethan 2 GB.

For more information about AGate tuning, see the ITS Tuning andTroubleshooting Guide.


(SH/AI/ADM)

SAP system: Enter the exact name of the SAP system (3-charactername of the SAP system) with which the ITS instance is meant to communicate

Client to be used: Global client used by the ITS to log on to the SAP system.

R/3 Username: Global user used by the ITS to log on to the SAP system.

R/3 Password: Enter password of the user

For security reasons, SAP recommends that you restrictaccess to services as much as possible.

- If you enter logon information here, the ITS places thevalues in the global service file and uses them as defaults for all services. This means that users can startany service without having to provide logon information.

- If you enter partial or no logon information here, the ITS attempts to get the missing details from the relevant service-specific service file, or sends a logon page for the user to complete.

You should only enter logon information here if you are providing access to a very restricted number of serviceswhere security is not critical. It is difficult to monitor large numbers of services covered by one global user.If you need to define a global user for some services, do one of the following:

- Use ITS Administration to specify the logon information.Enter the global user values that should apply to severalservices in the global service file. For all other services,enter the logon information in the service-specificservice files. This also encrypts the password.

- Enter the global user values that apply to several services above. For all other services, enter the logon information in the service-specific service files using the grid control editor in the SAP@Web Studio. This also encrypts the password.For more information about the SAP@Web Studio, see SAP@Web Studio Installation Guide [page 103].

50 Februar/2002


Window Name Input


(SH/AI/ADM)

There are two ways of defining a connection to the SAP system:

¶ Indirectly using the SAP system message serverSelect Connect to SAP system via Message Server to guarantee a balanced load on all application servers runningthe selected SAP system. This is the default option, and should be used for all production systems.

Message Server:Host name of the SAP system message server as it is knowneither by the domain name server (DNS) or the SAProuter.

Message Server Port:Port number on which the message server is listening. Neededonly if you do not specify a SAProuter (see SAP Router Stringbelow).

If a port number is displayed, do not change it.

If 0 is displayed, you must enter the correct port number. You will find the port on your message server host by searching for the string sapms<SAPSID> <portnumber> in file etc/services

where <SAPSID> is the three-character long message server

system ID (SAP system name).

¶ Directly using a single application serverSelect Connect to SAP system via Application Server for development systems only, where performance considerationsare less critical.

Application Server:Host name of the SAP system application server.

System number:System number of application server.

¶ Additionally, you can also specify a SAProuter String if required.

The syntax used is: /H/<router>/S/<service>

router is the host name of an SAProuter and service is either

the service name or the port number of the SAProuter service.

If sapdp99/S/service is missing, sapdp99 is used as the

default service name.

To define more than one SAProuter, you can concatenate the strings in the same order the routers connect the AGate host to the SAP system.

If no SAProuter is used to connect to the SAP system, leave this field blank.

Februar/2002 51


Window Name Input

Defining AGatePorts

(SH/AI/ADM)



Defining a LoginGroup

(SH/AI/ADM)

The following screen is displayed only, if you have chosen a valid message server and either a valid port number or SAProuter (otherwise SAPinst completes the installation, see next step).

If SAPinst can connect to the specified message server you will receive a list of existing Login Groups.

Otherwise you have to enter the Login Group manually. Be aware that the names of the login groups are case sensitive.

Defining AGateConnectionParameters

(WI)

¶ IP Name or IP address: This is the AGate host name or address known to the domain name server (DNS).

¶ ITS Manager port number

Here you must enter the port number as specified on the AGate host in the file \etc\services

To get the correct value, find the port number for the port sapavwmm_<virtual ITS>.

¶ ITS AGate port number

This is the port number on the AGate host that AGate is listening on.

Here you must enter the port number as specified on the AGate host in the file etc\services

To get the correct value, find the port number for the port sapavw00_<virtual ITS>.

Defining AGateProcesses (WI)

You should choose Yes if the corresponding AGate is configuredto run multiple processes. That is, during the AGate installation,you have chosen Configuration for productive environments (in window Defining Memory Configuration) with MaxAGates > 1 (inwindow Defining Number of AGate Processes).

ITS release notes Decide wether you want to read the release notes.

Starting Instanceafter Installation

(SH/AI/ADM)Currently, an ITS instance cannot be startedautomatically after the installation. How to, see section 1.3.2.3 below.

52 Februar/2002


2.3.2.2 Installing an ITS Instance on Linux/Solaris

Use

This procedure tells you how to to install an SAP ITS instances on released UNIX platforms.

Prerequisites

¶ If you start SAPinst GUI on your host, your DISPLAY and JAVA_HOME environment

variables must be set correctly.

¶ This section describes a local installation. For more information on remote installation,see Performing a Remote Installation [Page 93].

Procedure

1. Log on to your installation host as user root.

2. Mount the Server Components CD.

Mount the CD locally.We do not recommend that you use Network File System (NFS).

2. Create an installation directory for SAPinst with mode 777:

mkdir <SAPinst_INSTDIR>

chmod 777 <SAPinst_INSTDIR>

Each ITS instance must have a separate <SAPinst_INSTDIR> on a

common host.

3. Change to <SAPinst_INSTDIR> and run the script INSTALL from the mounted Server

Components CD:

cd <SAPinst_INSTDIR>

<Server Components CD>/ITS/UNIX/LINUX_32/INSTALL

SAPinst uses the ports 21212 and 21213 during the installation for communication with SAPinst GUI. If one of these ports is already used by another service you must start SAPinst as follows: Server Components CD>/ITS/UNIX/LINUX_32/INSTALL --port <free_port_number>where <free_port_number> and <free_port_number>+1 are unused

port number.For example, if you enter 6000 as <free_port_number>, SAPinst uses the ports 6000 and 6001.

SAPinst is now copied to your <SAPinst_INSTDIR> and SAPinst GUI starts

automatically by displaying the Welcome screen.

Februar/2002 53


4. Select ITS Installation on UNIX platforms and choose Next.


A CD Browser dialog may be displayed.This dialog only appears if the system wants to check or cannot find the file LABEL.ASC containing the ITS_Software label. The default path is: <Server Components CD>/ITS/ITS_SOFTFor more information on the CD Browser dialog, see Handling the CDBrowser Dialog [page 99].

5. The next steps depend on the following situations:

¶ If you install the ITS for the first time on this host, the following two windows are displayed (otherwise SAPinst omits thse dialog):

- Accepting ConditionsYou must accept the conditions

- Determining SAP ITS Installation Directory

Enter your SAP ITS installation directory (<ITS_InstDir>).

¶ 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 toupgrade the whole ITS (otherwise SAPinst omit this dialog):

- Checking ITS VersionIf you choose to update the ITS, SAPinst will upgrade the ITS (if a lower releaseis installed) or refresh the installed version (suitable if the already installedversion 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 start SAPinst again.

If you choose to install another instance, SAPinst creates an additional instance on this host, keeping the already installed ITS release.

¶ If you have already installed a higher ITS version on this host, the following screenappears, asking you whether to install only another instance or to downgrade the ITS from the current SAPinst:

- Checking ITS VersionDowngrading an ITS version may be suitable if you have installed a more recentITS, 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.

6. Follow the instructions in the SAPinst dialogs (see section Input for the Installation on Linux/Solaris [page 48]).

After you have maintained all input parameters, SAPinst starts the installation and displays installation progress during the processing phase. If the installation wassuccessful, the message The installation finished successfully. is displayed.

54 Februar/2002


If an error occurs during the input phase, SAPinst:

- Stops the installation

- Displays a dialog that informs you about the errorYou can now directly view the log file by choosing View Logs.Finally, you must cancel the installation with O.K. and try to solve the problem.

If an error occurs during the processing phase, SAPinst:


- Displays a dialog that informs you about the error.

You can now:

- Directly view the log file by choosing View Logs.

- Try to solve the problem (see SAPinst Troubleshooting Guide at: http://service.sap.com/sapinstfeedback)

- Retry the installation by choosing Retry.

- Cancel the installation by choosing O.K.

See also: Continuing an Interrupted Installation [page 93]

Februar/2002 55


2.3.2.3 Starting and stopping an ITS Instance on Linux/Solaris

Starting the Instances

You must start the instances manually after the installation:

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. Start the instances:

- If you want to start ITS Administration

<ITS_InstDir>/programs/mmanager -v ADM -c <ITS_InstDir>/config &

- If you want to start all AGates of a virtual Instance (<VITS>):

<ITS_InstDir>/programs/mmanager -v <VITS> -c <ITS_InstDir>/config &

- If you want to startl a single AGate instance of a virtual Instance (<VITS>):

<ITS_InstDir>/programs/agate -v <VITS> -c <ITS_InstDir>/config &

- If you want to start a WGate instance:

<apache_serverroot>/bin/apachectl start&

Stopping the Instances

kill -2 `cat <ITS_InstDir>/<VITS>/traces/MManager0_<VITS>/.pid`

kill -2 `cat <ITS_InstDir>/<VITS>/traces/AGate0_<VITS>/.pid`

(Do not forget the apostrophes!)

56 Februar/2002


2.3.3 Checking the ITS Installation Prerequisites

You have performed either a single host installation or a dual host installation.

Procedure

When you have completed the ITS installation, you should do the following:

¶ Check that the installation was successful.

¶ Ensure that the SAP system is available.

¶ 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 ITScomponents (WGate and AGate) and follow the procedures in the tables below according to the installation type.

Check Procedure

On the Web host, check that the Web server status

Windows 2000 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 StartupType columns are set to Started and Automatic.

UNIX Server

For more information on starting and checkinginstances see SAP Note 526835, section UNIX:Starting Instances.

Februar/2002 57


Check Procedure

On the Web host, check that the WGate component is present.

Windows 2000 Server

The location depends on the Web server you are using:

¶ If you are using the Microsoft Internet Information Server (IIS), you can find WGate.dll in

<ITS_InstDir>\WGateIIS.

¶ If you are using the Netscape EnterpriseServer (NES) or the iPlanet Web Server, you can find WGate40.dll or WGate41.dll in

the subdirectory scripts of the Web server’s

root directory.

¶ If you are using the Apache HTTP Server, you can find apWGate136.dll or apWGate1320.dll or apWGate122.dll in

<Apache installation directory>:\modules

where <release> stands for the Apache release you are using, for example apWGate<1312>.dll for Apache release 1.3.12.

To see .DLLs files, make sure that your Windows

Explorer displays all file types.

UNIX Server

¶ If you are using the Apache HTTP Server, you can find apWGate136.so or apWGate1320.so or apWGate122.so in

<Apache installation directory>:\modules

Both Operating Systems

¶ Check if the file wgate.conf is on the followinglocation (depending on your Web server):

- Apache, iPlanet, and Netscape EnterpriseWeb Server: <WebServer_InstDir>/conf

- Internet Information Server: <WebServer_InstDir>/programs

¶ Check if the following files exist under<ITS_InstDir>/config:

- ItsRegistryWgate.xml

- ItsRegistry<ITS_instance_name>.xml

58 Februar/2002


Check Procedure

On the AGate host, check that theITS Manager is started and that startup is set to automatic.

Windows 2000 Server

1. Choose Start Programs Administrative

Tools Computer Management.

2. Choose Services and Applications.

3. Choose Services.

4. Find the ITS Manager in the list of Servicesand check that the values in the Status and Startup Type columns are set to Started and Automatic. The ITS Manager is listed as ITSManager - <ITS instance>..

UNIX Server

For more information on starting and checkinginstances see SAP Note 526835, section UNIX:Starting Instances.

Both Operating Systems

Check if the following file exist under <ITS_InstDir>/config:

- ItsRegistry<ITS_instance_name>.xml

Is the SAP system Available?If you have the SAP GUI for Windows 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 SAPinst, you can find services under:

<ITS_InstDir>\<ITS instance>\services

If you have connected the ITS to a SAP system of Basis Release Ó 6.10 keepin mind that you must publish the services via the IACOR to the ITS host [page 65].

Februar/2002 59


3. Log on to the SAP system via the SAP GUI for Windows and start the transaction

<transaction>.

- To log on to the SAP system, you use a normal SAP user, as specified during SAPinst and entered in the global service file, or as specified in the service-specificservice file

- 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 one of the services installed by the SAPinst from a Web browser:

1. Choose a service <service>.srvc from the installation directory of your ITS instance.

Unless you specified a different path during SAPinst, you can find services under:

<ITS_InstDir>\<ITS instance>\services

2. Start a Web browser.

3. Enter the relevant URL:

The syntax for starting an ITS service from a Web browser via a URL is:

<protocol>://<server>:<port>/<execdir>/<WGateexec>/<service>/!

For full details about what values to enter for these URL elements, see Starting an ITS Service from a Web Browser [page 61].

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 logonscreen for the service <service>.

For information about troubleshooting the ITS installation, see the ITS Tuning andTroubleshooting Guide.

60 Februar/2002


2.3.4 Starting an ITS Service from a Web Browser

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>/<execdir>/<WGateexec>/<service>/!

Here is a summary of the URL elements:

URL Element Description Example Value(s)

<protocol> Transport protocol. http or https

<server> Web server name. MyWebServer

<port> Port number on which your Web server islistening.

81

The default value is 80.

<execdir> Directory location of WGate executable unlessredefined in WGate.conf.

scripts

Used for Microsoft IIS, Netscape NES and Apache.

<WGateexec> WGate executable.

This is a .dll (Windows) or .so (Unix) file.

WGate

<service> Name of ITS service to be started. webgui

! Final element.

This is an integral part of the URL and mustbe included.

!

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 onport 80.

In this case, the port number is omitted, because 80 is the default

value.

Februar/2002 61


2.4 Post-Installation Activities

2.4.1 IAC Publishing with the IACOR on Windows

Purpose

This process describes how to configure the IAC Object Receiver (IACOR) and to publish theIACs.

Prerequisites

You cannot use the IACOR for SAP systems with a Basis Release lower than 4.6C.

You have installed the ITS [page 36], because the IACOR files are automatically installed at the same time as the Internet Transaction Server (ITS).

Process Flow

1. Start the IACOR [page 63]

2. Configure the IACOR [page 65]

3. Publish the IACs [page 70]

4. Manage the IACOR [page 71]

62 Februar/2002


2.4.1.1 Starting the IACOR

Starting the IACOR

1. Log on to the ITS host as ITSadm.

2. Start IAC Object Receiver Administration from the Windows Service directory

<ITS_InstDir>\programs

and double-click IacorAdmin.exe.

If you are setting up the IACOR for the first time, you see a dialog boxcontaining the message Failed to attach to IACOR service – service is not running. You can ignore this by choosing OK.

The following dialog appears:

Februar/2002 63


3. Choose Options.


4. Choose Register.

You see a dialog box displaying the successful installation.

5. Choose OK.

The system now generates a IACOR service for Windows 2000.

6. To return to IAC Object Receiver Admin, choose OK.

7. To start the service choose Start.

- When the service is running, the IACOR icon in the top right corner displays a green “O“ symbol.

- When the service is stopped, the IACOR icon in the top right corner displays a red“O“ symbol.

Result

The IACOR service is started. You can now configure the IACOR [page 65].

64 Februar/2002


2.4.1.2 Configuring the IACOR

Configuring the IACOR

When the IACOR service is running, you have to set up connections to the SAP systemsfrom which the ITS files should be received.

You have to enter connections for the ITS AGate side (which handles service files, HTML templates, flow files, and language resource files), and the ITS WGate side (which needsaccess to the MIME files) separately.

Prerequisites

You have started the IACOR service.

Procedure

To configure the IACOR, do the following in IAC Object Receiver Administration:

1. Log on to the ITS host as ITSadm.

In case of a dual host installation you have to perform the steps on the AGate as well as on the WGate.

2. Start IAC Object Receiver Administration from the Windows Service directory

<ITS_InstDir>\programs

and double-click IacorAdmin.exe.


Februar/2002 65


3. Choose New.

The Add New Site Connections dialog box appears:

Enter the connection information in the following fields:

Field Description

ITS Instance Name of virtual ITS instance to which ITS files should be published.

If you have entered the virtual ITS instance the next fields will be filled automatically after pressing tabulatur key.

Check these entries.

Gateway Host Name of host that provides the RFC gateway for the source SAP system.

If you want the gateway host to be determined automaticallywhen registering the connection with a SAP system in the next dialog, leave the default <auto>.

Gateway Service Service port of the RFC gateway.

The naming convention is sapgw<SAP system number>. For

example, sapgw00.

If you want the gateway service to be determined automaticallywhen registering the connection with a SAP system in the next dialog, leave the default <auto>.

66 Februar/2002


Sitename For SAP systems with Basis Release 6.10 or higher, a siteincludes one or more servers that form a single publishingdestination receiving a common set of ITS files.

The IACOR generated RFC destinations are automaticallyassigned to a site that corresponds to the installed ITS instance. The naming convention of the site is:

<hostname AGATE>_<SID> or <hostname WGATE>_<SID>

where SID is the system ID of the SAP system the ITS instanceconnects to (for example AT3).

By defining ITS sites consisting of several ITS AGate and ITS WGate instances, you can deploy IAC files in your ITSlandscape without having to publish them to each and every ITS instance separately. Using ITS sites also helps to avoid problems when someone forgets to update an ITS WGate or anITS AGate in a Dual Host installation.

ITS (AGate) Destination Path

Destination for the files to be received by the ITS host. The default path is:

<ITS_InstDir>\<ITS instance>

If you configure the IACOR for a WGate (dual hostinstallation) you have to deselect this field.

Web Server(Hosting WGate)

Destination for the MIME files to be received by the Web server.The default path depends on the Web server software (see: ITSFile Types and Locations [page 117]).

When entering the destination directory for MIME objects makesure to use the right directory. The default setting is the root directory of the "Default" Web Server instance of a Microsoft IIS. In most cases this directory does not suit your installation.

If you configure the IACOR for an AGate (dual hostinstallation) you have to deselect this field.

When specifying the ITS and Web server destination paths, do notspecify remote machines and share names, even if the shares are on the same machine. Do not use UNC (Uniform Naming Convention)paths. Doing this results in an access error, because IACOR logs inwith a system account that does not have any network access.

Februar/2002 67


4. Choose OK.

You see the Create Site Destinations at R/3 dialog box, for example:

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 Destinationrequires you to log on to the source SAP system.

a. In the R/3 Server box, specify the SAP system Server.

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:

- The Group is the name in square brackets after the SAP system name.

- You can find details such as System Number and SAP Router String by right-clicking on the SAP system name and choosing Properties.

- 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, choosingGroups and entering the SAP system name in field System Id.

68 Februar/2002


b. In the User Login box, specify a SAP system logon information.

You must enter the data of a user that has authorization to create RFCdestinations in the relevant SAP system.

5. Choose OK.

Result

The IACOR now configures a RFC connection on the SAP system and states the connection in the IAC Object Receiver Admin screen.

¶ 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>_ITSIACOR_<IACOR host name>_<ITS instance>_WWW

¶ You can also find the RFC program ID assigned to the IACOR connection in the IACOR log (<ITS_instDir>\ iacor\traces); it is printed in square brackets when the connection is requested:

For example:Wed Sep 08 23:30:56 1999 - ITS_WWW<-itshost:

Connect: ITS receiving from itshost [IACOR_PAL100043_ITS_WWW]

See also:

Managing the IACOR [page 71]

Februar/2002 69


2.4.1.3 Publishing the IACs from a SAP system

Use

Use this procedure to publish IACs from a new installed SAP system of Release Ó 4.6C.

You can publish IACs since SAP systems of Release 4.6C

Do not use this procedure if you are upgrading to a SAP system of Release Ó 6.10. In thiscase, refer to topic Meeting the Requirements for the SAP Internet Solutions in the corresponding SAP system upgrade guide.

Prerequisites

You have started [page 63]and configured the IACOR [page 65] 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.


c. Choose the tab Internet Transaction Server.

d. Choose the option On Selected Site under the tab Publish.

e. Use the input help to select the site where you want to publish, and confirm.

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 unsing the checkboxes and thenchoose Publish.

The publishing process can take several minutes. An appropriate message appears if the publishing process was successful.

h. If you have configured multiple sites where you want to publish, repeat steps b. to g.

Result

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 61].

A log box is displayed after the publishing procedure.You can also watch the publishing progress in the IAC Admin screen on the ITS host.

70 Februar/2002


2.4.1.4 Managing the IACOR When you have started the IACOR service, choose Refresh to attach IACOR Admin to the service, or close and restart IACOR Admin. Then, the IACOR icon in the top right cornerdisplays a green “O“ symbol.

If IACOR Admin cannot find the IACOR service running, the IACOR icon in the top right corner displays a red “O“ symbol.

If the IACOR service is not running, all connections are flagged with a blue question mark.

You cannot run more than one instance of IACOR Admin at the same time.

IACOR Log FileAll actions, connection states, events, errors and received files are logged in the IACOR log file called Iacor.log, which resides in <ITS_InstDir>\iacor\traces.

To enable / disable RFC logging, use the Options function in IAC Object Receiver Admin.

Broken ConnectionsIf a connection is broken, IACOR automatically attempts to reestablish it. If this fails, IACORattempts to reestablish broken connections every 15 minutes.

To change this interval, use the Options function in IACOR Admin.

Broken connections are flagged with a red status icon.

Deleting the RFC DestinationsIf you delete the connections in the IACOR Admin tool, the corresponding RFC destinationconfiguration in the SAP system (SM59) will then be automatically deleted too.

Make always sure that all connections and RFC destinations you do not need anymore (maybe if the ITS is deactivated or uninstalled), are removed in the SAP system in order to avoid problems.

You can also delete RFC destinations by using transaction SM30 and maintain the table IACORDES and table ITSSITES (as of Release 6.10 or higher).

Februar/2002 71


2.4.2 Watchdog Configuration (Windows only) Purpose

This topic describes configuration procedures for the use of Watchdog regarding several scenarios:

¶ Configuring Watchdog for Load Balancing Service [page 73]

¶ Registering ITS in an LDAP Directory [page 77]

¶ Monitoring with Watchdog [page 80]

For more information about Watchdog, see ITS with LDAP and WBLS [page 22].

See also:

Additional Information [page 85]

Prerequisites

You have installed The ITS Watchdog service on the ITS host (AGate and WGate) during the SAPinst.

72 Februar/2002


2.4.2.1 Configuring Watchdog for WLBS

Use

To achieve high availability and load balancing via WLBS you have to:

a. Install WLBS on every WGate host.

b. Adapt the service its_ping.srvc.

c. Configure Watchdog in the Windows registry.

Procedure

Installing WLBS

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 BalancingTechnical Overview.

1. Open the network properties dialog for the network adapter and enable Network LoadBalancing.

Februar/2002 73


2. Configure the Properties of Network Load Balancing.

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 Remotecontrol.

3. Enter the host’s ordinary IP address as Dedicated IP address, specify the Subnet maskand 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.

74 Februar/2002


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:

Februar/2002 75


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 usefulcommands are:

- Wlbs enable <Port>

- Wlbs disable <Port>

- Wlbs query <Cluster IP address>

- 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 hardwareor network failures.

Adapting the service its_ping.srvcTo test an URL, ITS Watchdog utilizes an ITS service called its_ping. An URL is consideredto 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.srvcservice 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>

~password <your_password>

~language <language>

We recommend encrypting the password in this service file by using SAP@Web Studio or ITSAdministration.

Configuring Watchdog in the Windows registrySee Registry Configuration [page 82].

76 Februar/2002


2.4.2.2 Registering ITS in an LDAP Directory

Use

To register ITS in a SAP LDAP environment you have to:

a. Adapt the service file ldapreg.srvc.

b. Enable Watchdog for LDAP registration in the Windows registry.

c. Adapt the service its_ping.srvc.

d. Enable LDAP registration for the SAP system.

e. Install the latest SAP schema extension on the LDAP Server

f. Update registration tool ldapreg.exe on the SAP system executable directory.

g. Transport the function module WWW_LDAP_REGISTER_ITS into the SAP systemby applying a Support Package

Procedure

Adapting the service file ldapreg.srvcThe 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 willstart 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)



_FUNCTION WWW_LDAP_REGISTER_ITS

Februar/2002 77


Adapting the service its_ping.srvcTo 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.srvcservice 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>



WE recommend encrypting the password in this service file by using SAP@Web Studio or ITSAdministration.

78 Februar/2002


Installing the latest SAP schema extension on the LDAP ServerThe 6.20 SAP schema extension already includes the necessary information for registeringITS.

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: ITS registration in LDAP directories.

For example, the following information about ITS will be stored in the directory:

SAP-R3-ITSInstance(cn=<ITSInstanceName>_<Hostname>)

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-OperatingSystem

(I)Windows 2000 5.0 2195 Service Pack 1

String SAP-R3-WebServer(I)

iis

String(multivalued)

SAP-R3-URLs(I)

http://pcintel8.nt5.sap-ag.de:80/scripts/WGate

https://pcintel8.nt5.sap-ag.de:443/scripts/WGate

Mandatory:

String SAP-R3-ITSRelease(I)

46D patch 3000

String SAP-R3-Description

String(multivalued)

SAP-R3-AdminURLs(I)

http://pcintel8.nt5.sap-ag.de:81/scripts/WGate/adminremote/!

https://pcintel8.nt5.sap-ag.de:82/scripts/WGate/adminremote/!

Optional:

String SAP-R3-COMCLSID(I)

{a02a29a8-f272-44e3-9d9c-c4df1e892f10}

Further InformationFor more information refer to SAP Note 379691.

This note contains the most recent information how to enable the ITS LDAP registration for46B/C/D SAP systems.

Make sure that you have the most recent version of this note. You can find the SAP Notes in SAP Service Marketplace at: http://service.sap.com/notes.

Februar/2002 79


2.4.2.3 Monitoring with Watchdog

Use

You can use watchdog also (beneath LDAP and WLBS functionality) as a simple monitoringtool using a Web Browser.

In addition, it displays information about WLBS, if configured (see: Configuring Watchdog forWLBS [page 73])

Prerequisites

This feature is only available using the Microsoft Internet Information Server as Web Server.

Procedure

By using the URL http://<wgatehost>:<port>/sap/watchdog/watchdog.asp,you can monitor the ITS Watchdog status:

80 Februar/2002


Watchdog Heading Description

Instance ITS instance name

URL Basis URL of the instance

Status: enabled, disabled enabled, if URL and ITS instance are enabled else disabled

Availability: available,unavailable, available (not checked), unavailable (not

checked), not checked

available, if URL worked during the last test, else

unavailable.

If the URL is not checked by the ITS Watchdog (dependingon 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, disabling failed, enabled,

disabled, unchanged.

(if configured)

The value describes the last action performed by the service with respect to the corresponding WLBS port rule.

unchanged: means that the port status information is

considered unreliable and therefore The ITS Watchdoghas not changed the port rule status.

enabling failed / disabling failed: means that

execution of the port enabling or disabling command(defined by PortDisable and PortEnable; see RegistryConfiguration [page 82]) 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.

Februar/2002 81


2.4.2.4 Registry ConfigurationWatchdog can be configured in the registry underHKLM\System\CurrentControlSet\Service\ITS Watchdog\Parameters.

To activate registry changes The ITS Watchdog service must be restarted.

The ITS Watchdog offers the following features:

¶ Changes to the WGate configuration file of an ITS instance are detected automaticallywithout requiring the service to be restarted.

¶ The service does not monitor disabled ITS instances or disabled URLs and it does not check the “ADM” instance (see AdminInstance parameter).

¶ The service considers a port state as reliable if all related URLs have returned the same result during at least the last 2 trials (see Latency parameter).

¶ The service only enables/disables a port rule for reliable ports.

The following is an overview of the complete Watchdog registry settings (see next page):

82 Februar/2002


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:

- 0: Never

- 1: When the port information is reliableand the status has changed

- 2: Every time the port information is reliable

WLBSAutoDetect (default 1) Enables / disables automatic detection of WLBS:

- 0: If PortControl is enabled, ports areenabled and disabled even if no WLBS is available

- 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

¶ HKLM\SYSTEM\CurrentControlSet\Services\WLBS is found in the registry

¶ 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 theDCOM ITSWatchog.GetInstanceList method see: Additional Information [page 85]). Theservice does not recognize de-installation of WLBS without restarting the service.

Februar/2002 83


LDAP Entries

LDAPAutoRegister (default 0) Controls registration of the ITS instances in an LDAP directory

- 0: do no register

- 1: register

General Watchdog Entries

AdminInstance (default “ADM”) Specifies the name of the Windows Serviceinstance that should not be monitored.

TimeInterval (default 60) Specifies the time period in secs for testing the URLs.

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 returnedpage.

PageSize. (default 8192) Specifies maximum length used when searchingfor PagePattern.

MonitorLevel (default 1) Specifies which URLs are tested:

- 0: The first URL of each ITS instance

- 1: The first URL of each port of each ITS instance

- 2: All URLs of each ITS Instance

HttpTimeout (default 15000) Specifies the timeout in msecs for HTTPoperations during URL testing.

84 Februar/2002


2.4.2.5 Additional Information

Use

This topic describes

¶ The ITS Watchdog DCOM Interface (for development purpose)

¶ How to uninstall Watchdog

ITS Watchdog DCOM Interface

The ITS Watchdog provides an easy to use dual DCOM interface IITSWatchdog to accessstatus information and the WGate configuration.

Both monitoring tools (Active server page and R/3 MMC SnapIn) use this interface to accessThe ITS Watchdog service.

IITSWatchdog: GetInstanceListGet 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.

IITSWatchdog: ReadWGateConfig

Read WGate configuration for a given ITS instance. The file content is returned in a singlestring, lines are end with “\r\n”.

HRESULT ReadWGateConfig([in] BSTR instance,

[out] BSTR *filename,

[out] BSTR *text)

Return Values

S_OK

Februar/2002 85


IITSWatchdog: WriteWGateConfigWrite 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

86 Februar/2002


2.4.3 IAC Publishing with the IACOR on Linux

2.4.3.1 Configuring the IACOR on LINUX

Use

This section describes how to configure the IAC Object Receiver (IACOR) and to publish thepackages on Linux.

When the IACOR service is running, you have to set up connections to the SAP systemsfrom which the ITS files should be received.

You have to enter connections for the ITS (which handles service files, HTML templates, flow files, and language resource files), and the Web server (which needs access to the MIME files) separately.

For this, the IACOR must be started on a command line with special options.

Prerequisites

You cannot use the IACOR for SAP systems with a Release lower than 4.6C.

You have installed the ITS [page 48], because the IACOR files are automatically installed with the Internet Transaction Server (ITS).

Procedure

1. Start the IACOR service in directory /usr/itsadm/2.0/programs with the following command:

./iacor (or ./iacor & for running as background job)

2. Start the IacorCmd command script.

The following tables provide an overview of the command script, the commands and its parameters.

Command Script Usage

The script IacorCmd (default path <ITS_InstDir>/programs) provides a command

line interface for all configuration commands.

Usage:

Iacorcmd <command> [/<parameter>:<value>] [/<parameter>:<value>] [...]

Values have to be enclosed by quotes if they contain spaces, '<' or '>'.

Februar/2002 87


<command>s and parameters

add: Adds a connection so that IACs from a SAP system to the given virtual ITS

instance can be transferred.

MandatoryParameters:

Required value

Itsname Name of virtual ITS instance to which ITS files should be published.

Gwhost

Gwservice

gwhost: Name of host that provides the RFC gateway for the source SAP system.

gwservice: Service port of the RFC gateway. The namingconvention is sapgw<SAP system number>. For example, sapgw00

We recommend that you use the value "<auto>" for both parameters. This means that the systemdetects the required values automatically.

Desturlits

Desturlwww

desturlits: Destination for the files to be received by the ITS AGatehost. The default path is <ITS_installation_directory>/<ITS_instance-name>.

desturlwww: Destination for the MIME files to be received by the Web server (WGate host). The default path is <Apache_directory>/htdocs/sap/its/mimes

You must use both parameters if you configure the IACOR for a single host installation.

Appsrv

Sysnum

r3name

group

msgsrv

router

Do not use all parameters as some of them are alternatives to others.

You must use at least one of the following:

¶ Appsrv (hostname of the SAP system application server) and sysnum (SAP system number)

¶ r3name (name of your SAP system), group (Login group), andmsgsrv (hostname of the message server)

¶ r3name, group, and router (router string)

For more information, see the explanations in section Input for the Installation on Linux [page 48] (Window Name: DefiningConnection Parameters (1), Defining Connection Parameters (2),Defining a Login Group).

88 Februar/2002


MandatoryParameters:

Required value

client

r3user

r3password

Connection parameters for the SAP system

client: Client of the SAP system

r3user: A SAP system user

You must enter the data of a user that has authorization to create RFC destinations in the relevant SAP system.

r3password: Password for this user

Optionalparameters

Required value

gwrouterstr SAP Router String

You can find the SAP Router String in the SAP Logon of the corresponding host by right-clicking on the SAP system name and choosing Properties.

sitename For SAP systems with Basis Release 6.10 or higher, a siteincludes one or more servers that form a single publishingdestination receiving a common set of ITS files.

The IACOR generated RFC destinations are automaticallyassigned to a site that corresponds to the installed ITS instance. The naming convention of the site is:

<hostname AGATE>_<Sid> or <hostname WGATE>_<Sid>

where SID is the system ID of the SAP system the ITS instanceconnects to (for example AT3).

By defining ITS sites consisting of several ITS AGate and ITS WGate instances, you can deploy IAC files in your ITS landscapewithout having to publish them to each and every ITS instance separately. Using ITS sites also helps to avoid problems whensomeone forgets to update an ITS WGate or an ITS AGate in a Dual Host installation.

The sitename is created as <hostname>_<itsname> if not specified

language Two-digit abbreviation (EN for english, for example)

Example:

iacorcmd add /itsname:Q00 /gwhost:"<auto>" ...

Februar/2002 89


<command>s and parameters

modify: Modifies a connection: ITSAgate destination path / Web Server

destination path

Mandatory Parameters: Itsname / desturlits / desturlwww

Optional parameter: gwhost

For required values. See above

Example:

iacorcmd modify /itsname:Q00 /desturlits:"linuxpath"

Hint: You can chang the paths, but you cannot delete the paths.

delete: Deletes a connection

Mandatory Parameters: itsname / appsrv / sysnum / r3name / group / msgsrv / router

Optional parameter: gwhost

For required values. See above

Example:

iacorcmd delete /itsname:Q00 /appserv:"servername" ...

Result

The IACOR now configures an RFC connection at the specified host.

All the settings are stored in the file ItsRegistryIACOR.xml (default path: <ITS_InstDir>/config).

¶ 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>_ITSIACOR_<IACOR host name>_<ITS instance>_WWW

¶ You can also find the RFC program ID assigned to the IACOR connection in the IACOR log; it is printed in square brackets when the connection is requested:

For example:Wed Sep 08 23:30:56 1999 - ITS_WWW<-itshost:

Connect: ITS receiving from itshost [IACOR_PAL100043_ITS_WWW]

90 Februar/2002


2.4.3.2 Publishing the IACs from a SAP System

Use

Use this procedure to publish IACs from a new installed SAP system of Release Ó 6.10.

You can publish IACs since SAP systems of Release 4.6C.

Do not use this procedure if you are upgrading to an SAP system of Release Ó 6.10. In thiscase, refer to topic Meeting the Requirements for the SAP Internet Solutions in the corresponding SAP system upgrade guide.

Prerequisites

You have configured the IACOR on Linux [page 87] for the specific SAP system.

Procedure

3. Logon to the SAP system from which you want to publish the IAC.

4. Execute the report W3_PUBLISH_SERVICES (Transaction SE38).

a. Leave the fields Transport Request and Package empty and choose Execute.


b. Choose Workbench Settings.


c. Choose the tab Internet Transaction Server.

d. Choose the option On Selected Site under the tab Publish.

e. Use the input help to select the site where you want to publish, and confirm.

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 unsing the checkboxes and thenchoose Publish.

The publishing process can take several minutes. An appropriate message appears if the publishing process was successful.

h. If you have configured multiple sites where you want to publish, repeat steps b. to g.

Result

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 61].

A log box is displayed after the publishing procedure.

Februar/2002 91


2.5 Additional InformationPurpose

This topic describes how to

- Install additional ITS instances using the tool Package Manager.

- Repeate an ITS installation unattended

- Apply patches to the ITS

- Uninstall the ITS and ITS instances.

You should always perform instance maintenance and other administrationtasks 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 performadministration tasks after installation, see the ITS Administration Guide.

Information

SAPinst specific

¶ Monitoring a Remote Installation with SAPinst [page 93]

¶ Continuing an Interrupted Installation with SAPinst [page 93]

¶ Handling the CD Server Dialog [page 99]

SAP ITS specific

¶ Create additional ITS Instances [page 100]

¶ Repeat an ITS Installation unattended [page 100]

¶ Patch the ITS [page 101]

¶ Uninstall the ITS [page 102]

92 Februar/2002


2.5.1 SAPinst Specific Information

2.5.1.1 Continuing an Interrupted Installation As SAPinst does not abort the installation in error situations, you can continue the installationin two situations:

Situation 1:

You have not canceled the installation. That is, the error dialog box is still displayed and SAPinst is waiting for your input. Proceed as follows:

On the displayed error dialog box, choose Retry.

SAPinst now retries the installation step.

Situation 2:

You have canceled the installation. That is, the installation is aborted and needs to be continued. Since SAPinst records the installation progress in the file keydb.xml, it cancontinue the installation from the failed step without repeating previous steps.

You have two alternatives:

¶ Continuing the installation

¶ Restarting from scratch. That is, starting the installation with the delivered defaultkeydb.xml file.

In some cases, you must uninstall already installed components, before repeating the installation from scratch. That applies for example for an SAP system installation. See the uninstalling description in the corresponding installation guide.

Februar/2002 93


How to proceed on UNIX

Continuing the Installation

¶ Check if a SAPinst GUI Java process is still running, and if so kill it: ps -ef | grep java

¶ Make sure that all environment variables are set as described in the correspondinginstallation documentation.

¶ Start SAPinst from your <SAPinst_INSTDIR> with: ./sapinst

Restarting from scratch

You have the following alternatives

¶ Restart the installation from installation CD

¶ Start SAPinst from CD again as described above in this documentation.SAPinst deletes all files in your installation directory and asks you if you want to overwrite any existing installation directory.

¶ Prepare the new installation manually (installation CD is not needed)

In your <SAPinst_INSTDIR> do the following:

¶ Rename the file keydb.1.xml file (original file delivered by SAP) to keydb.xml.

¶ Delete all keydb.<no>.xml - files, if there are any.

¶ Start SAPinst from your <SAPinst_INSTDIR> with: ./sapinst

How to proceed on Windows

Continuing the Installation

¶ Check if a SAPinst GUI Java process is still running, and if so, kill it by looking for javaw.exe under Processes in your Task Manager.

¶ Choose Start Programs <menu_entry> SAPinst Server with GUI (or SAPinst GUI if you want to start the GUI only or SAPinst Server only if you want to start SAPinst without GUI).

Restarting from scratch

¶ Check if a SAPinst GUI Java process is still running, and if so, kill it by looking for javaw.exe under Processes in your Task Manager.

¶ Choose Start -> Programs -> <menu_entry> -> Prepare New Installation

¶ Current log and command files will now be copied to a backup directory that indicate

day and time of the backup: <SAPinst_Dir>\log<month>_<date><time>

¶ Choose Start Programs <menu_entry> SAPinst Server with GUI (or SAPinst GUI if you want to start the GUI only or SAPinst Server only if you want to start SAPinst without GUI).

94 Februar/2002


2.5.1.2 Performing a Remote Installation with SAPinst

Use

You can run SAPinst GUI standalone.

This allows you to deploy SAP Integration on another host (= remote host) while monitoringthe installation with SAPinst GUI on your local Windows or UNIX computer (=local host).

The overall process is (for details see procedures below):

1. Install SAPinst on your remote host and SAPinst GUI on your local host.

2. Start SAPinst server on your remote host.

3. Start SAPinst GUI on your local host.

4. Perform the installation using SAPinst GUI.

Prerequisites

¶ Make sure that you have performed the preparation activities for your local host and remote host (see Preparations [page 29]

¶ Both computers are on the LAN and can ping each other.

To test this, log on to your remote host and enter the command ping <local_host>

from the command prompt. Use the equivalent ping command on the local host.

SAPinst Ports

SAPinst uses the ports 21212 and 21213 during the installation for communication with SAPinst GUI. If one of these ports is already used by another service SAPinst will abort the installation with an appropriate error message.

In this case, you must start SAPinst or SAPinst GUI from the command prompt as follows:

¶ On UNIX: ./sapinst SAPINST_DIALOG_PORT=<free_port_number>

¶ On Windows: sapinst SAPINST_DIALOG_PORT=<free_port_number>

whereas <free_port_number> defines an unused port number. For example, if you

enter 6000 as <free_port_number>, SAPinst uses the ports 6000 and 6001.

The same applies for the SAPinst GUI commands startinstgui.bat (on Windows) and

startinstgui.sh (on UNIX).

Februar/2002 95


Procedures

Activities on a remote host (on which SAP Integration is to be installed)

If your remote host runs on a Windows platform:

1. Log on to your remote host as user with administrator rights.

2. Insert the Server Components CD in your CD drive.


<CD drive>\SAPinst\NT

A dialog now asks you perform a Standard or Custom Installation

If you choose a Custom installation you can define:

¶ Installation directory for the SAPinst <SAPinst_DIR>.

¶ SAPinst folder in the Start menu

The Start menu entry is used to generate unique start menu entries.For example: You enter SAP Integration InstallationCreated Start menu: StartĄ Programs SAP Integration Installation

¶ Connection parameters (not applicable here)

4. Choose Next.

SAPinst is now be copied to your <SAPinst_DIR> and the start menu entries are

created.

5. To start SAPinst choose StartĄ ProgramsĄ <menu_entry>Ą SAPinst server only

SAPinst server now starts and waits for connect to SAPinst GUI

6. Start SAPinst GUI on the local host, as described in Activities on your local host.

If your remote host runs on a UNIX platform:

1. Log on to your remote host as user root.

2. Mount the Server Components CD.

3. Create <SAPinst_INSTDIR> and change to this directory.

4. From path <Server Components CD>/SAPINST/UNIX/<platform> run

./INSTALL --nogui

SAPinst is now be copied to your <SAPinst_INSTDIR> without SAPinst GUI.

5. Start SAPinst from your <SAPinst_INSTDIR> by entering: ./sapinst

SAPinst now starts and waits for the connection to the SAPinst GUI. That is, on the

command prompt is displayed: guiengine: waiting for connect...

6. Start SAPinst GUI on your local host, as described in Activities on your local host.

96 Februar/2002


Activities on your local host (where SAPinst GUI should run)

If your remote host runs on a Windows platform:

1. Log on to your local Windows host.

2. Insert the Server Components CD into your CD-ROM drive.


<CD drive>\SAPinst\NT

A dialog now asks you perform a Standard or Custom Installation

4. Choose a Custom installation. You can define:

¶ Installation directory for the SAPinst (that is, for the SAPinst GUI)

¶ SAPinst folder in the Start menu

¶ Connection parameters (hostname and port number) to connect to your remote host(s). You can enter all known remote hosts and their corresponding free port number. Make sure to enter the same port number as SAPinst uses on the corresponding remotecomputer.

The Start menu entry and the connection parameters are used to generateunique start menu entries.For example:You enter the following during the installation:

- Start menu entry: SAPinst GUI

- Connection parameters (remote host / port): uwi005 / 8000

- Connection parameters (remote host / port): hs1101 / 5555

Then SAPinst creates the following start menu: StartĄ ProgramsĄ : SAPinst GUI Ą SAPinst GUI uwi005 8000 SAPinst GUI hs1101 5555

5. Enter your data, select the flag Install only the SAPinst GUI, and choose Next.

SAPinst GUI is now be copied to your <SAPinst_DIR> and the start menu entries are

created.

6. Choose StartĄ ProgramsĄ <menu_entry>Ą SAPinst GUI <host><port>

SAPinst GUI automatically connects to the host, which is waiting for connect.

That is, SAPinst GUI now starts and the Welcome screen is displayed.

If you have not entered connection parameters before, a dialog now asks you for the parameter:

- Hostname : Enter the hostname of the remote computer

- Port: Enter the same port number as SAPinst uses on the remote computer

7. You can now perform the installation from your local host.

Februar/2002 97


If your remote host runs on a UNIX platform:

1. Log on to your local UNIX host as user root.

2. Mount the Server Components CD-ROM.

3. Create <SAPinst_INSTDIR> and change to this directory:

¶ mkdir <SAPinst_INSTDIR>

¶ cd <SAPinst_INSTDIR>

4. Change to <Server Components CD>/SAPINST/UNIX/<platform> and run

./startinstgui.sh

SAPinst GUI is now be copied to your <SAPinst_INSTDIR>.

5. Start SAPinst GUI from your <SAPinst_INSTDIR> by entering: ./startinstgui.sh

SAPinst GUI automatically connects to the host, which is waiting for connect.

6. You can now perform the installation from your local host.

98 Februar/2002


2.5.1.3 Handling the CD Browser Dialog The following tells you how to handle the CD Browser dialog.

SAPinst displays this window in following situations:

1. SAPinst wants to check the availability of the software package.

You can recognize this situation by the flag Check Location displayed on the CD BrowserWindow.

Choose one of the following actions:

Action Result

You do not enter any PackageLocation and leave the flagCheck Location deselected.

SAPinst skips the check and you can continuethe installation procedure.However, SAPinst asks later for the missing

LABEL.ASC (see step 2 below).

You enter the path of the Package Location and leavethe flag Check Locationdeselected.

SAPinst skips checking the label location, but your entered package locations are used later for the installation.SAPinst only asks again for a missing

LABEL.ASC if the package location is

incorrect (see step 2 below).

You enter the path of the Package Location and selectthe flag Check PackageLocation

SAPinst checks the label location and displaysan error message if the location is incorrect.

If all locations are correct, SAPinst does not

ask again for the LABEL.ASC files later.

2. SAPinst cannot find the correct LABEL.ASC but needs the location of the software to process the installation now.

You can recognize this situation by the missing flag Check Location on the CD Browserwindow. You now have to enter the path to the correct LABEL.ASC. Otherwise, the installation cannot continue.

Additionally, you can copy the installation package by entering a location in the columnCopy Package to

Februar/2002 99


2.5.2 SAP ITS Specific Information

2.5.2.1 Installing Additional IACs

Use

You can add additional IACs to an already existing AGate and/or WGate installation by usingthe tool Package Manager.

This requires the tool SAPinst again.

Procedure

1. Log on to your ITS host as user <itsadm>.

2. Start SAPinst.

How to start SAPinst is already described:

- Install an ITS instance on Windows [page 43]

- Installing an ITS Instance on Linux / Solaris [page 53]



The window Checking ITS Version is displayed.

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 last several minutes.

2.5.2.2 Repeating an ITS Installation Unattended

Use

You can repeat your ITS installation and your ITS instance installation unattended. This may be very useful in case of

¶ damaged / missing files or total loss of data in the physical ITS installation directoryduring a system breakdown

¶ repeating an ITS installation on another host

Procedure

For more information see SAP Note 526835, section Repeating an ITS Installation Unattended.

100 Februar/2002


2.5.2.3 Applying Patches for the ITS For more information, see SAP Note 526835, section Applying Patches.

Februar/2002 101


2.5.2.4 Uninstalling the ITS

Uninstalling with SAPinst

This procedure does not uninstall an IACOR.

1. Log on to your ITS host as user <itsadm>.

2. Stop your Web server.

3. Start SAPinst.

How to start SAPinst is already described:

- Install an ITS instance on Windows [page 43]

- Installing an ITS Instance on Linux / Solaris [page 53]



The window Checking ITS Version is displayed.

5. Select Delete ITS Installation.

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 ITS Web server directories.

6. On Windows, run regedit and delete the key SAP_REGISTRY_PATH underHKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SessionManager\Environment.

102 Februar/2002


3 SAP@Web Studio Installation Guide Purpose

This documentation describes how to install the SAP@Web Studio.

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.

Implementation Considerations

If you want to give Internet and intranet users direct access to the SAP system by enablingthem 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.

Integration

If you are using the SAP@Web Studio to develop ITS-driven applications you also need:

¶ The 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

¶ A SAP system

The ITS requires an SAP system, which is Release 3.0D or higher.

If you install the SAP GUI for HTML, your SAP system must be Release 4.0B or higher.

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.

Constraints

The SAP@Web Studio runs on Windows 2000 servers.

Februar/2002 103


3.1 SAP@Web Studio InstallationPurpose

This process describes the main steps for installing the SAP@Web Studio.

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 [on page 36].

Process Flow

When installing the SAP@Web Studio, you need to take the following main steps:

1. Check the installation requirements [page 105].

2. Perform the preparatory steps [page 106].

3. Perform the installation [page 107].

4. Set up the environment [page 108].

104 Februar/2002


3.1.1 SAP@Web Studio InstallationRequirements

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.

Februar/2002 105


3.1.2 Preparing for SAP@Web Studio Installation

Prerequisites

You have read the installation requirements [page 105].

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, which identifies your R/3 instance.

If you want to connect to a message server as well, copy the appropriate message serverport entry, from the services file on the same machine that you got the saplogon.inifile 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.

Result

You are now ready to install the SAP@Web Studio [page 107].

106 Februar/2002


3.1.3 Installing the SAP@Web Studio This procedure describes how to install the SAP@Web Studio.

Prerequisites

You have read the installation requirements [page 105] and taken the preparatory steps [page 106].

Procedure

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

8. Choose Next.

9. Choose Finish to complete setup.

If the setup program states that your computer needs to be restarted, choose OK.

Result

The SAP@Web Studio is installed. You should now set up the environment [page 108].

Februar/2002 107


3.1.4 Setting up the SAP@Web Studio Environment

Use

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:

¶ Set up the R/3 server by connecting to an SAP system

¶ Define an ITS site, which is the server location of all the ITS files required to start a service

This documentation briefly describes the main steps you need to take.For full details, see the SAP@Web Studio documentation:

¶ In the SAP@Web Studio, choose Help Studio Documentation

¶ In the R/3 System, choose Help SAP Library SAP Web

Application Server Frontend Services (BC-FES) ITS /

SAP@Web Studio (BC-FES-ITS) SAP@Web Studio

Prerequisites

You have installed the SAP@Web Studio [page 107].

Procedure

Starting the SAP@Web Studio

To start the SAP@Web Studio from the Windows desktop after installation, choose StartPrograms SAP@Web Studio Studio <release>.

Setting up the EnvironmentThe 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.

108 Februar/2002


4 Appendix

4.1 General Information about ITS The Internet Transaction Server (ITS) extends the client/server architecture of the SAP system to the Internet.

HTTP DIAG

RFC

ISAPI,NSAPI,Apache

CGI

TCP/IP

Web servergateway

Applicationserver gateway

Web browser

Webserver

Internet TransactionServer (ITS)

AGate

R/3 System

WGate

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:

¶ Web server gateway (WGate)

¶ Application server gateway (AGate)

WGateWGate 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:

¶ Microsoft Internet Information Server (IIS) through the Information Server API (ISAPI)

¶ Netscape Enterprise Server (NES) through the Network Server API (NSAPI)

¶ iPlanet Webserver (iWS) through the Network Server API (NSAPI)

¶ Apache Web Server through the Apache Web Server API

Februar/2002 109


WGate connects a ‘stateless’ Web server, which communicates with Web browsers via singlerequest/response cycles, to a ‘stateful’ SAP system where business transactions depend on internal status.

When an Internet or intranet user starts an application from a Web browser and triggers anSAP transaction, function module or report via the ITS, a server process must be runningthroughout 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.

AGateAGate 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 SAPapplication 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.

You should have read the as well the sections concerning, instances [page111], file types and locations [page 117], and packages [page 120], especiallyif you are installing the ITS for the first time.

110 Februar/2002


4.2 ITS InstancesAn Internet Transaction Server (ITS) installation consists of one or more ITS instances, eachrunning 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 the 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.

Central

ITS Server

Consolidation R/3

CON

ITS

CON

Devlopment R/3

DEV

ITS

DEV

ITS

ADM

R/3 Systems

The above graphic shows three ITS instances:

¶ ADM is used to run ITS Administration

¶ CON is used for testing

¶ DEV is used for development

To install these 3 instances, you must run the SAPinst three times.

In production systems, security is critical, so you need to be more careful:

¶ 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

¶ Always run WGate and AGate on separate machines in a dual host installation, as described in ITS Installation Options [page 16].

In most cases, even in production systems, you only need to run one Web server and oneWGate 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.

Februar/2002 111


Web Server – ITS Scalability

WGate Connects to Multiple AGate Processes

AGat

ITS

Web serverDB

SAP System

App.

server

eWGate

AGateAGate

AGateAGate

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 processesallow you to handle large numbers of users, but you should take into account memory limitations.

112 Februar/2002


Multiple Web Servers / WGates Connect to 1 AGate

Web server

Web serverITS

DB

R/3 System

App.

server

WGate

WGate

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.

Multiple ITS Instances Connect to the Same SAP system

DB

R/3 System

WGate

WGate

WGate

ITS

Web server

Web server

Web server

AGate

AGate

AGate

App.

server

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 BalancingFrom 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.

Februar/2002 113


Single WGate Interconnects With Multiple AGates

WGate

HTTP

routerWeb server

AGate

AGate

AGate

ITS

Web

browser

This configuration reduces the risk of failure in large-scale implementations, because WGatealways routes the requests to the appropriate AGate instance, according to the load at the time.

Multiple WGates Interconnect With Multiple AGates for High Availability Systems

W Gate

WGate

HTTP

router

W eb server

W eb server

AGate

AGate

AGate

ITS

W eb

browser

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 cannotknow in advance how requests are going to be routed, so it is essential that all WGates areconnected to all AGates.

114 Februar/2002


ITS – SAP SYSTEM Scalability

ITS Connects to Single SAP Application Server

Application

server

Database

server

SAP SystemSAP System

ITSITS

Februar/2002 115


ITS Connects to SAP Message Server for Load Balancing

ITSITSDatabase

serverMessage

server

Application

server

Application

server

Application

server

SAP SystemSAP System

The ITS benefits from SAP system scalability through:

¶ Efficient transaction management

- Multiple work processes

- Load balancing to multiple application servers using login groups

¶ Database buffering

Buffering database tables on the application server achieves faster access to data.

116 Februar/2002


4.3 ITS File Types and Locations

ITS File TypesWhen 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 Webbrowser. Each service can consist of up to five ITS file types:

¶ A service file

¶ HTML templates

¶ Flow files

¶ Language resources

¶ Multipurpose Internet Mail Extension (MIME) files

The ITS may also derive some information from the global service file, which containssettings that apply to all services.

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 somedetails 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 itsown 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 HTML

Business statements. HTML

Business 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 whatthe user chooses to do.

In flow logic applications, there is one flow file for each HTML template that requires a dialogflow definition. Each flow file contains Extensible Markup Language (XML) statements, usinga 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 forplaceholders in the templates and replaces them with texts from the relevant languageresource file. Not all templates use language resource files.

Februar/2002 117


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 parametervalues for all services. The values defined in individual service files always override values inthe global service file.

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 implementationmodel used to develop the applications.

Format and extension for Web-enabled SAP transactions:

¶ Language-independent templates:

<program>_<screen>.html

¶ Language-specific templates:

<program>_<screen>_<language>.html

The <program>, <screen>, and <language> elements refer to the

SAP program, screen, and development language of the associated ABAP transaction.

Format and extension for flow file applications:

¶ <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

118 Februar/2002


MIME files Some examples of MIME files are:

¶ Image files:

- <name>.gif

- <name>.jpg

¶ Video files

- <name>.avi

¶ Sound files

- <name>.wav

Global service file global.srvc

ITS File LocationsUnless 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 storedon the ITS AGate server except MIME files, which are stored on the Web server.

ITS File Directory

Services <ITS_InstDir>\<ITS instance>\services

HTML templates <ITS_InstDir>\<ITS instance>\templates

¶ The templates directory contains a subdirectory for each

service under:

<ITS_InstDir>\<ITS instance>\ templates\<service>

¶ Each service subdirectory may also contain subdirectories foreach 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 serverconfiguration. The default is usually the Web server root directory for each ITS instance.

For Microsoft Internet Information Server (IIS), the recommendeddefault 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\

Februar/2002 119


For Apache Http Server, the default is:

C:\Program Files\Apache Group\Apache\htdocs\sap\its\mimes\

4.4 ITS Backup StrategyUse

SAPinst now automatically backs up the following files:

¶ Services

¶ Templates

¶ Mimes

Activities

Backups of these files will be done automatically, everytime you start an ITS installation affecting an already existing ITS instance, that is:

¶ Updating the ITS

¶ New instance installation using an already existing virtual instance name

¶ Adding new IAC packages to an ITS instance using the tool Package Manager

SAPinst then creates backups of the files in extra directories that indicate day and time of the backup.

Imagine you have an already installed ITS instance called CSR.

The relevant files will then be stored in (see also: ITS File Types andLocations on page 117):<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

120 Februar/2002


4.5 ITS Sub-ComponentsDefinition

The SAPinst includes the components:

¶ ITS Administration

¶ Internet Application Component Object Receiver (IACOR)

¶ Watchdog

For more information about the ITS Administration, see ITS Administration Guide.

For more information about the IAC developer tool SAP@Web Studio, see SAP@Web Studio Installation Guide [page 103].

IACOR

The Internet Application Components Object Receiver (IACOR) is a tool for enablingdirect publishing of Internet Transaction Server (ITS) files – service files, HTML templates,flow files, language resources, and MIME files – from the SAP system to the ITS (AGate) and the Web server.

This allows an automatic update of the ITS and the Web server whenever the SAP system is updated by a transport. In earlier releases, you had to publish the files manually from the SAP@Web Studio.

The IACOR is a Windows 2000 service, which – in the case of a dual host installation of the ITS – you have to install on both the AGate and the WGate. After configuration, it is ready to receive ITS files from one or more SAP systems.

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.

From SAP systems of Release 6.10 on, IACs should be exclusively published after ITS installation directly from the SAP system via the IACOR.

Watchdog

Watchdog is a Windows 2000 service running on a Web host offering the followingfunctionality:

- Monitoring of all ITS instances running on the local host via a dual DCOM interface.

- Registration of ITS instance in LDAP directories (optional).

High availability solution using Microsoft WLNB for the complete processing queue includingWGate

Februar/2002 121

Documents

ITSINST