clm 10 e sorc

Installation GuideDocument version: 1.0 2014-05-16

SAP Sourcing 10.0For Deployment on SAP NetWeaver 7.31 SP10 with Database Oracle

INTERNAL

Document History

CautionBefore you start the installation, make sure that you have the latest version of this document. The latest version is on SAP Service Marketplace at service.sap.com/eso.

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

Version Date Description

1.0 2014-05-16 Initial Release

2

INTERNAL Copyright 2014 SAP AG.All rights reserved.

SAP Sourcing 10.0Document History

http://service.sap.com/eso

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 Complete Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 Add Java Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Copy SAP Sourcing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 Prepare Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Identify Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Create Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Install Oracle Text Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Create Oracle Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Connect Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Install Obfuscation Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Copy JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Verify Settings for SAP Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1 Install SAP Sourcing Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2 Configure Software for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Execute Configure Utility Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Specify Location of SAP NetWeaver Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Update Java Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Select tools.jar File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Select Symantec.jar File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Include Custom JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Update WAR, EAR, and SCA Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Change Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Define Application Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Maintain Database Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.1 Install Baseline Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2 Define J2EE System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3 Install Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.4 Deploy SAP Sourcing SCA File to Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.5 Starting and Stopping SAP Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.6 Install Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Install Optimizer License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Deploy Optimizer SCA File to Optimizer Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Verify Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.7 Install Contract Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SAP Sourcing 10.0Content

INTERNAL Copyright 2014 SAP AG.

All rights reserved. 3

Enable JAVA-Based SAP Sourcing DOCX Generation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.1 Uninstalling and Reinstalling SAP Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.2 Undeploying SCA Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4


SAP Sourcing 10.0Content

1 Introduction

SAP Sourcing covers the entire strategic source to contract process across all categories of spend. It consists of a suite of the following solutions:

SAP Strategic Sourcing SAP Contract Lifecycle Management (SAP CLM) SAP Supplier Management

The key features of each of these solutions are listed below.

SAP Strategic Sourcing

SAP Strategic Sourcing lets you drive sustainable cost savings while ensuring sustainable sourcing processes.

This solution provides the following key features:

Project management

Bring internal stakeholders together using a shared, online project plan. Keep team members up-to-date using status reports and alerts. Track opportunities for savings. Leverage preconfigured business process templates to reduce cycle time and help ensure that best practices are repeated throughout your organization.

Collaborative, multiround sourcing processes

Enable multiple rounds to identify qualified suppliers and negotiate pricing while leveraging collaborative scoring and bid optimization features. Carry key data forward into a comprehensive request for proposal or auction.

Requests for information, proposals, and quotations

Conduct simple or complex sourcing activities for direct, indirect, and service categories by automating the creation of requests for information, proposals, and quotations.

Robust reporting

Analyze supplier responses using side-by-side comparisons, pricing, and potential savings reports. Help ensure that diverse suppliers are being invited to participate in sourcing events. Evaluate award decisions over time to understand what key criteria are being used in awarding business to suppliers.

Effective auctions

Create competitive bidding environments using reverse, forward, and Dutch auctions. Interact with suppliers in real time, using instant messaging, bidding consoles with real-time updates, and graphical representations of auction activities. Easily manage bidding and disclosure rules, such as bid and rank visibility, automatic extensions, weighted-bidding cost factors, staggered start and end times for individual items, and reserve prices.

Integrated sourcing and procurement execution

Integrate sourcing and procurement processes with SAP ERP and SAP SRM to drive compliance and realize savings.

SAP Contract Lifecycle Management

SAP Contract Lifecycle Management (SAP CLM) lets you optimize corporate contracts by automating contract creation, enhancing visibility, improving compliance, and delivering rapid time to value. By managing the entire contract lifecycle consistently across the enterprise, you can realize the full value of your contracts, resulting in higher profits and lower legal and financial risk.


Standardized, automated contract creation from clause libraries and templates

SAP Sourcing 10.0Introduction



Streamline the approval process with consistent, preapproved language, controlled edits, and appropriate approvals.

Fully searchable repository Contract performance management

Encourage purchasing under contract terms, track accruals against contracts, and streamline activities by quickly reporting on outstanding commitments and contracts.

Integration with back-end systems and processes

Improve compliance by integrating contract information into back-end systems. Management of expirations and contract audits

Optimize contract negotiations by initiating timely renewals and leveraging the full contract history to negotiate better terms and conditions.

SAP Supplier Management

SAP Supplier Management lets you optimize supplier onboarding, information management, evaluation, and performance management. With full supplier visibility, you can make more-informed, collaborative supply decisions that boost profitability.


Supplier onboarding and qualification

Automate supplier onboarding processes with supplier self-service and identify the right suppliers easily by streamlining the process for gathering additional information.

Supplier development

Drive improved performance with centralized monitoring and administration of supplier development. Supplier performance management

Manage scorecards and alerts related to key supplier performance indicators. Supplier information management

Capture, centralize, and share the most up-to-date supplier data across the enterprise, enabling more-informed, collaborative supply decisions.

More Information

SAP Library for SAP Sourcing on SAP Help Portal at help.sap.com SAP Business Suite SAP Sourcing

For information about supported software and hardware configurations, and for sizing guidelines, see the Product Availability Matrix for SAP Sourcing 10.0 at service.sap.com/pam.

1.1 About This Document

This guide describes how to install SAP Sourcing 10.0 on SAP NetWeaver NetWeaver 7.31 SP10 or later, usage type AS JAVA, with database Oracle.

The audience for this guide is anyone involved in the installation of SAP Sourcing and SAP CLM.

More Information

Troubleshooting [page 37]

6



http://help.sap.comhttp://service.sap.com/pam

For information about architecture and landscape, see the master guide for SAP Sourcing on SAP Service Marketplace at service.sap.com/eso.

For information about configuring SAP Sourcing, see the configuration guide for SAP Sourcing on SAP Service Marketplace at service.sap.com/eso.

1.2 Before You Start

You should have at least some basic familiarity with the SAP Sourcing application or have a strong IT background. The following are key skillsets for success:

Basic understanding of the target application server platform Familiarity with the target database and a basic understanding of how to set up a JDBC connection and how to

debug failures Basic working knowledge of the target operating system and a basic understanding of the different file systems,

security schemes, and available tools in the target operating system

1.2.1 Naming Conventions

In this guide, the following naming conventions apply.

Variables

The following table explains the variables that are used in this guide.

Table 2

Variable Description

SAP system ID in uppercase letters

SAP system ID in lowercase letters

Name of the corresponding host

Home directory of the user performing the deployment

Database system ID in uppercase letters

Database system ID in lowercase letters

Installation directory for the SAP system

Directory on which a CD is mounted

Directory on which a DVD is mounted

Operating system name within a path




http://service.sap.com/esohttp://service.sap.com/eso

2 Preparation

2.1 Complete Checklist

Be sure to complete the following checklist, as the installer could otherwise fail.

Procedure

1. Check whether make_sda.bat (Windows) or make_SDA.sh or make_SDA.csh (UNIX) is present in the scripts folder (for example, C:\usr\sap\CE1\J00\j2ee\deployment\scripts).This tool is used to convert .ear format to .sda format. If the file is not present, ask your SAP NetWeaver system administrator to verify that the application server for SAP NetWeaver is installed correctly.

