Mirroring Portal Content

Prerequisites

You have administrator read/write permissions for the target folder. See Permission Levels .
You have at least administrator read permissions for all objects you intend to copy in the source folder.

Context

Content mirroring allows mass duplication of content in the Portal Catalog, while maintaining a direct delta link relationship between the original and copied objects. The following object types can be mirrored:

Folders
iViews
Page
Roles
Worksets
Systems

The primary use content mirroring is to copy entire business packages supplied by SAP after they have been imported into the portal. Since business packages supplied by SAP are defined in the reserved namespace of SAP, they cannot be modified. Customers can use this tool to duplicate any business package into their own namespace and then modify it as needed. The delta links between the objects in the original business package and those in the copied one ensure that when the original business package is updated by SAP and imported into the portal over the existing one, the changes made to the duplicated business package by the customer are not lost.

Customers can also use the content mirroring tool to transport their own portal content objects from one portal area to another (within the same portal). Original objects can be kept untouched in one central system, while all "mirrored" objects are connected to them through delta links. This way, updates can be made freely to the duplicated objects.

For more information, see What Is Content Mirroring?

Procedure

Navigate to System Administration Transport Content Mirroring. The content mirroring tool is displayed.

Define the following parameters:

Source Folder ID	The ID of the folder you want to mirror. For example: `pcd:portal_content/com.sap.pct` You can obtain the ID of a folder by choosing Copy ID in the context menu of the folder in the Portal Catalog and copying the information into this field. Note Do not enter the direct path to a portal object; the tool currently supports only folders.
Target Folder ID	The ID of the destination folder. This folder must exist already in the Portal Catalog.
Prefix for Objects in Target Folder	The namespace prefix to be applied to all new objects and folders in the target folder. Leave this box blank if you want to maintain the namespace of the original objects. Caution When choosing a prefix, note that the full object ID of newly created objects must not exceed the maximum limit of 100 characters. If any object exceeds the limit, the entire operation will fail. You are notified if this happens. For more information, see How Are Portal Objects Named and Identified?
Object Types to Mirror	For iViews, pages, and systems, you can also specify whether or not non-template objects are copied.

Choose Execute . You are notified when the process has finished.

If any errors occurred during the mirroring process, you receive an on-screen error report.

Note

If an object with the same ID already exists in the target folder, the existing object is not overwritten. A new object is created, and the ID of each new object is assigned an incremental numeric suffix to the existing ID. The object name is maintained in the new object.

For example: com.sap.pct.goofy → com.sap.pct.goofy_1 → com.sap.pct.goofy_2

Results

The result of using the content mirroring tool on folders in the Portal Catalog is the same as that which is achieved when using the Copy/Paste as Delta Link action available in the context menus of objects in the Portal Catalog. For more information, see Copying an Object or Folder (Copy / Paste) .