Scm Opt Windows

Installation GuideSAP SCM Optimizer 7.03 or higher on Windows

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 2.0 – 2012-03-12

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/

instguides.

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2011-11-08 Initial Version

2.0 2012-03-13 More Generic Version

2/34 PUBLIC 2012-03-12

http://service.sap.com/instguides


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2 Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . . 9

3.3 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.3.1 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.3.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3.3 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 18

4.3.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.3.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.3.6 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.2 Performing a Setup Check of the RFC Gateway . . . . . . . . . . . . . . . . . . . . . . . . 25

5.3 Customizing the Optimizer Destination Entries . . . . . . . . . . . . . . . . . . . . . . . 27

5.4 Testing the Optimizer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.5 Applying the Latest Patches and Support Packages . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6.1 Uninstalling SAP SCM Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2012-03-12 PUBLIC 3/34

This page is left blank for documents that are printed on both sides.

1 Introduction

This documentation describes how to install SAP SCM Optimizer.

You can install SAP SCM Optimizer either on an ABAP application server or on a dedicated server

running on Windows with SAP Standalone Gateway installed.

Make sure that you have read the Master Guide for your SAP Business Suite Application before you

continue with this installation guide. You can find a printed version of the Master Guide in your

installation package or you can download the latest version at http://service.sap.com/

instguides.

1.1 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the

most recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of these SAP Notes, which you can find at: http://

service.sap.com/notes

SAP Note Number Title Description

1686826 Implementation of SCM Optimizer SCM-Optimizer information about the SAP system

1577112 SCM Optimizer: Sizing Information SCM Optimizer-specific sizing information and other requirements

1 Introduction

1.1 SAP Notes for the Installation

2012-03-12 PUBLIC 5/34



http://service.sap.com/notes

http://service.sap.com/notes

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1686826&_NLANG=en&_NVERS=0



2 Planning

2.1 Planning Checklist

This section tells you how to plan the installation of the SCM Optimizer:

You make yourself familiar with the implementation considerations [page 7].

2.2 Implementation Considerations

You can install SAP SCM Optimizer either on top of an existing ABAP application server or on a dedicated

server.

The following applies:

■ SAP SCM Optimizer runs on Windows, Linux, and AIX platforms.

For more information, see the Product Availability Matrix at http://service.sap.com/pam.

■ If you use a dedicated server for SAP SCM Optimizer, you need to install an SAP Standalone Gateway

beforehand. You can find the documentation Installation Guide — Standalone Gateway on <OS platform>

— For SAP Systems Based on SAP NetWeaver 7.0 including Enhancement Package 3 at: http://

service.sap.com/installnw70 Installation - Standalone Engines

RECOMMENDATION

The CPU time and memory requirement can be very high when you execute an optimizer

instance. If insufficient resources are available, this can impact heavily on performance or

affect correct implementation. Therefore, we highly recommend that you install an SAP

SCM Optimizer server for a production or test environment on dedicated hardware (that is,

no additional applications will run on this hardware). If you want to run other applications

on the optimizer server, you must make sure that these are executed in sequence or that the

hardware used provides sufficient resources. This also applies to executing several optimizer

instances.

■ Check SAP Note 1577112 for sizing information and other requirements.

2 Planning

2.1 Planning Checklist

2012-03-12 PUBLIC 7/34

http://service.sap.com/pam

http://service.sap.com/installnw70




3 Preparation

3.1 Preparation Checklist

You have to complete the following preparations:

1. If you want to install the SCM Optimizer on top of an existing ABAP application server, you make

sure that there is an ABAP application server in your system landscape.

2. If you want to install the SCM Optimizer on a dedicated host, you make sure that there is a

standalone SAP gateway on this host. If required, install it as described in the documentation

Installation Guide — Standalone Gateway on <OS platform> — For SAP Systems Based on SAP NetWeaver 7.0