2. Check whether dctool.bat (Windows) or dctool.sh (UNIX) is present in the SAP NetWeaver directory. This tool is used to convert .sda format to .sca format.

ExampleIf your SAP NetWeaver instance is in C:\usr\sap\NW1, check whether the di_cmd_tools.zip file in C:\usr\sap\NW1\SYS\global is unzipped. If it is not unzipped, unzip it. After you unzip this file, dctool.bat (Windows) or dctool.sh (UNIX) should be available at C:\usr\sap\NW1\SYS\global\di_cmd_tools\dc.

If the file is not present, ask your SAP NetWeaver system administrator to verify that SAP NetWeaver is installed correctly.

NoteIf you intend to use Linux or another Unix-based operating system, you must convert the dctool.sh file from Windows format to Unix format, as follows:

Table 3

Operating System

Execute These Commands

AIX strings dctool.sh > dctool.sh.tmprm dctool.shmv dctool.sh.tmp dctool.sh

HP-UX dos2ux dctool.sh

Solaris

Linux

dos2unix dctool.sh > dctool.sh.tmprm dctool.shmv dctool.sh.tmp dctool.sh

3. Check that the following environment variables are set correctly; otherwise, you will not be able to launch the dctool successfully, and the installer will fail to create the SCA files.

8


SAP Sourcing 10.0Preparation

JAVA_HOME NWDITOOLLIB

The environment variable NWDITOOLLIB must refer to the lib directory of the dctool. Note that you must use the absolute path of the lib directory. Also edit the dctool.bat (Windows) or dctool.sh (UNIX) to set the value of NWDITOOLLIB in the script.

PATHMake sure that the path to the Java binary file is at the beginning of the PATH environment variable.

Before using the installer, verify that you can launch the dctool successfully by entering dctool.bat (Windows) or dctool.sh (UNIX) in a DOS prompt or shell. If the dctool is launched successfully, you will see the following prompt:

dc>

For an example of a successfully running dctool, including the changes that were applied to the dctool.bat file to make the dctool work properly, see below. The changes are in bold and assume a system ID of CE1.




Example/**********DCTOOL.BAT**********/

@echo off

REM **********

REM *

REM * Batch file to launch new DC command line tool.

REM * This batch takes the Jars from directory lib.

REM * Environment variable NWDITOOLLIB must point to the absolute path of the lib

REM * directory.

REM *

REM * SAP AG 2008

REM *

REM **********

REM default value for lib directory, user should set the absolute path

REM set NWDITOOLLIB=../lib

set NWDITOOLLIB=C:\usr\sap\CE1\SYS\global\di_cmd_tools\lib

set JAVA_HOME=C:\usr\sap\\SYS\exe\jvm\NTI386\sapjvm_X.X\sapjvm_X\jre

if "%NWDITOOLLIB%"=="../lib" echo Warning: it is strongly recommended to use an absolute path as value for environment variable NWDITOOLLIB

if "%NWDITOOLLIB%"=="" goto usage

if "%JAVA_HOME%"=="" goto usage

set APPL=com.sap.tc.di.cmdline.ApplicationLauncher

set startup=%NWDITOOLLIB%\tc~di~cl~application_launcher_api.jar

set PARAM_JDK=-Ddctool.JDK_PATH="%JAVA_HOME%"

SET RETURNCODE=0

REM use system property -Xmx to increase the size for the virtual memory

REM use system property -Xss to increase the stack size

call "%JAVA_HOME%\bin\java" -classpath "%startup%" -Xmx256m -Xss20m -Dappl.jars="%NWDITOOLLIB%" -Dappl.classname=com.sap.tc.cetool.DcConsoleApplication -Ddctool.JDK_PROPERTY_NAME="default" %PARAM_JDK% %APPL% %* SET RETURNCODE=%errorlevel%

goto :end

:usage

echo Incorrect usage, the following environment variables must be set:

echo.

echo NWDITOOLLIB: must point to the "lib" folder that contains required Jars.

echo JAVA_HOME: must point to the installation folder of a Java SDK installation

echo.

goto end

:end

EXIT /B %RETURNCODE%

REM this is the end

/**********DCTOOL.BAT**********/

10



For more information about the dctool, see the readme.txt file in the same folder as the dctool.

2.2 Add Java Parameter

Procedure

1. Launch the J2EE Engine configuration tool.Only valid for: Windows |

For example, navigate to C:\usr\sap\XXX\J00\j2ee\configtool and launch configtool.bat.End of: Windows |

Only valid for: UNIX |

For example, navigate to /usr/sap/XXX/J00/j2ee/configtool and launch configtool.sh.End of: UNIX |

2. Navigate to Cluster Data VM Parameters Additional .3. In Java Parameters, add the following line if it does not already exist:

-Djava.awt.headless=true

2.3 Copy SAP Sourcing Media

Procedure

1. Download the SAP Sourcing media from SAP Software Download Center at service.sap.com/swdc.2. Copy the downloaded SAP Sourcing media to the application server.

2.4 Prepare Database Server

The tasks in Prepare Database Server must be carried out by an experienced database administrator.

2.4.1 Identify Server

Procedure

Identify the Oracle server to create an application database schema. The schema should be configured for a minimum of 5G. Actual database storage requirements can vary with use. The database server must be configured for UTF-8 data encoding to support alternate/multiple languages.




http://service.sap.com/swdc

2.4.2 Create Tablespaces

Procedure

SAP Sourcing supports up to three tablespaces to contain tables, indexes, and blobs, respectively. You should create at least one tablespace. You can create two additional tablespaces if you want to maintain your tables, indexes, and blobs in individual tablespaces.

2.4.3 Install Oracle Text Search

Procedure

NoteThis process is necessary only if you have not already installed Oracle Text Search.

Install Oracle Text Search on the database management system (DBMS) as described below. This is required for the platform to be installed successfully. It is also required if you want to use global search. For information about global search, see SAP Library for SAP Sourcing on SAP Help Portal at help.sap.com/sourcing SAP Sourcing 10.0 Help for Purchasers [choose a language] Getting Started General Functions Global Search .

1. In a command prompt, change the directory to the ctx admin directory by entering the following command, replacing c:\oracle\product\11.2.0\dbhome_1 with the location of your Oracle home directory.cd c:\oracle\product\11.2.0\dbhome_1\ctx\admin

2. In a second command prompt, log on to SQL*Plus by entering the following command:

sqlplus system;3. Enter the password for the system user.4. In the SQL prompt, enter the following command:

connect SYS as SYSDBA;5. In the SQL prompt, enter the following command:

@catctx.sql " NOLOCK is the desired password for the ctxsys user is the default tablespace for the search (for example, MYUSER) is the default temp space for the search (for example, TEMP) The last part of the command can be LOCK or NOLOCK; it specifies whether the ctxsys user account is

locked or not.

2.4.4 Create Oracle Service Account

The Oracle service account enables SAP Sourcing to connect to the database.

12



http://help.sap.com/sourcing

Procedure

1. Identify and create an Oracle service account. This may be the schema owner account.2. Grant the following privileges to the Oracle service account:

CONNECT RESOURCE CTXAPP UNLIMITED TABLESPACE CREATE DIMENSION CREATE VIEW

