You are on page 1of 22

Upgrade and Update Guide SAP Enhancement Package 1 for SAP NetWeaver 7.

3 Java
Preparation and Follow-Up Activities
Target Audience ■ System Administrators ■ Technology Consultants

PUBLIC Document version: 1.0 – 2011-11-21

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

2011-11-21

First version

2/22

PUBLIC

2011-11-21

. . . . . . . .3 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . .1 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Free Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 2. Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . .4 3. . Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Chapter 1 1. . . . . . . . . . . . . . . . . . . . 13 13 16 17 17 18 2011-11-21 PUBLIC 3/22 . . . . . . . . 10 Updating SLD Content of the Source System . . . . . . . . . . . . . . . . . . 10 Follow-Up Activities After the Update . . . . . . . . . . . . . . . . . . . . . . . . . . .2 1. . . . . . .4 Chapter 3 3. . . . . . . . . .1 2. . . . . . . . . . . . . . . . . . PI: Using a Wizard for Automated Processing of Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . ESR: Performing Follow-Up Activities for the Enterprise Services Repository . . . . . . . . . . . . . . . . . . . . . . . . . .5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESR: Using a Wizard for Automated Processing of Follow-Up Activities .3 2. . . . . . . . About this Document . . . . . . . . . . . . . . . . . . . .1 1. . . . . . . . . . . . . . . 5 5 5 6 Preparations for the Update . . . . . . . . . . . . . . . . . 9 Providing the JCE Jurisdiction Policy Files for Adobe Document Services . . .3 Chapter 2 2. . . . . . . . . . . . . . . . . . . . . EP: Checking the KMC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

sap. enhancement package installation and Support Package Stacks application.3 Java or when you apply Support Package Stacks to SAP enhancement package 1 for SAP NetWeaver 7.com/notes). and troubleshooting information.com/sltoolset. some of which you must read before you start with the preparations.com/instguides. For clarity and readability. Integration In addition to this guide. see SAP Service Marketplace at http:// service. you need the following documents: ■ Master Guide (or Upgrade Master Guide if such exists as a separate guide) for your product The Master Guide (or Upgrade Master Guide) guides you through the complete update process and refers you to the required documentation for each step.1 About this Document Purpose 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. information about using the Software Update Manager. To find the latest version of these documents.sap. When you actually perform the update. 1.1 Introduction About this Document 1 Introduction 1.1 1.3 Java.2 SAP Notes To prepare and perform the update of your SAP system. the generic term “update” is used in this document in the context of release upgrade. preparation and follow-up activities. ■ Update Guide – Update of SAP Systems Using Software Update Manager <version> To find the latest version of 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 2011-11-21 PUBLIC 5/22 . see SAP Service Marketplace at http:// service. This document supplements the document Update Guide – Update of SAP Systems Using Software Update Manager <version> which includes general planning. you require some additional information that is not included in this document. you may need information from some additional SAP Notes. These SAP Notes are named at the appropriate places in this document. This information is in a range of SAP Notes in SAP Support Portal (http://service.sap.

The following list contains these SAP Notes: SAP Note Number Description 669669 907897 1393764 1562025 1444305 Updating the SAP Component Repository in the SLD Errors when updating SAP CIM model to Version 1.com/nw73 Application Help http://help. 6/22 PUBLIC 2011-11-21 .com/nwce711 Application Help http://help.com/nwce71 Application Help http://help. this document also refers you to other SAP Notes that contain additional information.2 Local Installation of the SAP NetWeaver Library Application Help http://help.1 SAP NetWeaver Composition Environment 7.3 including enhancement package 1 SAP NetWeaver 7.1 including enhancement package 1 SAP NetWeaver Composition Environment 7.com/nw731 http://help.sap. make sure that you always use the latest version. ■ Local installation of the SAP NetWeaver Library Before the update. Procedure SAP NetWeaver Library on SAP Help Portal Follow the applicable path to the SAP NetWeaver Library on SAP Help Portal: Release Path SAP NetWeaver 7. you need to install the documentation for the target release. during and after the update.0) Configuration Wizard: PI-AEX EHP Upgrade Configuration Wizard: PI / ESR Support Package Update 1.5 or higher Updating the SAP Component Repository SLD (from 1.1 1.3 Introduction Accessing Documentation ■ Application-specific update Note: 1606172 ■ SAP Note for your database Since these SAP Notes are updated regularly.3 Accessing Documentation Before.sap. Other SAP Notes As well as the SAP Notes you need for the preparation. After the update.x to 2.sap. make sure that you can read the documentation DVD offline.sap. you must read the online documentation for the target release on the DVD.3 SAP NetWeaver Composition Environment 7.com/nwce72 Application Help Before and during the update.sap. 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.

