PUBLIC

Upgrade Guide

SAP ERP 6.0 Java

Support Release 3

Target Audience

n System administrators
n Technology consultants

Document version: 1.0 ‒ 03/28/2008

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
[Link]

© Copyright 2008 SAP AG. All rights reserved. JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
No part of this publication may be reproduced or
implemented by Netscape.
transmitted in any form or for any purpose without the
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,
express permission of SAP AG. The information contained
ByDesign, SAP Business ByDesign, and other SAP products
herein may be changed without prior notice.
and services mentioned herein as well as their respective
Some software products marketed by SAP AG and its
logos are trademarks or registered trademarks of SAP AG in
distributors contain proprietary software components of
Germany and in several other countries all over the world.
other software vendors.
All other product and service names mentioned are the
No part of this publication may be reproduced or trademarks of their respective companies. Data contained
transmitted in any form or for any purpose without the in this document serves informational purposes only.
express permission of SAP AG. The information contained National product specifications may vary.
herein may be changed without prior notice. These materials are subject to change without notice.
Some software products marketed by SAP AG and its These materials are provided by SAP AG and its affiliated
distributors contain proprietary software components of companies ("SAP Group") for informational purposes
other software vendors. only, without representation or warranty of any kind, and
Microsoft, Windows, Excel, Outlook, and PowerPoint are SAP Group shall not be liable for errors or omissions with
registered trademarks of Microsoft Corporation. respect to the materials. The only warranties for SAP Group
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, products and services are those that are set forth in the
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, express warranty statements accompanying such products
pSeries, xSeries, zSeries, System i, System i5, System p, and services, if any. Nothing herein should be construed as
System p5, System x, System z, System z9, z/OS, AFP, constituting an additional warranty.
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
This document was created using stylesheet 2006-12-31
i5/OS, POWER, POWER5, POWER5+, OpenPower and
(V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2
PowerPC are trademarks or registered trademarks of IBM
from Michael Kay ([Link] XSLT version 1.
Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
Disclaimer
are either trademarks or registered trademarks of Adobe
Some components of this product are based on Java™. Any
Systems Incorporated in the United States and/or other
code change in these components may cause unpredictable
countries.
and severe malfunctions and is therefore expressly
Oracle is a registered trademark of Oracle Corporation.
prohibited, as is any decompilation of these components.
UNIX, X/Open, OSF/1, and Motif are registered trademarks
Any Java™ Source Code delivered with this product is
of the Open Group.
only to be used by SAP’s Support Services and may not be
Citrix, ICA, Program Neighborhood, MetaFrame,
modified or altered in any way.
WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
Legal Software Terms
HTML, XML, XHTML and W3C are trademarks or registered
trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology. Terms for Included Open Source Software
Java is a registered trademark of Sun Microsystems, Inc. This SAP software contains also the third party open
source software products listed below. Please note that for

2/102 PUBLIC 03/28/2008

these third party products the following special terms and n "Source" form shall mean the preferred form
conditions shall apply. for making modifications, including but not
limited to software source code, documentation
1. This software was developed using ANTLR. source, and configuration files.
2. gSOAP n "Object" form shall mean any form resulting
Part of the software embedded in this product is gSOAP from mechanical transformation or translation
software. Portions created by gSOAP are Copyright of a Source form, including but not
(C) 2001-2004 Robert A. van Engelen, Genivia inc. All limited to compiled object code, generated
Rights Reserved. documentation, and conversions to other
THE SOFTWARE IN THIS PRODUCT WAS IN PART media types.
PROVIDED BY GENIVIA INC AND ANY EXPRESS n "Work" shall mean the work of authorship,
OR IMPLIED WARRANTIES, INCLUDING, BUT whether in Source or Object form, made
NOT LIMITED TO, THE IMPLIED WARRANTIES available under the License, as indicated by a
OF MERCHANTABILITY AND FITNESS FOR A copyright notice that is included in or attached
PARTICULAR PURPOSE ARE DISCLAIMED. IN to the work (an example is provided in the
NO EVENT SHALL THE AUTHOR BE LIABLE Appendix below).
FOR ANY DIRECT, INDIRECT, INCIDENTAL, n "Derivative Works" shall mean any work,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL whether in Source or Object form, that is
DAMAGES (INCLUDING, BUT NOT LIMITED TO, based on (or derived from) the Work and for
PROCUREMENT OF SUBSTITUTE GOODS OR which the editorial revisions, annotations,
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR elaborations, or other modifications represent,
BUSINESS INTERRUPTION) HOWEVER CAUSED as a whole, an original work of authorship. For
AND ON ANY THEORY OF LIABILITY, WHETHER the purposes of this License, Derivative Works
IN CONTRACT, STRICT LIABILITY, OR TORT shall not include works that remain separable
(INCLUDING NEGLIGENCE OR OTHERWISE) from, or merely link (or bind by name) to the
ARISING IN ANY WAY OUT OF THE USE OF THIS interfaces of, the Work and Derivative Works
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY thereof.
OF SUCH DAMAGE." n "Contribution" shall mean any work of
authorship, including the original version of
3. Apache License, Version 2.0
the Work and any modifications or additions
a) Definitions: to that Work or Derivative Works thereof,
n "License" shall mean the terms and conditions that is intentionally submitted to Licensor for
for use, reproduction, and distribution inclusion in the Work by the copyright owner
as defined by Sections 1 through 9 of this or by an individual or Legal Entity authorized
document. to submit on behalf of the copyright owner.
n "Licensor" shall mean the copyright owner or For the purposes of this definition, "submitted"
entity authorized by the copyright owner that means any form of electronic, verbal, or written
is granting the License. communication sent to the Licensor or its
n "Legal Entity" shall mean the union of the representatives, including but not limited to
acting entity and all other entities that control, communication on electronic mailing lists,
are controlled by, or are under common source code control systems, and issue tracking
control with that entity. For the purposes systems that are managed by, or on behalf
of this definition, "control" means (i) the of, the Licensor for the purpose of discussing
power, direct or indirect, to cause the direction and improving the Work, but excluding
or management of such entity, whether by communication that is conspicuously marked
contract or otherwise, or (ii) ownership of or otherwise designated in writing by the
fifty percent (50%) or more of the outstanding copyright owner as "Not a Contribution."
shares, or (iii) beneficial ownership of such n "Contributor" shall mean Licensor and any
entity. individual or Legal Entity on behalf of whom a
n "You" (or "Your") shall mean an individual or Contribution has been received by Licensor and
Legal Entity exercising permissions granted by subsequently incorporated within the Work.
this License.

03/28/2008 PUBLIC 3/102

 b) Grant of Copyright License such NOTICE file, excluding those notices that
Subject to the terms and conditions of this License, do not pertain to any part of the Derivative
each Contributor hereby grants to You a perpetual, Works, in at least one of the following places:
worldwide, non-exclusive, no-charge, royalty-free, within a NOTICE text file distributed as part
irrevocable copyright license to reproduce, prepare of the Derivative Works; within the Source
Derivative Works of, publicly display, publicly form or documentation, if provided along
perform, sublicense, and distribute the Work and with the Derivative Works; or, within a display
such Derivative Works in Source or Object form. generated by the Derivative Works, if and
c) Grant of Patent License wherever such third-party notices normally
Subject to the terms and conditions of this License, appear. The contents of the NOTICE file are
each Contributor hereby grants to You a perpetual, for informational purposes only and do not
worldwide, non-exclusive, no-charge, royalty-free, modify the License. You may add Your own
irrevocable (except as stated in this section) patent attribution notices within Derivative Works that
license to make, have made, use, offer to sell, sell, You distribute, alongside or as an addendum to
import, and otherwise transfer the Work, where the NOTICE text from the Work, provided that
such license applies only to those patent claims such additional attribution notices cannot be
licensable by such Contributor that are necessarily construed as modifying the License.
infringed by their Contribution(s) alone or by You may add Your own copyright statement to
combination of their Contribution(s) with the Your modifications and may provide additional
Work to which such Contribution(s) was submitted. or different license terms and conditions for use,
If You institute patent litigation against any entity reproduction, or distribution of Your modifications,
(including a cross-claim or counterclaim in a or for any such Derivative Works as a whole,
lawsuit) alleging that the Work or a Contribution provided Your use, reproduction, and distribution
incorporated within the Work constitutes direct or of the Work otherwise complies with the conditions
contributory patent infringement, then any patent stated in this License.
licenses granted to You under this License for that e) Submission of Contributions
Work shall terminate as of the date such litigation is Unless You explicitly state otherwise, any
filed. Contribution intentionally submitted for inclusion
d) Redistribution in the Work by You to the Licensor shall be
You may reproduce and distribute copies of the under the terms and conditions of this License,
Work or Derivative Works thereof in any medium, without any additional terms or conditions.
with or without modifications, and in Source or Notwithstanding the above, nothing herein shall
Object form, provided that You meet the following supersede or modify the terms of any separate
conditions: license agreement you may have executed with
Licensor regarding such Contributions.
A) You must give any other recipients of the Work
or Derivative Works a copy of this License; and f) Trademarks
This License does not grant permission to use
B) You must cause any modified files to carry
the trade names, trademarks, service marks, or
prominent notices stating that You changed
product names of the Licensor, except as required
the files; and
for reasonable and customary use in describing the
C) You must retain, in the Source form of any origin of the Work and reproducing the content of
Derivative Works that You distribute, all the NOTICE file.
copyright, patent, trademark, and attribution
g) Disclaimer of Warranty
notices from the Source form of the Work,
Unless required by applicable law or agreed to in
excluding those notices that do not pertain to
writing, Licensor provides the Work (and each
any part of the Derivative Works; and
Contributor provides its Contributions) on an
D) If the Work includes a "NOTICE" text file as part "AS IS" BASIS, WITHOUT WARRANTIES OR
of its distribution, then any Derivative Works CONDITIONS OF ANY KIND, either express
that You distribute must include a readable or implied, including, without limitation,
copy of the attribution notices contained within any warranties or conditions of TITLE,

4/102 PUBLIC 03/28/2008

 NON-INFRINGEMENT, MERCHANTABILITY, i) Accepting Warranty or Additional Liability
or FITNESS FOR A PARTICULAR PURPOSE. While redistributing the Work or Derivative Works
You are solely responsible for determining the thereof, You may choose to offer, and charge a fee
appropriateness of using or redistributing the Work for, acceptance of support, warranty, indemnity, or
and assume any risks associated with Your exercise other liability obligations and/or rights consistent
of permissions under this License. with this License. However, in accepting such
h) Limitation of Liability obligations, You may act only on Your own behalf
In no event and under no legal theory, whether in and on Your sole responsibility, not on behalf of
tort (including negligence), contract, or otherwise, any other Contributor, and only if You agree to
unless required by applicable law (such as deliberate indemnify, defend, and hold each Contributor
and grossly negligent acts) or agreed to in writing, harmless for any liability incurred by, or claims
shall any Contributor be liable to You for damages, asserted against, such Contributor by reason of your
including any direct, indirect, special, incidental, accepting any such warranty or additional liability.
or consequential damages of any character arising
as a result of this License or out of the use or Documentation in the SAP Service
inability to use the Work (including but not limited Marketplace
to damages for loss of goodwill, work stoppage, You can find this document at the following address:
computer failure or malfunction, or any and all [Link]

other commercial damages or losses), even if such

Contributor has been advised of the possibility of
such damages.

03/28/2008 PUBLIC 5/102

Aspects Covered by this Guide

This guide was generated according to the NetWeaver Development Infrastructure (DI)
following criteria: NetWeaver BI Java Components (BI-Java)
NetWeaver Enterprise Portal (EP)
SAP Component NetWeaver EP Core (EPC)
SAP ERP NetWeaver Process Integration (PI)
NetWeaver Mobile Infrastructure (MI)
Usage Type / Software Unit
Extended E-Selling Components (XECO) Platform
Self Services (XSS) Unix
Learning Solution (Content Player)
Biller Direct Technology
ERP Business Packages (Portal Content) Java
NetWeaver Application Server Java (AS Java)

6/102 PUBLIC 03/28/2008

Typographic Conventions

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
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
Example Textual cross-references to an internet address, for example, [Link]
/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 n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n 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

03/28/2008 PUBLIC 7/102

Document History

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 [Link]

The following table provides an overview on the most important document changes:
Version Date Description

1.0 3/28/2008 First version

8/102 PUBLIC 03/28/2008

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . 15
1.2.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 15
1.2.2 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2 Upgrade ‒ Step By Step . . . . . . . . . . . . . . . . . . . 19

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1 Upgrade Process Overview . . . . . . . . . . . . . . . . . . . 26
3.2 Synchronized Upgrade of Dual Stack Systems . . . . . . . . . . . . 27
3.3 Upgrade Scope for ERP Java Components . . . . . . . . . . . . . 29
3.4 Upgrade Scope for SAP NetWeaver . . . . . . . . . . . . . . . . 32
3.5 Planning the Upgrade of Non-Standard SAP Systems . . . . . . . . . 35
3.6 Upgrade of NWDI-Driven System Landscapes . . . . . . . . . . . . 36
3.7 Upgrade of High Availability Systems . . . . . . . . . . . . . . . 37
3.8 Checking the Source Release . . . . . . . . . . . . . . . . . . 38
3.9 Upgrade of the Operating System and Database System: Overview . . . . 38
3.10 Checking the Java Development Kit Version and Settings . . . . . . . . 40
3.11 Checking the Software Delivery Manager Version . . . . . . . . . . 41
3.12 Downloading Support Package Stacks . . . . . . . . . . . . . . . 42
3.13 Downloading Enhancement Packages . . . . . . . . . . . . . . . 43
3.14 Required DVDs . . . . . . . . . . . . . . . . . . . . . . . 45
3.15 Stopping SAP MMC and SDM GUI . . . . . . . . . . . . . . . . 45
3.16 Space Requirements in the File System and the Database . . . . . . . . 46
3.17 Using SAP Solution Manager . . . . . . . . . . . . . . . . . . 46

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 49
4.1 Preparing the Upgrade of Internet Sales (R/3 Edition) Web Application
Components . . . . . . . . . . . . . . . . . . . . . . . . 49
4.2 Performing a Database Backup . . . . . . . . . . . . . . . . . 51
4.3 Cleaning Up the Universal Worklist Cache . . . . . . . . . . . . . 51
4.4 Checking the C++ Runtime on AIX Operating System . . . . . . . . . 51
4.5 Undeploying the Software Component NWMADMIN . . . . . . . . . 52
4.6 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 52

03/28/2008 PUBLIC 9/102

4.7 Creating the Upgrade Directory . . . . . . . . . . . . . . . . . 53
4.8 Starting PREPARE . . . . . . . . . . . . . . . . . . . . . . 54
4.9 Starting the SDTGui . . . . . . . . . . . . . . . . . . . . . 56
4.10 Choosing the PREPARE Modules . . . . . . . . . . . . . . . . 56
4.11 Making Entries for the Initialization and Extraction Modules . . . . . . 57
4.12 Making Entries for the Configuration Module . . . . . . . . . . . . 59
4.13 Executing the General Checks and Finalization Modules . . . . . . . . 62

Chapter 5 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . 63

5.1 Starting the Upgrade . . . . . . . . . . . . . . . . . . . . . 63
5.2 Phase BEGIN_DOWNTIME . . . . . . . . . . . . . . . . . . . 63
5.3 Phase DOWNTIME_END . . . . . . . . . . . . . . . . . . . 64

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . 65

6.1 Executing the Script [Link] . . . . . . . . . . . . . . . . . 66
6.2 Upgrading or Installing Dialog Instances . . . . . . . . . . . . . . 67
6.3 Changing Passwords . . . . . . . . . . . . . . . . . . . . . 67
6.4 Performing Follow-Up Activities for the System Landscape Directory . . . 68
6.5 Performing Follow-Up Activities for the Composite Application Framework
Core (CAF Core) . . . . . . . . . . . . . . . . . . . . . . 68
6.6 Performing Follow-Up Activities for Adobe Document Services . . . . . 69
6.7 Performing Follow-Up Activities for SAP Solution Manager . . . . . . . 70
6.8 Checking the CBS Service Properties . . . . . . . . . . . . . . . 70
6.9 Importing XI Content for Software Component SAP_BASIS 7.00 . . . . . 71
6.10 Performing Follow-Up Activities for Business Intelligence . . . . . . . . 71
6.11 Checking the KMC Installation . . . . . . . . . . . . . . . . . 72
6.12 Performing Follow-Up Activities for Knowledge Management and Collaboration
(KMC) . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.13 Configuring Guided Procedures 2.0 Business Workflow Connectivity . . . 75
6.14 Undeploying Obsolete Mobile Infrastructure Development Components . . 76
6.15 Adjusting the XCM Configuration . . . . . . . . . . . . . . . . 76
6.16 Performing Follow-Up Activities for the E-Commerce User Management . . 78
6.17 Additional Follow-Up Activities for ERP E-Commerce . . . . . . . . . 79
6.17.1 Upgrading the Shop Management Data . . . . . . . . . . . . . . 79
6.17.2 Performing Adjustments to Java Class Changes . . . . . . . . . . . 80
6.17.3 Checking the Login Configuration . . . . . . . . . . . . . . . . 82
6.17.4 Replacing the Catalog Replication Mechanism . . . . . . . . . . . 83
6.17.5 Adjusting XCM Configuration and Creating Shops for New Scenarios . . . 83

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 85
A.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 85
A.1.1 Handling Upgrade Errors in SAPJup . . . . . . . . . . . . . . . 85

10/102 PUBLIC 03/28/2008

A.1.2 General Procedure for Upgrade Errors . . . . . . . . . . . . . . . 86
A.1.3 Upgrade Logs and Trouble Ticket . . . . . . . . . . . . . . . . 86
A.1.4 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . 88
A.1.5 Correcting Errors in the PREPARE Phases . . . . . . . . . . . . . 88
A.1.6 Correcting Problems in the Upgrade Phases for SAP Kernel, Internet Graphics
Service, and SAP MMC . . . . . . . . . . . . . . . . . . . . 89
A.1.7 Correcting Problems in the DEPLOY_* Phases . . . . . . . . . . . . 90
A.1.8 Correcting Problems with J2EE Engine Startup . . . . . . . . . . . 91
A.1.9 Starting and Stopping the J2EE Engine Manually . . . . . . . . . . . 92
A.1.10 Correcting Disk Space Problems . . . . . . . . . . . . . . . . . 93
A.1.11 Updating Version Information . . . . . . . . . . . . . . . . . 93
A.1.12 Migrating XCM Configuration Data Manually . . . . . . . . . . . . 94

Chapter B Reference . . . . . . . . . . . . . . . . . . . . . . . . . 97
B.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . 97

03/28/2008 PUBLIC 11/102

12/102 PUBLIC 03/28/2008
1 Introduction

1 Introduction

Purpose
This document describes the upgrade to SAP ERP 6.0 Support Release 3 Java Components. It
comprises the upgrade of the SAP Web Application Server 6.40 to SAP NetWeaver 7.0 SR3 Application
Server and the software installed on it. This means, it comprises the upgrade of the following
components:
Only valid for: Extended E-Selling Components (XECO)

n Internet Sales R/3 Edition (Internet Sales Web Application Components) 4.0 to SAP E-Commerce
for SAP ERP and IPC Web Application Components 4.0 to IPC 7.00 (included in software unit
Extended E-Selling Components).