3. Assign the following default roles to the Oracle service account:

CONNECT RESOURCE CTXAPP

ExampleCREATE USER IDENTIFIED BY

DEFAULT TABLESPACE TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT ACCOUNT UNLOCK;

GRANT CONNECT TO ;

GRANT RESOURCE TO ;

GRANT CTXAPP TO ;

ALTER USER DEFAULT ROLE CONNECT,RESOURCE,CTXAPP;

GRANT UNLIMITED TABLESPACE TO ;

GRANT CREATE VIEW TO ;

2.4.5 Connect Schema

Procedure

Obtain the connection information for the Oracle schema from your database administrator. To configure the application, you need:

Server host name System ID (SID) Port number Oracle user name Oracle password Database owner




2.4.6 Install Obfuscation Toolkit

Procedure

Verify and install Oracle toolkit DBMS_OBFUSCATION_TOOLKIT as described below. This toolkit supports Data Encryption Standard (DES) encryption, which is required by the application to encrypt sensitive data stored in the database. This toolkit is part of your Oracle installation media.

1. On the server machine, open a command window and change the directory to the following, where C:\oracle\product\11.2.0\dbhome_1 is the location of your Oracle home directory:

C:\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN2. Connect using SQLPLUS as SYS and run dbmsobtk.sql and prvtobtk.plb.3. Execute the following GRANT command:

grant execute on dbms_obfuscation_toolkit to public;4. Exit SQLPLUS.

2.4.7 Copy JDBC Driver

Prerequisites

Before copying the JDBC Driver, check the version of the JDBC Driver. It has to be 11.2.0.2.0 or the DBImport will throw a JDBC Driver not supported error. For more details, see SAP Note 1642326.

Procedure

Find the Oracle JDBC driver (ojdbc6.jar) in the following location and copy the driver to the application server, where it can be referenced during the SAP Sourcing installation process:

/product/11.2.0/dbhome_1/jdbc/lib

NoteThe installer copies the JDBC driver to the \lib directory as oracle.jar. To avoid confusion, this file can be renamed ojdbc6.jar.

NoteSAP Sourcing requires a minimum of 25-30 available database connections per active SAP Sourcing service to ensure sufficient connections exist to accommodate SAP Sourcing database activity.

2.4.8 Verify Settings for SAP Sourcing

Procedure

To support SAP Sourcing analytics, check that your Oracle server is set to the values in the following table. You can display the current settings and set the parameters using SQL*Plus; log on as the SYS user. Alternatively, you can

14



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

use the Oracle Enterprise Manager Database Control or Oracle Enterprise Manager Grid Control if you have installed it.

Table 4: Oracle Server Settings

Setting Value Comments

COMPATIBLE 8.1.0 (or greater) Optional

GLOBAL_NAMES TRUE

OPEN_CURSORS 500 500 is the minimum value. It can be higher if needed.

OPTIMIZER_MODE CHOOSE

PARALLEL_MAX_SERVERS 12 (or greater)

QUERY_REWRITE_ENABLED FALSE

QUERY_REWRITE_INTEGRITY TRUSTED

SQL92_SECURITY TRUE Optional

STAR_TRANSFORMATION_ENABLED TRUE

If you change any database configuration settings, restart the database.




3 Installation

Process Flow

The two primary steps of the installation procedure are:

1. Install SAP Sourcing binary files [page 16].2. Configure software for deployment [page 17].

NoteSAP Sourcing should be installed in the SAP NetWeaver server instance directory using the SAP NetWeaver Administrator user (adm). The SAP NetWeaver Administrator user must have complete access to the SAP NetWeaver and SAP Sourcing installation directories.

More Information


3.1 Install SAP Sourcing Binary Files

Prerequisites

Ensure that the database administrator has prepared the database server. For more information, see Prepare Database Server [page 11].

Procedure

1. Run the setup command for your operating system:

Table 5

Windows setup.exe

Solaris

AIX

HP-UX

Linux

chmod 755 setup.binsetup.bin

The SAP Sourcing installation wizard appears.2. Deploy the software binaries as follows:

1. Accept the license terms of the software.2. Specify the directory location for the SAP Sourcing software. This will be the SAP Sourcing home directory.

16


SAP Sourcing 10.0Installation

RecommendationWe recommend using lowercase characters for the SAP Sourcing home directory because there have been instances with Linux and UNIX where mixed-case characters have caused the installation to fail.

We recommend not using 00 at the end of the installation folder because it may conflict with other SAP NetWeaver instances.

3. Click Install and complete the steps in the wizard.

3.2 Configure Software for Deployment

After successful installation of the SAP Sourcing binary files, the configure utility launches. If it does not start automatically, start it manually by launching the configure utility from the bin folder in the SAP Sourcing home directory. For more information, see Execute Configure Utility Manually [page 17].

Whenever you change any of the parameters in this section, you must select the update SCA files option to rebuild the SCA file. You must then redeploy the SCA file as described in Deploy SAP Sourcing SCA File to Application Server [page 28].

NoteYou can use Symantec virus scanning, or you can use VSI. The installation steps you execute will differ depending on which virus scanning method you choose, so you much choose before proceeding.

3.2.1 Execute Configure Utility Manually

Normally the configure utility runs through a wizard. Run it manually if:

The configuration tool is not launched automatically after successful installation of the SAP Sourcing binary files.

You want to run the configuration tool to reconfigure the application after the initial installation of SAP Sourcing.

This is often done to rebuild the EAR and SCA files after the inclusion of custom jar files or the application of a software patch.

Procedure

Only valid for: Windows |

Go to \bin and double-click configure.exe.End of: Windows |

Only valid for: Solaris |

1. Open a command prompt and enter the following command to change the permissions of the configureSolaris.bin file so that it can be executed:chmod 755 configureSolaris.bin

2. Run:




/bin/configureSolaris.binEnd of: Solaris |

Only valid for: Linux |

1. Open a command prompt and enter the following command to change the permissions of the configureLinux.bin file so that it can be executed:chmod 755 configureLinux.bin

2. Run:

/bin/configureLinux.binEnd of: Linux |

Only valid for: AIX |

1. Open a command prompt and enter the following command to change the permissions of the configureAIX.bin file so that it can be executed:chmod 755 configureAIX.bin

2. Run:

/bin/configureAIX.binEnd of: AIX |

Only valid for: HP-UX |

1. Open a command prompt and enter the following command to change the permissions of the configureHPUX.bin file so that it can be executed:chmod 755 configureHPUX.bin

2. Run:

/bin/configureHPUX.binEnd of: HP-UX |

Result

The configure utility guides you through the sequence of tasks you need to perform, based on your particular configuration.

In the configure utility, click Next and follow the wizard prompts through the steps that follow.

3.2.2 Specify Location of SAP NetWeaver Home Directory

Procedure

Specify the location of the SAP NetWeaver home directory by entering the path to the J00 (or instance name) folder, for example, C:\usr\sap\ce1\J00 if the SAP NetWeaver home directory is directly on your C: drive. Do not enter the path beyond the J00 (or instance name) folder.

18



3.2.3 Update Java Home Directory

Procedure

The configuration tool provides a default Java home directory. You can select a different Java directory to be used by the SAP Sourcing standalone tools. The Java home directory used by the application is defined by the J2EE application server.

