Sapupgrade PI (ABAP+Java)

Upgrade and Update Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3 ABAP+JavaPreparation and Follow-Up ActivitiesTarget Audience System Administrators Technology Consultants

PUBLIC Document version: 1.0 2012-05-15

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/ instguides. The following table provides an overview of the most important document changes.Version Date Description

1.0

2012-05-15

Initial version

2/36

PUBLIC

2012-05-15

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Chapter 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 5 5 6

Preparations for the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Free Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . . . . . . . . 10 Taking Note of Activated ICM Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PI: Task Related to Background Job SWEQSRV . . . . . . . . . . . . . . . . . . . . . . . . 11 PI: Handling Inactive IDOCs and RFCs in the Integration Repository During the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PI: Archiving Messages in the PI Adapter Framework . . . . . . . . . . . . . . . . . . . . 12 PI: Resolving Inconsistencies in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . 12 PI: Conversion Agent by Informatica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Updating SLD Content of the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Follow-Up Activities After the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Using a Wizard for Automated Processing of Selected Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Create Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Generating Profiles for Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Creating Java RFC Destination XI_EXCHANGE_PROFILE . . . . . . . . . . . PI: Performing Follow-Up Activities for the Service Users . . . . . . . . . . . . . . . . PI: Performing Queue Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Adjusting the Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the ICM Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 16 17 19 19 20 21 23 23 24 24

2012-05-15

PUBLIC

3/36

3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 3.2.14 3.2.15 3.2.16 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11

PI: Creating Java RFC Destination BusinessProcessEngine_RFC . . . . . . . . . . PI: Create ABAP HTTP Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Create ABAP Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Creating ABAP Background Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Executing Workflow Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Configure Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Importing ESR Content for Software Component SAP_BASIS . . . . . . . . . . PI: Merging Exchange Profile Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Migrating Java Proxy-Based Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Setting Up a High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Adjusting the Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Performing Follow-Up Activities for UDDI . . . . . . . . . . . . . . . . . . . . . . . . . PI: Creating a Destination from AS Java to AS ABAP for Integration Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Rescheduling PI-Specific Background Jobs . . . . . . . . . . . . . . . . . . . . . . . . . Performing Application-Specific Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Specifying the Development Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . Publishing ITS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25 26 26 26 27 27 27 28 28 29 29 30 30 30 31 31 32

4/36

PUBLIC

2012-05-15

1 1.1

Introduction About this Document

1 Introduction

1.1 About this DocumentPurpose

This document describes the preparation and follow-up activities that you need to perform when you update your SAP system to SAP enhancement package 1 for SAP NetWeaver 7.3 (ABAP+Java) or when you apply Support Package Stacks to SAP enhancement package 1 for SAP NetWeaver 7.3 (ABAP+Java). For clarity and readability, the generic term update is used in this document in the context of release upgrade, enhancement package installation and Support Package Stack application. This document supplements the document Update Guide Update of SAP Systems Using Software Update Manager which includes general planning, preparation and follow-up activities, information about using the Software Update Manager, and troubleshooting information.Integration

In addition to this guide, you need the following documents: Upgrade Master Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3 The Upgrade Master Guide guides you through the complete update process and refers you to the required documentation for each step. To find the latest version of this document, see SAP Service Marketplace at http:// service.sap.com/upgradeNW73. Update Guide Update of SAP Systems Using Software Update Manager To find the latest version of this document, see SAP Service Marketplace at http:// service.sap.com/sltoolset Software Logistics Toolset 1.0 SUM .

