How to Upgrade to SAP NetWeaver 7.

3
Target Audience >aj System administrators >aj Technology consultants

PUBLIC >a?OiD+]Gy9%ki/KmTrYu d%Z5tcl2,

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/ maintenancenw73. The following table provides an overview of the most important document changes.
Version Date Description

1.1 1.0

2012-04-18 2010-11-29

Information regarding SAPup removed First version no changes.

2/44

PUBLIC

2012-04-18

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 Chapter 2 Chapter 3 3.1 3.2 3.3 Chapter 4 4.1 4.2 4.3 4.4 Chapter 5 Chapter 6 6.1 6.1.1 6.1.2 6.1.2.1 6.1.2.2 6.1.3 6.1.3.1 6.2

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Overall Process at a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 5 5 6 7

Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updates in an SAP System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade in an SAP System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Solution Manager Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of Landscape Verification 1.0 for SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the Maintenance Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 11 13 15 15 16 16 16

Selecting and Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . 21 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information for All Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage Type Process Integration: Specific Preparations . . . . . . . . . . . . . . . . . . . Taking Note of Activated ICM Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Task Related to Background Job SWEQSRV . . . . . . . . . . . . . . . . . . . . . . . . Usage Type Adobe Document Services: Specific Preparations . . . . . . . . . . . . . ADS: Providing the JCE Jurisdiction Policy Files for Adobe Document Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 25 25 26 26 27 27 27 27

2012-04-18

PUBLIC

3/44

6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.1.6 6.2.1.7 6.2.2 6.2.2.1 6.2.2.2

Usage Type Process Integration: Specific Follow-Up Activities . . . . . . . . . . . . . PI: Generating Profiles for Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Importing ESR Content for Software Component SAP_BASIS . . . . . . . . . . PI: Creating a Destination from AS Java to AS ABAP for Integration Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Assigning New Product in SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Rescheduling PI-Specific Background Jobs . . . . . . . . . . . . . . . . . . . . . . . . . PI Adapter Engine: Creating a JCo Destination for the ExchangeProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Composition Environment: Specific Follow-Up Activities . . . . . . . . . . . . . . . . Composition Environment: Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESR: Performing Follow-Up Activities for the Enterprise Services Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27 28 29 31 31 32 33 33 34 34 34

Chapter A A.1 A.2 Chapter B

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 List of Referenced Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 List of Referenced SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4/44

PUBLIC

2012-04-18

1 1.1

Getting Started About this Document

1 Getting Started

1.1 About this Document

This document guides you through the upgrade to SAP NetWeaver 7.3 from the following source releases: >\ SAP NetWeaver Process Integration 7.1 and 7.1 including enhancement package 1 >\ SAP NetWeaver Mobile 7.1 and 7.1 including enhancement package 1 >\ SAP NetWeaver Composition Environment 7.1, 7.1 including enhancement package 1, and 7.2 It contains all required steps with references to detailed documentation or SAP Notes, where necessary. To upgrade from these source releases, you use the Software Update Manager to which we refer to from this document. Integration For general information about the upgrade to SAP NetWeaver 7.3, see the Upgrade Master Guide for SAP NetWeaver 7.3 available at http://service.sap.com/upgradenw73. You should start to prepare for the upgrade with the Upgrade Master Guide.

1.2 The Overall Process at a Glance

The following graphic shows the main steps that are involved in the process and which are explained below:

2012-04-18

PUBLIC

5/44

1 1.3

Getting Started Glossary

@(Pd 5(}<Overview of Main Steps of the Upgrade Process

1.

You need an SAP Solution Manager 7.0 system with the latest available Support Package stack level and the SAP Solution Manager Maintenance Optimizer needs to be configured. 2. You register your systems in SLD and transfer the system data to SAP Solution Manager. 3. Optional: You run the landscape verification 1.0 for SAP Solution Manager (add-on to SAP Solution Manager) which checks the system data that is maintained in the Solution Manager System Landscape (transaction SMSY). 4. You check system data using transaction SMSY and if necessary, update them. 5. As soon as the system data in SMSY is maintained correctly, you start a new maintenance transaction in SAP Solution Manager. 6. As part of the maintenance transaction, you have to select the required software units you want to update as well as the target Support Package level. 7. This selection is used by the Maintenance Optimizer to generate a stack configuration file and to calculate the software components as well as the Support Packages. 8. You download the files using the Download Manager. 9. You provide all downloaded files to the Software Update Manager. 10. You upgrade the system using the Software Update Manager.

1.3 Glossary
Here is a short overview of some technical terms used in this document:

6/44

PUBLIC

2012-04-18

1 1.4 Term

Getting Started Reading Sequence Explanation

The SAP Solution Manager System Landscape collects information about the SAP systems in the landscape. (SMSY is the name of the transaction in SAP Solution Manager.) SLD The System Landscape Directory is a Java software component that is installed on any SAP NetWeaver Java system. It can be configured to contain information about all the Java systems in a landscape. It can also contain information about ABAP systems. Usually you use one central SLD for your whole SAP system landscape. Maintenance Optimizer The SAP Solution Manager Maintenance Optimizer guides the user through maintenance procedures for any system in the landscape. Maintenance Optimizer is part of SAP Solution Manager and uses the information that is stored in the SAP Solution Manager System Landscape. Stack configuration file The stack configuration file is created by the Maintenance Optimizer and is systemspecific. Depending on the software components that are installed in a system, the Maintenance Optimizer calculates the required software components that have to be updated to reach a certain target configuration. SUM The Software Update Manager is the program that updates SAP systems. Product Used in SAP solutions. Generally speaking, a product fulfills business requirements. Product Version A concrete release of a given product. It bundles together software component versions made available at the same time for implementing a well defined scope of functionality. Product Instance A part of a product version and the smallest element for designing system landscapes. It groups technically dependent software component versions, which have to be installed and operated on a single Technical Syst Software Component (SC) Reusable component of the product. Technical System The runtime environment, in which SAP applications are executed. It is identified with a system identifier (SID). It must be assigned manually to a product system. Product System A group of technical systems, on which one product version is installed. Logical Component A group of technical systems, on which the same product instance has been installed. The technical systems have different roles, for example, development, test or production system. Landscape Patterns Describe how systems are used in a landscape. Landscape pattern hub: Technical system used by two or more product systems. Landscape pattern sidecar: Technical system that is used by a single product system and is not running on the ABAP stack. SMSY

1.4 Reading Sequence

In the different phases of your upgrade project, different documents and information sources support you with information. We recommend to read the documents in the following order which leads you from overview documentation to detailed documentation.

2012-04-18

PUBLIC

7/44

1 1.4

Getting Started Reading Sequence

;):}CM]NDReading Sequence Document(s) Content /Target