Note
For upgrade information about the IPC Server/Engine, see SAP Note 844816. The IPC server is
no longer a separate component but included in the ERP ABAP Server (part of SAP Application
Platform). The SAP Note provides information about what actions are required due to this
technology change (with regards to the local IPC database, IPC configuration and user exits).
An existing IPC Server Installation is obsolete and can be removed.

End of: Extended E-Selling Components (XECO)

Only valid for: Self Services (XSS)

n (SAP MSS 100, SAP ESS 100 and SAP PCUI_GP 100) to (SAP MSS 600, SAP ESS 600, SAP PCUI_GP
600, SAP PSS 600, SAP ASR 600 and IS-HER-CSS 600)
End of: Self Services (XSS)

Only valid for: Biller Direct

n Biller Direct 3.0 to 6.0

End of: Biller Direct

Only valid for: Learning Solution (Content Player)

n Learning Solution (Content Player) 3.0 to Learning Solution 6.0

End of: Learning Solution (Content Player)

Besides the information about upgrading to SAP NetWeaver 7.0 Application Server Java, this
document also contains information about upgrading further SAP NetWeaver software units that
are possibly installed in the system that you want to upgrade. You will find information about the
following software units in this guide:

03/28/2008 PUBLIC 13/102

1 Introduction
1.1 New Features

n Business Intelligence Java Components (BI-Java)

n Process Integration (Exchange Infrastructure) (PI)
n EP Core (EPC)
n Enterprise Portal (EP)
n Mobile Infrastructure (MI)
n Development Infrastructure (DI)

Integration
If you want to upgrade this component in the context of the upgrade of an SAP Business Suite
application or one of its business scenarios, it is essential that you familiarize yourself with the
contents of the corresponding Upgrade Master Guide before starting the upgrade.

Note
To find the latest version of this document and the Upgrade Master Guide, see SAP Service Marketplace
at [Link]

In addition to this document, you also require other information, such as SAP Notes that are specific
to this upgrade, and any other documentation referred to in this document.

Constraints

Only valid for: Enterprise Portal (EP)

Although the former usage type Enterprise Portal has been separated into two usage types, EP Core
(EPC) and Enterprise Portal (EP), it is not possible to upgrade to usage type EP Core (EPC) only. If the
upgrade program detects a Portal Platform 6.0 installation in your source release system (based on
SAP Web AS 6.40), you can only perform an upgrade to usage types EPC + EP.
End of: Enterprise Portal (EP)

There is no SAP NW 7.0-compatible version of Adaptive Computing Controller (ACC) available. If

ACC is installed in your source release system, the upgrade program will undeploy it during the
upgrade. If you want to use ACC after the upgrade, you can perform a standalone installation of the
latest available version, Adaptive Computing Controller in SAP NetWeaver 7.1. For more information,
see SAP Note 1008828.

1.1 New Features

New Features in the Upgrade Based on SAP NetWeaver 7.0 Support Release 3
The upgrade to SAP ERP 6.0 SR3 Java Components includes SAP NetWeaver 7.0 Support Package 14
and SAP ERP 6.0 Support Package 11.

14/102 PUBLIC 03/28/2008

1 Introduction
1.2 Before You Start

New Features in the Upgrade Based on SAP NetWeaver 7.0 Support Release 2
The upgrade to SAP ERP 6.0 SR2 Java Components includes SAP NetWeaver 7.0 Support Package 09
and SAP ERP 6.0 Support Package 06.
As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separated into two related
usage types: EP Core (EPC) and Enterprise Portal (EP). Usage type EPC provides the core portal
capabilities available in the former usage type EP. Usage type EP now includes all portal add-on
capabilities but without the core portal functionality.

New Features in the Upgrade Based on SAP NetWeaver 7.0 Support Release 1

n Upgrade of High Availability Systems

SAPJup checks during PREPARE whether your system is a high availability system. If so, you have to
perform some additional actions manually.
n Solution Manager Key for the Upgrade
You need to run an SAP Solution Manager in your system landscape. PREPARE asks you to enter a
key generated by the Solution Manager without which it is not able to proceed.
n Support for Upgrades of NWDI‒Driven System Landscapes
SAPJup asks at the beginning of PREPARE whether the system that you want to upgrade is
configured as a runtime system in an NWDI track. If so, new versions of software components that
you have modified are not deployed during the upgrade. Instead, they are copied to the NWDI
transport directory and you can synchronize them with your modifications.
n Including Support Packages into the Upgrade
This function has been enhanced so that you can now include updates for the Software
Deployment Manager (SDM), the Internet Graphics Service and the SAP kernel.

1.2 Before You Start

1.2.1 Naming Conventions

mySAP ERP 2005 and SAP ERP 6.0

mySAP ERP 2005 has been renamed to SAP ERP 6.0. On the technical level, SAP ERP 6.0 is associated
with product version SAP ERP 2005. The term “SAP ERP 2005” remains valid. In this document,
the term “SAP ERP 6.0” and the name of the product version “SAP ERP 2005” are used to depict
the former release mySAP ERP 2005.

SAP NetWeaver Release Designators

As of March 2007, SAP updated its release naming strategy to remove year designations. As a result,
the product formerly named SAP NetWeaver 2004s has been renamed to SAP NetWeaver 7.0. Be aware

03/28/2008 PUBLIC 15/102

1 Introduction
1.2 Before You Start

that this release may be referred to in several ways as SAP transitions to the new name. These names
may include: SAP NetWeaver 2004s, SAP NetWeaver 7.0 (2004s), or SAP NetWeaver 7.0.

SAP NetWeaver Application Server and SAP Web Application Server

n The term “SAP NetWeaver Application Server” (or the short form “SAP NW AS”) is used in this
document when referring to SAP NetWeaver 7.0 and higher.
n The term “SAP Web Application Server” (or the short form “SAP Web AS”) is used in this
document when referring to Release 6.40.

SAP System ID
In this document, the SAP system ID is abbreviated as “SAPSID” or “sapsid.” If “sapsid” is used, your
SAP system ID must be entered in lowercase letters, for example “prd”. If “SAPSID” is used, you must
write in uppercase letters, for example “PRD”.

Instance Name
In this document, <instance_name> is used as a placeholder for the instance name in the instance
directory path of your system.
n For Java standalone systems, substitute <instance_name> with JC<xx> for the central instance and
J<xx> for dialog instances.
n For dual stack systems (ABAP + Java), substitute <instance_name> with DVEBMGS<xx> for the
central instance and D<xx> for dialog instances.
<xx> stands for the instance number.

1.2.2 SAP Notes

Definition
To prepare and perform the upgrade of your SAP system, you require some additional information
that is not included in this document. This information is in a range of SAP Notes on SAP Service
Marketplace, some of which you must read before you prepare the upgrade. The general Upgrade
Note contains current cross-database information on preparing the upgrade. There are separate
SAP Notes for the database-specific sections. When you actually upgrade the SAP system, you need
information from some additional SAP Notes. These SAP Notes are named at the appropriate places in
this guide.

SAP Notes for Preparing the Upgrade

You must request the general upgrade note for SAP NetWeaver, the upgrade note for your application,
and the SAP Note for your database before you start the upgrade. The general upgrade note for SAP
NetWeaver contains the keyword that you must enter when you start the upgrade.

16/102 PUBLIC 03/28/2008

1 Introduction
1.2 Before You Start

Since these SAP Notes are updated regularly, make sure you always use the newest version. The
following list contains the SAP Notes you need to prepare for the upgrade:
SAP Note Number Description Area
1102065 Additional information: Upgrade Specific to this upgrade
to SAP NetWeaver 7.0 SR3 Java
1131482 Additional information: Upgrade Specific to this upgrade
to SAP ERP 6.0 SR3 Java
Components
819876 Additional information: Upgrade IBM DB2 for Linux, Unix and
to SAP NetWeaver AS 7.0 Windows / specific to this upgrade
815202 Additional information: Upgrade IBM DB2 for z/OS / specific to this
to SAP NetWeaver AS 7.0 upgrade
851229 Additional information: Upgrade SAP MaxDB / specific to this
to SAP NetWeaver 7.0 Java upgrade
885167 Additional information: Upgrade Oracle / specific to this upgrade
to SAP NetWeaver 7.0 Java

Other SAP Notes

Besides the SAP Notes you need for preparing the upgrade, this upgrade guide also refers you to other
SAP Notes that contain additional information. The following list contains these SAP Notes:
SAP Note Description Area
Database-specific SAP Notes
356828 Migrating to 64-bit for AIX and Solaris IBM DB2 for Linux, UNIX and Windows
81737 APAR List IBM DB2 for z/OS
183311 Automated PTF Check IBM DB2 for z/OS
819829 Oracle Database 10g: Instant Client 10.x Oracle
on Unix
SAP Notes for All Databases
723909 Java VM settings for SAP J2EE 6.40/7.0 JVM and JDK
866472 Equivalent SP levels for NW ’04 and NW SAP Support Packages
7.0 Java components
813658 Repairs for upgrades to products based General upgrade
on SAP NW 7.0 AS
669669 Updating the SAP Component SAP Support Packages
Repository

03/28/2008 PUBLIC 17/102

1 Introduction
1.2 Before You Start

SAP Note Description Area

865424 SAPJupUser SAP* login error during General upgrade
upgrade
961747 Userhome folder support for special EP
characters

18/102 PUBLIC 03/28/2008

2 Upgrade ‒ Step By Step

2 Upgrade ‒ Step By Step

Checklist

Planning

o 1. You request the current SAP Notes for the upgrade. You require at least the general upgrade
Note 1102065, the ERP-specific upgrade Note 1131482, and the relevant database-specific SAP Note
[page 16].
o 2. You familiarize yourself with the upgrade process [page 26].
If you are upgrading a dual stack system, also read the information about the synchronization
of ABAP and Java upgrades [page 27].
o 3. You check the scope of the ERP Java components upgrade [page 29] and the SAP NetWeaver 7.0 upgrade
[page 32].
o 4. You plan the upgrade of non-standard SAP systems [page 35].
o 5. You consider the special properties of an upgrade of NWDI-driven system landscapes [page 36] in your
upgrade planning.
o 6. If you are upgrading a high availability system [page 37], check the specifics of this upgrade procedure.
o 7. You check the software requirements:
n The source release [page 38] of your SAP system
Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

l ISA R/3 Edition (Internet Sales Web Application Components) 4.0

End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: Self Services (XSS)

l
u SAP ESS 100 (Employee Self Service)
u SAP MSS 100 (Manager Self Service)
u SAP PCUI_GP 100 (Floor Plan Manager)
End of: Self Services (XSS)

Only valid for: Biller Direct

l Biller Direct 3.0

End of: Biller Direct

Only valid for: Learning Solution (Content Player)

l Learning Solution (Content Player) 3.0

End of: Learning Solution (Content Player)

03/28/2008 PUBLIC 19/102

2 Upgrade ‒ Step By Step

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

l IPC Web Application Components 4.0

End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: Application Server (AS)

l SAP Web Application Server 6.40 Support Package 09 or higher

End of: Application Server (AS)

Only valid for: Enterprise Portal (EP);EP Core (EPC)

l SAP Enterprise Portal 6.0_640 Support Package 09

End of: Enterprise Portal (EP);EP Core (EPC)

Only valid for: Process Integration (PI)

l SAP Exchange Infrastructure 3.0 Support Package 09

End of: Process Integration (PI)

Only valid for: BI Java Components (BI-Java)

l SAP BI 3.5 Java Components (Universal Data Integration / Meta Model Repository)
Support Package 09
End of: BI Java Components (BI-Java)

Only valid for: Mobile Infrastructure (MI)

l SAP Mobile Infrastructure 2.5 SP 09 or higher

End of: Mobile Infrastructure (MI)

Only valid for: Application Server (AS)

l Adobe Document Services 1.0 Support Package 09

End of: Application Server (AS)

Only valid for: Application Server (AS)

l SAP Knowledge Warehouse 7.0 (Internet Knowledge Servlet 1.0)

End of: Application Server (AS)

n You plan and perform the upgrade of the operating system or database system [page 38], if necessary:
For detailed information about operating system and database versions that are currently
supported, see SAP Service Marketplace at [Link] On the
same page, you can find a link to the general Product Availability Matrix.
Only valid for: IBM DB2 for Linux and UNIX and Windows

Database version: At least Version 9 FixPak 3; migrate before PREPARE

End of: IBM DB2 for Linux and UNIX and Windows

Only valid for: IBM DB2 for z/OS

Database version: At least Version 8.1.5 (New Function mode); migrate before PREPARE
End of: IBM DB2 for z/OS

20/102 PUBLIC 03/28/2008

2 Upgrade ‒ Step By Step

Only valid for: MaxDB

Database version: At least Version [Link]; migrate before PREPARE

End of: MaxDB

Only valid for: Oracle

Database version: At least Version [Link] for the upgrade; you can run PREPARE with
Version 9.2.0 or higher.
End of: Oracle

n JDK version and settings [page 40]

n Software Delivery Manager version [page 41]
o 8. You download Support Package Stacks [page 42].
o 9. You download Enhancement Packages [page 43].
o 10. You make sure that you have the required DVDs [page 45].
o 11. You consider that you have to shut down SAP Management Console and the SDM GUI [page 45].
o 12. You make sure that your system has the required hardware resources [page 46].
o 13. You plan the use of SAP Solution Manager [page 46] in your system landscape.

Preparation

Only valid for: Extended E-Selling Components (XECO)

o 1. You prepare the upgrade of Internet Sales (R/3 Edition) Web Application Components [page 49].
End of: Extended E-Selling Components (XECO)

o 2. You perform a database backup [page 51].

Only valid for: Enterprise Portal (EP)

o 3. For Knowledge Management and Collaboration only: You clean up the Universal Worklist Cache
[page 51].
End of: Enterprise Portal (EP)

o 4. You check the C++ Runtime [page 51] on AIX operating systems.
o 5. You undeploy the software component NWMADMIN [page 52].
o 6. You generate the SAP Solution Manager key [page 52].
o 7. You create the upgrade directory [page 53].
o 8. You start PREPARE [page 54] and the SDTGui [page 56].
o 9. You choose the PREPARE modules [page 56] and run the individual modules:
n Initialization and Extraction [page 57]
n Configuration [page 59]
n General Checks and Finalization [page 62]

Upgrade Process

o 1. You start the upgrade [page 63] from the upgrade directory.

03/28/2008 PUBLIC 21/102

2 Upgrade ‒ Step By Step

o 2. Before the downtime begins [page 63], you make a backup of the database and the upgrade directory,
stop all dialog instances, stop SAP MMC and SDM, stop jcmon and other standalone monitoring
tools, and if you are running an upgrade of a high availability system, you stop the Java central
instance and SCS instance.
o 3. At the end of the downtime, you again create backups [page 64], and if you are running an upgrade
of a high availability system, you start the SCS instance and the Java central instance.

Follow-Up Activities

o 1. You execute the script [Link] [page 66].

o 2. You upgrade or install dialog instances [page 67].
o 3. You change passwords [page 67] if necessary.
o 4. You perform the follow-up activities for the System Landscape Directory [page 68].
o 5. You perform the follow-up activities for the Composite Application Framework (CAF) [page 68].
o 6. You perform the follow-up activities for the Adobe Document Service [page 69].
o 7. You perform the follow-up activities for SAP Solution Manager [page 70].
Only valid for: Development Infrastructure (DI)

o 8. You check the CBS service properties [page 70].

End of: Development Infrastructure (DI)

Only valid for: Process Integration (PI)

o 9. You import the XI content [page 71] for SAP Basis 7.0.
End of: Process Integration (PI)

Only valid for: BI Java Components (BI-Java)

o 10. You perform the follow-up activities for Business Intelligence [page 71].
End of: BI Java Components (BI-Java)

Only valid for: Enterprise Portal (EP)

o 11. You check the Knowledge Management and Collaboration Installation [page 72].
End of: Enterprise Portal (EP)

Only valid for: Enterprise Portal (EP)

o 12. You perform the follow-up activities for Knowledge Management and Collaboration [page 74].
End of: Enterprise Portal (EP)

Only valid for: EP Core (EPC)

o 13. You perform the follow-up activities for Guided Procedures [page 75].
End of: EP Core (EPC)

Only valid for: Mobile Infrastructure (MI)

o 14. You undeploy obsolete Mobile Infrastructure development components [page 76].
End of: Mobile Infrastructure (MI)

22/102 PUBLIC 03/28/2008

2 Upgrade ‒ Step By Step

Only valid for: Biller Direct

o 15. You adjust the XCM configuration [page 76].

End of: Biller Direct

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

o 16. You perform the follow-up activities for E-Commerce:

n You adjust the XCM configuration [page 76].
n You perform follow-up activities for the E-Commerce user management [page 78].
End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: Extended E-Selling Components (XECO)

o 17. You perform the additional follow-up activities for ERP E-Commerce [page 79].
End of: Extended E-Selling Components (XECO)

03/28/2008 PUBLIC 23/102

This page is intentionally left blank.
3 Planning

3 Planning

This part of the document contains information about planning your upgrade. Before you begin the
actual upgrade, you must first plan it carefully. 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 to ensure that the
upgrade runs as efficiently as possible.

Note
TeamSAP offers the free upgrade service SAP GoingLive Functional Upgrade Check. A team of
experts checks the parameter settings of your system in one session before the upgrade, and gives
you detailed recommendations for the configuration. After the upgrade, the parameters and the
entire system status are checked again in a second session. For information about the service and on
ordering it, see SAP Service Marketplace at [Link] Maintenance &
Services SAP Support Offerings SAP Safeguarding .

When you plan your upgrade, note the following:

n All the times specified in this document are based on hardware with medium performance levels.
n Do not perform any additional actions during the upgrade that could cause it to run less smoothly.
n Start planning your upgrade in good time.
n If it is technically possible, or unless otherwise specified, we recommend that you upgrade the
operating system and database system and your SAP system at different times.
Actions
The following sections are important for planning the upgrade:
n Upgrade Process Overview [page 26]
n Synchronized Upgrade of Dual Stack Systems [page 27]
n Upgrade Scope for ERP Java Components [page 29]
Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Enterprise Portal (EP);EP

Core (EPC);Mobile Infrastructure (MI);Process Integration (PI)

n Upgrade Scope for SAP NetWeaver [page 32]

End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Enterprise Portal (EP);EP

Core (EPC);Mobile Infrastructure (MI);Process Integration (PI)

n Planning the Upgrade of Non-Standard SAP Systems [page 35]

n Upgrade of NWDI-Driven System Landscapes [page 36]
n Upgrade of High Availability Systems [page 37]

03/28/2008 PUBLIC 25/102

3 Planning
3.1 Upgrade Process Overview

n Checking Software Requirements

l Checking the Source Release [page 38]
l Upgrade of the Operating System and Database System: Overview [page 38]
l Checking the Java Development Kit Version and Settings [page 40]
l Checking the Software Delivery Manager Version [page 41]
n Downloading Support Package Stacks [page 42]
n Downloading Enhancement Packages [page 43]
n Required DVDs [page 45]
n Stopping SAP MMC and SDM GUI [page 45]
n Space Requirements in the File System and the Database [page 46]
n Using SAP Solution Manager [page 46]

3.1 Upgrade Process Overview

The following sections provide you with an overview of the upgrade process in general.

Features
The upgrade consists of two major parts: the PREPARE program and the actual upgrade.