1 1. 2011-11-21 PUBLIC 7/22 . use the documentation version on SAP Help Portal.3 Introduction Accessing Documentation RECOMMENDATION If there is a Support Package available for the documentation.

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

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.1 including enhancement package 1 ■ SAP NetWeaver Composition Environment 7.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. If you update an SAP NetWeaver system containing various usage types.3 ■ SAP NetWeaver Composition Environment 7. 2011-11-21 PUBLIC 9/22 . Before the update.2 ■ SAP NetWeaver Composition Environment 7.1 Checking the Free Space Requirements Make sure that at least the following free space is available in the system that you want to update: SUM Directory Download Directory (temporary space requirement) Approximately 15 GB Approximately 20 GB 2. You can prepare for the update while the system is in production operation. 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 9] ■ Only valid for: Adobe Document Services | Providing the JCE Jurisdiction Policy Files for Adobe Document Services [page 10] End of: Adobe Document Services | ■ Updating SLD Content of the Source System [page 10] 2.2 Checking the Source Release of the SAP System NOTE This step is not required if you apply a Support Package Stack. make sure that your source system is on any acceptable Support Package level for all usage types implemented in the system.1 Different SAP NetWeaver usage types have different minimum Support Package levels. Careful preparation of the update is the best guarantee that it runs without errors.2 2.

The version of the files which must be available in your system depends on the JVM version of the target release. the Software Update Manager prompts you to provide a path to a compatible version of the files. The SLD content consists of the following parts: 10/22 PUBLIC 2011-11-21 . Log on to AS Java as user Administrator. Only valid for: Adobe Document Services | 2. Procedure Procedure for Java Systems To determine the source release and Support Package level of your SAP system. If the files are not installed or incompatible. During the update. proceed as follows: 1. The current release and Support Package level are displayed under Version in the Software Components table. Otherwise. you download the latest SLD content from SAP Service Marketplace and import it into the SLD. To do this. 3.4 Updating SLD Content of the Source System Before you start the update process. you must provide the JCE unlimited strength jurisdiction policy files. the Software Update Manager checks if the JCE files are installed in your system and if their version is compatible with the JVM version. you need to update the System Landscape Directory (SLD) content of your source system. check whether the equivalent Support Package for the target release is already available.2 2. The required version is displayed on the screen. Choose System Information. this may delay your update schedule. NOTE Make sure that you also update the central SLD if it is located on a remote host.html 2. Go to the AS Java start page: http://<host name>:<port>/index. CAUTION If you have to apply Support Packages to your source release shortly before the update. End of: Adobe Document Services | 2.3 Providing the JCE Jurisdiction Policy Files for Adobe Document Services To update usage type Adobe document Services.3 Preparations for the Update Providing the JCE Jurisdiction Policy Files for Adobe Document Services NOTE The Software Update Manager will check whether your source release is supported for this update.

NOTE If no CR Content version is available. To find this information.3 | Function-Oriented View <Language> Solution Life Cycle Management Configuring. you must always import the latest SLD content into each SLD. Select the latest file. Therefore. CAUTION 4. go to SAP Service Marketplace (SMP) at: http://service. 3.1.sap.4.zip. Procedure 1.SAP NetWeaver 7. To download the required updates.5.com/patches Browse our Download Catalog On the next page.. you must initially fill the SLD.32 is the version of the CIM data model and SAP_CR 3. This is located under SAP CR CONTENT UP TO <yyyy> (<yyyy> is the current year) and has the file name cimsap. Working with and Administering System Landscape Directory Administrating the SLD End of: Source Release = SAP NetWeaver 7. this provides the initial content. Download the current CIM model. Determine the versions of the CIM data model and CR Content that are available in the SLD of your source release of the update. If the version of a CIM data model to be imported is lower than 1.4 Preparations for the Update Updating SLD Content of the Source System ■ Component Repository Content (CR Content) ■ Common Information Model (CIM) data model NOTE The CR Content and the CIM data model are independent from the SLD release. choose SAP Technology Components SAP CR CONTENT .. see the SAP Library [page 6] for your source release at: Only valid for: Source Release = SAP NetWeaver 7. For more information about configuring the SLD. Prerequisites To import the updated content into the System Landscape Directory. Download the necessary CR Content delta updates.2 2.3 | 2..SAP NetWeaver 7. When you install the system. For example.31. open the SLD and choose Administration Details Data .2 | SAP Library <Language> Administrator's Guide Administration of SAP NetWeaver CE Configuring. proceed as described in SAP Note 907897. 1.2 | Only valid for: Source Release = SAP NetWeaver 7. Working with and Administering System Landscape Directory Administrating the SLD End of: Source Release = SAP NetWeaver 7.1.10 the version of the CR Content. you require administration authorization. The following table contains the required updates depending on the version of the SLD content in the SLD of your source release of the update (the current version of your CR Content): 2011-11-21 PUBLIC 11/22 .

