sap supplier relationship management 7.0 including sap
TRANSCRIPT
SAP Supplier Relationship Management 7.0 Including SAP Enhancement
Package 1Upgrade Guide SAP Supplier Relationship Management 7.0
Including SAP Enhancement Package 1 Using the SAP Enhancement
Package Installer (SAPehpi)
For: Java UNIX
PUBLIC Document version: 1.0 – 2010-07-12
SAP AG Dietmar-Hopp-Allee 16
T +49/18 05/34 34 34 F +49/18 05/34 34 20
www.sap.com
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
2/28 PUBLIC 2010-07-12
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gSOAP
Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides
2010-07-12 PUBLIC 3/28
This guide was generated according to the following criteria:
SAP Component
Usage Type / Software Unit
NetWeaver BI Java Components (BI-Java)
NetWeaver Enterprise Portal (EP)
NetWeaver EP Core (EPC)
Typographic Conventions
Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.
Example Example
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.
Cross-references to other documentation or published works
Example Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2010-07-12 PUBLIC 5/28
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version on SAP Service Marketplace http://service.sap.com/
instguides.
The following table provides an overview on the most important document changes:
Version Date Description
1.2 Accessing the SAP Enhancement Package Installer (SAPehpi)
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Upgrade in an SAP System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.4 Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 4 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1 Synchronized Upgrade of Dual-Stack Systems . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 5 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1 Updating Dialog Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.1 Smoke Test (User Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.1.1 Verifying the UM Logon Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.1.2 Verifying the SSO Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.2 Smoke Test (Applet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.2.1 Verifying the Live Auction Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4 Migrating Data from Your Existing Live Auction Cockpit . . . . . . . . . . . . . . . . 24
5.5 Migrating Resource Customizations from Your Existing Live Auction
Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2010-07-12 PUBLIC 7/28
This page is left blank for documents that are printed on both sides.
1 Introduction
NOTE
This upgrade guide only applies if you are performing an upgrade of one of the following SAP
SRM Java systems based on SAP NetWeaver 7.0:
SAP SRM 5.0
SAP SRM 2007
1.1 About This Document
This document describes the upgrade to SAP SRM Live Auction Cockpit 7.01 (SAP SRM LAC 7.01)
based on SAP NetWeaver 7.0 including EHP 2. You perform the upgrade using the SAP Enhancement
Package Installer (SAPehpi).
This upgrade guide only contains the SAP SRM specific information needed for the upgrade. For more
information about SAPehpi and the steps you have to perform to upgrade your system, see the
document Installation Guide — SAP Enhancement Package Installation Using SAP Enhancement Package Installer
(SAPehpi) [page 10]. You have to use both guides in parallel.
This document also contains information about the upgrade to SAP NetWeaver 7.0 Application Server
Java including enhancement package 1, and information about the upgrade of the following software
units that are possibly installed in your system:
Business Intelligence Java Components (BI-Java)
Enterprise Portal (EP)
EP Core (EPC)
Prerequisites
Make sure you read the corresponding Master Guide for SAP SRM 7.0 including SAP enhancement
package 1 before you start with this upgrade guide. The Master Guide is available at the following
location: http://service.sap.com/srm-inst SAP SRM Server 7.01
Constraints
You need to consider the following constraints before you start the upgrade process:
SAPehpi can be used only for an upgrade of source release systems based on SAP NetWeaver 7.0. If
you want to upgrade SAP SRM 4.0 to SAP SRM 7.0 including SAP enhancement package 1, you
must use SAPJup, as described in the document Upgrade Guide SAP Supplier Relationship Management 7.0
1 Introduction
srm-inst SAP SRM Server 7.01 Upgrade Guides — SAP SRM 7.0 EHP1
This upgrade procedure does not include the upgrade of business packages for SAP SRM. For
information on upgrading the business packages, see SAP Solution Manager under <project name>
Configuration SAP SRM 7.0 EHP1 Basic Settings for SAP SRM Business Package for SAP SRM .
For general information on upgrading portal content, see the SAP NetWeaver 7.0 Upgrade Master
Guide on SAP Service Marketplace at http://service.sap.com/instguidesNW70 Upgrade
Upgrade Master Guide .
SAP Notes
You must read the following SAP Notes before you start the upgrade. These SAP Notes contain the
most recent information on the upgrade, as well as corrections to the upgrade documentation. Make
sure that you have the up-to-date version of each SAP Note, which you can find at http://
service.sap.com/notes.
SAP Note Number Description Area
1267573 Central Note: Upgrade to systems based on SAP NetWeaver 7.0 including enhancement package 2 Java
Specific to this upgrade
The references to the SAP Enhancement Package Installer (SAPehpi) documentation in this upgrade
guide always refer to the following on the SAP Service Marketplace portal:
http://service.sap.com/crm-inst SAP enhancement package 1 for SAP CRM 7.0 Install Enhancement
Package Installation on Existing SAP Systems SAP Enhancement Package Installation for Java Systems (using SAP
Enhancement Package Installer) <Operating System>
1 Introduction
10/28 PUBLIC 2010-07-12
This part of the document contains information about planning your upgrade. Before you begin the
actual upgrade, you must first plan it carefully, since careful planning is a prerequisite for a successful
SAP system upgrade. This includes requesting all the SAP Notes you need. The following information
helps you plan your upgrade so that downtime is reduced to a minimum and the upgrade runs as
efficiently as possible.
CAUTION
For more information about the planning steps you have to perform before running the SAPehpi,
see the document Installation Guide — SAP Enhancement Package Installation Using SAP Enhancement Package
Installer (SAPehpi) [page 10], section Planning.
2.1 Checking the Source Release
Before the upgrade, your SAP system must have a source release that has been released for this upgrade.
For more information, see Quick Guide [external document].
Procedure
To determine the source release and Support Package level, proceed as follows:
1. Go to the J2EE Engine Start Page: http://<host name>:<port>/index.html
2. Choose System Information.
3. Log on to the J2EE Engine:
If you have a standalone installation, log on as user Administrator.
If you have an add-in installation, log on as user J2EE_Admin.
The source release and Support Package level are then displayed under Version in the Software
Components table.
2.2 Upgrade in an SAP System Group
If you have more than one SAP system, for example, a production system and a development system,
you must consider the entire system group.
Upgrade your systems in the same sequence in which you transport your modifications.
2 Planning
2010-07-12 PUBLIC 11/28
Process
If you have a development system and a production system, upgrade the systems as follows:
1. Development system
2. Production system
If your system group consists of three SAP systems and includes a quality assurance system that
has been set up between the development and production system, work in the following order:
1. Development system
3. Production system
If you have made modifications to SAP objects that you want to retain, you must proceed in the above
sequence. The version management functions of the SAP system record all the changes you make only
in the system in which you made the modifications (the development system). Only this SAP system
offers you optimal support when you adjust modifications.
Changes made in the development system after the upgrade can be transported automatically to your
other SAP systems. If you use this procedure, you no longer need to perform time-consuming
adjustments in the production system.
CAUTION
If you have modified SAP objects, make sure that you keep your development system. Do not
copy your production system to your development system for test purposes.
For test purposes with realistic production data, set up a quality assurance system between the
development system and production system. This system can be a copy of the production system.
2 Planning
12/28 PUBLIC 2010-07-12
3 Preparation
This part of the document contains information about the preparations that you need to make before
you upgrade your system.
CAUTION
For more information about the preparation steps you have to perform before running the
SAPehpi, see the document Installation Guide — SAP Enhancement Package Installation Using SAP
Enhancement Package Installer (SAPehpi) [page 10], section Preparation.
3.1 Preparing SAP Solution Manager
The SAP Solution Manager Maintenance Optimizer plays a central role in the upgrade process. It is
mandatory to use SAP Solution Manager Maintenance Optimizer for the calculation of the required
upgrade packages, enhancement packages and Support Package stacks and for the creation of the stack
configuration file (xml file). The upgrade program reads this stack configuration file and uses it as an
input file for the upgrade.
The following sections explain how you have to prepare SAP Solution Manager and the Maintenance
Optimizer.
3.1.1 SAP Solution Manager Update
You require at least SAP Solution Manager 7.0 EHP1 Support Package Stack 23 and the implementation
content ST-ICO 150_700 SP 25. Note that ST-ICO 150_700 SP 25 is not included in the Support Package
Stack 23, that is, you have to download it separately.
We recommend that you always update your SAP Solution Manager to the latest Support Package
Stack.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of
SAP Solution Manager and that it completes successfully.
Related Documents Available at...
Upgrade Guide – SAP Solution Manager 7.0 incl. Enhancement Package 1 Describes the upgrade from source releases SAP Solution Manager 3.1 and 3.2. You can include the installation of the required Support Package stack in the upgrade procedure.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -
3 Preparation
2010-07-12 PUBLIC 13/28
Related Documents Available at...
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 Describes the update from source releases SAP Solution Manager 7.0. You can include the installation of the required Support Package stack in the update procedure.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -
Solution Operations Guide – SAP Solution Manager 7.0 EHP1, section Software Change Management Describes the actions required after the update to SAP Solution Manager 7.0 EHP1.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution Manager
Landscape verification 1.0 is an add-on to your SAP Solution Manager system. It supports you in
maintaining your system landscape data. The use of this tool is optional.
For information about the installation, see SAP Note 1468605.
3.1.3 Configuration of the Maintenance Optimizer
If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks,
see the Maintenance Optimizer Configuration Guide.
In any case, check SAP Note 1436297 Maintenance Optimizer: Notes for Enhancement Packages whether it contains
any corrections for the SAP Solution Manager 7.0 Support Package level you are using.
Related Documents Available at...
3.1.4 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape.
Therefore, it is crucial that this data is correctly maintained in SAP Solution Manager’s system landscape
(transaction SMSY). If you have already maintained the system landscape data, check carefully if this
data is correct.
Proceed in the following order:
1. If you have not already done so, capture the system data using the System Landscape Directory
(SLD).
2. Optional: Run the landscape verification 1.0 to check the system landscape data.
3. Maintain the system data in SAP Solution Manager.
3 Preparation
14/28 PUBLIC 2010-07-12
Capturing System Data Using SLD
1. Register all systems that you want to update in your central SLD. In case of a dual stack system,
you have to register both the ABAP stack and the Java stack.
The central SLD can either be the SLD of your SAP Solution Manager system, or you can have a
separate system where you run the SLD (a central runtime SLD). If you use a central runtime SLD,
make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
To register Java systems, you use the Visual Administrator. To register the ABAP system you use
transaction RZ70.
NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Software Life Cycle Management
System Landscape Directory Configuring Systems to Connect to SLD
For more information about the SLD synchronization, see the Planning Guide – System Landscape
Directory available at http://sdn.sap.com/irj/sdn/nw-sld.
If the registration was successful, both the ABAP system and the Java system appear in the SLD
under Technical Systems.
2. To transfer the data from the SLD to the SAP Solution Manager system landscape, schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP.
For more information, see the SAP Solution Manager Library at http://help.sap.com SAP
Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape .
Running the Landscape Verification 1.0
Running the landscape verification 1.0 is an optional step. This tool checks how your systems are
maintained in the SAP Solution Manager system. If it detects any inconsistencies, you are prompted to
correct existing entries or enter missing data. The tool provides you with information how to maintain
the data.
3 Preparation
2010-07-12 PUBLIC 15/28
To start the landscape verification, call transaction LVSM in SAP Solution Manager.
For more information about the landscape verification, choose the Help link from within the
application.
Maintaining System Data
When your product systems are known in SAP Solution Manager, you have to check and maintain the
system data, add your system to a logical component and to a solution.
1. In transaction SMSY, choose Landscape Components Product System <System> .
2. Check whether the product version is correct. The product version is displayed in the right pane
below the name of your system.
3. Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant. Make sure that no instance is marked as relevant that is not installed in your
system, as this would lead to the installation of unwanted software components in your system.
NOTE
You can only select one ABAP instance as relevant. You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance.
For more information about selecting the instances and required settings, see SAP Note 1344564 -
Maintenance Optimizer: Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY.
4. Java–based systems connected to SAP Business Suite Application ABAP Systems: Checking the
Landscape Patterns
Make sure that you have correctly modeled the connected Java systems as hub systems or sidecar
systems. A sidecar system is a system that is used by only one SAP Business Suite product (for example
an SAP Netweaver 7.0 Portal or Business Intelligence system used exclusively by one SAP ERP 6.0
3 Preparation
16/28 PUBLIC 2010-07-12
implications for the Maintenance Optimizer’s update strategy for your landscape: A sidecar system
only receives updates along with its associated SAP Business Suite system, whereas you can update
a hub system independently. However, the SAP Business suite software that is installed on the hub
system (for example, SAP XSS on an SAP NetWeaver Portal) is updated along with its associated
SAP Business Suite system.
For more information, see the document SAP Business Suite 7 i2010 Landscape Implementation – Technical
Planning Guide.
To check the landscape pattern of the connected Java systems, proceed as follows:
1. Log on to SAP Solution Manager and call transaction SMSY.
2. Choose Landscape Components Product Systems <System>
3. On the Product Instance Selection tab, double-click on the relevant Java product instances and
choose the Other Attributes tab.
4. Select the appropriate landscape pattern.
5. Creating the logical component
1. In transaction SMSY, choose System Groups and Logical Components
2. In the context menu of Logical Components choose Create New Logical Component.
3. Enter your system data.
The name of your logical component must start with “Z...”.
6. Assigning the system to the logical component
In the Current System Assignments of the newly created logical component, add your systems with the
appropriate roles (such as Development System or Production System).
RECOMMENDATION
We recommend adding all systems of one product to one logical component. This means
that you create one logical component and add the development system, the quality
assurance system, and the production system to the same logical component.
7. Optional: Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution.
However, if you already have a solution, then add your product system to it. When you later create
a maintenance transaction, you can select this solution and thus restrict the number of product
systems displayed.
1. Call transaction solution_manager and create a solution, if it does not yet exist.
2. Choose Solution Landscape and Solution Landscape Maintenance.
3. Add your SAP system to the solution as follows:
1. Change to edit mode.
2. Place the cursor on a new line in the Logical Component column.
3. Use the input help to select your system from the list (product, logical component).
4. Choose Complete System Data Replication.
3 Preparation
2010-07-12 PUBLIC 17/28
18/28 PUBLIC 2010-07-12
4 Upgrade Process
This section describes the upgrade process of SAP SRM Java systems as well as the synchronization steps
required for the upgrade of SRM dual-stack systems.
4.1 Synchronized Upgrade of Dual-Stack Systems
If you run an ABAP-based server and a Java-based server in the same SAP system, you must upgrade
them in parallel. The upgrade of these systems requires you to use the SAP Enhancement Package
Installer (SAPehpi) for the Java part and SAPup for the ABAP part. This procedure explains how to
perform a synchronized upgrade with these two tools.
Procedure
1. Start SAPup as usual using the STARTUP script.
2. Wait until the configuration roadmap step of the ABAP server upgrade is completed.
3. Download the latest SAPehpi from SAP Service Marketplace and unpack it.
4. Start SAPehpi with the following command:
Windows:
('jce_policy_zip=/<path_to_policy_files>>/SAPJVM5_crypto.zip' '-srvarg=/
5. Run both upgrades in parallel.
The ABAP upgrade uses the standard http server with the port number 4239 (http://<host name>:
4239). The Java upgrade uses the http server with the port number 7239 (http://<host name>:
7239)
2010-07-12 PUBLIC 19/28
This page is left blank for documents that are printed on both sides.
5 Follow-Up Activities
CAUTION
For more information about the follow-up activities that you have to perform after you have
upgraded your system, see the Installation Guide — SAP Enhancement Package Installation Using SAP
Enhancement Package Installer (SAPehpi) [page 10], section Follow-Up Activities.
5.1 Updating Dialog Instances
When you install new dialog instances, make sure that you use the correct installation DVDs.
The DVDs that you use for installing dialog instances have to correspond to the SAP NetWeaver release
and enhancement package level that is underlying your SAP Business Suite application system on the
central instance. So, if you have only updated the Business Suite application without the underlying
SAP NetWeaver, you have to use the installation DVDs that match the release and enhancement
package level of SAP NetWeaver. Using the SAP Business Suite 7 i2010 installation DVDs would lead to
problems due to changes in the kernel structure.
5.2 Changing Passwords
As of SAP NetWeaver 7.0 Support Package 03, new security policies apply. You have to change passwords
if:
Your passwords are older than 90 days.
Your passwords do not contain between 6 and 12 characters and do not consist of both letters and
numerals.
Your password contains a user name.
When you create a new password, you are not allowed to duplicate the old password.
If you change the J2EE engine administrator password, you have to make sure that external tools (for
example, SDM and JSPM) can read the password. These tools read the J2EE Engine administrator
password from the secure store. Since the secure store is not automatically updated, you have to do
this manually. Proceed as follows:
1. Select secure store.
2. Select the admin/password/<SAPSID> entry.
3. In the Value field, enter the new password for the J2EE Engine administrator and choose Add.
4. To save the data, choose File Apply .
5 Follow-Up Activities
Only valid for: SAP SRM Server;SRM Live Auction Cockpit (SRMLAC) |
5.3 Live Auction Cockpit Smoke Test
Launch the Live Auction Cockpit Smoke Test in your web browser to check that implementation was
successful.
General Information
Contains information about the Live Auction build as well as the J2EE server.
Smoke Test (User Management) [page 22]
Smoke Test (Applet) [page 0 ]
The Live Auction Cockpit Smoke Test resides on the J2EE server and has a URL similar to the following:
http://<j2ee_host.domain>:<default_port~50000>/srm/la.
5.3.1 Smoke Test (User Management)
The Smoke Test (User Management) tab contains 4 smoke tests – 2 self-diagnoses and 2 manual
diagnoses – that verify the correctness of the User Management configuration as well as the JCo/RFC
configuration on the current J2EE server. All self-diagnoses are run automatically when the page loads.
If a self-diagnosis runs error-free, the result is displayed in green. If a self-diagnosis fails, the result is
displayed in red. The J2EE's log and trace files display more information about an error after the result
has been displayed. Try to resolve any failures, in the order they are presented on the page.
Process
The system verifies that the J2EE server is configured to use an ABAP back end as the UME data
store.
You verify that the UM logon page is working properly and that it is using the correct ABAP back
end for user authentication.
You verify that the single sign-on ticket issuing system is generating an SSO ticket that is compatible
with the current J2EE server.
The system verifies that the JCo/RFC connection to the SRM server is working properly.
5.3.1.1 Verifying the UM Logon Page
Prerequisites
The system verifies that the J2EE server is configured to use an ABAP back end as the UME data source.
5 Follow-Up Activities
22/28 PUBLIC 2010-07-12
Procedure
1. Choose UME user admin and log on to the SAP SRM server to which the current J2EE server is
connected.
If the user authentication is successful, you see the user details screen on the UME administration
page.
Prerequisites
You have verified that the UM logon page is working properly and that it is using the correct ABAP
back-end for user authentication.
Procedure
1. Enter the URL for the ticket issuing system and choose Logon.
When the logon screen is displayed, log on with an SAP SRM user.
2. Once you have logged on successfully, close the browser window.
3. Return to the smoke test and refresh the page.
The ticket information as well as the status of the JCo RFC connection is displayed at the bottom
of the page.
5.3.2 Smoke Test (Applet)
The Smoke Test (Applet) tab contains 4 smoke tests – 3 self-diagnoses and 1 manual diagnosis – to
verify the deployments of the Live Auction Java applets and resource bundles.
All self-diagnoses are run automatically when the page loads. If a self-diagnosis runs error-free, the
result is displayed in green. If a self-diagnosis fails, the result is displayed in red. Try to resolve any
failures, in the order that they are presented on the page.
Process
The system verifies that the initiator applet JAR file of Live Auction is deployed properly.
The system verifies that the respondent applet JAR file of Live Auction is deployed properly.
The system verifies that the client resources JAR file of Live Auction is deployed properly.
NOTE
If you want to download the JAR file for further analysis after any of the steps above, click the
Download button.
You verify that the Live Auction applet settings are correctly configured and that the applet can
be launched.
2010-07-12 PUBLIC 23/28
Prerequisites
The system has verified the successful deployment of the following:
Live Auction initiator applet JAR file
Live Auction respondent applet JAR file
Live Auction client resources JAR file
Procedure
NOTE
The input fields displayed in this test are optional.
If the applet settings are configured properly and the applet can be launched, you see the applet's
splash screen.
NOTE
If you know the GUID of a valid auction on the SAP SRM server and want to view the auction
in the applet, enter all the necessary information in the input fields and then choose Test. End of: SAP SRM Server;SRM Live Auction Cockpit (SRMLAC) |
Only valid for: SRM Live Auction Cockpit (SRMLAC) |
5.4 Migrating Data from Your Existing Live Auction Cockpit
After the upgrade, you need to migrate auction data and update the database to initialize new database
fields in SAP SRM LAC 7.0. To do so, you must manually execute two post-upgrade reports. If you have
a lot of existing auction data in your system, we recommend scheduling a background job to run these
reports in order to avoid time-outs.
NOTE
Before performing post-upgrade activities, ensure that the JCo RFC user has S_RFC authorization.
Procedure
1. In the SAP SRM system, go to transaction SE38.
2. Execute report BBP_LA_DATA_MIGRATION.
BBP_Z090_XPRA_AUCTIONS_XPRA550.
Result
Any data from your existing Live Auction Cockpit is migrated. You can launch the application and
process auctions. End of: SRM Live Auction Cockpit (SRMLAC) |
5 Follow-Up Activities
24/28 PUBLIC 2010-07-12
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
Your SAP SRM Live Auction Cockpit (LAC) 7.0 system includes application properties preserved during
the upgrade process; however, it does not reflect any resource setting customizations that you may
have performed in your existing SAP SRM LAC system.
RECOMMENDATION
Before copying any customizations from your existing SAP SRM LAC system to your SAP SRM
LAC 7.0 system, launch SAP SRM LAC 7.0 to determine if those changes are still required.
CAUTION
Due to the unknown number and types of customizations in your existing system, the following
is intended as a reference guide rather than an exact procedure for migrating those customizations.
Procedure
RECOMMENDATION
To avoid overwriting your modifications whenever a patch is deployed, always create your own
resource files rather than replacing or modifying those shipped with SAP SRM LAC.
1. Once you have determined that you need to copy customizations from your existing SAP SRM
LAC system to SAP SRM LAC 7.0, identify what changes were made in your existing SAP SRM LAC
system and where they were made in the resource files. For more information, see Determining Existing
Customizations [external document].
Image Files
A number of image files that were used in previous versions of SAP SRM LAC have been
renamed or removed in SAP SRM LAC 7.0. Review your customized images and see if they are
affected.
There are also several new image files in SAP SRM LAC 7.0; you may wish to review those as
well.
For more information, see SAP Solution Manager; navigate to the configuration structure for
SAP SRM and choose Basic Settings for Strategic Sourcing Sourcing with RFx and Auction Settings for
Auction Configuring the Live Auction Cockpit User Interface .
Resource Bundles
A number of resource bundles that were used in previous versions of SAP SRM LAC have been
renamed or removed in SAP SRM LAC 7.0. Please review your customized resource bundles
to see if they are affected.
5 Follow-Up Activities
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
2010-07-12 PUBLIC 25/28
If you plan to carry over customized resource texts, make sure that the file names and the
resource keys of the original resource bundle files are unchanged.
Store all your customized resource files under:
<INSTDIR>:/usr/sap/<SAPSID>/SYS/global/srmla/resources
2. Adjust the values of the following properties to either 1 or 2 so that your customized files will be
used by SAP SRM LAC 7.0:
applet.initiator.archive
applet.respondent.archive
applet.archive.selection
For more information, see SAP Solution Manager; navigate to the configuration structure for SAP
SRM and choose Basic Settings for Strategic Sourcing Sourcing with RFx and Auction Settings for
Auction , and see:
Configuring the Live Auction Cockpit User Interface
Managing Live Auction Cockpit Properties End of: SRM Live Auction Cockpit (SRMLAC) |
5 Follow-Up Activities
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
26/28 PUBLIC 2010-07-12
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
© Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
SAP Supplier Relationship Management 7.0 Including SAP Enhancement Package 1
Table of Contents
2 Planning
2.2 Upgrade in an SAP System Group
3 Preparation
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution Manager
3.1.3 Configuration of the Maintenance Optimizer
3.1.4 Maintaining System Landscape Information
4 Upgrade Process
5 Follow-Up Activities
5.3.1 Smoke Test (User Management)
5.3.1.1 Verifying the UM Logon Page
5.3.1.2 Verifying the SSO Ticket
5.3.2 Smoke Test (Applet)
5.4 Migrating Data from Your Existing Live Auction Cockpit
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
Copyright and trademarks
For: Java UNIX
PUBLIC Document version: 1.0 – 2010-07-12
SAP AG Dietmar-Hopp-Allee 16
T +49/18 05/34 34 34 F +49/18 05/34 34 20
www.sap.com
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
2/28 PUBLIC 2010-07-12
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gSOAP
Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides
2010-07-12 PUBLIC 3/28
This guide was generated according to the following criteria:
SAP Component
Usage Type / Software Unit
NetWeaver BI Java Components (BI-Java)
NetWeaver Enterprise Portal (EP)
NetWeaver EP Core (EPC)
Typographic Conventions
Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.
Example Example
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.
Cross-references to other documentation or published works
Example Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2010-07-12 PUBLIC 5/28
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version on SAP Service Marketplace http://service.sap.com/
instguides.
The following table provides an overview on the most important document changes:
Version Date Description
1.2 Accessing the SAP Enhancement Package Installer (SAPehpi)
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Upgrade in an SAP System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.4 Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 4 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1 Synchronized Upgrade of Dual-Stack Systems . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 5 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1 Updating Dialog Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.1 Smoke Test (User Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.1.1 Verifying the UM Logon Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.1.2 Verifying the SSO Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.2 Smoke Test (Applet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.2.1 Verifying the Live Auction Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4 Migrating Data from Your Existing Live Auction Cockpit . . . . . . . . . . . . . . . . 24
5.5 Migrating Resource Customizations from Your Existing Live Auction
Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2010-07-12 PUBLIC 7/28
This page is left blank for documents that are printed on both sides.
1 Introduction
NOTE
This upgrade guide only applies if you are performing an upgrade of one of the following SAP
SRM Java systems based on SAP NetWeaver 7.0:
SAP SRM 5.0
SAP SRM 2007
1.1 About This Document
This document describes the upgrade to SAP SRM Live Auction Cockpit 7.01 (SAP SRM LAC 7.01)
based on SAP NetWeaver 7.0 including EHP 2. You perform the upgrade using the SAP Enhancement
Package Installer (SAPehpi).
This upgrade guide only contains the SAP SRM specific information needed for the upgrade. For more
information about SAPehpi and the steps you have to perform to upgrade your system, see the
document Installation Guide — SAP Enhancement Package Installation Using SAP Enhancement Package Installer
(SAPehpi) [page 10]. You have to use both guides in parallel.
This document also contains information about the upgrade to SAP NetWeaver 7.0 Application Server
Java including enhancement package 1, and information about the upgrade of the following software
units that are possibly installed in your system:
Business Intelligence Java Components (BI-Java)
Enterprise Portal (EP)
EP Core (EPC)
Prerequisites
Make sure you read the corresponding Master Guide for SAP SRM 7.0 including SAP enhancement
package 1 before you start with this upgrade guide. The Master Guide is available at the following
location: http://service.sap.com/srm-inst SAP SRM Server 7.01
Constraints
You need to consider the following constraints before you start the upgrade process:
SAPehpi can be used only for an upgrade of source release systems based on SAP NetWeaver 7.0. If
you want to upgrade SAP SRM 4.0 to SAP SRM 7.0 including SAP enhancement package 1, you
must use SAPJup, as described in the document Upgrade Guide SAP Supplier Relationship Management 7.0
1 Introduction
srm-inst SAP SRM Server 7.01 Upgrade Guides — SAP SRM 7.0 EHP1
This upgrade procedure does not include the upgrade of business packages for SAP SRM. For
information on upgrading the business packages, see SAP Solution Manager under <project name>
Configuration SAP SRM 7.0 EHP1 Basic Settings for SAP SRM Business Package for SAP SRM .
For general information on upgrading portal content, see the SAP NetWeaver 7.0 Upgrade Master
Guide on SAP Service Marketplace at http://service.sap.com/instguidesNW70 Upgrade
Upgrade Master Guide .
SAP Notes
You must read the following SAP Notes before you start the upgrade. These SAP Notes contain the
most recent information on the upgrade, as well as corrections to the upgrade documentation. Make
sure that you have the up-to-date version of each SAP Note, which you can find at http://
service.sap.com/notes.
SAP Note Number Description Area
1267573 Central Note: Upgrade to systems based on SAP NetWeaver 7.0 including enhancement package 2 Java
Specific to this upgrade
The references to the SAP Enhancement Package Installer (SAPehpi) documentation in this upgrade
guide always refer to the following on the SAP Service Marketplace portal:
http://service.sap.com/crm-inst SAP enhancement package 1 for SAP CRM 7.0 Install Enhancement
Package Installation on Existing SAP Systems SAP Enhancement Package Installation for Java Systems (using SAP
Enhancement Package Installer) <Operating System>
1 Introduction
10/28 PUBLIC 2010-07-12
This part of the document contains information about planning your upgrade. Before you begin the
actual upgrade, you must first plan it carefully, since careful planning is a prerequisite for a successful
SAP system upgrade. This includes requesting all the SAP Notes you need. The following information
helps you plan your upgrade so that downtime is reduced to a minimum and the upgrade runs as
efficiently as possible.
CAUTION
For more information about the planning steps you have to perform before running the SAPehpi,
see the document Installation Guide — SAP Enhancement Package Installation Using SAP Enhancement Package
Installer (SAPehpi) [page 10], section Planning.
2.1 Checking the Source Release
Before the upgrade, your SAP system must have a source release that has been released for this upgrade.
For more information, see Quick Guide [external document].
Procedure
To determine the source release and Support Package level, proceed as follows:
1. Go to the J2EE Engine Start Page: http://<host name>:<port>/index.html
2. Choose System Information.
3. Log on to the J2EE Engine:
If you have a standalone installation, log on as user Administrator.
If you have an add-in installation, log on as user J2EE_Admin.
The source release and Support Package level are then displayed under Version in the Software
Components table.
2.2 Upgrade in an SAP System Group
If you have more than one SAP system, for example, a production system and a development system,
you must consider the entire system group.
Upgrade your systems in the same sequence in which you transport your modifications.
2 Planning
2010-07-12 PUBLIC 11/28
Process
If you have a development system and a production system, upgrade the systems as follows:
1. Development system
2. Production system
If your system group consists of three SAP systems and includes a quality assurance system that
has been set up between the development and production system, work in the following order:
1. Development system
3. Production system
If you have made modifications to SAP objects that you want to retain, you must proceed in the above
sequence. The version management functions of the SAP system record all the changes you make only
in the system in which you made the modifications (the development system). Only this SAP system
offers you optimal support when you adjust modifications.
Changes made in the development system after the upgrade can be transported automatically to your
other SAP systems. If you use this procedure, you no longer need to perform time-consuming
adjustments in the production system.
CAUTION
If you have modified SAP objects, make sure that you keep your development system. Do not
copy your production system to your development system for test purposes.
For test purposes with realistic production data, set up a quality assurance system between the
development system and production system. This system can be a copy of the production system.
2 Planning
12/28 PUBLIC 2010-07-12
3 Preparation
This part of the document contains information about the preparations that you need to make before
you upgrade your system.
CAUTION
For more information about the preparation steps you have to perform before running the
SAPehpi, see the document Installation Guide — SAP Enhancement Package Installation Using SAP
Enhancement Package Installer (SAPehpi) [page 10], section Preparation.
3.1 Preparing SAP Solution Manager
The SAP Solution Manager Maintenance Optimizer plays a central role in the upgrade process. It is
mandatory to use SAP Solution Manager Maintenance Optimizer for the calculation of the required
upgrade packages, enhancement packages and Support Package stacks and for the creation of the stack
configuration file (xml file). The upgrade program reads this stack configuration file and uses it as an
input file for the upgrade.
The following sections explain how you have to prepare SAP Solution Manager and the Maintenance
Optimizer.
3.1.1 SAP Solution Manager Update
You require at least SAP Solution Manager 7.0 EHP1 Support Package Stack 23 and the implementation
content ST-ICO 150_700 SP 25. Note that ST-ICO 150_700 SP 25 is not included in the Support Package
Stack 23, that is, you have to download it separately.
We recommend that you always update your SAP Solution Manager to the latest Support Package
Stack.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of
SAP Solution Manager and that it completes successfully.
Related Documents Available at...
Upgrade Guide – SAP Solution Manager 7.0 incl. Enhancement Package 1 Describes the upgrade from source releases SAP Solution Manager 3.1 and 3.2. You can include the installation of the required Support Package stack in the upgrade procedure.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -
3 Preparation
2010-07-12 PUBLIC 13/28
Related Documents Available at...
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 Describes the update from source releases SAP Solution Manager 7.0. You can include the installation of the required Support Package stack in the update procedure.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1 -
Solution Operations Guide – SAP Solution Manager 7.0 EHP1, section Software Change Management Describes the actions required after the update to SAP Solution Manager 7.0 EHP1.
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution Manager
Landscape verification 1.0 is an add-on to your SAP Solution Manager system. It supports you in
maintaining your system landscape data. The use of this tool is optional.
For information about the installation, see SAP Note 1468605.
3.1.3 Configuration of the Maintenance Optimizer
If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks,
see the Maintenance Optimizer Configuration Guide.
In any case, check SAP Note 1436297 Maintenance Optimizer: Notes for Enhancement Packages whether it contains
any corrections for the SAP Solution Manager 7.0 Support Package level you are using.
Related Documents Available at...
3.1.4 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape.
Therefore, it is crucial that this data is correctly maintained in SAP Solution Manager’s system landscape
(transaction SMSY). If you have already maintained the system landscape data, check carefully if this
data is correct.
Proceed in the following order:
1. If you have not already done so, capture the system data using the System Landscape Directory
(SLD).
2. Optional: Run the landscape verification 1.0 to check the system landscape data.
3. Maintain the system data in SAP Solution Manager.
3 Preparation
14/28 PUBLIC 2010-07-12
Capturing System Data Using SLD
1. Register all systems that you want to update in your central SLD. In case of a dual stack system,
you have to register both the ABAP stack and the Java stack.
The central SLD can either be the SLD of your SAP Solution Manager system, or you can have a
separate system where you run the SLD (a central runtime SLD). If you use a central runtime SLD,
make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
To register Java systems, you use the Visual Administrator. To register the ABAP system you use
transaction RZ70.
NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Software Life Cycle Management
System Landscape Directory Configuring Systems to Connect to SLD
For more information about the SLD synchronization, see the Planning Guide – System Landscape
Directory available at http://sdn.sap.com/irj/sdn/nw-sld.
If the registration was successful, both the ABAP system and the Java system appear in the SLD
under Technical Systems.
2. To transfer the data from the SLD to the SAP Solution Manager system landscape, schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP.
For more information, see the SAP Solution Manager Library at http://help.sap.com SAP
Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape .
Running the Landscape Verification 1.0
Running the landscape verification 1.0 is an optional step. This tool checks how your systems are
maintained in the SAP Solution Manager system. If it detects any inconsistencies, you are prompted to
correct existing entries or enter missing data. The tool provides you with information how to maintain
the data.
3 Preparation
2010-07-12 PUBLIC 15/28
To start the landscape verification, call transaction LVSM in SAP Solution Manager.
For more information about the landscape verification, choose the Help link from within the
application.
Maintaining System Data
When your product systems are known in SAP Solution Manager, you have to check and maintain the
system data, add your system to a logical component and to a solution.
1. In transaction SMSY, choose Landscape Components Product System <System> .
2. Check whether the product version is correct. The product version is displayed in the right pane
below the name of your system.
3. Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant. Make sure that no instance is marked as relevant that is not installed in your
system, as this would lead to the installation of unwanted software components in your system.
NOTE
You can only select one ABAP instance as relevant. You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance.
For more information about selecting the instances and required settings, see SAP Note 1344564 -
Maintenance Optimizer: Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY.
4. Java–based systems connected to SAP Business Suite Application ABAP Systems: Checking the
Landscape Patterns
Make sure that you have correctly modeled the connected Java systems as hub systems or sidecar
systems. A sidecar system is a system that is used by only one SAP Business Suite product (for example
an SAP Netweaver 7.0 Portal or Business Intelligence system used exclusively by one SAP ERP 6.0
3 Preparation
16/28 PUBLIC 2010-07-12
implications for the Maintenance Optimizer’s update strategy for your landscape: A sidecar system
only receives updates along with its associated SAP Business Suite system, whereas you can update
a hub system independently. However, the SAP Business suite software that is installed on the hub
system (for example, SAP XSS on an SAP NetWeaver Portal) is updated along with its associated
SAP Business Suite system.
For more information, see the document SAP Business Suite 7 i2010 Landscape Implementation – Technical
Planning Guide.
To check the landscape pattern of the connected Java systems, proceed as follows:
1. Log on to SAP Solution Manager and call transaction SMSY.
2. Choose Landscape Components Product Systems <System>
3. On the Product Instance Selection tab, double-click on the relevant Java product instances and
choose the Other Attributes tab.
4. Select the appropriate landscape pattern.
5. Creating the logical component
1. In transaction SMSY, choose System Groups and Logical Components
2. In the context menu of Logical Components choose Create New Logical Component.
3. Enter your system data.
The name of your logical component must start with “Z...”.
6. Assigning the system to the logical component
In the Current System Assignments of the newly created logical component, add your systems with the
appropriate roles (such as Development System or Production System).
RECOMMENDATION
We recommend adding all systems of one product to one logical component. This means
that you create one logical component and add the development system, the quality
assurance system, and the production system to the same logical component.
7. Optional: Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution.
However, if you already have a solution, then add your product system to it. When you later create
a maintenance transaction, you can select this solution and thus restrict the number of product
systems displayed.
1. Call transaction solution_manager and create a solution, if it does not yet exist.
2. Choose Solution Landscape and Solution Landscape Maintenance.
3. Add your SAP system to the solution as follows:
1. Change to edit mode.
2. Place the cursor on a new line in the Logical Component column.
3. Use the input help to select your system from the list (product, logical component).
4. Choose Complete System Data Replication.
3 Preparation
2010-07-12 PUBLIC 17/28
18/28 PUBLIC 2010-07-12
4 Upgrade Process
This section describes the upgrade process of SAP SRM Java systems as well as the synchronization steps
required for the upgrade of SRM dual-stack systems.
4.1 Synchronized Upgrade of Dual-Stack Systems
If you run an ABAP-based server and a Java-based server in the same SAP system, you must upgrade
them in parallel. The upgrade of these systems requires you to use the SAP Enhancement Package
Installer (SAPehpi) for the Java part and SAPup for the ABAP part. This procedure explains how to
perform a synchronized upgrade with these two tools.
Procedure
1. Start SAPup as usual using the STARTUP script.
2. Wait until the configuration roadmap step of the ABAP server upgrade is completed.
3. Download the latest SAPehpi from SAP Service Marketplace and unpack it.
4. Start SAPehpi with the following command:
Windows:
('jce_policy_zip=/<path_to_policy_files>>/SAPJVM5_crypto.zip' '-srvarg=/
5. Run both upgrades in parallel.
The ABAP upgrade uses the standard http server with the port number 4239 (http://<host name>:
4239). The Java upgrade uses the http server with the port number 7239 (http://<host name>:
7239)
2010-07-12 PUBLIC 19/28
This page is left blank for documents that are printed on both sides.
5 Follow-Up Activities
CAUTION
For more information about the follow-up activities that you have to perform after you have
upgraded your system, see the Installation Guide — SAP Enhancement Package Installation Using SAP
Enhancement Package Installer (SAPehpi) [page 10], section Follow-Up Activities.
5.1 Updating Dialog Instances
When you install new dialog instances, make sure that you use the correct installation DVDs.
The DVDs that you use for installing dialog instances have to correspond to the SAP NetWeaver release
and enhancement package level that is underlying your SAP Business Suite application system on the
central instance. So, if you have only updated the Business Suite application without the underlying
SAP NetWeaver, you have to use the installation DVDs that match the release and enhancement
package level of SAP NetWeaver. Using the SAP Business Suite 7 i2010 installation DVDs would lead to
problems due to changes in the kernel structure.
5.2 Changing Passwords
As of SAP NetWeaver 7.0 Support Package 03, new security policies apply. You have to change passwords
if:
Your passwords are older than 90 days.
Your passwords do not contain between 6 and 12 characters and do not consist of both letters and
numerals.
Your password contains a user name.
When you create a new password, you are not allowed to duplicate the old password.
If you change the J2EE engine administrator password, you have to make sure that external tools (for
example, SDM and JSPM) can read the password. These tools read the J2EE Engine administrator
password from the secure store. Since the secure store is not automatically updated, you have to do
this manually. Proceed as follows:
1. Select secure store.
2. Select the admin/password/<SAPSID> entry.
3. In the Value field, enter the new password for the J2EE Engine administrator and choose Add.
4. To save the data, choose File Apply .
5 Follow-Up Activities
Only valid for: SAP SRM Server;SRM Live Auction Cockpit (SRMLAC) |
5.3 Live Auction Cockpit Smoke Test
Launch the Live Auction Cockpit Smoke Test in your web browser to check that implementation was
successful.
General Information
Contains information about the Live Auction build as well as the J2EE server.
Smoke Test (User Management) [page 22]
Smoke Test (Applet) [page 0 ]
The Live Auction Cockpit Smoke Test resides on the J2EE server and has a URL similar to the following:
http://<j2ee_host.domain>:<default_port~50000>/srm/la.
5.3.1 Smoke Test (User Management)
The Smoke Test (User Management) tab contains 4 smoke tests – 2 self-diagnoses and 2 manual
diagnoses – that verify the correctness of the User Management configuration as well as the JCo/RFC
configuration on the current J2EE server. All self-diagnoses are run automatically when the page loads.
If a self-diagnosis runs error-free, the result is displayed in green. If a self-diagnosis fails, the result is
displayed in red. The J2EE's log and trace files display more information about an error after the result
has been displayed. Try to resolve any failures, in the order they are presented on the page.
Process
The system verifies that the J2EE server is configured to use an ABAP back end as the UME data
store.
You verify that the UM logon page is working properly and that it is using the correct ABAP back
end for user authentication.
You verify that the single sign-on ticket issuing system is generating an SSO ticket that is compatible
with the current J2EE server.
The system verifies that the JCo/RFC connection to the SRM server is working properly.
5.3.1.1 Verifying the UM Logon Page
Prerequisites
The system verifies that the J2EE server is configured to use an ABAP back end as the UME data source.
5 Follow-Up Activities
22/28 PUBLIC 2010-07-12
Procedure
1. Choose UME user admin and log on to the SAP SRM server to which the current J2EE server is
connected.
If the user authentication is successful, you see the user details screen on the UME administration
page.
Prerequisites
You have verified that the UM logon page is working properly and that it is using the correct ABAP
back-end for user authentication.
Procedure
1. Enter the URL for the ticket issuing system and choose Logon.
When the logon screen is displayed, log on with an SAP SRM user.
2. Once you have logged on successfully, close the browser window.
3. Return to the smoke test and refresh the page.
The ticket information as well as the status of the JCo RFC connection is displayed at the bottom
of the page.
5.3.2 Smoke Test (Applet)
The Smoke Test (Applet) tab contains 4 smoke tests – 3 self-diagnoses and 1 manual diagnosis – to
verify the deployments of the Live Auction Java applets and resource bundles.
All self-diagnoses are run automatically when the page loads. If a self-diagnosis runs error-free, the
result is displayed in green. If a self-diagnosis fails, the result is displayed in red. Try to resolve any
failures, in the order that they are presented on the page.
Process
The system verifies that the initiator applet JAR file of Live Auction is deployed properly.
The system verifies that the respondent applet JAR file of Live Auction is deployed properly.
The system verifies that the client resources JAR file of Live Auction is deployed properly.
NOTE
If you want to download the JAR file for further analysis after any of the steps above, click the
Download button.
You verify that the Live Auction applet settings are correctly configured and that the applet can
be launched.
2010-07-12 PUBLIC 23/28
Prerequisites
The system has verified the successful deployment of the following:
Live Auction initiator applet JAR file
Live Auction respondent applet JAR file
Live Auction client resources JAR file
Procedure
NOTE
The input fields displayed in this test are optional.
If the applet settings are configured properly and the applet can be launched, you see the applet's
splash screen.
NOTE
If you know the GUID of a valid auction on the SAP SRM server and want to view the auction
in the applet, enter all the necessary information in the input fields and then choose Test. End of: SAP SRM Server;SRM Live Auction Cockpit (SRMLAC) |
Only valid for: SRM Live Auction Cockpit (SRMLAC) |
5.4 Migrating Data from Your Existing Live Auction Cockpit
After the upgrade, you need to migrate auction data and update the database to initialize new database
fields in SAP SRM LAC 7.0. To do so, you must manually execute two post-upgrade reports. If you have
a lot of existing auction data in your system, we recommend scheduling a background job to run these
reports in order to avoid time-outs.
NOTE
Before performing post-upgrade activities, ensure that the JCo RFC user has S_RFC authorization.
Procedure
1. In the SAP SRM system, go to transaction SE38.
2. Execute report BBP_LA_DATA_MIGRATION.
BBP_Z090_XPRA_AUCTIONS_XPRA550.
Result
Any data from your existing Live Auction Cockpit is migrated. You can launch the application and
process auctions. End of: SRM Live Auction Cockpit (SRMLAC) |
5 Follow-Up Activities
24/28 PUBLIC 2010-07-12
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
Your SAP SRM Live Auction Cockpit (LAC) 7.0 system includes application properties preserved during
the upgrade process; however, it does not reflect any resource setting customizations that you may
have performed in your existing SAP SRM LAC system.
RECOMMENDATION
Before copying any customizations from your existing SAP SRM LAC system to your SAP SRM
LAC 7.0 system, launch SAP SRM LAC 7.0 to determine if those changes are still required.
CAUTION
Due to the unknown number and types of customizations in your existing system, the following
is intended as a reference guide rather than an exact procedure for migrating those customizations.
Procedure
RECOMMENDATION
To avoid overwriting your modifications whenever a patch is deployed, always create your own
resource files rather than replacing or modifying those shipped with SAP SRM LAC.
1. Once you have determined that you need to copy customizations from your existing SAP SRM
LAC system to SAP SRM LAC 7.0, identify what changes were made in your existing SAP SRM LAC
system and where they were made in the resource files. For more information, see Determining Existing
Customizations [external document].
Image Files
A number of image files that were used in previous versions of SAP SRM LAC have been
renamed or removed in SAP SRM LAC 7.0. Review your customized images and see if they are
affected.
There are also several new image files in SAP SRM LAC 7.0; you may wish to review those as
well.
For more information, see SAP Solution Manager; navigate to the configuration structure for
SAP SRM and choose Basic Settings for Strategic Sourcing Sourcing with RFx and Auction Settings for
Auction Configuring the Live Auction Cockpit User Interface .
Resource Bundles
A number of resource bundles that were used in previous versions of SAP SRM LAC have been
renamed or removed in SAP SRM LAC 7.0. Please review your customized resource bundles
to see if they are affected.
5 Follow-Up Activities
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
2010-07-12 PUBLIC 25/28
If you plan to carry over customized resource texts, make sure that the file names and the
resource keys of the original resource bundle files are unchanged.
Store all your customized resource files under:
<INSTDIR>:/usr/sap/<SAPSID>/SYS/global/srmla/resources
2. Adjust the values of the following properties to either 1 or 2 so that your customized files will be
used by SAP SRM LAC 7.0:
applet.initiator.archive
applet.respondent.archive
applet.archive.selection
For more information, see SAP Solution Manager; navigate to the configuration structure for SAP
SRM and choose Basic Settings for Strategic Sourcing Sourcing with RFx and Auction Settings for
Auction , and see:
Configuring the Live Auction Cockpit User Interface
Managing Live Auction Cockpit Properties End of: SRM Live Auction Cockpit (SRMLAC) |
5 Follow-Up Activities
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
26/28 PUBLIC 2010-07-12
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
© Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
SAP Supplier Relationship Management 7.0 Including SAP Enhancement Package 1
Table of Contents
2 Planning
2.2 Upgrade in an SAP System Group
3 Preparation
3.1.2 Installation of Landscape Verification 1.0 for SAP Solution Manager
3.1.3 Configuration of the Maintenance Optimizer
3.1.4 Maintaining System Landscape Information
4 Upgrade Process
5 Follow-Up Activities
5.3.1 Smoke Test (User Management)
5.3.1.1 Verifying the UM Logon Page
5.3.1.2 Verifying the SSO Ticket
5.3.2 Smoke Test (Applet)
5.4 Migrating Data from Your Existing Live Auction Cockpit
5.5 Migrating Resource Customizations from Your Existing Live Auction Cockpit
Copyright and trademarks