We recommend that you specify the Java Virtual Machine (JVM) that is used to run your application server here. This is because a keystore is installed into the database using Java Cryptography Extension (JCE). The application will not start up if the JVM that built your database and the JVM that starts the application do not contain the same version of JCE. We provide a mechanism for reinstalling the keystore if this occurs. For more information, see SAP Note 1304005.

ExampleOnly valid for: Windows |

D:\usr\sap\\SYS\exe\jvm\NTI386\sapjvm_X.X\sapjvm_X\jreEnd of: Windows |


/usr/sap//SYS/exe/jvm/linuxx86_64/sapjvm_X.X/sapjvm_X/jreEnd of: UNIX |

3.2.4 Select tools.jar File

SAP Sourcing requires use of the tools.jar file, available in your JDK.On the Select Tools Jar File screen of the installation wizard, enter the tools.jar file by clicking Choose and browsing to the file. The tools.jar file is present in the path \lib, where is the path pointing to the JDK. This is the same path you entered earlier as the value of the JAVA_HOME system variable.For example, if the value of JAVA_HOME is C:\jdk1.6, you would enter C:\jdk1.6\lib\tools.jar.To replace an existing entry with a different file, click Choose and browse to the new file. This overrides the existing entry.

To remove an existing entry without choosing a different file, click Restore Default.

3.2.5 Select Symantec.jar File

NoteThis step is necessary only if you have chosen to use Symantec for virus scanning.

If you have chosen to use Symantec for virus scanning, you must provide the location of the symantec.jar file, as follows:





1. On the Configuration Tasks screen of the utility, make sure that the checkbox for Include Symantec.jar file is checked. If it is not checked, check it.

2. On the Symantec Jar page, use the Choose button to browse to the location of the symantec.jar file.

3.2.6 Include Custom JAR Files

Procedure

This is required only if you are including custom JAR code in your deployment.

If you select the include custom JAR files option, you must also select the update WAR, EAR, and SCA files option. The tool allows you to provide up to five custom JAR files in the following directory:

/custom

On the Specify Custom JAR Files screen, you enter a custom JAR file by clicking Choose and browsing to the file. To replace an existing entry with a different file, click Choose and browse to the new file. The existing entry is overwritten. To remove an existing entry, click Restore Default.

The files are included in the generated EAR file automatically.

In very rare cases, if you have more than five custom JAR files, you can copy them to the /custom directory manually, and run the update WAR, EAR, and SCA files option again.

3.2.7 Update WAR, EAR, and SCA Files

Procedure

This is required if you are configuring the system for the first time, and whenever you change any of the other parameters.

The SAP EAR, SDA, and SCA files are built and stored in the /fsapp directory.

3.2.8 Change Session Timeout

Procedure

This is optional.

The deployment descriptor for the SAP Sourcing application defaults to a 30-minute session timeout. To change this setting, choose the change session timeout option.

20



3.2.9 Define Application Context

Procedure

The default context is /, meaning that the application responds to servlet requests that come in as http://webserver/servlet. If you run in a non-default context, for example, /sourcing, the application responds only to requests that come in as http://webserver/sourcing/servlet.

You must create a unique application context under / because the default context / is reserved by SAP NetWeaver.

3.2.10 Maintain Database Connection Information

Procedure

1. Select the appropriate database.2. Provide the JAR file.

The JAR file name depends on your database version and JVM version.3. Enter the database connection information as shown in the following table.

Table 6: Database Connection Information

Field Description

Database Driver Class Required

oracle.jdbc.driver.OracleDriver

Database URL Required

The URL is required to connect to the database, and the user name and password to connect to the database schema. Modify the URL to include the host name, port, and system ID (SID) for your server. Your database administrator can provide you with the port number and SID. The URL must be in the following format:

jdbc:oracle:thin:@::

For example:

jdbc:oracle:thin:@localhost:1521:XE

User Name, Database Password Required

The user ID and password of the Oracle account that is used by the application to access the database. This is the connection information that you obtained during Preparation [page 8]. Your database administrator can provide you with this information.

Database Owner Required

This is typically the user name.




Field Description

Database Table Space, Database Index Space, Database Blob Space

Optional

Names of custom database tablespaces that are used for storing tables, indexes, and blobs. If you leave these fields blank, the default Oracle settings are used.

When the installation is complete, click Done to exit the wizard.

22



4 Post-Installation

Process Flow

After installing SAP Sourcing, carry out the following post-installation tasks:

1. Install baseline database [page 23].2. Define J2EE system properties [page 24].3. Install language packs [page 26] (optional).4. Define initial and maximum Java heap size.5. Deploy SAP Sourcing SCA file to application server [page 28].6. Install optimizer [page 30].7. Install contract generation [page 35].

Starting and Stopping SAP Sourcing

For information about starting and stopping SAP Sourcing during deployment, see Starting and Stopping SAP Sourcing [page 30].

More Information


4.1 Install Baseline Database

If this is a new installation and you do not have a baseline database, install it by running the DB Importer as described below. The DB Importer is used for initial database creation, database upgrades, language pack installation, and various database scripts provided with the software.

Prerequisites

You have installed Oracle Text Search. The installation will fail if this is not installed properly. For more information, see Install Oracle Text Search [page 12].

Procedure

1. Launch the DB Importer. It is located at:Only valid for: Windows |

\bin\dbimport.batEnd of: Windows |


/bin/dbimport.shEnd of: UNIX |

2. On the Setup tab of the DB Importer, use the file picker dropdown to browse to and choose the following file:

SAP Sourcing 10.0Post-Installation



fcieso.jar/com/sap/eso/odp/install/scripts/product/install_root.xml3. Leave the Context field blank.4. Enter the user name system and password manager.

NoteAfter logging on to the application, you will be required to change this password immediately and secure it properly.

5. Run the script by choosing Run.6. Once the script is complete, on the Script tab, verify successful installation. A successful script run is indicated

by a green checkmark. An unsuccessful script run is indicated by a red cross. If the script run was unsuccessful, click the Errors tab to troubleshoot. Resolve the errors and rerun the script. The failure must be resolved before the system can be used.

Troubleshooting

The following table contains troubleshooting tips.

Table 7: Troubleshooting

Problem Solution

You are unable to connect to the database in dbimport. Run the configure utility and verify or reset the database connection string, user name, and password.

The script does not start properly. Ensure that you have selected the JAR file from the dropdown rather than browsing to it.

Some creation steps fail. Verify that the database user has been created according to the SAP-recommended setup.

Result

The default database install provides enough information to create the system context for further configuration. The system context is only for creating and configuring the enterprise context(s).

4.2 Define J2EE System Properties

A dbimport script automates the process of setting the J2EE system properties.

Procedure

For more information about the following procedure, see SAP Note 1158487.

1. Start the DB Importer.2. Select the system context using user name system and password manager.3. In the DB Importer, use the file picker to browse to and select fciinstall.jar/scripts/dev/

import_netweaver_system_properties.xml and choose Open.4. On the Setup tab, choose Run.

Successful results are indicated with a green checkmark on the Script tab.

24




Result

The following tables show the properties that are installed automatically. Note that you can verify the J2EE system properties only after the application is deployed.

Table 8: J2EE System Properties

Field Value

