Smart Implement a Ion

7/31/2019 Smart Implement a Ion

http://slidepdf.com/reader/full/smart-implement-a-ion 1/35

SAP®

Document

mySAP Workplace 2.11 - Smart Implementation

Installation Guide

SAP AG

Neurottstr. 16

D-69190 Walldorf



SAP®

Document

SAP AG Page 2

Copyright

Copyright © 2000 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained herein may be changed without prior notice.

SAP AG further does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within these materials. SAP AG shall not be liable for any special, indirect, incidental,or consequential damages, including without limitation, lost revenues or lost profits, which may result fromthe use of these materials. The information in this documentation is subject to change without notice anddoes not represent a commitment on the part of SAP AG for the future.

Some software products marketed by SAP AG and its distributors contain proprietary software compo-nents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks of Microsoft Cor-poration.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®,

OS/390®, and OS/400® are registered trademarks of IBM Corporation.

OSF/Motif® is a registered trademark of Open Software Foundation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated.

UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.

ADABAS® is a registered trademark of SAP Software AG.

SAP®, R/2®, R/3®, RIVA®, ABAP®, SAP ArchiveLink®, SAPaccess®, SAPmail®, SAPoffice®, SAP-

EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB, Team SAP, BAPI,

Management Cockpit are registered or unregistered trademarks of SAP AG.

Icons

The following icons are used in this document as visual aids.

Icon Meaning

Caution

Example

Note

Recommendation

Version

V1.10 - January 2001.



SAP®

Document

SAP AG Page 3

Contents

1. INTRODUCTION ............................................................................................... 5

1.1 Overview of the Smart Implementation Process ....................................................................................5

1.2 Technical Infrastructure.............................................................................................................................6

2. INSTALLATION................................................................................................. 7

2.1 Installation Preparation............................................................................................................................7

2.1.1 System Requirements.............................................................................................................................................. 7

2.1.2 Configuration Assistant........................................................................................................................................... 7

2.1.3 Preinstallation of Software ..................................................................................................................................... 8

2.2 Installing the mySAP Workplace 2.11...................................................................................................11

2.2.1 Prerequisites ..........................................................................................................................................................11

2.2.2 Starting the Installation.........................................................................................................................................11

2.2.3 Troubleshooting ....................................................................................................................................................13

2.3 Smart Implementation of Two SAP Systems on the Same Host ..........................................................13

3. CONFIGURATION OVERVIEW ........................................................................ 14

3.1 Workplace Server ...................................................................................................................................143.1.1 SID and TCP Ports.................................................................................................................................................14

3.1.2 Workplace Add-Ons............................................................................................................................................14

3.1.3 SAP Users and Passwords ...................................................................................................................................14

3.1.4 Clients ....................................................................................................................................................................14

3.1.5 Role Assignment....................................................................................................................................................15

3.1.6 Component Systems.............................................................................................................................................15

3.1.7 MiniApp Servlet for iViews ..................................................................................................................................16

3.1.8 TMS .......................................................................................................................................................................16

3.1.9 Standalone Gateway...........................................................................................................................................16

3.2 Windows OS ...........................................................................................................................................173.2.1 Groups...................................................................................................................................................................17

3.2.2 Users......................................................................................................................................................................18

3.2.3 Remote access ......................................................................................................................................................18

3.2.4 Installation Directories..........................................................................................................................................19

3.3 Middleware .............................................................................................................................................20

3.3.1 ITS and Web Server Instances ............................................................................................................................20

3.3.2 ITS Version ............................................................................................................................................................20

3.3.3 IAC Packages .......................................................................................................................................................20

3.3.4 ITS Administrator Account....................................................................................................................................20



SAP®

Document

SAP AG Page 4

4. POST-INSTALLATION ACTIVITIES..................................................................... 21

4.1 Mandatory Activities...............................................................................................................................21

4.1.1 Changing Passwords............................................................................................................................................21

4.1.2 Installing Licenses for the SAP Systems...............................................................................................................21

4.2 Optional Activities ...................................................................................................................................22

4.2.1 Integrating Component Systems..........................................................................................................................22

4.2.2 Configuring the Workplace Server.....................................................................................................................23

4.2.3 Activating the MiniApps.......................................................................................................................................28

4.3 Installing the Online Documentation .....................................................................................................30

4.3.1 Activating the EarlyWatch Alert Service.............................................................................................................30

4.3.2 Activating the Service Data Control Center .......................................................................................................30

4.3.3 TMS Configuration ...............................................................................................................................................31

4.3.4 Setting up the DBA Planning Calendar ..............................................................................................................314.3.5 Implementing Central User Administration.........................................................................................................32

4.3.6 ITS and Web Server Monitoring.........................................................................................................................33

5. APPENDIX...................................................................................................... 34

5.1 Documentation ........................................................................................................................................34

5.1.1 Overview of Documentation................................................................................................................................34

5.1.2 Viewing the Documents........................................................................................................................................35

5.2 The Smart Implementation Homepage in SAP Service Marketplace.................................................35



SAP®

Document

SAP AG Page 5

1. Introduction

1.1 Overview of the Smart Implementation Process

The following table provides an overview of all phases you have to go through during the Smart Imple-mentation with the corresponding documentation. All phases shown in the table below are mandatory.

Phase Tasks Documentation

I Planning the system infrastructure

There are different ways of distributing thesoftware components on one or multipleserver machines. In this phase, you mustconsider aspects such as security, perform-ance, and the integration into an existingsystem landscape.

mySAP Workplace Network Integration Guide

<DVD>:\documentation\wp_infra.pdf

For information about Network Integration, seethe network homepage in SAP Service Market-

place:http://service.sap.com/network.

II Sizing the WP system infrastructure

Sizing means determining the hardwarerequirements of an SAP System such asnetwork bandwidth, physical memory, CPUpower, and I/O capacity.The size of the hardware and database isinfluenced by both business aspects andtechnological aspects. This means that the

number of users using the various applica-tion components and the data load they puton the network must be taken into account.

For detailed information about SAP sizing, werecommend you to visit the sizing homepage inSAP Service Marketplace:

http://service.sap.com/sizing

III Configuring the system landscape withthe Configuration Assistant

