Installation Guide

SAP enhancement package 1 for SAP SRM 7.0 Java Hubs Based
on SAP NetWeaver 7.3 Application Server Java
Additional Planning, Preparation, and Post-installation Steps

Target Audience
Ç1Ï˘;Ó System Administrators
Ç1Ï˘;Ó Technical Consultants

PUBLIC
Ç1Ïü˚˝8Lùü˛ai yÿì¡{T"ì’AkN¶B°ùžN·áSïŽy⁄˚aa°åøi…Ò DGÜł ‚ 1ÙB„‘Ù2bü
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: http://service.sap.com/srm-inst.

The following table provides an overview of the most important document changes.
Version Date Description
1.0 2011-09-19 Initial Version

2/26 PUBLIC 2011-09-19

Table of Contents

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

Chapter 2 Planning and Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Live Auction Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 Post-Installation Steps for Live Auction Cockpit . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 Defining a Web Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.2 Configuring Live Auction Cockpit Settings with the J2EE Configuration
Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.2.1 Modifying Property Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.2.1.1 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.3 Configuring Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.4 Managing Customizing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.4.1 Maintaining HTTP Connections to an External Server . . . . . . . . . . . . . . . . . . 16
3.1.4.2 Maintaining the Definition of a Back-End System in B2B . . . . . . . . . . . . . . . . . 17
3.1.4.3 Maintaining Number Ranges for Transaction Type . . . . . . . . . . . . . . . . . . . . . 17
3.1.5 Configuring Properties for Live Auction Cockpit . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.6 Adjusting Server Name and IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1.7 Live Auction Cockpit Smoke Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.7.1 Smoke Test (User Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.7.1.1 Verifying the UM Logon Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.7.1.2 Verifying the SSO Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.7.2 Smoke Test (Applet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.7.2.1 Verifying the Live Auction Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2 Accessing Configuration Documentation in SAP Solution
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 4 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.1 Installing the Business Packages for SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2011-09-19 PUBLIC 3/26

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

1 Introduction

You need this document when you install SAP enhancement package 1 for SAP SRM 7.0 Java Hubs
based on SAP NetWeaver 7.3 application server Java. This document contains additional planning,
preparation, and post-installation steps that you have to perform in addition to the installation
procedure described in the documentation Installation Guide — SAP Systems Based on SAP NetWeaver 7.3
Application Server Java on <OS>: <DB>.
Make sure you have read the documentation Master Guide – SAP Supplier Relationship Management powered by
SAP NetWeaver before you start with any installation guide. The Master Guide and the installation guides
are available at http://service.sap.com/srm-inst Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 7.01 .

2011-09-19 PUBLIC 5/26

This page is left blank for documents
that are printed on both sides.
2 Planning and Preparation
2.1 Live Auction Cockpit

2 Planning and Preparation

\ôT¾…*<{]b¸aM×vÐR?”ÜkNèb4&ÖåÕ*fyK‰TEÁúk¨)Œóià@Ë0UF!›zbŒ^h´]¯V|Z‘ÝZú{H<¦;¾ÖÔ…¹’IûÙBN’<õ9ø'ž`è Ç

2.1 Live Auction Cockpit

SAP Bidding Engine with Live Auction Cockpit (LAC) enables you to perform live online auctions in
a real-time user interface. For more information about the features and functions available for live
auctions, see the release notes and SAP library documentation.

Before You Install Live Auction Cockpit

LAC is deployed as part of the overall installation of SAP SRM with SAP NetWeaver Java Application
Server (J2EE Engine). If you install the SRM ABAP system and J2EE Engine on the same machine, the
ABAP back-end system is the default data source, as desired. However, if you install the J2EE Engine on
a separate machine, you must change the default setting and select the SRM ABAP back end as the data
source for the J2EE Engine.

CAUTION

When defining parameters as part of the process of installing Live Auction Cockpit, you must
select the ABAP back end as the UME data source for the configuration in order for SSO to work
with LAC.

Useful Information in SAP Library

Several post-installation tasks refer to activities performed in the J2EE Engine. These include using the
administration and configuration tools, as well as starting and stopping the system. For more
information about the tools and the procedures below, see the following documentation for the J2EE
Engine.
\ôTÿ5p Starting or stopping the J2EE Engine
EXAMPLE

SAP NetWeaver 7.3 Library English SAP NetWeaver Library: Function-

http://help.sap.com/nw73
Oriented View Application Server Application Server Java Administering Application Server Java
Administration Administration Tools SAP NetWeaver Administrator Operation Work Center
\ôTÿ5p Configuring SSO between the J2EE Engine and the back-end system
EXAMPLE

http://help.sap.com/nw73 SAP NetWeaver 7.3 Library English SAP NetWeaver Library: Function-
Oriented View Security User Authentication and Single Sign-On

2011-09-19 PUBLIC 7/26

2 Planning and Preparation
2.1 Live Auction Cockpit

˝ÚÄùÌk Configuring User Management Engine

EXAMPLE

http://help.sap.com/nw73 SAP NetWeaver 7.3 Library English SAP NetWeaver Library: Function-
Oriented View Security Identity Management User Management of the Application Server Java
˝ÚÄ˝é¥ …˙Èl%™>ÏeN¤Ét—´â*˘‡\9„ÒÑDçcD[Ó¸‡/¾flÈ0þ]GL{É—\;DéÚ½MÖÆï˘龀DíVJò5ýí˜4?

8/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

3 Post-Installation

p8,ł_�Dfi[òfle·€1“GraÞ¯gl˘Tˇ hô0g” hÁçÙ<ƒn'åÌÐ…œO¾žÒÐßW"fiˆ(`W>èdÓ¥˘âÕfŧÏ˚xP’ Ý˝C_uFa ̦ßSûâק¯

3.1 Post-Installation Steps for Live Auction Cockpit

3.1.1 Defining a Web Alias
To facilitate customization, the resource files for the Live Auction Cockpit applet 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 via HTTP. This is achieved by creating a Web alias for the
directory that contains the resources. Without this alias, the applet cannot load properly.

Procedure
1. Go to the SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa
where
p8í U <host> is the host where AS Java is installed
p8í U <port> is the HTTP port of the ICM. It consists of 5<Java instance_number>00.
2. Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3. Choose Add Alias
4. In the Name column, enter srmla/lib/resources.
5. Enter Path.
EXAMPLE

<INSTDIR>:\usr\sap\<SAPSID>\SYS\global\srmla\resources
6. Choose Save.

NOTE

If 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 (<INSTDIR>:\usr\sap\<SAPSID>>\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.

2011-09-19 PUBLIC 9/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

3.1.2 Configuring Live Auction Cockpit Settings with the J2EE

Configuration Adapter
The following table lists the JCo settings for Live Auction Cockpit. You can modify properties with
default settings to tune your systems to find the optimal values for these properties. You must enter
values for those properties that are not shipped with default values. See the following sections for more
information and recommended settings.

JCo Properties

* Required properties that are described in other sections of this document.

◊ It is highly recommended that you tune your systems to find the optimal values for these properties.
For more information, see JCo Pool Settings.
Property Name Description Default Value
jco.client.lang Creates a JCo pool with the specified value for ◊
the SAP logon language. M"VgÞ English, EN
M"VgÞ German, DE
M"VgÞ Japanese, JA
jco.client.client SAP Client *
jco.client.user Logon user *

NOTE
This user must be defined in the SAP
system as follows:
M"VgÞ User type: communication or system user
M"VgÞ 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 R/3 name *
jco.client.ashost SAP Application Server *
jco.client.sysnr SAP system number *
jco.poolmgr.connectiontimeout Connection is considered to have timed out 600000 ms (10 minutes)
when there has been no activity on it for the
specified time interval.
jco.poolmgr.maxwaittime Maximum length of time, in milliseconds, to 30000 ms (30 seconds)
wait for a connection request when the pool
is exhausted.
jco.poolmgr.timeoutcheckinterva The length of time, in milliseconds, after 60000 ms (1 minute)
l which all connections are periodically
checked for timeouts.
jco.pool.maxconn This is the absolute maximum number of 15 ◊
connections that can be simultaneously
opened for the given pool.

10/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

Property Name Description Default Value

jco.pool.maxpoolsize Maximum number of connections that can be 10 ◊
kept open and managed in the pool.
jco.performance.monitor Monitors the execution time for ABAP 0 (disabled)
function modules and writes the statistics to
the monitor log file.
<ËÊÎáë 0 = disabled
<ËÊÎáë 1 = enabled
Log file: <INSTDIR>\usr\sap\<sapsid>\
<instanceNumber>\j2ee\cluster\server0\
log\applications\sap.com\com.
sap.srm.la\srmlaLog-[n].log

jco.performance.monitor.interva The intervals, in milliseconds, at which the 300000 ms (5 minutes)

l statistics for the execution times of ABAP
function modules are written to the log file.
jco.pool.monitor Monitors the JCO pool and writes the statistics 0 (disabled)
to the monitor log file.
<ËÊÎáë 0 = disabled
<ËÊÎáë 1 = enabled
Log file: <INSTDIR>\usr\sap\<sapsid>\
<instanceNumber>\j2ee\cluster\server0\
log\applications\sap.com\com.sap.srm.la
\srmlaLog-[n].log

jco.pool.monitor.interval The intervals, in milliseconds, at which the 300000 ms (5 minutes)

statistics on the JCo pool size.

3.1.2.1 Modifying Property Values

1. Go to the SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa
<ËÊÎáë <host> is the host where AS Java is installed.
<ËÊÎáë <port> is the HTTP port of the ICM. It consists of 5<Java instance_number>00.
2. Choose Operations Systems Start & Stop Java Applications
3. Search for and select com.sap.srm.la
4. Choose More Actions.
5. Choose View Application Properties.
6. Under Extended Details, select the property to be changed.
7. Choose Save.
8. Stop and restart the application.

3.1.2.1.1 Properties
The following tables describe the properties available for configuration. Use this information to help
you change settings as explained above in Modifying Property Values [page 11].

2011-09-19 PUBLIC 11/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

JCo Client Settings

The following properties are required to establish communication between Live Auction Cockpit and
the back-end SAP System.
Property Comments
Jco.client.client The value of this property is the client number that the SAP SRM system is running on.
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 user’s profile, and must have authorization to access the following
function groups:
{EÒ¶T¹ BACV
{EÒ¶T¹ BBP_LA_BIZAPI
{EÒ¶T¹ BBP_LA_MAINTENANCE
{EÒ¶T¹ RFC1
{EÒ¶T¹ SDIFRUNTIME
{EÒ¶T¹ SYST
{EÒ¶T¹ SYSU
For more information about RFC authorization objects, see http://help.sap.com/nw70
SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrator's Guide SAP
NetWeaver Security Guide Security Guides for Connectivity and Interoperability Technologies RFC/ICF
Security Guide RFC Scenarios RFC Communication Between SAP Systems Authorizations .

NOTE
For connectivity between the UI and back-end system, the generic R/3 user must be
assigned the following roles:
{EÒ¶T¹ Purchaser Roles
EXAMPLE
{EÒ¶TÖ SAP_BBP_STAL_OPERAT_PUR_LIGHT for operational purchaser
{EÒ¶TÖ SAP_BBP_STAL_STRAT_PUR_LIGHT for strategic purchaser (which
should include the profile containing the authorization object
BBP_PD_AUC)
{EÒ¶T¹ A bidder role
EXAMPLE
SAP_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.

JCo Message Server Client Settings

Determine whether or not to use group load balancing in your system landscape, then make settings
as appropriate.

12/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

NOTE

You only need to provide either the application server settings or the group load balancing settings,
not both. However, if both are provided, Live Auction Cockpit connects using the application
server settings with no load balancing

System Landscape Settings

Group Load Balancing Ææ½#¸‹ jco.client.mshost
Ææ½#¸‹ jco.client.group
Ææ½#¸‹ jco.client.r3name

Application Server with No Load Balancing Ææ½#¸‹ jco.client.ashost

Ææ½#¸‹ jco.client.sysnr

JCo Pool Settings

RECOMMENDATION

We strongly recommend you to test your environment to determine the optimal values for these
three properties. 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 Comments Recommendations

jco.pool.maxconn This value refers to the absolute maximum This value should always be equal to or
number of connections that Live Auction greater than the value for
Cockpit can simultaneously open for each jco.pool.maxpoolsize.
pool. You should set this value high enough to
handle peak activity loads.
CAUTION
Live Auction Cockpit creates a pool for RECOMMENDATION
each supported SAP client. Therefore, For 25 concurrent bidders, we
in a multiple SAP client scenario, it is recommend setting the value to 15.
possible to have more than one pool.
jco.pool.maxpoolsize This value refers to the maximum number You should set this value high enough so
of pooled connections kept for reuse. that under a typical workload, no
additional connections are required.
CAUTION
The difference between the value of RECOMMENDATION
jco.pool.maxconn and For 25 concurrent bidders, we
jco.pool.maxpoolsize is the number recommend setting the value to 10.
of connections that can be opened to
the SAP system to perform a task and
then disconnect. These connections
are not reused and are therefore
considered more expensive.
jco.client.lang This is an optional setting. If you expect to have a large group of
When this value is set, a JCo pool is created users logging on for any given language,
using its value as the SAP logon language. we strongly recommend you to specify
that language in the property file. This
avoids unnecessarily consuming

2011-09-19 PUBLIC 13/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

Property Comments Recommendations

The value for this property must be a comma resources with multiple one-time
separated list of valid 2-letter SAP external connections by using pooled
language codes. connections instead.
As a result of defining language values in
CAUTION the property file, a JCo pool is created to
Ensure that the SAP SRM system has a maintain connections for each language
language installed for each of the and client number combination.
corresponding language codes. Therefore, we recommend you to also
On the fly connections, which are adjust the value for
more resource consuming than jco.pool.maxpoolsize accordingly.
pooled connections, are created for
users who log on with a language that
is not listed in the property file.

Other Property Settings

Property Name Description Default Value
msg.client.protocol Override the default messaging empty (no override)
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.
msg.client.serverHost Override the default host name of empty (no override)
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.
msg.client.serverPort Override the default port number of empty (no override)
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.
srmla.um UME authentication. empty (enabled)
0 = disable

·ï½−cT…'›¢òÎÀ=ÿ¥'o>–ã©@4V-4Jã<Ò`Ãz"8:#¤Bd3łQÿêE¥ì&éÉ/tõ˛Ã¶¤fi=?á^¨ûƒè×7ÄÃ!ÃÐ÷ÀÐ6Wn-îÛà fis`$w yKfi

3.1.3 Configuring Single Sign-On

To enable Single Sign-On (SSO) you need to configure certain settings in SAP Supplier Relationship
Management (SAP SRM).

14/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

Prerequisites
You have access to the following transactions in SAP SRM:
zYv÷6 RZ10 (Edit Profiles)
zYv÷6 STRUST (Trust Manager)
zYv÷6 SAP NetWeaver Application Server Java (AS Java) is running.
zYv÷6 To start SAP NetWeaver Administrator, enter the follwoing data in a Web browser: http://
<host>:<port>/nwa, where

zYv÷Y <host> is the host where AS Java is installed

zYv÷Y <port> is the HTTP port of the ICM. It consists of 5<Java instance_number>00. for Example,
if the Java instance number is 60, the HTTP port is 5600.

Procedure
1. Open your SAP SRM System
1. Create SSO ticket in Profile Maintenance.
1. Go to transaction RZ10.
2. Choose the Default profile along with the latest version number and select Extended
Maintenance.
3. Change the following profile parameters:
zYv÷6 login/create_sso2_ticket = 1
zYv÷6 login/accept_sso2_ticket = 1
4. Save and Activate the profile.
A new profile is automatically generated.
5. Restart the application server.
CAUTION

Do not forget or skip this step.

2. Export the R3 SSO certificate from the Trust Manager on the target host server.
1. Go to transaction STRUST.
2. Double-click the text box to the right of Own certif.
The certificate information is displayed.
NOTE

Make a note of the values displayed in the certificate information because you need
to enter those values below in step 3.
3. Click the icon with the quick info Export Certificate.
4. Save the file as <R3_Name>-<Client>.crt.
EXAMPLE

For SAP System EBS, client 300, the file name is EBS-300.crt.
CAUTION

Make sure Binary is selected under File Format.

2011-09-19 PUBLIC 15/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

NOTE

If you export the certificate to a local system, you must copy the file from the local
system to the target host server.
2. Go to the SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa
to import the R3 SSO certificate to the java engine.
1. Go to the Configuation tab
2. Choose Trusted Systems in the Security area
3. Choose Add Trusted Systems By Uploading Certificate Manually
4. Go to the Single Sign-On with SAP Logon Tickets tab.
5. Enter the System ID, the Client and the Certificate File name.
For more information about how to configure Single Sign-on, see SAP Library at http://
help.sap.com/nw73 under SAP NetWeaver 7.3 Library English SAP NetWeaver Library: Function-Oriented View
Security User Authentification and Single Sign-On
YÄïìdŸ±˜ Ï
w|˛ØÓú±?ÕsÂXÇS,,ˆ†Rx›×6äDŁ÷Ø ¨<p!ý¹ïÍAô#‚Ïra¶m)�‡‡Ð8;µìû§á˚ç˙}†d®DˇŠ

3.1.4 Managing Customizing Settings

You must make these settings in the SAP Supplier Relationship Management (SAP SRM) system so
that Live Auction Cockpit functions correctly:
YÄï AV Maintaining HTTP Connections to an External Server [page 16]
YÄï AV Maintaining the Definition of a Back-End System in B2B [page 17]
YÄï AV Maintaining Number Ranges for Transaction Types [page 17]

3.1.4.1 Maintaining HTTP Connections to an External Server

You must configure the HTTP connections to direct ITS to the server name and port of the Live Auction
J2EE server. This creates the Live Auction link on the ITS page used to launch the Live Auction Cockpit.

Procedure
1. See Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings
Define RFC Destinations HTTP Connections to Ext. Server .
2. Choose Create.
3. Create an RFC destination with the key SRM_LIVE_AUCTION and connection type G.
4. 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 (5<instance
number>00). For example, if during the installation, the instance number used was 01 then the port
number is 50100.)

16/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

NOTE

If you have implemented a reserve proxy as an additional security measure to hide and protect
the private hostname of the Live Auction J2EE server, enter the reserve proxy server host
name and port number for the Target host and Service No.
5. Test the connection to see whether SAP SRM can locate the external server for the HTTP service.
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.

3.1.4.2 Maintaining the Definition of a Back-End System in

B2B
Procedure
1. In transaction SM31, enter table/view BBP_BACKEND_DEST.
2. Choose Maintain.
3. Choose New Entries.
4. Select the destination for which you want to configure this SAP SRM Client, using the
Destinations list.
NOTE

Once you have created another HTTP Connection to Ext. Server (via transaction SM59)
with another key, such as SRM_LIVE_AUCTION_2, this additional entry appears in the list of
destinations.
5. Select SRM Live Auction from the System Type list.
6. Save your data.

Result
The system is now properly configured for the current SAP SRM client to use the destination specified.

3.1.4.3 Maintaining Number Ranges for Transaction Type

Procedure
1. See Customizing for SAP Supplier Relationship Management under 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.

3.1.5 Configuring Properties for Live Auction Cockpit

We deliver customized properties required for Live Auction Cockpit in the standard SAP system delivery
into client 000. If the client for Live Auction Cockpit is not the default 000, compare and adjust the

2011-09-19 PUBLIC 17/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

entries for view BBPV_LA_PROP in the Live Auction Cockpit client (for example if you use client 200).
Make sure that the entries there are identical to those in client 000 of the same system.

CAUTION

You must configure an RFC connection to the client 000 of the SAP system. For more information,
see Managing IMG Settings [page 16].

Procedure
1. Go to transaction SM31 on the Live Auction Cockpit client.
EXAMPLE

200
2. Enter Table/View BBPV_LA_PROP.
3. Choose Maintain.
The Live Auction Properties Management page is displayed.
4. Choose Utilities Adjust .
5. Enter the R/3 Connection that points to client 000 and press 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 the Edit Adjust Copy all enter .
9. Press F3 to go back one screen.
10. Press F3 again.
A dialog box displays asking whether or not to copy the changes.
11. Choose Yes.
12. Save the settings and exit.

3.1.6 Adjusting Server Name and IP Address

Procedure
In order for the SAP Bidding Engine server to recognize the Live Auction Cockpit server, you need to
add the server name and its IP address to the file hosts. The file is located at C:\WINNT\System32\drivers
\etc.

EXAMPLE

10.48.82.200 : la_server.wdf.sap.corp

CAUTION

To ensure accurate time-related data and function, confirm that the system times for both the
J2EE server and the SAP system server are synchronized.

18/26 PUBLIC 2011-09-19

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

You can also use, for example, SNTP (Simple Network Time Protocol) to ensure time does not
drift in both servers after initial synchronization.

JÛ•/’^ñgöÉLϦw‘•eE2}W&½oë´zý÷˙Z2qèq7èRIÙ³‹iüv�˛ßó°B−⁄ñÙh ˘$¼6â…Pœ§¹t‰ÊÊNÍ‘,PƒÝÕh+ÍÚ˜^½³Ü Æ÷−G1[C‘·Æ¸ˇ¬i¬ï<9V+˙eł!äÏ£ÿÕļ±ôê´9úã

3.1.7 Live Auction Cockpit Smoke Test

Launch the Live Auction Cockpit Smoke Test in your web browser to check that implementation was
successful.
The smoke test page contains three tabs:
JÛ•Àµ’ General Information
Contains information about the Live Auction build as well as the J2EE server.
JÛ•Àµ’ Smoke Test (User Management) [page 19]
JÛ•Àµ’ Smoke Test (Applet) [page 20]
The Live Auction Cockpit Smoke Test resides on the J2EE server and has a URL similar to the following:
http://<j2ee_host.domain>:<default_port~50000>/srm/la.

3.1.7.1 Smoke Test (User Management)

The Smoke Test (User Management) tab contains 4 smoke tests – 2 self-diagnoses and 2 manual
diagnoses – that verify the correctness of the User Management configuration as well as the JCo/RFC
configuration on the current J2EE server. All self-diagnoses are run automatically when the page loads.
If a self-diagnosis runs error-free, the result is displayed in green. If a self-diagnosis fails, the result is
displayed in red. The J2EE's log and trace files display more information about an error after the result
has been displayed. Try to resolve any failures, in the order they are presented on the page.

Process

JÛ•Àµ’ The system verifies that the J2EE server is configured to use an ABAP back end as the UME data
store.
JÛ•Àµ’ You verify that the UM logon page is working properly and that it is using the correct ABAP back
end for user authentication.
JÛ•Àµ’ You verify that the single sign-on ticket issuing system is generating an SSO ticket that is compatible
with the current J2EE server.
JÛ•Àµ’ The system verifies that the JCo/RFC connection to the SRM server is working properly.

3.1.7.1.1 Verifying the UM Logon Page

Prerequisites
The system verifies that the J2EE server is configured to use an ABAP back end as the UME data source.

2011-09-19 PUBLIC 19/26

3 Post-Installation
3.1 Post-Installation Steps for Live Auction Cockpit

Procedure
1. Choose UME user admin and log on to the 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.
2. Close the browser window.

3.1.7.1.2 Verifying the SSO Ticket

Prerequisites
You have verified that the UM logon page is working properly and that it is using the correct ABAP
back-end for user authentication.

Procedure
1. Enter the URL for the ticket issuing system and choose Logon.
When the logon screen is displayed, log on with an SAP SRM user.
2. Once you have logged on successfully, close the browser window.
3. Return to the smoke test and refresh the page.
The ticket information as well as the status of the JCo RFC connection is displayed at the bottom
of the page.

3.1.7.2 Smoke Test (Applet)

The Smoke Test (Applet) tab contains 4 smoke tests – 3 self-diagnoses and 1 manual diagnosis – to
verify the deployments of the Live Auction Java applets and resource bundles.
All self-diagnoses are run automatically when the page loads. If a self-diagnosis runs error-free, the
result is displayed in green. If a self-diagnosis fails, the result is displayed in red. Try to resolve any
failures, in the order that they are presented on the page.

Process

o€~0=Å The system verifies that the initiator applet JAR file of Live Auction is deployed properly.
o€~0=Å The system verifies that the respondent applet JAR file of Live Auction is deployed properly.
o€~0=Å The system verifies that the client resources JAR file of Live Auction is deployed properly.

NOTE

If you want to download the JAR file for further analysis after any of the steps above, click the
Download button.

o€~0=Å You verify that the Live Auction applet settings are correctly configured and that the applet can
be launched.

20/26 PUBLIC 2011-09-19

3 Post-Installation
3.2 Accessing Configuration Documentation in SAP Solution Manager

3.1.7.2.1 Verifying the Live Auction Applet

Prerequisites
The system has verified the successful deployment of the following:
`±eŽ.M Live Auction initiator applet JAR file
`±eŽ.M Live Auction respondent applet JAR file
`±eŽ.M Live Auction client resources JAR file

Procedure
1. Trigger the test by choosing Test.
NOTE

The input fields displayed in this test are optional.

If the applet settings are configured properly and the applet can be launched, you see the applet's
splash screen.
NOTE

If you know the GUID of a valid auction on the SAP SRM server and want to view the auction
in the applet, enter all the necessary information in the input fields and then choose Test.
`±e|…÷ùÒo2æ}łWb¿ü½±C“Q/ñåOˇË�t“‚L·Úk3lç][]ï·�¼Ùì2§ÜTÏFŸÏ‡òb@o˘Ôº‘ùn_P+Y˚Í,Àz[ õŠÇ–o²=_—@^<ÉQLÖþÃŁ}ûJk?#Ì.3þ¤q
`±e|…÷ùÒo2æ}łWb¿ü½±CžQ2ñåPˇð�O“ÔLÄÚO3kçH[]ô·ù¼äì@§ÒT•F·Í‡ôn@;˘µç‘ÉnyPz˚â,£z1 :ŠØ

3.2 Accessing Configuration Documentation in SAP Solution

Manager
To access configuration documentation in SAP Solution Manager, you have to connect your newly
installed SAP system to SAP Solution Manager.

Procedure
Create a configuration project with the related configuration guide as described in the following
documentation:
http://help.sap.com SAP Solutions SAP Solution Manager Documentation for SAP Solution Manager
<current release> SAP Solution Manager Implementing and Upgrading SAP Solutions Projects
Configuration .

More Information
http://service.sap.com/solutionmanager Media Library How-To Documents How to Create a
Configuration Guide using SAP Solution Manager

2011-09-19 PUBLIC 21/26

This page is left blank for documents
that are printed on both sides.
4 Additional Information
4.1 Installing the Business Packages for SRM

4 Additional Information

4.1 Installing the Business Packages for SRM

Process
For information on installing the Business Packages for SAP SRM 7.0, see SAP Note 1232945.

2011-09-19 PUBLIC 23/26

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example Ý¿‹‡«° Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Ý¿‹‡«° Cross-references to other documentation or published works
Example Ý¿‹‡«° Output on the screen following a user action, for example, messages
Ý¿‹‡«° Source code or syntax quoted directly from a program
Ý¿‹‡«° File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

24/26 PUBLIC 2011-09-19

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP
AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an SAP company
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.

Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or
altered in any way.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

2011-09-19 PUBLIC 25/26

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2011 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.