PREPARE
PREPARE mainly performs checks, collects data, and requires some data input and decisions from you.

n Checks
PREPARE checks the system and determines most of the relevant system parameters automatically
(for example, SAP system profiles, SDM parameters, and source release components).
n DVD extraction
The DVD contents are extracted to the upgrade directory.
n Target release configuration
PREPARE maps the source release components to the target release software units. In this way it
determines which components need to be upgraded and which new components have to be
installed during the upgrade. The upgrade program always deploys complete software units.

Example
If the upgrade program detects the IPC Web Application Components on the upgrade host, it
deploys the software unit Extended E-Selling Components, which includes SAP Shared Java
Applications, and SAP Java Data Dictionary.

For more information about the software units, see Upgrade Scope for ERP Java Components [page 29].
PREPARE also enables you to update software components that are not part of the shipment,
for example, customer developments or third-party software. You can also specify that certain
components are not updated, but remain unchanged.

26/102 PUBLIC 03/28/2008

3 Planning
3.2 Synchronized Upgrade of Dual Stack Systems

If you have modified SAP software, these components are detected by the PREPARE program. You
can then decide whether you want to keep the old version or provide a new one.
In addition, you can include Support Packages in the upgrade process. The Support Packages
are then imported during the upgrade and your system has the most up-to-date state after the
upgrade.

Upgrade
The upgrade itself performs conversions, updates, and deployments. The upgrade consists of the
following major steps:
n Start of downtime
n Update of SAP kernel, SAP MMC, and SDM
n Deployment of the file system, the database, and the core engine modules
n Offline migration: The Java Migration Tool (JMT) converts and migrates structures and data of
the J2EE Engine.
n Online migration: SAPJup starts the J2EE Engine in safe mode and performs application-specific
conversions.
n Deployment of software units as specified during PREPARE
n Restart of the J2EE Engine in normal mode and resumption of production operation

Dialog Instances
You have to shut down all dialog instances in the cluster manually before you start the upgrade. To
upgrade the dialog instances, you have to reinstall [page 67] them.

3.2 Synchronized Upgrade of Dual Stack Systems

If you run an ABAP-based server and a Java-based server in the same system, you have to upgrade
them in parallel. The two upgrade processes require a synchronization that affects the following areas:
n Upgrade progress
n User management
n Profile changes
n Start/stop of the SAP system
n Reset of upgrades

Progress of the Upgrade

The upgrades for both parts, the ABAP-based server and the Java-based server, have to be synchronized.
For a proper synchronization, it is essential that you first start the upgrade of the ABAP-based server,
that is, you start the upgrade program SAPup. SAPup then detects that there is a Java server installed in
the same system and prompts you to start the Java server upgrade as well.

03/28/2008 PUBLIC 27/102

3 Planning
3.2 Synchronized Upgrade of Dual Stack Systems

SAPup and SAPJup synchronize themselves at three points during the upgrade. That is, if one upgrade
has already reached a synchronization point, but the other has not, the first one waits. Once both
have reached the synchronization point, they can proceed.
The following synchronization points exist:
n At the beginning of the downtime
n When the profiles are about to be changed
n At the end of the downtime
This synchronization ensures that the downtime is as short as possible.

Figure 1: Synchronization Points of Parallel ABAP and Java Upgrade

Upgrade Strategy
For a synchronized upgrade of a dual stack system, you can only use the downtime-minimized upgrade
strategy for the ABAP part.

UME Configuration
During the ABAP upgrade downtime, ABAP user management is not available. If your User
Management Engine (UME) uses ABAP user management, it cannot access any user data during this
period. Therefore the Java upgrade program switches the UME configuration to data source “local”.
This is only a temporary configuration for the duration of the upgrade and is switched back after
the upgrade.

Profile Changes
Depending on the configuration of your source release system, the profile changes are made in
different ways:
n ABAP server Unicode and Java server Unicode
If ABAP and Java server both run Unicode, only one kernel is required during regular production
operation. However during the upgrade, two kernels exist temporarily. A second, validated kernel
is required for ABAP profile changes. This validated kernel is installed automatically during the

28/102 PUBLIC 03/28/2008

3 Planning
3.3 Upgrade Scope for ERP Java Components

kernel switch phase of the ABAP server upgrade. At the end of the downtime, the kernel used by
the Java server, which is the latest available kernel, is copied to the executable directory.
n ABAP server Non-Unicode and Java server Unicode
Since two kernels are installed, no dependencies exist. Make sure that you have both required
SAP kernel DVDs available.

Start and Stop of the SAP System

The ABAP upgrade program changes the profile parameters for starting and stopping the SAP system
so that the Java instance is not started automatically together with SAP Web Application Server ABAP.
The Java upgrade program starts and stops the J2EE Engine with internal commands when required.

Reset of Upgrades
If one upgrade fails, you must reset both upgrades. You must not proceed with only one upgrade
process, since this would lead to an inconsistent system state.

3.3 Upgrade Scope for ERP Java Components

The upgrade program SAPJup detects which ERP Java components are installed in your source
release system. It then deploys the new version of the software during the upgrade. Since the
upgrade program always deploys complete software units, you may have a larger amount of software
components installed in your target release system than in the source release system.
Only valid for: Biller Direct

Biller Direct
Biller Direct 3.0 is upgraded to Biller Direct 6.0. The deployment of the software unit Biller Direct 6.0
includes the SAP Java Data Dictionary 5.0, since it contains the XCM database tables.
End of: Biller Direct

Only valid for: Self Services (XSS)

Self Services (XSS)

In mySAP ERP 2004 the SAP Self Services (XSS) comprises the software components SAP ESS 100, SAP
MSS 100 and SAP PCUI_GP 100. If SAPJup detects one of these components in the source system, it
deploys the following components:
n SAP ESS 600 (SAP Employee Self Service)
n SAP MSS 600 (SAP Manager Self Service)
n SAP PCUI_GP 600 (SAP Floor Plan Manager)
n SAP PSS 600 (SAP Project Self Service)
n SAP ASR 600 (SAP HCM Administrative Services)
n IS-HER-CSS 600 (SAP for Higher Education and Research Industry Solution)

03/28/2008 PUBLIC 29/102

3 Planning
3.3 Upgrade Scope for ERP Java Components

If SAP Enterprise Portal 6.0 and ERP 2004 Business Packages are installed in the same system as SAP Self
Services, the portal is upgraded to SAP NetWeaver 7.0 usage type Enterprise Portal and the ERP 2004
Business Packages are upgraded to ERP 2005 Business Packages (Portal Content).
If no Enterprise Portal and no Business Packages are present on the Self Services host, then SAPJup
automatically installs SAP NetWeaver 7.0 usage type EP Core and ERP 2005 Business Packages (Portal
Content).
For more information about the upgrade strategies for Self Services and Business Packages,
see the Upgrade Master Guide ‒ SAP ERP 6.0, available on SAP Service Marketplace at
[Link] For information about the upgrade of distributed system
landscapes, see SAP Note 879335.

Caution
Be aware of the following restrictions:
n If you upgrade SAP Self Services, you must also upgrade the SAP ERP Central Component (SAP
ECC) to 6.0. You cannot run the upgraded SAP Self Services with SAP ECC 5.0.
n As of SAP NetWeaver 7.0, the wdDoExit() plug is no longer supported for navigating between Web
Dynpro applications within the portal. This might effect Business Packages like Employee Self
Services that are still using this functionality on top of SAP NetWeaver ´04. After upgrade to SAP
NetWeaver 7.0, applications based on Web Dynpro might not work properly. You either need to
use the new navigation mechanism, as described in SAP Note 895224, or run the Web Dynpro
application on a separate SAP NetWeaver ´04 system. For more information, see SAP Note 895224.

End of: Self Services (XSS)

Only valid for: ERP Business Packages (Portal Content)

Business Packages
If the upgrade program detects an Enterprise Portal and Business Packages in the system that you are
going to upgrade, the Enterprise Portal is upgraded to SAP NetWeaver 7.0 usage type Enterprise Portal
and the ERP 2004 Business Packages are upgraded to ERP 2005 Business Packages (Portal Content).
End of: ERP Business Packages (Portal Content)

Only valid for: Extended E-Selling Components (XECO)

Extended E-Selling Components

The Extended E-Selling Components are the successors of SAP Internet Sales R/3 Edition (Internet Sales Web
Application Components) 4.0 and Internet Pricing & Configurator Web Applications (IPC-WAC) 4.0.

Note
SAP Internet Sales (R/3 Edition) has been renamed to SAP E-Commerce for SAP ERP.

30/102 PUBLIC 03/28/2008

3 Planning
3.3 Upgrade Scope for ERP Java Components

If SAPJup detects one of these predecessor components, it deploys the software unit Extended E-Selling
Components, which includes the following components:
n SAP Shared Java Applications 5.0
n SAP Java Data Dictionary 5.0

Note
SAPJup does not deploy the following software components:
n CRM Java Components 5.0
n CRM Java Web Components 5.0
n CRM IPC Mobile 5.0
n SAP Shared Java Components 5.0
n SAP Shared Web Components 5.0
n Apache Jakarta Struts 1.1
n Tealeaf 4.5
These software components are not required to run the applications. They are only required for
development purposes in the NetWeaver Development Infrastructure.

Caution
If you want to run SAP E-Commerce 5.0 with a backend release between SAP R/3 4.6C and SAP
ECC 5.0 and want to use the Internet Pricing and Configurator, you have to install SAP NetWeaver
7.0 Application Server ABAP including SAP Application Platform (SAP AP). This is due to the
architectural changes of the Internet Pricing and Configurator, which is no longer a separate server,
but part of SAP AP and processed on application servers.
To install SAP NetWeaver 7.0 Application Server ABAP and SAP AP, proceed as described in the
following documentation:
n Installation Guide ‒ SAP NetWeaver 7.0 <Technology> on <Operating System>: <Database>
n SAP Note 848412: SAP Application Platform 7.00: add-on installation
For general information, see SAP Note 848416 Overview: Notes about SAP Application Platform.
For information about the required configuration, see the documentation SAP E-Commerce 5.0 for mySAP
ERP — IPC Configuration Guide on SAP Service Marketplace at [Link]
SAP ERP 6.0 Installation .
End of: Extended E-Selling Components (XECO)

03/28/2008 PUBLIC 31/102

3 Planning
3.4 Upgrade Scope for SAP NetWeaver

Only valid for: Learning Solution (Content Player)

Learning Solution (Content Player)

Learning Solution 3.0 is upgraded to Learning Solution 6.0, which does not include any further
components.
End of: Learning Solution (Content Player)

SAP NetWeaver
The underlying technology for ERP Java Components is the SAP NetWeaver Application Server Java
(AS Java). For more information about SAP NetWeaver AS Java, see section Upgrade Scope for SAP
NetWeaver [page 32]. This section also contains information about further NetWeaver software units.
Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Enterprise Portal (EP);EP

Core (EPC);Mobile Infrastructure (MI);Process Integration (PI)

3.4 Upgrade Scope for SAP NetWeaver

SAP NetWeaver is the underlying technology of your SAP Business Suite application.
The upgrade program detects which software is installed in the source release system and maps
it to the SAP NetWeaver 7.0 usage types. SAPJup then upgrades your system to a system with
the determined usage types. AS Java is the basis for all other usage types. For more information
about usage types, see the Master Guide for SAP NetWeaver 7.0 available on SAP Service Marketplace at
[Link] Installation .
Application Server (AS Java)
Previously separately installable components, such as the Internet Knowledge Servlet, BI Universal
Data Integration, BI Meta Model Repository and Adobe Document Services have been integrated into
the Application Server Java. In detail, AS Java comprises the following:
n Lifecycle Management Tools
n SAP CAF-UM
n User Management Engine (UME) Administration
n SAP CAF
n SAP Internet Knowledge Servlet (IKS)
n SAP BI Universal Data Integration (BI UDI)
n SAP BI Meta Model Repository (MMR)
n Adobe Document Services
n Java Support Package Manager
n SAP Tech S Offline
n SAP Java Tech Services
n SAP J2EE Engine
n SAP J2EE Engine Core

32/102 PUBLIC 03/28/2008

3 Planning
3.4 Upgrade Scope for SAP NetWeaver

n SAP Startup Framework

n Java Log Viewer
n J2EE Engine Core Tools
n J2EE Engine Base Tables
n SAP Software Delivery Manager
n SAP Kernel
Only valid for: BI Java Components (BI-Java)

Business Intelligence Java Components (BI-Java)

Note
Usage type BI-Java requires Enterprise Portal.

BI-Java comprises the following:

n BI Reporting and Planning
n BI WebDynpro ALV
n BI Information Broadcasting
n BI Web Applications
n BI Base Services
End of: BI Java Components (BI-Java)

Only valid for: Process Integration (PI)

Process Integration (PI)

PI comprises the following:
n XI Content SAP_Basis 7.00
n XI Adapter Framework Core 7.00
n XI Adapter Framework 7.00
n XI Tools 7.00
End of: Process Integration (PI)

Only valid for: EP Core (EPC)

EP Core
EP Core comprises the following:
n Portal 7.00
n Portal Framework 7.00
n Portal Core Services 7.00
n Portal Web Dynpro 7.00
n Universal Worklist & Collaboration Process Engine 7.00
n CAF EU 7.00
End of: EP Core (EPC)

03/28/2008 PUBLIC 33/102

3 Planning
3.4 Upgrade Scope for SAP NetWeaver

Only valid for: Enterprise Portal (EP)

Enterprise Portal (EP)

EP comprises the following:
n PDK Portal Services 7.00
n SAP CAF-KM 7.00
n Lifecycle Management Portal 7.00
n RTC Stream 7.00
n RTC 7.00
n KMC Collaboration 7.00
n KMC Content Management 7.00
n KMC Base Components 7.00
n Visual Composer Base 7.00
n Visual Composer Framework 7.00
n Visual Composer Flex 7.00
n Visual Composer GP Kits 7.00
n Visual Composer XX Kits 7.00
n Web Dynpro Extensions 7.00
End of: Enterprise Portal (EP)

Only valid for: Mobile Infrastructure (MI)

Mobile Infrastructure (MI)

MI comprises the following:
n MI Administration 7.00
n MI Laptop 7.00
n MI Drivers 7.00
n MI Client 7.00
End of: Mobile Infrastructure (MI)

Only valid for: Development Infrastructure (DI)

Development Infrastructure (DI)

DI comprises the following:
n DI Design Time Repository 7.00
n DI Component Build Server 7.00
n DI Change Management Server 7.00
n DI Build Tool 7.00
End of: Development Infrastructure (DI)

End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Enterprise Portal (EP);EP Core

(EPC);Mobile Infrastructure (MI);Process Integration (PI)

34/102 PUBLIC 03/28/2008

3 Planning
3.5 Planning the Upgrade of Non-Standard SAP Systems

3.5 Planning the Upgrade of Non-Standard SAP Systems

The following section provides an overview of how you can upgrade SAP systems that you have
enhanced with custom developments or third-party software or SAP systems where you have
modified SAP software.
Depending on the type of enhancement or modification, several cases can be distinguished, which are
outlined below.

Process
n You have modified SAP software or created your own software components, using the SAP
NetWeaver Development Infrastructure (NWDI).
For information about the upgrade of systems that are configured as runtime systems of the NWDI
and the modification adjustment, see Upgrade of NWDI-Driven System Landscapes [page 36].
n You have modified SAP software without using the NWDI.
If you have modified Software Components (SC) and also modified the name of the component
vendor, SAPJup detects that these are modified components. In the configuration module of
PREPARE, the operation Scan inbox is assigned to these components. This enables you to provide
adjusted SCAs that are then deployed during the upgrade. Proceed as follows:
1. Compare your modified software components with the new SAP versions of the software
components.
2. Redo the modifications where necessary and create your own SCAs.
3. Copy the SCAs to the EPS inbox of your transport directory.
4. In the PREPARE module Configuration, specify that SAPJup deploys these SCAs.

Caution
If you have modified Software Components without modifying the name of the component
vendor, SAPJup is not able to detect that you have modified the component. In the PREPARE
module Configuration, the operation Scan inbox is not offered for these components. You lose your
modifications if you proceed.
For information about how you can upgrade these components, see SAP Note 918370.

n You have installed third-party components in your system or you have installed custom
developments that have been developed without using the NWDI.
SAPJup assigns the operation Scan inbox to these components during PREPARE.
You have to provide new versions of these components, that is, versions that are valid for the
target release. Put them into the EPS inbox and specify during PREPARE that SAPJup deploys
these new versions.

03/28/2008 PUBLIC 35/102

3 Planning
3.6 Upgrade of NWDI-Driven System Landscapes

3.6 Upgrade of NWDI-Driven System Landscapes

If you want to upgrade a system that is part of a system landscape controlled by SAP NetWeaver
Development Infrastructure (NWDI) you have to note some special properties. The NWDI has
special knowledge about the software component archives (SCAs), for example about the storage
of design time objects in the Design Time Repository, or about the upgrade sequence of software
applications in a system landscape.
The maintenance process for NWDI-driven system landscapes is described in the current online
documentation available on SAP Help Portal at [Link] SAP NetWeaver 7.0
Library <Language> SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management
by Key Capability Software Life Cycle Management Software Logistics Working with the Development Infrastructure
Administration of the Development Infrastructure Maintenance of an NWDI-Driven System Landscape .
The online documentation focuses on the import of Support Packages into the runtime systems.
However, the upgrade process runs on the same principle.
Below, a rough overview of the steps from an upgrade perspective is given.
The upgrade process for development and consolidation systems differ from the upgrade of quality
assurance and production systems. In the development and consolidation system you can adjust
the new SAP component versions to your modifications and build software component archives
(SCAs). The adjusted SCAs are then deployed during the upgrade of the quality assurance and
production system.

Caution
You can only upgrade a quality assurance or production system if you provide adjusted SCAs for all
components that you modified in the source release.

Prerequisites
n You have upgraded the NWDI system (the central system that controls the runtime systems) to at
least SAP NetWeaver 7.0 Support Package 05.
n The runtime systems have at least SAP NetWeaver ´04 Support Package level 16.
n You have made the preparations as described in the SAP NetWeaver Library documentation under
Maintenance of an NWDI-Driven System Landscape Preparing the Systems .

Process
1. During PREPARE you are asked whether the system that you want to upgrade is configured as a
runtime system in an NWDI track. If yes, you have to specify whether the system is a development
system (DEV), consolidation system (CONS), quality assurance system (QA), or production
system (PROD).
2. Upgrade of Development and Consolidation System

36/102 PUBLIC 03/28/2008

3 Planning
3.7 Upgrade of High Availability Systems

a) After you have entered the path to the NWDI transport directory, SAPJup copies all SAP
components included in the shipment to this directory.

Note
While browsing for the NWDI transport directory in the Select Transport Directory dialog box, you
may encounter an error message in a Windows ‒ No Disk dialog box. In this case, in the Windows ‒
No Disk dialog box choose Cancel and continue with the selection of the transport directory.

