SAP Supplier Relationship Management 7.0 Including Enhancement Package 3 Java and ABAP

Installation GuideSAP Supplier Relationship Management 7.0 Including Enhancement Package 3 Java and ABAPFor: ABAP Java

Target Audience System Administrators Technology Consultants

PUBLICDocument version: 1.0 2013-08-13

Document History

CAUTIONBefore 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 Description1.0 2013-08-13 Final version

2/32 PUBLIC 2013-08-13

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Essential Information: Process and Documentation Overview . . . . . . . . . . . . . . 51.2 Additional Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Note About the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Update and Migration Process for SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Defining a Web Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Defining a Web Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3 Live Auction Properties: Overview and Modifications . . . . . . . . . . . . . . . . . . . 153.3.1 JCo Property Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.2 JCo Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3.3 JCo Message Server Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3.4 JCo Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.5 Other Property Settings for LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.6 Modifying Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.4 Configuring Single Sign-On for LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5 Enabling Auctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.5.1 Creating HTTP Connections to an External Server . . . . . . . . . . . . . . . . . . . . . 243.5.2 Defining a Back-End Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.5.3 Defining Number Ranges for Auctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.6 Copying Customizing Settings from the Default Client . . . . . . . . . . . . . . . . . . 253.7 Server Name and IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.8 LAC Smoke Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.8.1 Smoke Testing User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.8.2 Smoke Testing the LAC Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2013-08-13 PUBLIC 3/32

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

Only valid for: ABAP;Java |

1 Getting Started

Only valid for: ABAP;Java |This section of the guide contains important information that you need to read before starting your installation process.End of: ABAP;Java |Only valid for: ABAP;Java |

1.1 Essential Information: Process and Documentation Overview

Only valid for: ABAP;Java |You are currently reading the Installation Guide for SAP Supplier Relationship Management 7.0 Enhancement Package 3 ABAP and Java. This guide only contains information specific to SAP SRM, but you need additional information provided by the SAP SRM 7.13 Master Guide to enable you to perform your installation correctly.End of: ABAP;Java |Only valid for: ABAP;Java |

NOTESpecifically, you need to use the SAP NetWeaver server installation guides (ABAP or Java versions) in parallel to the Installation Guide for SAP Supplier Relationship Management 7.0 Enhancement Package 3 ABAP and Java: Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.40 on :

Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 7.40 on :

You have to use the SAP NetWeaver server installation guides in parallel with this application-specific guide, because the two types of guides complement each other the SAP NetWeaver server guide contains the overall process, tool, operating system- and database-specific information while this guide contains the application-specific information.You find the SAP NetWeaver server installation guides on the SAP Service Marketplace at the same location as the SAP SRM 7.13 Master Guide, see path below.

End of: ABAP;Java |The SAP SRM 7.13 Master Guide contains a section Main Implementation Processes and Related Documentation with the following subsections with vital information:

1 Getting Started1.1 Essential Information: Process and Documentation Overview

2013-08-13 PUBLIC 5/32

Planning for Installation, Update, and Upgrade ProcessesContains a list of topics (including documentation references) you need to consider when you are planning your implementation project.

Implementation of the Installation ProcessProvides a step-by-step overview of the installation process (new installation of an SAP system including an enhancement package), with reference to the required tools and associated documentation.

Implementation of the Update ProcessProvides a step-by-step overview of the update process (installation of an enhancement package on an existing SAP system), with reference to the required tools and associated documentation.

Implementation of the Upgrade ProcessProvides a step-by-step overview of the upgrade process (upgrade to an SAP system including an enhancement package), with reference to the required tools and associated documentation.

NOTEMake sure that you collect all the information provided in this overview before starting your installation, upgrade or update project.

Make sure that you have downloaded the latest version of the SAP SRM 7.13 Master Guide from the SAP Service Marketplace: http://service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 .End of: ABAP;Java |Only valid for: ABAP;Java |

1.2 Additional Installation InformationWhen preparing your installation, you need to consider the following information specific to SAP Supplier Relationship Management: Media list

The media list contains the list of relevant installation media that you need to have available when you start the installation.You can find the media list at: http://service.sap.com/instguides Installation & Upgrade Guides

SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 . SAP SRM Server ABAP installation

You select the option SAP Application Server ABAP for SAP SRM 7.13 when you are asked to choose the installation option. All relevant ABAP components are then installed by the installation tool.

NOTEYou need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.40 on : in parallel with this guide.

1 Getting Started1.2 Additional Installation Information

6/32 PUBLIC 2013-08-13

You can find the SAP NetWeaver server installation guide at: http://service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 .

SAP SRM Server Java installationNOTEYou need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 7.40 on : in parallel with this guide.You can find the SAP NetWeaver server installation guide at: http://service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 .

SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP NetWeaver 7.40.

If you deploy SAP SRM on the SAP NW Portal, you need to install the SRM Business Packages together with the SAP NetWeaver Portal components. You select the relevant components in the installation tool.

