Importing EPA Archives 

Use

This scenario describes how to import EP 6.0 content objects that were combined in an EPA archive by the export process into another EP 6.0 portal.

You import EPA archives into the portal either from the server from the import directory, or from the client. To find out where the import directory for the server import resides, see Packages and Transport Objects.

Prerequisites

You manually copy the exported EPA archive that was created during the export from the export directory to the import directory.

Procedure

...

       1.      In the delivered administrator role choose System Administration ® Transport ® Import.

       2.      Specify whether you want to import from the client or the server.

       3.      If you import from the server, navigate to the directory or sub-directory containing the import package using the Browse function. The import directory is already pre-defined. If you are importing EP 6.0 content, you have to import a file in EPA format into the portal.

       4.      With the Select function, select a package to be imported. The package is automatically unpacked and the individual objects are listed in the object preview.

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

       6.      Specify whether or not the existing portal content may be overwritten by the import.

Note that objects in the „com.sap.portal“ or „com.sap.km“ namespace are not imported into the portal. Existing content objects are thus not overwritten, even if you specify that they should be overwritten. See also Protection of Objects During Import and Export.

       7.      Start the import with Import.

A new screen appears showing the status of the import. You can stop the import with Stop Import. The status of the import is updated automatically until the import has finished. Error messages appear with a link which you can click to go directly to an explanatory text.

Once the import has been completed, you can check if the objects were correctly imported using the log. If the import was successful, the object has status OK.

During the import, a log file is created as an XML file. This XML file can be monitored with the CCMS tool and displayed with the Log Viewer. For more information about portal monitoring see Monitoring Techniques and Logging.

Result

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 folder hierarchies are built analogously in the target system to the source system during import. All the attributes of a folder (name, description) are included in the export, and therefore exist in the target system after the import.

The following rules apply for storing the migrated objects in the target system:

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

Example: If the path for the content administrator role in the source and target systems is identical (Portal Content ® Portal Administrator ® Content Administrators), the role is created in folder Content Administrators in the target system analogously to the source system. If the role already exists in the target system, it is overwritten when the new version is imported.

·        If a folder hierarchy does not exist in the target system, you should always export the portal objects together with the entire folder hierarchy, and not export only the individual objects. The path with the folder names is built in the target system during the import. 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.