CRDelta41514_0-10006428. and still choose Cancel Import. 6.7. download the latest data model cimsap.. When you repeat the import of a delta that has already been imported successfully.4 Preparations for the Update Updating SLD Content of the Source System Initial Version of CR Content Required SMP Entry Point and Update Files From 1.ZIP.zip and the following files: CRDelta1511_0-10004549. The warnings are caused by an error when selecting the entry point on SAP Service Marketplace. For some archives. the import is not carried out. The update contains all the changes as of the initial status (aggregate of all updates). It ignores all changes that you have already imported.0 From 3.0 From 5.ZIP.. choose Administration Details Data ...0 From 4.ZIP SMP entry point: SAP CR CONTENT UP TO 2009 File name: CRDelta515*.x to 4. To check the version of the content that you have imported into the SLD. For more information.. For example. ■ Import the CR Content update file(s) CRDelta. x to 2..0 File name: CRDelta1418_0-10003379. The system does not unpack the archives but imports them as a ZIP file.ZIP 5. Repeat steps 1 and 2.zip. and the latest file CRDelta515*. The program only imports the changes that are not already present in your Component Repository.zip into the SLD. see SAP Note 1393764.ZIP SMP entry point: SAP CR CONTENT UP TO 2008 File name: CRDelta41514_0-10006428. 12/22 PUBLIC 2011-11-21 .. go to the SLD start page and choose Administration Import . check whether you need to consider further details in your case. which is correct.ZIP SMP entry point: SAP CR CONTENT UP TO 2007 File name: CRDelta1511_0-10004549.. if you are using the current CR Content 3.x to 5. To import the content into the SLD.2 2. you need to follow particular instructions that are described at the end of this section. perform the following activities: ■ To import the CIM model update file(s) cimsap. You must not ignore any warning messages here..ZIP.x to 3. SMP entry point: SAP MASTER DATA FOR SLD 2.0 From 2. You have now downloaded the required archives.y (latest version) End of maintenance reached.x to 5. Before the import.

If you find errors.3 3. Log on to the portal as a user with the super administrator role.Process Integration (PI) | ■ ■ Only valid for: Enterprise Services Repository | ESR: Using a Wizard for Automated Processing of Follow-Up Activy [page 17] End of: Enterprise Services Repository | Only valid for: Enterprise Services Repository | ESR: Performing Follow-Up Activities for the Enterprise Services Repository [page 18] End of: Enterprise Services Repository | Only valid for: Enterprise Portal (EP) | 3. Log on to the portal as a user with the super administrator role.Process Integration (PI) | PI: Using a Wizard for Automated Processing of Follow-Up Activity [page 17] End of: PI Adapter Engine.1 Follow-Up Activities After the Update EP: Checking the KMC Installation 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. Checking the Component Monitor 1. 2011-11-21 PUBLIC 13/22 . Choose Content Administration KM Content and check whether any errors are displayed. 2.1 EP: Checking the KMC Installation NOTE This step is not required if you apply a Support Package Stack. then check the deployment and the log files. Choose System Administration Support Knowledge Management Component Monitor . 2. Actions You must perform the following actions before you resume production operation of your system: ■ Only valid for: Enterprise Portal (EP) | EP: Checking the KMC Installation [page 13] End of: Enterprise Portal (EP) | ■ Performing Follow-Up Activities for the System Landscape Directory [page 16] ■ Only valid for: PI Adapter Engine. Use the KM Content iView and the KM Component Monitor to find out whether you can start up the system without any errors. Procedure Checking the KM Content iView 1.