1.2 SAP NotesTo prepare and perform the update 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 in SAP Support Portal (http://service.sap.com/notes), some of which you must read before you start with the preparations. When you actually perform the update, you may need information from some additional SAP Notes. These SAP Notes are named at the appropriate places in this document.SAP Notes for Preparing the Update

You must request the following SAP Notes from SAP Support Portal before you start the update process: Central Software Update Manager Note

2012-05-15

PUBLIC

5/36

1 1.3

Introduction Accessing Documentation

Application-specific update Note: 1609441 SAP Note for your database Since these SAP Notes are updated regularly, make sure that you always use the latest version.Other SAP Notes

As well as the SAP Notes you need for the preparation, this document also refers you to other SAP Notes that contain additional information. The following list contains these SAP Notes:SAP Note Number Description

28022 669669 737625 888362 907897 1139642 1321868 1393764 1405648 1444305 1450419 1693104

Customer system: Where-used list of SAP objects Updating the SAP Component Repository in the SLD Parameter recommendations for the ICM Helpful technical hints for installing and maintaining MIC Errors when updating SAP CIM model to Version 1.5 or higher Hardware Requirements in Unicode Systems Configuration Wizard: PI Upgrade Updating the SAP Component Repository SLD (from 1.x to 2.0) BPE-HT: Job SWEQSRV not scheduled after startup of BPE Configuration Wizard: PI / ESR Support Package Update Configuration Wizard: PI Upgrade EHP PI Upgrade: Cache Connectivity Test failed

1.3 Accessing DocumentationBefore, during and after the update, you require the SAP online documentation. There are different ways to access the online documentation: SAP NetWeaver Library on SAP Help Portal You can access the documentation for all maintained product releases on SAP Help Portal. Local installation of the SAP NetWeaver Library Before the update, make sure that you can read the documentation DVD offline. After the update, you need to install the documentation for the target release.ProcedureSAP NetWeaver Library on SAP Help Portal

Follow the applicable path to the SAP NetWeaver Library on SAP Help Portal:

6/36

PUBLIC

2012-05-15

1 1.3

Introduction Accessing Documentation Pathhttp://help.sap.com/nw731

Release

SAP NetWeaver 7.3 including enhancement package 1 SAP NetWeaver 7.3 SAP NetWeaver Process Integration 7.1 SAP NetWeaver Process Integration 7.1 including enhancement package 1 SAP NetWeaver 7.0 SAP NetWeaver 7.0 including enhancement package 1 SAP NetWeaver 7.0 including enhancement package 2Local Installation of the SAP NetWeaver Library

Application Help http://help.sap.com/nw73 Application Help http://help.sap.com/nwpi71 Application Help http://help.sap.com/nwpi711 Application Helphttp://help.sap.com/nw70 http://help.sap.com/nw701 http://help.sap.com/nw702

Application Help Application Help Application Help

Before and during the update, you must read the online documentation for the target release on the DVD.RECOMMENDATION

If there is a Support Package available for the documentation, use the documentation version on SAP Help Portal.

2012-05-15

PUBLIC

7/36

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

2 2.1

Preparations for the Update Checking the Free Space Requirements

2 Preparations for the Update

This part of the document contains information about the preparations that you need to make before you update your system. You can prepare for the update while the system is in production operation. Careful preparation of the update is the best guarantee that it runs without errors. The Software Update Manager supports you here by making a range of checks automatically in the preparation roadmap steps (Initialization, Extraction, Configuration, and Checks). To make sure that all requirements are met, run the preparation roadmap steps of Software Update Manager as soon as possible. You can reset and repeat the preparation roadmap steps as often as you need by choosing Back before you start the actual procedure in roadmap step Preprocessing. The successful execution of the preparation roadmap steps is a prerequisite for starting the roadmap step Preprocessing. Actions You perform the following actions before you start the Software Update Manager: Checking the Free Space Requirements [page 9] Checking the Source Release of the SAP System [page 10] Taking Note of Activated ICM Services [page 11] PI: Task Related to Background Job SWEQSRV [page 11] Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Handling Inactive IDOCs and RFCs in the Integration Reposito [page 11]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Archiving Messages in the PI Adapter Framework [page 12]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Resolving Inconsistencies in the Database [page 12]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Upgrading Conversion Agent by Informatica [page 12]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

Updating SLD Content of the Source System [page 13]

2.1 Checking the Free Space RequirementsMake sure that at least the following free space is available in the system that you want to update:SUM Directory Approximately 20 GB

2012-05-15

PUBLIC

9/36

2 2.2

Preparations for the Update Checking the Source Release of the SAP System

Download Directory Approximately 20 GB (temporary space requirement) DIR_TRANS Approximately 20 GB Shadow System Approximately the space required for your source release instance, that is, the size of the following directory: UNIX: /usr/sap/ Windows: :\usr\sap\ IBM i: /usr/sap/

2.2 Checking the Source Release of the SAP SystemNOTE

This step is not required if you apply a Support Package Stack. Before the update, your SAP system must have one of the source releases that have been released for this update and apply to all databases: SAP NetWeaver 7.3 SAP NetWeaver Process Integration 7.1 including enhancement package 1 SAP NetWeaver Process Integration 7.1 SAP NetWeaver 7.0 including enhancement package 2 SAP NetWeaver 7.0 including enhancement package 1 SAP NetWeaver 7.0 SPS 05 (or higher) Different SAP NetWeaver usage types have different minimum Support Package Stack levels. If you update an SAP NetWeaver system containing various usage types, make sure that your source system is on any acceptable Support Package Stack level for all usage types implemented in the system.NOTE

Make sure that you include at least Support Package Stack 02 in the upgrade.NOTE

The Software Update Manager will check whether your source release is supported for this update.CAUTION

If you have to apply Support Packages to your source release shortly before the update, check whether the equivalent Support Package Stack for the target release is already available. Otherwise, this may delay your update schedule.ProcedureProcedure for ABAP Systems

To determine the source release of the SAP system, log on to the system and choose System Status .

10/36

PUBLIC

2012-05-15

2 2.3

Preparations for the Update Taking Note of Activated ICM Services

The release appears in the Component version field.Procedure for Java Systems

To determine the source release and Support Package Stack level of your SAP system, proceed as follows: 1. Go to the AS Java start page: http://:/index.html 2. Choose System Information. 3. Log on to AS Java as user J2EE_Admin. The current release and Support Package level are displayed under Version in the Software Components table.

2.3 Taking Note of Activated ICM ServicesThe 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.

2.4 PI: Task Related to Background Job SWEQSRVThe 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.Procedure

If the job was scheduled in the operation mode periodic in the source system, SAP Note 1405648 must be applied before starting the update.Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

2.5 PI: Handling Inactive IDOCs and RFCs in the Integration Repository During the UpgradeOnly active RFCs and IDOCs inside your Integration Repository are upgraded. Open change lists are not taken into account during the upgrade. If you have inactive IDOCs or RFCs in your system, follow the instructions below. To archive the messages, you have to minimize the retention time. You can manually set the retention time for messages to be expired. You can then remove these messages from the database immediately or archive them before deleting them.Procedure

To set the retention time for archiving, perform the following steps:

2012-05-15

PUBLIC

11/36

2 2.6

Preparations for the Update PI: Archiving Messages in the PI Adapter Framework

1. 2.

In a Web browser, enter the following URL:http://:/MessagingSystem/archiving/reorgdb.jsp.

Enter a number of days. For the messages that were sent or received earlier than the number of days you have specified, the retention time is reset so that you can delete them immediately from the database.NOTE

If you want to archive a large number of messages before deleting them, we recommend that you select groups of messages in several steps to adjust the retention time and then archive them. Archiving can be time-consuming and may impede the current message throughput.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

2.6 PI: Archiving Messages in the PI Adapter FrameworkIf you have scheduled an archiving job for the Adapter Framework or PCK, make sure that all messages are archived before you start the upgrade. If successfully finished messages are still in the database of the source release system, only their status information is migrated to the target release system. Therefore, the messages themselves are not accessible for the archiving job after the upgrade.Procedure

To archive the messages, proceed as described in SAP Note 807615.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

2.7 PI: Resolving Inconsistencies in the DatabaseTo prevent errors during the upgrade caused by inconsistent objects in the database, you must perform some checks before the upgrade and resolve these inconsistencies. If you do not perform the checks, the upgrade might stop during the downtime with a migration controller error.Procedure

For more information, see SAP Note 1154961.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

2.8 PI: Conversion Agent by InformaticaIf the Conversion Agent by Informatica exists in your source release system, proceed as described below.Procedure

Depending on your source release system, proceed in one of the following ways:

12/36

PUBLIC

2012-05-15

2 2.9

Preparations for the Update Updating SLD Content of the Source System

If your source release is SAP NetWeaver 7.0, SAP NetWeaver 7.0 including enhancement package 1 or SAP NetWeaver 7.0 including enhancement package 2, the Software Update Manager detects the Conversion Agent by Informatica and prompts you for a successor version. Since no successor exists, set it to remove. If your source release is SAP NetWeaver Process Integration 7.1, SAP NetWeaver Process Integration 7.1 including enhancement package 1 or SAP NetWeaver 7.3, remove the Conversion Agent by Informatica before you start the update process.

2.9 Updating SLD Content of the Source SystemBefore you start the update process, you need to update the System Landscape Directory (SLD) content of your source system.NOTE

Make sure that you also update the central SLD if it is located on a remote host. To do this, you download the latest SLD content from SAP Service Marketplace and import it into the SLD. The SLD content consists of the following parts: Component Repository Content (CR Content) Common Information Model (CIM) data modelNOTE

The CR Content and the CIM data model are independent from the SLD release. Therefore, you must always import the latest SLD content into each SLD.Prerequisites

To import the updated content into the System Landscape Directory, you require administration authorization.Procedure

Proceed as described in SAP Note 669669.

2012-05-15

PUBLIC

13/36

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

3

Follow-Up Activities After the Update

3 Follow-Up Activities After the Update

This part of the document contains information about the follow-up activities that you need to perform after you have updated your SAP system. When you perform follow-up activities, note the following information: Before you start the follow-up activities, you must have run the update up to and including the MODPROFP_UPG phase. The Software Update Manager stops in the MODPROFP_UPG phase and prompts you to start several follow-up activities. It then executes the last phases and completes the update. At the same time, you can already perform the specified follow-up activities. The follow-up activities are divided into three blocks: Actions needed before resuming production operation These actions ensure that all the processes that are relevant to system operation are available again. You can start these actions while the Software Update Manager is finishing the update. Actions during limited production operation During this time, your SAP system is already consistent and all the processes that are relevant to system operation are available. However, this system state does not yet contain measures for optimizing performance, or actions for resuming standard operation (resuming background processing, or adjusting authorizations, for example). Check the actions that are listed in this block and if necessary, perform them before you restart production operation. Actions during production operation You can also perform these actions when the system is back to production operation. Actions You must perform the following actions before you resume production operation of your system: Performing Follow-Up Activities for the System Landscape Directory [page 16] PI: Using a Wizard for Automated Processing of Selected Follow-Up Activity [page 17] Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Migrating Java Proxy-Based Applications [page 28]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: UNIX;Windows | Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Setting Up a High Availability System [page 29]End of: UNIX;Windows | Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Adjusting the Adapter Configuration [page 29]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

2012-05-15

PUBLIC

15/36

3 3.1

Follow-Up Activities After the Update Performing Follow-Up Activities for the System Landscape DirectoryOnly valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Performing Follow-Up Activities for UDDI [page 30]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Creating a Destination from AS Java to AS ABAP for Integration [page 30] PI: Rescheduling PI-Specific Background Jobs [page 30] Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP Web AS 6.40 | Performing Application-Specific Activities [page 31]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP Web AS 6.40 |

You can perform the following actions during limited production operation of your system: Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

PI: Specifying the Development Language [page 31]End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

Publishing ITS Objects [page 32]

3.1 Performing Follow-Up Activities for the System Landscape DirectoryNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. 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.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 [page 6] for your target release at: SAP Library SAP NetWeaver Security Guide Security Aspects for Lifecycle Management System Landscape Directory Security Guide Configuring SLD Security Roles Update the SLD content and data modelNOTE

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 [page 13]. 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 [page 6] for your target release at:

16/36

PUBLIC

2012-05-15

3 3.2

Follow-Up Activities After the Update PI: Using a Wizard for Automated Processing of Selected Follow-Up Activities

Function-Oriented View Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administrating the SLD In either situation, you also need to configure the following SLD components: SLD Data Supplier Proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View 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 [page 6] for your target release at: Function-Oriented View 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 ClientMore Information

After the update, if the access to the SLD is no longer possible for some users, see SAP Note 1617234.

3.2 PI: Using a Wizard for Automated Processing of Selected Follow-Up ActivitiesYou can use a configuration wizard to automate the following follow-up activities after you have performed the update:Source Release Follow - Up Activity

SAP NetWeaver 7.0 SAP NetWeaver 7.0 including enhancement package 1 SAP NetWeaver 7.0 including enhancement package 2

PI: Create Users [page 19] PI: Generating Profiles for Roles [page 19] PI: Creating Java RFC Destination XI_EXCHANGE_PROFILE [page 20] PI: Performing Follow-Up Activities for the Service Users [page 21] PI: Performing Queue Registration [page 23] PI: Adjusting the Exchange Profile [page 23] Activating the ICM Service [page 24] Performing Follow-Up Activities for the System Landscape Directory [page 24] PI: Creating Java RFC Destination BusinessProcessEngine_RFC [page 25] PI: Create ABAP HTTP Destinations [page 26] PI:Create ABAP Destinations [page 26] PI: Create ABAP Background Jobs [page 26]

2012-05-15

PUBLIC

17/36

3 3.2

Follow-Up Activities After the Update PI: Using a Wizard for Automated Processing of Selected Follow-Up Activities Follow - Up Activity

Source Release

PI: Execute Workflow Customizing [page 27] PI:Configure Alerting [page 27] Importing ESR Content for Software Component SAP_BASIS 7.31 [page 27] SAP NetWeaver Process Integration 7.1 PI: Create Users [page 19] SAP NetWeaver Process Integration 7.1 including PI: Generating Profiles for Roles [page 19] enhancement package 1 PI: Creating Java RFC Destination SAP NetWeaver 7.3 XI_EXCHANGE_PROFILE [page 20] PI: Performing Queue Registration [page 23] PI: Adjusting the Exchange Profile [page 23] Activating the ICM Service [page 24] PI: Performing Follow-Up Activities for the System Landscape Directory [page 24] PI: Creating Java RFC Destination BusinessProcessEngine_RFC [page 25] PI:Create ABAP Destinations [page 26] PI: Create ABAP Background Jobs [page 26] PI: Execute Workflow Customizing [page 27] PI:Configure Alerting [page 27] PI: Importing ESR Content for Software Component SAP_BASIS 7.31 [page 27] SAP NetWeaver 7.3 including enhancement PI: Performing Queue Registration [page 23] package 1 Activating the ICM Service [page 24] PI: Execute Workflow Customizing [page 27] PI: Importing ESR Content for Software Component SAP_BASIS 7.31 [page 27] PI: Merging Exchange Profile Properties [page 28]

To operate the wizard, perform the following steps: 1. To start SAP NetWeaver Administrator, go to http://:/nwa. 2. Log on with your AS Java administrator user. 3. Choose Configuration Scenarios Configuration Wizard . 4. From Automation Tasks, choose All Configuration Tasks (dropdown box). 5. Select the configuration task relevant for your source release and choose Start:Source Release Configuration Task Configuration Wizard Information

SAP NetWeaver 7.0 SAP NetWeaver 7.0 including enhancement package 1 SAP NetWeaver 7.0 including enhancement package 2 SAP NetWeaver Process Integration 7.1 SAP NetWeaver Process Integration 7.1 including enhancement package 1 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including enhancement package 1

PI Upgrade

SAP Note 1321868

PI Upgrade EHP

SAP Note 1450419

PI / ESR Support Package Update

SAP Note 1444305

18/36

PUBLIC

2012-05-15

3 3.2


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. If you cannot run these steps automatically, you have to perform them manually. For more information about the manual procedures, see the corresponding subsections in this guide listed above.

3.2.1 PI: Create UsersNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. After the upgrade you need to create user PICACHEUSER and assign the required roles for this user.Procedure

To create user PICACHEUSER, perform the following steps: 1. Log on as an administrator to your AS ABAP system. 2. Call transaction SU01. 3. Create user PICACHEUSER and define it as a system user (user type System) To assign the required roles for user PICACHEUSER, proceed as follows: 1. Log on as an administrator to your AS ABAP system. 2. Call transaction SU01. 3. Assign the following roles for this user: SAP_XI_CACHE_SERV_USER SAP_BC_WEBSERVICE_PI_CFG_SRV SAP_SLD_CONFIGURATOR

3.2.2 PI: Generating Profiles for RolesNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP 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 . 1. Select All Roles. 2. In the Role field, enter SAP_XI*.

2012-05-15

PUBLIC

19/36

3 3.2


3. 4.

3.

4.

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 .

3.2.3 PI: Creating Java RFC Destination XI_EXCHANGE_PROFILENOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. To connect to the Integration Server, you have to create the XI_EXCHANGE_PROFILE RFC destinationProcedure

1.

Start the SAP NetWeaver Administrator using the following URL:http://:/nwa

20/36

PUBLIC

2012-05-15

3 3.2


2. 3. 4.

Log on with your AS Java administrator user. Choose Configuration Infrastructure Destination Create the XI_EXCHANGE_PROFILE RFC destination with user PILDUSER as a logon user.

Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.4 PI: Performing Follow-Up Activities for the Service UsersNOTE

This step only applies if you have not used the PI Upgrade CTC Wizard to perform the basic configuration steps after the update. After the upgrade, you need to perform some follow-up activities for technical users and users possessing the role SAP_XI_APPL_SERV_USER: You need to switch the user type from Service to System. You need to assign new composite roles to some of the technical users. You need to perform this in the following systems: In the central user administration system (CUA) if you have configured the PI users there Locally in the XI Integration Server clientPrerequisites

Make sure that the Integration Server client is connected to your central user administration system (CUA). You can check this using transaction SCUA.ProcedureTechnical Users

1.

Find out the names of the following users: Service user for Exchange Profile maintenance See the Exchange Profile menu Connection in field User (the default value is PILDUSER). Service user representing the Integration Repository component See the Exchange Profile parameter com.sap.aii.repository.serviceuser.name (the default name is PIREPUSER). Service user representing the Integration Directory component See the Exchange Profile parameter com.sap.aii.directory.serviceuser.name (the default name is PIDIRUSER). Service user representing the Runtime Workbench component See the Exchange Profile parameter com.sap.aii.rwb.serviceuser.name (the default name is PIRWBUSER). Service user representing the Adapter Engine component

2012-05-15

PUBLIC

21/36

3 3.2


2.

3.

See the Exchange Profile parameter com.sap.aii.adapterframework.serviceuser.name (the default name is PIAFUSER). Service user representing the Integration Server component See the Exchange Profile parameter com.sap.aii.integrationserver.serviceuser.name (the default name is PIISUSER). Service user representing a generic application system component See the Exchange Profile parameter com.sap.aii.applicationsystem.serviceuser.name (the default name is PIAPPLUSER). Service user representing the CMS Transport system component In the CMS system, see Landscape Configurator Domain Data CMS User (the default name is LSADMIN). Change the user type from Service to System: In transaction SU01 individually for each user: 1. Call transaction SU01. 2. Enter the user name and choose Logon Data User type System . 3. Save the data. In transaction SU10, for all users in one action: 1. Call transaction SU10. 2. Enter all technical users in the list. 3. Choose User Data Change . 4. On the Logon tab page, change the user type to System and select Change. 5. Save the data. Assign the new composite roles to some of the users. The following table contains the information which role to assign to which user:Default User NamePI(XI)AFUSER PI(XI)DIRUSER PI(XI)REPUSER PI(XI)ISUSER PI(XI)RWBUSER

Composite RoleSAP_XI_AF_SERV_USER_MAIN SAP_XI_ID_SERV_USER_MAIN SAP_XI_IR_SERV_USER_MAIN SAP_XI_IS_SERV_USER_MAIN SAP_XI_RWB_SERV_USER_MAIN

1. 2. 3. 4.

Call transaction SU01. Enter the user name and choose Roles. Add the new role. Save the data.

Users with Role SAP_XI_APPL_SERV_USER

1. 2.

Call transaction SU10. To fill the list with users, proceed as follows:

22/36

PUBLIC

2012-05-15

3 3.2


3. 4. 5. 6.

1. Select an empty user field and choose F4 . 2. On the Users by system-specific roles tab page, enter SAP_XI_APPL_SERV_USER in the Role field. 3. In field Receiving System, enter the Integration Server system (in case of CUA). 4. Start the search. 5. Select all users and choose OK. Select all users in the list. Choose User Data Change . On the Logon tab page, change the user type to System and select Change. Save the data.

End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.5 PI: Performing Queue RegistrationNOTE

This step only applies if you have not used the PI Upgrade, PI Upgrade EHP, or PI/ESR Support Package Update CTC Wizard to perform the basic configuration steps after the update. As of SAP NetWeaver PI 7.1, the functionality for qRFC inbound queues has been enhanced. To use this functionality, you must register further qRFC inbound queues.Procedure

1. 2.

Call transaction SXMS_QREG. Choose Register Queues.

3.2.6 PI: Adjusting the Exchange ProfileNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. After the update you have to adjust the propertycom.sap.aii.connect.integrationbuilder.startpage.url. You also have to manually import new

Exchange Profile properties shipped with a new release.Procedure

1. 2.

Start the configuration UI (Exchange Profile) using the following URL:http:///webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

In the Connections section, change the entry for the propertycom.sap.aii.connect.integrationbuilder.startpage.url:

Replace rep/start/index.jsp with dir/start/index.jsp.

2012-05-15

PUBLIC

23/36

3 3.2


Merging Exchange Profiles Properties

Perform the steps described in the SAP Library [page 6] for your target release at: Function-Oriented View Process Integration Configuring Process Integration (PI) After Installation Basic Configuration (CTC Wizard-Assisted and Manual) Manual Configuration for Usage Type PI Upgrade/Update Exchange Profile Properties

3.2.7 Activating the ICM ServiceNOTE

This step only applies if you have not used the PI Upgrade, PI Upgrade EHP, or PI/ESR Support Package Update CTC Wizard to perform the basic configuration steps after the update. The Software Update Manager disables services of the Internet Communication Framework (ICF) during the update for security reasons. You have to activate the services that you require again after the update.Procedure

Call transaction SICF and activate the required services by executing function module SXMB_ACTIVATE_ICF_SERVICES.More Information

For information about parameter recommendations for the ICM, see SAP Note 737625.Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.8 Performing Follow-Up Activities for the System Landscape DirectoryNOTE

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

After the update, you have to create the SLDSLD Client User

Client and the SLD Data Supplier users.

1. 2. 3. 1.

Create the SLD Client User user and assign it to the SAP_SLD_CONFIGURATOR group. Add roles SAP_SLD_CONFIGURATOR, Guest and SAP_SLD_GUEST to group SAP_SLD_CONFIGURATOR. Create the HTTP destinations to the SLD_Client. Create the SLDData Supplier user and assign it to the SAP_SLD_DATA_SUPPLIER group.

SLD Data Supplier User

24/36

PUBLIC

2012-05-15

3 3.2


2. 3.

Add roles SAP_SLD_DATA_SUPPLIER, Guest and SAP_SLD_GUEST to group SAP_SLD_DATA_SUPPLIER. Create the HTTP destinations to the SLD_DataSupplier.

Assigning New Product in SLD

After the update, you must add the new product SAP EHP1 FOR SAP NW 7.3 to all technical systems and business systems. 1. Log on to the SLD system using the following command: http://:/sld. 2. Select Technical Systems and under Technical System Type AS ABAP Version 731. 3. Select the Installed Software tab and select Add New Product. A list of available products appears. 4. Select SAP EHP1 FOR SAP NW 7.3. 5. Assign the following components:SAP BASIS 7.31 SAP ABA 7.31 SAP BW 7.31

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.

End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.9 PI: Creating Java RFC Destination BusinessProcessEngine_RFCNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. After the update, you have to create the BusinessProcessEngine_RFC RFC destination.Procedure

To create the BusinessProcessEngine_RFC RFC destination, proceed as follows: 1. In the SAP NetWeaver Administrator, choose Configuration Management Infrastructure Destinations . 2. To create an RFC destination, choose Create. 3. Specify BusinessProcessEngine_RFC as the destination name, and RFC as the type. Apply the default values except for the following:

2012-05-15

PUBLIC

25/36

3 3.2


In the Connection section, set Load Balancing to No In the Authentication section, specify the user PIRWBUSEROnly valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.10 PI: Create ABAP HTTP DestinationsNOTE

This step only applies if you have not used the PI Upgrade CTC Wizard to perform the basic configuration steps after the update. After the update you have to create the INTEGRATION_DIRECTORY_HMI RFC destination on AS ABAP, which is used for the cache update.Procedure

To create the INTEGRATION_DIRECTORY_HMI RFC destination, proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View Process Integration Configuring Process Integration After Installation Configuring Process Integration (PI) Dual-Stack Basic Configuration (CTC Wizard-Assisted and Manual) Manual Configuration for Usage Type PI Create Destinations on the ABAP ServerEnd of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.2.11 PI: Create ABAP DestinationsNOTE

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

Create the RFC destination CUST_BACK.

3.2.12 PI: Creating ABAP Background JobsNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. After the update, you have to create the ABAP Background Jobs.Procedure

Perform the steps described in SAP Note 1492986.

26/36

PUBLIC

2012-05-15

3 3.2


3.2.13 PI: Executing Workflow CustomizingNOTE

This step only applies if you have not used the PI Upgrade, PI Upgrade EHP, or PI/ESR Support Package Update CTC Wizard to perform the basic configuration steps after the update. To be able to use the Business Process Engine, you have to configure the workflow customizing.Procedure

Perform the following steps in your AS ABAP system: 1. Call transaction SE37. 2. Execute function module SWF_XI_BPM_AUTO_UPG_CUST.

3.2.14 PI: Configure AlertingNOTE

This step only applies if you have not used the PI Upgrade or PI Upgrade EHP CTC Wizard to perform the basic configuration steps after the update. After the update, you have to configure the component-based message alerting function.Procedure

To configure the component-based message alerting function, proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View Process Integration Configuring Process Integration After Installation Configuring Process Integration (PI) Dual-Stack Basic Configuration (CTC Wizard-Assisted and Manual) Manual Configuration for Usage Type PI Configuring Component-Based Message Alerting

3.2.15 PI: Importing ESR Content for Software Component SAP_BASISNOTE

This step only applies if you have not used the PI Upgrade, PI Upgrade EHP, or PI/ESR Support Package Update CTC Wizard to perform the basic configuration steps after the update. Download the latest ESR content for software component SAP_BASIS 7.31 from SAP Service Marketplace and import it into your system.Prerequisites

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

2012-05-15

PUBLIC

27/36

3 3.3

Follow-Up Activities After the Update PI: Migrating Java Proxy-Based Applications

Procedure

To import the ESR content for the software component SAP_BASIS 7.31, proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View Process Integration Configuring Process Integration After Installation Configuring Process Integration (PI) Dual-Stack Basic Configuration (CTC Wizard-Assisted and Manual) Manual Configuration for Usage Type PI Importing ESR ContentOnly valid for: Source Release = SAP NetWeaver 7.3 |

3.2.16 PI: Merging Exchange Profile PropertiesNOTE

This step only applies if you have not used the PI/ESR Support Package Update CTC Wizard to perform the basic configuration steps after the update. After the update, you have to manually import new Exchange Profile properties shipped with a new release or support package.Procedure

Perform the steps described in the SAP Library [page 6] for your target release at: Function-Oriented View Process Integration Configuring Process Integration (PI) After Installation Basic Configuration (CTC Wizard-Assisted and Manual) Manual Configuration for Usage Type PI Upgrade/Update Exchange Profile PropertiesEnd of: Source Release = SAP NetWeaver 7.3 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.3 PI: Migrating Java Proxy-Based ApplicationsYou have built applications using Java Proxies that have been generated in your source release system. To enable your applications to run after the upgrade, you have to adapt some references inside the applications.Procedure

1.

Open the application-j2ee-engine.xml file, which is included in your application EAR file, and change the following references : The AS Java library com.sap.aii.proxy.runtime This library has been replaced by the service com.sap.aii.proxy.svc. Adapt the reference as follows: com.sap.aii.proxy.svc

28/36

PUBLIC

2012-05-15

3 3.4

Follow-Up Activities After the Update PI: Setting Up a High Availability System

The AS Java library com.sap.aii.messaging.runtime The library has been replaced by the library com.sap.aii.af.sdk.lib. Adapt the reference as follows: com.sap.aii.af.sdk.lib

2.

Deploy the EAR files in your SAP NetWeaver 7.3 including enhancement package 1 environment.

End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: UNIX;Windows | Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.4 PI: Setting Up a High Availability SystemYou may want to run your upgraded SAP NetWeaver PI system in a high availability environment. To do so, you have to perform a system copy of your system and thereby change the system variant.Procedure

Proceed as described in the document System Copy for SAP NetWeaver 7.3 Including Enhancement Package 1.End of: UNIX;Windows | Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.5 PI: Adjusting the Adapter ConfigurationYou have used the classes com.sap.aii.messaging.adapter.Conversion or com.sap.aii.messaging.adapter.XSLTConversion in one of the following cases: To configure the module AF_Modules/MessageTransformBean in an adapter configuration of your Advanced Adapter Engine To configure a dispatcher in an adapter configuration of your Adapter Engine (Java SE) After the upgrade, you have to adjust the configurations to make the scenarios work properly again.Procedure

Change the following: Instead of com.sap.aii.messaging.adapter.Conversion, use com.sap.aii.af.sdk.xi.adapter.Conversion. Instead of com.sap.aii.messaging.adapter.XSLTConversion, use com.sap.aii.af.sdk.xi.adapter.XSLTConversion. For more information, see the SAP Library [page 6] for your target release at:

2012-05-15

PUBLIC

29/36

3 3.6

Follow-Up Activities After the Update PI: Performing Follow-Up Activities for UDDI

Function-Oriented View Process Integration Integration Directory Integration Directory (Dual Stack) Defining Communication Channels Inserting Modules into Module Processor Inserting MessageTransformBean in Module ProcessorEnd of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.6 PI: Performing Follow-Up Activities for UDDISAP NetWeaver PI 7.1 including enhancement package 1 is shipped with a UDDI version 3 application, whereas SAP NetWeaver 7.0 and SAP NetWeaver 2004 have been shipped with UDDI version 2 applications. The UDDI version 3 application has a new database schema and a new user management. The upgrade program cannot migrate customer data from SAP NetWeaver 7.0 and lower automatically into the new UDDI version 3 database, since different user stores are used by the two UDDI versions.Procedure

For information about migrating customer data based on UDDI version 2, see SAP Note 1114056.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.7 PI: Creating a Destination from AS Java to AS ABAP for Integration Process MonitoringYou 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 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://:/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

3.8 PI: Rescheduling PI-Specific Background JobsIn 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.

30/36

PUBLIC

2012-05-15

3 3.9

Follow-Up Activities After the Update Performing Application-Specific Activities

Procedure

You must reschedule the following background jobs manually: Background Job for Missed Deadlines Background Job for Work Items with Errors Background Job for Event Queue Background Job for Clearing Report Background Job for Shared Memory Update of the Container Factory Background Job for Packaging 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.Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP Web AS 6.40 |

3.9 Performing Application-Specific ActivitiesProcedure

Some applications require you to perform 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. If you need to display Release Notes in your SAP system, proceed as follows: Call transaction SPRO and, in the IMG structure, choose Additional Information Release Notes . If you want to display the Release Notes independently from the IMG, choose Help Release Notes . When you choose this option for the first time, you are prompted to generate the Release Notes before you can display them.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP Web AS 6.40 | Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.10 PI: Specifying the Development LanguageAs of SAP NetWeaver PI 7.1, the attribute Original Language is required for software component versions in the Enterprise Service Repository. You can only create new and change existing software component versions after you have specified the original language.

2012-05-15

PUBLIC

31/36

3 3.11

Follow-Up Activities After the Update Publishing ITS Objects

Procedure

1. 2. 3.

Log on to the Enterprise Service Repository with a user having administration rights. Open the editor for your software component versions by double-clicking on the software component version in the navigation tree. In the Original Language field, enter the original language and save your changes.NOTE

You do not need to set the original language for the software component versions delivered by SAP since normally you do not modify them.End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.11 Publishing ITS ObjectsAfter the upgrade of your SAP NetWeaver system, ITS services might not be executable in the integrated ITS or the services that start might not behave as expected. You have to publish all ITS services available in the system to the integrated ITS.Procedure

Follow the steps described in SAP Note 790727.

32/36

PUBLIC

2012-05-15

Typographic Conventions

Example

Description

Example Example ExampleExample

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your . 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 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools 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

2012-05-15

PUBLIC

33/36

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.

34/36

PUBLIC

2012-05-15

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

2012-05-15

PUBLIC

35/36

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.

Documents

Sapupgrade PI (ABAP+Java)