including Enhancement Package 3, which you can find at: http://service.sap.com/installnw70

Installation - Standalone Engines

3. You make sure that you have the required user authorization for running SAPinst [page 9].

4. You prepare the installation media [page 10] for the SCM Optimizer installation.

3.2 Required User Authorization for Running SAPinst

Although SAPinst automatically grants the required rights to the user account used for the installation,

you have to check whether this account has the required authorization to perform the installation.

The authorization required depends on whether you intend to perform a domain or local installation.

If necessary, you have to ask the system administrator to grant the account the necessary authorization

before you start the installation. If you attempt the installation with an account that has not the

required authorization, the installation aborts.

This section informs you about the authorization required for a domain and a local installation.

Procedure

CAUTION

Do not use the user <sapsid>adm for running SAPinst.

Domain Installation

For a domain installation the account used for the installation needs to be a member of the local

Administrators and the domain Admins group of the domain involved. All machines in the system

must belong to the same domain. In a domain installation, the user information is stored centrally on

the domain controller and is accessible to all hosts in the system.

If the SAP system is to be distributed across more than one machine, SAP strongly recommends you

to perform a domain installation to avoid authorization problems.

3 Preparation

3.1 Preparation Checklist

2012-03-12 PUBLIC 9/34


CAUTION

■ ● You use the same master password on all hosts.

● All hosts belong to the same Windows work group.

■ For performance and security reasons, SAP does not support an SAP system installation on

a domain controller.

■ If for any reason, the account used for the installation is not a member of the domain

Admins group, you can perform the installation with a domain user who is a member of the

local Administrators group. However, the domain administrator has to prepare the system

appropriately for you.

For a domain installation, you need to:

1. Check that the account used for the installation is a member of the domain Admins group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the domain Admins group.

Local Installation

For a local installation the account used for the installation needs to be a member of the local

Administrators group of the machine involved. In a local installation, all Windows account

information is stored locally on one host and is not visible to any other hosts in the system.

CAUTION

Do not use the Windows built-in account Administrator or the renamed built-in account to

install your SAP system with SAPinst. The built-in account only has restricted network access

rights that are required by SAPinst. If you renamed the built-in account Administrator, do not

create a new account named Administrator.

For a local installation, you need to:

1. Check that the account used for the installation is a member of the local Administrators group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the local Administrators group.

3.3 Preparing the Installation Media

This section describes how to prepare the installation media, which is available as follows:

■ You obtain the installation media as part of the installation package.

■ You can also download the installation media from SAP Service Marketplace, as described at the

end of this section.

Procedure

1. Identify the required media for your installation as listed below.

3 Preparation


10/34 PUBLIC 2012-03-12

The media names listed below are abbreviated.

The following table shows the media required for the installation of SAP SCM Optimizer:

SCM Optimizer Release Installation Media

SAP SCM Optimizer 7.03 Installation SAP SCM Optimizer Installation Master 7.03

SAP SCM Optimizer 9.0 Installation SAP SCM Optimizer Installation Master 9.0

2. Make the required installation media available on each installation host.

CAUTION

■ If you copy the media to disk, make sure that the paths to the destination location of the

copied media do not contain any blanks and commas.

■ If you perform a domain installation and do not want to copy the media but use network

drives for mapping the installation media, make sure that the <sapsid>adm user has access

to the UNC paths of the network drives.

Downloading Installation Media from SAP Service Marketplace

You normally obtain the installation media as part of the installation package from SAP.

However, you can also download installation media from the software distribution center on SAP

Service Marketplace using one of the following paths:

■ http://service.sap.com/swdc Installations and Upgrades My companys application components

<your product> <your product version>

■ http://service.sap.com/swdc Installations and Upgrades A-Z index <first letter of your product>

<your product version>

NOTE

If you download installation media, note that they might be split into several files. In this case,

you have to reassemble the required files after the download.

1. Identify all download objects that belong to one installation medium according to one or both of