During this phase, you have to configure thewhole infrastructure and system landscapewith the Configuration Assistant (page 7).The Configuration Assistant stores all infor-mation in a single configuration file. Installa-tion and configuration of single componentsoccurs later on during the automatic instal-

lation.

The Configuration Assistant contains an exten-sive online help. You can find this program inSAP Service Marketplace:

http://service.sap.com/smart

IV Preinstallation of software

Before starting the Smart Installation, somesoftware components must be preinstalled.This is an essential prerequisite for theSmart Installation.

See the chapter Preinstallation of Software(page 8).

V Unattended installation and configura-tion of components

The actual installation is an automated pro-cess that reduces user interaction to aminimum.

For information about the installation process,see the chapter Installing the mySAP Work- place 2.11 (page 11).



SAP®

Document

SAP AG Page 6

The automated configuration includes thecreation of ITS instances, Web server in-stances, ports, users, and the pre-configuration of the SAP System.

Do not start the Smart Implementation beforeyou have successfully completed all prepara-tion tasks (Phase IV). Otherwise the installationfails.

For a description of pre-configured settings,see the section Configuration Overview (page14).

VI Post-Installation activities

When the installation has successfully com-pleted, only a few post-installation steps arerequired to complete the configuration of

components (see phase V).

See the chapter Post-Installation Activities(page 21).

You can find a detailed description of all documents in the section Overview of Documenta-tion (page 34).

1.2 Technical Infrastructure

You can find information about the technical infrastructure in the document mySAP Workplace 2.11

Smart Implementation - Technical Infrastructure (see Overview of Documentation, page 34).

For information about network integration, see the mySAP Workplace Network Integration Guide.



SAP®

Document

SAP AG Page 7

2. Installation

This chapter contains essential information about the installation process. Make sure that you carefully

follow all the steps that are mentioned here. Chapter 3 provides an overview of settings that were madeautomatically during the unattended installation. You do not have to perform any activities here.

Chapter 4 provides an overview of steps that have to be made when the installation is finished.

2.1 Installation Preparation

Before starting the installation process, all prerequisites described in this chapter must befulfilled. Do not start the Smart Installation without performing these steps. Otherwise the in-stallation procedure fails.

We strongly recommend that you download and use the latest version of

- System Requirements

- Installation Guide (this document)

- Configuration Assistant

You can find this documentation in SAP Service Marketplace:


2.1.1 System RequirementsFor a comprehensive description of system requirements, see the document mySAP Workplace 2.11 -Smart Implementation - System Requirements.

Make sure that the host used for the Smart Implementation fulfills all the requirements de-scribed in this document.

2.1.2 Configuration Assistant

The Configuration Assistant lets you easily and conveniently configure the whole infrastructure and sys-

tem landscape before starting the actual installation process. The mySAP Workplace configuration isindependent of the actual installation. It can be performed on a different host. The Configuration Assis-

tant stores all configuration information in a single file, the configuration file wpconf.cfg.

The configuration file created by the Configuration Assistant is a prerequisite for the SmartInstallation. You must enter your configuration data with the Configuration Assistant beforeyou can start the Smart Installation.

Installing the Configuration Assistant

The Configuration Assistant for the mySAP Workplace 2.11 is a Windows program that runs on any

Windows 95, Windows 98, Windows NT 4.0, or Windows 2000 operating system.



SAP®

Document

SAP AG Page 8

To install the Configuration Assistant on your machine, start the self-extracting SAPConfSetup.exe

file and follow the instructions given on the screen.

To uninstall the Configuration Assistant , choose Add/Remove Programs or Software from the Win-dows Control Panel, select SAP Configuration Assistant and choose Add/Remove.

How to Use the Configuration Assistant

The configuration is divided into several dialogs steps. Select the corresponding dialog from the left sideof the main screen to access the corresponding dialog form.

A green checkmark on a pushbutton indicates that a dialog has been completed. Some buttons are un-available until you have entered the information in a preceding dialog.

The Configuration Assistant contains online help documentation. To get general help about

the Configuration Assistant, choose Help → Help Topics or choose F1.

To get help about a particular input control, click the right toolbar button or choose SHIFT-F1,then select the required item.

- You can save the configuration information at any time by choosing File → Save on themain screen.

- You can open a configuration file that was previously saved by choosing File → Open.

- To print out the complete current configuration information, choose File → Print .

2.1.3 Preinstallation of Software

The following software must be installed before you start the Smart Installation procedure.Otherwise the installation stops. We recommend you not to install other software compo-nents on the installation host, because the compatibility of the automatic installation processwith third-party software has not been tested.

Windows OS (Windows NT 4.0 Server or Windows 2000 Advanced Server)

The Smart Implementation for the mySAP Workplace 2.11 supports Windows NT 4.0 (Service Pack 6a)and Windows 2000 (Service Pack 1). Currently, not all database platforms support Windows 2000:

Database Windows NT 4.0 (SP 6a) Windows 2000 (SP 1)

Microsoft SQL Server 7.0 SP1 Yes Yes

DB2 UDB 6.2, Fixpack 4 Yes Yes

SAP DB 7.2 Yes Yes

Oracle 8.1.6 Yes Yes

Informix 7.31 TC 6 with ICONN 2.40 Yes No

As part of the installation procedure, SAP recommends you to install two separate Windows operating

systems (two Windows NT systems or - if supported by the database platform - two Windows 2000 sys-



SAP®

Document

SAP AG Page 9

tems). One Windows OS is for production purposes and the other one for service, backup, and trouble-shooting ("initial Windows OS").

We recommend that you perform a backup of the production Windows NT system before starting theSmart Implementation. If the installation fails and cannot be restarted, you can easily restore a clean

Windows NT operating system and start again.

For a Microsoft Windows NT 4.0 installation, you need the MS Windows NT Server CD. In addi-tion, Service Pack 6a is required for the Smart Implementation. If Service Pack 6a for Windows NTwas not installed before starting the installation, it is automatically installed during the installationprocess.

For a Microsoft Windows 2000 installation, you need the MS Windows 2000 Server CD. In addi-tion, Service Pack 1 is required. If Service Pack 1 for Windows 2000 was not installed before startingthe installation, it is automatically installed during the installation process.

You must use a US English Windows OS.

Never perform a Smart installation on a Windows OS domain controller (neither on a PDCnor on a BDC).