b) Any components that you have modified in the source release have the status Managed by NWDI
on the selection screen for the target release components (PREPARE module Configuration).
These components are not deployed during the upgrade.
c) After the upgrade, you can take the components from the NWDI transport directory and
perform the modification adjustment by using the NWDI. Then, deploy the adjusted software
components (SCs) to the upgraded development or consolidation system.
d) In the consolidation system, you assemble the modified SCs as software component archives
(SCAs).
3. Upgrade of Quality Assurance and Production System
During the upgrade of quality assurance and production systems, SAPJup deploys the modified
components that you have built in the consolidation system. In the PREPARE module Configuration,
all modified components have the status “Scan inbox” on the selection screen for the target release
components. You have to select the new versions from the inbox and to rebuild the component
list. The modified components are then included in the deployment.

3.7 Upgrade of High Availability Systems

High availability systems use switchover clusters to guarantee the availability of the system. Critical
software units such as the SAP central services instance (SCS) and the database instance are replicated
across multiple hosts in a cluster. When a primary node fails, proprietary switchover software
automatically switches the failed software unit to another hardware node in the cluster. For more
information about high availability, see the Technical Infrastructure Guide — SAP NetWeaver 7.0 (2004s),
which is available on SAP Service Marketplace at [Link]
The upgrade of high availability systems differs from the upgrade of normal systems since SAPJup,
which runs on the central instance host, cannot control processes on the remote (cluster) SCS.
The upgrade process of a high availability system is as follows:
1. SAPJup checks whether the central file share (normally /sapmnt/<SAPSID>) is located on
the central instance host. If not, it assumes that the upgrade is running in a high availability
environment.
2. At the beginning of the downtime, you have to stop the remote SCS manually.
3. During the upgrade, SAPJup temporarily installs an additional SCS on the central instance host.

03/28/2008 PUBLIC 37/102

3 Planning
3.8 Checking the Source Release

4. SAPJup updates the profiles and the kernel on the central instances and all kernels that are located
in the central file share.
5. SAPJup removes the temporary SCS.
6. You have to start the remote SCS manually when the downtime has finished.
7. If you are running a heterogeneous cluster (where the remote SCS is running on an operating
system other than the central instance and therefore the kernel of this instance is not located in
central file share,) you have to update this kernel manually.

3.8 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 Upgrade - Step by Step [page 19].

Procedure
To determine the source release and Support Package level, proceed as follows:
1. Go to the J2EE Engine Start Page: [Link] name>:<port>/[Link]
2. Choose System Information.
3. Log on to the J2EE Engine:
n If you have a standalone installation, log on as user Administrator.
n 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.

3.9 Upgrade of the Operating System and Database System:

Overview

When you upgrade your SAP system, you may have to update your operating system and database
to a new version.
For detailed information about which versions are currently supported, see SAP Service Marketplace
at [Link] On the same page, you can find a link to the general
Product Availability Matrix.
PREPARE only checks the minimum versions required to run the PREPARE and the upgrade.
If you need to upgrade an operating system or database, or migrate a database, then the timing and
the sequence of the individual upgrades is of great importance. The procedure differs according to
the database you use. In the following, we describe the main process steps for upgrading the operating
system and database system for each database.

38/102 PUBLIC 03/28/2008

3 Planning
3.9 Upgrade of the Operating System and Database System: Overview

Process
For information about the required versions, see Upgrade ‒ Step by Step [page 19].
Only valid for: IBM DB2 for Linux and UNIX and Windows

IBM DB2 for Linux, UNIX, and Windows

1. Migrate the database to the required version if you have not already done so. The migration guide
is a PDF document on the data carrier that contains the required version of the database.
2. AIX / Solaris: Migrate the database to 64 bit if you have not already done so.
The database instance and the SAP kernel must be migrated to 64 bit. For more information,
see SAP Note 356828.
3. Start PREPARE and analyze the results.
4. Upgrade the system.
End of: IBM DB2 for Linux and UNIX and Windows

Only valid for: IBM DB2 for z/OS

IBM DB2 for z/OS

Make sure that you meet the following requirements before you start PREPARE for the first time:
Required PTFs and APARs: SAP Note 81737 (APAR list) contains information about the PTFs that you
need to import before the upgrade. A PTF check tool is available for all source releases. This tool is
described in SAP Note 183311. A missing PTF can lengthen the runtime of the upgrade significantly.
End of: IBM DB2 for z/OS

Only valid for: MaxDB

SAP MaxDB
Prerequisite for PREPARE: If the database server and the central instance are not identical, install
the latest DB client software on the central instance. For information about the procedure, see
the document Upgrade to SAP MaxDB Version <x>: <OS> on SAP Service Marketplace at
[Link] Other Documentation Database Upgrades SAP MaxDB .
Proceed as follows:
1. If you have not already done so, upgrade SAP MaxDB to at least the minimum required version.
For information about the procedure, see the document Upgrade to SAP MaxDB Version <x>: <OS>.
2. Start PREPARE and analyze the results.
3. If necessary, upgrade the operating system.
Repeat the PREPARE module General Checks and complete the module successfully.
4. Upgrade the system.
End of: MaxDB

03/28/2008 PUBLIC 39/102

3 Planning
3.10 Checking the Java Development Kit Version and Settings

Only valid for: Oracle

Oracle
Proceed as follows:
1. Install the Oracle client software for the target release. For more information about this procedure,
see SAP Note 819829.
2. If necessary, upgrade the operating system.
3. Start PREPARE and analyze the results.
4. If you have not already done so, migrate the Oracle database to at least the minimum required
version as described in the documentation Migrating/Upgrading to Oracle Version <x>: <OS>.
5. Upgrade the system.
End of: Oracle

3.10 Checking the Java Development Kit Version and Settings

SAP NetWeaver AS Java requires a specific version of the Java Development Kit (Java™ 2 SDK,
Standard Edition ‒ JDK). In addition, SAP NetWeaver 7.0 may require different memory and Java VM
settings for your JDK than those maintained when you installed your source release system. You
have to adjust these settings before the upgrade.

Checking the JDK Version

1. Check the JDK versions that are released for SAP systems on SAP Service Marketplace at
[Link] Product Availability Matrix SAP NETWEAVER SAP
NETWEAVER 7.0 JSE Platforms .
2. Check the installed JDK version by using the command java –version.
3. If necessary, download and install the required JDK version. For more information, see SAP Note
723909.
4. For systems with strong encryption only: If you have installed a new JDK version, update the
JCE jurisdiction policy files.
The JCE jurisdiction policy files are not copied automatically to the new JDK directory. You
have to perform the following steps manually:
a) Download the JCE jurisdiction policy files from your JDK provider. For more information,
see your JDK provider´s document.
b) Copy the JCE jurisdiction policy files into the JDK directory.
c) Unpack the zip or tar file to the <jdk_dir>/jre/lib/security directory. For additional
steps, see your JDK provider´s document.
5. Change the configuration of the J2EE Engine as described in SAP Note 718901. Additionally, make
sure that the <JAVA_HOME> environment variable of the user who wants to run the administration

40/102 PUBLIC 03/28/2008

3 Planning
3.11 Checking the Software Delivery Manager Version

and life-cycle tools (for example, the Visual Administrator, Config Tool, SDM, JSPM) contains
the path to the Java Development Kit (JDK) of the J2EE Engine.

Checking the Memory and Java VM Settings

For information about memory requirements and Java VM settings, see SAP Note 723909 and the SAP
Notes for each supported JDK referenced within this SAP Note.

3.11 Checking the Software Delivery Manager Version

The upgrade requires Software Delivery Manager version 6.40 Support Package 14. If you have a lower
SDM version, you need to update the SDM before you start PREPARE.

Procedure
1. Download the SDM Support Package from SAP Service Marketplace:
a) Enter the SAP Service Marketplace at [Link]
b) In the navigation area on the left, choose Entry by Application Group.
c) On the Support Packages and Patches screen, choose SAP NetWeaver SAP NETWEAVER SAP
NETWEAVER04 Entry by Component Application Server Java SAP J2EE Engine 6.40 #OS
independent .
The appropriate files are displayed on the Downloads tab page.
d) Select the required file named J2EERT<SP_Number>_<Patch_level>-<Counter>.SAR and save it
to your system.
e) To extract [Link], enter the following command: [Link] -xvf
J2EERT<SP_Number>_<Patch_level>-<Counter>.SAR J2EE-RUNT-CD/SDM/[Link] .
2. Update SDM:
a) Go to the SDM installation directory (default directory is
usr/sap/<SAPSID>/<Instance>/SDM/program).
b) Stop SDM by entering the following command:
./[Link]
c) Set SDM to operate in standalone mode by entering the following command:
./[Link] jstartup mode=standalone
d) Copy [Link] to the temporary folder <sdm_temp>.
e) In <sdm_temp> extract [Link] with the following command:
jar -xvf [Link]
f) Execute the script ./[Link].
g) When prompted, enter the SDM installation directory.
In a standard installation, this is usr/sap/<SAPSID>/<Instance>/SDM/program.
h) Switch to the SDM installation directory.
i) Set SDM to operate in the integrated mode by entering the following command:

03/28/2008 PUBLIC 41/102

3 Planning
3.12 Downloading Support Package Stacks

./[Link] jstartup mode=integrated

j) Start SDM by entering the following command:
./[Link]

3.12 Downloading Support Package Stacks

Note
This upgrade release must be used with content that incorporates SAP NetWeaver 7.0 (but not an
SAP enhancement package for SAP NetWeaver 7.0).
If you want to apply an SAP enhancement package for SAP NetWeaver 7.0, you must use the Upgrade
Master DVD supplied with the relevant SAP NetWeaver 7.0 enhanced content, that is, with the target
SAP enhancement package for SAP NetWeaver 7.0.

You can include Support Packages for the target release in the upgrade. This means that these
Support Packages are imported during the upgrade and your system is at the most up-to-date Support
Package level after the upgrade. To prepare for this step, you must download the latest released
Support Package Stack available on SAP Service Marketplace by using the Maintenance Optimizer in
SAP Solution Manager. For detailed information about the Maintenance Optimizer, see SAP Help
Portal at [Link] SAP Solutions SAP Solution Manager SAP Solution Manager <Release>
<Language> Change Management Maintenance Optimizer .
The target release that you want to upgrade to, must have an equivalent or higher Support Package
level than the source release. Support Packages for the same product, but different releases contain the
same corrections. For example, Support Package Stack 14 for SAP NetWeaver ´04 contains the same
corrections as Support Package Stack 05 for SAP NetWeaver 7.0. This means that they are equivalent. If
your source release has a certain Support Package level, you can only upgrade to a target release that
has the equivalent Support Package level. You either have to use a Java DVD that contains the correct
equivalent (or higher) Support Package level or you must include Support Packages of the correct
level for all components during the BIND_SUPPORT_PACKAGES phase in PREPARE. For information
about which SAP NetWeaver 7.0 Support Package level you need to include, see SAP Note 866472.
When you run PREPARE, you are asked to specify the Support Package Stacks that you want to include
in the upgrade. In the Configuration module, the Select Package Type dialog screen is displayed and allows
you to choose from the following options:
n The Support Package Stack option enables you to update the Support Packages by applying a Support
Package Stack (SP Stack).
SP Stacks are sets of Support Packages and patches for the respective product version that must
be used in the given combination. For more information regarding SP Stacks, see SAP Service
Marketplace at [Link]
n The Single Support Packages and Patches option allows you to update only particular software
components if you do not want to apply complete SP Stacks. This is generally not recommended

42/102 PUBLIC 03/28/2008

3 Planning
3.13 Downloading Enhancement Packages

because using this method can bring your system to inconsistent state. However if you explicitly
need to update only some of the components, you can use this option.
n The option Do not apply Support Packages allows you to skip this step if there are no Support Packages
that you want to apply.

Note
We recommend that you always upgrade to the latest Support Package level.

Prerequisites
n The <sapsid>adm user has Read permissions for the global EPS inbox directory
/usr/sap/trans/EPS/in.
n There is enough free disk space available. For more information, see Space Requirements in the File
System and the Database [page 46].
n You have updated your Download Manager to the latest available version. For more information,
see SAP Note 1135313.

Procedure
1. Check SAP Service Marketplace at [Link] SP Stack Information SP
Stack Schedule for the latest Support Package Stack.
2. If it does not yet exist, create the directory /usr/sap/trans/EPS/in.
3. Download the Support Package files (Software Component Archives ‒ SCAs) to the directory
/usr/sap/trans/EPS/in using the Maintenance Optimizer in SAP Solution Manager.

3.13 Downloading Enhancement Packages

To download SAP enhancement packages that you want to include in the upgrade, you use the
Maintenance Optimizer in SAP Solution Manager. The Maintenance Optimizer supports you in
selecting and downloading all required enhancement package files. In addition, the Maintenance
Optimizer generates an enhancement package stack configuration file and provides it to the upgrade
program using the EPS inbox of the transport directory. The upgrade program then uses this
information for installing the enhancement package files.

Prerequisites
n You have identified which technical usages you want to implement. For more information, see the
document Master Guide ‒ SAP enhancement package 3 for SAP ERP 6.0 and SAP Note 1083576.
n You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP
Help Portal at [Link] SAP Solutions SAP Solution Manager SAP Solution Manager

03/28/2008 PUBLIC 43/102

3 Planning
3.13 Downloading Enhancement Packages

<Release> <Language> Change Management Maintenance Optimizer Planning and Monitoring Product
Maintenance and also in section Automatically Calculating Product Maintenance Files.
n You have assigned an ABAP system to a product maintenance procedure. This system is now
automatically considered to be relevant for the upgrade.
n In SAP Solution Manager System Landscape (transaction SMSY), you have identified as relevant the
Java instances that are installed in the source release system and that are relevant for the upgrade.
n You have familiarized yourself with SAP Note 1122966 and the relevant Notes that are referenced in
this Note.

Procedure
1. Start SAP Solution Manager using the transaction solution_manager. To start the Maintenance
Optimizer, choose Operations Change Management Maintenance Optimizer .
2. In the Maintenance Optimizer, choose the solution for which you want to download enhancement
package files.
3. Choose Create New Maintenance Transaction.
4. Select the product version for which you want to include an enhancement package installation
in the upgrade.
The Maintenance Optimizer displays all the systems assigned to the selected product version.
5. Select the checkbox for the systems for which you want to include the enhancement package
installation in the upgrade and choose Continue.
6. On the subsequent screen, select the Upgrade option and then choose Find Download Files.
The Maintenance Optimizer displays all installable enhancement packages for the intended
product version.
7. Select the product version (enhancement package) and the target Support Package Stack level.
8. Select the technical usages that you want to update with the enhancement package.

Note
You require at least the same Java instances that are already installed and used in your source
release system. Only those technical usages that are appropriate to be included in your upgrade
are selectable. All highlighted Java instances are automatically included later in the installation.

9. Choose Find Download Files for the Stack Version.

The Maintenance Optimizer displays the product maintenance files in three successive lists.
10. Select the required files from the displayed lists:
n The first list shows all files that are dependent on the type of your operating system and system
database.
Select those files that correspond to the combination of your operating system and database.
Select also the database-independent files (under DBINDEP).

44/102 PUBLIC 03/28/2008

3 Planning
3.14 Required DVDs

n You get to the second list by choosing Continue. This list displays all Support Package files that
are not assigned to the selected Support Package Stack. You must check whether the Support
Packages listed here are suitable for your product maintenance procedure.
Deselect the checkbox for the files for the following components:
l Components for which you do not want to download Support Packages
l Components that you do not want to include in the installation
n You get to the third list by choosing Continue. The list displays all product maintenance files that
are part of the selected Support Package Stack.
Ensure that all files that are assigned to the Support Package Stack are selected here. Files that
are not selected will not be included later in the download.
11. Choose Continue. To download the files, select whether you want to download them with the
Software Lifecycle Manager (SLM) or with the Download Basket and then choose Select Download
Type.
12. Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket. A dialog window opens and displays all files.
13. Confirm the download for all files.
14. Open your SAP Download Manager and download the files to the global EPS inbox directory
/usr/sap/trans/EPS/in.

Note
The enhancement package stack configuration file is being automatically generated and saved
to the global EPS inbox directory.

3.14 Required DVDs

You require the following DVDs for the upgrade:

n Upgrade Master DVD for your SAP application
n SAP Kernel DVD for SAP NetWeaver 7.0
n Java DVD for SAP NetWeaver 7.0 and for SAP Business Suite 2005
For the correct labels of the data carriers, see the Media List, which is included in the Master Guide for
your SAP application.

3.15 Stopping SAP MMC and SDM GUI

You must stop SAP Management Console (SAP MMC) and the Software Deployment Manager (SDM)
GUI at the latest when the actual upgrade starts. When you plan your upgrade, take into account

03/28/2008 PUBLIC 45/102

3 Planning
3.16 Space Requirements in the File System and the Database

that both programs will not be available for a certain period of time. However, SAP MMC and SDM
can still run while the PREPARE phases are running.

Procedure
Close the SAP MMC application and the SDM GUI now or when the upgrade program prompts you
to stop both programs at the required point in time.

3.16 Space Requirements in the File System and the Database

Before the upgrade, make sure that there is enough free space available in the file system and in the
database of the system that you want to upgrade.
In the file system, you require the following free space:
n Upgrade directory: at least 3.5 GB
n Directory usr/sap/<SAPSID>: at least 5 GB
The database space requirements largely depend on the software units that are installed in your
system.
For more information, see SAP Note 995762.

3.17 Using SAP Solution Manager

Using SAP Solution Manager throughout the life cycle of your SAP application leads to a faster
implementation and more efficient operation of the SAP application by providing all implementation
and upgrade content for commonly used standard processes. In addition, projects become more
transparent, having up-to-date central project documentation all in one place at any point in time.
For technical reasons, you require an SAP Solution Manager system to upgrade your SAP application.
During the upgrade process you are prompted to enter an SAP Solution Manager key. Without
this key, the upgrade process cannot continue.

Note
You may generate all needed SAP Solution Manager keys [page 52] for your entire system landscape
(development, quality assurance, and production system) in one SAP Solution Manager system.
If you plan to install several solution landscapes (for example, in different countries), one SAP
Solution Manager system is still sufficient.

The minimum release and Support Package level of SAP Solution Manager is SAP Solution Manager
3.2 SP 8.
For more information, see SAP Note 805390 and SAP Service Marketplace at
[Link]

46/102 PUBLIC 03/28/2008

3 Planning
3.17 Using SAP Solution Manager

Procedure
1. If you have not been using SAP Solution Manager yet, install it as described in the document
Installation Guide ‒ SAP Solution Manager <Release> <Operating System> - <Database>. You can find
the document on SAP Service Marketplace at [Link] SAP
Components SAP Solution Manager Release <x> .
2. Make sure that the SAP system for which you want to perform an upgrade is known to your
SAP Solution Manager.
To create your SAP system in the Solution Manager System Landscape transaction, proceed as follows:
a) Log on to your SAP Solution Manager system.
b) Call transaction SMSY (Solution Manager System Landscape).
c) Select the landscape component Systems and choose Create from the context menu.
d) In the next dialog box, enter the SAP system ID as the system name.
e) Choose a product and a product version from the input help.
f) Save your entries.

03/28/2008 PUBLIC 47/102

This page is intentionally left blank.
4 Preparation

4 Preparation

This part of the documentation contains information about the preparations that you need to make
before you upgrade your system.
You can prepare for the upgrade while the system is in production operation. Careful preparation
of the upgrade is the best guarantee that it will run without errors. The PREPARE program supports
you here by making most of the necessary checks automatically. PREPARE runs for approximately
one hour.
Only valid for: Extended E-Selling Components (XECO)