jms.common.queueconnectionfactory jmsfactory/default/fs.common.QueueConnectionFactory

jms.destination.queue.jmx_queue jmsqueues/default/fs.queue.JmxQueue

jms.destination.queue.iapi_event_queue jmsqueues/default/fs.queue.IapiEventQueue

jndi.java.naming.factory.initial com.sap.engine.services.jndi.InitialContextFactoryImpl

jndi.java.naming.factory.url.pkgs com.sap.tm.jndi.providers

jndi.java.naming.provider.url

This property is installed with the following value:

localhost:50004

Modify this property to reflect the actual host and port. You do this as follows:

1. Log on to SAP Sourcing as the system user.2. On the System Setup tab, find the Configuration section

and choose System Properties.

The port is set to 50004 by default, which is believed to be the correct default port for instance 0. If SAP Sourcing is installed on an instance other than 0, or on an instance that does not use the default port, the port will be different. Consult your SAP NetWeaver system administrator to determine the correct port.

Examplep123456.wdf.sap.corp:50004

Table 9: Optimizer System Properties for SAP NetWeaver

Field Value

optimization.config.queue_connection_factory jmsfactory/default/fs.optimization.QueueConnectionFactory

optimization.config.halt_destination jmsqueues/default/fs.optimization.HaltAllocationQueue

optimization.config.request_destination jmsqueues/default/fs.optimization.AllocationRequestQueue

optimization.config.status_destination jmsqueues/default/fs.optimization.AllocationStatusQueue

jndi.java.naming.factory.initial com.sap.engine.services.jndi.InitialContextFactoryImpl

jndi.java.naming.factory.url.pkgs com.sap.tm.jndi.providers




Field Value

optimization.jndi.java.naming.provider.url

This property is installed with the following value:

localhost:50004

Modify this property to reflect the actual host and port. You do this as follows:

1. Log on to SAP Sourcing as the system user.2. On the System Setup tab, find the Configuration section

and choose System Properties.

The port is set to 50004 by default, which is believed to be the correct default port for instance 0. If the optimizer is installed on an instance other than 0, or on an instance that does not use the default port, the port will be different. Consult your SAP NetWeaver system administrator to determine the correct port.

Examplep123456.wdf.sap.corp:50004

NoteWhen using a SAP NetWeaver application server and deploying the optimizer on a server that is remote from the SAP Sourcing server, you must conditionally initialize the system property optimization.jndi.force_remote = TRUE as follows:

1. Log on to SAP Sourcing as the system user.2. On the System Setup tab, find the Configuration section and choose System Properties.3. Choose New.4. In the Set field, choose optimization from the dropdown.5. In the Name field, choose optimization.jndi.force_remote from the dropdown.6. In the Value field, enter TRUE.7. Save your entries.

4.3 Install Language Packs

This is optional.

SAP Sourcing supports the following languages:

English Chinese, Simplified Czech Danish Dutch Finnish French German

26



Hungarian Italian Japanese Korean Polish Portuguese (Brazilian) Russian Serbian Slovak Spanish Swedish Turkish

By default, only English is installed.

Procedure

NoteIt is best to stop SAP Sourcing when executing this procedure. If you choose not to stop SAP Sourcing, then after you finish you need to refresh localized resources, as follows:

1. Log in as the system user.2. Navigate to System Information Cache tab.3. Choose Refresh Localized Resources.

.

NoteIf you encounter unexpected errors in the languages after the upgrade is complete, you may need to restart the Sourcing instance.

1. From a command prompt, go to the /bin installation directory and enter dbimport to start the DB Importer utility.

2. On the Setup tab, select the fci.jar file (where is the language that you want to install).

3. Navigate to the /i18n/ODP/ directory (where is the language that you want to install) and select the install_language.xml script file.

4. On the Setup tab, open the input help dropdown for the Context field and choose System Context.5. As user name, enter the system manager user system and enter the appropriate password.6. Choose Run.7. On the Script tab, verify whether the script run was successful (green checkmarks) or whether there were any

errors (red Xs). You can try the following to identify and remove errors:

Check and address any warnings or errors on the Errors tab. Check the log files under the /logs folder in the home directory. Warnings are not saved to the error log.

8. On the Setup tab, select the fci_eso.jar file (where is the language that you want to install).

9. Navigate to the /i18n/ESO/ directory (where is the language that you want to install) and select the install_language.xml script file.

10. Carry out steps 4 through 7 above.




11. Repeat as required for additional languages.

4.4 Deploy SAP Sourcing SCA File to Application Server

Prerequisites

You are familiar with the Software Update Manager (SUM).

NoteThe SUM, which is a part of the Software Linguistics Toolset, replaces the Java Support Package Manager (JSPM) for the maintenance of SAP systems based on SAP NetWeaver. The section below describes the procedures for using SUM to deploy/update the SAP Sourcing SCA file to the application server as a single software component.

Note For the latest SAP notes, download links for SL tools, SCN blogs, and guides related to the SL Toolset and

SUM, see the Software Logistics Toolset documentation links at service.sap.com/sltoolset. For detailed information about troubleshooting the download, installation, and use of SUM to apply single-

component updates and patches, see section 7 of websmp104.sap-ag.de/~sapidb/011000358700000783722011E.

Preparation

Download the SUM

If you have not downloaded the SUM while installing or upgrading to NetWeaver 7.31 SP10, then you can download the latest version from the SAP Service Marketplace at service.sap.com/swdc Support Packages and Patches A-Z Index S SL Toolset SL Toolset Entry by Component Software Update Manager (SUM) .

Install the SUM

1. Log on as user ADM to the host on which the primary application server instance is running.2. Unpack the Software Update Manager package with the following command:

SAPCAR xvf \\.SAR R :\usr\sap\This command creates the directory SUM under the :\user\sap\ directory. You can also specify a directory other than :\user\sap\. In the following, refers to the directory \\SUM.

Note The SAPCAR version referenced in the PATH environment variable is identical to the one in the kernel directory. In addition, no reference to any other SAPCAR version may exist in the PATH variable. The complete path to the SUM directory must not exceed 30 characters.

28



http://service.sap.com/sltoolsethttps://websmp104.sap-ag.de/~sapidb/011000358700000783722011Ehttps://websmp104.sap-ag.de/~sapidb/011000358700000783722011Ehttp://service.sap.com/swdc

Procedure

Starting and Running the SUM

Starting the SUMOnly valid for: Windows |

To start the Software Update Manager, enter the following command: :\\STARTUP.BAT.End of: Windows |


To start the Software Update Manager, follow these steps:End of: Linux |


1. Change directories to /.2. Enter the following command: ./STARTUP.

End of: Linux |

NoteAlways start the SUM from within the directory in which it is placed.

Starting the SUM GUI

This procedure depends on the host on which you start the GUI. We recommend that you call the GUI from an Internet browser. If, for example, you have to use the SAProuter to pass a firewall, call the GUI by using the Java runtime environment. In this case, you can specify the required routing string. On the host where you want to start the GUI, at least Java 6 must be installed.

Follow these instructions to start the GUI from a browser

1. Open the following URL: , where is the name of the host where the SUM is running. This opens the update start page.