If you deploy the Java version of Live Auction Cockpit, you need to select the relevant components for installation.

NOTENote that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM 7.01.For more information, see http://help.sap.com/srm713 Application Help SAP Library SAP Supplier Relationship Management Business Functions and Customizing Switches SRM, Strategic Sourcing Innovations .

The following table shows the selection you need to do in the installation tool, depending on your requirements:

SRM Software Units Description Dependent OnSRMLAC SRM Live Auction Cockpit AS JavaSRM JAVA SRM Java AS Java, EP CoreSRM Supp SRM Supplier AS Java, EP CoreBP-SRM SRM Portal Content AS Java, EP Core, SRM JAVA, BP-SRM-COMBP-SRM-COM SRM Business Packages AS Java, EP CoreBP-Supp SRM Portal Content Supplier AS Java, EP Core, SRM Supp

Installation of SAP SRM Business PackagesFor information on installing the Business Packages for SAP SRM, see SAP Notes 1232945 and 1649846.

1 Getting Started1.2 Additional Installation Information

2013-08-13 PUBLIC 7/32

Additional information is available in the SAP Help Portal: http://help.sap.com/srm SAP Supplier Relationship Management SAP Enhancement Package 3 for SAP SRM 7.0 Application Help SAP Library SAP Supplier Relationship Management Business Packages .

End of: ABAP;Java |Only valid for: ABAP;Java |

1.3 Important SAP NotesOnly valid for: ABAP;Java |Note Number Desciption1582094 EHP2 for SAP SRM 7.0 SP Stacks - Release & Information Note1642797 Java Installation for Business Suite 7i20111232945 BP for SRM 7.0: Installing the Business Packages1649846 BP for SRM 7.0 EhP2: Installation Information

End of: ABAP;Java |End of: ABAP;Java |Only valid for: ABAP;Java |

1.4 GlossaryThis section explains the most common terms and concepts used in the installation, update and upgrade guides.Term / Concept Definition / ExplanationUpdate Installation of an enhancement package on an existing SAP system.

Update may also refer to other software updates, such as support package deployments.In a profile (see glossary entry below), update is referred to as Enhancement Package Installation.

Upgrade Upgrade to an SAP system including an enhancement package.Installation New installation of an SAP system including an enhancement packageProfiling The guide contains some sections or paragraphs that are profiled, that is,

they are used in various contexts (upgrade, update, installation, ABAP and Java). For example, a section may be used for both upgrade and update topics.A profile is indicated by brackets above and below the profiled section and the profiling context it is valid for.

OS Abbreviation for operating system.DB Abbreviation for database.

End of: ABAP;Java |End of: ABAP;Java |

1 Getting Started1.3 Important SAP Notes

8/32 PUBLIC 2013-08-13


2 Process

This section of the guide contains information about process-related application-specific tasks if there are any (in some cases, there are no application-specific tasks).Only valid for: ABAP;Java |

2.1 Note About the ProcessOnly valid for: ABAP;Java |

NOTEThe installation processes are described in detail in the SAP NetWeaver server installation guides (ABAP or Java): Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.40 on :

Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 7.40 on :

You have to use the SAP NetWeaver server guide in parallel with this application-specific guide, because the two types of guide complement each other the SAP NetWeaver server guide contains the overall process, tool, operating system- and database-specific information while this guide contains the application-specific information.SAP Supplier Relationship Management 7.0 Enhancement Package 3 actually requires no application-specific steps in the Process section there are only generic steps documented in the SAP NetWeaver server guides.You find the SAP NetWeaver server installation guides on the SAP Service Marketplace at http://service.sap.com/instguides Installation & Upgrade Guides SAP NetWeaver SAP

NetWeaver 7.4 .


2 Process2.1 Note About the Process

2013-08-13 PUBLIC 9/32


2.2 Update and Migration Process for SAP HANAThis section provides an overview of the update and upgrade process steps required to enable SAP enhancement package 3 for SAP SRM 7.0 to run on SAP HANA. It also provides references to the documentation required for the process steps.The following table contains definitions of the most important terms used in this section:Term DefinitionUpdate Installation of an enhancement package on an existing SAP system.Upgrade Upgrade to an SAP system including an enhancement package.

The update process consists of the steps listed below, some of which may be optional, depending on your start release.

NOTEBefore performing the steps described below, consider making a homogeneous system copy to preserve your current status, so that you have a reference or fallback system in place. You can do the system copy before any of the steps below, depending on your requirements and schedule.For more information about system copy of systems based on SAP NetWeaver 7.3 (or higher), see the documentation at http://service.sap.com/sltoolset Software Logistics Toolset 1.0Software Provisioning Manager 1.0 .For more information about system copy of systems based on SAP NetWeaver releases lower than 7.3, see the SAP NetWeaver installation guides at http://service.sap.com/instguides

Installation & Upgrade Guides SAP NetWeaver

1. Installation of Application Function Libraries (AFLs)Install the AFLs as described in the SAP HANA Installation Guide with Unified Installer at http://help.sap.com/hana SAP HANA SAP HANA Appliance SAP HANA Installation Guide with Unified Installer