n Preparing the Upgrade of Internet Sales (R/3 Edition) Web Application Components [page 49]
End of: Extended E-Selling Components (XECO)

n Performing a Database Backup [page 53]

Only valid for: Enterprise Portal (EP)

n Cleaning Up the Universal Worklist Cache [page 51]

End of: Enterprise Portal (EP)

n Checking the C++ Runtime on AIX Operating System [page 51]

n Undeploying the Software Component NWMADMIN [page 52]
n Generating the SAP Solution Manager Key [page 52]
n Creating the Upgrade Directory [page 53]
n Starting PREPARE [page 54]
n Starting the SDTGui [page 56]
n Choosing the PREPARE Modules [page 56]
n Making Entries for the Initialization and Extraction Modules [page 57]
n Making Entries for the Configuration Module [page 59]
n Executing the General Checks and Finalization Modules [page 62]
Only valid for: Extended E-Selling Components (XECO)

4.1 Preparing the Upgrade of Internet Sales (R/3 Edition)

Web Application Components

The default upgrade process is to first copy your SAP Internet Sales (R/3 Edition) system and then
upgrade this copy to SAP E-Commerce 5.0. If you follow this procedure, your source release system is

03/28/2008 PUBLIC 49/102

4 Preparation
4.1 Preparing the Upgrade of Internet Sales (R/3 Edition) Web Application Components

kept as a backup. If you do not want to create a system copy, you have to make sure that the XML files
that contain the shop data are not stored in a directory within SAP Web AS.

Note
During the upgrade, the Internet Sales Web Application Components 4.0 are undeployed.

Creating a System Copy

Create a system copy as described in the documentation Homogeneous and Heterogeneous System Copy for SAP
Systems based on SAP Web Application Server Java 6.40 SR1.
The documentation is available on SAP Service Marketplace at
[Link] SAP NetWeaver Releases ´04
Installation SAP Web AS SAP Web AS 6.40 SR1 and Related Documentation .

Preserving Shop Data

In Internet Sales (R/3 Edition) 4.0, the data of the Shop Management Web Application was stored
in XML files in the file system. In SAP E-Commerce 5.0, this data is stored in the database of SAP
NetWeaver AS Java. After you have performed the upgrade, you have to import the XML files
manually (see section Upgrading the Shop Management Data [page 79]).

Note
You only have to perform the steps below if you want to upgrade your system without performing a
system copy first.

Before you start the upgrade, make sure that the XML files that contain the shop data are not stored
in a directory within SAP Web AS. The path to these files is defined in the Extended Configuration
Management (XCM) of the Shop Management Application. Perform the following steps to make sure
that your data is not deleted during the upgrade:
1. Log on to the XCM of the Shop Management Web Application by entering
[Link]
2. Choose Start Components Shop and select the component used in your application
configuration.
3. The parameter Object-Path contains the path to the XML files.
4. If the path leads to a directory within SAP Web AS Java
(/usr/sap/<SAPSID>/<instance_name>/<...>), then copy all files to a directory outside of Web
AS Java to make sure that the files are not deleted during the upgrade.
End of: Extended E-Selling Components (XECO)

50/102 PUBLIC 03/28/2008

4 Preparation
4.2 Performing a Database Backup

4.2 Performing a Database Backup

Before you start PREPARE, you must create a backup of your database to make sure you can restore the
database in case the upgrade fails for any reason.

Procedure
For detailed information about how to perform a database backup, see the manual for your database.
If you are upgrading a dual stack system (ABAP + Java), see the upgrade guide for ABAP systems for
information about strategies for archiving and backing up your system.
Only valid for: Enterprise Portal (EP)

4.3 Cleaning Up the Universal Worklist Cache

Before the upgrade, you must clean up the UWL cache since otherwise the UWL database upgrade fails.

Prerequisites
This step is only required if Knowledge Management and Collaboration is installed in your source
release system.

Procedure
1. Log on to the Portal with role Super Administrator.
2. Choose System Administration System Configuration Universal Worklist and Workflow Universal Worklist
Administration .
3. Choose All Systems from the drop-down list and then Clear Cache.
End of: Enterprise Portal (EP)

4.4 Checking the C++ Runtime on AIX Operating System

To run Adobe Document Services a C++ runtime is required. Use the following commands to check
whether C++ Set has been installed, and if so, which level has been installed:
n lslpp -l [Link]
The value for parameter [Link] must be at least [Link].
n lslpp -l [Link]
The value for parameter [Link] must be at least [Link].
If the C++ set has not been installed or if the version is incorrect, download the correct version from
your country version of the IBM AIX Fix Distribution Web page or from the United States Web

03/28/2008 PUBLIC 51/102

4 Preparation
4.5 Undeploying the Software Component NWMADMIN

page [Link] Use program smit to install the

C ++ Set as user root. You can also download the "Base Level File Set" ([Link].[Link])
from the same location.

4.5 Undeploying the Software Component NWMADMIN

If your source release system has the Support Package level 6.40 SP 15 or higher, you have to undeploy
the software component NWADMIN before you start PREPARE.

Procedure
1. Log on to the SAP system.
2. Start the SDM GUI and logon to the SDM Server.
3. Choose the Undeployment tab page.
4. Select the following components:
n tc/mobile/admin/ea
n tc/mobile/admin/mds/service
n tc/mobile/admin/services
n tc/mobile/admin/ui
n tc/mobile/admin/ump
n tc/mobile/monitor/ui
5. Choose Start Undeployment and confirm the undeployment.

4.6 Generating the SAP Solution Manager Key

In the Initialization module, phase SOL_MAN_KEY_CHECK, you have to enter a key generated by SAP
Solution Manager to be able to proceed with the upgrade.

Prerequisites
The minimum release and Support Package level of SAP Solution Manager is SAP Solution Manager
3.2 SP 8.

Procedure
1. In your SAP Solution Manager system, call transaction SMSY.
The Solution Manager System Landscape screen appears.
2. Depending on the SAP Solution Manager release you are using, choose Landscape Component Other
Object or System Landscape Other Object .
3. Set the System indicator.

52/102 PUBLIC 03/28/2008

4 Preparation
4.7 Creating the Upgrade Directory

4. From the input help, choose the system for which you want to perform the upgrade.
5. Choose Generate Installation/Upgrade Key.
6. Enter the requested information.
If necessary, change the default values.
7. Choose Generate Key.
The system displays the key.

4.7 Creating the Upgrade Directory

The SAP system is upgraded using the upgrade directory, which can be a softlink to another physical
directory. It is divided into subdirectories that can also be softlinks.
The standard path for the upgrade directory is /usr/sap/jupgrade on the host with the central
instance. You can give it a different name if you want.
For more information, see Using a Different Upgrade Directory below.
The PREPARE program needs the upgrade directory before the actual upgrade since it copies data and
programs into this directory.

Caution
Before you start the new upgrade, the directory must exist but be empty.

Prerequisites
n The upgrade directory must be installed on the host with the central instance.
n Make sure that there is enough free disk space for the upgrade directory. This space is required for
the upgrade and the logs and is distributed among several subdirectories. For an estimation of the
disk space needed for the upgrade directory, see section Space Requirements in the File System and in the
Database [page 46]. The size may vary by up to 25%, depending on your database and source release.
We recommend that you create the directory with more space if your systems include extensive
customer developments or large amounts of individual documentation. If you want to include
Support Packages in the upgrade, you also need to make these directories larger.

Upgrade Directory Does Not Exist

1. Log on to the central instance as user root.
2. Create the upgrade directory as follows:
mkdir <upgrade directory>
cd <upgrade directory>
chown <sapsid>adm.
chgrp sapsys.
chmod 755.

03/28/2008 PUBLIC 53/102

4 Preparation
4.8 Starting PREPARE

The owner of the upgrade directory and of all the subdirectories must be the SAP system
administrator <sapsid>adm.

Upgrade Directory Already Exists

1. Check whether data from the previous upgrade is still in the upgrade directory. If this is the case,
we recommend that you back up at least subdirectory log for documentation purposes.
2. Log on as user <sapsid>adm.
3. Switch to the upgrade directory and delete all the subdirectories:
cd <upgrade directory>
ls -ld * (for checking purposes)
rm -rf *

Caution
If you have created softlinks to subdirectories, this deletes the links but not the content of the
directories you linked to. To delete these directories as well, you must delete the directories
individually and redefine the links. Copy any manually created directories before you delete them,
if you want to keep them.

Using a Different Upgrade Directory

You can use an upgrade directory other than the default upgrade directory. This is useful if you have
multiple SAP systems on a single host and you want to upgrade them all to a new release.

Note
Do not include blanks in the upgrade directory name. The upgrade program cannot handle paths
containing blanks.

To use an upgrade directory other than the default one, you have to specify the directory when you
start PREPARE for the first time [page 54].
If you want to start PREPARE again or want to start the upgrade, you do this from within the upgrade
directory and thus do not need to specify the directory again (see Starting PREPARE [page 54] and
Starting the Upgrade [page 63]).

4.8 Starting PREPARE

Prerequisites
Only valid for: Enterprise Portal (EP)

n If you are upgrading an SAP system with usage type EP and usage type Business Intelligence Java
Components (BI-Java) is not installed in it, in order to prevent the deployment of usage type

54/102 PUBLIC 03/28/2008

4 Preparation
4.8 Starting PREPARE

BI-Java on the target release system, you have prepared your source system as described in SAP
Note 1015214.
End of: Enterprise Portal (EP)

n If you are upgrading a dual stack (ABAP+Java) system, you have already started the upgrade
program for the ABAP server, SAPup.
This is essential for the proper synchronization of both upgrades.
n Your J2EE Engine is up and running. You must not stop the J2EE engine manually.
n You have downloaded the latest correction package for the upgrade program from SAP Service
Marketplace at [Link] Entry by Application Group Additional
Components Upgrade Tools CORRECTIONS FOR UPGRADE CORRECTIONS FOR UPGRADE 7.00 .
n For source release system based on SAP Web AS 6.40: There is no JSPM directory available under
/usr/sap/<SAPSID>/<central_instance_name>/j2ee.
n You are logged on to the upgrade host as user <sapsid>adm.
n User <sapsid>adm has the required permissions:
The <sapsid>adm user must be the owner and must have full (xrw) permissions for all files under
the directories /usr/sap/<SAPSID> and /sapmnt/<SAPSID>. If symbolic links are used, user
<sapsid>adm must be the owner of those as well.

Starting PREPARE for the First Time

1. Mount the Upgrade Master DVD directory.
2. Go to the mount directory and execute the command JPREPARE.
The required programs are copied to the upgrade directory.

Note
If you want to use a different upgrade directory, start PREPARE from the command line and specify
the upgrade directory path; for example, enter JPREPARE /<your_upgrade_directory>.

3. Start the SDTGui. [page 56].

Note
If you encounter any problems during PREPARE or during the upgrade, see Handling Upgrade Errors
[page 85].

Restarting PREPARE
You can restart PREPARE from the upgrade directory. Proceed as follows:
1. Go to <upgrade directory>/exe.
2. Enter the command PREPARE.

03/28/2008 PUBLIC 55/102

4 Preparation
4.9 Starting the SDTGui

Resetting PREPARE
If you want to repeat PREPARE completely from the beginning, proceed as follows:
1. Remove the upgrade directory.
2. Start PREPARE from the DVD as described in Starting PREPARE for the First Time.

4.9 Starting the SDTGui

You can control the upgrade on the host where you started the upgrade, as well as from a remote
host. To control it from a remote host, you must start the SDTGui in a Web Browser, which requires
Java Web Start technology.

Prerequisites
Make sure that PREPARE is running.

Starting the SDTGui in a Web Browser

1. Start a Web browser and enter [Link] in the address field.
2. Choose Start J2EE Upgrade Frontend (SDTGui).

Starting the SDTGui locally

1. Start the GUI as follows:
a) Change to <upgrade directory>/exe.
b) Execute the command startgui.
2. Proceed as follows:
a) In the Host name field, enter the name of the host where the central instance is running.
b) In the Port number field, do not change the default value 6241.
c) Choose Login.

4.10 Choosing the PREPARE Modules

PREPARE consists of the following five modules:

n Initialization
n Extraction
n Configuration
n General Checks
n Finalization
When you start PREPARE, you must choose which module(s) you want to run on the first screen. Each
module has a status (initial, succeeded, or error). All modules are mandatory and have to be executed

56/102 PUBLIC 03/28/2008

4 Preparation
4.11 Making Entries for the Initialization and Extraction Modules

one after the other, since they depend on their predecessors. You can repeat individual modules
as often as you want.

Procedure
When you select the PREPARE modules, note the following:
n If you are running PREPARE for the first time, choose at least the modules Initialization and Extraction,
since all other modules depend on them.
n If you want to exit and restart SAPJup, you have the following two options:
l Restart phase list at the point it has stopped.
You restart the process at exactly the point where you have exited.
l Select modules to execute.
You are shown the module selection dialog screen and can choose to repeat the entire module.
The following figure shows the PREPARE screen where you can choose the modules:

Figure 2: Selection Screen for Prepare Modules

4.11 Making Entries for the Initialization and Extraction

Modules

1. Include the correction package in the upgrade. The correction package provides the latest
corrections for the upgrade program.
Proceed as follows:

03/28/2008 PUBLIC 57/102

4 Preparation
4.11 Making Entries for the Initialization and Extraction Modules

a) Make sure that you have the latest version of the correction package. You can download the
correction package from SAP Service Marketplace at [Link]
Entry by Application Group Additional Components Upgrade Tools CORRECTIONS FOR UPGRADE
CORRECTIONS FOR UPGRADE 7.00 .
For more information, see SAP Note 813658.
b) Copy the package to your upgrade directory.
c) Choose Continue.
SAPJup extracts the package. To do this, it exits and restarts itself.
After the restart of the upgrade, you must restart the SDTGui [page 56].
2. Enter the keyword that is specified in the current SAP upgrade note.
You can find the number of the SAP Note in SAP Notes for the Upgrade [page 16].
The keyword and the correction package belong together and are updated simultaneously.
An error can occur if the correction package is outdated. In this case, proceed as follows:
a) Choose Cancel to cancel the phase and then exit SAPJup.
b) Remove the upgrade directory.
c) Start PREPARE from the DVD as described under “Starting PREPARE for the First Time” in
Starting PREPARE [page 54].
d) Download the latest correction package from SAP Service Marketplace and copy it to the
upgrade directory.
e) Proceed with the PREPARE program.
3. Enter the Solution Manager key.
You must generate a key in SAP Solution Manager [page 52]. To be able to proceed with the upgrade,
you must enter it when prompted.
If you are performing an upgrade of a dual stack system, you only have to enter the Solution
Manager key during the upgrade of the ABAP stack.
4. If you are upgrading a high availability system [page 37], enter the path to the central file share and an
instance number for the temporary SCS instance.
5. Check that the SAP system ID from the system that you want to upgrade is displayed. If it is
correct, choose Confirm.
Otherwise, cancel the phase, exit SAPJup, and restart it using the correct <sapsid>adm user.
6. Set a password for the J2EE super admin user (SAP*). During the upgrade, the User Management
Engine (UME) is reconfigured, so that only the SAP* user can access the system during the upgrade
downtime. The upgrade procedure initializes the account and you have to provide a password.
The SAP* user is only active during the upgrade downtime. SAPJup deactivates it after the
downtime has finished and restores the original UME configuration.
Remember the password in case you have to access the J2EE Engine during downtime.

Caution
Do not change the SAP* password manually once it is set. This would lead to a failure later in
the upgrade process.

58/102 PUBLIC 03/28/2008

4 Preparation
4.12 Making Entries for the Configuration Module

7. A summary of all system parameters that have been detected is displayed. Choose Continue or
cancel the phase and exit the program.
8. Confirm the usage of Business Intelligence (BI) and Mobile Infrastructure (MI) if required:
If SAPJup detects BI or MI installation, you are asked to confirm that they have been used in the
source release. If BI and MI have not been used on the source release, deselect the checkbox. As a
consequence, the usage types BI and MI are not deployed during the upgrade.
9. Enter the paths to all required upgrade DVDs.
n If you have access to only one DVD drive, you have to insert the DVDs one after the other:
a) Insert the first DVD.
b) Enter the mount point.
c) To start the DVD extraction, choose Continue.
d) Repeat this process until the lower table on the dialog screen displays the status Extracted
for all DVD subdirectories.
n If you have multiple DVD drives, you can insert all DVDs and enter the mount points at once.
The upgrade program extracts the contents into <upgrade directory>/data/archives.

4.12 Making Entries for the Configuration Module

The Configuration module enables you to specify the composition of the target release system.

Procedure
1. Decide which Support Packages you want to include in the upgrade. The Support Packages that
are available in the EPS inbox of your transport directory are displayed on the screen. Specify the
Support Package level for each target release component.
You can put further Support Packages in the EPS inbox and then display them by choosing Rescan.

Note
SAPJup only displays Support Packages in the following cases:
n For components already installed on the source release:
The Support Packages in the EPS inbox must be newer than those currently installed in your
system.
n For components that will be installed as part of the upgrade process:
The Support Packages in the EPS inbox must be newer than those that are included in the
upgrade DVD.

03/28/2008 PUBLIC 59/102

4 Preparation
4.12 Making Entries for the Configuration Module

Figure 3: Selection Screen for Support Packages

2. Decide how you want to handle the components during the upgrade.
The screen displays all components that are involved in the upgrade, either because they have been
detected on the source release system or because they belong to the target release shipment. The
following information is displayed for each component:
n Vendor
n Component Name
n Release
n Support Package Level
n Patch Level
n Operation

60/102 PUBLIC 03/28/2008

4 Preparation
4.12 Making Entries for the Configuration Module

Figure 4: Selection Screen for Target Release Components

In column Operation you can find the action that SAPJup will perform for the component. The
operation types are set automatically by SAPJup. You can only decide on the components for
which Scan inbox is specified as operation. The following four operation types exist:
n Scan inbox ‒ Assigned to components for which the upgrade program cannot find any
successor, such as customer developments or third-party software. You can either update
the components or keep them unchanged.
If you want to update these components, proceed as follows:
a) Provide a deployment archive (for example, SCAs) with the target release version of the
component in your EPS inbox.
b) Select the radio button Rebuild component list after scanning inbox at the bottom of the selection
screen.
c) Choose Continue.
If you do not have a successor for the components and you are sure that the components are
compatible with the new release, you can change the operation to Keep.
n Keep ‒ Set for components that have no successor but are compatible with the new release.
The component will remain unchanged during the upgrade.
n Deploy ‒ The normal upgrade operation. The component will be deployed to update or install it.
n Undeploy ‒ Applies to those components that no longer exist in the target release or have been
renamed.
3. To proceed with the PREPARE unit, confirm the list of components.

03/28/2008 PUBLIC 61/102

4 Preparation
4.13 Executing the General Checks and Finalization Modules

4.13 Executing the General Checks and Finalization Modules

The upgrade program checks the operating system and database versions and the JDK version. If it
detects a version that is not supported for the target release software, it writes the results to the log
file [Link] and displays a message.

Procedure
1. Enter the path to a JDK directory containing a JDK version that is supported for the target release.
As a default, SAPJup proposes the path to the currently used JDK. However, this might not be
supported for the target release. Therefore you must enter the path to a directory where you
have placed a supported JDK version.
For more information, see section Checking the Java Development Kit Version [page 40].
2. The status of the PREPARE modules is displayed. If SAPJup has detected any errors, for example
an operating system or database version that is not supported for the target release, it displays a
message telling you to check entries in the log file [Link].
3. Perform the actions that are prompted in [Link].

