Importing and Exporting PCD Objects (SAP Library

Importing and Exporting PCD Objects

Use

You can export and import roles and dependent objects. You need this function to export roles and their dependent objects (worksets, External Services, pages, iViews) from the Portal and to import the objects into the Portal.

When objects are imported or exported, a package file (PKG file) is automatically created that contains references to the objects and their dependencies. The PKG file contains information on the objects that are being exported or imported, and on their dependencies. For example, if a role is exported, the automatic objects that belong to it are also exported (worksets, pages, Java iViews, Net iViews and so on).

The lead object for the import and exports processes is normally the role. A role can have dependencies on the following objects:

On other roles
On worksets
On external services
On pages
On PAR files

Pages, for example, contain further dependencies on NET iViews and Java iViews.

The PKG file contains a list of lead objects (for example, roles) and an object list with the dependent objects and their parameters and values. XML files are also created for objects that are being imported or exported, for example, IVU files for iViews, PAG files for pages, and so on. All objects are stored in the same import or export directory.

You need these functions for the following scenarios:

You have two Portal installations and want to export and import objects from installation to another.
You are importing objects from the iViewStudio.

The following documentation consists of only scenario 1. Documentation on scenario 2 can be found in the iView studio.

Prerequisites

You configured the PCD appropriately. Read also Maintaining Parameters for the PCD.

Features

You can export and import roles and dependent objects from and to the PCD.

Export of Objects from the PCD:

You can export all PCD objects. The most significant object is the role. A role contains references to the objects that are assigned to it. All the dependent objects (worksets, external services) are therefore exported together with a role. The exported objects are automatically stored in the folder you defined on the Servlet Engine. Pages and Java and NET iViews that are assigned to them are exported with the role although they are not stored in the PCD.

You can also export objects (worksets, external services) individually, that is, independently of the role.

If you are exporting objects that are not stored in the PCD, see:

Exporting Java iViews

Exporting NET iViews

Exporting a Page

Import of Objects to the PCD

You can import all the objects that are dependent on a role into the Enterprise Portal. The most significant object is the role. A role contains references to the objects that are assigned to it. All the dependent objects are therefore imported together with a role, like for the export function. Pages and Java and NET iViews that are assigned to them are imported with the role although they are not stored in the PCD.

You can also import Java iViews individually, that is independently of the role.

If you are importing objects that are not stored in the PCD, see:

Importing Java iViews

Importing NET iViews

Importing Pages

Activities

Exporting PCD Objects

Start the export tool in the administrator role. Choose Portal Admin ® Export. You can also call the export tool directly from the Role Editor.

Choose the object that you want to export (for example, 'role') from the dropdown list.

Add the available objects to the export list by choosing Add. If you are exporting objects that have dependent objects (for example, roles) you must check Include dependent content objects and supplementary files.

Enter a name for the export directory on the machine on which the Java application is running. All the exported files are placed in this folder. You can also find a folder using the Browse function.

Choose Export.

The system automatically creates an export folder in the export area of the PCD. All the files to be exported are automatically placed in this folder. The system automatically creates a file with the extension .pkg containing all the objects in the export list. The file contains references to the dependent objects and the corresponding export files.

Note that the notification in the export screen is only valid for NET iViews (not for Java iViews).

Importing PCD Objects

Start the import tool in the administrator role. Choose Portal Admin ® Import. You can also call the import tool directly from the Role Editor.

Specify where the files to be imported are found.

Server: If you select this option you can find files on the server.

Client: If you select this option you can find files on your local client.

Choose Browsing and look for the name of the PKG file to be imported under File. This file contains the names of all the objects to be imported. The file also contains references to the dependent objects and the corresponding import files.

Decide what you want to happen to existing content when you import new content.

None: Content objects that already exist in the Enterprise Portal (for example, roles, worksets) are not overwritten.

Only iViews: Only iViews that already exist in the Enterprise Portal are overwritten. Other objects are not overwritten.

Overwrite all: All existing content objects are overwritten.

Choose Import.

The filed are imported and stored on the server in the corresponding import folder.