2. Dual-stack splitAs of SAP enhancement package 2 for SAP SRM 7.0 you cannot deploy a dual-stack system (with both ABAP and Java components running the same system). If your system is currently implemented as a dual-stack system, you have to perform a split.For information on how to do a dual-stack split, see: 1686144, 1655335 and Tool Guides at http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Dual-Stack Split

NOTEWhen applying Support Package 1 to SAP enhancement package 3 for SAP SRM 7.0, you have to use the Software Update Manager.

2 Process2.2 Update and Migration Process for SAP HANA

10/32 PUBLIC 2013-08-13

3. Database migrationNOTEBefore performing these substeps, check the release information note (RIN for SAP SRM 7.00 EHP3 SP1) 1818517.

This step consists of the following substeps:1. Install SAP HANA

The SAP HANA appliance software can only be installed by certified hardware partners on validated hardware running a specific operating system.For more information, see 1514967 and the system operations information at http://help.sap.com/hana SAP HANA Appliance System Administration and Maintenance InformationSAP HANA Technical Operations Manual

2. To migrate your source database to the SAP HANA database, you perform a heterogeneous system copy. How to perform the system copy is described in the guide referenced in the note below.NOTEDatabase Migration for SAP HANA DatabaseAn existing SAP system is migrated to the SAP HANA database automatically using the Database Migration Option (DMO) of the Software Update Manager (SUM), which updates and migrates the database in one step. For more information, see SAP Notes 1875197 and 1813548, and SAP Service Marketplace at http://service.sap.com//sltoolset. You need to use at least SPS09 of the Software Update Manager 1.0.


2 Process2.2 Update and Migration Process for SAP HANA

2013-08-13 PUBLIC 11/32

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


3 Follow-Up Activities

Only valid for: ABAP;Java |This section of the guide describes application-specific steps that have to be done after the installation process is complete.End of: ABAP;Java |

3.1 Defining a Web AliasAfter an upgrade from SRM on NW 70x to SRM on NW73x or higher the WEB alias configuration must be adapted manually again.Refer to section 3.1, Defining Web Alias, of the Installation guide of Supplier Relationship Management 7.0 Including enhancement Package 3 ABAP and JAVAOnly valid for: Java |

3.2 Defining a Web AliasTo enable easy customization of the Live Auction Cockpit applet, the resource files are packaged separately from the Web application itself. In order for the applet to retrieve its resources, the Web server must make the resource files accessible through HTTP. You can enable this by creating a Web alias for the directory that contains the resources. Without this alias, the applet cannot load properly.

PrerequisitesThe J2EE Engine is running.

ProcedureSAP NetWeaver Application Server Java 7.40Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 7.40. The procedure for SAP NetWeaver 7.40 is described below.1. Open the J2EE Engine Administration tool.

EXAMPLEOn Windows, browse to:\usr\sap\\\j2ee\admin\go.batOn UNIX, browse to:

3 Follow-Up Activities3.1 Defining a Web Alias

2013-08-13 PUBLIC 13/32

\usr\sap\\\j2ee\admin\go.sh Port: 504

2. Enter the J2EE Engine administrator password and choose Connect.3. In the navigation pane, choose Server Services HTTP Provider .4. Select the Runtime tab.5. Select the Aliases tab.6. Enter Alias: srmla/lib/resources.7. Enter Path.

EXAMPLE:\usr\sap\\SYS\global\srmla\resources

8. Choose Add.9. Choose Save Properties.10. Close the J2EE Engine Administration tool.

NOTEIf you are using load balancing (that is, running Live Auction Cockpit on more than one Java server) you must carry out the following steps:1. On the central instance, share the srmla folder (:\usr\sap\>\SYS

\global\srmla) for the dialog server user.2. Maintain the alias for the dialog instance so that the path points to the shared folder on the

central instance.

SAP NetWeaver Application Server Java 7.40Use the following procedure for SAP NetWeaver 7.40:1. Go to the SAP NetWeaver Administrator using the following URL: http://:/nwa.

is the host on which the SAP NetWeaver Application Server Java 7.30 is installed. is the HTTP port of the Internet Communication Manager (ICM). It has the following

format: 500.2. Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases .3. Choose Add Alias.4. In the Name column, enter srmla/lib/resources.5. Enter the path.

EXAMPLE:\usr\sap\\SYS\global\srmla\resources

6. Save your changes.End of: Java |

3 Follow-Up Activities3.2 Defining a Web Alias

14/32 PUBLIC 2013-08-13

Only valid for: Java |

3.3 Live Auction Properties: Overview and ModificationsThe following sections provide information that enables you to customize the Live Auction properties.Only valid for: Java |

3.3.1 JCo Property SettingsSAP Java Connector (JCo) properties are listed in the following table, with default values provided where required. You must optimize default values marked with an asterisk (*) to suit your system requirements.Property Name Description Default Valuejco.client.lang Creates a JCo pool with the specified value for the

