Object Storage in the Portal Catalog 

Use

Once the objects have been uploaded from the ABAP-based systems, they are stored in the Portal Catalog in a special directory.

Prerequisites

The objects were successfully uploaded and stored in the PCD.

Activities

In the Portal Catalog, choose Portal Content ® Migrated Content ® SAPComponentSystems. This folder also contains further sub-folders. The objects uploaded from the backend systems are stored there, sorted by the portal object type to which they were converted and the logical system from which they were uploaded.

The objects are grouped as follows:

·        iViews

All services (such as transactions) are converted to iViews and stored in folder iViews. Services are sorted by object type and stored in other sub-folders. For example, the transactions are stored in folder sap_tx.

·        Roles

If the uploaded roles were converted to portal roles, they are stored in folder Roles.

·        Worksets

If the uploaded roles were converted to worksets, they are stored in folder Worksets.

·        Pages

If the uploaded roles contain MiniApps, a page is automatically created for each uploaded role and the MiniApps are assigned to this page. These automatically generated pages are stored in folder Pages. For more information see Considerations when Uploading MiniApps.

The folder in which the objects are stored after the upload is defined in migration service com.sap.portal.pcd.rolemigration. The path portal_content/com.sap.portal.migrated/SAPComponentSystems/ is entered as default value.

You can change this value by entering a different path.

...

       1.      In the System Administration role, choose System Administration ® System Configuration ® Service Configuration.

       2.      Expand the hierarchy under Application, find service com.sap.portal.pcd.rolemigration and edit it.

       3.      Change the value of the property Root path for migration objects by entering a different path.

Do not copy or move individual objects to another folder in the Portal Catalog after the upload. This could result in inconsistencies in subsequent uploads. For example, a subsequent upload of the role/user assignment for a copied role will no longer work. If the role is in another folder, the uploaded information can no longer be referenced.

Dependencies of moved objects to the objects they contain (roles and the iViews they contain) can be lost when you copy or move.