Configure your network properly in accordance with the settings made in the Configuration Assistant . For the Web servers, the fully qualified domain names (FQDN) are required.

The host name is case-sensitive and must be written in exactly the same way for the fol-lowing:

a) DNS entry (if applicable)

b) etc\hosts file (if applicable)

c) Host Name entry in the network properties.

Make sure that the hostname does not exceed 12 characters.

To avoid any confusion, SAP recommends you to use only lower-case host names. Note thedifference between a computer’s hostname and the MS Windows computer name (which isalways upper case).

Third Party Products

We recommend you to use a newly installed operating system with no other software

components installed except the required software components that are described in thefollowing sections.

The compatibility of the automatic installation process with third-party software has not been tested.

Installing the Web Server

The Smart Implementation for the mySAP Workplace does not include any licenses for aWeb server. Therefore, you have to preinstall Web server software on your dedicated Webserver.



SAP®

Document

SAP AG Page 10

Install one of the supported Web Servers (Microsoft Internet Information Server, Apache or NetscapeEnterprise Server ) on your system drive (that is, the drive where your Windows OS is installed - typically

C:\).

Microsoft Internet Information Server (IIS)

Operating System: Windows NT 4.0 or Windows 2000.

The version of the Internet Information Server that has to be installed depends on the Windows OS thatwas preinstalled (see the section Preinstallation of Software, page 8).

On the operating system Windows NT 4.0, install Microsoft Internet Information Server 4.0.

This IIS version is part of the MS Option Pack.

On the operating system Windows 2000, install Microsoft Internet Information Server 5.0.

Netscape Enterprise Server 4.1

Operating System: Windows NT 4.0.

You must use the default paths. Do not choose an administration port number between

1080 and 2100.

Apache 1.3.12

Operating System: Windows NT 4.0.

You must use the default installation path C:\Program Files\Apache Group\Apache.

Do not change the default configuration file httpd.conf. The virtual hosts are configuredautomatically during the Smart installation.



SAP®

Document

SAP AG Page 11

2.2 Installing the mySAP Workplace 2.11

2.2.1 Prerequisites

You have successfully completed all steps described in the chapter Installation Preparation (page 7).

The hardware and software corresponds to the System Requirements (page 7).

You have preinstalled the required software components (page 8).

You have closed all other software components. You have also checked for programs that start atboot time, such as services or Office components (for example, findfast ), since the server rebootsseveral times during the installation. Such programs might interfere with the installation and causeerrors.

Do not start the Smart Installation before successful completion of all preparation tasks.

Otherwise the installation fails.

2.2.2 Starting the Installation

We strongly recommend that you read SAP Note 365949 before starting the installation.You can find SAP Notes in SAP Service Marketplace:

http://service.sap.com/notes.

The duration of the installation depends on your computer hardware (5-12 hours). Do notstop the installation during a phase of low system activity or low CPU usage. Use the Win-dows NT Task Manager to monitor changes in the Processes list.

1. Log on to the Windows OS System as a member of the group Administrators or Domain Admins.The installation automatically creates appropriate user accounts:

If you log on as a local administrator, only local users are created. You must log-on as a localadministrator if you are using an INFORMIX database for the SAP System installation. In thiscase, an installation into an existing Windows OS domain is not supported.

If you log on as a domain administrator, local users and domain user accounts are created, de-pending on the installation host type. This option is only supported for Smart Implementationsthat are based on a MS SQL, DB/2, SAP DB or Oracle database system.

StandaloneServer

Server is a domain member Primary domaincontroller (PDC)

Backup domaincontroller (BDC)

Log on:localadmin

The installa-tion onlycreates localaccounts

The installation only creates localaccounts.

Do not install. Do not install.

Log on:

domainadmin

The installation also creates domainaccounts.

Note, that the domain administrator

must be authenticated by the PDC.

Do not install. Do not install.



SAP®

Document

SAP AG Page 12

2. Mount the installation DVD in your local DVD drive or use a network share.

3. Start the program <DVD>:\install.exe. The automatic installation procedure starts.

4. Enter your Windows administrator password. You can perform the installation as a local administra-

tor or a domain administrator (see the details in the table above).5. Make the required selections and entries (host, share, and drive letter). For more information, see

the <DVD>:\install.hlp file or the online help that is included in the install.exeprogram.

6. Make sure that the configuration file wpconf.cfg is available. The configuration file was created

with the Configuration Assistant (page 7).

To determine the overall configuration of the system, install.exe searches for the con-

figuration file wpconf.cfg in the following locations:

A:\wpconf.cfg (floppy drive)

C:\cfg\wpconf.cfg

If the configuration file cannot be found in the default locations, perform one of the following activi-ties:

a) Specify an alternative file.

b) Start the Configuration Assistant and enter the required configuration information manually.

c) Select a different configuration file by choosing File → Open.

4. To start the unattended installation, choose Start .

The installation runs automatically and no additional user interaction is required. Ignore the popup win-dow TopTier - R/3 BOR Model Transporter that appears temporarily towards the end of the installationprocess.



SAP®

Document

SAP AG Page 13

2.2.3 Troubleshooting

The following points are only relevant if you encounter problems during the installation process:

For problems with hardware or drivers, contact your hardware vendor.

For problems with the MS Windows OS installation (page 8), contact Microsoft or your Windows OSpartner.

If you detect any network problems during the installation process and you are running a server withmultiple network adapters, check the network settings. If you cannot solve the problem, reduce thenumber of network interface cards to one.

Check the latest SAP Notes.

For specific problems during the installation, read the error message on the screen carefully andcollect the installation logs in the installation directories mentioned above. After a successful installa-

tion, all log files are copied to the directory C:\Setup. They remain in this directory.

Try to fix the error and restart the Smart Installation with <DVD>:\install.exe.

SAP BackOffice

If you cannot solve the problem, create an error message with the component specification XX-ECOM.

You can create error messages in SAP Service Marketplace:

http://service.sap.com/message .

For direct support, call our help desk on +49 62 27 - 74 50 75.

In addition, the Back Office will put you in touch with experts to help you with special tasks in your im-

plementation project.

2.3 Smart Implementation of Two SAP Systems on the Same Host