2. Java WebStart may not be available for the Windows platforms IA64 and X86_64. In this case, a dialog box may appear prompting you to run or save the file sdtdsu.jnlp. Choose Run.

3. If the dialog box does not appear, choose the link GUI for the Software Update Manager on the update start page.

If this does not start the SUM GUI, refer to the documentation and the evaluation form, available on the update start page.

Starting the SUM GUI on Remote Windows Hosts

Follow these instructions if you want to enable remote hosts to run the SUM GUI:

1. Create the following directory structure on each remote host. You can copy this structure from the parent host:

\sdt\lib \sdt\exe\DSUGui.bat

2. Start the SUM GUI in a command prompt with the command DSUGui.bat.

Deploying SAP Sourcing

Follow the directions in the SUM GUI to deploy the SAP Sourcing SCA file on the application server:

In the Specify Credentials step, enter the password for the adm OS user. In the Select Target step, enter the location of the manually prepared download directory where the SAP

Sourcing SCAs are located. You can put all files and software packages with which you want to update your




http:%3Chost%20name%3E:4239

system in a download directory or you can just point the SUM to the \fsapp directory from which it can pick up the SCA files.

In the Confirm Target step, enter the keyword for the upgrade. Enter the keyword that is specified in the current central Software Update Manager Note 1707161. Choose Next to confirm the component updates and patches you want to apply to the system.

The Execute Process step automatically triggers the next stage of the upgrade process. This step is broken down into the following:

Initialization Configuration, where you enter all the information required for the upgrade procedure, such as system

users and passwords and information about the support packages you want to include.

NoteIf you pointed the SUM to the fsapp directory, the Optimizer SCA will also be picked up for deployment. If you have a separate system for the Optimizer, skip the Optimizer SCA and choose to deploy only the SAP Sourcing SCA.

Checks Preprocessing Execution Postprocessing Finalization Summary

Once you have finished this process step by step, you have completed the deployment.

Starting the SAP Sourcing Application

Start the SAP Sourcing application from the SAP NetWeaver Administrator. For more information, see Starting and Stopping SAP Sourcing [page 30]. To verify that the application is running, point a browser at ://fssystem/portal/login.

4.5 Starting and Stopping SAP Sourcing

Procedure

If you need to start or stop SAP Sourcing during deployment, you can do so as follows:

1. Launch the SAP NetWeaver Administrator.2. On the Operation tab, choose Systems Start & Stop Java Applications .3. Use the filter to find E-Sourcing.4. Select the application that you want to start or stop, and choose Start or Stop.

4.6 Install Optimizer

The optimizer is an optional tool that performs complex calculations and comparisons to automatically determine an award scenario based on your specified priorities, goals (such as achieving the lowest cost or the highest quality), and rules. The optimizer generates the best possible solutions to meet your goal based on the specified rules.

30



http://%3Chost%3E:%3Cport%3E/%3Ccontext%3E/fssystem/portal/loginhttp://%3Chost%3E:%3Cport%3E/%3Ccontext%3E/fssystem/portal/login

You must install the optimizer on a machine that is physically separate from the SAP Sourcing server. Technically, the system will still function if you run the optimizer on the same machine in a different Java Virtual Machine (JVM), but this is strongly discouraged.

You must run the optimizer server with the same version and vendor for JVM software as the SAP Sourcing server. Otherwise, the optimizer will not function.

NoteYou can install the optimizer independent of the SAP Sourcing installation. However, you can complete the optimizer installation only after a working SAP Sourcing application has been installed and a context has been created. Typically, the optimizer is installed just after the SAP Sourcing installation.

To install the optimizer, you run the same setup executable and configure executable as for the SAP Sourcing server. You should define the same application context and maintain the same database connection information. The optimizer does not need its own database. The SAP Sourcing database connection information is a mandatory input for the installers configuration utility when it is run for the first time.

NoteIf SAP Sourcing is being implemented on the NetWeaver application server and the optimizer will be deployed remotely (on a different machine), you must set the Optimization.jndi.force_remote system property in SAP Sourcing, as follows:

1. Log on to SAP Sourcing using the system account (/fssystem/portal/login) or the enterprise account for a single-context installation.

2. Go to the System Properties page and search for optimization properties.3. Set Optimization.jndi.force_remote to TRUE.

NoteIf you want to install the optimizer on a different operating system than the one on which SAP Sourcing is installed (for example, Windows instead of UNIX), you must download the appropriate setup executable for that operating system.

The installer creates both the esoserver.sca and esooptimizer.sca files.To deploy the optimizer, you upload the esooptimizer.sca file to the SAP NetWeaver application server. For more information, see Deploy Optimizer SCA File to Optimizer Application Server [page 32].

Prerequisites

The Java Development Kit (JDK), SAP NetWeaver, and SAP Sourcing must be installed on the server.

Recommended Server Topology

For the recommended server topology, see Supported Platforms and Configurations in the product availability matrix on SAP Service Marketplace at service.sap.com/pam.




http://service.sap.com/pam

4.6.1 Install Optimizer License

Procedure

Unlike the rest of the SAP Sourcing application, the optimizer will not function without a valid license key. You can obtain a license key from SAP Customer Support. Before requesting the license key, obtain the installation ID of the SAP Sourcing application.

For more information, see Install License Key in the configuration guide for SAP Sourcing on SAP Service Marketplace at service.sap.com/eso.

4.6.2 Deploy Optimizer SCA File to Optimizer Application Server

Prerequisites

You are familiar with the Software Update Manager (SUM).

NoteThe SUM, which is a part of the Software Linguistics Toolset, replaces the Java Support Package Manager (JSPM) for the maintenance of SAP systems based on SAP NetWeaver. The section below describes the procedures for using SUM to deploy/update the SAP Optimizer SCA file to the optimizer application server as a single software component.

Note For the latest SAP notes, download links for SL tools, SCN blogs, and guides related to the SL Toolset and

SUM, see the Software Logistics Toolset documentation links at service.sap.com/sltoolset. For detailed information about troubleshooting the download, installation, and use of SUM to apply single-

component updates and patches, see section 7 of websmp104.sap-ag.de/~sapidb/011000358700000783722011E.

Preparation

Download the SUM

If you have not downloaded the SUM while installing or upgrading to NetWeaver 7.31 SP10, then you can download the latest version from the SAP Service Marketplace at service.sap.com/swdc Support Packages and Patches A-Z Index S SL Toolset SL Toolset Entry by Component Software Update Manager (SUM) .

Install the SUM

1. Log on as user ADM to the host on which the primary application server instance is running.2. Unpack the Software Update Manager package with the following command:

SAPCAR xvf \\.SAR R :\usr\sap\

32



http://service.sap.com/esohttp://service.sap.com/sltoolsethttps://websmp104.sap-ag.de/~sapidb/011000358700000783722011Ehttps://websmp104.sap-ag.de/~sapidb/011000358700000783722011Ehttp://service.sap.com/swdc

This command creates the directory SUM under the :\user\sap\ directory. You can also specify a directory other than :\user\sap\. In the following, refers to the directory \\SUM.

Note The SAPCAR version referenced in the PATH environment variable is identical to the one in the kernel directory. In addition, no reference to any other SAPCAR version may exist in the PATH variable. The complete path to the SUM directory must not exceed 30 characters.

Procedure

Starting and Running the SUM

