Adaptive Computing Controller 1.0

(1)

Installation Guide

Adaptive Computing Controller 1.0

For SAP Web Application Server 6.40

Document Version 1.9 – January 04, 2006

(2)

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior notice.

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

Microsoft^®, WINDOWS^®, NT^®, EXCEL^®, Word^®, PowerPoint^®and SQL Server^® are registered trademarks of Microsoft Corporation.

IBM^®, DB2^®, DB2 Universal Database, OS/2^®, Parallel Sysplex^®, MVS/ESA, AIX^®, S/390^®, AS/400^®, OS/390^®, OS/400^®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere^®, Netfinity^®, Tivoli^®, Informix and Informix^® Dynamic Server^TM are trademarks of IBM 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 of the Open Group.

LINUX is a registered trademark of Linus Torvalds and others.

Citrix^®, the Citrix logo, ICA^®, Program Neighborhood^®, MetaFrame^®, WinFrame^®, VideoFrame^®, MultiWin^® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C^®, World Wide Web Consortium, Massachusetts Institute of Technology.

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

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 by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

MaxDB™ is a trademark of MySQL AB, Sweden

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP Business Suite, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:

service.sap.com/instguides

T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

(3)

Source Software

This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply.

SAP License Agreement for STLport

SAP License Agreement for STLport between

SAP Aktiengesellschaft

Systems, Applications, Products in Data Processing Neurottstrasse 16

69190 Walldorf Germany ( hereinafter: SAP )

and

you

( hereinafter: Customer )

1. Subject Matter of the Agreement

a. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.

b. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this

Agreement.

c. The Customer may distribute binaries compiled with

(4)

are met;

• The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met:

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no

representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement

distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

2. Support and Maintenance

SAP does not provide software maintenance for the STLport.

Software maintenance of the STLport therefore shall be not included.

All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and

(5)

free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures,

advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.

4. Limited Liability

a. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.

b. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances

indirect damage, consequential damage caused by a defect or lost profit.

d. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.

e. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.

f. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.

(6)

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and

database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the

documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon Meaning Caution

Example

Note

Recommendation Syntax

(7)

Installation Guide – Adaptive Computing Controller 1.0... 9

1 Introduction... 9

1.1 Naming Conventions...9

2 Installation – Step by Step ... 10

3 Patch – Step by Step ... 11

4 Installation Planning ... 12

5 Installation Preparations... 13

6 Installation Process... 15

6.1 Installing with SAPinst ...15

6.2 Input Parameters for the ACC Installation...18

7 Patch Process ... 19

7.1 Upgrading ACC...19

7.1.1 Download the required archive files ...19

7.1.2 Deploy the downloaded files ...19

8 Post-Installation and Post-Patch Activities ... 25

8.1 Configuration ...25

8.2 Restart the SAP System...25

9 Installation Check ... 28

9.1 Check the Readiness of ACC Backend ...28

9.2 Check the Readiness of ACC Frontend ...28

Appendix... 29

1. SAP J2EE Engine Ports ... 29

2. SAPinst - Installation Tool-specific Information... 31

2.1 Controlling a SAPinst Installation from a Remote Machine...31

2.2 Continuing an Interrupted Installation with SAPinst ...33

2.3 Handling the CD Browser Dialog ...35

(8)

It’s strongly recommended that you take the ACC

Implementation & Operation Guide as the first document

in setting up adaptive computing environment.

(9)

Installation Guide – Adaptive Computing Controller 1.0

1 Introduction

The Adaptive Computing Controller (ACC) is a system management like component based on the J2EE Engine of SAP Web Application Server 6.40.

It enables the system administrator to control the whole landscape from a single point through observation, operation and dynamic resource distribution.

1.1 Naming Conventions

In this documentation, the following naming conventions apply:

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<SAPINSID> SAP instance ID in uppercase letters

<sapinsid> SAP instance ID in lowercase letters

<sapinsnum> SAP instance number

<hostname> The host name in lowercase letters