The Smart Implementation of the mySAP Workplace 2.11 does not support an automatic installation incombination with older Smart Implementation products on a single host.

There is no functional restriction concerning the integration of BBP/CRM 2.0B and WP 2.11when these components are installed on different hosts.



SAP®

Document

SAP AG Page 14

3. Configuration Overview

This chapter provides an overview of configuration settings that were made during the unattended in-

stallation process.

3.1 Workplace Server

3.1.1 SID and TCP Ports

The SID and system number of the Workplace Server correspond to the values that were entered in the

Configuration Assistant (page 7). The default SID is WPS and the default system number is 02.

The system uses the following TCP ports (where nn is the system number):

Dispatcher (DP Port): 3200+nn

Gateway (GW port): 3300+nn Message server (MS port): 3600+nn.

3.1.2 Workplace Add-Ons

During the installation, the latest consistent set of add-ons and patches was applied to your WorkplaceServer. This also applies to the Workplace Plug-in 2.11.

3.1.3 SAP Users and Passwords

The following standard SAP users were created in all clients:

User Function Initial password

SAP* Standard user 06071992

DDIC Standard user 19920706

ADMINBC Standard user init

CCMS CPIC user for monitoring init

SAPCPIC (CPIC user) init

To avoid any security risk, we strongly recommend that you change the passwords for SAPusers immediately after the installation.

3.1.4 Clients

The following clients are created during the Smart Installation:

Client Description

000 Standard Client

066 EarlyWatch Client

400 Customizing Client

Client 400 (Customizing Client ) is mainly used for maintaining roles. All Customizing changes are re-

corded automatically.



SAP®

Document

SAP AG Page 15

3.1.5 Role Assignment

The following roles were assigned to the user ADMINBC:

Single Role Function

SAP_BC_BASIS_ADMIN Administrator for the mySAP Workplace

SAP_BC_RRR_SAA_ADMIN System Administration Assistant - System Administrator

SAP_BC_TRANSPORT_ADMINISTRATOR Administration in the Change and Transport System

SAP_SV_SERVICE_WP_USER mySAP Support Workplace User

The roles SAP_BC_BASIS_ADMIN, SAP_BC_RRR_SAA_ADMINand

SAP_BC_TRANSPORT_ADMINISTRATORcontain links to the most important administration trans-

actions. For example, you can start transactions for CCMS system monitoring and CTS transac-

tions for the administration of the transport infrastructure (or transactions for transport requests).You can do this directly from the LaunchPad. Additionally, there are links leading to office transac-tions and to the System Administration Assistant .

The role SAP_SV_SERVICE_WP_USER contains links to SAPNet - Web Frontend, SAPNet - R/3

Frontend (formerly known as SAP Online Service System, SAP OSS) and the mySAP SupportWorkplace

The user ADMINBC was created on the Workplace Server during the unattended installation

process (see SAP Users and Passwords, page 14). ADMINBC has all authorizations that are

required for the administration of the mySAP Workplace.

3.1.6 Component Systems

For each logical system <SID>CLNT<CLIENT>, the following instances were created during the installa-

tion procedure:

One ITS Instance

One Web server Instance

One TopTier server Instance

The unattended installation of these instances is based on information that was provided by the Configu-ration Assistant (for example, to define the TCP Ports for the Web server).If you want to use the Drag&Relate feature, you have to make some additional, manual settings later (see Post-Installation Activities, page 21)



SAP®

Document

SAP AG Page 16

3.1.7 MiniApp Servlet for iViews

The MiniApp Servlet for iViews is automatically installed during the Smart installation.

With mySAP Workplace 2.11, SAP is shipping the MiniApp Servlet for iViews for the first time. The

MiniApp Servlet for iViews contains the following utilities

Web Site Component Creator

This replaces the Web Source Editor, which was part of the Drag&Relate Servlet until Workplace 2.10.You use this tool to maintain Web sites and their relationships to Drag&Relate objects.

iView Creator

An interface that enables you to include Web applications from SAP’s development partner TopTier un-der the product name iViews as MiniApps in the MiniApp catalog on the Workplace Server.

For more information about configuring the MiniApp Servlet for iViews, see SAP Note 350425.

3.1.8 TMS

The Transport Management System (TMS) was not configured during the unattended installation proc-

ess, since the Workplace Server usually has to be integrated into an existing transport domain. For de-tailed information about the configuration steps, see TMS Configuration (page 31).

3.1.9 Standalone Gateway

The standalone gateway is required for OS monitoring programs to establish a communication with theSAP System.

If no SAP System is present on the middleware host, the unattended installation process installs: A standalone gateway (default system number is 77).

The executables SAPOSCOL and RFCOSCOL.

The Windows NT service SAPOSCOL to collect operating system data on the middleware host.



SAP®

Document

SAP AG Page 17

3.2 Windows OS

3.2.1 Groups

