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

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 Chapter 3 3.1 3.2 3.3 3.4 3.5

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 . . . . . . . . . . . . . . . . . . . . . . . . 9 Providing the JCE Jurisdiction Policy Files for Adobe Document Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Updating SLD Content of the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Follow-Up Activities After the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . EP: Checking the KMC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Using a Wizard for Automated Processing of Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESR: Using a Wizard for Automated Processing of Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESR: Performing Follow-Up Activities for the Enterprise Services Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 16 17 17 18

2011-11-21

PUBLIC

3/22

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

1 1.1

Introduction About this Document

1 Introduction

1.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.3 Java or when you apply Support Package Stacks to SAP enhancement package 1 for SAP NetWeaver 7.3 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 Stacks application. This document supplements the document Update Guide Update of SAP Systems Using Software Update Manager <version> 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: 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. To find the latest version of these documents, see SAP Service Marketplace at http:// service.sap.com/instguides. Update Guide Update of SAP Systems Using Software Update Manager <version> To find the latest version of this document, see SAP Service Marketplace at http:// service.sap.com/sltoolset.

1.2 SAP Notes

To 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

2011-11-21

PUBLIC

5/22

1 1.3

Introduction Accessing Documentation

Application-specific update Note: 1606172 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

669669 907897 1393764 1562025 1444305

Updating the SAP Component Repository in the SLD Errors when updating SAP CIM model to Version 1.5 or higher Updating the SAP Component Repository SLD (from 1.x to 2.0) Configuration Wizard: PI-AEX EHP Upgrade Configuration Wizard: PI / ESR Support Package Update

1.3 Accessing Documentation

Before, 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.
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.3 including enhancement package 1 SAP NetWeaver 7.3 SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Composition Environment 7.1 including enhancement package 1 SAP NetWeaver Composition Environment 7.2
Local Installation of the SAP NetWeaver Library

Application Help http://help.sap.com/nw73 Application Help http://help.sap.com/nwce71 Application Help http://help.sap.com/nwce711 Application Help
http://help.sap.com/nw731 http://help.sap.com/nwce72

Application Help

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

6/22

PUBLIC

2011-11-21

1 1.3

Introduction Accessing Documentation RECOMMENDATION

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

2011-11-21

PUBLIC

7/22

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. 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.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.2 Checking the Source Release of the SAP System

NOTE

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 Composition Environment 7.2 SAP NetWeaver Composition Environment 7.1 including enhancement package 1 SAP NetWeaver Composition Environment 7.1 Different SAP NetWeaver usage types have different minimum Support Package levels. If you update an SAP NetWeaver system containing various usage types, make sure that your source system is on any acceptable Support Package level for all usage types implemented in the system.

2011-11-21

PUBLIC

9/22

2 2.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.
CAUTION

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

To determine the source release and Support Package level of your SAP system, proceed as follows: 1. Go to the AS Java start page: http://<host name>:<port>/index.html 2. Choose System Information. 3. Log on to AS Java as user Administrator. The current release and Support Package level are displayed under Version in the Software Components table.
Only valid for: Adobe Document Services |

2.3 Providing the JCE Jurisdiction Policy Files for Adobe Document Services
To update usage type Adobe document Services, you must provide the JCE unlimited strength jurisdiction policy files. The version of the files which must be available in your system depends on the JVM version of the target release. During the update, the Software Update Manager checks if the JCE files are installed in your system and if their version is compatible with the JVM version. If the files are not installed or incompatible, the Software Update Manager prompts you to provide a path to a compatible version of the files. The required version is displayed on the screen.
End of: Adobe Document Services |

2.4 Updating SLD Content of the Source System

Before 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:

10/22

PUBLIC

2011-11-21

2 2.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. 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

1.

Determine the versions of the CIM data model and CR Content that are available in the SLD of your source release of the update. To find this information, open the SLD and choose Administration Details Data . For example, 1.5.32 is the version of the CIM data model and SAP_CR 3.10 the version of the CR Content.
NOTE

If no CR Content version is available, you must initially fill the SLD. When you install the system, this provides the initial content. For more information about configuring the SLD, see the SAP Library [page 6] for your source release at:
Only valid for: Source Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2 |

SAP Library <Language> Administrator's Guide Administration of SAP NetWeaver CE Configuring, Working with and Administering System Landscape Directory Administrating the SLD
End of: Source Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2 | Only valid for: Source Release = SAP NetWeaver 7.3 |

Function-Oriented View <Language> Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administrating the SLD
End of: Source Release = SAP NetWeaver 7.3 |

2.

3.

To download the required updates, go to SAP Service Marketplace (SMP) at: http://service.sap.com/patches Browse our Download Catalog On the next page, choose SAP Technology Components SAP CR CONTENT . Download the current CIM model. This is located under SAP CR CONTENT UP TO <yyyy> (<yyyy> is the current year) and has the file name cimsap....zip. Select the latest file.
CAUTION

4.