the following:

■ Material number

All download objects that are part of an installation medium have the same material number

and an individual sequence number:

<material_number>_<sequence_number>

EXAMPLE

51031387_1

51031387_2

...

■ Title

All objects that are part of a medium have the same title, such as

<solution><media_name><OS> or <database>RDBMS<OS> for RDBMS media.

3 Preparation


2012-03-12 PUBLIC 11/34

http://service.sap.com/swdc

http://service.sap.com/swdc

2. Download the objects to the download directory.

3. To correctly re-combine the media that are split into small parts, you must unpack all parts into

the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the

medium and copies the data into it. The data is now all in the correct directory, the same as on the

medium that was physically produced. For more information, see SAP Note 1258173.

3 Preparation


12/34 PUBLIC 2012-03-12


4 Installation

4.1 Installation Checklist

This section provides information about the steps that you have to perform to install SAP SCM

Optimizer.

1. Make sure that you have completed the planning [page 7] and preparation [page 9] activities before you

start the installation.

2. You run the installation with SAPinst [page 13].

Additional information about SAPinst:

■ How to Avoid Automatic Logoff by SAPinst [page 16]

■ Interrupted Installation with SAPinst [page 17]

■ Performing a Remote Installation with SAPinst [page 18]

■ Starting SAPinst GUI Separately [page 19]

■ Running SAPinst in Accessibility Mode [page 21]

■ Troubleshooting with SAPinst [page 23]

4.2 Running SAPinst

This section describes how to run the installation tool SAPinst. SAPinst includes a GUI client and a GUI

server, which both use Java.

The procedure describes an installation where SAPinst, GUI client, and GUI server are running on the

same host. In the following, GUI client and GUI server are addressed as “SAPinst GUI”.

Useful Information About SAPinst

■ When you start SAPinst, it automatically starts the SAPinst GUI.

■ SAPinst creates the installation directory sapinst_instdir, which is located directly in the %

ProgramFiles% directory. If SAPinst is not able to create sapinst_instdir there, it tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.

RECOMMENDATION

We recommend that you keep all installation directories until the system is completely and

correctly installed.

■ SAPinst creates a subdirectory for each installation option called sapinst_instdir

\<installation_option_directory>, which is located in %ProgramFiles%.

4 Installation

4.1 Installation Checklist

2012-03-12 PUBLIC 13/34

■ SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located

in %TEMP%, %TMP%, %TMPDIR%, or %SystemRoot%. These files are deleted after SAPinst has stopped

running.

The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely

delete it.

The temporary directory also contains the log file dev_selfex.out from the extraction process,

which might be useful if an error occurs.

CAUTION

If SAPinst cannot find a temporary directory, the installation terminates with the error

FCO-00058.

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between SAPinst, GUI server, GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with the GUI client.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for

free port numbers. If the search fails, SAPinst exits.

In this case or if you want SAPinst to use specific ports, open a command prompt and change to

the required directory as follows:

Execute sapinst.exe with the following command line parameters:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>

● GUISERVER_HTTP_PORT=<port_number_http_server>

■ To see a list of all available SAPinst properties, open a command prompt and start SAPinst with

command line parameter -p:

sapinst.exe -p

■ If you need to run SAPinst in accessibility mode, make sure that you have activated and adjusted

accessibility settings as described in Running SAPinst in Accessibility Mode [page 21].

■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.

NOTE

If you need to terminate SAPinst you can do this by choosing File Exit in the menu of

the Program Starter window.

Prerequisites

■ Make sure that you use an account with the required user authorization to run SAPinst [page 9].

Procedure

1. Log on to the installation host using an account with the required user authorization to run SAPinst [page

9].

4 Installation

4.2 Running SAPinst

14/34 PUBLIC 2012-03-12

CAUTION

Do not use an existing <sapsid>adm user.

2. Make the medium for the installation master available on the installation host.

