Creating the UCD Structure

Use

You access and manage the UCD using the JNDI API. The provided infrastructure is an UCD tree root that contains a separate context (folder) for each user. The name of the context is based on the principal ID of the user. Each user context contains application data relevant for that user only.

When storing data in the UCD, we recommend creating below each user context a separate namespace context for each application type, for example Admin Studio or Navigation. The namespace context is a semantic object ( com.sap.portal.ns.namespaceservice.NamespaceManager ), which enables saving data within one unit. This facilitates the handling of transports, memory management, and enables loading all application-specific information at once. Below each namespace context, we recommend to use a separate context for each application for saving the application-specific data.

The following diagram illustrates the structure of the UCD:

Figure 1: UCD Structure

We recommend to logically divide the data stored in the UCD between different namespace contexts.

Note

The Transport mechanism supports the transport of UCD data. UCD transport is done at the level of the user context, not at the namespace context level.