<httpport> The http port number.

<DBSID> Database system ID in uppercase letters

<dbsid> Database system ID in lowercase letters

<SAPinst_INSTDIR> Installation directory for the SAP installation tool SAPinst

<INSTDIR> Installation directory for the SAP system

<CD-DIR> Directory on which a CD is mounted

<OS> Operating system name within a path

The following examples show how the variables are used:

− Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.

If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/C11.

(10)

2 Installation – Step by Step

This section provides an overview of the complete installation procedure.

If there is already an installed ACC, follow the chapter “Patch – Step by Step” (see chapter 3).

If the ACC has to be installed in a new environment, proceed with the next steps in this chapter “Installation – Step by Step”.

You can print out the tables below, follow the installation sequence exactly as shown in the tables and mark the step with ! if completed successfully.

Installation Planning

Careful planning is a prerequisite for the successful installation of the system.

! Action

Installation Planning

Installation Preparations

! Action

Prepare the SAP J2EE engine for the Adaptive Computing Controller installation Preparing the System for SAPinst GUI

Preparing the Installation CD

Installation Process

! Action

Installation Process

Post-Installation Activities

! Action Configurations

Restart the SAP System

(11)

3 Patch – Step by Step

Patching to ACC SP8 is only possible from ACC SP7.

This section provides an overview of the procedure to patch the ACC from SP7 to SP8.

You can print out the tables below, follow the patch sequence exactly as shown in the tables and mark the step with ! if completed successfully.

Patch Process

! Action Patch Process

Post-Patch Activities

! Action Configurations

Restart the SAP System

(12)

4 Installation Planning

Make sure that you read Installation – Step by Step before you start installation planning.

Check Documentation