Starting the SUM

To start the Software Update Manager, enter the following command: :\\STARTUP.BAT.

NoteAlways start the SUM from within the directory in which it is placed.

Starting the SUM GUI

This procedure depends on the host on which you start the GUI. We recommend that you call the GUI from an Internet browser. If, for example, you have to use the SAProuter to pass a firewall, call the GUI by using the Java runtime environment. In this case, you can specify the required routing string. On the host where you want to start the GUI, at least Java 6 must be installed.

Follow these instructions to start the GUI from a browser

1. Open the following URL: , where is the name of the host where the SUM is running. This opens the update start page.

2. Java WebStart may not be available for the Windows platforms IA64 and X86_64. In this case, a dialog box may appear prompting you to run or save the file sdtdsu.jnlp. Choose Run.

3. If the dialog box does not appear, choose the link GUI for the Software Update Manager on the update start page.

If this does not start the SUM GUI, refer to the documentation and the evaluation form, available on the update start page.

Starting the SUM GUI on Remote Windows Hosts

Follow these instructions if you want to enable remote hosts to run the SUM GUI:

1. Create the following directory structure on each remote host. You can copy this structure from the parent host:

\sdt\lib \sdt\exe\DSUGui.bat

2. Start the SUM GUI in a command prompt with the command DSUGui.bat.

Deploying SAP Optimizer

Follow the directions in the SUM GUI to deploy the SAP Optimizer SCA file on the application server:

In the Specify Credentials step, enter the password for the adm OS user. In the Select Target step, enter the location of the manually prepared download directory where the SAP

Sourcing SCAs are located. You can put all files and software packages with which you want to update your




http:%3Chost%20name%3E:4239

system in a download directory or you can just point the SUM to the \fsapp directory from which it can pick up the SCA files.

In the Confirm Target step, enter the keyword for the upgrade. Enter the keyword that is specified in the current central Software Update Manager Note 1707161. Choose Next to confirm the component updates and patches you want to apply to the system.

The Execute Process step automatically triggers the next stage of the upgrade process. This step is broken down into the following:

Initialization Configuration, where you enter all the information required for the upgrade procedure, such as system

users and passwords and information about the support packages you want to include.

NoteIf you pointed the SUM to the fsapp directory, the SAP Sourcing SCA will also be picked up for deployment. Since you have a separate system for the Optimizer, skip the SAP Sourcing SCA and choose to deploy only the SAP Optimizer SCA.

Checks Preprocessing Execution Postprocessing Finalization Summary

Once you have finished this process step by step, you have completed the deployment.

Starting the SAP Optimizer Application

The optimizer is deployed on SAP Netweaver. It will be started automatically. For more information, see Starting and Stopping SAP Sourcing [page 30]. To verify that the application is running, point a browser at ://fssystem/portal/login.

4.6.3 Verify Installation

Prerequisites

The system user has maintained the following system property. For more information, see Define J2EE System Properties [page 24].

optimization.jndi.java.naming.provider.url

Procedure

To check that the optimizer is installed correctly:

1. In SAP Sourcing, choose Setup.2. On the System Administration tab, find the System Management section and choose System Information.3. On the Optimizer tab:

Check that the state of all queues is active. Check that all Java Virtual Machine (JVM) information is read back from the optimizer.

34



http://%3Chost%3E:%3Cport%3E/%3Ccontext%3E/fssystem/portal/loginhttp://%3Chost%3E:%3Cport%3E/%3Ccontext%3E/fssystem/portal/login

Check that the JVM version is the same as that shown on the Service Registration tab. In the Version Information table, check that the following fields all have the same value, for example 7.0:

Local Request Payload Version Remote Request Payload Version Local Response Payload Version Remote Response Payload Version

4. Check that no errors are returned in the SAP Sourcing and optimizer log files.

4.7 Install Contract Generation

Contract generation is an optional service that enables the user to generate a contract from an RFx, auction, or master agreement. Each contract is based on a contract document template, which consists of clauses and sections of standard legal terms. Clauses can contain variables that are automatically replaced with terms and other detailed information that is taken directly from a sourcing event such as an RFx or auction, or from a specific agreement.

NoteWhen you set up the MS Word Contract Template that will be used to format contracts, be sure to specify a Microsoft Word template file (that is, a file with the .DOTX extension). This must not be a Microsoft Word document file (that is, do not choose a file with the .DOCX extension).

The contract document is a Microsoft Word file that is attached to the sourcing event from which it is created. After the contract is generated, you can edit it in Microsoft Word and use it for negotiation with the supplier.

More Information


4.7.1 Enable JAVA-Based SAP Sourcing DOCX Generation Service

The SAP Sourcing DOCX Generation Service generates and works with documents only in .docx and .dotx formats. For example, you cannot upload .doc or .dot files to the SAP Sourcing DOCX Generation Service, except for legacy control documents.

To enable the SAP Sourcing DOCX Generation Service, follow these steps:

1. Log on as a member of the administrator group.2. Select Setup System Properties Contractgen.wordservice.enabled .3. Select Edit. In the Value field, type FALSE.4. Save your changes.




5 Additional Information

5.1 Uninstalling and Reinstalling SAP Sourcing

Procedure

Uninstalling SAP Sourcing

Launch the SAP Sourcing uninstaller in the _uninst directory and uninstall the SAP Sourcing software. The SAP Sourcing uninstaller utility does not remove data from the database. If required, you must do this manually.

NoteBefore manually removing the directory containing the earlier installation, back up the directory.

If the SAP Sourcing uninstaller utility is not available, for example on a UNIX-based system, manually remove the directory containing the earlier installation.

Reinstalling SAP Sourcing

1. Launch the setup installer for your operating system.

After the installation is completed successfully, the configuration tool is launched automatically. If the configuration tool is not launched automatically, start it manually. For more information, see Execute Configure Utility Manually [page 17].

2. Using the configuration tool, configure the software for deployment.

For more information, see Configure Software for Deployment [page 17].3. Carry out the post-installation steps.

For more information, see Post-Installation [page 23].4. Deploy and perform additional configurations.

For more information, see the configuration guide for SAP Sourcing on SAP Service Marketplace at service.sap.com/eso.

5.2 Undeploying SCA Files

There is generally no need to undeploy SCA files because the Software Update Manager (SUM) supports the update of SCA files without undeployment. The following procedure is only for situations where you need to remove SCA files from SAP NetWeaver for some other reason.

36


SAP Sourcing 10.0Additional Information

http://service.sap.com/eso

Procedure

1. Open a command prompt and launch telnet using the following command, where NWhostname is the name of the server running SAP NetWeaver, and JNr is the instance number, for example 00 or 01. You can find the instance number from your SAP NetWeaver installation folder, for example, C:\usr\sap\CE1\J00.

Telnet 508

ExampleTelnet localhost 50008

2. Log on using the SAP NetWeaver Administrator and password.3. To undeploy the SAP Sourcing SCA file, enter the following command:

UNDEPLOY name=E-Sourcing-Server vendor=sap.com on_undeploy_error=stopTo undeploy the optimizer SCA file, enter the following command:

UNDEPLOY name=E-Sourcing-Optimizer vendor=sap.com on_undeploy_error=stop

5.3 Troubleshooting

Procedure