examine both the application and content files. 14/22 PUBLIC 2011-11-21 .netweaver. Checking the Deployment If the portal does not start up after the installation. or you notice errors in the Knowledge Management component monitor. Switch to the directory that contains the files for the deployment of KM and Collaboration content: 3. Try to correct the error in the system configuration.sap.sap.err file.* ■ com.* ■ com. and Tracing Component Monitor . 1. then check the deployment. but the extension is . see the online documentation at http:// help.ib. In this case.sap. read the error message. For Filters.1 Follow-Up Activities After the Update EP: Checking the KMC Installation 3. ■ Red shows the object cannot be started or is configured incorrectly.3 3.bi.* ■ com. When you check the deployment. but an error occurred.com/nw731 Application Help Function–Oriented View <Language> SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management Administration Guide System Administration Monitoring. ■ Yellow indicates that one or more lower-level items are red.km. Switch to the directory that contains the deployment files for the Knowledge Management and Collaboration applications: Only valid for: UNIX | /usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/ server0/apps/sap. If an object has the status red. Repository Services and Services. Check whether any of the following files have the extension . For more information about the configuration.err: ■ com. The log file has the same name as the .err this indicates that the deployment was executed. Logging. find out the reason for the error in the corresponding log file. 4.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcd End of: UNIX | Only valid for: IBM i5/OS | /usr/sap/<SID>/<instance_name>/j2ee/cluster/ server0/apps/sap.* If any files have the ending . The colors beside the entries indicate the following: ■ Green shows the object is functioning well.log.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcd End of: IBM i5/OS | Only valid for: Windows | <Drive>:\usr\sap\<SAPSID>\<instance_name>\j2ee\cluster\server0\apps\ sap.sap. Repository Managers.sap.workflow.com\irj \servlet_jsp\irj\root\WEB-INF\deployment\pcd End of: Windows | 2. check whether all subentries have the status green.

err.bi.log file to find out what caused the error.* ■ com.km* files have the ending .sap. then check the available trace file.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcdContent End of: UNIX | Only valid for: IBM i5/OS | /usr/sap/<SID>/<instance_name>/j2ee/cluster/ server0/apps/sap. If errors appear in the trace file.trc with the most recent date. Check whether any of the following files have the extension .err: ■ com.sap.km. Checking the Log Files If the portal does not start up after the installation of Content Management and Collaboration or you notice errors in the KM Content iView.3 3.sap. NOTE You can also view the trace file using the Log Administrator.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcdContent End of: IBM i5/OS | Only valid for: Windows | <Drive>:\usr\sap\<SAPSID>\<instance_name>\j2ee\cluster\server0\apps\ sap.ib. try to solve them and then restart the AS Java. Switch to the directory: Only valid for: Windows | <Drive>:\usr\sap\<SAPSID>\<instance_name>\j2ee\cluster\server0\log\ End of: Windows | Only valid for: UNIX | /usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/log/ End of: UNIX | Only valid for: IBM i5/OS | /usr/sap/<SID>/<instance_name>/j2ee/cluster/server0/log/ End of: IBM i5/OS | 2.sap.com\irj \servlet_jsp\irj\root\WEB-INF\deployment\pcdContent End of: Windows | 4.*.netweaver.sap. End of: Enterprise Portal (EP) | Viewer that is available in the SAP NetWeaver 2011-11-21 PUBLIC 15/22 .1 Follow-Up Activities After the Update EP: Checking the KMC Installation Only valid for: UNIX | /usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/ server0/apps/sap.workflow. Open the file defaultTrace.* ■ com.* ■ com. 1.* If any of the com. Also check the AS Java log files mentioned below. check the corresponding .