Upgrade Master Guide SAP NetWeaver 7.3 How to Upgrade to SAP NetWeaver 7.3 (this guide)

Individual documents and SAP Notes as referenced in this How-to Guide, for example, the Update Guide Update of SAP Systems Using the Software Update Manager 1.0

Provides general information about the upgrade to SAP NetWeaver 7.3 and all available upgrade paths. You are guided through the upgrade process with special focus on the SAP Solution Manager setup and use for your upgrade. You get product-specific information that is not covered by generic documentation and you are directed to separate guides with detailed information where necessary. You find detailed procedures for the individual steps required for the upgrade in these guides.

8/44

PUBLIC

2012-04-18

Process Overview

2 Process Overview

This section contains a checklist with all the actions you need to perform. For more information, follow the links to the descriptions of the actions. Read this list completely before you begin with the activities to get a thorough understanding of the process and to plan your schedule and resources accordingly.
Checklist

VF1. You check the availability of Support Packages [page 11] as described in SAP Note 1528990 VF2. You plan the sequence of upgrades in your SAP system group [page 13] and provide additional temporary systems for dual maintenance. VF3. You update SAP Solution Manager [page 15] to at least SAP Solution Manager 7.0 Support Package Stack 23. VF4. You run transaction SOLMAN_SETUP after the SAP Solution Manager update. VF5. Optional: You install the landscape verification 1.0 add-on [page 16] on top of your SAP Solution Manager system. VF6. You configure the Maintenance Optimizer [page 16]. VF7. You check the composite SAP Note 1436297 for corrections for the maintenance optimizer and apply the required SAP Notes. VF8. Maintain your system landscape data in SAP Solution Manager [page 16]: 1. Make your systems known to SAP Solution Manager using SLD. 2. Optional: Run the landscape verification 1.0 for SAP Solution Manager to check the entries in transaction SMSY. 3. Correct the SMSY entries, if necessary. VF9. You create a new maintenance transaction [page 21] in SAP Solution Manager and download the required software files and the stack configuration file. VF10. You prepare your system [page 25] for the upgrade as described in this guide and in the Update Guide Update of SAP Systems with Software Update Manager 1.0. This includes preparation activities for the hardware (for example, checking disk space requirements), activities for the database (for example, preparing free space, updating statistics, planning backups) and for the SAP system itself (for example, preparing the modification adjustment, checking the number of background processes). VF11. You perform the upgrade with the latest available Software Update Manager. VF12. You perform the follow-up activities as described in this guide and in the Update Guide Update of SAP Systems with Software Update Manager 1.0

2012-04-18

PUBLIC

9/44

Process Overview

SDk13. You perform regression tests.

10/44

PUBLIC

2012-04-18

3 3.1

Planning Checking Prerequisites

3 Planning

3.1 Checking Prerequisites

Procedure
Checking the Required Target Support Package Stack

When you upgrade your SAP system, you have to include a minimum Support Package stack for the target release into the upgrade. If your source release system has the most recent Support Package Stack level, make sure that this equivalent Support Package stack for the target release is already released. Proceed as follows: 1. Check SAP Note 1528990 for the required Support Package stack. 2. Check the Support Package stack schedule on SAP Service Marketplace at http:// service.sap.com/sp-stacks SP Stack Schedule for release date of the Support Package Stack you require.
NOTE

Do not apply the latest Support Package stack to the system that you want to upgrade shortly before an upgrade.
l@Y-,a*k1Z>s>|wD:_J?Fe"j@2V0J
G

3.2 Updates in an SAP System Group

NOTE

This section is relevant if you perform an enhancement package installation or SPS update. If you have an SAP system group consisting, for example, of a production system, a quality assurance system, and a development system, you must consider the entire system group regarding the sequence of updates. In addition, the update procedure influences the development activities, for example, dual maintenance might be temporarily necessary to ensure that your production system is supported with emergency corrections.
Procedure
Sequence of Updates

Update your systems in the same sequence in which you transport your modifications. Update each system with the same software packages.

2012-04-18

PUBLIC

11/44

3 3.2

Planning Updates in an SAP System Group

If your system group consists of three SAP systems and includes a quality assurance system that has been set up between the development and production system, work in the following order: 1. Development system 2. Quality assurance system 3. Production system
RECOMMENDATION

We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems. If you have made modifications to SAP objects that you want to retain, you must proceed in the above sequence. The version management functions of the SAP system record all the changes you make only in the system in which you made the modifications (the development system). Only this SAP system offers you optimal support when you adjust modifications. Changes made in the development system after the update can be transported automatically to your other SAP systems. If you use this procedure, you no longer need to perform time-consuming adjustments in the production system.
CAUTION

If you have modified SAP objects, make sure that you keep your development system. Do not copy your production system to your development system for test purposes.
Impact on Development

At a certain point in time during the update procedure, the development environment of the system that is updated is locked. Consider this development freeze in your project plan and inform your developers about it. To avoid the development system being unavailable during the update, we recommend that you add a temporary copy of your development system to your system landscape. This temporary development system can supply your production system with emergency corrections or support a phased development go-live after you have updated the original development system. You then have to make any corrections in the original development system as well as in the temporary development system. Make sure that your developers are notified about the dual maintenance.

12/44

PUBLIC

2012-04-18

3 3.3

Planning Upgrade in an SAP System Group

P)!dyL?^pw9 kWDual Maintenance