• Read SAP Note 725397 Adaptive Computing (http://service.sap.com/notes) and all related information in the notes which are mentioned there.

• Recommended for troubleshooting: SAPinst Troubleshooting Guide (http://service.sap.com/sapinstfeedback)

The SAPinst Troubleshooting Guide provides up-to-date information about how to avoid installation failure and what to do if a failure occurs.

(13)

5 Installation Preparations

Prepare the SAP Web AS

A SAP J2EE Engine is the basis for the Adaptive Computing Controller.

Therefore, before you begin with the installation, make sure that the following prerequisites are met:

• SAP Web AS 6.40 J2EE system is successful Installed

Prepare the System for SAPinst GUI

The installation tool SAPinst uses the Java based graphical user interface SAPinst GUI.

You can run the SAPinst GUI on the installation host or, if required, you can control an installation using a standalone SAPinst GUI on a separate Windows or UNIX host.

This standalone SAPinst GUI enables you to perform the installation on a remote host while monitoring it with the SAPinst GUI from a local host. If you want to do that, see Controlling a SAPinst Installation from a Remote Machine.

Check the existence of a released Java Runtime Environment (JRE) on the host where SAPinst GUI should run:

Platform Required JRE for the SAPinst GUI

• Linux-IA32

• Linux-IA64

The required JRE is the same as for the SAP Web AS 6.40.

See at http://service.sap.com/platforms → Availability of SAP components in Detail → SAP Web AS / R/3 / Kernel

• JRE is not part of the SAP shipment. If necessary you need to download and install it.

• To check the version of an already installed JRE, enter:

java -version

For UNIX only

The JAVA_HOME environment variable must be set for the user root to the valid <JAVA_HOME> directory as follows:

Shell Used

Command

Bourne shell (sh)

JAVA_HOME= <path_to_JAVA_HOME>

export JAVA_HOME C shell

(csh)

setenv JAVA_HOME <path_to_JAVA_HOME>

Korn shell (ksh)

export JAVA_HOME <path_to_JAVA_HOME>

Other platforms No special JRE required for SAPinst GUI, because the JRE is integrated in the SAPinst GUI executable.

(14)

Preparing Required CD

Make sure that you have the following CD available: ACC Installation Master CD

(15)

6 Installation Process 6.1 Installing with SAPinst

Use

This procedure tells you how to run SAPinst to install ACC on released platforms.

It describes an installation where SAPinst GUI and SAPinst server are running on the same host. If you want to perform a remote installation, that is, SAPinst GUI is running on another host, see Controlling a SAPinst Installation from a Remote Machine.

SAPinst GUI Handling

The following push buttons are available on the different SAPinst GUI dialogs (Input screens, Installation Progress screen, Message Box):

Push Button Meaning

Back Displays the previous dialog for editing Next Displays the next dialog for editing

Cancel Cancels the installation with the following options:

− Stop

Stops the installation and leaves the installation files in the state in which they are at the current point in time. This means that you can continue the installation later from this point.

− Reset

Resets all installation input files. All files in the installation directory are removed from the system and no log files are saved. This means that you must start the installation from scratch again.

Logoff Cancels the connection to the SAPinst GUI only. The SAPinst server keeps on running.

Typical use case:

You need to logoff during the installation (for what reason ever) from the host where you control the installation with SAPinst GUI.

Then you can connect from another host to the running installation. Be aware, that you need the <installation CD> for that.

For more information on running SAPinst GUI standalone see Starting SAPinst GUI on a local Host

View Log Displays the content of the sapinst.log file during the installation.

Retry Performs the installation step again (if an error has occurred).

Stop Stops the installation and leaves the installation files in the state in which they are at the current point in time. This means that you can continue the installation later from this point.

Reset Resets all installation input files. All files in the installation directory are removed from the system. No backup is available.

This means that you must start the installation from the beginning again.

Procedure

(16)

Mount the CD locally. We do not recommend using Network File System (NFS).

Follow those steps:

On UNIX:

Make sure that your DISPLAY environment variable is set to <Host_name>:0.0, where <Host_name>

is the host on which the SAPinst GUI will be displayed.

Shell Used Command

Bourne Shell (bsh) DISPLAY=<Host_name>:0.0 export DISPLAY

C Shell (csh) ./setenv DISPLAY <Host_name>:0.0 Korn Shell (ksh) export DISPLAY=<Host_name>:0.0

Run sapinst from the mounted <installation_CD>:

If the WebAS is installed on an virtual hostname, the command is like this:

<installation_CD>/SAPINST/UNIX/<OS>/sapinst SAPINST_USE_HOSTNAME=<virtual hostname>

If the WebAS is installed on the physical hostname, the command can be called without the Parameter SAPINST_USE_HOSTNAME.

Normally, SAPinst creates the installation directory sapinst_instdir directly below the temporary directory ($TEMP or $TMP or /tmp). Therefore make sure that your operating system is configured not to delete the temporary directory and its subdirectories when the system is rebooted.

You need at least 40 MB free space for your temporary directory for each installation service.

If SAPinst does not find any temporary directory, the installation terminates with the error FCO- 00058.

The created directory sapinst_instdir - which is the current working directory for your installation - and SAPinst GUI starts automatically by displaying the Welcome screen.

4. In the first input dialog screen, select the following service from the tree structure and choose Next.

J2ee Engine: AC1 Instance number: <sapinsnum>

Follow the instructions on your screen. The necessary input parameters are listed in the section Input Parameters for ACC Installation.

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

(17)

The screen shot below shows the ACC-SAPinst screen during an installation.

Troubleshooting

• If an error occurs during the dialog phase, SAPinst:

− Stops the installation

− Displays a dialog that informs you about the error

You can now directly view the log file by choosing View Logs.

Finally, you must abort the installation with Stop or Reset, and try to solve the problem.

• If an error occurs during the processing phase, SAPinst:

− Stops the installation

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

− Directly view the log file by choosing View Logs.

(18)

− Stop or Reset the installation.

For more information, see Continuing an Interrupted Installation with SAPinst .

6.2 Input Parameters for the ACC Installation

The following table lists prompts from SAPinst, provides you with a description of the prompt and outlines the information you might need to enter to continue with the installation of your SAP instance.

Window Description CD Browser CD Name

A CD Browser may ask for the file LABEL.ASC containing the required label.

The default path is: <default_path>

For more information on the CD Browser dialog, see Handling the CD Browser Dialog Selecting the

SAP J2EE Engine

Select the existing SAP J2EE engine on which you want to install the Adaptive Computing Controller.

(19)

7 Patch Process 7.1 Upgrading ACC

Patching to ACC SP8 is only possible from ACC SP7 and patching to ACC SP9 is only possible from SP8.

Before starting the patch procedure, read the valid note for SP8 (see SAP note 864855: “Support Package 08 for ACC 1.0”) and for SP9 (see SAP note 897651: “Support Package 09 for ACC 1.0”).

7.1.1 Download the required archive files

Download the required SCA files from the following link:

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000604910&

Navigate to Download area for support packages ACC 1.0 SPX Æ ADAPT. COMP. CONTR. 1.00 Æ ADAPT. COMP. CONTR. 1.00 Æ OS independent.

The two necessary files for a complete patching process start with ACCXX_X and ACCONLXX_X. The “XX”

in the filenames show the version of the ACC. Download the latest version of each file type.

7.1.2 Deploy the downloaded files

Use the Software Deployment Manager (SDM) for patch to the required SP as follows:

To patch the ACC you have to use the SDM and it is very important to deploy both archive files separately. First deploy the ACCONLXX_X.sca and then in a second step deploy the ACCXX_X.sca.

Step1: Log onto SDM

• Start an X-Server on the local host.

• Follow the steps:

On UNIX:

Make sure that your DISPLAY environment variable is set to <IP LOCAL HOST>:0.0, where the local host is <IP LOCAL HOST>.

Shell Used Command

Bourne Shell (bsh) DISPLAY=<IP LOCAL HOST>:0.0 export DISPLAY

C Shell (csh) ./setenv DISPLAY <IP LOCAL HOST>:0.0 Korn Shell (ksh) export DISPLAY=<IP LOCAL HOST>:0.0

• Go to the directory /usr/sap/<SID>/<INST-NAME>/SDM/program

• Start Software Deployment Manager(SDM)

• Log onto SDM

a. To connect, click on the icon 1) indicated in the figure below to connect.

b. Then login to SDM with the SDM password given during the WebAS installation.

c. In the field Hostname, enter the hostname which the WebAS was installed on (basically the hostname which is stored in the SecureStore of the ConfigTool).

(20)

1.) connect