If the version of a CIM data model to be imported is lower than 1.4.31, proceed as described in SAP Note 907897. Download the necessary CR Content delta updates. 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

2 2.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. x to 2.0 From 2.x to 3.0 From 3.x to 4.0 From 4.x to 5.0 From 5.x to 5.y (latest version)

End of maintenance reached. For more information, see SAP Note 1393764. SMP entry point: SAP MASTER DATA FOR SLD 2.0 File name: CRDelta1418_0-10003379.ZIP SMP entry point: SAP CR CONTENT UP TO 2007 File name: CRDelta1511_0-10004549.ZIP SMP entry point: SAP CR CONTENT UP TO 2008 File name: CRDelta41514_0-10006428.ZIP SMP entry point: SAP CR CONTENT UP TO 2009 File name: CRDelta515*.ZIP

5.

6.

For example, if you are using the current CR Content 3.7, download the latest data model cimsap....zip and the following files: CRDelta1511_0-10004549.ZIP, CRDelta41514_0-10006428.ZIP, and the latest file CRDelta515*.ZIP. You have now downloaded the required archives. The system does not unpack the archives but imports them as a ZIP file. For some archives, you need to follow particular instructions that are described at the end of this section. Before the import, check whether you need to consider further details in your case. To import the content into the SLD, perform the following activities: To import the CIM model update file(s) cimsap....zip into the SLD, go to the SLD start page and choose Administration Import . Import the CR Content update file(s) CRDelta....zip. The update contains all the changes as of the initial status (aggregate of all updates). The program only imports the changes that are not already present in your Component Repository. It ignores all changes that you have already imported. When you repeat the import of a delta that has already been imported successfully, the import is not carried out, which is correct. You must not ignore any warning messages here, and still choose Cancel Import. The warnings are caused by an error when selecting the entry point on SAP Service Marketplace. Repeat steps 1 and 2. To check the version of the content that you have imported into the SLD, choose Administration Details Data .

12/22

PUBLIC

2011-11-21

3 3.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. 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;Process Integration (PI) | PI: Using a Wizard for Automated Processing of Follow-Up Activity [page 17]
End of: PI Adapter Engine;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.1 EP: Checking the KMC Installation

NOTE

This step is not required if you apply a Support Package Stack. Use the KM Content iView and the KM Component Monitor to find out whether you can start up the system without any errors. If you find errors, then check the deployment and the log files.
Procedure
Checking the KM Content iView

1. 2.

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

Checking the Component Monitor

1. 2.

Log on to the portal as a user with the super administrator role. Choose System Administration Support Knowledge Management

Component Monitor .

2011-11-21

PUBLIC

13/22

3 3.1

Follow-Up Activities After the Update EP: Checking the KMC Installation

3.

4.

For Filters, Repository Managers, Repository Services and Services, check whether all subentries have the status green. The colors beside the entries indicate the following: Green shows the object is functioning well. Red shows the object cannot be started or is configured incorrectly. Yellow indicates that one or more lower-level items are red. If an object has the status red, read the error message. Try to correct the error in the system configuration. For more information about the configuration, see the online documentation at http:// help.sap.com/nw731 Application Help FunctionOriented View <Language> SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management Administration Guide System Administration Monitoring, Logging, and Tracing Component Monitor .

Checking the Deployment

If the portal does not start up after the installation, or you notice errors in the Knowledge Management component monitor, then check the deployment. When you check the deployment, examine both the application and content files. 1. Switch to the directory that contains the deployment files for the Knowledge Management and Collaboration applications:
Only valid for: UNIX |

/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/ server0/apps/sap.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.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.com\irj \servlet_jsp\irj\root\WEB-INF\deployment\pcd

End of: Windows |

2.

Check whether any of the following files have the extension .err: com.sap.ib.bi.* com.sap.km.* com.sap.netweaver.* com.sap.workflow.* If any files have the ending .err this indicates that the deployment was executed, but an error occurred. In this case, find out the reason for the error in the corresponding log file. The log file has the same name as the .err file, but the extension is .log. Switch to the directory that contains the files for the deployment of KM and Collaboration content:

3.

14/22

PUBLIC

2011-11-21

3 3.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.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.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.com\irj \servlet_jsp\irj\root\WEB-INF\deployment\pcdContent

End of: Windows |

4.

Check whether any of the following files have the extension .err: com.sap.ib.bi.* com.sap.km.* com.sap.netweaver.* com.sap.workflow.* If any of the com.sap.km* files have the ending .err, check the corresponding .log file to find out what caused the error. Also check the AS Java log files mentioned below.

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, then check the available trace file. 1. 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.

Open the file defaultTrace.*.trc with the most recent date. If errors appear in the trace file, try to solve them and then restart the AS Java.
NOTE

You can also view the trace file using the Log Administrator.
End of: Enterprise Portal (EP) |

Viewer that is available in the SAP NetWeaver

2011-11-21

PUBLIC

15/22

3 3.2

Follow-Up Activities After the Update Performing Follow-Up Activities for the System Landscape Directory