SAP logon language.* English, EN German, DE Japanese, JA

jco.client.client SAP client -jco.client.user Logon user

NOTEYou have to define this user in the SAP system as follows: User type: communication or system user Roles assigned: Purchaser and Bidder

-

jco.client.passwd Logon password -jco.client.mshost SAP message server -jco.client.group Group of SAP application servers -jco.client.r3name SAP ERP name -jco.client.ashost SAP application server -jco.client.sysnr SAP system number -jco.poolmgr.connectiontimeout The connection is considered to have timed out

when there has been no activity on it for the specified time interval.

600,000 ms (10 minutes)

jco.poolmgr.maxwaittime The maximum length of time, in milliseconds, for the system to wait for a connection request when the pool is exhausted.

30,000 ms (30 seconds)

jco.poolmgr.timeoutcheckinterval The length of time, in milliseconds, after which all connections are periodically checked for time-outs.

60,000 ms (1 minute)

jco.pool.maxconn The absolute maximum number of connections that can be simultaneously opened for a given pool.

15*

3 Follow-Up Activities3.3 Live Auction Properties: Overview and Modifications

2013-08-13 PUBLIC 15/32

Property Name Description Default Valuejco.pool.maxpoolsize The maximum number of connections that can be

kept open and managed in the pool.10*

jco.performance.monitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file. 0 = disabled 1 = enabledLog file: \usr\sap\\ \j2ee\cluster\server0\ log\applications\sap.com\com. sap.srm.la\srmlaLog-[n].log

0*

jco.performance.monitor.interval The intervals, in milliseconds, at which the statistics for the execution times of ABAP function modules are written to the log file.

300,000 ms (5 minutes)

jco.pool.monitor Monitors the JCo pool and writes the statistics to the monitor log file. 0 = disabled 1 = enabledLog file: \usr\sap\\ \j2ee\cluster\server0\ log\applications\sap.com\com.sap.srm.la \srmlaLog-[n].log

0

jco.pool.monitor. interval The intervals, in milliseconds, at which the statistics on the JCo pool size are written to the log file.

300,000 ms (5 minutes)

End of: Java |Only valid for: Java |

3.3.2 JCo Client SettingsSAP Java Connector (JCo) properties that control the communication between the Live Auction applet and the back-end SAP system are listed in the following table.Property Name DescriptionJco.client.client The number of the client on which the SAP Supplier Relationship Management (SAP

SRM) application is running.Jco.client.passwd NOTE

The password is not displayed. Instead, each character in the password is represented by an asterisk (*).

Jco.client.user JCo users must be assigned standard authorization objects, such as S_RFC, contained as part of the standard RFC users profile, and must have authorization to access the following function groups: BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE


16/32 PUBLIC 2013-08-13

Property Name Description RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects, see http://help.sap.com/nw74

SAP NetWeaver 7.40 Security Guide Security Guides for Connectivity and Interoperability Technologies RFC/ICF Security Guide RFC Scenarios Security Measure Overview (RFC)RFC Communication Between SAP Systems Authorizations .

NOTEFor connectivity between the UI and back-end system, the generic back-end user must be assigned the following roles: Purchaser Roles

EXAMPLE SAP_BBP_STAL_OPERAT_PUR_LIGHT for operational purchaser SAP_BBP_STAL_STRAT_PUR_LIGHT for strategic purchaser (which

should include the profile containing the authorization object BBP_PD_AUC)

A bidder roleEXAMPLESAP_BBP_STAL_BIDDER (which should include the profile containing the authorization object BBP_VEND)

In addition to these two types of roles, assign the additional authorization object, S_BTCH_ADMIN, to the RFC user profile to fully control the auction process.


3.3.3 JCo Message Server Client SettingsSAP Java Connector (JCo) properties that control group load balancing are listed in the following table.

NOTEYou need to provide either the application server settings or the group load balancing settings, not both. However, if both settings are available, Live Auction Cockpit uses the application server settings without load balancing as default.

Property Names Description jco.client.mshost jco.client.group jco.client.r3name

Settings that enable group load balancing.

jco.client.ashost jco.client.sysnr

Application server settings without load balancing.

End of: Java |


2013-08-13 PUBLIC 17/32


3.3.4 JCo Pool SettingsSAP Java Connector (JCo) properties for creating pooled connections are listed in the following table.

RECOMMENDATIONWe strongly recommend that you test your environment to determine the optimal values for the three properties listed in the table below. To assist you in this task, you can also enable the performance monitors, jco.performance.monitor and jco.pool.monitor, which write the performance data to the log file for analysis.

Property Name Descriptions Recommended Settingsjco.pool.maxconn This value refers to the absolute maximum

number of connections that Live Auction Cockpit can simultaneously open for each pool.

CAUTIONLive Auction Cockpit creates a pool for each supported SAP client. Therefore, in a multiple SAP client scenario, it is possible to have more than one pool.

