How are the Display Profile XML Documents Stored?

Display profile documents are stored in their entirety as a single attribute in the Sun Java System Sun Java System Access Manager software services layer. Potentially, the Portal Server software could store a display profile document for a user’s organization or sub-organization, each role the user belongs to, and the user. That is, for the different LDAP nodes (base DN, org DN, role DNs, and uid DN), you can store a display profile document. There is also a global display profile document.

The user’s display profile is a series of XML documents describing container management and properties for channels. (One display profile document is equivalent to one XML document.) The user’s display profile document set is made up from the non-empty documents stored at the user’s organization, various sub-organizations, any roles, and the user LDAP nodes. This display profile document set is “merged” at runtime to form a single configuration for the user’s Desktop.

To change display profile property values, the providers use the provider APIs (PAPI) to get and set the values. When the channel values are set to the display profile, the PAPI internal implementation uses the Sun Java System Access Manager SDK to set the display profile document in the Sun Java System Access Manager software Desktop service attribute.

Though possible, you should not edit the display profile using the Sun Java System Access Manager SDK.