3. Start SAPinst by double-clicking sapinst.exe from the following path:

<media drive>:\IM_WINDOWS_X86_64

NOTE

If you need to perform the installation in accessibility mode, open a command prompt, change

to the <media drive>:\DATA_UNITS\<product>_IM_WINDOWS_<your platform> directory,

and execute sapinst.exe –accessible.

For more information, see Running SAPinst in Accessibility Mode [page 21].

The GUI starts automatically by displaying the Welcome screen.

4. If SAPinst prompts you to log off from your system, log off and log on again.

SAPinst restarts automatically.

5. Follow the instructions in the SAPinst input screens and enter the required parameters.

NOTE

For more information about the input parameters, position the cursor on the parameter and

press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.

This screen shows both the parameters that you entered and those that SAPinst set by default. If

required, you can revise the parameters before starting the installation.

6. To start the installation, choose Start.

SAPinst starts the installation and displays the progress of the installation.

When the installation option has finished successfully, SAPinst displays the message Execution of

<Option_Name> has completed.

7. We recommend that you delete the directory %userprofile%\.sdtgui\.

8. If you copied installation media to your hard disk, you can delete these files when the installation

has successfully completed.

More Information ■ How to Avoid Automatic Logoff by SAPinst [page 16]




■ Running SAPinst in Accessibility Mode [page 21]


4.3 Additional Information About SAPinst

The following sections provide additional information about SAPinst:

4 Installation


2012-03-12 PUBLIC 15/34

■ How to Avoid Automatic Logoff by SAPinst [page 16]




■ Running SAPinst with Accessibility Mode [page 21]


4.3.1 How to Avoid Automatic Logoff by SAPinst

When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user

account used for the installation has the required privileges and authorization.

For a domain installation, the account needs to be both a member of the local Administrators group

and the domain Admins group. For a local installation, the account needs to be a member of the local

group Administrators group.

In both cases, the user account must be authorized to do the following:

■ Act as part of the operating system

■ Adjust memory quotas for a process

■ Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automatically logs

the account off to activate them. To avoid SAPinst logging the account off, you can set these rights

manually before you start the installation.

Procedure

You perform the following steps to assign these rights to the user account used for the installation.

CAUTION

Be aware that domain policies override locally defined policies. This means that if you want to

grant domain administrator rights to a user who belongs to the local Administrators group,

make sure that you have also defined domain administrator rights for this user on domain level.

1. Choose Start Settings Control Panel Administrative Tools Local Security Policy .

2. In the Local Security Settings window, choose Local Policies User Rights Assignment. .

3. Double-click the required right under Policy and choose Add User or Group.

4. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.

5. Confirm your entry and then repeat the steps for each remaining policy that the user requires for

the installation.

6. Log off and log on again to apply the changes.

4 Installation


16/34 PUBLIC 2012-03-12

More Information

Required User Authorization for Running SAPinst [page 9]

4.3.2 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

■ An error occurred during the Define Parameters or Execute phase:

SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses

and a dialog box appears. The dialog box contains a short description of the choices listed in the

table below as well as a path to a log file that contains detailed information about the error.

■ You interrupted the installation by choosing Cancel in the SAPinst menu.

CAUTION

If you stop an option in the Execute phase, any system or component installed by this option

is incomplete and not ready to be used. Any system or component uninstalled by this option

is not completely uninstalled.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below).

Continue SAPinst continues the installation from the current point.

View Log Access installation log files.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to

continue an interrupted installation after an error situation.

1. Log on as a user who is a member of the local administrators group.

2. Make the medium for the installation master available on the installation host.

3. <media drive>:\IM_WINDOWS_X86_64

4. Double-click sapinst.exe.

NOTE

4 Installation


2012-03-12 PUBLIC 17/34

5. From the tree structure in the Welcome screen, select the installation option that you want to

continue and choose Next.

The What do you want to do? screen appears.