This value has to be equal to or greater than the value for jco.pool.maxpoolsize.You have to set this value high enough to handle peak activity loads.

RECOMMENDATIONFor 25 concurrent bidders, we recommend setting the value to 15.

jco.pool.maxpoolsize This value refers to the maximum number of pooled connections kept for reuse.

CAUTIONThe difference between the value of jco.pool.maxconn and jco.pool.maxpoolsize is the number of connections that can be opened on the SAP system to perform a task and then disconnect. These connections are not reused and are therefore seen as expensive regarding system load.

You have to set this value high enough so that, under a typical system load, no additional connections are required.

RECOMMENDATIONFor 25 concurrent bidders, we recommend setting the value to 10.

jco.client.lang This is an optional setting.When this value is set, a JCo pool is created with its value used as the SAP logon language.The value for this property must be a comma separated list of valid 2-letter SAP external language codes.

CAUTIONEnsure that the SAP Supplier Relationship Management system has

If you expect a large group of users to log on in different languages, we strongly recommend that you specify each of those languages in the property file. This enables the use of pooled connections and avoids the unnecessary use of multiple one-time connections.As a result of defining language values in the property file, a JCo pool is created to maintain connections for each language and client number combination. Therefore, we recommend that you also


18/32 PUBLIC 2013-08-13

Property Name Descriptions Recommended Settingsa language installed for each of the corresponding language codes.On-the-fly connections, which are more resource-consuming than pooled connections, are created for users who log on with a language that is not listed in the property file.

adjust the value for jco.pool.maxpoolsize accordingly.


3.3.5 Other Property Settings for LACThe following table lists some additional important configuration properties for the Live Auction Cockpit (LAC).

Property Name DescriptionDefault Value

msg.client.protocol Overrides the default messaging protocol used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape.If no value is specified, the default protocol is used.

Empty (no override)

msg.client.serverHost Overrides the default host name of the messaging server used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape.If no value is specified, the default server host name is used.

Empty (no override)

msg.client.serverPort Overrides the default port number of the messaging server used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape.If no value is specified, the default server port is used.

Empty (no override)

srmla.um Authentication of the User Management Engine (UME).0 = disabled.

Empty (enabled)


3.3.6 Modifying PropertiesProcedureYou can adapt Live Auction Cockpit properties as described in the following linked sections: JCo Property Settings [page 15] JCo Client Settings [page 16] JCo Message Server Client Settings [page 17] JCo Pool Settings [page 18]


2013-08-13 PUBLIC 19/32

Other Property Settings for LAC [page 19]The SAP NetWeaver tools you can use to modify properties are described in the next sections. Use the tool that fits your requirements.

Modifying Properties with the Configuration Adapter Service (SAP NetWeaver Application Server Java 7.02)1. Stop the J2EE server.2. Launch the J2EE engine Configuration Adapter Service.

On Windows: Go to usr\sap\\\j2ee\configtool\configtool.bat and double-click go.bat.

On UNIX: Go to usr/sap///j2ee/configtool/configtool.sh and run go.sh.

3. Choose the icon with the quick info text: Switch to configuration editor mode.4. On the Display Configuration tab, choose Configurations apps sap.com com.sap.srm.la appcfg .5. Choose the icon with the quick info: Switch between view and edit mode.6. Double-click Propertysheet application.global.properties.

A separate window containing the Change Configuration page opens.7. To modify values, choose the corresponding property in the table.

A separate window containing the Change Property Entry page opens.8. Enter the new value in the Custom field and choose Apply Custom.9. Continue in the same way until you have finished your custom settings, then choose Ok on the

Change Configuration page.10. Exit the Configuration Adapter Service and start the J2EE server.

Modifying Properties with the Visual Administrator (SAP NetWeaver Application Server Java 7.02)1. Verify that the J2EE server is running.2. Launch the J2EE engine Visual Administrator.

On Windows: Go to usr\sap\\\j2ee\admin and double-click go.bat.

On UNIX: Go to usr/sap///j2ee/admin and run go.sh.3. Navigate to the Configuration Adapter by choosing Server Services Configuration

Adapter .4. On the Display Configuration tab, choose Configurations apps sap.com com.sap.srm.la appcfg .5. Choose the icon with the quick info text Switch between view and edit mode.6. Double-click Propertysheet application.global.properties.

A separate window containing the Change Configuration page opens.7. To modify values, choose the corresponding property in the table.

A separate window containing the Change Property Entry page opens.


20/32 PUBLIC 2013-08-13

8. Enter the new value in the Custom field and choose Apply Custom.9. Continue in the same way until you have finished your custom settings, then choose Ok on the

Change Configuration page.10. Exit the Visual Administrator and restart the J2EE server.

Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 7.30 and higher version)1. Go to the SAP NetWeaver Administrator using the following URL: http://:/nwa.

is the host on which the SAP NetWeaver Application Server Java 7.40 is installed. is the HTTP port of the Internet Communication Manager (ICM). It has the following