Note
If [Link] contains the entry that your database version is too low and you therefore have
to upgrade your database, you must perform a complete PREPARE run again after you have
upgraded your database. To do so, remove the upgrade directory and start PREPARE from the
Upgrade Master DVD.

4. Repeat the General Checks module and complete it successfully.

5. The Finalization module does not require any user interaction.

62/102 PUBLIC 03/28/2008

5 Upgrade Process

5 Upgrade Process

The following sections are important for performing the upgrade:

n Starting the Upgrade [page 63]
n Phase BEGIN_DOWNTIME [page 63]
n Phase DOWNTIME_END [page 64]

5.1 Starting the Upgrade

Prerequisites
n Your J2EE Engine is up and running. You must not stop the J2EE Engine manually. SAPJup stops
and starts the engine when needed.
n You are logged on to the upgrade host as user <sapsid>adm.
n User <sapsid>adm has the required permissions:
The <sapsid>adm user must be the owner and must have full (xrw) permissions for all files under
the directories /usr/sap/<SAPSID> and /sapmnt/<SAPSID>. If symbolic links are used, user
<sapsid>adm must be the owner of those as well.
n You have stopped all dialog instances.

Procedure
1. Go to <upgrade directory>/exe/.
2. Enter the command UPGRADE.
Apart from the activities in the phases BEGIN_DOWNTIME and DOWNTIME_END, the upgrade requires
no user interaction.
If you encounter any problems during the upgrade, see the troubleshooting sections in the Appendix.

5.2 Phase BEGIN_DOWNTIME

Procedure
Before the downtime begins, perform the following actions:
1. Ensure that you can recover your SAP system after errors:
n Make sure that you can recover the database to its current state.

03/28/2008 PUBLIC 63/102

5 Upgrade Process
5.3 Phase DOWNTIME_END

n Back up the upgrade directory so that you can reset the upgrade to this state at a later point in
time.
If you are upgrading a dual stack system (ABAP + Java), see the upgrade guide for the ABAP stack
for information about strategies for archiving and backing up your system.
2. Stop all dialog instances.
3. Stop SDM now at the latest by closing the SDM GUI.
4. Stop jcmon and all other standalone monitoring tools.
5. If you are upgrading a system that runs in a high availability landscape, stop the Java central
instance and then the SCS instance manually.
6. If your system is installed in a high availability switch-over environment, make sure that the
failover capabilities of the cluster switch-over software are disabled during the downtime. This is to
prevent unwanted failover actions during stop actions of the upgrade procedure.

5.3 Phase DOWNTIME_END

1. At the end of the downtime, create the following backups:

n A backup of your database as described in your database manual
n A backup of the upgrade directory
2. If you are upgrading a high availability system, start the SCS instance and afterwards the Java
central instance manually.

64/102 PUBLIC 03/28/2008

6 Follow-Up Activities

6 Follow-Up Activities

This part of the documentation contains information about the follow-up activities that you need to
perform after you have upgraded your SAP system:

Note
Some applications require you to perform some application-specific follow-up activities, without
which the applications cannot run. These application-specific activities are described in the Release
Notes for the particular application. The Release Notes are available on SAP Service Marketplace
at [Link]

n Executing the Script [Link] [page 66]

n Upgrading or Installing Dialog Instances [page 67]
n Changing Passwords [page 67]
n Performing Follow-Up Activities for the System Landscape Directory [page 68]
n Performing Follow-Up Activities for the Composite Application Framework Core (CAF Core) [page 68]
n Performing Follow-Up Activities for Adobe Document Services [page 69]
n Performing Follow-Up Activities for SAP Solution Manager [page 70]
Only valid for: Development Infrastructure (DI)

n Checking the CBS Service Properties [page 70]

End of: Development Infrastructure (DI)

Only valid for: Process Integration (PI)

n Importing XI Content for Software Component SAP_Basis 7.00 [page 71]

End of: Process Integration (PI)

Only valid for: BI Java Components (BI-Java)

n Performing Follow‒Up Activities for Business Intelligence [page 71]

End of: BI Java Components (BI-Java)

Only valid for: Enterprise Portal (EP)

n Checking the KMC Installation [page 72]

End of: Enterprise Portal (EP)

Only valid for: Enterprise Portal (EP)

n Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) [page 74]
End of: Enterprise Portal (EP)

03/28/2008 PUBLIC 65/102

6 Follow-Up Activities
6.1 Executing the Script [Link]

Only valid for: EP Core (EPC)

n Configuring Guided Procedures 2.0 Business Workflow Connectivity [page 75]

End of: EP Core (EPC)

Only valid for: Mobile Infrastructure (MI)

n Undeploying Obsolete Mobile Infrastructure Development Components [page 76]

End of: Mobile Infrastructure (MI)

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO);Biller Direct

n Adjusting the XCM Configuration [page 76]

End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO);Biller Direct

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

n Performing Follow-Up Activities for the E-Commerce User Management [page 78]
End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: Extended E-Selling Components (XECO)

n Performing Additional Follow-Up Activities for ERP E-Commerce [page 79]

End of: Extended E-Selling Components (XECO)

6.1 Executing the Script [Link]

After the upgrade, you need to make a number of adjustments. To do this, you need the
authorizations of the user root.
If your system is a dual stack system, see the relevant upgrade guide for the ABAP stack for
information about executing [Link].

Procedure
Only valid for: IBM DB2 for z/OS;MaxDB;Oracle

1. Log on as user <sapsid>adm.

2. Stop the system with stopsap.
3. Enter the following command sequence:
su - root
cd <upgrade directory>/data/kernel
./[Link] <SAPSID>
exit
4. Start the system with startsap.
End of: IBM DB2 for z/OS;MaxDB;Oracle

66/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.2 Upgrading or Installing Dialog Instances

Only valid for: IBM DB2 for Linux and UNIX and Windows

1. Log on as user <sapsid>adm.

2. Stop the system with stopsap.
3. Enter the following command sequence:
su root
cd <upgrade directory>/data/kernel
./[Link] <SAPSID>
exit
4. Start the system with startsap.
End of: IBM DB2 for Linux and UNIX and Windows

6.2 Upgrading or Installing Dialog Instances

After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
Due to the fact that some special settings and binaries on a dialog instance cannot be upgraded
remotely, you can only upgrade a dialog instance by uninstalling the old instance and then installing
a new dialog instance with the tool SAPinst.
If necessary, you can also install additional dialog instances.

Procedure
1. Uninstall the old dialog instances as described in the document Installation Guide ‒ SAP Web Application
Server 6.40 Java on <Operating System>: <Database>, Part II Installation and Post-Installation.
2. Install the new dialog instances as described in the document Installation Guide ‒ <SAP NetWeaver /
SAP application> <Technology> on <Operating System>: <Database>.

Caution
If you upgrade a dialog instance, make sure to use the same instance number as on the source release.

6.3 Changing Passwords

As of SAP NetWeaver 7.0 Support Package 03, new security policies apply. You have to change
passwords if:
n Your passwords are older than 90 days.
n Your passwords do not contain between six and twelve characters and do not consist of both
letters and numerals.
n Your password contains a user name.

03/28/2008 PUBLIC 67/102

6 Follow-Up Activities
6.4 Performing Follow-Up Activities for the System Landscape Directory

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. Restart the J2EE Engine.

6.4 Performing Follow-Up Activities for the System

Landscape Directory

The follow-up activities that you have to perform for the System Landscape Directory (SLD) depend
on the situation in your source release system, that is, whether SLD was configured or not.

Procedure
n If the SLD was configured in SAP NetWeaver ´04, you must only perform the following two actions
to enable the use of SLD in SAP NetWeaver 7.0:
l Configure User Management
Define security roles and assign users to these roles as described in the document
Post-Installation Guide ‒ System Landscape Directory of SAP NetWeaver 7.0, section “Configuring
User Management”. The document is available on SAP Service Marketplace at
[Link]
l Update the SLD content and data model
Download the latest SLD content from SAP Service Marketplace and import it into the SLD.
For more information, see SAP Note 669669.
n If SLD was not configured in SAP NetWeaver ´04 but you want to use it in SAP NetWeaver 7.0,
you must perform all configuration activities that are described in the document Post-Installation
Guide ‒ System Landscape Directory of SAP NetWeaver 7.0 available on SAP Service Marketplace at
[Link]

6.5 Performing Follow-Up Activities for the Composite

Application Framework Core (CAF Core)

Depending on whether CAF Core has been configured in the source release or not, perform the
following actions:

68/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.6 Performing Follow-Up Activities for Adobe Document Services

n CAF Core has not been configured in the source release

If the Composite Application Framework has not been configured in the source release but you
want to use it in production operation in SAP NetWeaver 7.0, you must configure it as described in
the online documentation on SAP Help Portal at [Link] SAP NetWeaver
7.0 Library <Language> SAP NetWeaver Library IT Scenarios at a Glance Developing, Configuring, and
Adapting Applications Creating Composite Applications .
n CAF Core has been configured in the source release
The configuration is retained during the upgrade. You only have to create the roles CAFAdmin
and CAFUIAdmin manually after the upgrade. For information about how to create these
roles, see the online documentation on SAP Help Portal at [Link] SAP
NetWeaver 7.0 Library <Language> SAP NetWeaver Library Technology Consultant´s Guide Developing,
Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework Core
Configuration Guide Setting Up Roles .

6.6 Performing Follow-Up Activities for Adobe Document

Services

To use Adobe Document Services productively after the upgrade, you must perform certain follow-up
activities. The follow-up activities mainly depend on the situation in your source release, that is
whether ADS was configured in your source release system or not.
The Adobe Document Services Configuration Guide for SAP NetWeaver 7.0 is available at the following locations:
n On SDN at
[Link] Installation & Configuration Interactive Forms —
Configuration Guides Configuration Guide for SAP Interactive Forms by Adobe
n In SAP Library at [Link] SAP NetWeaver 7.0 Library <English> SAP
NetWeaver Library Technology Consultant’s Guide Cross-NetWeaver Configurations Adobe Document Services
- Configuration .

Procedure
n ADS was not configured in SAP NetWeaver ´04
Perform the complete ADS configuration as described in Adobe Document Services Configuration Guide
for SAP NetWeaver 7.0.
n ADS was configured in SAP NW ´04
Perform the following configuration steps:
l Create a new http destination to SAP NetWeaver Application Server with the name
FP_ICF_DATA_<SAPSID>.
For detailed information about the procedure, see the document Adobe Document Services
Configuration Guide for SAP NetWeaver 7.0, section Configuring the Web Service Securing Access to the

03/28/2008 PUBLIC 69/102

6 Follow-Up Activities
6.7 Performing Follow-Up Activities for SAP Solution Manager

Web Service Configuration of the Web Service for Basic Authentication Creating or Changing the Destination
Service .
l If you want to use Secure Socket Layer (SSL), perform the configuration steps as described in
the document Adobe Document Services Configuration Guide for SAP NetWeaver 7.0, section Configuring
the Web Service Securing Access to the Web Service Configuration of the Web Service SSL Connection .
l Support Package 11 or lower only
Delete the credentials for interactive forms and create them again. For detailed information
about the procedure, see the document Adobe Document Services Configuration Guide for SAP NetWeaver
7.0, section Installing and Configuring Credentials.

6.7 Performing Follow-Up Activities for SAP Solution Manager

1. Connect the newly upgraded SAP system to SAP Solution Manager.

For more information, see the Configuration Guide: SAP Solution Manager, section “Solution Monitoring:
Setting Up the SAP Solution Manager” and “Solution Monitoring: Setting Up the Service Data
Control Center” on SAP Service Marketplace at [Link] SAP
Components SAP Solution Manager Release <x> .
2. Activate the EarlyWatch alert.
For more information, see the SAP Solution Manager online documentation at SAP Solution
Manager Solution Monitoring Using SAP EarlyWatch Alert .
Only valid for: Development Infrastructure (DI)

6.8 Checking the CBS Service Properties

After the upgrade you must check whether the following three CBS service properties are still valid
and suitable for the content you want to build:
n JDK_HOME_PATHS
n BUILD_TOOL_JDK_HOME
n BUILD_TOOL_VM_ARGS
For information about configuring CBS, see the SAP NetWeaver 7.0 online documentation at
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
Administrator’s Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
Development Infrastructure (DI) , then in section Component Build Service, see Configuring the Component Build
Service.
End of: Development Infrastructure (DI)

70/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.10 Performing Follow-Up Activities for Business Intelligence

Only valid for: Process Integration (PI)

6.9 Importing XI Content for Software Component SAP_BASIS

7.00

After the upgrade, you have to import the latest XI content for software component SAP_BASIS 7.00.

Procedure
1. From the SAP NetWeaver 7.0 Java DVD, copy the file
/J2EE_OSINDEP/UT/SAPBASIS<nn>_<nn>.zip
(where <nn>_<nn> stands for the relevant SP level and patch level) to directory
/usr/sap/<SAPSID>/SYS/global/xi/repository_server/import
and extract the file.

Note
You can also download XI content from SAP Service Marketplace. The latest XI content is always
available at [Link] Support Packages and Patches Entry by Application
Group SAP Content ESR Content (XI Content) XI CONTENT SAP_BASIS .

2. On your SAP NetWeaver Exchange Infrastructure host, call the transaction SXMB_IFR.
3. Choose Repository (Design).
4. Choose Tools → Import Design Objects.
5. Choose the extracted file with file extension .tpz residing in the directory
/usr/sap/<SAPSID>/SYS/global/xi/repository_server/import.
6. Import the file.
End of: Process Integration (PI)

Only valid for: BI Java Components (BI-Java)

6.10 Performing Follow-Up Activities for Business

Intelligence

If you have already used Information Broadcasting (IB) in NetWeaver ´04, you only have to perform
the configuration steps for the two new components, BI Reporting and Planning and BI Webdynpro
ALV.
If you have not configured Information Broadcasting in the source release, you have to perform
the complete BI configuration, that is, the configuration of IB, BI Reporting and Planning, and BI
Webdynpro ALV.

03/28/2008 PUBLIC 71/102

6 Follow-Up Activities
6.11 Checking the KMC Installation

As of SAP NetWeaver 7.0, BI Universal Data Integration (BI UDI) is an integral part of SAP NetWeaver
Application Server. BI UDI allows the integration of external data sources by using BI Java Connectors.
You need to complete the necessary follow-up activities and configuration tasks to make use of
the connectors.

Configuration of BI Information Broadcasting

For information about the configuration of BI Information Broadcasting, see the SAP Implementation
Guide (IMG) at SAP NetWeaver Business Intelligence Settings for Reporting and Analysis Settings for
Information Broadcasting

Configuration of BI Reporting and Planning

You have to create a RFC connection to the Adobe Server. For detailed information, see IMG SAP
NetWeaver Business Intelligence Settings for Reporting and Analysis and SAP NetWeaver Business
Intelligence BI Integrated Planning

Configuration of BI Web Dynpro ABAP ALV

You have to create RFC destinations and Web Service destinations as described in the IMG under
Application Server Web Dynpro for ABAP Set-Up Printing for Web Dynpro ABAP ALV .

Configuration of BI UDI
For information about the configuration of BI UDI, see the IMG at SAP NetWeaver Business
Intelligence UDI Settings by Purpose.
End of: BI Java Components (BI-Java)

Only valid for: Enterprise Portal (EP)

6.11 Checking the KMC Installation

As of SAP NetWeaver 7.0, Knowledge Management and Collaboration is an integral part of usage type
Enterprise Portal (EP). The upgrade program installs KMC during the upgrade if it has detected an
Enterprise Portal installation in the source release system. After the upgrade has finished, you can
perform some checks to see whether the KMC installation succeeded.
Use the KM Content iView and the KM Component Monitor to find out whether you can start up the system
without any errors. If you find errors, check the deployment and the log files.

Checking the KM Content iView

1. Log on to the portal as a user with the super administrator role.
2. Choose Content Administration KM Content and check whether any errors are displayed.

72/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.11 Checking the KMC Installation

Checking the Component Monitor

1. Log on to the portal as a user with the super administrator role.
2. Choose System Administration Monitoring Knowledge Management Component Monitor .
3. For Filters, Repository Managers, Repository Services and Services, check whether all subentries have the
status green. The colors beside the entries indicate the following:
n Green indicates that the object is functioning well.
n Red indicates the object cannot be started or is configured incorrectly.
n Yellow indicates that one or more lower-level items are red.
4. If an object has the status red, read the error message. Try to correct the error in the system
configuration.
For more information about the configuration, see the online documentation at
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
SAP NetWeaver by Key Capability Information Integration by Key Capability Knowledge Management
Administration Guide System Administration Monitoring, Logging, and Tracing Component Monitor .

Checking the Deployment

If the portal does not start up after the installation, or you notice errors in the Content Management
component monitor, then check the deployment. When you check the deployment, examine both
the application and content files.
1. Switch to the directory that contains the deployment files for the Content Management and
Collaboration applications:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/apps/[Link]
/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd
2. Check whether any of the following files have the extension .err:
n [Link].*
n [Link].*
n [Link].*
n [Link].*
If any files have the extension .err, this indicates that the deployment was executed but an error
has occurred. In this case, find out the reason for the error in the corresponding log file. The log
file has the same name as the .err file, but the extension is .log.
3. Switch to the directory that contains the files for the deployment of CM and Collaboration
content:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/apps/[Link]
/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent
4. Check whether any of the following files have the extension .err:

03/28/2008 PUBLIC 73/102

6 Follow-Up Activities
6.12 Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC)

n [Link].*
n [Link].*
n [Link].*
n [Link].*
If any of the [Link]* files have the extension .err, check the corresponding .log file to find
out what has caused the error. Check also the SAP J2EE log files mentioned above.

Checking the Log Files

If the Portal does not start up after the installation of Content Management and Collaboration or you
notice errors in the KM Content iView, check the available trace file.
1. Switch to the directory /usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/log/.
2. Open the file [Link] with the most recent date. If errors appear in the trace file, try
to solve them and then restart the SAP J2EE Engine.

Note
You can also view the trace file using the log viewer that is available in the SAP J2EE Visual
Administrator.
End of: Enterprise Portal (EP)

Only valid for: Enterprise Portal (EP)

6.12 Performing Follow-Up Activities for Knowledge

Management and Collaboration (KMC)

The follow-up activities for Knowledge Management and Collaboration are different depending on
whether you have used KMC in the source release or not.

KMC Was Not Configured in NW ´04

n Rename the following two files
l [Link] to [Link]
l [Link] to [Link]
The files are located in the following directory:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/apps/[Link]/irj
/servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl/
n Configure Knowledge Management and Collaboration
To be able to use the basic features from Knowledge Management and Collaboration, you have
to perform the minimal configuration tasks. These steps are also required if you want to use
the Running an Enterprise Portal scenario.

74/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.13 Configuring Guided Procedures 2.0 Business Workflow Connectivity

For Knowledge Management, see the following documentation for the basic configuration tasks:
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
Technology Consultant´s Guide Running an Enterprise Portal Providing Uniform Content Access Minimal
Configuration for Knowledge Management .
For Collaboration, see the following documentation for the basic configuration tasks:
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
Technology Consultant´s Guide Running an Enterprise Portal Providing Uniform Content Access Minimal Basic
Configuration for Collaboration .