P)!dyLC?^sw9k,AQ-kxjU9W*pr P)!dyL?^cwW9RktAkxD9W*npOq?J(X1

3.3 Upgrade in an SAP System Group

NOTE

This section is only relevant if you perform a release upgrade. If you have more than one SAP system, for example, a production system, a quality assurance system, and a development system, you must consider the entire system group. Upgrade your systems in the same sequence in which you transport your modifications. In addition, the upgrade influences the development activities, for example, dual maintenance might be temporarily necessary to ensure that your production system is supported with emergency corrections.
Process

Sequence of Upgrades If your system group consists of three SAP systems and includes a quality assurance system that has been set up between the development and production system, work in the following order: 1. Development system 2. Quality assurance system 3. Production system If you have made modifications to SAP objects that you want to retain, you must proceed in the above sequence. The version management functions of the SAP system record all the changes you make only in the system in which you made the modifications (the development system). Only this SAP system offers you optimal support when you adjust modifications.

2012-04-18

PUBLIC

13/44

3 3.3

Planning Upgrade in an SAP System Group

Changes made in the development system after the upgrade can be transported automatically to your other SAP systems. If you use this procedure, you no longer need to perform time-consuming adjustments in the production system.
CAUTION

If you have modified SAP objects, make sure that you keep your development system. Do not copy your production system to your development system for test purposes. Impact on Development At a certain point in time during the upgrade, the development environment of the system that is upgraded is locked. Consider this development freeze in your project plan and inform your developers about it. To avoid the development system being unavailable during the upgrade, we recommend that you add a temporary copy of your development system to your system landscape. This temporary development system can supply your production system with emergency corrections or support a phased development go-live after you have upgraded the original development system. You then have to make any corrections in the original development system as well as in the temporary development system. Make sure that your developers are notified about the dual maintenance.

,zHob7q?Q#Dual Maintenance

Back to Quick Guide [external document]

,yHhb4Dbq<~QANcA]4&d:Rr^R

14/44

PUBLIC

2012-04-18

4 4.1

Preparing SAP Solution Manager SAP Solution Manager Update

4 Preparing SAP Solution Manager