format: 500.2. Choose Operations Systems Start & Stop Java Applications .3. Search for and select com.sap.srm.la.4. Choose More Actions.5. Chose View Application Properties.6. Under Extended Details select the property to be changed.7. Choose Modify, enter the customized value, and then choose Set.8. Save your changes and restart the application.End of: Java |End of: Java |Only valid for: Java |

3.4 Configuring Single Sign-On for LACThis section explains how to set up Single Sign-On (SSO) for the Live Auction Cockpit (LAC). You need to make settings in both the SAP Supplier Relationship (SAP SRM) system and in the SAP J2EE Engine (SAP NetWeaver 7.20) or in the SAP NetWeaver Administrator (SAP NetWeaver 7.30 or higher version).

PrerequisitesYou have user rights for the following SAP SRM transactions: RZ10 (Edit Profiles) STRUST (Trust Manager) Your SAP NW Application Server Java (AS Java) is running. SAP NW 7.02: You have administrator rights on the SAP J2EE Engine. SAP NW 7.30 or higher version:: You have administrator rights on the SAP NetWeaver

Administrator.Go to the SAP NetWeaver Administrator using the following URL: http://:/nwa. is the host on which the SAP NetWeaver Application Server Java 7.40 is installed.

3 Follow-Up Activities3.4 Configuring Single Sign-On for LAC

2013-08-13 PUBLIC 21/32

is the HTTP port of the Internet Communication Manager (ICM). It has the following format: 500. For example, if the Java instance number is 60, the HTTP port is 56000.

Procedure1. Create the SSO ticket in Profile Maintenance in your SAP SRM system.

1. Start transaction RZ10.2. Choose the Default profile with the latest version number and select Extended Maintenance.3. Create the following profile parameters:

login/create_sso2_ticket = 1 login/accept_sso2_ticket = 1

4. Save and Activate the profile.A new profile is automatically generated.

5. Restart the application server.CAUTIONDo not forget or skip this step.

2. Export the back-end SSO certificate from the Trust Manager on the target host server (the SAP SRM system).1. Start transaction STRUST.2. Double-click the text box to the right of Own certif.

The certificate information is displayed.NOTEMake a note of the values displayed in the certificate information because you need to enter those values in a later step.

3. Choose the icon with the quick info text Export Certificate.4. Save the file as -.crt.

EXAMPLEFor SAP System EBS, client 300, the file name is EBS-300.crt.CAUTIONMake sure that Binary is selected under File Format.NOTEIf you export the certificate to a local system, you must copy the file from the local system to the target host server.

3. Make sure that the AS Java server is running and Import the back-end SSO certificate.1. If you are using SAP NW 7.02, proceed as follows:

1. Open the SAP J2EE Engine administration tool.2. Enter the administrator password and choose Connect.3. Choose Server Services Key Storage .


22/32 PUBLIC 2013-08-13

4. Choose TicketKeyStore in the View panel.5. Choose Load in the Entry group box.6. Choose the -.crt certificate that was exported from the SAP

SRM system earlier in step 2.The certificate is added to the list in the Entries panel.

NOTEMake a note of the distinguished names of both issuer and subject that are displayed in the certificate of the SAP SRM system. You need them for a later step.

2. Configure the Security Provider service in the SAP J2EE Engine with the administrator tool.1. Choose Server Services Security Provider .2. Choose Ticket in the Component panel and go to the Authentication tab.3. Modify the options of EvaluateTicketLoginModule and add the properties listed in the table

below to each back-end system on which you want to configure SSO:NOTEFor each property below, {n} represents the number of the back-end system on which you want to configure SSO.

Property Example Commenttrustedsys{n}: , , trustedsys1: EBS,

300-

trustediss{n}: trustediss1: CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system.

trusteddn{n):

trusteddn1: CN=EBS The value you define here must be identical to the subject distinguished name in the certificate of the SAP SRM system.

3. If you are using SAP NW 7.30 or higher version, proceed as follows:1. Go to the SAP NW Administrator to import the R3 SSO certificate.2. Go to the Configuration tab.3. Choose Trusted Systems in the Security area.4. Choose Add Trusted Systems By Uploading Certificate Manually .5. Go to the Single Sign-On with SAP Logon Tickets tab and enter the system ID, the client, and

the certificate file name.


2013-08-13 PUBLIC 23/32

For more information about how to configure Single Sign-On, see the documentation at http://help.sap.com/nw74 SAP NetWeaver 7.4 Application Help Function-Oriented ViewSecurity User Authentication and Single Sign-On .


3.5 Enabling AuctionsThe following sections contain settings to enable auctions in your systems.Only valid for: Java |

3.5.1 Creating HTTP Connections to an External ServerYou must configure HyperText Transfer Protocol (HTTP) connections to direct your Web server to the server name and port of the Live Auction J2EE server. This creates a link on your Web server page that is used to launch the Live Auction Cockpit.

Procedure1. Configure the HTTP connection in Customizing for SAP SRM under SRM Server Technical Basic