KMC Was Configured in NetWeaver ´04

n Reconfigure the Collaboration Launch Pad as described in the following documentation in SAP
Help Portal:
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
Technology Consultant´s Guide Running an Enterprise Portal Providing Uniform Content Access Minimal Basic
Configuration for Collaboration
n As of SAP NetWeaver 7.0 Support Package Stack 09, the encoding of user IDs in the userhome
Repository has changed. You must migrate the userhome Repository of users that have a ~ (tilde)
in their name before the users log on to SAP Enterprise Portal for the first time.
For more information, see SAP Note 961747.
End of: Enterprise Portal (EP)

Only valid for: EP Core (EPC)

6.13 Configuring Guided Procedures 2.0 Business Workflow

Connectivity

If you have not configured Business Workflow Connectivity in SAP NetWeaver ´04 and want to use it
in SAP NetWeaver 7.0, you must perform some configuration tasks such as setting parameters.

Procedure
For detailed information about the configuration procedure, see the online documentation in the
SAP Help Portal at [Link] SAP NetWeaver 7.0 Library <Language> SAP
NetWeaver Library Technology Consultant’s Guide Developing, Configuring, and Adapting Applications Creating
Composite Applications CAF-GP Configuration Guide .
End of: EP Core (EPC)

03/28/2008 PUBLIC 75/102

6 Follow-Up Activities
6.15 Adjusting the XCM Configuration

Only valid for: Mobile Infrastructure (MI)

6.14 Undeploying Obsolete Mobile Infrastructure

Development Components

The upgrade procedure normally undeploys no longer needed source release development
components (DCs). If this undeployment fails for any reason, you have to undeploy all obsolete
Mobile Infrastructure DCs manually after the upgrade.

Procedure
1. Start the Software Deployment Manager (SDM) GUI.
2. Choose the Undeployment tab page.
3. Check if there are any DCs whose name starts with tc/mobile/ and whose release, which is
displayed under Count, is 6.30. These components are obsolete.
4. Undeploy the obsolete components.
For more information about using SDM, see the online documentation at
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library
SAP NetWeaver Developer´s Guide Fundamentals Using Java Complete Java Documentation for Developers
Online Core Development Tasks Deployment: Putting it All Together Software Deployment Manager SDM
Remote GUI Client .
End of: Mobile Infrastructure (MI)

Only valid for: Biller Direct;CRM Java Components (JCRM);Extended E-Selling Components (XECO)

6.15 Adjusting the XCM Configuration

Note
This section applies to SAP E-Commerce for SAP CRM (E-Selling and E-Service) and SAP
E-Commerce for SAP ERP.
In mySAP ERP 2004 the Extended Configuration Management (XCM) has been used to configure
the applications. The customizing data was stored in XML files ([Link] and
[Link]) in the file system. As of SAP ERP 6.0, the customizing data is stored in the
database of SAP NetWeaver AS Java 7.0. You have to check and adjust the configuration settings
after the upgrade. For information about using the Extended Configuration Management (XCM)
Administration tool, see the document Installation Guide - SAP ERP <Release> on <Operating System>:
<Database>, section Using Extended Configuration Management (XCM).

76/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.15 Adjusting the XCM Configuration

Entering Passwords
If you used the secure storage to encrypt passwords in the source release system, you have to reenter
each password after the upgrade. Whenever XCM data was modified, the secure storage was used.

Performing Adjustments to New Connection Concept

In the new release, each session is by default switched to https. To be able to log on to a web
application, you have to check the XCM settings. Proceed as described below and adjust the XCM
configuration:
1. Access the admin area of your web application ([Link]
name>/admin)
2. Start the XCM Admin by following the link Extended Configuration Management (XCM) Administration.
3. Open the tree on the left by choosing Start General Application Settings Customer <Application
Name> <Application Name>config .
4. Choose Edit.
5. Define the following parameters:
n [Link]: the http port of the NetWeaver Application Server
n [Link]: the https port of the NetWeaver Application Server
n SSLEnabled:
l true = every session is switched to https
l false = every session keeps the protocol that is currently used

Note
To be able to switch to the https connection, you have to enable https by using the Visual
Administrator of your NetWeaver Application Server Java.

Checking the XCM Configuration

In the new release, some new parameters and components are required in the XCM configuration.
Furthermore, some of those that have been used on the source release are no longer required.
Those parameters, that are no longer used are highlighted in yellow and their description starts
with ‘OBSOLETE’. The description also contain information about what is used instead, or why
the parameter is no longer required.
You have to check the complete configuration of each web application and perform all required
configuration steps.

Note
You do not have to remove the obsolete parameters or components from the configuration.

Replacing Component UI Configuration

The SAP configuration __backwardcompability_only__ for the component UI is no longer
supported as of SAP E-Commerce 5.0. If you are using this component configuration or your

03/28/2008 PUBLIC 77/102

6 Follow-Up Activities
6.16 Performing Follow-Up Activities for the E-Commerce User Management

own customer configuration, which derives from this configuration, you have to create a new
configuration for the component UI, derived from the SAP configuration default or default-hom.
End of: Biller Direct;CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

6.16 Performing Follow-Up Activities for the E-Commerce

User Management

As of SAP E‒Commerce 5.0 new user roles are provided. The old user roles are no longer supported.
For each Web application a service user role and at least one Internet user role are available. For more
information about the available roles, see the documentation in the Solution Manager.
Due to these changes, you have to perform updates in the user management as outlined below.

Updating Customized User Roles

Adjust your user role copies according to the authorizations provided in the new application user
roles. We recommend to create role copies and to refine authorizations with own authorization
values.

Creating Service Users

It is now possible to have a service user for each application. You have to create service users and to
assign them the appropriate service user role. You also have to create new customer JCO components
in the Extended Configuration Management (XCM) of your E‒Commerce applications, which you
can then select in the user settings of your XCM application configurations.

Assigning Roles to Web-Based User Management

You have to assign new user roles to the Web-based user management by using the following IMG
activity:
CRM E-Commerce Basic Settings for E-Commerce Internet User Web-Based User Management Set up
Roles for Web-based User Management
Furthermore adjust the role mapping to Enterprise Portal roles if your E-Commerce applications run
in an Enterprise Portal. For more information, see SAP Note 713472.

Assigning Roles to the Reference User

You have to assign new user roles to the reference users created for the E-Commerce
Business-to-Consumer (B2C) application or for the Web-based user management application.

78/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.17 Additional Follow-Up Activities for ERP E-Commerce

Internet User
You have to assign new user roles to your existing Internet users for the E‒Commerce applications
they have to use. To apply mass user changes, use the User Mass Maintenance (Transaction SU10).
End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO)

Only valid for: Extended E-Selling Components (XECO)

6.17 Additional Follow-Up Activities for ERP E-Commerce

In addition to adjusting the XCM configuration [page 76] and the user management [page 78], you have to
perform the following follow-up activities for SAP E-Commerce for SAP ERP:
n Upgrading Shop Management Data [page 79]
n Performing Adjustments to the Java Class Changes [page 80]
n Checking the Login Configuration [page 82]
n Replacing the Catalog Replication Mechanism [page 83]
n Adjusting XCM Configuration and Creating Shops for New Scenarios [page 83]

6.17.1 Upgrading the Shop Management Data

In SAP E-Commerce 5.0, the customizing data of the Shop Management Application is stored in the
database of SAP NetWeaver AS Java, while in previous releases the shop data was stored in the file
system in xml format.

Prerequisites
n You have access to the files that contain the shop data from ISA (R/3 Edition) 4.0.
n You have created an XCM application configuration for the Shop Management Web Application
(Shopadmin). The Shop Management Web Application is automatically installed with SAP
E-Commerce 5.0. The parameter object-path of the shop component must contain the path to
the XML files that contain the shop data from ISA (R/3 Edition) 4.0.

Procedure
1. Call the SAP E-Commerce Administration Console of the web application Shopadmin in the
upgraded system. To do so, enter [Link]
2. Choose the hyperlink Shop Data Migration (XML files to SAP J2EE Database).
3. Enter the name of the XCM application configuration that you created, as specified under
“Prerequisites”.
4. Choose Submit.

03/28/2008 PUBLIC 79/102

6 Follow-Up Activities
6.17 Additional Follow-Up Activities for ERP E-Commerce

The shops are now uploaded to the database of SAP NetWeaver AS Java and you can access them
using the Shop Management application.

Note
The shops are stored in such a way that they depend on the ERP system ID and client. Therefore,
you might have to migrate the shop data from the file system to the NetWeaver Application Server
database more than once, depending on how many systems and clients you are using in your
landscape.

6.17.2 Performing Adjustments to Java Class Changes

The following sections describe changes that have been made to Java classes. If you have modified
these classes in the source release, you have to adjust your modifications to the new developments.
As a prerequisite to run SAP E-Commerce 5.0, you must install the R/3 Plug-In 2004 SP10 for SAP
R/3 4.6c and R/3 Enterprise. The former Plug-In function modules are an integral part of mySAP
ERP 2004 and SAP ERP 6.0.

Obsolete Classes
In SAP Internet Sales (R/3 Edition) 3.1 and 4.0, some specific back-end classes and algorithm classes
had been used if no R/3 Plug-In was available or if the R/3 release was SAP R/3 4.6C or lower. These
classes are not used anymore. However, they are still delivered for documentation reasons:
n [Link].ShopR3
n [Link].CCardStrategyR340b
n [Link].CreateStrategyR340B
n [Link]
n [Link].DetailStrategyR340b
n [Link].DetailStrategyR3PI40

Incompatible Java Changes in Back-End Classes for SAP E‒Commerce for SAP ERP
This section is only relevant if you have implemented extensions in the back-end classes for SAP
E-Commerce for SAP ERP. These back-end classes are included in the following packages (or
subpackages of these packages):
n [Link].r3base
n [Link].r3
n [Link].r3
n [Link].r3

The following classes are affected:

n Class ChangeStrategy

80/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.17 Additional Follow-Up Activities for ERP E-Commerce

Method public boolean dequeueDocument has a new parameter of type SalesDocumentR3.

In releases SAP R/3 4.6C to mySAP ERP 2004, an update is performed for this sales document
to remove all locks. The same was performed in SAP Internet Sales (R/3 Edition) 4.0, but at a
different place. In SAP ERP 6.0, the ChangeStrategy class has been reimplemented. This new
implementation is called [Link]. It
enables a better lock handling performance.
n Class Extension
The Extension class has been moved from [Link] to
[Link].r3base.
n Class ServiceR3IPC
l Method protected void customerExitBeforeDocumentCreation now uses the Map class
instead of the HashMap class.
l Method protected void customerExitAddKNVVParameters has been removed. Instead, a new
exit protected void customerExitBeforeHeaderAttributeCall is available. Note that the
function module ISA_PRICING_HDRDATA_GET is now used to read the header attributes. This
function module reads more attributes than only those from table KNVV.
n Class ShopBase
Method protected Set readSalesAreas() now returns the Set class instead of the Map class.
n Class StatusStrategyR3
l An additional parameter of type ReadStrategy has been introduced in the constructor of
StatusStrategyR3. This change also applies to the derived class StatusStrategyR3PI.
l ClassStatusStrategy is no longer used for the search of sales documents, since a new search
framework has been implemented.
n Class WriteStrategyR3
A new parameter of type JCoConnection has been introduced for method protected String
convertProductIds. This parameter was necessary because of a new back-end call that converts
material numbers from internal to external format and the other way round. The method
also issues a back-end exception now. This change also applies to method protected void
setItemProductInfo.

Changes in Functionality of Class WriteStrategyR3

n Method public void setPartnerInfo:

In 3.1 and 4.0, a manually entered ship-to address in B2B got the sold-to ID as key and not the
underlying ship-to ID. In SAP E-Commerce for SAP ERP 5.0 this behavior has been changed. If you
create a new ship-to address in the basket on the basis of an existing ship-to address, it gets the
ship-to ID as key in the ERP order.

03/28/2008 PUBLIC 81/102

6 Follow-Up Activities
6.17 Additional Follow-Up Activities for ERP E-Commerce

Example
Sold-to ID is 1000, ship-to ID is 1010. The ship-to address is “Becker Berlin, 12 Lagerhausstrasse”.
The end-user changes this address to “Becker Berlin, 20 Lagerhausstrasse”. As a result, a manual
address will appear in the ERP order (on header or on item level) with key 1010.

n Method protected void shipToDataToRFCSegment: A manually entered ship-to address gets its
language from the shop and not, (as in release 4.0), from the master data ship-to address.

6.17.3 Checking the Login Configuration

As of SAP E-Commerce 5.0, we recommend that you use the SU01-based login configurations. Check
the following sections if you have used an SU05 based login configuration in your source release.

B2B XCM Default for Login Configuration

The default user configuration for ERP E-Commerce has changed from SU05
(R3_SU05Customer_LoginCustomerNo) to SU01 (R3_SU01UserContactPerson) in XCM. If you have not
changed the default setting , you will now use the SU01-based configuration.
Review your login configuration settings in XCM (usertype) at Application configurations Customer
<your configuration> .

Role Assignment for Anonymous SU05 User

E-Commerce 5.0 introduces special authorization roles. Authorization roles have been defined that
contain the SD authorization objects and new E‒Commerce-specific objects, for example, to view
certain documents in ERP E-Commerce.
When E-Commerce for SAP ERP runs with an SU01-based login configuration, you have to assign
certain roles to the actual E-Commerce user (for example, SAP_ISA_B2B_FULL) and some to the
anonymous user that is defined in XCM (for example SAP_ISA_B2B_RFC). For more information
about the available roles, see the configuration documentation for ERP E-Commerce User
Management in SAP Solution Manager. You cannot assign authorization roles to SU05 users. In that
case, all checks are performed against the anonymous user.
Make sure that the anonymous user that you define in XCM has the corresponding role for the RFC
user (for example, SAP_ISA_B2B_RFC or SAP_ISA_B2C_RFC) and also the necessary application
roles (for example, SAP_ISA_B2B_FULL).

User migration from SU05 to SU01

You can migrate your existing SU05 user accounts to SU01. After you have migrated the accounts, the
system generates an SU01 user the first time an SU05 user logs on to the upgraded ERP E‒Commerce
application. For detailed information about the migration procedure, see the configuration
documentation for ERP E-Commerce User Management in the SAP Solution Manager. Note that

82/102 PUBLIC 03/28/2008

6 Follow-Up Activities
6.17 Additional Follow-Up Activities for ERP E-Commerce

you must assign the authorization role SAP_ISA_UADM_MANAGER to the anonymous RFC user
for the migration period in addition to the already assigned roles. Otherwise, no new SU01 accounts
can be created.

6.17.4 Replacing the Catalog Replication Mechanism

As of E‒Commerce 5.0, an ABAP report replicates the ERP product catalogs to Search and
Classification (TREX). It replaces the trexr3 J2EE application. The report provides a Business Add-In
(BAdI) which you can use to adapt the retrieval and formatting of catalog data individually. The
catalog data is transferred directly from the ERP system to TREX using an RFC protocol. That means,
that the J2EE engine is not involved in the replication process and the running applications are not
affected, neither in terms of memory usage, nor in terms of CPU usage on the J2EE engine.

Procedure
To start the report call transaction ISA_CAT_REPLICATION. You can also schedule the report as a job.

6.17.5 Adjusting XCM Configuration and Creating Shops for

New Scenarios

If you are running the new scenarios “Business-On-Behalf” or “Catalog and Order Management for
Internal Users ”, you have to perform adjustments in the XCM configuration and to create new shops.
Both scenarios have in common that the sold-to party is selectable during the order creation process.

Adjusting XCM Configuration

Change the parameter shopdata as follows:
n If you run the “Business-On-Behalf ”scenario, change it to r3shop_bob
n If you run the “B2B for internal users ”, change it to r3shop_agent

Creating Shops
You cannot use existing shops for the two new scenarios. Instead you have to create new shops
as follows:
1. Create a new shop.
2. Specify the scenario.
3. Copy the shop data from an existing shop that you have uploaded as described in Upgrading the
Shop Management Data [page 79].
End of: Extended E-Selling Components (XECO)

03/28/2008 PUBLIC 83/102

This page is intentionally left blank.
A Appendix

A Appendix

A.1 Troubleshooting
This part of the document contains additional information on how to proceed when you want to
correct known problems that have occurred during the upgrade.
n Handling Upgrade Errors in SAPJup [page 85]
n General Procedure for Upgrade Errors [page 86]
n Upgrade Logs and Trouble Ticket [page 86]
n Tracing [page 88]
n Correcting Errors in the PREPARE Phases [page 88]
n Correcting Problems in the Upgrade Phases for SAP Kernel, Internet Graphics Service, and SAP MMC [page 89]
n Correcting Problems in the DEPLOY_* Phases [page 90]
n Correcting Problems with J2EE Engine Startup [page 91]
n Starting and Stopping the J2EE Engine Manually [page 92]
n Correcting Disk Space Problems [page 93]
n Updating Version Information [page 93]
Only valid for: Biller Direct;CRM Java Components (JCRM);Extended E-Selling Components (XECO)

n Migrating XCM Configuration Data Manually [page 94]

End of: Biller Direct;CRM Java Components (JCRM);Extended E-Selling Components (XECO)

A.1.1 Handling Upgrade Errors in SAPJup

When an error occurs or an upgrade phase terminates, the upgrade program stops. The upgrade
program offers you five options how to proceed:
n Repeat phase from point of failure
After you have corrected the error, you repeat the phase from exactly the point where the error
occurred.
n Repeat phase
After you have corrected the error, you may want to repeat the whole phase.
n Ignore error and go to next phase
This option requires a very deep understanding of the upgrade procedure. To avoid follow-up
problems with the upgrade, you have to consult SAP Support. SAP Support will provide you with
a password, if it is safe to continue the upgrade like this, or will solve the problem and allow you to
continue the upgrade without the need for a password.

03/28/2008 PUBLIC 85/102

A Appendix
A.1 Troubleshooting

n Jump to another phase

This option requires a very deep understanding of the upgrade procedure. To stop you choosing
this option deliberately or by mistake or wrongly you require a password from SAP Support to
select it.
From a list of all phases that belong to the current module, you can choose the phase to which you
want to jump.
n Exit program
The upgrade stops and you exit the upgrade program.

A.1.2 General Procedure for Upgrade Errors