2.) sdm

(21)

Step2: Deploy ACCONL01_0.sca

• Select ACCONL01_0.sca file:

a. Navigate to the Deployment tab and click on the “+” icon to add the new archive file.

b. Select ACCONL01_0.sca file (filenames may differ depending on the number of the SP) and click Choose.

• Select upgrade mode

a. click the button 1) in the following screenshot.

b. Set the radio button to Update deployed SDAs/SCAs that have any version.

c. To start the deployment, click Next and then Start. Finally, click the Confirm button to confirm deployment in the last SDM screen.

(22)

Step3: Deploy ACC01_0.sca

• Select ACC01_0.sca file:

a. Navigate to the Deployment tab and click on the “+” icon to add the new archive file.

b. Select all of the ACC01_0.sca file (file names may differ depending on the number of the SP) and click Choose.

(23)

• Select upgrade mode

a. click the button 1) in the following screenshot.

b. Set the radio button to Update deployed SDAs/SCAs that have any version.

c. To start the deployment, click Next and then Start. Finally, click the Confirm button to confirm deployment on the last SDM screen.

(24)

• Allow the SDM to restart the engine when the SDM prompts you.

(25)

8 Post-Installation and Post-Patch Activities 8.1 Configuration

•

For intallation

To make sure ACC works fine after installation, follow the steps which are described in the ACC Implementation and Operation Guide, and to the ACC Customizing Guide..

You can find all Guides at:

•

For patch