5G~{c $MW>AN8fO'6T

The SAP Solution Manager Maintenance Optimizer plays a central role in the upgrade process. It is mandatory to use SAP Solution Manager Maintenance Optimizer for the calculation of the required upgrade packages, enhancement packages and Support Package stacks and for the creation of the stack configuration file (xml file). The upgrade program reads this stack configuration file and uses it as an input file for the upgrade.
5Gt{, 4SqWyONi8O

The following sections explain how to prepare SAP Solution Manager and the Maintenance Optimizer: 5G+ SAP Solution Manager Update [page 15] 5G+ Installation of Landscape Verification 1.0 for SAP Solution Manager [page 16] 5G+ Configuration of the Maintenance Optimizer [page 16] 5G+ Maintaining System Landscape Information [page 16]

4.1 SAP Solution Manager Update

You require at least SAP Solution Manager 7.0 EHP1 Support Package Stack 23. We recommend that you always update your SAP Solution Manager to the latest Support Package stack. Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents Available at...

Upgrade Guide SAP Solution Manager 7.0 incl. Enhancement http://service.sap.com/instguides SAP Package 1 Components SAP Solution Manager Release 7.0 EHP1 Describes the upgrade from source releases SAP Solution Manager 3.1 and 3.2. You can include the installation of the required Support Package stack in the upgrade procedure. Update Guide SAP Enhancement Package 1 for SAP Solution http://service.sap.com/instguides SAP Manager 7.0 Components SAP Solution Manager Release 7.0 EHP1 Describes the update from source release SAP Solution Manager 7.0. You can include the installation of the required Support Package stack in the update procedure. Solution Operations Guide SAP Solution Manager 7.0 EHP1, http://service.sap.com/instguides SAP section Software Change Management Components SAP Solution Manager Release 7.0 EHP1

2012-04-18

PUBLIC

15/44

4 4.2

Preparing SAP Solution Manager Installation of Landscape Verification 1.0 for SAP Solution Manager Available at...

Related Documents

Describes the actions required after the update to SAP Solution Manager 7.0 EHP1.

4.2 Installation of Landscape Verification 1.0 for SAP Solution Manager

Landscape verification 1.0 is an add-on to your SAP Solution Manager system. It supports you in maintaining your system landscape data. The use of this tool is optional. For information about the installation, see SAP Note 1468605.

4.3 Configuration of the Maintenance Optimizer

If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer configuration guide. In any case, check whether SAP Note 1436297 contains any corrections for the SAP Solution Manager 7.0 Support Package level you are using.
Related Documents Available at...
http://service.sap.com/mopz (link at the bottom of the page) http://service.sap.com/notes

Maintenance Optimizer Configuration Guide SAP Note 1436297

4.4 Maintaining System Landscape Information

The Maintenance Optimizer relies on up-to-date information about your system landscape. Therefore, it is crucial that this data is correctly maintained in the SAP Solution Manager system landscape (transaction SMSY). If you have already maintained the system landscape data, check carefully if this data is correct. Proceed in the following order: 1. If you have not already done so, capture the system data using the System Landscape Directory (SLD). 2. Optional: Run the landscape verification 1.0 to check the system landscape data. 3. Maintain the system data in SAP Solution Manager.
Procedure
Capturing System Data Using SLD

1.

Register all systems that you want to update in your SLD. In case of a dual-stack system, you have to register both the ABAP stack and the Java stack.

16/44

PUBLIC

2012-04-18

4 4.4

Preparing SAP Solution Manager Maintaining System Landscape Information

Depending on your applications, this can either be the SLD of your SAP Solution Manager system (if there are no dependencies of production runtime systems), or you have separate SLD systems for production and non-production use (default recommendation). If you use a central runtime SLD, distribute the data of all technical systems that are registered in the central SLD, from the central SLD to the development SLDs and to the local SLD in SAP Solution Manager. For more information about the SLD topology options and synchronization, see the Planning Guide System Landscape Directory available at http://sdn.sap.com/irj/sdn/nw-sld. To register Java systems, you use the Visual Administrator, or, as of SAP NetWeaver 7.1, the NetWeaver Administrator. To register the ABAP system, you use transaction RZ70. For more information about the registration of systems, see the SAP Library for your source release:
Release SAP Library Paths

SAP NetWeaver http://help.sap.com/nw70 SAP NetWeaver Library <Language> SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Software Life Cycle Management 7.0 System Landscape Directory Configuring Systems to Connect to SLD SAP NetWeaver http://help.sap.com/ SAP NetWeaver SAP NetWeaver Process Integration SAP NetWeaver Process Integration Library <Language> SAP NetWeaver Process Integration Library Process Function-Oriented View Application Server Infrastructure Configuring, Working with and Integration 7.1 Administering System Landscape Directory Configuring Systems to Connect to the SLD and SAP NetWeaver Process Integration 7.1 EHP1 SAP NetWeaver Connecting the system to the SLD is part of the initial system configuration as described Composition at: http://help.sap.com/nwce71/ SAP NetWeaver Composition Environment 7.1 (EHP 1) Library Environment Administrator's Guide Configuration of SAP NetWeaver CE Initial System Configuration 7.1 and SAP Configuring System Landscape Directory NetWeaver Composition Environment 7.1 EHP1 SAP NetWeaver Connecting the system to the SLD is part of the initial system configuration as described Composition at: http://help.sap.com/nwce72 SAP NetWeaver Composition Environment 7.2 Library Environment Administrator's Guide Configuration of SAP NetWeaver CE Configuring Mandatory Components 7.2 Configuring Application Server Java Mandatory Configuration Tasks Configuring System Landscape Directory

2.

If the registration was successful, both the ABAP system and the Java system appear in the SLD under Technical Systems. To transfer the data from the SLD to the SAP Solution Manager system landscape, schedule SLD update jobs in the SAP Solution Manager transaction SMSY_SETUP.

2012-04-18

PUBLIC

17/44

4 4.4

Preparing SAP Solution Manager Maintaining System Landscape Information

For more information, see the SAP Solution Manager Library at http://help.sap.com SAP Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data Capture for System Landscape .

3n<N0?Capturing System Data Using SLD Running the Landscape Verification 1.0

Running the landscape verification 1.0 is an optional step. This tool checks how your systems are maintained in the SAP Solution Manager system. If it detects any inconsistencies, you are prompted to correct existing entries or enter missing data. The tool provides you with information about maintaining the data. To start the landscape verification, call transaction LVSM in SAP Solution Manager. For more information about the landscape verification, choose the Help link from within the application.

3n<M0?Landscape Verification 1.0

18/44

PUBLIC

2012-04-18

4 4.4

Preparing SAP Solution Manager Maintaining System Landscape Information

Maintaining System Data

When your product systems are known in SAP Solution Manager, you have to check and maintain the system data, and add your system to a logical component and to a solution. 1. In transaction SMSY, choose Landscape Components Product System <System> . 2. Check whether the product version is correct. The product version is displayed in the right pane below the name of your system. 3. Choose the Selection of Product Instances tab and check that everything that is installed in your system is flagged as Relevant. Make sure that no instance is marked as relevant that is not installed in your system, as this would lead to the installation of unwanted software components in your system.
NOTE

You can only select one ABAP instance as relevant. You have to flag further ABAP instances as Also Installed in Relevant ABAP Product Instance. For more information about selecting the instances and required settings, see SAP Note 1344564 and SAP Note 1429764. Create the logical component as follows: 1. In transaction SMSY, choose System Groups and Logical Components. 2. In the context menu of Logical Components, choose Create New Logical Component. 3. Enter your system data. The name of your logical component must start with Z.... Assign the system to the logical component. In the Current System Assignments of the newly created logical component, add your systems with the appropriate roles (such as Development System or Production System).
RECOMMENDATION

4.

5.

6.

We recommend that you add all systems of one product to one logical component. This means that you create one logical component and add the development system, the quality assurance system, and the production system to the same logical component. Optional: Add the product system to a solution. It is no longer mandatory to create a solution and to add your product system to a solution. However, if you already have a solution, then add your product system to it. When you later create a maintenance transaction, you can select this solution and thus restrict the number of product systems displayed. 1. Call transaction SOLUTION_MANAGER and create a solution, if it does not yet exist. 2. Choose Solution Landscape and Solution Landscape Maintenance. 3. Add your SAP system to the solution as follows: 1. Change to edit mode. 2. Place the cursor on a new line in the Logical Component column. 3. Use the input help to select your system from the list (product, logical component). 4. Choose Complete System Data Replication.

2012-04-18

PUBLIC

19/44

4 4.4

Preparing SAP Solution Manager Maintaining System Landscape Information

5.

Save your selection.

20/44

PUBLIC

2012-04-18

Selecting and Downloading Software Packages

5 Selecting and Downloading Software Packages

Create a maintenance transaction in SAP Solution Manager Maintenance Optimizer to calculate the required software packages and the stack configuration file.
Procedure

1. 2. 3. 4.

In SAP Solution Manager, start transaction solman_workcenter and choose Change Management Choose New Maintenance Transaction. If you have maintained a solution, choose the solution for which you want to download the software packages. Select the system(s) that you want to include in the maintenance transaction. The product version dropdown box displays all product versions of the selected solution and, depending on the product version, the systems are displayed. You can run a maintenance transaction for one or multiple systems of one product version of exactly one solution.
RECOMMENDATION

5.

Create a single stack configuration file for all systems of a track (development system, quality assurance system, and production system). In addition, run your Maintenance Optimizer transactions for every affected system at the same point in time, ideally also in the same maintenance transaction. That way you make sure that all systems are upgraded with exactly the same software. If you run the same Maintenance Optimizer transaction at different points in time, the Maintenance Optimizer might include slightly different software. This is due to the fact that SAP changes Support Package stacks whenever a critical issue in the currently delivered software arises. ChooseCalculate Files Automatically as the file selection mode.
RECOMMENDATION

6. 7.

Check the Log tab regularly to see if any severe issues have occurred. In case you are unsure, create a customer message and assign it to component SV-SMG-MAI (Maintenance Optimizer). In addition, the Systems tab provides valuable information about the systems to be upgraded. Select the Upgrade update option. Select the target stack.

2012-04-18

PUBLIC

21/44

Selecting and Downloading Software Packages

8. Choose any additional Java instances that you want to install. 9. Check and confirm the target constellation for your system. 10. Select any add-ons that you want to install as part of this maintenance transaction. Maintenance Optimizer offers you to include add-ons directly into your maintenance operation so you can make use of the same downtime window instead of installing the add-ons separately afterwards. When you select an add-on, you can choose the system on which the add-on will be installed using the Assign System link. 11. Select the files that correspond to the combination of your operating system and database. In addition, select the files for SAP IGS and SAP HOST AGENT. If you run application servers on different operating systems, make sure that you also include their kernels files. When you slide with the mouse pointer over the kernel files, a quick info text displays for which system the kernel files have been calculated. 12. Select the stack-independent files and files for the add-on upgrade or add-on installation. In most cases, the stack-independent files include a SPAM/SAINT update for the target release. If you have decided to install new add-ons, Maintenance Optimizer displays now the corresponding files.
NOTE

The stack-independent files are not automatically included in the upgrade of your system. You have to include them manually during the Configuration roadmap step of the SAP Enhancement Package Installer. 13. Decide about the stack-dependent files.
RECOMMENDATION

We recommend you keep the selection. However, you can deselect any Support Package that you do not want to be applied to your system. Components of an SP Stack that are not used for productive use do not need to be patched during the implementation of the SP Stack, unless there is a technical or logical dependency to the used components. The Add Java Patches pushbutton allows you to search for appropriate Java patches and add them to the download basket. As these patches are not added to the stack configuration file, they are not implemented during this maintenance transaction. Their implementation is a separate step afterwards. 14. To download the files, select whether you want to download them with the Download Basket or with the Software Lifecycle Manager (only available if configured). 15. To access the stack configuration file, choose the Stack Files tab.
n$Kvm'M3VK^7c&N 3sX:2E]_~4E{E,w|6LPJA)2-m

Use the XML file. The text file is only needed for an upgrade with source release SAP R/3 4.6C.
n$Kv4'# ^+&N3oX{2{[_o4UdE%6|

22/44

PUBLIC

2012-04-18

Selecting and Downloading Software Packages

16. Download the files. We recommended starting the download shortly after you have run the maintenance transaction.

2012-04-18

PUBLIC

23/44

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

6 6.1

Upgrade Preparations

6 Upgrade

To perform the upgrade, you use the Software Update Manager. The upgrade to SAP NetWeaver 7.3 from SAP NetWeaver 7.1 and higher is technically an update, comparable with an enhancement package installation. Therefore, the Software Update Manager is used which internally calls the known SAP Enhancement Package Installer. General preparation and follow-up activities as well as the handling of the Software Update Manager are described in the document Update Guide Update of SAP Systems Using the Software Update Manager 1.0 available at http://service.sap.com/upgradenw73. In addition, you have to perform preparations and follow-up activities specific to your usage type. These specific actions are described in the following sections.
CAUTION

You have to perform both the general preparation activities as well as the usage type specific preparations before you can start the Software Update Manager. Make sure you start with these preparations in good time. You can also consider performing these preparations in parallel to the preparation of SAP Solution Manager and the download of the required software packages and the stack configuration file.

6.1 Preparations 6.1.1 Additional Information for All Usage Types

SAP Notes

SAP Note 1390477 Additional info for upgrade to SAP NetWeaver 7.3 contains supplementing information about the upgrade.
Supported Source Releases

The upgrade to SAP NetWeaver 7.3 with the Software Update Manager is supported from the following source releases: d& SAP NetWeaver Composition Environment 7.2 d& SAP NetWeaver Composition Environment 7.1 and 7.1 including enhancement package 1 d& SAP NetWeaver Process Integration 7.1 and 7.1 including enhancement package 1 d& SAP NetWeaver Mobile 7.1 and 7.1 including enhancement package 1

2012-04-18

PUBLIC

25/44

6 6.1

Upgrade Preparations

Minimum Operating System and Database Versions

For information about which operating system and database versions are currently supported, see the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/PAM.
Free Space Requirements

Make sure, that at least the following free space is available in the system that you want to upgrade:
Update Directory Download Directory DIR_TRANS Shadow System 10 15 GB 5 GB 3 GB Approximately the space required for your source release instance, that is the size of the following directory: ?(r Unix: usr/sap/<sapsid> ?(r Windows: <drive>:\usr\sap\<sapsid> ?(r IBM i: usr/sap/<sid> Approximately 50 GB

Free space in the database

6.1.2 Usage Type Process Integration: Specific Preparations

You need to make the following preparations before you can upgrade your Process Integration system. When you upgrade a standalone Advanced Adapter Engine or Partner Connectivity Kit (PCK), no specific preparation activities are required.
NOTE

If you are using a standalone Advanced Adapter Engine, you first have to upgrade the Process Integration system where the Advanced Adapter Engine belongs to. ?(r PI: Taking Note of Activated ICM Services [page 26] ?(r PI: Task Related to Background Job SWEQSRV [page 27]
KgOUS 
i2c_6|/z25q

6.1.2.1 Taking Note of Activated ICM Services

The Software Update Manager disables services of the Internet Communication Framework (ICF) for security reasons.
Procedure

Call transaction SICF and make a note of the activated services.

CgO2US}
i#c66|/p

26/44

PUBLIC

2012-04-18

6 6.2

Upgrade Follow-Up Activities

](X m0SP6(b#k[K=5"OV5H4l JvhA* )V zj.S~jeb33"]

6.1.2.2 PI: Task Related to Background Job SWEQSRV

Procedure

The background job for managing the correct processing of the event queue (SWEQSRV) is an optional periodical task for the Business Process Engine (BPE). After the startup of the BPE, the job SWEQSRV is no longer scheduled. If the job was scheduled in the operation mode periodic in the source system, SAP Note 1405648 must be applied before starting the update.
](X e0z(D#S[K=5"Y5H(w HwhS*-)W ?j1.~l

6.1.3 Usage Type Adobe Document Services: Specific Preparations

You need to make the following preparations before you can update Adobe Document Services (ADS).
](X m0SP6(b#k[K=5"`5H' DhV*&)] [j._~~eWl3B:/nSD

6.1.3.1 ADS: Providing the JCE Jurisdiction Policy Files for Adobe Document Services
To update usage type Adobe Document Services (ADS), you must provide the JCE unlimited strength jurisdiction policy files. The version of the files, which must be available in your system depends on the JVM version of the target release. During the update, the Software Update Manager checks if the JCE files are installed in your system and if their version is compatible with the JVM version. If the files are not installed or incompatible, the Software Update Manager prompts you to provide a path to a compatible version of the files. The required version is displayed on the screen. For more information about where to download the JCE unlimited strength jurisdiction policy files from, see SAP Note 1240081.
](X e0z(D#S[K=5"N5H## @fhG*!)V ?j.S~seN

6.2 Follow-Up Activities 6.2.1 Usage Type Process Integration: Specific Follow-Up Activities
This part of the document contains information about follow-up activities for the Process Integration system, that you need to perform after the update.

2012-04-18

PUBLIC

27/44

6 6.2

Upgrade Follow-Up Activities NOTE

There are no follow-up activities for the standalone Advanced Adapter Engine and the Partner Connectivity Kit. You can use a configuration wizard to automate the below follow-up activities after you have performed the update. If you cannot run these steps automatically, you have to perform them manually. For more information about the manual procedures, see the subsequent sections in this guide. To operate the wizard, perform the following steps: 1. To start SAP NetWeaver Administrator, go to http://<host>:<port>/nwa. 2. Log on with your JEE administrator user. 3. Choose Configuration Scenarios Configuration Wizard. 4. From Configuration View, choose All Configuration Tasks (dropdown box). 5. Select PI Upgrade EHP and choose Start. If you want to execute the follow-up activities for the Adapter Framework, select Adapter Engine Upgrade. For more information, see: PI-AF: Creating a JCo Destination for the ExchangeProfile [page 33]. If you want to repeat the upgrade process, choose Re-execute. 6. When prompted by the wizard, provide the required entries (users and passwords). The follow-up steps are then processed automatically. For more information about the wizard, see SAP Note 1450419. You must perform the following actions before you resume production operation of your system: 84? PI: Generating Roles for SAP_XI and SAP_SLD [page 28] 84? Performing Follow-Up Activities for the System Landscape Directory [page 29] 84? PI: Importing ESR Content for Software Component SAP_BASIS 7.3 [page 31] 84? PI: Creating a Destination from AS Java to AS ABAP for Integration Process Monitoring [page 31] 84? PI: Assigning New Product in SLD [page 32] You can perform the following actions during limited production operation of your system: 84? PI: Rescheduling PI-Specific Background Jobs [page 33]
8V.pBG#M>jcwZ8Nn<QZ =9^0.=fTI$%'n/G#S\R&tj64;@wy

6.2.1.1 PI: Generating Profiles for Roles

NOTE

This step only applies if you have not used the CTC Wizard to perform the basic configuration steps after the update.
Procedure

To generate all roles, proceed as follows: 1. Call transaction PFCG. 2. Choose Utilities Mass Generation .

28/44

PUBLIC

2012-04-18

6 6.2

Upgrade Follow-Up Activities

3.

4.

Select All Roles. In the Role field, enter SAP_XI*. Select Generate Automatically. Choose F8 and then Generate online. If a list of profiles that have not yet been generated is displayed, repeat the procedure by choosing F8 . 5. Repeat the steps for the roles SAP_SLD*. 6. Repeat the steps for the roles SAP_BC_AI_LANDSCAPE_DB_*. 7. Repeat the steps for the roles SAP_BC_JSF_COMMUNICATION*. 8. Repeat the steps for the roles SAP_BC_BGRFC_SUPERVISOR in IS client. 9. Repeat the steps for the roles SAP_BC_BGRFC_SUPERVISOR in client 000. 10. Repeat the steps for the roles SAP_BC_WEBSERVICE_SERVICE_USER in IS client. 11. Repeat the steps for the roles SAP_BC_WEBSERVICE_SERVICE_USER in client 000. Choose Utilities Mass Comparison . 1. In the Role field, enter SAP_XI*. 2. Select Output Error Messages. 3. Choose F8 . No error message should be displayed. You can ignore the message that a certain role does not have a profile. 4. Repeat the steps for the roles SAP_SLD*. 5. Repeat the steps for the roles SAP_BC_AI_LANDSCAPE_DB_*. 6. Repeat the steps for the roles SAP_BC_JSF_COMMUNICATION*. 7. Repeat the steps for the roles SAP_BC_BGRFC_SUPERVISOR in IS client. 8. Repeat the steps for the roles SAP_BC_BGRFC_SUPERVISOR in client 000. 9. Repeat the steps for the roles SAP_BC_WEBSERVICE_SERVICE_USER in IS client. 10. Repeat the steps for the roles SAP_BC_WEBSERVICE_SERVICE_USER in client 000. Restart the AS Java from transaction SMICM by choosing Administration AS Java Instance (Local) Send Hard Shutdown with Restart .

1. 2. 3. 4.

+s2T[H5M0b}j}~|@9Dm@LJ5"BN ;6Sl! l,8nF1:uNV@ +y:TH_5M|b}j9~D@Y9d7m}L15,WN 6l. u

6.2.1.2 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 the SLD was configured or not.

2012-04-18

PUBLIC

29/44

6 6.2

Upgrade Follow-Up Activities

Procedure

) If the SLD was configured in your source release system, you must perform the following actions to enable the use of the SLD in your updated system: ) Configure the user management Define security roles and assign users to these roles. Proceed as described in the SAP Library [external document] for your target release at: SAP Library <Language> SAP NetWeaver Security Guide Security Aspects for Lifecycle Management System Landscape Directory Security Guide Configuring SLD Security Roles ) Update the SLD content and data model
NOTE

This action is not required if you have already updated the SLD content and data model as described in Updating SLD Content of the Source System [external document]. We recommend that you download the latest SLD content from SAP Service Marketplace and import it into the SLD. For more information, see SAP Note 669669. ) If the SLD was not configured in your source release system but you want to use it in your target release system, proceed as described in the SAP Library [external document] for your target release at: Function-Oriented View <Language> Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administering the SLD In either situation, you also need to configure the following SLD components: ) SLD Data Supplier Proceed as described in the SAP Library [external document] for your target release at: Function-Oriented View <Language> Application Server Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Connecting Systems to the SLD ) For AS ABAP systems: Connecting AS ABAP Systems to the SLD Setting Up the SLD Data Supplier for AS ABAP Based Systems ) For AS Java systems: Connecting AS Java Systems to the SLD Setting Up the SLD Data Supplier for AS Java Based Systems ) SLD Client Proceed as described in the SAP Library [external document] for your target release at: Function-Oriented View <Language> Application Server Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Connecting Systems to the SLD Connecting AS Java Systems to the SLD Configuring the SLD Client
More Information

After the update, if the access to the SLD is no longer possible for some users, see SAP Note 1617234.
)O">wDaEk[oE-\q#@lR*