Groups that already exist before the installation starts are kept. Depending on the server role (standa-lone server or member of a Windows NT domain) and the administrators role (local administrator or do-main administrator), the following standard SAP groups are created during the unattended installationprocess (see also Starting the Installation, page 11.

Group Function

SAP_<SID>_LocalAdmin Local administrator group. Only local groups are created and main-tained on the SAP server. A local group can only be given permissionsand rights to the system where it is located.

SAP_<SID>_GlobalAdmin This global group is a domain-level SAP administration group for or-ganizing SAP System administrators. The main function of a globalgroup is to gather users together at the domain level so that they canbe placed in the appropriate local groups.

SAP_LocalAdmin This local 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 sys-

tems.

The SAP_<SID>_GlobalAdmin groups of all the SAP Systems thatare part of the transport infrastructure are added to the

SAP_LocalAdmin group. Therefore, the users <SID>adm and SAP-

Service<SID> of all systems in the transport infrastructure are

members of the SAP_LocalAdmin group and have the authorizations

necessary to start and execute transports.



SAP®

Document

SAP AG Page 18

3.2.2 Users

Users that already exist before starting the installation are kept. In addition, their group membership andpasswords are redefined (see the table below).

All Windows OS users and database users (for example, sapr3, db2admin, <SID>adm

and so on) have the initial password sap.

User Function Component Assigned Group(s)

<SID>adm SAP System administrator accountthat enables interactive administra-tion of the system.

SAP System Administrators

SAP-Service<SID>

User account that is required tostart the SAP System. Nobody canlog on to the system with this ac-count.

It has the local user right to log onas a service and is a member of the

local administrator’s group.

This user is not created for Informixinstallations.

SAP System UsersSAP_<SID>_LocalAdminSAP_LocalAdmin

itsadm Windows NT user for the admini-stration of the SAP Internet Trans-action Server (ITS).

AGateWGate

The advantage of the additional SAPService<SID> account is that it does not allow an interactive

logon and so prevents abuse of the account. Therefore, it is not necessary to define an expiration datefor the password, and the option user must change password at next logon does not have to be set.

3.2.3 Remote access

Microsoft NetMeeting 3.0 is automatically installed during the installation:



SAP®

Document

SAP AG Page 19

3.2.4 Installation Directories

The following directories were created during the installation process. (Depending on your individualconfiguration, only a subset of these directories may exist).

C:\SetupC:\<Database>

C:\Middleware

C:\r3setup

c:\sp6

c:\sp1

c:\IE501

These installation directories are not needed after the successful completion of the Smart implementa-tion and can be deleted.

Do not delete the C:\cfg directory after the installation.



SAP®

Document

SAP AG Page 20

3.3 Middleware

3.3.1 ITS and Web Server Instances

Web servers and components are installed on the Web server hosts, the Web middleware, and thebackend SAP Systems. The following table summarizes the TCP/IP port numbers that are configuredduring the Smart Implementation.

Workplace ITS Ports Admin Instance Ports Ports for Component System Middleware(i= # of Component Systems)

A-Gate: 3900

Mapping Manager: 3901

Web Port: 80

A-Gate: 3910

Mapping Manager: 3911

Web Port: 89

A-Gate: <3910+10*i>

Mapping Manager: <3911+10*i>

Web Server Port: <1080+2*i>

Gateway Sys. No: 77

These defaults settings can be changed by directly editing the configuration file.

3.3.2 ITS Version

The following ITS version is included in the Smart Implementation:

ITS 4.6D, build No. 347423, version 4640.3039.34.7423.

3.3.3 IAC Packages

The following IAC packages are included in the Smart Implementation for the mySAP Workplace 2.11

Workplac.car patch 7 SAP Notes: 359318, 359319, 358837, 364595, 366641, 369004, 368159

Webaddon.car patch 1 SAP Note: 354106

PBuilder.car patch 1 SAP Note: 359735

NTauth.car patch SAP Note: 361064

Guistart.car patch SAP Note: 358804

MWP.car Server Component CD C3

WP_Comp.car Server Component CD C3

3.3.4 ITS Administrator Account

The Internet Transaction Server has a built-in administrator account called itsadmin (initial password:

init). To log on as itsadmin on the ITS, enter the following in the address line of your Web browser:

http://<host>:89/scripts/wgate/admin/!



SAP®

Document

SAP AG Page 21

4. Post-Installation Activities

4.1 Mandatory Activities

4.1.1 Changing Passwords

For maximum security, we strongly recommend that you change the standard SAP pass-words immediately after the installation.

You can find an overview of SAP users and passwords in the section SAP Users and Passwords (page14)

4.1.2 Installing Licenses for the SAP Systems

Use

The Smart Implementation for the mySAP Workplace 2.11 is delivered with temporary SAP licenses thatlet you operate your system for four weeks. This means that you need to install your own licenses for each SAP System within this period.

To import the SAP license, you need the installation number and the customer key. You can requestlicense keys for systems as follows:

SAP Service Marketplace (see SAP Note 94998)

Fax (see description below)

Customers who have access to SAP Service Marketplace should always request the license key throughSAP Service Marketplace since this is quicker and easier.

Procedure

To install the SAP license with fax, perform the following steps:

1. To get the hardware key (that is, the customer key) needed for the license request, enter the follow-ing command on the host where the message server is running:

saplicense -get

The system displays an 11-character hardware key, for example, D1903055560.

2. Send a fax with the following information to SAP:

• Hardware key from previous step

• Name of the installed SAP System (that is, the value of <SID> )

• The date when you installed the database

3. After you have received your license key from SAP, install it as follows, making sure that you enter the license key exactly as shown in the SAP reply to your fax:

saplicense -install

a) If the license installation is successful, you see the following message:

license successfully installed.

You now have a permanent license for your SAP System.



SAP®

Document

SAP AG Page 22

b) If the license installation is not successful, you see the following message: check failed,

no license installed.

4. For more information, see the following in the SAP Library:

BC Basis→

Kernel Components→

BC SAP License .

4.2 Optional Activities

4.2.1 Integrating Component Systems

Preconfiguration

To facilitate the integration of component systems, the following steps were already performed on theWorkplace server during the unattended installation:

SPAM/SAINT update

Import of Plug-ins and patches (including the Workplace Plug-in 2.11)

Creation of logical systems

Creation of RFC destinations

Creation of ITS instances

Creation of Web server instances

Manual Steps

You must perform the following steps to complete the integration of component systems into the mySAP

Workplace 2.11.

In the component systems:

1. Define a service user and its authorizations.

The service user in the component systems constitutes the data interface between the componentsystem and the Workplace Server and requires authorizations that allow it to read certain data. SAPNote 215927 lists the authorizations required for the service user. SAP ships a roleSAP_WPC_EXCHANGE on the mySAP.com Role Templates CD, however this role is not complete.

You can find the missing authorizations in the SAP Note. Download the role from the WorkplaceServer. Then upload the role to your component system, save it with a meaningful name and add themissing authorizations. Finally generate the authorization profile and assign the role to your service

user.2. Import the Workplace Plug-In WP-PI 2.11.

Import the Workplace Plug-In WP-PI 2.11 into all of the mySAP Workplace component systems. For Workplace component systems with a SAP Basis Release 4.0B or higher, you install the Plug-Inusing the SAINT transaction; for Workplace component systems based on Releases 3.1H and 3.1I,you use the tp tool. In both cases, the installation takes approximately 15 minutes. Due to the ab-sence of integration, you do not have to shut down the component system, so you can perform theinstallation during production operation.

The procedure is described in the following Notes:

350540 Workplace Plug-In 2.11: Add-On Installation/Delta Upgrade (for SAP-Basis 3.1H and 3.1I)