■ If the SLD was not configured in your source release system but you want to use it in your target release system. Procedure ■ If the SLD was configured in your source release system. 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 <Language> Application Server Application Server Infrastructure Configuring. 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. see SAP Note 669669. whether the SLD was configured or not. Working with and Administering System Landscape Directory Connecting Systems to the SLD Connecting AS Java Systems to the SLD Configuring the SLD Client 16/22 PUBLIC 2011-11-21 .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. proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View <Language> Solution Life Cycle Management Configuring. Proceed as described in the SAP Library [page 6] 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 [page 10].2 Follow-Up Activities After the Update Performing Follow-Up Activities for the System Landscape Directory 3.3 3. We recommend that you download the latest SLD content from SAP Service Marketplace and import it into the SLD. Working with and Administering System Landscape Directory Administering the SLD In either situation. 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 <Language> Application Server Application Server Infrastructure Configuring. For more information.

For more information about this task. perform the following steps: 1. You can use a configuration wizard to automate the following follow-up activities after you have performed the update.4 ESR: Using a Wizard for Automated Processing of FollowUp Activities NOTE This section only applies if you perform an SP Stack update. To start SAP NetWeaver Administrator. 5. The following follow-up steps are then processed automatically: ■ The relevant service users are checked ■ SLD on local host only: The System Landscape Directory (SLD) content for the enhancement package is imported ■ The ESR content for the enhancement package (software component version SAP BASIS 7. 2. To operate the wizard.3 PI: Using a Wizard for Automated Processing of Follow-Up Activities NOTE This section only applies if you perform an enhancement package installation of Advanced Adapter Engine Extended. When prompted by the wizard. Advanced Adapter Engine Extended only: Select PI Advanced Adapter Engine Extended (AEX) EHP Upgrade and choose Start. Log on with your AS Java administrator user. 6. perform the following steps: 2011-11-21 PUBLIC 17/22 . 4. choose All Configuration Tasks (dropdown box).31) is imported [page 18] ■ The new technical system is assigned to the system description of the Advanced Adapter Engine in the SLD End of: Process Integration (PI) | Only valid for: Enterprise Services Repository | 3. Choose Configuration Scenarios Configuration Wizard. From Configuration View. 3.3 Follow-Up Activities After the Update PI: Using a Wizard for Automated Processing of Follow-Up Activities Only valid for: Process Integration (PI) | 3. If you want to repeat the update process. You can use a configuration wizard to automate the following follow-up activities after you have performed the update.3 3. To operate the wizard. see SAP Note 1562025. go to http://<host>:<port>/nwa. choose Re-execute. provide the required entries (users and passwords).

To start SAP NetWeaver Administrator. see SAP Note 1444305. End of: Source Release = SAP NetWeaver 7. You have to update the SAP BASIS content by manually importing the ESR content. choose All Configuration Tasks (dropdown box). 5. For more information about this task. choose Re-execute. Choose Configuration Scenarios Configuration Wizard. Open this start page by calling it either from your user menu or with Transaction SXMB_IFR. go to http://<host>:<port>/nwa. You start the Enterprise Services Builder or the Integration Builderby means of an HTML start page. Choose Enterprise Services Repository. Procedure 1. Log on to the SAP system on which your Enterprise Services Builder has been installed. From Configuration View.3 | 6. The ESR content for the enhancement package (software component version SAP BASIS 7. provide the required entries (users and passwords). The follow-up steps are then processed automatically. Log on with your AS Java administrator user. perform the following steps: 1. 3. 18/22 PUBLIC 2011-11-21 . Only valid for: Source Release = SAP NetWeaver 7. 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. It has been covered by the wizard. yo do not need to perform this follow-up step. Start the Enterprise Services Builder and call the Enterprise Services Repository: To do this.31) is imported [page 18] End of: Enterprise Services Repository | Only valid for: Enterprise Services Repository | 3.3 3.5 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. 4. 2.3 | Select PI / ESR Support Package Update and choose Start.5 Follow-Up Activities After the Update ESR: Performing Follow-Up Activities for the Enterprise Services Repository 1. When prompted by the wizard. 3. 2. If you want to repeat the update process.

