Embed Size (px)
DESCRIPTION
Installation Guide SRM EHP2 Java and ABAP
Citation preview
Installation GuideSAP Supplier Relationship Management 70 Including Enhancement Package 2 Java and ABAP
For ABAP Java
Target Audience System Administrators Technology Consultants
PUBLICDocument version 10 ndash 2011-11-08
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 httpservicesapcom
instguides
The following table provides an overview of the most important document changes
Version Date Description
10 2011-11-08 Final version
230 PUBLIC 2011-11-08
Table of Contents
Chapter 1 Getting Started 5
11 Essential Information Process and Documentation Overview 5
12 Additional Installation Information 6
13 Important SAP Notes 8
14 Glossary 8
Chapter 2 Process 9
21 Note About the Process 9
Chapter 3 Follow-Up Activities 11
31 Defining a Web Alias 11
32 Live Auction Properties Overview and Modifications 12
321 JCo Property Settings 13
322 JCo Client Settings 14
323 JCo Message Server Client Settings 15
324 JCo Pool Settings 15
325 Other Property Settings for LAC 17
326 Modifying Properties 17
33 Configuring Single Sign-On for LAC 19
34 Enabling Auctions 21
341 Creating HTTP Connections to an External Server 22
342 Defining a Back-End Destination 22
343 Defining Number Ranges for Auctions 23
35 Copying Customizing Settings from the Default Client 23
36 Server Name and IP Address 24
37 LAC Smoke Tests 25
371 Smoke Testing User Management 25
372 Smoke Testing the LAC Applet 26
2011-11-08 PUBLIC 330
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
1 Getting Started
Only valid for ABAPJava |
This section of the guide contains important information that you need to read before starting your
installation processEnd of ABAPJava |
Only valid for ABAPJava |
11 Essential Information Process and Documentation Overview
Only valid for ABAPJava |
You are currently reading the Installation Guide for SAP Supplier Relationship Management 70 Enhancement Package
2 ABAP and Java This guide only contains information specific to SAP SRM but you need additional
information provided by the SAP SRM 702 Master Guide to enable you to perform your installation
correctlyEnd of ABAPJava |
Only valid for ABAPJava |
NOTE
Specifically 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 70 Enhancement Package 2 ABAP
and Java
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 702 Master Guide see path below
End of ABAPJava |
The SAP SRM 702 Master Guide contains a section Main Implementation Processes and Related Documentation with
the following subsections with vital information
1 Getting Started
11 Essential Information Process and Documentation Overview
2011-11-08 PUBLIC 530
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
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 httpservicesapcom
instguides
The following table provides an overview of the most important document changes
Version Date Description
10 2011-11-08 Final version
230 PUBLIC 2011-11-08
Table of Contents
Chapter 1 Getting Started 5
11 Essential Information Process and Documentation Overview 5
12 Additional Installation Information 6
13 Important SAP Notes 8
14 Glossary 8
Chapter 2 Process 9
21 Note About the Process 9
Chapter 3 Follow-Up Activities 11
31 Defining a Web Alias 11
32 Live Auction Properties Overview and Modifications 12
321 JCo Property Settings 13
322 JCo Client Settings 14
323 JCo Message Server Client Settings 15
324 JCo Pool Settings 15
325 Other Property Settings for LAC 17
326 Modifying Properties 17
33 Configuring Single Sign-On for LAC 19
34 Enabling Auctions 21
341 Creating HTTP Connections to an External Server 22
342 Defining a Back-End Destination 22
343 Defining Number Ranges for Auctions 23
35 Copying Customizing Settings from the Default Client 23
36 Server Name and IP Address 24
37 LAC Smoke Tests 25
371 Smoke Testing User Management 25
372 Smoke Testing the LAC Applet 26
2011-11-08 PUBLIC 330
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
1 Getting Started
Only valid for ABAPJava |
This section of the guide contains important information that you need to read before starting your
installation processEnd of ABAPJava |
Only valid for ABAPJava |
11 Essential Information Process and Documentation Overview
Only valid for ABAPJava |
You are currently reading the Installation Guide for SAP Supplier Relationship Management 70 Enhancement Package
2 ABAP and Java This guide only contains information specific to SAP SRM but you need additional
information provided by the SAP SRM 702 Master Guide to enable you to perform your installation
correctlyEnd of ABAPJava |
Only valid for ABAPJava |
NOTE
Specifically 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 70 Enhancement Package 2 ABAP
and Java
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 702 Master Guide see path below
End of ABAPJava |
The SAP SRM 702 Master Guide contains a section Main Implementation Processes and Related Documentation with
the following subsections with vital information
1 Getting Started
11 Essential Information Process and Documentation Overview
2011-11-08 PUBLIC 530
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Table of Contents
Chapter 1 Getting Started 5
11 Essential Information Process and Documentation Overview 5
12 Additional Installation Information 6
13 Important SAP Notes 8
14 Glossary 8
Chapter 2 Process 9
21 Note About the Process 9
Chapter 3 Follow-Up Activities 11
31 Defining a Web Alias 11
32 Live Auction Properties Overview and Modifications 12
321 JCo Property Settings 13
322 JCo Client Settings 14
323 JCo Message Server Client Settings 15
324 JCo Pool Settings 15
325 Other Property Settings for LAC 17
326 Modifying Properties 17
33 Configuring Single Sign-On for LAC 19
34 Enabling Auctions 21
341 Creating HTTP Connections to an External Server 22
342 Defining a Back-End Destination 22
343 Defining Number Ranges for Auctions 23
35 Copying Customizing Settings from the Default Client 23
36 Server Name and IP Address 24
37 LAC Smoke Tests 25
371 Smoke Testing User Management 25
372 Smoke Testing the LAC Applet 26
2011-11-08 PUBLIC 330
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
1 Getting Started
Only valid for ABAPJava |
This section of the guide contains important information that you need to read before starting your
installation processEnd of ABAPJava |
Only valid for ABAPJava |
11 Essential Information Process and Documentation Overview
Only valid for ABAPJava |
You are currently reading the Installation Guide for SAP Supplier Relationship Management 70 Enhancement Package
2 ABAP and Java This guide only contains information specific to SAP SRM but you need additional
information provided by the SAP SRM 702 Master Guide to enable you to perform your installation
correctlyEnd of ABAPJava |
Only valid for ABAPJava |
NOTE
Specifically 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 70 Enhancement Package 2 ABAP
and Java
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 702 Master Guide see path below
End of ABAPJava |
The SAP SRM 702 Master Guide contains a section Main Implementation Processes and Related Documentation with
the following subsections with vital information
1 Getting Started
11 Essential Information Process and Documentation Overview
2011-11-08 PUBLIC 530
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
1 Getting Started
Only valid for ABAPJava |
This section of the guide contains important information that you need to read before starting your
installation processEnd of ABAPJava |
Only valid for ABAPJava |
11 Essential Information Process and Documentation Overview
Only valid for ABAPJava |
You are currently reading the Installation Guide for SAP Supplier Relationship Management 70 Enhancement Package
2 ABAP and Java This guide only contains information specific to SAP SRM but you need additional
information provided by the SAP SRM 702 Master Guide to enable you to perform your installation
correctlyEnd of ABAPJava |
Only valid for ABAPJava |
NOTE
Specifically 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 70 Enhancement Package 2 ABAP
and Java
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 702 Master Guide see path below
End of ABAPJava |
The SAP SRM 702 Master Guide contains a section Main Implementation Processes and Related Documentation with
the following subsections with vital information
1 Getting Started
11 Essential Information Process and Documentation Overview
2011-11-08 PUBLIC 530
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for ABAPJava |
1 Getting Started
Only valid for ABAPJava |
This section of the guide contains important information that you need to read before starting your
installation processEnd of ABAPJava |
Only valid for ABAPJava |
11 Essential Information Process and Documentation Overview
Only valid for ABAPJava |
You are currently reading the Installation Guide for SAP Supplier Relationship Management 70 Enhancement Package
2 ABAP and Java This guide only contains information specific to SAP SRM but you need additional
information provided by the SAP SRM 702 Master Guide to enable you to perform your installation
correctlyEnd of ABAPJava |
Only valid for ABAPJava |
NOTE
Specifically 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 70 Enhancement Package 2 ABAP
and Java
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 702 Master Guide see path below
End of ABAPJava |
The SAP SRM 702 Master Guide contains a section Main Implementation Processes and Related Documentation with
the following subsections with vital information
1 Getting Started
11 Essential Information Process and Documentation Overview
2011-11-08 PUBLIC 530
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Planning for Installation Update and Upgrade Processes
Contains a list of topics (including documentation references) you need to consider when you are
planning your implementation project
Implementation of the Installation Process
Provides 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 Process
Provides 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 Process
Provides 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
NOTE
Make 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 702 Master Guide from the SAP
Service Marketplace httpservicesapcominstguides Installation amp Upgrade Guides SAP
Business Suite Applications SAP SRM SAP SRM Server 702 End of ABAPJava |
Only valid for ABAPJava |
12 Additional Installation Information
When 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 httpservicesapcominstguides Installation amp Upgrade Guides
SAP Business Suite Applications SAP SRM SAP SRM Server 702
SAP SRM Server ABAP installation
You select the option SAP Application Server ABAP for SAP SRM 702 when you are asked to choose
the installation option All relevant ABAP components are then installed by the installation tool
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server ABAP of SAP
NetWeaver 70 Including EHP 3 on ltOSgt ltDBgt in parallel with this guide
1 Getting Started
12 Additional Installation Information
630 PUBLIC 2011-11-08
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP SRM Server Java installation
NOTE
You need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver
73 on ltOSgt ltDBgt in parallel with this guide
You can find the SAP NetWeaver server installation guide at httpservicesapcom
instguides Installation amp Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 702
SAP Note 1642797 describes where to find the correct kernel for a new Java installation on SAP
NetWeaver 73
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
NOTE
Note that SAP strongly recommends using the Live Auction ABAP version as of SAP SRM
701
For more information see httphelpsapcomsrm702 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 On
SRMLAC SRM Live Auction Cockpit AS Java
SRM JAVA SRM Java AS Java EP Core
SRM Supp SRM Supplier AS Java EP Core
BP-SRM SRM Portal Content AS Java EP Core SRM JAVA BP-SRM-COM
BP-SRM-COM SRM Business Packages AS Java EP Core
BP-Supp SRM Portal Content Supplier AS Java EP Core SRM Supp
Installation of SAP SRM Business Packages
For information on installing the Business Packages for SAP SRM see SAP Notes 1232945 and
1649846
1 Getting Started
12 Additional Installation Information
2011-11-08 PUBLIC 730
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Additional information is available in the SAP Help Portal httphelpsapcomsrm SAP
Supplier Relationship Management SAP Enhancement Package 2 for SAP SRM 70 Application Help SAP
Library SAP Supplier Relationship Management Business Packages End of ABAPJava |
Only valid for ABAPJava |
13 Important SAP NotesOnly valid for ABAPJava |
Note Number Title
1582094 EHP2 for SAP SRM 70 SP Stacks - Release amp Information Note
1642797 Java Installation for Business Suite 7i2011
1232945 BP for SRM 70 Installing the Business Packages
1649846 BP for SRM 70 EhP2 Installation Information
End of ABAPJava |
End of ABAPJava |
Only valid for ABAPJava |
14 Glossary
This section explains the most common terms and concepts used in the installation update and upgrade
guides
Term Concept Definition Explanation
Update Installation of an enhancement package on an existing SAP systemUpdate may also refer to other software updates such as support package deploymentsIn 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 package
Profiling 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 topicsA 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 ABAPJava |
End of ABAPJava |
1 Getting Started
13 Important SAP Notes
830 PUBLIC 2011-11-08
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for ABAPJava |
2 Process
This section of the guide contains information about process-related application-specific tasks ndash if there
are any (in some cases there are no application-specific tasks)
Only valid for ABAPJava |
21 Note About the ProcessOnly valid for ABAPJava |
NOTE
The 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 70 Including EHP
3 on ltOSgt ltDBgt
Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 73 on ltOSgt ltDBgt
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 mdash 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 70 Enhancement Package 2 actually requires no
application-specific steps in the Process section ndash 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
httpservicesapcominstguides Installation amp Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 702
End of ABAPJava |
End of ABAPJava |
End of ABAPJava |
2 Process
21 Note About the Process
2011-11-08 PUBLIC 930
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
This page is left blank for documents that are printed on both sides
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for ABAPJava |
3 Follow-Up Activities
Only valid for ABAPJava |
This section of the guide describes application-specific steps that have to be done after the installation
process is completeEnd of ABAPJava |
Only valid for Java |
31 Defining a Web Alias
To 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
Prerequisites
The J2EE Engine is running
Procedure
SAP NetWeaver Application Server Java 702
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 73 The
procedure for SAP NetWeaver 730 is described below
1 Open the J2EE Engine Administration tool
EXAMPLE
On Windows browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingobat
On UNIX browse to
ltINSTDIRgtusrsapltsapsidgtltinstancenumbergtj2eeadmingosh Port 5ltinstance
numbergt04
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 srmlalibresources
3 Follow-Up Activities
31 Defining a Web Alias
2011-11-08 PUBLIC 1130
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
7 Enter Path
EXAMPLE
ltINSTDIRgtusrsapltSAPSIDgtSYSglobalsrmlaresources
8 Choose Add
9 Choose Save Properties
10 Close the J2EE Engine Administration tool
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 (ltINSTDIRgtusrsapltSAPSIDgtgtSYS
globalsrmla) 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 730
Use the following procedure for SAP NetWeaver 730
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases
3 Choose Add Alias
4 In the Name column enter srmlalibresources
5 Enter the path
EXAMPLE
ltINSTDIRgtusrsapltSAP system IDgtSYSglobalsrmlaresources
6 Save your changesEnd of Java |
Only valid for Java |
32 Live Auction Properties Overview and Modifications
The following sections provide information that enables you to customize the Live Auction properties
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1230 PUBLIC 2011-11-08
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for Java |
321 JCo Property Settings
SAP 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 Value
jcoclientlang Creates a JCo pool with the specified value for the SAP logon language
English EN German DE Japanese JA
jcoclientclient SAP client -
jcoclientuser Logon user
NOTE
You have to define this user in the SAP system as follows User type communication or system user
Roles assigned Purchaser and Bidder
-
jcoclientpasswd Logon password -
jcoclientmshost SAP message server -
jcoclientgroup Group of SAP application servers -
jcoclientr3name SAP ERP name -
jcoclientashost SAP application server -
jcoclientsysnr SAP system number -
jcopoolmgrconnectiontimeout The connection is considered to have timed out when there has been no activity on it for the specified time interval
600000 ms (10 minutes)
jcopoolmgrmaxwaittime The maximum length of time in milliseconds for the system to wait for a connection request when the pool is exhausted
30000 ms (30 seconds)
jcopoolmgrtimeoutcheckinterval The length of time in milliseconds after which all connections are periodically checked for time-outs
60000 ms (1 minute)
jcopoolmaxconn The absolute maximum number of connections that can be simultaneously opened for a given pool
15
jcopoolmaxpoolsize The maximum number of connections that can be kept open and managed in the pool
10
jcoperformancemonitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file 0 = disabled 1 = enabled
0
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1330
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Property Name Description Default ValueLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcom sapsrmla
srmlaLog-[n]log
jcoperformancemonitorinterval The intervals in milliseconds at which the statistics for the execution times of ABAP function modules are written to the log file
300000 ms (5 minutes)
jcopoolmonitor Monitors the JCo pool and writes the statistics to the monitor log file 0 = disabled 1 = enabledLog file ltINSTDIRgtusrsapltsapsidgt ltinstanceNumbergtj2eeclusterserver0 log
applicationssapcomcomsapsrmla
srmlaLog-[n]log
0
jcopoolmonitor interval The intervals in milliseconds at which the statistics on the JCo pool size are written to the log file
300000 ms (5 minutes)
End of Java |
Only valid for Java |
322 JCo Client Settings
SAP 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 Description
Jcoclientclient The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running
Jcoclientpasswd NOTE
The password is not displayed Instead each character in the password is represented by an asterisk ()
Jcoclientuser JCo users must be assigned standard authorization objects such as S_RFC contained as part of the standard RFC userrsquos profile and must have authorization to access the following function groups BACV BBP_LA_BIZAPI BBP_LA_MAINTENANCE RFC1 SDIFRUNTIME SYST SYSUFor more information about RFC authorization objects see httphelpsapcomnw70
SAP NetWeaver 70 Security Guide Security Guides for Connectivity and Interoperability Technologies
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1430 PUBLIC 2011-11-08
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Property Name DescriptionRFCICF Security Guide RFC Scenarios Security Measure mdash Overview (RFC) RFC
Communication Between SAP Systems Authorizations
NOTE
For 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 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
End of Java |
Only valid for Java |
323 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table
NOTE
You 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
jcoclientmshost
jcoclientgroup
jcoclientr3name
Settings that enable group load balancing
jcoclientashost
jcoclientsysnr
Application server settings without load balancing
End of Java |
Only valid for Java |
324 JCo Pool Settings
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1530
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
RECOMMENDATION
We 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 jcoperformancemonitor and jcopoolmonitor which write the
performance data to the log file for analysis
Property Name Descriptions Recommended Settings
jcopoolmaxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool
CAUTION
Live 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 jcopoolmaxpoolsizeYou have to set this value high enough to handle peak activity loads
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 15
jcopoolmaxpoolsize This value refers to the maximum number of pooled connections kept for reuse
CAUTION
The difference between the value of jcopoolmaxconn and jcopoolmaxpoolsize 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
RECOMMENDATION
For 25 concurrent bidders we recommend setting the value to 10
jcoclientlang This is an optional settingWhen this value is set a JCo pool is created with its value used as the SAP logon languageThe value for this property must be a comma separated list of valid 2-letter SAP external language codes
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codesOn-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
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 connectionsAs 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 adjust the value for jcopoolmaxpoolsize accordingly
End of Java |
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1630 PUBLIC 2011-11-08
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for Java |
325 Other Property Settings for LAC
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC)
Property Name DescriptionDefault Value
msgclientprotocol Overrides the default messaging protocol used by the Live Auction applet This is useful when reverse proxies are used in the system landscapeIf no value is specified the default protocol is used
Empty (no override)
msgclientserverHost 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 landscapeIf no value is specified the default server host name is used
Empty (no override)
msgclientserverPort 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 landscapeIf no value is specified the default server port is used
Empty (no override)
srmlaum Authentication of the User Management Engine (UME)0 = disabled
Empty (enabled)
End of Java |
Only valid for Java |
326 Modifying Properties
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections
JCo Property Settings [page 13]
JCo Client Settings [page 14]
JCo Message Server Client Settings [page 15]
JCo Pool Settings [page 15]
Other Property Settings for LAC [page 17]
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 702)
1 Stop the J2EE server
2 Launch the J2EE engine Configuration Adapter Service
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
2011-11-08 PUBLIC 1730
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
On Windows Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtool
configtoolbat and double-click gobat
On UNIX Go to usrsapltsapsidgtltinstancenumbergtj2eeconfigtoolconfigtoolsh
and run gosh
3 Choose the icon with the quick info text Switch to configuration editor mode
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 702)
1 Verify that the J2EE server is running
2 Launch the J2EE engine Visual Administrator
On Windows Go to ltdrivegtusrsapltsapsidgtltinstance numbergtj2eeadmin and
double-click gobat
On UNIX Go to usrsapltsapsidgtltinstance numbergtj2eeadmin and run gosh
3 Navigate to the Configuration Adapter by choosing Server ltinstance numbergt Services Configuration
Adapter
4 On the Display Configuration tab choose Configurations apps sapcom comsapsrmla appcfg
5 Choose the icon with the quick info text Switch between view and edit mode
6 Double-click Propertysheet applicationglobalproperties
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 Visual Administrator and restart the J2EE server
Modifying Properties with the SAP NetWeaver Administrator (SAP NetWeaver Application Server Java 730)
1 Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
3 Follow-Up Activities
32 Live Auction Properties Overview and Modifications
1830 PUBLIC 2011-11-08
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00
2 Choose Operations Systems Start amp Stop Java Applications
3 Search for and select comsapsrmla
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 applicationEnd of Java |
End of Java |
Only valid for Java |
33 Configuring Single Sign-On for LAC
This 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 702) or in the SAP NetWeaver Administrator (SAP NetWeaver 730)
Prerequisites
You 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 702 You have administrator rights on the SAP J2EE Engine
SAP NW 730 You have administrator rights on the SAP NetWeaver Administrator
Go to the SAP NetWeaver Administrator using the following URL httplthostgtltportgtnwa
lthostgt is the host on which the SAP NetWeaver Application Server Java 730 is installed
ltportgt is the HTTP port of the Internet Communication Manager (ICM) It has the following
format 5ltJava instance numbergt00 For example if the Java instance number is 60 the HTTP
port is 56000
Procedure
1 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
logincreate_sso2_ticket = 1
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2011-11-08 PUBLIC 1930
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
loginaccept_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 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
NOTE
Make 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 ltback-end_namegt-ltclientgtcrt
EXAMPLE
For SAP System EBS client 300 the file name is EBS-300crt
CAUTION
Make sure that Binary is selected under File Format
NOTE
If 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 702 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
4 Choose TicketKeyStore in the View panel
5 Choose Load in the Entry group box
6 Choose the ltback-end_namegt-ltclientgtcrt certificate that was exported from the SAP
SRM system earlier in step 2
The certificate is added to the list in the Entries panel
NOTE
Make 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
3 Follow-Up Activities
33 Configuring Single Sign-On for LAC
2030 PUBLIC 2011-11-08
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
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
NOTE
For each property below n represents the number of the back-end system on
which you want to configure SSO
Property Example Comment
trustedsysn ltback-end_namegt ltclientgt trustedsys1 EBS
300
-
trustedissn ltissuer distinguished namegt trustediss1 CN=EBS The value you define here must be identical to the issuer distinguished name in the certificate of the SAP SRM system
trusteddnn) ltsubject distinguished namegt
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 730 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
For more information about how to configure Single Sign-On see the documentation at
httphelpsapcomnw73 SAP NetWeaver 73 Application Help Function-Oriented View
Security User Authentication and Single Sign-On End of Java |
Only valid for Java |
34 Enabling Auctions
The following sections contain settings to enable auctions in your systems
3 Follow-Up Activities
34 Enabling Auctions
2011-11-08 PUBLIC 2130
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for Java |
341 Creating HTTP Connections to an External Server
You 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
Procedure
1 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 (5ltinstance
numbergt00) For example if during the installation the instance number used was 01 then the port
number is 50100)
NOTE
If 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 serverEnd of Java |
Only valid for Java |
342 Defining a Back-End Destination
Prerequisites
You 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 22]
Procedure
1 In the SAP SRM client start transaction SM31 and enter BBP_BACKEND_DEST in the TableView field
3 Follow-Up Activities
34 Enabling Auctions
2230 PUBLIC 2011-11-08
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
2 Choose Maintain
3 Choose New Entries
4 Select the destination for this SAP SRM client using the Destinations list
NOTE
All previously created HTTP connections for the Live Auction Cockpit are listed here
5 Select SRM_LIVE_AUCTION from the list
6 Save your dataEnd of Java |
Only valid for Java |
343 Defining Number Ranges for Auctions
To enable auctions in the Live Auction Cockpit you must define number ranges
Procedure
1 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 settingsEnd of Java |
End of Java |
Only valid for Java |
35 Copying Customizing Settings from the Default Client
SAP 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
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
Prerequisites
You have configured an RFC connection (Remote Function Call) to client 000 in the SAP SRM system
Procedure
1 Go to transaction SM31 on your LAC client
2 Enter BBPV_LA_PROP in the TableView field
3 Choose Maintain
The Auction Properties Management screen is displayed
4 Choose Utilities Adjustment
3 Follow-Up Activities
35 Copying Customizing Settings from the Default Client
2011-11-08 PUBLIC 2330
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
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 settingsEnd of Java |
Only valid for Java |
36 Server Name and IP Address
You must ensure that the SAP Bidding Engine server can recognize the Live Auction Cockpit (LAC)
server
Integration
Make sure that the Live Auction Cockpit server name and IP address is entered in the hosts file of the
SAP Bidding Engine server
EXAMPLE
The IP address and LAC server name looks similar to this example
104882200la_serveryourcorp
You can find and check the hosts file at cWINNTSystem32driversltgt
CAUTION
Confirm 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
End of Java |
3 Follow-Up Activities
36 Server Name and IP Address
2430 PUBLIC 2011-11-08
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Only valid for Java |
37 LAC Smoke Tests
The 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 |
371 Smoke Testing User Management
The following smoke tests are available for the SAP User Management Engine (UME)
2 automatic system smoke tests
2 manual smoke tests
These 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
ltj2ee_hostdomaingtltdefault_port~50000gtsrmla
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 must solve errors
in the order they are presented on the smoke test page
UME Smoke Test Processes
The 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 JCoRFC 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
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
Prerequisites
The automatic system smoke test has verified that the J2EE server is configured to use an ABAP back
end as the UME data source
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2530
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Procedure
You 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 pageEnd of Java |
Only valid for Java |
372 Smoke Testing the LAC Applet
The following smoke tests are available for the Live Auction Cockpit (LAC)
3 automatic system smoke tests
1 manual smoke test
These 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 httpltj2ee_hostdomaingtdefault_port~50000srmla
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
LAC Smoke Test Processes
The 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
3 Follow-Up Activities
37 LAC Smoke Tests
2630 PUBLIC 2011-11-08
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
NOTE
If 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
Prerequisites
The three automatic smoke tests have verified the correct deployment of the respective LAC JAR files
Procedure
Start 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
NOTE
If 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 ABAPJava |
3 Follow-Up Activities
37 LAC Smoke Tests
2011-11-08 PUBLIC 2730
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom 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
2830 PUBLIC 2011-11-08
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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 AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle and Java are registered trademarks of OracleUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologySAP R3 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 countriesBusiness 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 companySybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-11-08 PUBLIC 2930
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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 AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