3.2 Performing Follow-Up Activities for the System Landscape Directory

The follow-up activities that you have to perform for the System Landscape Directory (SLD) depend on the situation in your source release system, that is, whether the SLD was configured or not.
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 <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]. 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: Function-Oriented View <Language> Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administering the SLD In either situation, you also need to configure the following SLD components: SLD Data Supplier Proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View <Language> Application Server Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Connecting Systems to the SLD For AS ABAP systems: Connecting AS ABAP Systems to the SLD Setting Up the SLD Data Supplier for AS ABAP Based Systems For AS Java systems: Connecting AS Java Systems to the SLD Setting Up the SLD Data Supplier for AS Java Based Systems SLD Client Proceed as described in the SAP Library [page 6] for your target release at: Function-Oriented View <Language> Application Server Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Connecting Systems to the SLD Connecting AS Java Systems to the SLD Configuring the SLD Client

16/22

PUBLIC

2011-11-21

3 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.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. You can use a configuration wizard to automate the following follow-up activities after you have performed the update. To operate the wizard, perform the following steps: 1. To start SAP NetWeaver Administrator, go to http://<host>:<port>/nwa. 2. Log on with your AS Java administrator user. 3. Choose Configuration Scenarios Configuration Wizard. 4. From Configuration View, choose All Configuration Tasks (dropdown box). 5. Advanced Adapter Engine Extended only: Select PI Advanced Adapter Engine Extended (AEX) EHP Upgrade and choose Start. For more information about this task, see SAP Note 1562025. If you want to repeat the update process, choose Re-execute. 6. When prompted by the wizard, provide the required entries (users and passwords). 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.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.4 ESR: Using a Wizard for Automated Processing of FollowUp Activities

NOTE

This section only applies if you perform an SP Stack update. You can use a configuration wizard to automate the following follow-up activities after you have performed the update. To operate the wizard, perform the following steps:

2011-11-21

PUBLIC

17/22

3 3.5

Follow-Up Activities After the Update ESR: Performing Follow-Up Activities for the Enterprise Services Repository

1. 2. 3. 4. 5.

To start SAP NetWeaver Administrator, go to http://<host>:<port>/nwa. Log on with your AS Java administrator user. Choose Configuration Scenarios Configuration Wizard. From Configuration View, choose All Configuration Tasks (dropdown box).
Only valid for: Source Release = SAP NetWeaver 7.3 |

Select PI / ESR Support Package Update and choose Start. For more information about this task, see SAP Note 1444305.
End of: Source Release = SAP NetWeaver 7.3 |

6.

If you want to repeat the update process, choose Re-execute. When prompted by the wizard, provide the required entries (users and passwords). The follow-up steps are then processed automatically. The ESR content for the enhancement package (software component version SAP BASIS 7.31) is imported [page 18]

End of: Enterprise Services Repository | Only valid for: Enterprise Services Repository |

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, yo do not need to perform this follow-up step. It has been covered by the wizard. You have to update the SAP BASIS content by manually importing the ESR content, which you can find at: Windows:\usr\sap\<SAPSID>\SYS\global\xi\content UNIX:/usr/sap/<SAPSID>/SYS/global/xi/content IBM i:/usr/sap/<SID>/SYS/global/xi/content
Prerequisites

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

1.

Start the Enterprise Services Builder and call the Enterprise Services Repository: To do this, perform the following steps: 1. Log on to the SAP system on which your Enterprise Services Builder has been installed. 2. You start the Enterprise Services Builder or the Integration Builderby means of an HTML start page. Open this start page by calling it either from your user menu or with Transaction SXMB_IFR. 3. Choose Enterprise Services Repository.

18/22

PUBLIC

2011-11-21

3 3.5

Follow-Up Activities After the Update ESR: Performing Follow-Up Activities for the Enterprise Services Repository

2.

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. 4. 5.

The actual ESR content files have the extension .tpz. You must not unpack these files. The import directory is created the first time you call the Enterprise Services Builder. Choose Tools Import design objects . ESR content can be imported either from a server directory or from a directory of your local PC (Client). SAP recommends that you import ESR content from the server directory. Choose Server. You can only select files from the following import directory: 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 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. If an error occurs, this information is important for support. Take one of the following precautions to retain the overview of the imported ESR content: If the release and the Support Package are clear from the file name of the TPZ file, simply leave the files in the directory importedFiles (as described above). If a file with the same file name already exists in the directory importedFiles, the Enterprise Services Builder adds the date and time of the import to the file name of the imported export file. This enables you to check which file was imported last. After a successful import, you can keep the packed files, from whose naming convention you can derive the Support Package. Move them into the directory importedFiles, for example.
End of: Enterprise Services Repository |

2011-11-21

PUBLIC

19/22

Typographic Conventions

Example
<Example>

Description

Example Example Example

Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 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

20/22

PUBLIC

2011-11-21

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 2011 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, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle and Java are registered trademarks of Oracle. 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. 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. 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

2011-11-21

PUBLIC

21/22

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 2011 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.