Settings Define RFC Destinations .2. Choose HTTP Connection to External Server.3. Choose Create.4. Create an RFC destination with the key SRM_LIVE_AUCTION and connection type G.5. Enter the Live Auction Cockpit server as the Target Host, using the fully qualified host name with

the domain, and its port number as the Service No.The port number consists of the instance number that is used during installation (500). For example, if during the installation, the instance number used was 01 then the port number is 50100.)

NOTEIf you have implemented a reserve proxy as an additional security measure to hide and protect the private host name of the Live Auction J2EE server, enter the reserve proxy server host name and port number as the Target Host and Service No.

6. Test the connection to see whether SAP SRM can locate the external server.If the status bar shows ICM_HTTP_CONNECTION_FAILED, you need to check for an error with the specification of the Live Auction Cockpit application server.

End of: Java |

3 Follow-Up Activities3.5 Enabling Auctions

24/32 PUBLIC 2013-08-13


3.5.2 Defining a Back-End DestinationPrerequisitesYou have created a HTTP connection to the Live Auction Cockpit J2EE server with the key SRM_LIVE_AUCTION. This connection is listed in the Destinations list from which you select the back-end destination.For more information, see Creating HTTP Connections to an External Server [page 24].

Procedure1. In the SAP SRM client, start transaction SM31 and enter BBP_BACKEND_DEST in the Table/View field.2. Choose Maintain.3. Choose New Entries.4. Select the destination for this SAP SRM client, using the Destinations list.

NOTEAll previously created HTTP connections for the Live Auction Cockpit are listed here.

5. Select SRM_LIVE_AUCTION from the list.6. Save your data.End of: Java |Only valid for: Java |

3.5.3 Defining Number Ranges for AuctionsTo enable auctions in the Live Auction Cockpit, you must define number ranges.

Procedure1. Define number ranges for auctions in Customizing for SAP SRM: SRM Server Cross-Application

Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Auctions .2. Choose Change Intervals.3. Choose Insert Interval.4. Maintain the number ranges and save your settings.End of: Java |End of: Java |Only valid for: Java |

3.6 Copying Customizing Settings from the Default ClientSAP delivers customized properties required for the Live Auction Cockpit (LAC) in the standard SAP Supplier Relationship (SAP SRM) system. The default client is 000. If this is not your LAC client, copy

3 Follow-Up Activities3.6 Copying Customizing Settings from the Default Client

2013-08-13 PUBLIC 25/32

the entries in view BBPV_LA_PROP to your client, for example, client 200. Ensure that the entries in your client are identical to those of the default client 000.

PrerequisitesYou have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system.

Procedure1. Go to transaction SM31 on your LAC client.2. Enter BBPV_LA_PROP in the Table/View field.3. Choose Maintain.

The Auction Properties Management screen is displayed.4. Choose Utilities Adjustment .5. Enter the RFC connection that points to client 000 and choose Enter.

The comparison result screen is displayed.6. Choose Edit Select Select All .7. Choose Edit Adjust .

The Detail View: Adjust Page is displayed.8. Choose Edit Adjust Copy All Entries .9. Choose F3 to go back one screen.10. Choose F3 again.

A dialog box appears asking whether or not to copy the changes.11. Choose Yes.12. Save your settings.End of: Java |Only valid for: Java |

3.7 Server Name and IP AddressYou must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC) server.

IntegrationMake sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the SAP Bidding Engine server.

EXAMPLEThe IP address and LAC server name looks similar to this example: 10.48.82.200:la_server.your.corp.

You can find and check the hosts file at c:\WINNT\System32\drivers\.

3 Follow-Up Activities3.7 Server Name and IP Address

26/32 PUBLIC 2013-08-13

CAUTIONConfirm that the system times of both the LAC server and the SAP Bidding Engine server are synchronized, to ensure that time-dependent functions run accurately and time-dependent data is processed with the correct time stamp.You can use, for example, the Simple Network Time Protocol (SNTP) to ensure that the internal clock in both servers does not become asynchronous again after you have done the initial synchronization.


3.8 LAC Smoke TestsThe following sections contain information about smoke tests available for Live Auction Cockpit (LAC). The tests allow you to check if certain system settings and connections were set up correctly.Only valid for: Java |

3.8.1 Smoke Testing User ManagementThe following smoke tests are available for the SAP User Management Engine (UME): 2 automatic system smoke tests 2 manual smoke testsThese tests verify the correctness of the User Management configuration as well as the SAP Java Connector (JCo) and the Remote Function Call (RFC) configuration on the current J2EE server.You launch the UME smoke tests from the Live Auction Cockpit Smoke Test page that is stored on the J2EE server and has a URL similar to this one: http://:/srm/laThe automatic smoke tests run automatically when the smoke test page loads. When a test runs error-free, the result is displayed in green. When a test fails, the result is displayed in red. The J2EE server log and trace files display more information about errors after the tests have ended. You must solve errors in the order they are presented on the smoke test page.

