Installation Guide Installation Guide Installation Guide Installation Guide SAP SAP SAP SAP ® Web Application Web Application Web Application Web Application Server 6.20 Installation Server 6.20 Installation Server 6.20 Installation Server 6.20 Installation on Windows 2000: on Windows 2000: on Windows 2000: on Windows 2000: IBM eServer iSeries IBM eServer iSeries IBM eServer iSeries IBM eServer iSeries (and AS/400) (and AS/400) (and AS/400) (and AS/400)
No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.
Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® andSQL Server® are registered trademarks of Microsoft Corporation.
trademarks of IBM Corp. in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks ofthe Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,WinFrame®, VideoFrame®, MultiWin® and other Citrix product namesreferenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
J2EE™ 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 byNetscape.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,Management Cockpit, mySAP, mySAP.com, and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. MarketSet and EnterpriseBuyer are jointly owned trademarks of SAP Markets and CommerceOne. All other product and service names mentioned are thetrademarks of their respective owners.
DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.
Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.
Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/xxxxxxxxhttp://service.sap.com/xxxxxxxxhttp://service.sap.com/xxxxxxxxhttp://service.sap.com/xxxxxxxx
Example Text Words or characters thatappear 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 thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody 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 asthey appear in thedocumentation.
<Exampletext>
Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.
EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
SAP Web AS Installation on Windows 2000: IBM eServer iSeries (and AS/400)
4 July 2002
Contents
SAP Web Application Server Installation on Windows 2000:IBM eServer iSeries (and AS/400) .................................................. 6
1 New Features ...................................................................................... 82 How to Install a Dialog Instance on a Windows 2000Application Server............................................................................... 103 Installation Planning ........................................................................ 13
3.1 Required Documentation.....................................................................133.2 System Configuration ..........................................................................153.3 SAP Directories ....................................................................................173.4 Users and Groups ................................................................................183.5 Hardware and Software Requirements Check ...................................19
3.5.1 Requirements Checklist for a Dialog Instance ............................................................204 Installation Preparation ................................................................... 22
4.1 Checking for Windows File System ....................................................224.2 Preparing iSeries for Windows File System Access .........................224.3 Installing Up-To-Date Dynamic Link Libraries ...................................234.4 Adjusting Virtual Memory ....................................................................234.5 Reducing the Size of the File Cache ...................................................244.6 Granting User Rights for the Installation............................................244.7 Using the SAP System ID and Host Name..........................................264.8 Preparing the SAP System Transport Host........................................264.9 Preparing the Host for SAPinst GUI....................................................274.10 Preparation of Required CDs for the Installation.............................284.11 Active Directory Services ..................................................................30
5 Installation Procedures.................................................................... 315.1 Input Parameters for the Installation ..................................................315.2 Running SAPinst ..................................................................................36
6 Post-Installation Activities .............................................................. 406.1 Downloading the SAP Java Crypto Toolkit ........................................406.2 Installing Borland JBuilder ..................................................................416.3 Installing a JDBC Driver.......................................................................416.4 Starting and Stopping the SAP system ..............................................436.5 Logging on to the SAP system............................................................446.6 Checking SAP system Services ..........................................................456.7 Configuring Windows Transport Systems .........................................456.8 Secure Single Sign-On.........................................................................46
6.8.1 Preparing the Application Server for Single Sign-On..................................................48
SAP Web AS Installation on Windows 2000: IBM eServer iSeries (and AS/400)
July 2002 5
6.8.2 Preparing SAP GUI and SAP Logon for Single Sign-On ............................................486.8.3 Mapping SAP System Users to Windows Users for Single Sign-On ..........................49
6.9 Performing a Backup of the Dialog Instance .....................................507 Additional Information ..................................................................... 52
7.1 Continuing an Interrupted Installation with SAPinst .........................527.2 Additional Information about the SAP J2EE Engine .........................537.3 Deleting a Dialog Instance...................................................................567.4 SAP System Security on Windows .....................................................57
7.4.1 Automatic Creation of Accounts and Groups..............................................................607.4.2 Performing a Domain Installation as Local Administrator ...........................................61
7.5 Changing the Password for User <sid>adm ......................................63
SAP Web AS Installation on Windows 2000: IBM eServer iSeries (and AS/400)
6 July 2002
SAP Web Application ServerInstallation on Windows 2000: IBMeServer iSeries (and AS/400)PurposeThis documentation explains how to install a single SAP dialog instance on a Windows 2000application server, when your database resides on an IBM eServer iSeries with a GlobalLanguage Solution (GLS) installation.
With Windows 2000, you must use the English (International) version of theoperating system, but you can use a different language for the graphical userinterface (GUI). For more information, see SAP Note 362379.
The SAP Web Application Server (SAP Web AS) is the underlying technology of almost allmySAP.com solutions. This is the new name for what has been referred to up until SAPRelease 4.6D as SAP Basis. The release number of the SAP Web Application Server reflectsthe independence of solutions and their underlying technology components provided by SAP.
For more information on the technology provided by the SAP Web AS, see the SAP ServiceMarketplace at: http://service.sap.com/technology
A minimum SAP system consists of a central instance and a database instance or of acentral database instance. Optional dialog instances may be installed on different Windows2000 hosts once the installation of the central instance and the database instance has beencompleted.
This documentation only refers to the installation of a dialog instance on aWindows 2000 application server. If you have not yet installed a centralinstance and a database instance on your iSeries, see the SAPdocumentation SAP Web Application Server Installation: IBM eServer iSeries(and AS/400) for Release 6.20. This documentation is also part of theinstallation package.
When you set up an SAP system on your Windows 2000 application server, you need toinstall the components that enable the system to operate. These are the:
• Dialog instances
• Front ends
The installation of front ends for the SAP system is described separately in thedocumentation SAP Front End Installation Guide.
Implementation ConsiderationsBefore you can begin with the installation of the dialog instance on your Windows 2000application server, you must have installed an SAP central and a database instance on youriSeries host. On the basis of information about the expected workload, set of applications thatare to be deployed and number of users, your SAP hardware partner can recommend afeasible configuration.
July 2002 7
Before you install the main components of an SAP system (central and database instance)you have to decide between the following configuration types:
• Central system (or 2-tier system)The central instance and the database instance are installed on a single host.
• Standalone database system (or 3-tier system)The central instance and database instance are installed on different hosts.
However, we recommend that you install the central instance and thedatabase instance on the same host. If you choose a standalone databasesystem installation you have to be aware that for an upgrade you will have tomove the central instance temporarily to the database instance host.
For your installation procedure on Windows 2000 it is of no importance whether you have acentral system or a standalone database system. You need to know how many dialoginstances are required. You can only install one dialog instance per Windows 2000 host.Once the plan is complete and the required hardware available, you can start with theinstallation process as described in this documentation.
ConstraintsThe SAP installation tools must only be used in accordance with the instructions and for thepurposes described in the SAP installation documentation. Improper use of the SAPinstallation tools can damage files and systems already installed.
SAP system installations should only be performed by SAP TechnicalConsultants who are certified for your operating system, your database andthe SAP system you are installing.
Downward-Compatible Releases of DB/OS platforms for SAP ProductsSAP plans to regularly release the newest database (DB) and operating-system (OS) versions of mySAP.com products. These releases aredownward-compatible with earlier SAP releases. Be aware that, for alreadyshipped mySAP.com components, we only support the installation fordatabase versions proposed by the installation tool. Therefore, you mustinstall a mySAP.com component or perform a system copy using adownward-compatible database as follows:• Install the component with the old proposed database version.• Upgrade the old database version to the downward-compatible new
version.
1 New Features
8 July 2002
1 New FeaturesThe installation for SAP Web Application Server (SAP Web AS) 6.20 has the following newfeatures:
SAP Web AS InstallationArea Description
New installation tool SAP provides a new installation tool called System LandscapeImplementation Manager, known for short as SAPinst.
The main advantages compared with the previous installation toolR3SETUP are:
• SAPinst lets you step back to correct your entries during theinput phase without restarting the installation.
• SAPinst does not abort due to errors. Instead, it stops theinstallation and you can retry the installation after having solvedthe problem. Alternatively, you can abort the installationmanually if you want.
• SAPinst continues an aborted installation directly from the pointof failure.
• SAPinst records installation progress in a single log file,sapinst.log.
• SAPinst has a graphical user interface (GUI) called SAPinstGUI that allows you to watch the progress of the installation andsee all messages issued by SAPinst. As SAPinst GUI is Javabased, you need a Java Runtime Environment (JRE).A What's this? help is integrated in SAPinst GUI. To use this,
choose , then click on the field for which you want moreinformation.
You can start SAPinst GUI on a remote computer ifyou want.For more information on SAPinst, see thedocumentation SAPinst Troubleshooting Guide at:http://service.sap.com/sapinstfeedback
Integration of SAP J2EEEngine
A Java 2 Enterprise Edition (J2EE) standards-based engine isprovided and supported by SAP as a runtime environment for theJava-based components of mySAP.com. It is an integral part of theSAP Web Application Server as of Release 6.20, which delivers areliable and scalable e-business environment with native Javasupport that is fully J2EE compliant.
The SAP J2EE Engine integrated into the SAP Web AS providesthe following features:
• J2EE compliance
• Enterprise JavaBeans
• Web and Internet enabling
• XML support
1 New Features
July 2002 9
For more information, see the SAP Library (choose Help � SAPLibrary in your SAP system or access the SAP Library at:http://help.sap.com) and choose mySAP TechnologyComponents � SAP Web Application Server � SAP J2EEEngine.
Operating system support Only Windows 2000 is supported for the installation of SAP Web AS6.20.
Documentation Due to the above changes, especially the introduction of SAPinst,the structure and content have changed significantly for theinstallation of the dialog instance on a Windows 2000 applicationserver. For more information, see How to Install the DialogInstance on a Windows 2000 Application Server [Page 10].
2 How to Install a Dialog Instance on a Windows 2000 Application Server
10 July 2002
2 How to Install a Dialog Instance on aWindows 2000 Application Server
The structure of the installation documentation and therefore the procedure touse it have changed significantly for the installation of a dialog instance on aWindows 2000 Application Server.
Use the tables below as a checklist for installing the system and to navigate through theinstallation procedures. All necessary installation phases (planning, preparation, installation,and post-installation) are listed in these tables. They contain links to the procedures in thisdocumentation. Use the links to the general descriptions of the actions and to any additionalinformation to help you perform the actions. This prevents you missing important information.
We recommend you to proceed as follows to install your SAP system:
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 thecorresponding section.
b. Perform the procedure described there.
c. After successfully completing the installation step, mark the corresponding entry inthe printed table with > to log the progress of your installation.
d. Proceed with the next step listed in the table.
Installation ChecklistThe following tables list the actions you need to perform when you install your dialoginstance.
Installation PlanningCareful planning is a prerequisite for the successful installation of the system.> Action
Read the required documentation [Page 13].
Make sure you have obtained the current SAP Note.Decide on the optimal configuration for the system [Page 15].
Check the hardware and software requirements [Page 19].
Installation PreparationBefore you install the actual SAP system, you have to perform the following actions:> Action
Check the Windows file system [Page 22].
Prepare iSeries for Windows file system access [Page 22].
Install up-to-date dynamic link libraries [Page 23].
Adjust virtual memory [Page 23].
2 How to Install a Dialog Instance on a Windows 2000 Application Server
July 2002 11
Reduce the size of the file cache [Page 23].
Use the SAP system ID and the host name [Page 25].
Prepare the SAP system transport host [Page 26].
Grant user right for the installation [Page 24].
Prepare the host for SAPinst GUI [Page 27].
Prepare the required CD for the installation [Page 28].
Optionally, use the active directory services [Page 29].
Installation Procedures> Action
Check the input parameters for the installation [Page 31].
To install the dialog instance, run SAPinst [Page 36].
Check that the front end software is installed on at least one host machine in your systemenvironment. For more information on how to install the front end software, see theseparate documentation:
• SAP Front End Installation Guide (English version)
• SAP Frontend-Installationsleitfaden (German version)
You can find this documentation in the SAP Service Marketplace at:http://service.sap.com/instguides
Post-Installation Activities> Action
If required, download the SAP Java Crypto Toolkit for the SAP J2EE Engine [Page 40].
If required, install Borland JBuilder [Page 41] for SAP remote support.
If required, install a JDBC Driver [Page 41].
Check that you can start and stop the SAP system [Page 43].
Check that you can log on to the SAP system [Page 44].
Check the SAP system services [Page 45].
Configure Windows transport systems [Page 45].
If required, Secure Single Sign-On [Page 46],
Perform a backup of the dialog instance [Page 50].
After the installation, the SAP J2EE Engine is activated. If you do not want to use the SAPJ2EE Engine, you can deactivate it. For more information, see Additional Informationabout the SAP J2EE Engine [Page 53] → Deactivation of the SAP J2EE Engine.
2 How to Install a Dialog Instance on a Windows 2000 Application Server
12 July 2002
Additional InformationYou might need to refer to the optional sections below when installing your dialog instanceon a Windows 2000 application server.
>>>> Section
Continuing an Interrupted Installation with SAPinst [Page 52]
Additional Information about the SAPJ2EE Engine [Page 53]
Deleting a Dialog Instance [Page 56]
SAP System Security on Windows [Page 57]
Changing the Password for User <sid>adm [Page 63]
3 Installation Planning
July 2002 13
3 Installation Planning
The structure of the installation documentation and therefore the procedure touse it has changed significantly. For more information on how to use theinstallation documentation, see How to Install a Dialog Instance on aWindows 2000 Application Server [Page 10].
3.1 Required DocumentationBefore starting the installation, make sure you have access to the following information:
• SAP Installation Note 484548iSeries: 3 tier system instruction
SAP NotesMake sure you have obtained all the SAP Notes required for installing this release of the SAPsystem on IBM eServer iSeries. Obtain the SAP Notes immediately before you start theinstallation.
SAPNote
Title
495432 6.20 SAP Web Application Server Installation on Windows 2000: IBMeServer iSeries
495433 6.20 SAP Web Application Server Installation on IBM eServer iSeries
85129 Download SAP@Web Studio and ITS, Upgrade Information
SAPinst Troubleshooting GuideRead the documentation SAPinst Troubleshooting Guide . It provides up-to-date informationabout how to avoid installation failure and what to do if a failure occurs.
You can find the SAPinst Troubleshooting Guide in the SAP Service Marketplace at:http://service.sap.com/sapinstfeedback
3 Installation Planning
14 July 2002
Naming ConventionsIn this documentation, the following naming conventions apply:
TerminologySAP System and SAP Web Application ServerThe term SAP system is the same as SAP Web Application Server.
SAP System IDThe SAP system ID is abbreviated to SID and SAPSID or sid and sapsid. For <sid> /<sapsid>, substitute your SAP system ID in lower case characters, for example, prd. For<SID> / <SAPSID>, substitute your SAP system ID in upper case characters, for example,PRD.
IBM eServer iSeriesIBM eServer iSeries is referred to as iSeries.
IBM eServer iSeries was formerly called IBM AS/400.
IBM DB2 Universal Database for iSeriesIBM DB2 Universal Database for iSeries is referred to as DB2 UDB for iSeries.
IBM DB2 Universal Database for iSeries was formerly called IBM Universal Database forAS/400.
VariablesVariables Description
<SID> and <SAPSID> SAP system ID in uppercase letters
<sid> and <sapsid> SAP system ID in lowercase letters
<INSTDIR> Installation directory
<SAPLOCALHOST> Name of Windows 2000 application server
<SAPTRANSHOST> Name of transport directory (on iSeries)
<SAPGLOBALHOST> Name of central instance
<SAPDATABASEHOST> Name of database host
<CD-DIR> Directory on which CD-ROM is mounted
<OS> Operating system name within a path
The following is an example of how the variables are used:
Log on as user <sid>adm and change to the directory /usr/sap/<SID>.If your SAP system ID is C11, log on as user c11adm and change to directory/usr/sap/C11.
3 Installation Planning
July 2002 15
Additional Information
Documents that are also part of the delivered Installation/UpgradeDocumentation CD-ROM are marked with "[CD]".
• Platforms released for mySAP.com, see the SAP Service Marketplace at:http://service.sap.com/platforms
• Technical infrastructure (like configuration scenarios and related aspects such assecurity, load balancing, availability and caching), see SAP Service Marketplace at:http://service.sap.com/network
• Installation of front ends for the SAP system, see the documentation Front EndInstallation Guide [Presentation CD] or the SAP Service Marketplace at:
http://service.sap.com/instguides
• mySAP.com Workplace, see the SAP Service Marketplace at:http://service.sap.com/workplace
• SAP systems for high availability purposes, see:
− SAP online documentation BC SAP High Availability in the SAP Library (choose Help� SAP Library in your SAP system) or access the SAP Library at:http://help.sap.com
− SAP Service Marketplace at:http://service.sap.com/ha
• Copying an SAP system, see the SAP Service Marketplace:
− Homogeneous System Copy at:http://service.sap.com/instguides
− Heterogeneous System Copy at:http://service.sap.com/osdbmigration
• Information about SAP Web AS Security, see the SAP Service Marketplace at:http://service.sap.com/security
3.2 System ConfigurationThe configuration of the system is generally planned well in advance of the installationtogether with the hardware vendor. Configuration planning involves deciding whether a 2-tiersystem or 3-tier system is to be installed, and how many dialog instances are required.
The configuration is worked out with the hardware partner on the basis of sizing informationthat reflects the system workload. Details such as the set of applications that are to bedeployed, how intensively these are to be used, and the number of users enable thehardware vendor to recommend a configuration that performs well.
An SAP system consists of a database server, (optional) additional application servers, and anumber of front end computers. The graphic below shows a typical distribution of theinstances of an SAP system over several computers.
3 Installation Planning
16 July 2002
The database server is the computer on which the database is installed. This server usuallyalso accommodates the central instance (the SAP instance that includes the message serverand enqueue server processes). If the central instance is installed on a separate applicationserver, the database server is called a standalone database server.
Additional dialog instances (SAP instances including only dialog, batch, spool, or updateprocesses) are installed on application servers. These servers can be either iSeries hosts orWindows 2000 hosts.
You can think of an SAP instance (central or dialog instance or standalone gateway) as agroup of processes that are started and stopped at the same time. Every instance has a two-digit identifier between 00 and 97 that must be unique on a computer.
You must have completed the planning and system configuration before you install an SAPsystem (including a database and a central instance) on your iSeries. This documentationonly refers to the installation of a dialog instance on a Windows 2000 application server withyour database residing on an iSeries.
Typical Configuration of an SAP system
We recommend that you install only one SAP dialog instance on eachWindows 2000 host you want to use.
SAP Instance
(DVEBMGS00)
SAP Instance
(D00)
SAPInstance
(D01)
DB
SAP GUI SAP GUI SAP GUI SAP GUI SAP GUI SAP GUI
ApplicationServer
with one Dialog
Instance
Database Server Application Server with Central Instance
WindowsApplication
Server with one Dialog
Instance
iSeries
iSeries iSeries
Windows 2000
ApplicationServer
with one Dialog
Instance
DATABASE
PC1 PC2 PC3 PC4 PC5 PC6
3 Installation Planning
July 2002 17
3.3 SAP DirectoriesDefinitionThe following gives you some background information about the SAP directories that havebeen created during the installation. The base directories required for the SAP centralinstance are:
• \\<SAPGLOBALHOST>\sapmnt, created on the central instance (of your iSeries). Itcontains general SAP software
• \\<SAPTRANSHOST>\sapmnt\trans, created on the transport host. It contains SAPsoftware for the transport of objects between SAP systems
The following explanation distinguishes between a global, local and database host.
The global host is the machine on which the SAP central instance is running (on youriSeries).The local host, is the current machine on which an SAP instance is running.The DB host is the machine on which the database server is running (on your iSeries).
Use
Directory \usr\sapThe installation program creates directory \usr\sap on the local host and shares it assaploc.
On local hosts, \\<SAPLOCALHOST>\saploc contains only instance-specific data andcopies of the SAP executables. The executables on the local host are updated from those onthe global host each time the local instance is started and if it is necessary.
The SAP software is stored in directory \\<SAPGLOBALHOST>\sapmnt and contains globaland local (instance-specific) data on a global host.
Directory \sapmnt\transIn an SAP system landscape there must be a global directory for the transport of objectsbetween SAP systems. This directory is created on one SAP instance host in the SAPsystem landscape (the transport host). This typically resides on the central instance of youriSeries. It must be accessible for every host on which an SAP instance is installed and whichbelongs to this SAP system landscape. The path on every host must be\\<SAPTRANSHOST>\sapmnt\trans.
SAP enables you to make a transport host known to the Domain Name Server for allWindows 2000 systems. For more information, see Preparing the SAP System TransportHost [Page 26].
StructureDirectory Structure of a Distributed Installation
This graphic shows how the central instance, which runs on the global host, interacts with aWindows 2000 application server. On such a distributed instance host, the parametersSAPGLOBALHOST and SAPLOCALHOST have different values. Distributed instances useSAPGLOBALHOST to access global data on the central instance.
3 Installation Planning
18 July 2002
3.4 Users and GroupsOn the iSeries and the Windows 2000 application server, the following user and groups areneeded.
Windows 2000 User and Groups
User Description<sid>adm SAP system administrator / SAP service account
Groups DescriptionSAP_<SID>_GlobalAdmin Domain-level SAP administration group
SAP_<SID>_LocalAdmin Local SAP administration group
iSeries User and Groups
User Description<sid>adm SAP system administrator / SAP service account
Groups Description<SID>Group SAP system administration group
Not necessarily oncentral instance SAP System distributes updates from
the global host to the application server.run_nt
3 Installation Planning
July 2002 19
3.5 Hardware and Software RequirementsCheckPurposeSAP specifies minimum hardware and software requirements to ensure that a newly installedsystem performs well. These requirements are summarized in hardware and softwarerequirements checklists and are only valid for the current release.
These checklists give the minimum requirements for the installation of a dialog instance on aWindows 2000 application server and do not take customer data into account. Depending onthe amount of data involved, the requirements might change.
For a more precise sizing definition that reflects your particular system load, you can contacta hardware vendor. The vendor analyzes the load and calculates suitable hardware sizing.
If you have any questions, contact the person in charge of installation, your CompetenceCenter, or your local IBM representative.
Prerequisites• For remote support, the remote connection specified in the contract agreement must be
available before installation. The Internet address setup at SAP and registration are dealtwith during the installation.
• You are only allowed to install an SAP system on certified hardware. AddOn SystemhausGmbH certifies hardware platforms for SAP on Microsoft Windows 2000. It certifies aspecified release of Microsoft Windows 2000. SAP customers can then run the SAPsystem on the respective platform for all the combinations of the SAP system anddatabases released by SAP for the specified release of Microsoft Windows 2000. Youcan find more information about certified platforms at: http://addon.saponwin.com
Process Flow1. See the checklist dialog instance [Page 19].
2. Check the network requirements. These are described in the documentation NetworkIntegration of SAP Servers, which you can find at:http://service.sap.com/networks
If you do not fully meet the relevant requirements, you might experienceproblems when working with your SAP system.
3 Installation Planning
20 July 2002
3.5.1 Requirements Checklist for a Dialog InstanceThe Windows 2000 application server must meet the following requirements:
RequirementType
How to check
Hardwarerequirements
CD drive on your Windows 2000 application server
• Tape drive for backups, either 4mm DAT or DLT.Hardware compression is recommended
• Disk space of 250 MB (not including virtualmemory).To check, choose: Start → Programs →Administrative Tools → Computer ManagementIn the Computer Management tree, choose:Storage → Disk Management
• RAM of 512 MBTo check, chooseStart → Programs → Administrative Tools →Computer Management.In the Computer Management tree choose:System Tools → System Information → SystemSummary.
• Virtual memory of 4 times RAM.Maximum required is 10 GB. To check, right-click onMy Computer → Properties. If required, choosesection Virtual Memory and then Change.
Softwarerequirements
• Client Access Express for IBM iSeries
• For OS/400 Release V5R1 you need the IBM product5722 XE1.
a. To install the product, map a network drive onyour Windows 2000 server to the QIBM share onthe database host:\\<dbhost>\QIBM
b. Choose Start → Run and enter:\\<dbhost>\QIBM\PRODDATA\CA400\EXPRESS\INSTALL\IMAGE\SETUP.EXE
• Latest XDA for Client Access Express.
To download the latest XDA for Client Access,proceed as follows:
a. Go to the IBM Web pagehttp://www.ibm.com/servers/eserver/iseries/access/xda/
b. On the XDA for Client Access site, chooseDownload.
The iSeries Client Access page appears.
3 Installation Planning
July 2002 21
c. Download the setup.exe file to a folder, forexample C:\TEMP
d. In the Windows Explorer open the file you havejust downloaded and double-click it.
The XDA setup application is executed.
• Windows 2000 Server, Service Pack 1 or higherWindows 2000 Advanced ServerWindows 2000 Data Center ServerTo check, choose: Start → Run. Enter the commandwinver
• Internet Explorer 4.0, service pack 1 or higheror Internet Explorer 5.0
• Windows NT Resource Kit is strongly recommendedto enable support.
Otherrequirements
• Check that the network requirements are met. Youcan find more information in the SAP ServiceMarketplace at:http://service.sap.com/networks
• To prepare printers for use in the SAP system,check that they operate correctly at the Windows2000 level using the Print Manager as follows:Choose Start → Settings → Printers to check theprinter installation. If you can print from a Windows2000 application (for example, Notepad), the printeris installed correctly.For more information, see the Windows 2000documentation.
4 Installation Preparation
22 July 2002
4 Installation Preparation
The structure of the installation documentation and therefore the procedure touse it has changed significantly. For more information on how to use theinstallation documentation, see How to Install a Dialog Instance on aWindows 2000 Application Server [Page 10].
4.1 Checking for Windows File SystemUseThis section describes how to check that you are using the Windows File System (NFTS) onhosts where the SAP system is to be installed. NTFS supports full Windows security and longfile names.
You must use NTFS for an SAP system installation. Do not install the SAPdirectories on an FAT partition.
Procedure1. Open the Windows Explorer.
2. Select the root directory.
3. Choose File → Properties.
4. To see the type of file system that is in use, choose General.
4.2 Preparing iSeries for Windows File SystemAccessUseYou use this procedure to start the NetServer on iSeries. Windows 2000 uses NetServer toaccess IFS files on the iSeries where the central instance is running.
ProcedureThe NetServer should be started automatically by adding the following command to thestartup program specified in the QSTRUPPGM system value (WRKSYSVAL QSTRUPPGM):
1. Log on to iSeries as a user that has authorization *IUSYSCFG, for example userQSECOFR.
2. Enter the following command:STRTCPSVR SERVER(*NETSRV) or STRTCPSVR SERVER(*ALL)
4 Installation Preparation
July 2002 23
4.3 Installing Up-To-Date Dynamic LinkLibrariesUseYou must install up-to-date dynamic link libraries (DLLs) on all Windows 2000 hosts in thesystem where you intend to run an SAP instance. The DLLs are required for correctfunctioning of the SAP system.
Procedure1. Insert the SAP Kernel CD in the CD-ROM drive.
2. Switch to directory <CD_DRIVE>:\NT\I386\NTPATCH .
3. Start program r3dllins.exe.
When the installation has finished, you are prompted to reboot the system toactivate the changes.If your DLLs were already up-to-date before you started the r3dllins.exeprogram, no new DLLs are installed and you are not prompted to reboot.
4.4 Adjusting Virtual MemoryUseYou must adjust virtual memory on all Windows hosts in the system where you intend to runan SAP dialog instance.
Procedure1. Right-click on My Computer and choose Properties.
2. On the Advanced tab, choose Performance Options.
3. On the Performance dialog box, check the page file setting and, if necessary, chooseChange to adapt it.
The virtual memory must be at least four times the RAM. More than 10 GB is notrequired.
For more information, see Hardware and Software Requirements Check [Page 19].
4 Installation Preparation
24 July 2002
4.5 Reducing the Size of the File CacheUseYou use this procedure to change the size of the file cache.
Procedure1. Choose Start →=Settings → Control Panel →=Network and Dial-up Connections.
2. In the Network and Dial-up connections dialog box, double-click Local Area Connections.
3. In the Local Area Connection Status dialog box, choose Properties.
4. In the Local Area Connection Properties dialog box, double-click File and Printer Sharingfor Microsoft Networks.
If you cannot select File and Printer Sharing for Microsoft Networks, thisoption has not yet been installed. To install it, you need the Windows 2000Server CDs.
5. Select Maximize data throughput for network applications.
6. To confirm your entries, choose OK.
4.6 Granting User Rights for the InstallationUseThe installation of the SAP system and the SAPinst tool is only possible with certain rightsand privileges that authorize the execution of the installation steps. Without these rights andprivileges any attempt to install the system aborts. Therefore, before you start the installation,you have to ask the system administrator to grant you the necessary authorizations.
One of the fundamental decisions that have to be made before the installation, is to decidewhether a domain or a local installation is to be performed. Depending on the type ofinstallation, different rights and privileges are necessary to permit the execution of theinstallation steps. This is of particular importance when multiple Windows 2000 applicationserver are to be installed. To perform a local installation, you need to be LocalAdministrator of the machine involved. To perform a domain installation, you need to beDomain Administrator of the domain involved, and all Windows 2000 hosts in thesystem must belong to the same domain. In a local installation, all Windows 2000 accountand user information is stored locally on one host and is not visible to any other hosts in thesystem. In a domain installation, the user information is stored centrally on the domaincontroller and is accessible to all hosts in the system.
If the SAP system is to run on a single Windows 2000 host, you can perform a localinstallation. If the system is to be distributed across more than one machine, SAP stronglyrecommends a domain installation.
Performing a local installation for a distributed system leads to authorizationproblems that have to be resolved.
4 Installation Preparation
July 2002 25
A domain installation requires a domain controller to store user and account informationcentrally for the whole system. For performance and security reasons the domain controllermust not be located on a host on which an SAP instance is running.
For performance and security reasons, it is advisable not to run an SAPinstance on a domain controller.Never perform a local installation on a domain controller.
Procedure
Local InstallationTo perform a local installation, you need to have Local Administration rights for theWindows 2000 application server. In a local installation, all Windows account and userinformation is stored locally on one host and is not visible to any other hosts in the system.
Domain InstallationTo perform a domain installation, you need to have Domain Administration rights. In adomain installation, the user information is stored centrally on the domain controller and isaccessible to all hosts in the system.
To obtain these rights the system administrator must enter you as a member of the DomainAdmins group.
Domain Installation Without Domain Administration RightsIf, for any reason, you are unable to get domain administrator rights for the installation, youcan perform the installation as a user with local administrator rights. However, you first haveto prepare this user as follows:
1. Ask the current Domain Administrator to create a new global group calledSAP_<SID>_GlobalAdmin and the following user accounts:
− SAPService<SID>
− <sid>adm
Be careful to enter SAPService<SID>, <sid>adm andSAP_<SID>_GlobalAdmin exactly as specified observing upper andlowercase. For example, for a system called C11 enter SAPServiceC11 andc11adm.
2. Once the accounts have been created:
− Assign users SAPService<SID> and <sid>adm to the newly created groupSAP_<SID>_GlobalAdmin
− Assign the user <sid>adm to the group Domain Users .
Any user with local administrator rights can now perform a domain installation withSAPinst without being a member of the Domain Admins group.
4 Installation Preparation
26 July 2002
4.7 Using the SAP System ID and Host NameUseIn the course of the installation of the central instance on IBM eServer iSeries you had tochoose an SAP system ID that identifies the whole system. For the installation of a dialoginstance on a Windows 2000 application server you have to use the same ID and enter it forthe variable <SID> or <SAPSID>. You also need to check the host name for compatibility.
You have to use the same SAP system ID you used for the installation on theiSeries. You cannot change the SAP system ID after the installation.
Procedure1. Use SAP system ID, according to the following conventions:
− It must be unique within your network.
− It must consist of three alphanumeric characters, for example, C11.
− Only uppercase letters are allowed.
− The first character must be a letter, not a digit.
2. Make sure that the host name of your system does not contain any special charactersuch as a hyphen or an underscore. In addition, the host name must not exceed 13characters in length. Otherwise, unpredictable problems might arise using the SAPsystem, especially when using the Change and Transport System.
4.8 Preparing the SAP System Transport HostUseYou need to prepare one host in the SAP system for the role of transport host. This host hasthe function of controlling the import or export of files between the current SAP system andother SAP systems (for example, a test or development system).
The transport host uses the sapmnt\trans directory to temporarily store files that havebeen exported from one system and are waiting to be imported into another system.Depending on your requirements, you can decide to use the central instance host (iSeries).
See SAP Note 360515 for more information on preparing the SAP systemtransport host.
ProcedureMap the IP address of the transport host to the alias SAPTRANSHOST using one of thefollowing methods:
• On the DNS server
If a DNS server is available for your system, ask your administrator to map the IPaddress of the transport host to the alias SAPTRANSHOST.
4 Installation Preparation
July 2002 27
The DNS server is a database that contains a set of files with information about theTCP/IP network, including the mapping of host names or aliases to IP addresses.
• In the hosts files
If no DNS server is available, you can map the IP address to the alias SAPTRANSHOST inthe hosts file. This is located in the Windows 2000 default directory:<Drive>:\WINNT\system32\drivers\etc
Open the hosts file with an editor and add the line:
<IP_address> <hostname> SAPTRANSHOST
The result of this step is to assign the alias SAPTRANSHOST to the transport host.
Copy the newly edited hosts file to all hosts where an SAP instance is to run.
If the transport host has more than one network card, take special care whenyou determine the IP address that is entered in the hosts file or on the DNSserver. Make sure you enter the main IP address and that the binding order iscorrectly defined. To check the binding order, choose:Start → Settings → Network and Dial-up Connections, then Advanced →Advanced Settings
ResultYou have configured your system so that the installation tool SAPinst can recognize thetransport host.
4.9 Preparing the Host for SAPinst GUIUseThe Java-based SAPinst graphical user interface (GUI) called SAPinst GUI requires a JavaDevelopment Kit (Java™ 2 SDK, Standard Edition) with graphical capabilities (AWT, Swing).Since IBM eServer iSeries does not provide a Graphical User Interface, you must install theJDK on a Windows host to perform the installation with SAPinst.
Prerequisites• You can find the JDK versions that are released for the SAP Web Application Server and
the SAP J2EE Engine at:http://service.sap.com/platforms
SAPinst GUI requires the same JDK version as the SAP Web ApplicationServer 6.20.The JDK is not part of the SAP shipment.
4 Installation Preparation
28 July 2002
• Make sure that your JAVA_HOME environment variable is set to<JAVA_HOME>.
• Make sure that $Java_Home/bin is included in your system path.• Make sure that your JAVA_HOME environment variable is set correctly. For more
information, see the JDK installation documentation.
• To avoid an error when starting SAPinst GUI, you must make sure that there are no .jarfiles from an XML parser tool, such as Xerces or Xalan, in the JDK ext directory, asdescribed in the procedure below.
Procedure
Checking the JDK ext Directory1. Log on to the host on which you intend to run SAPinst GUI.
2. Check whether there are already <parser_name>.jar files, for example,xerces.jar, in your ext directory. The default path under Windows is:
<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 to their original names after the installationprocedure is complete.
4.10 Preparation of Required CDs for theInstallationRequired CDs for the Dialog Instance InstallationThe following CD is required for the dialog instance installation on a Windows 2000application server:
SAP InstanceInstallation
Required CD
Dialog instanceinstallation
Kernel NT
Availability of CDsUse one of the following methods to make CDs available in parallel:
• Before the installation
Make sure you have the CD drive ready and copy the CD manually to the local hard diskon your Windows host.
4 Installation Preparation
July 2002 29
• During the installation
Use the SAPinst dialog CD Browser and check the entered location. Then copy thecontent of the entire CD to the path you entered in column Copy Package to.
CD Browser DialogDuring the installation procedure SAPinst first checks and finally verifies the availabilityand location of the required installation CD. SAPinst does this by displaying a CD Serverdialog, asking for the file LABEL.ASC that contains the information of the software package tobe installed.
SAPinst displays this dialog in the following situations:
• SAPinst wants to check the availability of the software package.
You can recognize this situation by the flag Check Location displayed on the CD ServerWindow.
You can take one of the following actions:
Action Result
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 missingLABEL.ASC (see second bullet point below).
Enter the path of the PackageLocation and leave the flagCheck Location deselected.
SAPinst skips checking the label location, butyour entered package locations are used laterfor the installation.SAPinst only asks again for a missingLABEL.ASC if the package location isincorrect (see second bullet point below).
Enter the path of the PackageLocation and select the flagCheck Package Location.
SAPinst checks the label location and displaysan error message if the location is incorrect.
If all locations are correct, SAPinst does notask again for the LABEL.ASC files later.
• SAPinst cannot find the correct LABEL.ASC but needs the location of the software toprocess 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, theinstallation cannot continue.
In addition, you can copy the installation package by entering a location in the columnCopy Package to.
4 Installation Preparation
30 July 2002
4.11 Active Directory ServicesPurposeThe Active Directory is a Windows 2000 feature that allows important information within acorporate network to be stored centrally on a server where it can easily be accessed andadministered. Storing information at one central location for the entire network has theadvantage that data only has to be maintained once and will therefore not be redundant orinconsistent.
If an Active Directory is available in the corporate network, the SAP system can be configuredto take advantage of it. An appropriately configured SAP system can read information fromthe directory and also store information there.The following explains how SAP systems can benefit from using the Active Directory and alsogives an overview of steps that are necessary to configure the system for the use of thedirectory.
The SAP system is able to interact with the Active directory on the basis ofthe LDAP protocol. This defines how communication between the SAPsystem and the directory is conducted and how data in the directory isstructured, accessed or modified. If directory types other than the ActiveDirectory also support the LDAP protocol, the SAP system can takeadvantage of the information stored there. For example, if there is an LDAPdirectory on a UNIX or Windows machine, the SAP system can be configuredso that it can use the information available there. In the following, directoriesother than the Active directory that implement the LDAP protocol are referredto as generic LDAP directories.
In the SAP environment, the information stored in an Active Directory or Generic LDAPdirectory can be exploited by:
• The LDAP Connector
• SAP Logon (planned for the future)
The LDAP ConnectorThe LDAP Connector is an ABAP interface to the Active Directory that enables SAPapplications to access and utilize information stored in the directory. For example, the LDAPConnector enables the SAP Office application to fill and update its address book data simplyby reading information from the directory. The Connector can be used by SAP applications,but also by customers that wish to develop enhancements for applications that integrateActive Directory Services.
Before the LDAP Connector can be used, it has to be installed as described in SAP Note188371.
The SAP LogonIn future, the configuration of the SAP Logon dialog box will be simplified with the help of theActive Directory. At present, after the SAP installation, the SAP logon for each front end hasto be manually configured by entering technical details on available systems. A planned SAPfeature will be able to automatically configure the logon for systems that integrate ActiveDirectory services.
For more information about the integration of the Active Directory, see the Windows SAPdocumentation: SAP Web Application Server Installation on Windows: IBM DB2 UniversalDatabase for UNIX and Windows.
5 Installation Procedures
July 2002 31
5 Installation Procedures
The structure of the installation documentation and therefore the procedure touse it has changed significantly.For more information on how to use the installation documentation, see Howto Install a Dialog Instance on a Windows 2000 Application Server [Page 10].
5.1 Input Parameters for the InstallationTo prepare for the dialog phase of the installation, we recommend that you write down theinformation you have to enter before starting SAPinst. Having the required information readyin advance helps you avoid unnecessary delays and errors.
The following tables show the prompts that are required for the dialog instance installationincluding the SAP J2EE Engine for an existing central instance:
Window Prompt Meaning
Welcome Welcome to theSystemLandscapeImplementationManager(SAPinst)
Choose SAP Web Application Server 6.20 DialogInstance for DB2 UDB on iSeries.
SAP system ID Enter exactly the name of the SAP system<SAPSID> that you have entered during thecentral instance installation.
Instance numberof the SAP dialoginstance
Enter an instance number for the dialog instance.You can specify a value from 0 to 97, except thenumbers 2, 25 72 and 89.
If more than one SAP instance is running on thesame host, both instances must be assigneddifferent numbers.
SAP systemcommonparameters
Instance numberof the SAP centralinstance
Enter exactly the instance number of the centralinstance.To find out the number, look under the SAPdirectory<DRIVE>:\usr\sap\<SAPSID>\DVEBMGS<nn>. The value <nn> is the number assigned to thecentral instance.
5 Installation Procedures
32 July 2002
Host name of theSAP centralinstance
Enter exactly the name of the central instancehost that you have entered during the centralinstance installation.To find out the host name, enter hostname at thecommand prompt of the central instance host.
Name of thedatabaseinstance
Enter exactly the name of the database instance<SID> that you have entered during the centralinstance installation.
Name of thedatabaseinstance host
Enter exactly the name of the database instancehost that you have entered during the centralinstance installation.
5 Installation Procedures
July 2002 33
SAP systemLDAPparameters
LDAP support Choose the type of LDAP integration you want toconfigure for the SAP system.
• Via Active Directory ServiceSelect this option to integrate Windows 2000Active Directory services. An Active Directorymust be available on the network.
• Via Generic LDAP DirectorySelect this option to configure the system tosupport LDAP directories that are running onWindows or UNIX machines. A generic LDAPdirectory must be available on the network.
• No LDAP SupportSelect this if you do not want to configure theSAP system to integrate LDAP services.
Required InputDepending on your selection the followinginformation is required:
• Management DomainSpecify a container in the Active Directorywhere information related to the new SAPsystem is to be stored. Use the distinguishedname syntax. The name of the container(management domain) can reflect theorganizational structure of your company. Forexample, if the system is for corporatefinances and located in Walldorf, the namecan be: CN=Finance,CN=Walldorf
Profile parameter: 1dap / saprdn
You need not specify this.
However in a large system landscape, werecommend setting this parameter to reflectthe structure of multiple SAP installations.
• Container for all SAP-related entriesSpecify the SAP root container in the LDAPDirectory under which all future informationrelated to SAP systems is to be stored. Usethe distinguished name syntax that specifiesboth the name of the container and the path toreach it.
Profile parameter: 1dap / saproot
− Via Active Directory Service:We do not recommend setting thisparameter. If you do not set thisparameter, the system automaticallycalculates the default value to storeinformation in the configuration context forActive Directory Service (ADS).
5 Installation Procedures
34 July 2002
− Via Generic LDAP DirectoryYou must specify this parameter.
• LDAP ServersEnter the DNS host name of the server onwhich the LDAP directory is running. If thedirectory is replicated on other servers in thenetwork, specify these as well. For example:ldapsrv1 ldapsrv2Profile parameter: ldap / servers.Note that the replica must be writeable.
− Via Active Directory Service:We do not recommend setting thisparameter. If you do not set thisparameter, the system automatically findsthe best ADS Server.
− Via Generic LDAP Directory:You must specify one or more LDAPservers, separated by blanks.
• Windows 2000 domain of the ADS serverDo not select this option. It does not apply toWindows 2000.
• Domain Containing group SAP_LDAPThe group was defined earlier, when the ActiveDirectory was configured for the SAP system.
Domaininformation for theSAP systemaccounts
You can choose one of the following options:
• Installation in the Domain of the Current User
• Local installation
• Installation in a different Domain
SAP instancehostinformation
RAM / Swapspace for the SAPinstance
RAM and swap space that is reserved for theSAP instance. The default value is the entireRAM or swap space.
Be sure to reserve at least the minimum valuesrequired for your instance.
Drive for SAPsystem directory
Enter the drive for the SAP base directory tree.
For example, if you select D:, the directory\usr\sap is created under drive D.
SAP systeminstancedirectories
Host withtransport directory
Enter the name of the host where the centraltransport directory is located.
5 Installation Procedures
July 2002 35
SAP systemadministrator(<sid>adm)
• The User ID must be the same as the one ofthe central instance.
• This password must match the password for<sid>adm on the database host.
Userinformation
CD Browser:Location of theinstallation CDs
This dialog only appears if the system wants tocheck or cannot find the file LABEL.ASC thatcontains the relevant installation information.
Depending on the required installation CD,specify the path to the directory where thecorresponding file LABEL.ASC is located:
• CD Kernel <SAP Component>:Enter the path/drive of the SAP Kernel CD(default value).
• CD J2EE-JAVA-COMPONENTS, folder J2EE-ENG:Enter the path to the directory J2EE-ENG onthe SAP J2EE CD (for example, D:\J2EE-ENG).
• CD J2EE-JAVA-COMPONENTS, folder SDM:Enter the path to the directory SDM on the SAPJ2EE CD.
• CD J2EE-JAVA-COMPONENTS, folderWAPSCOMP:Enter the path to the directory WAPSCOMP onthe SAP J2EE CD.
SAP systemservice ports
Enter the port number of the Message ServerPort.
The port number of the MessageServer Port must be the sameas the one on the central instancehost.
5 Installation Procedures
36 July 2002
Maximummemory, the SAPJ2EE Engine willuse
Enter the maximum memory in MB.SAP J2EEEngine
SAP J2EE Enginecommunicationuser SAPJSFinformation
To prepare the installation, you have created thecommunication user SAP JSF in your productionclient that is required for the user authenticationfor RFC communication between the J2EEservice Security and the SAP Web ApplicationServer.
• Client:Enter the SAP system client in which youcreated the communication user SAPJSF.
• Password:Enter and confirm exactly the Password youhave entered during the creation of thecommunication user SAPJSF.
Location ofthe Javadevelopmentkit
JDK directory Enter the location where the Java DevelopmentKit (JDK) is installed on your host.
5.2 Running SAPinstUseYou use this procedure to run SAPinst to install a dialog instance on a Windows 2000application server.
Prerequisites• If you start the SAPinst GUI on your host, make sure that the JAVA_HOME environment
variable is set correctly.
• As the SAPinst installation directory contains important log and command files for theinstallation, we recommend that you start SAPinst from the kernel CD for every dialoginstance you are going to install. Otherwise, you might lose previous log and commandfiles stored in the SAPinst installation directory.
Before you start the installation, be aware of the following:
− When you install a dialog instance with SAPinst for the very first time on a host, youhave to start SAPinst from the Kernel CD with the setup.cmd command. SAPinstis copied to the directory you have specified. This directory is also used as theinstallation directory for the instance you are installing. Afterwards, you can use theWindows Start menu to install additional dialog instances on the same host.
− If you want to install a dialog instance on the host where a previous dialog instancehas not been successfully installed, you must run SAPinst again from the Kernel CDto create a new installation directory for the SAPinst log and command files.
5 Installation Procedures
July 2002 37
− For every additional dialog instance that you want to install on the same host or fordeployment of the Java core central instance (after successful installation of anotherinstance), we recommend that you start SAPinst from the Kernel CD. By doing so,you make sure that every instance installation has its own log and command files.
Alternatively, you can start the new installation by entering:
a. Start → Programs → <menu_entry> → Prepare New Installation
b. Start → Programs → <menu_entry> → SAPinst server with GUI
Be aware that the installation directory of the previously installed instance onthat host will be overwritten when you use the Start menu to start the newinstallation. For this reason, you should only use it if you are sure that you donot need the log and command files of the previously successfully installedinstance.
• If you want to perform a remote installation – that is, SAPinst GUI is started on anotherhost to monitor the installation – you do not need to set the JAVA_HOME environmentvariable on your instance host. This section describes a standard, that is, a localinstallation.
• Make sure you have installed Client Access Express for IBM eServer iSeries. Forinformation on how to install Client Access Express for IBM eServer iSeries, seeRequirements Checklist for a Dialog Instance [Page 19].
Procedure1. Log on to your host as a user who is a member of the local administration group.
2. Insert the Kernel CD 1 in your CD drive.
3. Run Setup.cmd from the following path:
<CD drive>:\SAPinst\NT
SAPinst uses the ports 21212 and 21213 during the installation forcommunication with SAPinst GUI. You get an error message if one of theseports is already in use. In this case, you must do the following:
a. Copy directory SAPINST/NT from the Kernel CD to your local harddisk.
b. In file SAPINST/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 ports60000 and 60001
d. Run Setup.cmd from your local hard disk.
5 Installation Procedures
38 July 2002
SAPinst asks if you want to perform a Standard or Custom installation.
If you choose a Custom installation you can define:
− Installation directory for SAPinst
You can choose any name for the installation directory. In this documentation,<SAPinst_INSTDIR> refers to the installation directory.
− SAPinst folder in the Start menu
The Start menu entry is used to create unique Start menu entries.For example, you enter the following for the Start menu during the installation:Dialog InstanceThen SAPinst creates the following Start menu:Start � Programs � Dialog Instance � …
− Connection parameters (not relevant for a local installation)
4. Select Standard or Custom and choose Next.
SAPinst is now copied to your <SAPinst_INSTDIR> and the Start menu entries arecreated, as shown in the following table:
Start Menu EntryStart ���� Programs ����<menu_entry> ����
Description
Prepare New Installation Prepares SAPinst to install an additional instance on this host.
Current log and command files are copied to a backupdirectory (under the current SAPinst directory) indicating thedate 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 forparameters (host and port) to connect to the SAPinst serverhost.
SAPinst server only Only relevant for a remote installation.Starts SAPinst server only and waits for connection to theSAPinst GUI
SAPinst server with GUI Starts SAPinst server and SAPinst GUI. The Welcome screenis displayed and you can perform the installation.
5. If SAPinst prompts to reboot your system, shut down any SAP instance running on thishost and reboot.
In this case, you do not have to restart your SAP system after the reboot until SAPinstprompts to do so (see below).
5 Installation Procedures
July 2002 39
6. To start the installation with SAPinst choose Start � Programs � <menu_entry> �SAPinst server with GUI
SAPinst uses the ports 21212 and 21213 during the installation forcommunication with SAPinst GUI. You get an error message if one of theseports is already in use. In this case, you must do the following:
a. Open a command prompt.b. Change to your <SAPinst_INSTDIR> and run:
.\sapinst.exe SAPINST_DIALOG_PORT=<port>where <port> is an unused port on your host.
The SAPinst GUI now starts and the Welcome screen is displayed.
7. Select SAP Web Application Server 6.20 Dialog Instance for DB2/AS400 and chooseNext.
8. Accept the License Agreement for STL port.
9. Enter the SAP system ID and select the instance you want to install.
10. Choose Next.
11. Follow the instructions in the SAPinst dialogs.
If you have entered all required information during the input phase, SAPinst starts theinstallation and displays installation progress during the processing phase.
Troubleshooting• If an error occurs during the input phase, SAPinst:
− Stops the installation.
− Displays a dialog informing 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:
− Stops the installation.
− Displays a dialog informing 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.
− Abort the installation by choosing O.K.
See also Continuing an Interrupted Installation with SAPinst [Page 52].
6 Post-Installation Activities
40 July 2002
6 Post-Installation Activities
The structure of the installation documentation and therefore the procedure touse it have changed significantly for the installation of a dialog instance on aWindows 2000 application server. You must read How to Install a DialogInstance on a Windows 2000 Application Server [Page 10] before performingthe post-installation activities.
6.1 Downloading the SAP Java Crypto ToolkitUseYou require the SAP Java Crypto Toolkit, if:
• You want to configure Client SSL (Secure Sockets Layer) for the combined (that is,ABAP and J2EE) SAP Web Application Server and/or
• You want to make Java encryption functions available for the SAP Web ApplicationServer.
Procedure1. For the operation of the SAP J2EE Engine, you require the SAP Java Crypto Toolkit.
For more information, see the SAP Service Marketplace at:http://service.sap.com/swcenter � SAP Cryptographic Library.
The SAP Java Crypto Toolkit offered for downloading in the SAP ServiceMarketplace is subject to export control regulation in Germany as the countryof origin and import regulation of your own country. SAP may not yet have acorresponding export license for your user / company.
2. After you have downloaded the SAP Java Crypto Toolkit files, copy them to the followingdirectories:
If you use the standalone version of the SAP J2EE Engine:
6.2 Installing Borland JBuilderFor Remote Support from SAP, you require Borland JBuilder 5 Enterprise on any Windowshost in your SAP system landscape, for example on a programmer's workstation.
You can download Borland JBuilder from http://www.borland.com.
6.3 Installing a JDBC DriverUseIf the SAP J2EE Engine is used in a scenario in which it has to connect directly to adatabase, you have to install a database-specific JDBC (Java Database Connectivity) driver.
PrerequisitesMake sure that you have installed the following software on both your database server andthe SAP J2EE Engine host:
• IBM Toolbox for Java (license program 5722JC1)
• TCP/IP Connectivity Utility for AS/400 (license program 5722TC1)
• Java Development Kit 1.3.1 (licensed program 5722JV1, option *BASE and option 5)
6 Post-Installation Activities
42 July 2002
Procedure1. Make sure that the SAP system is not up and running (stopsap).
2. Log on to the database host and to the SAPJ2EE Engine host as user QSECOFR.
3. On the database server, check that the QUSER profile is enabled. Enter:
DSPUSRPRF(QUSER)
4. The DDM TCP/IP server and DATABASE and SIGNON host servers need to be startedat IPL. Add the following to the startup script identified by the QSTRUPPEM systemvalue:
• To start the TCP/IP server, enter:STRTCPSVR SERVER(*DDM)
• To start special host servers, enter:STRHOSTSVR SERVER(*DATABASE *SIGNON) RQDPCL(*TCP)
5. Copy the JDBC driver to a temp directory on your Windows host from:\\<db_host>\qibm\proddata\HTTP\Public\jt400\lib\jt400.jar
6. Restart your SAP system (startsap).
7. Start the SAP J2EE Engine Administrator from a Windows host. You can do one of thefollowing:
− Use the command line and enter:<J2EE_drive>:\usr\sap\<SAPSID>\<instance_name>\j2ee\admin\go.bat
− Choose the following from the Windows Start menu:
Programs → SAP J2EE Engine 6.20 → Instance <instance_number> →Administrator
8. Log on to your SAP J2EE Engine host as user Administrator.
9. In the navigation frame of the SAP J2EE Engine Administrator, choose Services → DBPool.
10. Choose Add Driver.
11. Enter the class name of the driver:com.ibm.as400.access.AS400JDBCDriver
12. If required, specify the path to the JDBC driver in the temp directory that was copied instep 5.
If you want to add a DB pool (a symbolic connection to the database (datasource)) using the above installed JDBC driver, you must specify thedatabase URL as follows: jdbc:as400://<database_server>
6 Post-Installation Activities
July 2002 43
6.4 Starting and Stopping the SAP SystemUseYou use this procedure to check that you can start and stop the SAP system after theinstallation. You use the Microsoft Management Console (MMC) to start and stop the SAPsystem.
PrerequisitesYou have logged on to the SAP system host as user <sid>adm.
Procedure
The newly installed MMC only allows you to start or stop the SAP systemlocally on the host that you are logged on to. Later you can configure theMMC to enable central management of all hosts.For more information, see the SAP Library:a. Choose Help → SAP Library in your SAP system.b. Choose mySAP Technology Components → SAP Web Application Server
→ Computing Center Management System → Monitoring in the CCMS→ Microsoft Management Console: Windows
Alternatively you can access the SAP Library at http://help.sap.com:a. Choose SAP Web Application Server → SAP Web Application Server
6.20.b. Select the required language.c. Choose mySAP Technology Components → SAP Web Application Server
→ Computing Center Management System → Monitoring in the CCMS→ Microsoft Management Console: Windows
Starting the Dialog Instance1. On the Windows 2000 host, choose Start → Programs →=SAP System Management
Console.
2. In the tree, select the node representing the dialog instance.
3. Access the context menu by click the right mouse button.
4. Choose Start.
The SAP dialog instance is started.
Stopping the Dialog InstanceProceed as follows on each Windows 2000 host where you want to stop a dialog instance ofthe SAP system:
1. Choose Start → Programs →=SAP System Management Console.
2. In the tree, select the node representing the dialog instance.
3. Access the context menu by clicking the right mouse button.
4. Choose Stop.
6 Post-Installation Activities
44 July 2002
6.5 Logging on to the SAP SystemUseThis section describes how to log on your Windows 2000 application server after theinstallation.
PrerequisitesYou have already started the SAP system and installed a front end.
There are two standard users in the SAP system after the installation:
User Initial Password Clients where User ExistsSAP* 06071992 000, 001, 066
DDIC 19920706 000, 001
Procedure1. To start SAP Logon:
− SAP GUI for Windows:On the machine, where you have installed the front end, choose Start → Programs→= SAP Frontend<Release> →=SAPlogon
− SAP GUI for Java:Invoke the script guilogon from the GUI installation directory without arguments.
The SAP Logon dialog box opens.
2. Create a logon entry for the newly installed system:
a. Choose New.
b. Enter the following data:
Field Description
Description ofsystem
Give a meaningful description, for example, the host name of the centralinstance or the SAP system ID.
ApplicationServer
Specify the name of the central instance host
Systemnumber
Specify the number you entered for the central instance during theinstallation.
When you choose OK, the SAP Logon dialog box reappears and now includes an entryfor the new system.
3. Double-click the new system entry.The logon screen for the SAP system appears.
4. Log on as a user defined on the database instance or use a default user (SAP* or DDIC).
6 Post-Installation Activities
July 2002 45
6.6 Checking SAP System ServicesUseThis section describes how to check SAP system services. This helps you to solve initialproblems that you might experience when trying to log on or run the system for the first time.
Procedure1. Log on to the SAP system [Page 44]. If you have trouble logging on, or subsequently
experience problems trying to run the system, look at the following files located indirectory \usr\sap\<SID>\D<no>\WORK\:
− dev_ms (central instance only)
− dev_disp
− dev_w0
− dev_rd
2. Call transaction SM50 to check services.
The services available for the instance are displayed, that is, dialog, update, batch andspool. If the services are not displayed look at the files listed under no.1 to get moreinformation.
3. Call transaction SM51 to check all available instances with their services.
A list of all available instances is displayed.
If the display is OK, double-click one instance to display the services available for thatinstance. If the display is empty, look at the files listed under no. 1 to get moreinformation.
4. Call transaction SM21 to check the system log.
6.7 Configuring Windows Transport SystemsUseSome command line functions of the transport program tp.exe do not work, for exampleshadow buffers. You have to correct the transport profile.
When using tp.exe from the command prompt, it is necessary to modify the transportconfiguration profile to indicate the transport directory in NETBIOS naming convention.
PrerequisitesYou have configured the domain controller in the Transport Management System (TMS). Formore information, see Configuring the Transport Management System in the installationdocumentation SAP Web Application Server Installation: IBM eServer iSeries (and AS/400).
6 Post-Installation Activities
46 July 2002
ProcedureModify the TP_DOMAIN_<SID>.PFL file on the iSeries in the /sapmnt/trans/bindirectory.
Access from Windows 2000:
\\<saptranshost>\saptext\trans\bin\ and then sappad.exe
Sappad.exe can be found in the SAP executable directory.
Access from the SAP System1. Call transaction STMS.
The Transport Management System screen appears.
2. Choose System overview.
The System Overview: Domain <DomainName> screen appears.
3. Double-click the system in which you want to perform the changes.
The Display TMS Configuration: System <SID> screen appears.
4. Choose Transporttool and then Display<-> Change.
6.8 Secure Single Sign-OnPurposeSingle Sign-On is a method of logging on to the SAP system that simplifies the logonprocedure without reducing security. When a system has been configured for Single Sign-On,an authorized user who has logged on to the operating system can access the SAP systemsimply by selecting it in the SAP logon window or clicking on the shortcut. Work in theapplication can begin immediately without first entering an SAP system user name andpassword. Single Sign-On is a quick method of logging on to the system and has theadvantage that it is easy to administer because it significantly reduces the work associatedwith SAP system user management.
6 Post-Installation Activities
July 2002 47
PrerequisitesAn essential prerequisite for enabling Single Sign-On is the assignment of the SAP systemuser to the Windows user that is normally entered to log on to the operating system. Oncethis assignment has been made and the system prepared accordingly, the user logging on tothe operating system is always automatically associated with the assigned SAP system user.As a result, the system recognizes that the rights and authenticity of the SAP system userneed to be verified, without explicitly requiring the entry of the user name and password.
FeaturesWhen a Windows user has logged on successfully, the SAP GUI gets the security context forauthentication through the GSS-API interface. The security context is then passed on to theapplication server where it is verified. The GSS-API interface (Dynamic Link Librarygssapi32.dll) is delivered together with the SAP system and enables the use of thenative security functionality offered by the Microsoft Security Support Provider Interface(SSPI).
We particularly recommend the configuration of Single Sign-On when strict guidelines areapplied to the syntax and expiration period of user passwords. The resulting user andpassword administration is often complex and can be reduced effectively by implementingSingle Sign-On.
IntegrationFor information on how to improve the security of your system with the help of third-partyproducts, see the SAP Online Documentation on Secure Network Communications in theSAP Library at http://help.sap.com
In the SAP Library, choose SAP Web Application Server → Security → Secure NetworkCommunications (SNC).
Process FlowTo enable the use of Single Sign-On you need to:
1. Prepare the application server [Page 47]
2. Prepare SAP GUI and SAP Logon [Page 48]
3. Map SAP system Users to Window Users [Page 49]
Map SAP system users to Windows usersBefore you begin, you must start the Service Windows LM Security Support Provider:
2. Select the service NT LM Security Support Provider.
3. On the General tab, change the startup type from manual to automatic.
6 Post-Installation Activities
48 July 2002
6.8.1 Preparing the Application Server for SingleSign-OnUseThis procedure is required to set up Single Sign-On.
Prerequisites1. Copy the gssapi32.dll file from the Kernel CD to the directory
<DRIVE>:\USR\SAP\<SID>\SYS\EXE\RUN on the dialog instance of your applicationserver. The gssapi32.dll file is located on the Kernel CD in the directory<CD_DRIVE>:\NT\I386\.
2. In the profile of the dialog instance, enter the following SAP parameters:snc/accept_insecure_cpic =1
(<DOMAIN_NAME> is the domain that the user <sid>adm belongs to.)
snc/r3int_rfc_secure =0
3. Stop and restart the SAP system to activate the profile parameters.
6.8.2 Preparing SAP GUI and SAP Logon for SingleSign-OnUseThis procedure is required to set up Single Sign-On.
PrerequisitesYou have completed preparing the application server for Single Sign-On [Page 47].
Procedure1. Copy the gssapi.32dll file from the Kernel CD to the SAP GUI directory.
2. Set the Windows environment variable SNC_LIB on the PC where your SAP GUI runs.The variable specifies the path to the gssapi.32dll file.
6 Post-Installation Activities
July 2002 49
3. To do this:
a. Choose Start → Settings → Control Panel → System → Environment.
b. In User Variables for <user> enter the following:
Variable: SNC_LIB
Value: <DRIVE>:\<SAPGUI_PATH>\gssapi32.dll
c. Choose Set and confirm your entries with OK.
4. Log off and then log on to your Windows system again, as the same user, to activate thenew environment variable setting.
5. Set the required logon options to activate Single Sign-On.
a. In the SAP logon window, choose Edit and in the window that opens, Advanced.
The Advanced Options dialog box appears.
b. In the SNC name field, enter:p:<DOMAIN_NAME>\<sid>adm
<DOMAIN_NAME> is the domain the user <sid>adm belongs to.
The administrator of the system HWA, belonging to the domain DEC_NT, wouldenter:P:DEC_NT\HWAADM
6. Select Enable Secure Network Communications and confirm the entries with OK.
ResultThe SAP Logon window now displays an icon with a key beside the system entry. Thisindicates that Single Sign-On is active. The next time an SAP system user that has beenassigned to a Windows user logs on to the system, the application is opened withoutrequiring the entry of a user name and password.
6.8.3 Mapping SAP System Users to Windows Usersfor Single Sign-OnUseWhen you have configured your system, you can enable SAP system users to log on withSingle Sign-On by assigning them to Windows users.
PrerequisitesYou have completed the following procedures:
• Preparing the Application Server for Single Sign-On [Page 47]
• Preparing SAP GUI and SAP Logon for Single Sign-On [Page 48]
3. Enter the name of the SAP system user and choose User names → Change.
4. Choose the SNC tab. In the field SNC name, enter the name of the Windows user that isto be assigned to the SAP system user in uppercase:p:<DOMAIN_NAME>\<NT_USERNAME>
DOMAIN_NAME> is the Windows domain that the user belongs to and <NT_USERNAME>the Logon ID of the Windows user.
For the user Walker, belonging to the domain SAP_ALL, enterp:SAP_ALL\Walker
5. Select Insecure communication permitted. This permits the user to still access the systemwithout using the Single Sign-On feature, to work in a different domain.
6. Save the entries.
6.9 Performing a Backup of the Dialog InstanceUseWe recommend that you perform an offline backup of your dialog instance at the end of theinstallation.
PrerequisitesYou have stopped the following:
• The SAP system (in this case the dialog instance)
• The SAP-related services (SAP<SID>_<instance> and SAPOSCOL)
ProcedureLog on as user <sid>adm and shut down the SAP system.
1. To save the Registry:
a. Choose Start =→=Programs → Accessories → System Tools → Backup
b. Click Emergency Repair Disk.
The Emergency Repair Diskette dialog box appears.
c. Select Also Backup the Registry to the Repair directory
When you confirm your entry the Registry is written to diskette.
6 Post-Installation Activities
July 2002 51
2. Save the System State Data:
a. Choose Start → Programs → Accessories → System Tools → Backup.
b. Click Backup Wizard.
c. On the Backup Wizard dialog box, select Only backup the System State Data andchoose Next.
d. Specify the Backup media type and the destination of the backup. Choose Next.
e. Check the information on the dialog box and then choose Finish to start the backup.
3. Back up all SAP-specific and all database-related directories:
a. Choose Start → Programs → Accessories → System Tools → Backup.
b. Click Backup Wizard.
c. On the What to Back up dialog box, select Backup selected files, drives or networkdata and choose Next.
d. On the Items to Back Up dialog box, select the Windows NT directory and all SAPand database-related directories, including:\USR\SAP
<HOMEDIR> of <sid>adm
\WINNT
Choose Next.
e. On the Where to Store the Backup screen, specify the media type and destination forthe backup.
f. Check the information displayed and then choose Finish to start the backup.
7 Additional Information
52 July 2002
7 Additional Information
7.1 Continuing an Interrupted Installation withSAPinstUseAs SAPinst does not abort the installation in error situations, you can continue an interruptedinstallation if:
• You have not canceled the installation.
• You have already canceled the installation.
Procedure• You have not canceled the installation.
The error dialog box is still displayed and SAPinst is waiting for your input.
Proceed as follows:
In the error dialog box, choose Retry.
SAPinst now retries the installation step.
• You have already canceled the installation.
That is, the installation was aborted and you want to continue it. Since SAPinst recordsthe installation progress in the keydb.xml file, it can continue the installation from thefailed step without repeating previous steps.
You have two alternatives:
a. Continue the installation.
b. Restart the installation from scratch, that is, start the installation with the keydb.xmldefault file as delivered.
These two alternatives are described below.
In some cases, you must uninstall installed components, before you repeatthe installation from scratch. For example, this applies to an SAP systeminstallation. For more information, see the uninstallation description in thecorresponding installation guide.
Continuing the Installationa. Check if an SAPinst GUI Java process is still running, and if so, delete it by looking
for javaw.exe under Processes in your Task Manager.
b. Choose Start→Programs→<menu entry>→SAPinst Server with GUI (or SAPinst GUIif you want to start the GUI only or SAPinst Server only if you want to start SAPinstwithout the GUI).
7 Additional Information
July 2002 53
Restarting from the Beginninga. Check if an SAPinst GUI Java process is still running, and if so, delete it by looking
for javaw.exe under Processes in your Task Manager.
b. Choose Start→Programs→<SAPinst...on<iSeries_name>→Prepare New InstallationCurrent log and command files are now copied to a backup directory that indicatesthe date and time of the backup:<SAPinst_dir>\log<month>_<date><time>
c. Choose Start→Programs→<menu entry>→SAPinst Server with GUI (or SAPinst GUIif you want to start the GUI only or SAPinst Server only if you want to start SAPinstwithout the GUI).
7.2 Additional Information about the SAP J2EEEngine
For more information, see the SAP Library:a. Choose Help � SAP Library in your SAP system.b. Choose mySAP Technology Components → SAP Web Application
Server → SAP J2EE Engine.
Alternatively you can access the SAP Library at http://help.sap.com:a. Choose SAP Web Application Server → SAP Web Application Server
6.20.b. Select the required language.c. Choose mySAP Technology Components � SAP Web Application
Server � SAP J2EE Engine.
File System Structure of the SAP J2EE Engine InstallationAfter the installation of the SAP J2EE Engine, the following file system structure applies forthe SAP J2EE Engine (j2ee) and its Software Delivery Manager (sdm, see section TheSoftware Delivery Manager below):
7 Additional Information
54 July 2002
/ or <DRIVE>
usr
sap
<SAPSID>
j2ee sdm
... ...
/ or <DRIVE>
usr
sap
<SAPSID>
<Instance Name>
j2ee
...
Central Instance Dialog Instance
<Instance Name>
For example, the file system structure may look as follows:• On a central instance with SAP system ID C11 and instance name
DVEBMGS00 on UNIX, the SAP J2EE Engine is installed to/usr/sap/C11/DVEBMGS00/j2ee and the corresponding SDM isinstalled to /usr/sap/C11/DVEBMGS00/sdm.
• On a dialog instance with instance name D01 on Windows, the SAPJ2EE Engine is installed to c:\usr\sap\C11\D01\j2ee. No SDMis installed.
Ports Used by the SAP J2EE EngineThe ports used by the SAP J2EE Engine are listed in the file prepconf.log located in theinstallation directory of the SAP J2EE Engine (see section above).
Administration of the SAP J2EE EngineYou can administrate the SAP J2EE Engine from within the SAP Web Application Server.
To administrate the SAP J2EE Engine:
1. Call transaction SMICM in the SAP Web Application Server.
2. Choose Administration � J2EE-Server.
The following functions are available:
• Send soft shutdown (with / without restart)
• Send hard shutdown (with / without restart)
• Set the restart flag of the SAP J2EE Engine.
7 Additional Information
July 2002 55
For more information, see the SAP Library:a. Choose Help → SAP Library in your SAP system.b. Choose mySAP Technology Components → SAP Web Application
Server → SAP J2EE Engine.
Alternatively you can access the SAP Library at http://help.sap.com:a. Choose SAP Web Application Server → SAP Web Application Server
6.20.b. Select the required language.c. Choose mySAP Technology Components → SAP Web Application
Server → SAP J2EE Engine.
Deactivation of the SAP J2EE EngineAfter the installation, the SAP J2EE Engine is activated. If you do not want to use the SAPJ2EE Engine, you can deactivate it by setting the parameter rdisp/j2ee_start to 0 in theinstance profile of every installed SAP instance:
• On UNIX, log on as user root and edit the file<sapmnt>/profile/<SAPSID_INSTANCENAME_HOSTNAME>
• On Windows, edit the file <DRIVE>:\usr\sap\<SAPSID>\sys\profile\<SAPSID_INSTANCENAME_HOSTNAME>
• On IBM eServer iSeries, edit the file\\<Central Host> \sapmnt \<SAPSID>\profile \
<SAPSID_INSTANCENAME_HOSTNAME>
The following is an exemplary extraction of an edited UNIX instance profile:. . .rdisp/max_priv_time = 0rdisp/j2ee_start = 0exe/j2ee = /usr/sap/MB2/DVEBMGS45/j2ee/cluster/
The Software Delivery ManagerEvery SAP J2EE Engine on a central instance and every SAP J2EE Engine installedstandalone requires a Software Delivery Manager (SDM). SDM is a tool with which you canmanage and deploy software packages that you receive from SAP.
To manage and deploy SAP applications in programming languages otherthan ABAP, the SDM is integrated into the SAP installation tool SAPinst.Therefore, the current section only contains background information.
7 Additional Information
56 July 2002
Software Delivery Catalog (SWC)
The software packages are delivered in a Software Delivery Catalog (SWC). The SWCcontains the meta descriptions of its Software Delivery Archives, which it bundles as logicaldeployment units.
Software Delivery Archive (SDA)
The Software Delivery Archive (SDA) is the delivery format for SAP applications inprogramming languages other than ABAP. It is a ZIP-compatible archive format that can beused as a container for other archives. The SDA contains the manifest information of itsarchives (such as jar, war, ear) and an SAP manifest, which contains additional softwarelogistics information.
SDAs can be nested recursively, with the manifest information being passed on to the SDA atthe highest level.
An SDA that does not contain any other archives is an atomic SDA. This is also the smallestunit that you can deploy on a local host. Furthermore, the SDA is the smallest unit for whichpatches can be created and delivered.
Deployment
The deployment is the final step in the software delivery process; it involves the deploymentof available software packages - Software Delivery Archives (SDAs) - in the runtimeenvironment of the SAP systems.
When deploying SDAs, the Software Delivery Manager stores the data in the SDMRepository, where it then manages the installed archives. The SDM recognizesdependencies between archives and provides support when you install and maintain sharedapplications.
7.3 Deleting a Dialog InstanceUseYou can remove the dialog instance with the help of a wizard.
PrerequisitesThe dialog instance must be stopped.
Procedure1. Log on as user <sid>adm.
2. Choose Start → Settings → Control Panel → Add/Remove Programs.Scroll to the SAP entries.
Each dialog instance that is installed on the computer is listed with an entry ofthe form: SAP Application Server for System <SID>instance
3. Select the instance you want to delete from the list and choose Change/Remove.
The welcome window of the SAP Uninstall Wizard opens.
7 Additional Information
July 2002 57
4. Choose Next.
A dialog box appears allowing you to select an uninstall method:
Uninstall Method Description
Complete Select this to remove all the SAP instances that are installed on thelocal computer. Note that this includes all the SAP instances initiallylisted in the Add/Remove Programs Properties dialog box, regardless ofthe highlighted selection.Choose Finish to start the deletion.
Select Custom and choose Next to access the Select Componentsdialog box that allows you to mark the instances you want to remove.
In the Select Components dialog box, use the check box beside aninstance to indicate whether only the instance involved or the entiresystem, with global accounts, is to be deleted.
Uninstall instance-independent components
Select this additional option, if there is no other SAP system on the localmachine. In this case directories such as usr\sap are also deleted.
Add
Choose to manually add instances you want to delete if they do notappear on the list.
Custom
Finish
Choose to start the deletion.
The wizard informs you when the SAP system or selected instances have been deletedsuccessfully.
7.4 SAP System Security on WindowsIn a standard SAP system installation, all steps relevant for security are automaticallyperformed by SAPinst. Although SAPinst ensures that the system is protected againstunauthorized access, it is nevertheless important for the system administrator to ensure thatno breaches of security can occur.
Distributed SAP systems with multiple application servers have to be installed in a Windowsdomain to ensure central and straightforward administration of the SAP system. The followinggives you an overview of the user accounts and groups that SAPinst creates during a domaininstallation.
User AccountsSAPinst creates two accounts for SAP system administration:
• <sid>adm
SAP system administrator account that enables interactive administration of the system.
7 Additional Information
58 July 2002
• SAPService<SID>
(This user is created for iSeries installations but it is not used. User <sid>adm is usedinstead)
GroupsSAPinst creates two groups during a domain installation.
• SAP_<SID>_GlobalAdmin
This global group is a domain-level SAP administration group for organizing SAP systemadministrators. The only function of a global group is to gather users together at thedomain level so that they can be placed in the appropriate local groups.
• SAP_<SID>_LocalAdmin
Only local groups are created and maintained on an application server. A local group canonly be given permissions and rights to the system where it is located. The system is partof a particular domain, and the local group can contain users and global groups from thisdomain.
• SAP_LocalAdmin
This group is created on all hosts, but is particularly important for the transport host.Members of the group have Full Control over the transport directory (usr\SAP\trans)that allows transports to take place between systems.
The SAP_<SID>_GlobalAdmin groups of all the SAP systems that are part of thetransport infrastructure are added to the SAP_LocalAdmin group. As a consequence,users <sid>adm and SAPService<SID> of all systems in the transport infrastructureare members of the SAP_LocalAdmin group and have the authorizations necessary toinitiate and execute transports.
7 Additional Information
July 2002 59
SAP DirectoriesSAPinst protects SAP directories under usr\SAP\<SID> by only granting group<SID>_local\administrators full control over these directories.
The following graphic illustrates the user accounts and groups created by SAPinst in asystem infrastructure consisting of two SAP systems.
User Groups and Accounts
Application server
Full control
Local Group
member of
member of
Domain
Users
Users:<sid_1>admSAPService<SID_1>
Global Group
SAP_<SID_1>_GlobalAdmin
SAP_<SID>_LocalAdmin
Users
Users:<sid_2>admSAPService<SID_2>
member of
Global Group
SAP_<SID_2>_GlobalAdmin
usr\sap\<SID>
TransportHost
Full control
Local Group
SAP_LocalAdmin
usrsap
transprfclog
member of
System 1 System 2
An access control list (ACL) controls the access to the SAP system objects.To ensure a secure system, only the local group SAP_<SID>_LocalAdmin,the group Administrators and the account SYSTEM are members of allSAP system object ACLs.
7 Additional Information
60 July 2002
7.4.1 Automatic Creation of Accounts and GroupsPurposeDuring the installation, SAPinst automatically creates the accounts and groups required forthe operation of the SAP system.
FeaturesThe following graphic gives an overview of the steps carried out by SAPinst to create theusers and groups for a domain installation.
SAP Administrator :SAP Service Account:
Creation of SAP Domain User AccountsCreation of accounts<sid>admSAPService<SID>
Creation andmodification ofglobal group in thedomain
Creation ofGlobal Group : SAP_<SID>_GlobalAdmin
Addition of <sid>adm and SAPService<SAPSID>to group SAP_<SID>_GlobalAdmin
Addition of <sid>adm andSAPService<SID> to the Windows 2000local Administrators Group
Creation and modification of local group on each application server
Creation of a local group on the application serverLocal Group : SAP_<SID>_LocalAdmin
Addition of the global groupSAP_<SID>_GlobalAdmin to the local groupSAP_<SID>_LocalAdmin
Creation of a local group on the applicationserverLocal Group : SAP_LocalAdmin
Addition of the global groupSAP_<SID>_GlobalAdmin to the local groupSAP_LocalAdmin on the application server
Addition of <sid>adm to the Windows 2000Domain Users group.
7 Additional Information
July 2002 61
Assignment of rightsfor the SAPdirectories
For Administrators and SAP_Local Admin
groups assignment of Full Control over: usr
usr\sap
usr\sap\trans
\usr\sap\prfclog
For Administrators andSAP_<SID>_LocalAdmin groupsAssignment of Full Control over:usr\sap\<SID>
7.4.2 Performing a Domain Installation as LocalAdministratorUseThe installation of SAPinst and the SAP system must be performed by a user that is adomain administrator. If, for any reason, you are unable to grant a user domain administratorrights, it is possible to perform the installation as a user with local administrator rights.However, the system has to be prepared appropriately. A new global group,SAP_<SID>_GlobalAdmin, and two new users, SAPService<SID> and <sid>adm, haveto be created. The new users must be added to the SAP_<SID>_GlobalAdmin group.
PrerequisitesThe actions described must be performed by a domain administrator.
Procedure
Creating the New GroupTo create the SAP_<SAPSID>_GlobalAdmin group:
1. Log on as domain administrator.
2. To start the Active Directory Users and Computers Console, choose:
Start →=
==
=Programs → Administrative Tools → Active Directory Users and Computers
If you cannot find Active Directory Users and Computers, start it as follows:a. Choose Start → Run and enter mmc.b. Choose Console → Add/Remove Snap-in... and choose Add.c. Choose Active Directory Users and Computers.d. Choose Add.e. When finished, choose Close and then OK.
7 Additional Information
62 July 2002
3. In the tree on the left, right-click on the Users folder and choose:
New → Group
4. Enter the following:
Group name: SAP_<SAPSID>_GlobalAdmin
Group name (pre-Windows 2000): SAP_<SAPSID>_GlobalAdmin
5. Select the following:
Group scope: Global
Group type: Security
6. Choose OK.
Creating the New UsersCreating the SAP System User <sapsid>adm1. In the Active Directory Users and Computers Console right-click on the Users folder in
the tree on the left and choose:
New →→→→ User
2. Enter the following:
Field name Entry
First name: None
Initials: None
Last name: None
Full name: <sapsid>adm
User logonname:
<sapsid>adm
User logon name(pre-Windows2000):
<sapsid>adm
Enter the <sapsid>adm user in lower case.3. Choose Next and enter the following:
Password: <password>
Confirm password: <password>
Make sure that no other options are selected.4. Choose Next and then Finish.
7 Additional Information
July 2002 63
Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group1. In the Users folder select the newly created user account in the list on the right and
double-click it.
2. Select the Member of tab.
3. Choose Add.
4. Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to thelist on the bottom. By default, the user is also a member of the Domain Users group.
5. Choose OK twice.
7.5 Changing the Password for User <sid>admUseYou use this procedure to change the password for <sid>adm.
Your SAP system connects to the database as user <sid>adm. The encrypted password ofuser <sid>adm is stored in a password file in the global profile directory on your iSeries. TheSAP system gets the profile names and the password from this file, decrypts thepassword, and then connects to the database.
DB2 UDB for iSeries uses the authorization mechanism of the operating system. Thereforethe password stored in the password file must always match the valid iSeries operatingsystem password for user <sid>adm. A special tool is provided to ensure this.
PrerequisitesYou have changed the password for the user <sid>adm with the program setdb4pwd.exe.
The setdb4pwd.exe program can be found in the following directory:
\\<saplocalhost>\saploc\<SID>\<inst>\exe
<saplocalhost> is the name of the Windows 2000 server where the dialog instance wasinstalled.
ProcedureTo change the password for <sid>adm:
1. Log on to any Windows 2000 application server as user <sid>adm.
2. Open a command prompt and enter the following command:setdb4pwd %dbs_db4_ntlogonfile% <sid>adm <password>
Replace <password> with the new password for user <sid>adm.
3. To test the connection, enter:R3trans.exe -d
4. Use the file trans.log in the local directory to see if errors occurred while testing theconnection.