30/44

PUBLIC

2012-04-18

6 6.2

Upgrade Follow-Up Activities

l$es-OPJ1 )<*+-29\w% {ug!)%N($pfId%cgDV]

6.2.1.3 PI: Importing ESR Content for Software Component SAP_BASIS

NOTE

This step only applies if you have not used the CTC Wizard to perform the basic configuration steps after the update. Download the latest ESR content for software component SAP_BASIS 7.30 from SAP Service Marketplace and import it into your system.
Prerequisites

You have performed the necessary activities for the SLD [page 29].
Procedure

1.

2.

Download the latest ESR content from SAP Service Marketplace at http://service.sap.com/ swdc Support Packages and Patches My Companys Application Components XI CONTENT SAP_BASIS XI CONTENT SAP_BASIS <release> . Copy the XICNTSAPBASIS<SP>_<PL>.SCA file to the following directory, where <SP> stands for the Support Package level and <PL> stands for the corresponding patch level:
l$es-OPJ1 )<*+;19\ ow

<DRIVE>:\usr\sap\<SAPSID>\SYS\global\xi\repository_server\import\
l$esb_J< )9c+7 l$es-OPJ1 )<*+9> 9m

/usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
l$esb_J 2 l$es-OPJ1 )<*+%2u9\Qw

