How Are Portal Objects Named and Identified?

Use

Each object in the Portal Content Directory (PCD) has an ID that uniquely identifies it. For example, a role may have the following ID:

pcd:portal_content/com.sap.pct/administrator/content_admin/com.sap.portal.content_admin_role

The following table shows the components that can make up the content object ID:

ID Component

Example

Complete path of the object in the PCD, separated by slashes.

<pcd:portal_content/administrator/content_admin/>

Base name of the ID. This string cannot include periods (.).

<content_admin_role>

Namespace prefix. This ID component is optional and is located in before the base name of the ID. The namespace prefix can include periods.

<com.sap.portal>

Features

Note that content objects delivered by SAP may contain one of the following namespace prefixes:

  • com.sap*

  • com.sap.portals*

  • com.sap.km*

Activities

We recommend that you:

  • Use namespace prefixes for your own content objects as well as for the names of folders in the Portal Catalog.

  • Develop a global namespace concept in order to:

    • Clearly distinguish between objects by assigning namespaces that indicate the relevant organizational unit

    • Separately handle objects of different organizational units in content administration

The portal includes a naming conventions service that enables you to create rules for valid namespaces. For more information, see Defining Naming Conventions for Content Object Namespaces .

Example

  • A complete ID for a role without a namespace prefix:

    pcd:portal_content/administrator/content_admin/content_admin_role

  • A complete ID for a role with a namespace prefix:

    pcd:portal_content/com.sap.pct/administrator/content_admin/ com.sap.portal.content_admin_role