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 default directory. During the upload you can define a different directory especially for roles uploaded into the system.

Activities

For object upload, you have the following options:

●      Upload to default folders

●      Upload to other folders

Upload to Default Folders

The folder in which the SAP NetWeaver Portal stores the objects after the upload is defined in the configuration of the role upload service under the property Root path for migration objects. For more information, see Configuring the Role Upload Service. The default path is portal_content/com.sap.portal.migrated/SAPComponentSystems.

You can find this folder in the Portal Catalog under Portal Content → Migrated Content → SAPComponentSystems. The portal creates further subfolders automatically during the upload. The objects uploaded from the back-end systems are automatically sorted in this folder according to the following criteria:

●      By the portal object type to which the portal converts them

●      By the logical system from you uploaded them

The objects are grouped as follows:

●      iViews

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

●      Roles

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

●      Worksets

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

●      Pages

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

Upload to Other Folders

To store the objects in another folder, a more flexible storage is available for roles. During an upload, you can specify a different target folder for the roles. For more information see Defining Settings for the Upload.

The disadvantage of this procedure is that the objects are not sorted automatically according to the logical system. You must do this manually by creating the appropriate folders in the Portal Catalog.

Do not manually copy or move roles to another folder in the Portal Catalog after the upload. This results in inconsistencies in subsequent uploads. If the role is in another folder (moved or copied), the uploaded information about the user-role assignment can no longer be assigned.

You can be more flexibly with other objects. For example, you can copy worksets and iViews to other folders as delta links.

If you do the same thing with roles, the portal can update the contents of the role from the delta link after another upload. However, the portal cannot copy the current user-role assignments from the back-end system. These assignments cannot be updated from a delta link.