6. In the What do you want to do? screen, decide between the following alternatives and continue with

Next:

Alternative Behavior

Run a new option SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>

EXAMPLE

log_01_Oct_2008_13_47_56

CAUTION

SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the old option SAPinst continues the interrupted installation option from the point of failure.

4.3.3 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst runs on the

remote host, and the SAPinst GUI runs on the local host. The local host is the host from which you

control the installation with the SAPinst GUI. The SAPinst GUI connects using a secure SSL connection

to SAPinst.

Prerequisites

■ The remote host meets the prerequisites for starting SAPinst as described in Running SAPinst [page

13]

■ Both computers are in the same network and can ping each other.

To test this:

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

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

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host

have exactly the same version. You can check this by using the option –version as described in

the procedure below and in the procedure in Starting SAPinst GUI Separately [page 19].

4 Installation


18/34 PUBLIC 2012-03-12

■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER

command line parameter, make sure that this user exists on the remote host.

Procedure

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Make the Installation Master medium available on your remote host.

3. Open a command prompt and change to the required directory by entering the following

command:

<media drive>:\IM_WINDOWS_X86_64

4. Check the version of the sapinst executable by entering the following command:

sapinst –version

The version of the sapinst executable must be exactly the same as the version of the

sapinstgui executable on the local host (see also Starting SAPinst GUI Separately [page 19]).

5. Execute sapinst.exe -nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the

command prompt:

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

<port_number> to continue with the installation

6. Start the SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 19].

4.3.4 Starting SAPinst GUI Separately

You use this procedure to start the SAPinst GUI separately. You need to start the SAPinst GUI separately

in the following cases:

■ You closed the SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still

running.

■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from

SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 18].

Prerequisites

■ The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst

as described in Running SAPinst [page 13].

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host

have exactly the same version. You can check this by using the option –version as described in

the procedure below and in the procedure in Performing a Remote Installation with SAPinst [page 18].

4 Installation


2012-03-12 PUBLIC 19/34

Procedure

Starting SAPinst GUI on Windows

1. Make the Installation Master medium available on the host on which you want to start the SAPinst

GUI.

2. Change to the directory of the sapinstgui executable using the following command:

cd /d <media drive>:\IM_WINDOWS_X86_64

3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant

command line parameters:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

sapinstgui.exe –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst

[page 18]).

2. Start the SAPinst GUI by entering the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui_client> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

sapinstgui.exe -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to


● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui.exe -host <remote_host> -port





The SAPinst GUI starts and connects to SAPinst.

Starting SAPinst GUI on UNIX

1. Make the Installation Master medium available on the installation host.

4 Installation


20/34 PUBLIC 2012-03-12

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

2. Change to the directory of the sapinstgui executable using the following command:

Change to the directory of the sapinstgui executable using the following command: cd

<Mountpoint of Installation Master medium>/IM_<your OS>

3. Start the SAPinst GUI by executing ./sapinstgui with the relevant command line parameters:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

./sapinstgui –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst

[page 18]).

2. Start the SAPinst GUI by entering the following command:

./sapinstgui -host <remote_host> -port





■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed

as follows:

● If you are performing a local installation with SAPinst and SAPinst GUI running on the

same host, execute the following command:

sapinstgui -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to


● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui -host <remote_host> -port





The SAPinst GUI starts and connects to SAPinst.

4.3.5 Running SAPinst in Accessibility Mode

You can also run SAPinst in accessibility mode. The following features are available:

4 Installation


2012-03-12 PUBLIC 21/34

■ Keyboard access:

This feature is generally available for all operating systems.

■ High-contrast color:

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.

■ Custom font setting:

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.

Procedure

Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before

you start SAPinst or the SAPinst GUI.

NOTE

The following procedure applies for Windows Server 2008 and might be different when using

another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

2. Select Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme drop-down box.

To define your own color schemes, choose Advanced.

