Show TOC

Importing and Deploying EPA ArchivesLocate this document in the navigation structure

Prerequisites

The exported EPA archive that was created during the export is manually copied from the export directory to the import directory.

Context

You import EPA archives into the portal either from the import directory on the portal server or from the client.

Procedure

  1. Navigate to Start of the navigation path System Administration Next navigation step System Administration Next navigation step Transport End of the navigation path and, from the Detailed Navigation panel, choose Import .
  2. Specify whether you want to import from the client or the server.

    If you import from the server, browse to the directory or subdirectory containing the import package. (Choose Upload to navigate to subfolders.)

  3. Choose Select to view the contents of the package.

    You can still change the location from which to import, client or server, and browse to the package before importing.

    If you import from the client, select your EPA file on the client using Browse, and upload it to the server. The upload folder is automatically created in the import directory with the corresponding user ID. The individual objects are listed in the object preview.

  4. Specify whether or not the existing portal content may be overwritten by the import.
  5. Choose Import .

    A new screen appears showing the status of the import. You can stop the import by choosing Cancel . You can then choose Return to the preview page .

    When the import is complete, you can check the log that appears to see if the objects were correctly imported.

Results

The imported objects are created in the same Portal Catalog folder in the target system as in the source system. Since you can export entire folder hierarchies, the hierarchies are built on the target system with the same structure as on the source system. All the attributes of a folder are included in the export.

Note

After you import an EPA archive that contains URL aliases, you must restart the com.sap.portal.navigation.AliasService service in SAP NetWeaver Administrator in order to see the URL aliases in the URL Alias Manager and use them in the Master Rule Collection . For more information, see Starting and Stopping Portal Services .

Rules Applying to Imports

  • If the folder hierarchies in the Portal Catalog are completely identical in the source and target systems, the object is created or, if it already exists, it is overwritten in the target system.

  • If a folder hierarchy does not exist in the target system, it is recommended to export the portal objects together with the entire folder hierarchy, and not export only the individual objects. If you do not include the entire folder hierarchy in the export, the hierarchy is built during the import, but only object IDs appear instead of the folder names. This is because the folder attributes are not exported and imported.

  • If you only export part of the folder hierarchy, but not the complete hierarchy, and import this part into the target system, this part is created together with the folder name. The missing hierarchy levels are built in the target system, but only the IDs appear instead of the folder name.