Process
1. Check the trouble ticket and the phase log [page 86] for information about the error and possible solutions.
2. Close SAPJup.
3. Raise the trace level [page 88].
4. Start SAPJup again and repeat the phase to collect detailed information in the trace file.
5. Check the below sections for information about known problems.
6. If you cannot solve the problem yourself, create an error message in SAP Support Portal
([Link] and assign it to component BC-UPG-TLS-TLJ. Attach the
phase log files and the content of the trace file directory to the message.

A.1.3 Upgrade Logs and Trouble Ticket

The upgrade program logs all actions in upgrade logs, which you can use as your starting point for
troubleshooting. There is a log file for each upgrade phase. Additional service programs, which are
called from the upgrade program, also write log files.
Trouble tickets are special log files that are created when an error occurs.

Features

Log Files
The log files are stored under <upgrade directory>/logs and have the following naming convention:
<phase name><three-character-id><nn>.log, where <nn> is the number of phase iterations you
have already performed.

Example
Log file for DEPLOY_ONLINE phase: DEPLOY_ONLINE_DON_02.LOG

86/102 PUBLIC 03/28/2008

A Appendix
A.1 Troubleshooting

Logs that end with the extensions *.out and *.err belong to service programs, for example these are
log files of the Software Deployment Manager (SDM). [Link] contains overall status information
about the upgrade process.
You can view the log files using the log viewer, which is integrated into the SDTGui. To access it,
choose Services Log Viewer .
Using the log file converter, you can convert the log files to a human readable format. You can read
the converted files with any text editor. To convert the log files, proceed as follows:
1. Go to <upgrade directory>/logs.
2. Enter the following command:
log_reader <name of log file> <name of converted file>

Example
log_reader BUILD_COMPONENT_LIST_ACL_01.LOG
HUMAN_READABLE_BUILD_COMPONENT_LIST_ACL_01.LOG

The converted file is placed into the log directory.

Note
You can ignore the error messages No deployed SDA with the specified component
attributes <attributes> found. contained in the log files UNDEPLOY_LIST_UAF_<NN>.LOG and
UNDEPLOY_LIST_UAP_01.LOG.

Trouble Ticket
Trouble tickets are stored under <upgrade directory>/log and use the following naming
convention:
Trouble_Ticket_<xx>.log, where <xx> is the number of the error (not related to the phase number).
The trouble ticket contains general information about the system and the error. It references the
names of the log files for the phase and the external processes. You can use the terms at the end of the
ticket to search for SAP Notes related to the error.
If you open an error message, attach the trouble ticket to it to provide SAP Support with the
information.

Example
Trouble Ticket Report
Upgrade to NetWeaver 05
SID................: DIV
Hostname...........: ld0202
Install directory..: /usr/sap/DIV
Upgrade directory..: /usr/sap/jupgrade
Database...........: SAP DB

03/28/2008 PUBLIC 87/102

A Appendix
A.1 Troubleshooting

Operating System...: UNIX

Source release.....: 630
Target release.....: 700
Current usages.....: AS;BI
ABAP stack present.: false
The execution of prepare/EXTRACT/DETERMINE_USAGE_COMPONENTS ended in
[Link]: 3
More information can be found in the log file DETERMINE_USAGE_COMPONENTS_DUC_01.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS
note providing a solution to this problem. Search for OSS notes with the following
search terms:
[Link]
[Link].0002
[Link]
[Link]
DETERMINE_USAGE_COMPONENTS
EXTRACT prepare

A.1.4 Tracing

During the upgrade, a trace file is written and saved under <upgrade directory>/trc. As a default,
the trace level is set to ERROR. If you encounter any upgrade problems, you can raise the trace level to
gather more information. Send this file to SAP Support for further analysis.

Procedure
1. To raise the trace level, open the file <upgrade directory>/param/[Link].
2. Set the parameter [Link] to DEBUG.

A.1.5 Correcting Errors in the PREPARE Phases

Errors in DETECT_START_RELEASE_COMPONENTS Phase

In this phase, the upgrade program executes several Software Deployment Manager (SDM)
commands. SDM analyzes the source release system by using the action sduinfo to detect all
deployed components. If this phase fails, proceed as follows:
1. To find the command that has failed, check the log file
DETECT_START_RELEASE_COMPONENTS_SRC_xx.LOG.
2. Call SDM and try to execute the failed command from the command line.

88/102 PUBLIC 03/28/2008

A Appendix
A.1 Troubleshooting

For information about the procedure, see the SDM documentation available in
usr/sap/<SAPSID>/<instance_name>/SDM/program/doc.
3. If the command also fails when you execute it from the command line, then create an error
message in SAP Support Portal ([Link] and assign it to component
BC-CTS-SDM.

Errors in the EXTRACT_ROMS Phase

The most common error in this phase is that the upgrade program cannot find the correct
components on the mounted DVD to extract them.
An error message prompts you to provide the correct DVD. You can also see in the SDTGui that,
under DVD Subdirectory Status, the checkboxes in column Extracted are deselected.
1. To check whether you have mounted the correct DVD, check the [Link] file of the mounted
DVD.
2. Insert the correct DVD and repeat the EXTRACT_ROMS phase.
Disk space problems can also occur in this phase. For more information, see Correcting Disk Space
Problems [page 93].

Errors in the BUILD_COMPONENT_LIST Phase

If the upgrade program detects usage type BI or MI in the source release, you are asked to confirm
that they have been used in the source release. The corresponding target release components are
then deployed during the upgrade.
If by mistake you do not confirm that BI and MI are active in the source release, their components will
show up in the BUILD_COMPONENT_LIST phase with status Scan Inbox assigned to them, instead of Deploy.
To upgrade BI or MI, repeat PREPARE and confirm in the Initialization module that BI or MI are active
in the source release.

A.1.6 Correcting Problems in the Upgrade Phases for SAP

Kernel, Internet Graphics Service, and SAP MMC

The phases COPY_BINARIES, UPGRADE_MMC, and UPGRADE_IGS are used to upgrade SAP Kernel, Internet
Graphics Service (IGS), and SAP Management Console (SAP MMC). Errors in these phases are related
to running applications which lock application files and prevent them from being overwritten.

Procedure
1. Find the running application and stop it.
2. Search for running processes and stop them, too.
3. Repeat the failed phase.

03/28/2008 PUBLIC 89/102

A Appendix
A.1 Troubleshooting

A.1.7 Correcting Problems in the DEPLOY_* Phases

The target release components are deployed in different phases:

n DEPLOY_FS:
Deployment of the file system content. The J2EE Engine is stopped during the
deployment.
n DEPLOY_JDD: Deployment of database content. The J2EE Engine is stopped during the deployment.
n DEPLOY_OFFLINE: Deployment of core engine components. The J2EE Engine is stopped during
the deployment.
n DEPLOY_ONLINE: Deployment of all other software components. The J2EE Engine is running
during the deployment.
All DEPLOY_* phases call the Software Deployment Manager (SDM) to deploy the software. Errors
mainly occur in the DEPLOY_ONLINE phase.
Problems in the DEPLOY_* phases can also be related to J2EE Engine startup problems [page 91].

Procedure
1. If an error occurs in one of the deployment phases, the trouble ticket contains the exact name of
the SDM log file, which adheres to the following naming convention:
DEPLOY_SLOT_<x>__<three character ID>_<nn>.LOG
Search for the string “Error” in the SDM log files.
2. Depending on the error, proceed as described below:
n ERROR: Not deployed. Deploy Service returned ERROR:
[Link]: Cannot deploy application <application name>.
[..]
This error message occurs if a component cannot be deployed.
You can find the name of the Software Component Archive (SCA) that failed to be deployed
at the end of the log file.
If you encounter such a problem, create an error message and assign it to component
BC-CTS-SDM or to the component of the SCA which could not be deployed.
n ERROR: [Link]: The application start is forbidden, because
of the server mode and action.
You can ignore this error message.
n ERROR: An error occured in the JStartup Framework. The instance with instance
name <instance_name> did not respond within 300 s.
Try to find the reason for the J2EE Engine startup failure. For more information, see Correcting
Problems with the J2EE Engine Startup [page 91]. If the startup process has no errors but is just slow,
increase the timeout as described in SAP Note 891905.
n Error: Caught IOException while copying file to target location:
[Link]: No space left on device.
For more information, see Correcting Disk Space Problems [page 93].

90/102 PUBLIC 03/28/2008

A Appendix
A.1 Troubleshooting

n If there is no error message, but the DEPLOY_ONLINE phase runs for a long time, then check the
DEPLOY_SLOT_* log file for activity. If there is no activity in the log file and the timestamp is not
changing, check whether there is a problem with the database.
n Failure of DEPLOY_* phases can be related to a wrong system state of the J2EE Engine. During
the runtime of the DEPLOY_* phases, the system has to be in a defined state, that is the J2EE
Engine must either be stopped or must be running (see above). If the system is not in this
defined state because of errors in the start or stop procedures, the phases fail. Proceed as follows:
a) Open the [Link] file located in <upgrade directory>/param and search for the
failed phase.
b) To find out in which state the J2EE Engine must be, check the previous phase (START_*,
STOP_*).
c) Check the state of your J2EE Engine. If it is not in the expected state, then start or stop the
J2EE Engine, as required.
For information about the procedure, see Starting and Stopping the J2EE Engine Manually [page 92].
d) Repeat the phase.

A.1.8 Correcting Problems with J2EE Engine Startup

During the upgrade, the J2EE Engine is stopped and started several times. Errors in the startup of
the J2EE Engine can cause the upgrade to fail. In the trouble ticket and the phase log file you can
then find the error message:
Could not start J2EE Engine instance with name <name> and number <number> of the
standard system. Could not start instance <instance number>

Searching the Cause for the Error

To find the reason for the startup failure, you have to check the developer trace and log files of
the Java Startup and Control Framework, which starts the J2EE Engine. They are located in the
following directory:
/usr/sap/<SAPSID>/<instance_name>/work.
There are different kinds of trace and log files:
n Most important is the trace file of the JControl program, dev_jcontrol.
n Further trace files belong to the JLaunch processes that are started during the J2EE Engine startup:
dev_bootstrap, dev_dispatcher, dev_server<n>, and dev_sdm
n The standard error and output files of the JLaunch processes:
sdt_bootstrap.out, sdt_dispatcher.out, sdt_server<n>.out, and sdt_sdm.out

For more information about the Java Startup and Control Framework, see the online documentation
at [Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library SAP
NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual
J2EE Engine Starting and Stopping the Engine Administration of the Java Startup and Control Framework .

03/28/2008 PUBLIC 91/102

A Appendix
A.1 Troubleshooting

Message Server Not Started

If the message server was not started correctly, you can find the error message Can´t attach to
message server in the dev_jcontrol trace file. Proceed as follows:

1. Check that the SCS instance that contains the message server is running and that the message
server port is correct.
2. Start the SCS instance if it is not running.
For information about starting the SCS instance, see the online documentation at
[Link] SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library SAP
NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration
Manual J2EE Engine Starting and Stopping the Engine .

Errors in the Bootstrap Process

If errors in the bootstrap process occur, the dev_jcontrol trace file contains the error message ERROR
=> invalid return code of process [bootstrap] (exitcode=-1). Errors in the bootstrap process
are most commonly related to database problems. Proceed as follows:
1. Check that the database is running.
2. Check the following log files that are related to the bootstrap process for errors:
n std_bootstrap.out
n jvm_bootstrap.out
n dev_bootstrap_ID<instance ID>00
n dev_bootstrap_ID<instance ID>50
n /usr/sap/<SAPSID>/<central_instance_name>/j2ee/bootstrap/[Link]
3. If you need to create an error message, assign it to the component BC-JAS.

A.1.9 Starting and Stopping the J2EE Engine Manually

If a problem with the upgrade occurs, you might need to start and stop the J2EE Engine manually.
The procedure for starting and stopping the J2EE Engine during the upgrade downtime differs,
depending on whether you have a dual stack (ABAP+Java) or a standalone J2EE Engine.
During an ABAP+Java dual stack upgrade, the J2EE Engine is uncoupled from the ABAP server with
regard to starting or stopping the J2EE Engine. That is, the J2EE Engine is not started and stopped
together with the ABAP server using startsap and stopsap but by internal commands.

Starting and Stopping the J2EE Engine Manually During an ABAP+Java

Dual Stack Upgrade
n To start the J2EE Engine, execute the command <upgrade directory>/exe/jcontrol
–DSAPSTART=1 pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>.
n To stop the J2EE Engine, execute the command kill -2 <jcontrol-pid>, where <jcontrol-pid>
is the process ID of the JControl process. You can get the PID by using the ps command.

92/102 PUBLIC 03/28/2008

A Appendix
A.1 Troubleshooting

Starting and Stopping a Standalone J2EE Engine During the Upgrade

n To start the J2EE Engine, execute the command sapstart pf=<start_instance_profile>.
n To stop the J2EE Engine, execute the script [Link] from the directory
usr/sap/<SAPSID>/<instance_name>/work.

A.1.10 Correcting Disk Space Problems

During the EXTRACT_ROMS phase of the Extraction module, it can occur that SAPJup displays the
following error: Could not create variable handler JUP.J2EE. Could not load namespace
JUP.J2EE from file <upgrade directory>/data/variables/[Link]
Excetption has occured: Fatal Error: [Link]:
> expected(:main:,row:93, col:59)
This error message appears when there is not enough disk space available.
Further disk space-related problems can occur in the DEPLOY_* and COPY_BINARIES_* phases. If a
DEPLOY_* phase fails, the following error appears in the SDM deployment log in the log directory of
the upgrade directory:
Jun 17, 2005 12:50:15... Info: Loading archive
’/usr/sap/jupgrade/data/archives/ADSSAP02_0.SCA’
Jun 17, 2005 12:50:58... Error: Caught IOException while copying file to target
location: [Link]: No space left on device
In some cases, the deployment error doese not correctly indicate the reason for the problem. For
more information, see SAP Note 865424.

Procedure
To solve the problem, proceed as follows:
1. Delete the upgrade directory.
2. Add extra free space to the file system.
3. Restart the upgrade using the Upgrade Master DVD (see Starting Prepare [page 54]).

A.1.11 Updating Version Information

Up to Software Deployment Manager (SDM) version SAP NetWeaver ´04 SP 13 and SAP NetWeaver
7.0 SP 04, an SDM mode exists, in which SDM does not update the version information in table
BC_COMPVERS during the deployment. This results in an inconsistency between the version
information in BC_COMPVERS and the SDM repository after the upgrade. If you look up the version
information by entering [Link] you will see the old versions of all components,
whereas you can see the new versions in the SDM GUI.

03/28/2008 PUBLIC 93/102

A Appendix
A.1 Troubleshooting

Procedure
To correct the inconsistency between BC_COMPVERS and SDM, proceed as follows:
1. Stop the SDM server.
2. Set the SDM jstartup mode to standalone:
sdm jstartup "mode=standalone"
3. Set the SDM systemcomponentstate mode to activate:
sdm systemcomponentstate "mode=activate"
This will also sync the SDM repository and the BC_COMPVERS table.
4. Set the SDM jstartup mode back to integrated:
sdm jstartup "mode=integrated".
5. Start the SDM server
6. Check the system information by entering [Link]
For more information about executing SDM commands, see the SDM documentation available in
usr/sap/<SAPSID>/<instance_name>/SDM/program/doc.

Only valid for: CRM Java Components (JCRM);Extended E-Selling Components (XECO);Biller Direct

A.1.12 Migrating XCM Configuration Data Manually

SAPJup migrates the XCM configuration data automatically from the file system to the database of
SAP NetWeaver Application Server Java. In case of an error, this data might not be available after the
upgrade and you have to upload the data manually.

Prerequisites
You have access to the directory, where the configuration files from the source release web
applications are stored.

Procedure
1. Access the SAP E-Commerce Administration Console of the web application for which you want
to import the configuration ([Link]
2. Follow the link Extended Configuration Management (XCM) Administration to access the XCM
Administrator.
3. Choose Start XCM Settings on the left side.
4. Choose Edit (in the right upper corner). In the Edit mode, you can see two new text fields and
buttons below Upload configuration data from file-system.
5. Enter the path to the corresponding files or use the Search button to select them from the wizard.
The file [Link] contains the component configuration data, file [Link]
contains the application configuration data.

94/102 PUBLIC 03/28/2008

A Appendix
A.1 Troubleshooting

Note
To find out, where the configuration files of your source release web application are located
proceed as follows:
a) Access the XCM Administration application with the URL
[Link]
b) Navigate to Start Options .
The path to the configuration files is displayed.

6. Choose Upload.
7. Choose Display to change back to the display mode.
End of: CRM Java Components (JCRM);Extended E-Selling Components (XECO);Biller Direct

03/28/2008 PUBLIC 95/102

This page is intentionally left blank.
B Reference

B Reference

B.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the
various phases in the life cycle of SAP software.

Figure 5: Documentation Types in the Software Life Cycle

Cross-Phase Documentation
SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 labout
anguages, as well as many glossary entries in English and German.
n Target group:
l Relevant for all target groups
n Current version:
l On SAP Help Portal at [Link] Additional Information Glossary (direct access)
or Terminology (as terminology CD)
l In the SAP system in transaction STERM

03/28/2008 PUBLIC 97/102

B Reference
B.1 The Main SAP Documentation Types

SAP Library is a collection of documentation for SAP software covering functions and processes.
n Target group:
l Consultants
l System administrators
l Project teams for implementations or upgrades
n Current version:
l On SAP Help Portal at [Link] (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for
raising security levels. A collective security guide is available for SAP NetWeaver. This document
contains general guidelines and suggestions. SAP applications have a security guide of their own.
n Target group:
l System administrators
l Technology consultants
l Solution consultants
n Current version:
l On SAP Service Marketplace at [Link]

Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required
installable units for each business or IT scenario. It provides scenario-specific descriptions of
preparation, execution, and follow-up of an implementation. It also provides references to other
documents, such as installation guides, the technical infrastructure guide and SAP Notes.
n Target group:
l Technology consultants
l Project teams for implementations
n Current version:
l On SAP Service Marketplace at [Link]
The installation guide describes the technical implementation of an installable unit, taking
into account the combinations of operating systems and databases. It does not describe any
business-related configuration.
n Target group:
l Technology consultants
l Project teams for implementations
n Current version:
l On SAP Service Marketplace at [Link]
Configuration Documentation in SAP Solution Manager—SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business and IT scenarios. It contains IMG
activities, transactions, and so on, as well as documentation.

98/102 PUBLIC 03/28/2008

B Reference
B.1 The Main SAP Documentation Types

n Target group:
l Technology consultants
l Solution consultants
l Project teams for implementations
n Current version:
l In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring a single SAP system. The IMG activities
and their documentation are structured from a functional perspective. (In order to configure a
whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to
the relevant IMG activities in the individual SAP systems, is used.)
n Target group:
l Solution consultants
l Project teams for implementations or upgrades
n Current version:
l In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the solution operations guide. The manual refers users to the tools and
documentation that are needed to carry out various tasks, such as monitoring, backup/restore,
master data maintenance, transports, and tests.
n Target group:
l System administrators
n Current version:
l On SAP Service Marketplace at [Link]
The solution operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation
that are needed to carry out the various operations-related tasks.
n Target group:
l System administrators
l Technology consultants
l Solution consultants
n Current version:
l On SAP Service Marketplace at [Link]

Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of an
SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an
upgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.

03/28/2008 PUBLIC 99/102

B Reference
B.1 The Main SAP Documentation Types

n Target group:
l Technology consultants
l Project teams for upgrades
n Current version:
l On SAP Service Marketplace at [Link]
The upgrade guide describes the technical upgrade of an installable unit, taking into account
the combinations of operating systems and databases. It does not describe any business-related
configuration.
n Target group:
l Technology consultants
l Project teams for upgrades
n Current version:
l On SAP Service Marketplace at [Link]
Release notes are documents that contain short descriptions of new features or changes in SAP
NetWeaver or an SAP application since the previous release. Release notes about ABAP developments
enable the SAP system to generate delta and upgrade IMGs.
n Target group:
l Consultants
l Project teams for upgrades
n Current version:
l On SAP Service Marketplace at [Link]
l In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

100/102 PUBLIC 03/28/2008

This page is intentionally left blank.
 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
[Link]

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