The following tables contain tips for troubleshooting SAP Sourcing and contract generation.

Table 10: Troubleshooting SAP Sourcing

Issue Solution

You have trouble running dbimport and get the error Unable to connect to the database.

Check the install logs for the following error: error:java.lang.RuntimeException: Error checking JDBC Driver name.This error can be caused by using an unsupported driver. See SAP Note 2444116 for details about what is needed.

You are unable to connect to the database. Check that you have correctly specified the user ID, password, driver class, and database URL.

Exampleuser=esdev

password=orcl

driverClass=oracle.jdbc.driver.OracleDriver

url=jdbc:oracle:thin:@10.48.82.95:1521:ORCL

You are unable to connect to the database. Verify that your JDBC driver is version 11.2 or later. If you are using an earlier version of the JDBC driver, see SAP Note 1642326.

The configure utility does not start automatically. See Execute Configure Utility Manually [page 17].




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

Issue Solution

You get an error message that the configure utility is not in a valid SAP Sourcing home directory.

Check that the JAVA_HOME environment variable is set to the SAP NetWeaver JDK directory. The following examples use export and setenv, depending on the shell.Only valid for: UNIX |

Exampleexport JAVA_HOME=/usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6

setenv JAVA_HOME /usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6

End of: UNIX |

Check that the bin directory of the SAP NetWeaver JDK directory is added at the beginning of the PATH environment variable. The following examples use export and setenv, depending on the shell.Only valid for: UNIX |

Exampleexport PATH=/usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6/bin:$PATH

setenv PATH /usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6/bin:$PATH

End of: UNIX |


Create the directory for the SAP Sourcing installation with the root user, and use the chown command to change the owner of this directory to the SAP NetWeaver Administrator user (adm) before running the SAP Sourcing setup.bin (for example, setupSolaris.bin) as the SAP NetWeaver Administrator user.End of: UNIX |

The Oracle JAR file is not specified. Specify the JDBC driver for Oracle. For more information, see Copy JDBC Driver [page 14].

install_root.xml stalls when it is run. 1. Stop the process to close the halted DB Importer.2. Rerun the dbimport.bat (Windows) or

dbimport.sh (UNIX) file, select the install_root.xml, and run the scripts.

You are unable to log on after running install_root.xml.

Check the log files at:

/logs/install.logs

38



Issue Solution

The keystore could not be initialized when you start the system or when you start the DB Importer.

A JCE exception appears in the logs.

In this situation, the following issues arise:

Directory configuration passwords do not function properly.

License keys are deactivated. Historical proxy bids in auctions are lost and cannot be

recovered.

Reinstall the SAP Sourcing keystore. For more information, see SAP Note 1304005.

The make_SDA tool was not found. Check whether make_sda.bat (Windows) or make_SDA.sh (UNIX) is present in the folder specified in the error message. If the file is not present, check that the application server for SAP NetWeaver is installed correctly.

The dctool was not found. Check whether dctool.bat (Windows) or dctool.sh (UNIX) is present in the folder specified in the error message. If the file is not present, ask your SAP NetWeaver system administrator to verify that SAP NetWeaver is installed correctly.

The SCA files were not created. First try the solutions to the following issues:

The make_SDA tool was not found. The dctool was not found.

If the problem persists, check that the environment variables JAVA_HOME and NWDITOOLLIB are set correctly. For more information (including an example of a successfully running dctool), see Complete Checklist [page 8].Check that the environment variable APPSERVER is set to NETWEAVER. For more information, see Install SAP Sourcing Binary Files [page 16].





Issue Solution

The WAR, EAR, and SCA file update failed. Check whether the EAR file is created in the /fsapp folder. If yes, check whether the settings for the dctool.bat (Windows) or dctool.sh (UNIX) file have been made. For more information, see Complete Checklist [page 8].Only valid for: Solaris |

1. Using the SAP NetWeaver Administrator user (adm), switch to the Bash shell by entering bash.

2. Set the environment variables for PATH and JAVA_HOME.

Exampleexport PATH=/usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6/bin:$PATH

export JAVA_HOME=/usr/sap//SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6

3. Increase the stack size for the duration of the installation by entering ulimit -s 20480.

4. Modify the content of dctool.sh. The file content should appear as follows (with adjusted paths for NWDITOOLLIB and JAVA_HOME):NWDITOOLLIB=/usr/sap/QO1/SYS/global/di_cmd_tools/lib

JAVA_HOME=/usr/sap/QO1/SYS/exe/jvm/sun_64/sapjvm_6.1.025/sapjvm_6

APPL=com.sap.tc.di.cmdline.ApplicationLauncher

startup=$NWDITOOLLIB/tc~di~cl~application_launcher_api.jar

PARAM_JDK=-Ddctool.JDK_PATH="$JAVA_HOME"

"$JAVA_HOME/bin/java" -cp "$startup" -Xmx256m -Xss20m

-Dappl.jars="$NWDITOOLLIB" -Dappl.classname=com.sap.tc.cetoo

l.DcConsoleApplication -Ddctool.JDK_PROPERTY_NAME="default" $PARAM_JDK

$APPL $*End of: Solaris |

40



Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your .

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

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

SAP Sourcing 10.0Typographic Conventions



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

www.sap.com

Copyright 2014 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. National product specifications may vary.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.SAP 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.Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Please see www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

http://www.sap.comhttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademarkhttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademarkhttp://www.sap.com/corporate-en/legal/copyright/index.epx

SAP Sourcing 10.0Table of Contents1 Introduction1.1 About This Document1.2 Before You Start1.2.1 Naming Conventions

2 Preparation2.1 Complete Checklist2.2 Add Java Parameter2.3 Copy SAP Sourcing Media2.4 Prepare Database Server2.4.1 Identify Server2.4.2 Create Tablespaces2.4.3 Install Oracle Text Search2.4.4 Create Oracle Service Account2.4.5 Connect Schema2.4.6 Install Obfuscation Toolkit2.4.7 Copy JDBC Driver2.4.8 Verify Settings for SAP Sourcing

3 Installation3.1 Install SAP Sourcing Binary Files3.2 Configure Software for Deployment3.2.1 Execute Configure Utility Manually3.2.2 Specify Location of SAP NetWeaver Home Directory3.2.3 Update Java Home Directory3.2.4 Select tools.jar File3.2.5 Select Symantec.jar File3.2.6 Include Custom JAR Files3.2.7 Update WAR, EAR, and SCA Files3.2.8 Change Session Timeout3.2.9 Define Application Context3.2.10 Maintain Database Connection Information

4 Post-Installation4.1 Install Baseline Database4.2 Define J2EE System Properties4.3 Install Language Packs4.4 Deploy SAP Sourcing SCA File to Application Server4.5 Starting and Stopping SAP Sourcing4.6 Install Optimizer4.6.1 Install Optimizer License4.6.2 Deploy Optimizer SCA File to Optimizer Application Server4.6.3 Verify Installation

4.7 Install Contract Generation4.7.1 Enable JAVA-Based SAP Sourcing DOCX Generation Service

5 Additional Information5.1 Uninstalling and Reinstalling SAP Sourcing5.2 Undeploying SCA Files5.3 Troubleshooting

Copyright and Trademarks

Documents

clm 10 e sorc