UME Smoke Test ProcessesThe tests perform the following automatic and manual checks: The system verifies that the J2EE server is configured to use an ABAP backend as the UME data

store. The system verifies that the JCo/RFC connection to the SRM server is working properly. You run a manual smoke test to verify that the UME logon page is working properly and that it

is using the correct ABAP back end for user authentication.

3 Follow-Up Activities3.8 LAC Smoke Tests

2013-08-13 PUBLIC 27/32

You run a manual smoke test to verify that the single sign-on (SSO) ticket issuing system is generating an SSO ticket that is compatible with the current J2EE server.

The procedures for the manual smoke tests are described below.

PrerequisitesThe automatic system smoke test has verified that the J2EE server is configured to use an ABAP back end as the UME data source.

ProcedureYou verify that the UME logon page is working properly and is using the correct ABAP back end for user authentication:1. Go to the LAC smoke test page and choose the Smoke Test User Management tab.2. Choose UME User Admin and log on to the SAP Supplier Relationship Management (SAP SRM)

server to which the current J2EE server is connected.If the user authentication is successful, you see the user details screen on the UME administration page.

After you have run the above manual smoke test, proceed to the second one to check that the SSO ticket is generated properly:1. Go to the LAC smoke test page and choose the Smoke Test User Management tab.2. Enter the URL of the SSO ticket issuing system and choose Logon.

When the logon screen is displayed, log on with an SAP SRM user.3. When you have logged on successfully, refresh the LAC smoke test page.

The ticket information as well as the status of the JCo RFC connection is displayed at the bottom of the page.


3.8.2 Smoke Testing the LAC AppletThe following smoke tests are available for the Live Auction Cockpit (LAC): 3 automatic system smoke tests 1 manual smoke testThese tests verify the correct deployment of the LAC applet and resource bundles.You launch the LAC applet smoke tests from the LAC smoke test page that is stored on the J2EE server and has a URL similar to this one: http://:default_port~50000/srm/la.The automatic smoke tests run automatically when the smoke test page loads. When a test runs error-free, the result is displayed in green. When a test fails, the result is displayed in red. The J2EE server log and trace files display more information about errors after the tests have ended. You have to solve errors in the order they are presented on the smoke test page.


28/32 PUBLIC 2013-08-13

LAC Smoke Test ProcessesThe system verifies that the following LAC JAR files are deployed properly: The initiator applet JAR file The respondent applet JAR file The client resources JAR file

NOTEIf you want to download the JAR files for further analysis after any of the steps above, you can choose the Download function on the LAC smoke test page.

You run a manual smoke test to verify that the LAC applet settings are correctly configured and that the applet can be launched.

PrerequisitesThe three automatic smoke tests have verified the correct deployment of the respective LAC JAR files.

ProcedureStart the test by choosing Test on the LAC smoke test page on the Smoke Test Applet tab.The input fields displayed in this test are optional.If the applet settings are configured properly and the applet can be launched, the applet start screen appears.

NOTEIf you know the GUID (Globally Unique Identifier) of a valid auction on the SAP Supplier Relationship Management (SAP SRM) server and want to view the auction in the applet, enter all the necessary information in the optional input fields of the smoke test and then choose Test.

End of: Java |End of: Java |End of: ABAP;Java |


2013-08-13 PUBLIC 29/32

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 .ExampleExample

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

Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the

documentationhttp://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 Web123456 Hyperlink to an SAP Note, for example, SAP Note 123456Example 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 toolsEXAMPLE 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/32 PUBLIC 2013-08-13

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

Copyright 2013 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.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 http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2013-08-13 PUBLIC 31/32

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

Copyright 2013 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.

SAP Supplier Relationship Management 7.0 Including Enhancement Package 3 Java and ABAPTable of Contents1 Getting Started1.1 Essential Information: Process and Documentation Overview1.2 Additional Installation Information1.3 Important SAP Notes1.4 Glossary

2 Process2.1 Note About the Process2.2 Update and Migration Process for SAP HANA

3 Follow-Up Activities3.1 Defining a Web Alias3.2 Defining a Web Alias3.3 Live Auction Properties: Overview and Modifications3.3.1 JCo Property Settings3.3.2 JCo Client Settings3.3.3 JCo Message Server Client Settings3.3.4 JCo Pool Settings3.3.5 Other Property Settings for LAC3.3.6 Modifying Properties

3.4 Configuring Single Sign-On for LAC3.5 Enabling Auctions3.5.1 Creating HTTP Connections to an External Server3.5.2 Defining a Back-End Destination3.5.3 Defining Number Ranges for Auctions

3.6 Copying Customizing Settings from the Default Client3.7 Server Name and IP Address3.8 LAC Smoke Tests3.8.1 Smoke Testing User Management3.8.2 Smoke Testing the LAC Applet

Copyright and trademarks

Documents

SAP Supplier Relationship Management 7.0 Including Enhancement Package 3 Java and ABAP