/usr/sap/<SID>/SYS/global/xi/repository_server/import/
l$esb_J /{?+?

3. 4. 5. 6.

Log on to the Enterprise Services Repository by choosing Enterprise Services Builder on the start page. Choose Tools Import Design Objects . Choose the file XICNTSAPBASIS<SP>_<PL>.TPZ . Import the file.

l$esb_J mq+ u9\w"9 {ug3}%n(>p#LN6 l$es-OPJ1 )<*+-29\w% {ug!)%N($pfId%cgDV]

6.2.1.4 PI: Creating a Destination from AS Java to AS ABAP for Integration Process Monitoring
You can monitor integration processes (cross-component Business Process Management) using SAP NetWeaver Administrator. To enable this function, the Java-based user interface of SAP NetWeaver

2012-04-18

PUBLIC

31/44

6 6.2

Upgrade Follow-Up Activities

Administrator has to retrieve data being persisted in the ABAP stack of the Integration Server. Therefore, a destination from the Java stack to the ABAP stack is needed. You create the necessary destination in SAP NetWeaver Administrator.
Procedure

1. 2. 3. 4.

To start SAP NetWeaver Administrator, enter the following address in your Internet browser: http://<host>:<port>/nwa. Log on with your AS Java administrator user. Choose Infrastructure Destinations . Specify the RFC destination. To do this, choose the Logon Data tab and enter the user and password. The Special Data tab contains default values that are already set

^dT0^7:cth"0SgF}*:9E*V)[{7*w8}PP Td\Y ^
:Fct=p0`gF}5:/*)[Z7!#8B}&P^ f:KPM4-zq-*H"p!x~Eunh3+~f3 ^&-,M_0;

6.2.1.5 PI: Assigning New Product in SLD

NOTE

This step is not required if you apply a Support Package Stack. After the update, you must add the new product SAP NETWEAVER 7.3 to all technical systems and business systems.
Procedure

1. 2. 3. 4. 5.

Log on to the SLD system using the following command: http://<host>:<port>/sld. Select Technical Systems and under Technical System Type AS ABAP Version 730. Select the Installed Software tab and select Add New Product. A list of available products appears. Select SAP NETWEAVER 7.3. Assign the following components:
SAP BASIS 7.30 SAP ABA 7.30 SAP BW 7.30

6. 7.

Save your assignments. Select the Business Systems tab. For each Business System, click on the link of the Business System, select the Installed Software tab, assign the new product and select Save.

^dT0^:Jctc0pgF}
:T*G)[f7d`V8H}cPm :5PM  