Running SAPinst in Accessibility Mode

You can either perform a local installation, where SAPinst and SAPinst GUI are running on the same

host, or a remote installation, where SAPinst and SAPinst GUI are running on different hosts.

■ Local installation:

Start SAPinst as described in Running SAPinst [page 13] by executing the following command:

sapinst.exe –accessible

■ Remote installation:

1. Start SAPinst on the remote host by executing the following command from the command

line as described in Performing a Remote Installation with SAPinst [page 18]:

sapinst.exe –nogui

2. Start SAPinst GUI on the local host by executing the following command from the command

line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 19]:

sapinstgui.exe -accessible –host <remote_host> -port


4 Installation


22/34 PUBLIC 2012-03-12

4.3.6 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

■ Stops the installation

■ Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known SAPinst issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the Define Parameters or Execute phase, do either of the following:

■ Try to solve the problem

■ Stop the installation by choosing Cancel in the SAPinst menu.

For more information, see Interrupted Installation with SAPinst [page 17].

■ After resolving the problem, you can continue the installation by choosing Retry.

4. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%

\.sdtgui\ for errors.

■ If the SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile

% directory.

5. If you cannot resolve the problem, create a customer message using component BC-INS.

4 Installation


2012-03-12 PUBLIC 23/34



5 Post-Installation

5.1 Post-Installation Checklist

You need to perform the following post-installation steps for SAP SCM Optimizer after SAPinst has

finished:

1. You perform a setup check of the RFC gateway [page 25].

2. You customize the SAP Optimizer destination entries [page 27].

3. You test the SCM Optimizer installation [page 27].

4. You check for patches and support packages [page 27].

5.2 Performing a Setup Check of the RFC Gateway

We recommend that you perform a setup check of the RFC gateway.

Procedure

1. If you use a standalone gateway instance, start the gateway instance.

2. Log on to the ABAP application server.

3. Call transaction SM59.The Display and maintain RFC destinations screen appears.

4. Open the node TCP/IP connection.

5. For the first optimizer server, you have to adapt the RFC entries that are existing in your system.

The RFC entries existing in your system might look as follows:

NOTE

You only have to adapt the entries that actually exist in your system, for example

OPTSERVER_CS01.

Note that SAP TM systems might only have entries starting with “T” (for example TVRG01) .

EXAMPLE

■ OPTSERVER_CS01

■ OPTSERVER_CTM01

■ OPTSERVER_DPS01

■ OPTSERVER_MMP01

■ OPTSERVER_SEQ01

■ OPTSERVER_SNP01

■ OPTSERVER_VSR01

■ OPTSERVER_TSPS01

5 Post-Installation

5.1 Post-Installation Checklist

2012-03-12 PUBLIC 25/34

■ OPTSERVER_TVRG01

■ OPTSERVER_TVSR01

■ OPTSERVER_TVSS01

NOTE

For any additional optimizer server, you have to create a new RFC entry (for example,

OPTSERVER_CTM02). Make sure that this new RFC entry ends with a two digit number that is

different from 01.

To adapt an RFC entry:

1. Double-click the destination name OPTSERVER_<Optimizer>01.The RFC Destination

OPTSERVER_<Optimizer>01 screen appears.

2. Depending on the server, you must do the following to check the RFC entries:

Standalone SAP SCM Optimizer on Separate HostSAP SCM Optimizer and ABAP Application Server on Same Host

1. Choose Start on Explicit host.2. In the Program field, check your program path (see table Program Paths

of RFC Entries below).3. Check the name of your Target Host.4. Enter the number of the gateway host and the corresponding

gateway service SAPGW<GW_NO>.

NOTE

You can find out the required parameters on your target host as follows:1. On your target host, call transaction SMGW.2. Choose Goto Parameters Display (see entries for

gateway hostname and gateway service).5. Confirm with OK.

1. Choose Start on Application server.