350538 Workplace Plug-In 2.11: Add-On Installation/Delta Upgrade (for SAP Basis 4.0B – 4.6D).



SAP®

Document

SAP AG Page 23

Do not install any Plug-ins on the Workplace Server. During the Smart installation, the latestconsistent set of add-ons and patches was already applied to your Workplace Server.

3. Import transaction classification data and, if required, classify additional transactions manu-ally (only necessary for Backend Systems < 4.6C).

Not all SAP transactions are compatible with the SAP GUI for HTML, some require the SAP GUI for Windows or the SAP GUI for JAVA. SAP provides transaction classification data which classifieseach transaction according to the SAP GUI that it requires. You can find this data in the Download Area in the SAP Online correction folder in the SAP Service Marketplace athttp://service.sap.com/support.

Find out the Basis release of each of your component systems, download the corresponding pack-age and import it into your component system. For detailed instructions, see SAP Note 203120.Before you import the transaction classification data, you must first import the Workplace Plug-In, asit contains the DDIC definition of the table in which the transaction classification data is stored.

4. Import Drag&Relate metadata

SAP provides Drag&Relate metadata in the SAP Online correction folder on the SAP Service Mar-

ketplace at http://service.sap.com/support. The Drag&Relate metadata contains the infor-

mation necessary for link generation, for example, assigning data elements or transactions to busi-ness objects, and for parameterized launching of transactions with Drop actions.

Download the Drag&Relate package for each Workplace component system and import it into your component system. For more information, see SAP Notes 335373 and 335369.

On the Workplace Server:

After performing all these activities, load the data from the component systems to the Workplace Server for the first time and schedule the job SAP_WP_CACHE_RELOAD to be performed on a daily basis.

4.2.2 Configuring the Workplace Server

With the following steps, you integrate the Workplace Server into the Workplace. This enables you toadministrate the Workplace Server using a Web Browser. Note that SAPGUI access is independent of these configuration steps.

Creating RFC Destinations

1. Log on to your Workplace Server with SAPGUI:Client : 400

User : adminbc

Password : <password>

2. Call transaction sm59.

The Display and maintain RFC Destinations screen appears.

3. Expand the R/3 connections tree.

You see a list of RFC destinations that were already defined.

4. Choose Create.

The RFC Destination screen appears.

5. In the RFC Destination field, enter <SID>CLNT400 (<SID> is an abbreviation for the system ID of

the Workplace Server, for example, WPS)



SAP®

Document

SAP AG Page 24

6. In the Connection Type field, choose type 3 (Connection to R/3 System).

7. Enter a description, for example, Workplace default RFC destination.

8. Enter the required logon information:

Client : 400User : ddic

Password : <standard password>

9. Choose Save.

10. In the Target Host field, enter the host name for the Workplace Server (for example, mysap05).

11. In the System number field, enter the corresponding system number (for example 05).

12. Choose Test Connection.

A screen asking Save changes first? appears.

13. Choose Yes.

The RFC Connection Test screen appears.



SAP®

Document

SAP AG Page 25

14. Check the test results and choose Back .

Creating Logical systems

1. Call transaction SPRO.

The Customizing: Execute Project screen appears.

2. Choose SAP Reference IMG. The Display IMG screen appears.

3. Choose Basis → Application Link Enabling (ALE) → Sending and Receiving Systems → Logical

Systems → Define Logical System.

4. Click the execute button on the left to Define Logical System.

The Change View "Logical Systems": Overview screen appears.

5. Choose New Entries. The New Entries: Overview of Added Entries screen appears.



SAP®

Document

SAP AG Page 26

6. In the field Log. System, enter <SID>CLNT400 (for example, WPSCLNT400. <SID> is an abbrevia-

tion for the system ID of the Workplace Server).

7. In the Name field, enter a description (for example, WP 2.11 default LS).

8. Choose Save.9. Select an existing transport request or create a new one, if required.

10. Choose OK .

11. Choose Save.

12. Choose the Back button to return to the R/3 Basis Implementation Guide Structure.

Adding Component Systems

1. Choose Basis → Application Link Enabling (ALE) → Sending and Receiving Systems → Logical

Systems → Assign Client to Logical System.

2. Click the execute button on the left to Assign Client to Logical System.

3. Double click the field 400 in the Client column.

The Display View "Clients": Details screen appears.

4. Enter a city (for example, WALLDORF) and the logical system that corresponds to the Workplace

Server (for example, WPSCLNT400).

5. In the Std. currency field, choose a standard currency (for example, DEM for German Mark).

6. In the Client role field, choose Customizing.

7. Save your entries.

Creating Logical Web Servers

1. Call transaction sm31.

2. In the Table/view field, enter TWPURLSVR.

3. Choose Maintain.

4. Choose New Entries.

5. In the Logical System field, enter the newly created logical system (for example, WPSCLNT400).

6. In the Web server field, enter the fully qualified domain name of the corresponding Web server (for

example, mysap05.wdf.sap-ag.de).

7. In the Web protocol field, enter HTTP.

8. Make the same entries in the fields GUI Start Server , GUI Start Protocol , Drag&Relate Server andDrag&Relate Protocol .

9. Choose Save.

10. Confirm the proposed transport request.



SAP®

Document

SAP AG Page 27

Role Maintenance

You have to perform the following steps for each of the following roles:

SAP_BC_BASIS_ADMIN

SAP_BC_RRR_SAA_ADMIN

SAP_BC_TRANSPORT_ADMINISTRATOR

SAP_SV_SERVICE_WP_USER

Procedure

1. Call Transaction PFCG. The Role Maintenance Screen appears.

2. Enter the corresponding role (for example, SAP_BC_RRR_SAA_ADMIN).

3. Choose Copy Role.

4. In the to role field, rename the role by adding Z_ at the beginning (for example,

Z _SAP_BC_RRR_SAA_ADMIN). When renaming the role SAP_BC_TRANSPORT_ADMINISTRATOR,

you have to shorten the name (for example, Z _SAP_BC_TRANSPORT_ADMIN).

You can ignore the message Distribution failed that appears when some of the objects are currentlylocked.

5. Choose Copy all .

6. Choose Change Role.

7. Choose Menu.

8. Click the empty field below Target System and choose the select icon that appears on the right side.