The configuration parameters of ACC are re-organized in SP8 to be more user-friendly All your old settings in previous SPs should have been migrated to SP8 successfully after the patch process. It’s recommended that you double check in the configtool whether all your old settings are still there in SP8 (refer to the ACC Implementation Guide and to the ACC Customizing Guide).

It is recommended that J2EE Engine will be restarted to make sure all the configurations take effect.

You can find all above mentioned guides at

8.2 Restart the SAP System

8.2.1 Starting and Stopping the SAP System (Unix) Use

You need to check that you can start and stop the SAP system after the installation using the scripts startsap and stopsap in the exe directory.

Prerequisites

• You have signed on to the SAP system hosts as user <sapsid>adm.

• For more information on how to start or stop database-specific tools, see the database-specific

information in this documentation and the documentation from the database manufacturer.

• If you want to use startsap or stopsap (for example, in a script) and require the fully qualified name

of these SAP scripts, create a link to startsap or stopsap in the home directory of the corresponding user.

If there are multiple SAP instances on one host – for example, a central instance and a dialog instance – you must add an extra parameter to the scripts:

startsap <instanceID>

stopsap <instanceID>

For example, enter:

startsap DVEBMGS00

SAP Web AS J2EE only system

The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a J2EE dialog instance is J<Instance_Number>.

(26)

When you use stopsap in an MCOD system with two central instances, only one central instance and the database are shut down. Therefore, you must first stop the other SAP system with stopsap R3 or make sure that it has already been stopped.

1. Enter the following to stop dialog instances:

stopsap

2. To stop the central instance, the central services instance and the database instance:

{ If you have a central system – that is, central instance, central services instance and database instance on the same host – enter the following on the central system host:

stopsap

This stops the central instance, the central services instance and then the database.

You can stop the SAP system and the database separately by entering the command stopsap R3 <instanceID of central instance>, then stopsap R3 <instanceID of

central services instance> and then stopsap <instanceID> .

Make sure that you always stop the central instance first and the central services instance second because otherwise the database cannot be stopped.

There is also the parameter J2EE that is a synonym for the parameter R3. For SAP Web AS ABAP+J2EE systems, you can enter either the command stopsap R3 or stopsap J2EE to stop the SAP instance comprising both ABAP and J2EE.

{ If you have a distributed system – that is, central instance, central services instance and database instance on different hosts – do the following:

i.On the central instance host, enter:

stopsap R3

ii.On the central services instance host, enter:

stopsap R3

iii. On the database host, enter:

stopdb

Make sure that no SAP instance is running before you enter stopdb on a standalone database server. No automatic check is made.

Starting the SAP System

.

1. To start the central instance and database instance:

{ If you have a central system – that is, central instance, central services instance and database instance on the same host – enter the following on the central system host:

(27)

startsap R3 <instanceID of central services instance>

startsap R3 <instanceID of central instance>

Make sure that you always start the database first because otherwise the central services instance and the central instance cannot be started.

There is also the parameter J2EE that is a synonym for the parameter R3. For SAP Web AS ABAP+J2EE systems, you can enter either the command startsap R3 or startsap J2EE to start the SAP instance comprising both ABAP and J2EE.

{ If you have a distributed system – that is, central instance, central services instance and database instance on different hosts – do the following:

i. On the database host, enter:

startdb

ii.On the central services instance host, enter:

startsap R3

iii. On the central instance host, enter:

startsap R3

2. Enter the following to start dialog instances, if there are any:

Startsap

(28)

9 Installation Check

9.1 Check the Readiness of ACC Backend

Step1. Start up the J2EE Administrator Tool

In folder /usr/sap/<SAPID>/<SAPINSID>/j2ee/admin, there’s a go file. Run it.

The password must be inputted to login.

The password is set during the installation of the Web AS Then the SAP J2EE Engine Administrator window appears.

Step2. In the SAP J2EE Engine Administrator window, choose the Cluster tab. In <SAPSID>Æ

<SAPINSID> -> Services, if there’s a service named Adaptive Computing Controller, it means the ACC backend has been installed successfully.

9.2 Check the Readiness of ACC Frontend

It will take several minutes for ACC service to start and load relevant data from SLD. Please be patient in the meantime to wait the system start up.

The following link can be used to access ACC UI:

http://<hostname>:<httpport>/webdynpro/dispatcher/sap.com/ca~ac~acc~accadministrationtools/Admi nistrationTools

You can refer to the SAP J2EE Engine Ports for the calculation of <httpport>.

If the URL is opened successfully and the logging in window appears, it means the ACC frontend has been installed successfully.

(29)

Appendix

1. SAP J2EE Engine Ports

These ports are used for communication with the J2EE Engine as part of the SAP Web AS. They are generated at installation time and when new cluster elements have to be created.

For the J2EE Engine, 20 ports are available for the dispatcher element and 80 are available for the server elements, since five is the maximum number of ports for a server process. Therefore, no more than 16 server cluster elements can be created on one instance.

The J2EE Engine ports must meet the following requirements:

• The port value must be a number over 50000

• For each cluster element the ports begin with 50000+100*instance_number, where

instance_number is a two digit number from 00 to 99 specifying the number of central instance and dialog instances

{ For dispatcher cluster elements

The ports are created from 50000+100*instance_number+port_index, where port_index is a number from 0 to 19 inclusive.

Dispatcher port_index Values

Index Port Name

0 HTTP port

1 HTTP SSL port

2 IIOP Initial Context port

3 IIOP SSL port

4 P4 port

5 P4 HTTP Tunneling port

6 P4 SSL port

7 IIOP port

8 Telnet port

10 JMS port

According to the formula mentioned above and the port_index values, the dispatcher ports for the J2EE Engine are as follows (in the table below, NN corresponds to instance_number):

J2EE Engine Dispatcher Ports

Service Name Port Number Default Value Range (min-max)

HTTP 5NN00 50000 50000-59900

HTTP over SSL 5NN01 50001 50001-59901

IIOP 5NN07 50007 50007-59907

IIOP Initial Context 5NN02 50002 50002-59902

IIOP over SSL 5NN03 50003 50003-59903

(30)

JMS 5NN10 50010 50010-59910

{ For server cluster elements

The ports are created from 50000+100*instance_number+20+n*5+port_index,where n is the number of server elements from 0 to 15 andport_index is from 0 to 4.

The ports for J2EE Engine server3 with instance_number=15 are from 51535 (50000+100*15+20+3*5+0) to 51539 (50000+100*15+20+3*5+4).

Server port_index Values

Index Port Name

0 Join port

1 Debug port

According to the formula mentioned above and the port_index values, the server ports for the J2EE Engine are as follows:

J2EE Engine Server Ports

Internal Port Value

Server Join Port For s0: 5NN20, for s1=5NN25, for

s2=5NN30….for s15=5NN95, where s0, s1, s2,..s15 shows the number of server processes and NN is instance_number.

Server Debug Port For s0: 5NN20, for s1=5NN25, for

s2=5NN30….for s15=5NN95, where s0, s1, s2,..s15 shows the number of server processes and NN is instance_number.

Example

The port for P4 on a dispatcher element with instance_number=15 is:

P4 port=50000+100*15+4=51504

(31)

2. SAPinst - Installation Tool-specific Information 2.1 Controlling a SAPinst Installation from a Remote Machine

Purpose

You can run the SAPinst GUI in standalone mode to perform a remote installation.

This enables you to install an SAP system on another host (the remote host) while monitoring the installation with the SAPinst GUI on your local Windows or UNIX computer (the local host).

Prerequisites

• Make sure that you have performed the preparation activities for your local host (SAPinst GUI host) and your remote host.

For more information, see “Installation Preparations” in this documentation.

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

To test this:

− Log on to your remote host and enter the command ping <local host>.

− Log on to the local host and enter the command ping <remote host>.

Process Flow

1. Starting SAPinst on the Remote Host 2. Starting SAPinst GUI on the Local Host

2.1.1 Starting SAPinst on the Remote Host

Use

You use this procedure to set up your remote host where SAPinst server should run only. The remote host is the host where you want to install the SAP system.

Procedure

1. Log on to your installation host as user with <the authorized role; for example: administrator or root>

rights.

2. Depending on the operating system insert these steps and delete the non-applicable, if required:

On UNIX:

Mount the <installation_CD>.

3. Depending on the operating system do the following steps:

On UNIX:

Run the following command:

<installation_CD>/SAPINST/UNIX/<OS>/sapinst SAPINST_START_GUI=false From now on, there is no difference between Windows and UNIX Platforms.

(32)

Use

You use this procedure to set up your local host when you want to run SAPinst GUI standalone on your local host.

Typical examples for running or starting SAPinst GUI only are:

− Controlling a SAPinst installation from an other host

− Connecting a SAPinst GUI after choosing the push button Logoff during the installation.

Procedure

1. Log on to your installation host as user with < the authorized role; for example: administrator or root>

rights.

On UNIX:

Run the script startInstGui.sh from the mounted <installation_CD>:

<installation_CD>/SAPINST/UNIX/<OS>/

The SAP Installation GUI Connection dialog appears.

4. Enter the host name of the Installation Host and the same Port as SAPinst uses on the remote host and choose OK.

SAPinst GUI now connects to the SAPinst server and the first dialog of the installation appears.

(33)

2.2 Continuing an Interrupted Installation with SAPinst

Use

SAPinst does not abort the installation in error situations. Therefore, you can continue an interrupted installation when you have:

• Not canceled the installation

That is, the error dialog box is still displayed and SAPinst is waiting for your input. You proceed as follows:

In the error dialog box, you choose Retry.

SAPinst now retries the installation step.

• Already canceled the installation

That is, the installation was aborted. There are the following situations:

If you have canceled with…

Meaning

Stop Since SAPinst records the installation progress in the keydb.xml file, you can continue the installation from the failed step without repeating previous steps.

During this procedure, you can Reset the installation, too, if required.

Reset You must restart from the beginning, that is, with the default keydb.xml file as delivered.

In some cases, you must uninstall already installed components, before repeating the installation from the beginning. For example, this applies to an SAP system

installation. For more information, see the description on how to de-install a component in the corresponding installation guide.

Prerequisites

You have solved the problem that caused the error situation.

Procedure

1. Log on to your installation host as user with < the authorized role; for example: administrator or root>

rights.

On UNIX:

Run the script sapinst from the mounted <installation_CD>:

<installation_CD>/SAPINST/UNIX/<OS>/

(34)

If there is only one component to install, SAPinst directly displays the dialog What do you want to do? without presenting the Welcome screen.

The What do you want to do? screen appears.

5. In the What do you want to do? screen, decide between the following alternatives and choose OK.

Alternative Behavior Run a new

Installation

The installation will not be continued.

Instead, SAPinst deletes the mentioned installation directory for the chosen installation service and starts the installation from the beginning.

The log files from the old installation are put into a backup directory with the following naming convention:

<log_day_month_year_hours_minutes_seconds > (log_01_Oct_2003_13_47_56, for example).

Continue old installation

The installation of the mentioned installation service will be continued from the point of failure.

(35)

2.3 Handling the CD Browser Dialog

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

SAPinst displays this window in following situations:

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

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

Choose one of the following actions:

Action Result You do not enter any Package

Location and leave the flag Check Location deselected.

SAPinst skips the check and you can continue the installation procedure.

However, SAPinst asks later for the missing LABEL.ASC (see step 2 below).

You enter the path of the Package Location and leave the flag Check Location deselected.

SAPinst skips checking the label location, but your entered package locations are used later for the installation.

SAPinst only asks again for a missing

LABEL.ASC if the package location is incorrect (see step 2 below).

You enter the path of the

Package Location and select the flag Check Package Location

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

If all locations are correct, SAPinst does not ask again for the LABEL.ASC files later.

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

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

Additionally, you can copy the installation package by entering a location in the column Copy Package to.

Adaptive Computing Controller 1.0

Installation Guide