-0$H"px~Es|<3+|3 ]&>

32/44

PUBLIC

2012-04-18

6 6.2

Upgrade Follow-Up Activities

'M&y*'G Jt(zWA;n@{_uv\C0JI#xhrfZ&-

6.2.1.6 PI: Rescheduling PI-Specific Background Jobs

In addition to rescheduling background jobs that were locked when you isolated the primary application server instance, you must reschedule some SAP NetWeaver PI-specific background jobs.
Procedure

You must reschedule the following background jobs manually: z Background Job for Missed Deadlines z Background Job for Work Items with Errors z Background Job for Event Queue z Background Job for Clearing Report z Background Job for Shared Memory Update of the Container Factory z Background Job for Packaging z Background Job for Reorganization To reschedule the jobs, proceed as follows: 1. Call transaction SWF_XI_CUSTOMIZING. 2. Select the background job. 3. Choose the button for performing the automatic workflow Customizing. In addition, you may have to reschedule the background job for managing the correct processing of the event queue (SWEQSRV). This background job is an optional periodical task for the Business Process Engine (BPE). After the startup of the BPE, the job SWEQSRV is no longer scheduled. If the job was scheduled in the operation mode Depending on load (dynamic), it must be started manually after the upgrade.
'M&"*GlJB(BWA,;}@`_gv\CWJaE 'M&y*'G Jt(zWA;.
_Ov\C'JZLqhr ZC

6.2.1.7 PI Adapter Engine: Creating a JCo Destination for the ExchangeProfile

NOTE

If you used the PI-specific configuration wizard to automate a number of certain follow-up activities, yo do not need to perform this follow-up step. It has been covered by the wizard. The Adapter Engine uses a Java RFC destination "XI_EXCHANGE_PROFILE" to connect to the Exchange Profile. To create this destination, proceed as follows:
Procedure

1.

In the SAP NetWeaver Administrator, go to Configuration Connectivity Destinations .

2012-04-18

PUBLIC

33/44

6 6.2

Upgrade Follow-Up Activities

2. 3. 4.

Create a new destination of type RFC with the name XI_EXCHANGE_PROFILE. Enter the connection data for the server where your ExchangeProfile is stored (usually the PI Integration Server). (Optional) To make the communication more secure, you can configure the destination to use SNC.

+v+>(<GnbxTdPL8[0rmkY}G7(?Fxn !v+qd3<qVL4xTdA6KPL#9[dr"k<}G*?Fxkm7X-las?Fc{ p9_I(c]MJ[RLJOxk

6.2.2 Composition Environment: Specific Follow-Up Activities

!v+qd3<qVL4x TdKPL0[%r"kr}G,'?Nxkm|X-lf6c

6.2.2.1 Composition Environment: Performing Follow-Up Activities for the System Landscape Directory
After the upgrade process has finished successfully, you have to update the software catalog in your System Landscape Directory (SLD), as described in SAP Note 669669.
+v+>(<gW`x TdOPL/|[%r:ks}G~n?`xkUmk !v+qd3<qVL4x<TdA!@PL#.[!rQ(kn}G=#?PxkmxXS-l5R6c

6.2.2.2 ESR: Performing Follow-Up Activities for the Enterprise Services Repository
NOTE

If you used the PI/ESR -specific configuration wizard to automate a number of certain follow-up activities, you do not need to perform this follow-up step. It has been covered by the wizard. You have to update the SAP BASIS content by manually importing the ESR content, which you can find at:  Windows:\usr\sap\<SAPSID>\SYS\global\xi\content  UNIX:/usr/sap/<SAPSID>/SYS/global/xi/content  IBM i:/usr/sap/<SID>/SYS/global/xi/content
Prerequisites

You must have the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER to be able to export and import ESR content.
Procedure

1.

Start the Enterprise Services Builder and call the Enterprise Services Repository: To do this, perform the following steps:

34/44

PUBLIC

2012-04-18

6 6.2

Upgrade Follow-Up Activities

1. 2.

2.

Log on to the SAP system on which your Enterprise Services Builder has been installed. You start the Enterprise Services Builder or the Integration Builderby means of an HTML start page. Open this start page by calling it either from your user menu or with transaction SXMB_IFR. 3. Choose Enterprise Services Repository. Copy the ESR content into the following import directory for the Enterprise Services Repository: h Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\import h UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import h IBM i: /usr/sap/<SID>/SYS/global/xi/repository_server/import
CAUTION

3. 4. 5.

The actual ESR content files have the extension .tpz. You must not unpack these files. The import directory is created the first time you call the Enterprise Services Builder. Choose Tools Import design objects . ESR content can be imported either from a server directory or from a directory of your local PC (Client). SAP recommends that you import ESR content from the server directory. Choose Server. You can only select files from the following import directory: h Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\import h UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import h IBM i: /usr/sap/<SID>/SYS/global/xi/repository_server/import The sequence in which you import the files is not important

Result

After a successful import, the Enterprise Services Builder moves the imported TPZ files into the following directory: h Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\importedFiles h UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/importedFiles h IBM i: /usr/sap/<SID>/SYS/global/xi/repository_server/importedFiles The Support Package of imported software component versions is displayed on the Details tab page for the relevant software component version in the Enterprise Services Builder. If an error occurs, this information is important for support. Take one of the following precautions to retain the overview of the imported ESR content: h If the release and the Support Package are clear from the file name of the TPZ file, simply leave the files in the directory importedFiles (as described above). If a file with the same file name already exists in the directory importedFiles, the Enterprise Services Builder adds the date and time of the import to the file name of the imported export file. This enables you to check which file was imported last.

2012-04-18

PUBLIC

35/44

6 6.2

Upgrade Follow-Up Activities

C After a successful import, you can keep the packed files, from whose naming convention you can derive the Support Package. Move them into the directory importedFiles, for example.
Bff#?
Cw[47^d9Oyo
_zu3EVeK/aV7pbX Bff#?
Ct[>-7^s9WyoH_Czu!E5V7s#a[V7p6`lv-.PAlncBU~>:

36/44

PUBLIC

2012-04-18

A A.1

Appendix List of Referenced Documentation

A Appendix

A.1 List of Referenced Documentation

The following table lists all documents that are referenced in the present document.
Documentation Location
http://service.sap.com/upgradenw73

Upgrade Master Guide for SAP NetWeaver 7.3 Planning Guide System Landscape Directory Update Guide Update of SAP Systems with the Software Update Manager 1.0 Upgrade Guide SAP NetWeaver 7.3 <Technology> for <Operating System><Database> Upgrade Guide SAP Solution Manager 7.0 incl. Enhancement Package 1 Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 Solution Operations Guide SAP Solution Manager 7.0 EHP1, section Software Change Management Maintenance Optimizer Configuration Guide

Planning

http://sdn.sap.com/irj/sdn/nw-sld

http://service.sap.com/upgradenw73

http://service.sap.com/upgradenw73

http://service.sap.com/instguides

SAP Components

SAP Solution Manager

Release 7.0 EHP1

http://service.sap.com/mopz (link at the bottom of the page)

A.2 List of Referenced SAP Notes

SAP Note Number Title

1390477 1528990 1436297 1344564 1429764 1468605 1405648 1450419

Additional Information for Upgrade to SAP NetWeaver 7.3 SP Equivalence for update/upgrade to SAP NW 7.30 Maintenance Optimizer: Notes for Enhancement Packages Maintenance Optimizer: Check system landscape Automatic assignment of products in SMSY Installing ST-LV 100 on SAP Solution Manager 7.0 BPE-HT: Job SWEQSRV not scheduled after startup of BPE Configuration Wizard: PI EHP Update

2012-04-18

PUBLIC

37/44

A A.2

Appendix List of Referenced SAP Notes Title

SAP Note Number

669669

Updating the SAP Component Repository in the SLD

38/44

PUBLIC

2012-04-18

Reference

B Reference

2012-04-18

PUBLIC

39/44

Typographic Conventions

Example
<Example>

Description

Example Example Example

Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 _]e Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. _]e Cross-references to other documentation or published works _]e Output on the screen following a user action, for example, messages _]e Source code or syntax quoted directly from a program _]e File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools 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 Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

40/44

PUBLIC

2012-04-18

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

Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/ OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

2012-04-18

PUBLIC

41/44

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer

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

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

42/44

PUBLIC

2012-04-18

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

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