9. Choose Select RFC Destination.

10. Select a RFC destination (for example, WPSCLNT400).

11. Choose Authorizations.

12. Choose change authorization data to define the corresponding authorizations.

13. Click the Generate button to create the profiles.

14. Choose Menu and click the Distribute button. If the message Distribution failed appears, you can

ignored it. The distribution will be performed later during an automatic process.

15. Choose Save.

Role Assignment

Perform the following steps for the users adminbc and CCMS.

1. Call transaction SU01.

2. Select a user (for example, adminbc).

3. Choose Change.

4. Choose Roles.

5. Select all SAP Roles (starting with SAP_).

6. Click the Delete line button. All SAP Roles are removed. The remaining roles are beginning with Z_.

7. Choose Save.



SAP®

Document

SAP AG Page 28

Logging on to the Workplace

1. Open a Web browser.

2. In the Address line, enter the following: http://<host>/scripts/wgate/sapwp/!

For example, http://mysap05.wdf.sap-ag.de/scripts/wgate/sapwp/!).

The logon screen of the mySAP Workplace 2.11 appears.

3. Enter the required logon information.

4. Choose Logon.

The user interface of the mySAP Workplace appears.

The MiniApps are not fully functional yet. You must perform the following steps to complete their configu-ration.

4.2.3 Activating the MiniApps

There are two MiniApps included in the workspace. You have to perform the following steps to activatethem.

Installing the IacorAdmin service

1. On the Workplace server, start the following program:

C:\Program Files\SAP\ITS\2.0\Admin\IacorAdmin.exe

The message Failed to attach to IACOR service - service is not running appears, which is okay for now.

2. In the IAC Object Receiver Admin window, choose Options.

3. In the NT Service Registration field , choose Register .

4. Choose OK and quit.

5. Start the IACOR service:

Windows NT: Choose Control Panel → Services and start the IACOR service manually. It is notnecessary to reboot the server. The IacorAdmin service is now installed

Windows 2000: Choose Programs → Administrative Tools → Services and start the IACORservice manually. It is not necessary to reboot the server. The IacorAdmin service is now in-stalled.

Publishing the Web templates

1. Log on to the Workplace server.

2. Call transaction SE80. The ABAP Development Workbench opens.

3. Choose Internet Service and enter the service SAA_TASKLIST

4. Confirm by choosing ENTER.

5. Double click the service SAA_TASKLIST

6. Expand the structure SAA_TASKLIST → Theme 99 → HTML templates.

7. Double click Start .

8. Choose Publish.



SAP®

Document

SAP AG Page 29

Releasing the Report for the Web

1. Call transaction smw0

2. Choose Internet Release → Reports.

3. Enter rssaa_workplace.

4. Choose Release. The report is now released for the Web.

5. Log on to the mySAP Workplace using a Web browser. Congratulations - your mySAP Workplace isfully Web enabled now.

The MiniApp Task List provides an overview of tasks that have to be performed on a regular basis. Tasks that were successfully completed are marked by a green symbol in the statusrow.



SAP®

Document

SAP AG Page 30

4.3 Installing the Online Documentation

Use

SAP currently provides an HTML-based solution for the SAP online documentation. The ApplicationHelp, Glossary, Implementation Guide (IMG) and Release Notes are delivered in HTML format. You candisplay the documentation with a Java-compatible Web browser.

Procedure

1. Install the online documentation as described in the document Installing the Online Documentation.

This document is delivered as part of the Online documentation CD.

2. Log on to your SAP system.

3. Choose Help → SAP library .

4.3.1 Activating the EarlyWatch Alert Service

Use

The EarlyWatch Alert Service is used to check the installation of your SAP System regularly. It automati-cally analyzes the current data of the SAP installation. The analysis tools are constantly improved andadapted to new requirements. Be sure to read the SAP Notes and recommendations that describe thisservice.

Procedure

To activate the EarlyWatch Alert Service, perform the activities described in the SAP Notes 178631( Activation Service Data Control Center ) and 187939 (TCC Service Tools Update). Note that a new Ear-lyWatch Alert architecture was introduced with Release 4.6 (see SAP Note 207223).

For additional documentation, see the document <DVD>:\Documentation\sdcc.pdfon the installa-

tion DVD.

4.3.2 Activating the Service Data Control Center

Use

The Service Data Control Center is used for collecting and sending performance data. This tool is beingconstantly improved and adapted to new requirements. After the Smart Implementation of the mySAPWorkplace this function has to be activated on the customer site.

Procedure

Call transaction SE38. The ABAP editor starts.

1. In the Program field, enter BDLSETUP.

2. Choose Execute (F8).

3. In the KEY field, enter INIT_RUN. Leave the Value field empty.


5. Start the Report BDLSETUP again.

6. In the KEY field, enter LOGONGRP.

7. In the Value field, enter EWA.


9. Start the ReportBDLSETUP

again.



SAP®

Document

SAP AG Page 31

10. In the KEY field, enter DEST.

11. In the Value field, enter SAPOSS.


13. Call transaction SDCC.

The Service Data Control Center starts.

14. Choose Maintenance → Refresh → Service Definitions.

A window appears: Refresh Service Definitions?

15. Confirm by choosing Yes.

This step might take some time. If you encounter problems during this step, note that the remote desti-

nation SAPOSS (to be maintained in transaction SM59) must be active and fully functional.

4.3.3 TMS Configuration

SAP recommends that you register the Workplace Server system for an existing transportdomain. You can find a detailed description of the TMS configuration in the Online Help of the Change and Transport System (CTS).

Registering a Central Transport Directory

1. In the instance profile of the Workplace Server, enter the parameter DIR_TRANS.

2. Enter the path to the central transport directory as the value of this parameter.

3. Make sure that the corresponding directory can be reached.

Registering the WP System for an Existing Transport Domain

1. Log on to the Workplace Server as user ADMINBC.

2. Call transaction STMS.

The system proposes a transport domain to which the Workplace System can be added. You canaccept this proposal or change the transport domain. For more information, see the online docu-mentation.

Adding the WP System to an Existing Transport Domain

1. Log on as administrator to the component system that functions as a domain controller.

2. Call transaction STMS.

The WP System now waits to be included in the transport domain.