Choose Server. from whose naming convention you can derive the Support Package. Choose Tools Import design objects . You can only select files from the following import directory: ■ Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\import ■ UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import ■ 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 actual ESR content files have the extension “. Take one of the following precautions to retain the overview of the imported ESR content: ■ If the release and the Support Package are clear from the file name of the TPZ file. you can keep the packed files.3 3. If a file with the same file name already exists in the directory importedFiles. this information is important for support. Copy the ESR content into the following import directory for the Enterprise Services Repository: ■ Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\import ■ UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import ■ IBM i: /usr/sap/<SID>/SYS/global/xi/repository_server/import CAUTION 3. SAP recommends that you import ESR content from the server directory.tpz”. for example. The import directory is created the first time you call the Enterprise Services Builder. End of: Enterprise Services Repository | 2011-11-21 PUBLIC 19/22 . 5. Move them into the directory importedFiles. This enables you to check which file was imported last.5 Follow-Up Activities After the Update ESR: Performing Follow-Up Activities for the Enterprise Services Repository 2. ■ After a successful import. simply leave the files in the directory importedFiles (as described above). the Enterprise Services Builder adds the date and time of the import to the file name of the imported export file. ESR content can be imported either from a server directory or from a directory of your local PC (Client). the Enterprise Services Builder moves the imported TPZ files into the following directory: ■ Windows: \usr\sap\<SAPSID>\SYS\global\xi\repository_server\importedFiles ■ UNIX: /usr/sap/<SAPSID>/SYS/global/xi/repository_server/importedFiles ■ 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. You must not unpack these files. If an error occurs. 4.

for example. names of variables and parameters. for example. for example. pushbutton labels. SAP Note 123456 ■ Words or characters quoted from the screen. for example. SELECT and INCLUDE Keys on the keyboard http://www. These include field labels. These include report names. database table names. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action. and key concepts of a programming language when they are surrounded by body text.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.com /example 123456 Example Example EXAMPLE EXAMPLE 20/22 PUBLIC 2011-11-21 . for example. transaction codes.sap. messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths. program names. menu names. “Enter your <User Name>”. and names of installation. 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. screen titles. upgrade. and database tools Technical names of system objects. Arrows separating the parts of a navigation path. and menu options.

PowerPC. System Storage. Web Intelligence. XHTML and W3C are trademarks or registered trademarks of W3C®. z/OS. Adobe. i5/OS. System i5. System z9. National product specifications may vary. Acrobat. z10. Crystal Decisions. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. if any. and SAP Group shall not be liable for errors or omissions with respect to the materials. and PowerPoint are registered trademarks of Microsoft Corporation. ICA. Massachusetts Institute of Technology. iAnywhere. z9. Sybase is an SAP company. the Adobe logo. xSeries. DB2 Connect. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase. Intelligent Miner. POWER. 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. Sybase 365. MetaFrame. Duet. RACF. Citrix. without representation or warranty of any kind. SAP NetWeaver. GPFS. HACMP. System x. SAP BusinessObjects Explorer. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Business Objects is an SAP company Sybase and Adaptive Server. Disclaimer Some components of this product are based on Java™. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap. System z10. System z. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. IBM. POWER6. BusinessObjects. PostScript. Oracle and Java are registered trademarks of Oracle. OS/2. Linux is the registered trademark of Linus Torvalds in the U. and Motif are registered trademarks of the Open Group. pSeries. Redbooks. Program Neighborhood. Inc. Parallel Sysplex.S. AIX. OS/390. OSF/1. XML. SAP. R/3. Business Objects and the Business Objects logo. StreamWork. PowerVM. Data contained in this document serves informational purposes only. OpenPower. zSeries. POWER5+. Inc. 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. DB2. as is any decompilation of these components. Crystal Reports. Power Architecture. and other countries.sap. Xcelsius. The information contained herein may be changed without prior notice. WebSphere. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. iSeries. World Wide Web Consortium. DB2 Universal Database. POWER6+. BladeCenter. OS/400. ByDesign. X/Open. Windows. PartnerEdge. All rights reserved. SAP HANA. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. POWER5. and MultiWin are trademarks or registered trademarks of Citrix Systems. Nothing herein should be construed as constituting an additional warranty. HTML. S/390 Parallel Enterprise Server. Outlook. VideoFrame. These materials are subject to change without notice. RETAIN. Excel. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. System p. z/VM. System p5. eServer. Netfinity. System i.com/instguides 2011-11-21 PUBLIC 21/22 . AS/400.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. 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. BatchPipes. S/390. WinFrame. Microsoft.com © Copyright 2011 SAP AG. MVS/ESA. All other product and service names mentioned are the trademarks of their respective companies. UNIX. SQL Anywhere.

com © Copyright 2011 SAP AG.sap. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. All rights reserved. The information contained herein may be changed without prior notice. .