2. In the Program entry field, check your program path (see table Program Paths of RFC Entries below).

CAUTION

If your ABAP application server is a Unicode system, you must do the following in addition

to the above setting for each OPTSERVER_<Optimizer>01 destination:

1. Choose the tab Unicode.

2. You must select the indicator Unicode, and in the group frame Character Conversion, leave

the indicator at the default setting.

RFC Program Path

OPTSERVER_CTM01 <OPT_DRIVE>:\apoopt\ctm\bin\ctmsvr.exe

OPTSERVER_DPS01 <OPT_DRIVE>:\apoopt\dps\bin\dsoptsvr.exe

OPTSERVER_SNP01 <OPT_DRIVE>:\apoopt\snp\bin\snpopsvr.exe

OPTSERVER_SEQ01 <OPT_DRIVE>:\apoopt\seq\bin\seqopsvr.exe

OPTSERVER_VSR01 <OPT_DRIVE>:\apoopt\vsr\bin\vsropsvr.exe

OPTSERVER_MMP01 <OPT_DRIVE>:\apoopt\mmp\bin\mmpopsvr.exe

OPTSERVER_CS01 <OPT_DRIVE>:\apoopt\cs\bin\csopsvr.exe

OPTSERVER_TSPS01 <OPT_DRIVE>:\apoopt\cs\bin\csopsvr.exe

5 Post-Installation

5.2 Performing a Setup Check of the RFC Gateway

26/34 PUBLIC 2012-03-12

RFC Program Path

OPTSERVER_TVRG01 <OPT_DRIVE>:\apoopt\vsr\bin\vsropsvr.exe

OPTSERVER_TVSR01 <OPT_DRIVE>:\apoopt\vsr\bin\vsropsvr.exe

OPTSERVER_TVSS01 <OPT_DRIVE>:\apoopt\vsr\bin\vsropsvr.exe

NOTE

You only have to adapt the entries that actually exist in your system, for example

OPTSERVER_CS01.

Note that SAP TM systems might only have entries starting with “T” (for example TVRG01) .

3. Save your entry and choose Exit.

4. Repeat the steps 1. to 3. for the remaining RFC entries.

5.3 Customizing the Optimizer Destination Entries

Procedure


2. Call transaction SPRO.

3. Choose SAP Reference IMG.

4. Expand the Cross-Application Components tree and choose Processes and Tools for Enterprise Applications

Remote Control and Communication Framework .

5. Choose the Execute button of the step Edit Destinations and maintain it according to the customizing

documentation.

6. Perform the Connection Test in this transaction after the customization.

5.4 Testing the Optimizer Installation

Procedure


2. Call transaction RCC_CUST and click the connection test button. All tests must be successful (green

light).

5.5 Applying the Latest Patches and Support Packages

Procedure

Proceed as described in SAP Note1686826.

5 Post-Installation

5.3 Customizing the Optimizer Destination Entries

2012-03-12 PUBLIC 27/34



6 Additional Information

This section contains additional information on the SAP SCM Optimizer installation:

■ Uninstalling the SAP SCM Optimizer [page 29]

6.1 Uninstalling SAP SCM Optimizer

Proceed as follows to uninstall SAP SCM Optimizer

Procedure

1. If your SAP SCM Optimizer runs on a dedicated host, stop the SAP Standalone Gateway.

2. Delete the directory <drive>:\apoopt completely with all its content.

3. If required, uninstall also the SAP Standalone Gateway.

6 Additional Information

6.1 Uninstalling SAP SCM Optimizer

2012-03-12 PUBLIC 29/34

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

30/34 PUBLIC 2012-03-12

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

2012-03-12 PUBLIC 31/34

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly 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 MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

32/34 PUBLIC 2012-03-12


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2012 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Date post:	03-Jan-2016
Category:	Documents
Upload:	veesams-srinivas
View:	115 times
Download:	5 times

Scm Opt Windows

Documents