3. Confirm the inclusion in the transport domain.

4.3.4 Setting up the DBA Planning Calendar

Use the following procedure to set up the DBA Planning Calendar with a ‘best practices’ planning.

1. Log on to the system in client 000 with user ddic (initial password: 19920706).

2. Call transaction SE38.

The APAP Editor starts.



SAP®

Document

SAP AG Page 32

3. In the Program field, enter INST_DB13_CONFIG .

4. Choose Execute.

5. Choose T to configure a development and test system, or P for a productive system.

6. Check and accept or modify the planning.

4.3.5 Implementing Central User Administration

In Smart Implementations, central user administration is implemented on the Workplace Server by exe-

cuting the report INST_CREATE_CUA.

1. Call transaction SE38.

The ABAP editor starts.

2. In the program field, enter INST_CREATE_CUA.

3. Choose Execute.

Only execute this report in the client in which you want to set up central user administration.

Only execute this report once. Do not execute it again later after you have already madecentral user administration settings.

You can integrate all SAP Systems with Release 4.5A or higher with the central user administrationfunctions. You must first include all clients of the relevant systems in an ALE (Application Link Enabling)distribution model. These clients are known as logical systems in the ALE environment.

A Smart Implementation of the mySAP Workplace uses the Workplace Server as the central instance for

maintaining users. This includes all component systems specified in the Configuration Assistant.

The data required for setting up central user administration is loaded when you install the WorkplaceServer. This means that the component system data is already visible. You can change these values, for example if the system environment of a component system has changed.

Process Flow

The report INST_CREATE_CUAperforms the following steps to set up central user administration:

• A logical system (LS) is set up for each specified client. These logical systems are needed bythe ALE distribution model.

Naming convention for logical systems: <SID>CLNT<Client>

<SID> : System ID of the component System

<Client> : Client of the component System relevant for central user administration

• The logical system of the Workplace Server is assigned to the current client, if this has not al-ready happened. An automatic check is made on the assignment of clients to logical systems inthe component systems.

• The ALE distribution model is generated with the previously defined logical systems.

• RFC destinations are created. The names of the RFC destinations are identical to the names of the logical systems. The Configuration Assistant gathered the technical information on the RFCdestinations before the installation. A check is made to see whether the RFC destinations of thecomponent systems function with the Workplace Server. If not, you must create the RFC desti-nations manually in the appropriate component system.



SAP®

Document

SAP AG Page 33

• The partner profiles are generated on the Workplace Server. The partner profiles can only begenerated automatically in the component systems if these systems have Release 4.6C or higher.

• The ALE distribution model is distributed to all specified logical systems. Fully functioning RFC

destinations are a prerequisite for this.

Manual Steps

The report cannot perform all of the required steps automatically:

• You must generate the partner profiles in all component systems with a release lower than 4.6A.

To do this, call transaction BD64 and choose Environment → Generate partner profiles.

• If there is no functioning RFC destination for the connection between the component system andthe Workplace Server, you must create this destination in the component system with transac-

tion SM59.

Remember that the names of the RFC destinations must be the same as the names of the logi-

cal systems.

• If the information on the logical systems delivered in the installation is no longer up-to-date, youcan exclude these logical systems from the generation of the central user administration. To dothis, select Ignore. You can also delete logical systems from the list, and add other logical sys-

tems.

Only use the INST_CREATE_CUAprogram for the initial setup of a CUA environment after

the Smart Workplace Server installation. Do not use it for later updates to the CUA environ-ment.

If you have not altered default values of the gateway installation, the gateway service is

named sapgw77.

4.3.6 ITS and Web Server Monitoring

You can use the CCMS monitor (transaction code: rz20) for monitoring the ITS and Web server. For

distributed installations, we recommend you to display the monitoring data in a tree structure.

To do this, you have to perform the actions described in SAP Note 210890.



SAP®

Document

SAP AG Page 34

5. Appendix

5.1 Documentation

5.1.1 Overview of Documentation

Documentation Purpose Location of Documentation

WP 2.11 Smart Imple-mentation - InstallationGuide (this document)

Components of the mySAPWorkplace, installation process,preconfigured settings, integra-tion of existing systems

<DVD>:\documentation\smartinst_wp211.pdf

We recommend that you

download the latest versionfrom SAP Service Market-

place (Alias: /smart).

WP 2.11 Smart Imple-mentation - SystemRequirements

Supported Platforms. supporteddatabases, Web servers, re-quired Disk layout

<DVD>:\documentation\sysreq_wp211.pdf

We recommend that youdownload the latest versionfrom SAP Service Market-

place (Alias: /smart).

WP 2.11 Smart Imple-mentation - Technical Infrastructure

System infrastructure, scenar-ios, distribution of components

<DVD>:\documentation\wp_infra.pdf

WP 2.11 Workplace

Network IntegrationGuide

Component systems, SAPGUIvariants, Single Sign-On,Drag&Relate, ITS architecture

<DVD>:\documentation\wp_nig.pdf

WP 2.11 MiddlewareInstallation guide

Installation and configuration of middleware components. Moststeps were already performed

during the Smart implementa-tion.

<DVD>:\documentation\wpmid211

Configuration Guide for the mySAP Workplace2.11

Registering logical systems,Creating RFC Connections,Registering a Server, MakingCentral Settings

<DVD>:\documentation\wp211_conf.pdf

Drag&Relate Use and configuration of Drag&Relate in the mySAPWorkplace 2.11

<DVD>:\documentation\drag_rel.pdf

Service Data Control Center

All aspects of network integra-tion, for example, integration of SAP servers, integration of SAPfrontends, security and more.

<DVD>:\documentation\sdcc.pdf



SAP®

Document

SAP Network Integra-tion Guide

All aspects of network integra-tion, for example, integration of SAP servers, integration of SAPfrontends, Internet integration,

security and more.

<DVD>:\documentation\nig_en.pdfnig_de.pdf

5.1.2 Viewing the Documents

You have to install Acrobat Reader 4.0 to view the PDF documents. You can find this program on the

installation DVD in the directory <DVD>:\documentation\acroread.

5.2 The Smart Implementation Homepage in SAP Service Market-place

You can find current information about the Smart Implementation and the latest version of the WorkplaceConfiguration Assistant on our homepage at:
