In general, any service-related data that is not server-specific is stored in the Sun Java System Access Manager directory. Server-specific data can be stored in properties files that are local to the specific server.
SMS provides a mechanism for services to define and manage their configuration data by using an Extensible Markup Language (XML) file that adheres to the SMS Document Type Definition (DTD). The definition of the configuration parameters through the XML file is called the schema for the service. Each Portal Server 7.1 service (Desktop, Rewriter, and Search) has its own XML and properties files for presenting and modifying service specific data.
Within the Sun Java System Access Manager framework, Portal Server 7.1 defines services related to the following functional areas:
The SunPortalRewriterService includes data associated with the Rewriter component, including the named rule sets that control the rewriting operation. The Rewriter API makes reference to the named rule sets that are stored in the directory.
In addition, the Portal Server 7.1 also uses other DTDs to define LDAP attribute values for the display profile and the Rewriter ruleset.
The Display Profile Document Type Definition (DTD) defines how the Display Profile is structured. The underlying data format for a display profile document is XML. It is intended to define the display configuration for the Desktop. It does that by defining provider, portlet, and channel objects, and their properties. The Rewriter ruleset DTD defines the structure of the ruleset. The Rewriter includes a default ruleset.
The file paths for the various XML, DTD, and schema files used to define the services of the Portal Server 7.1 (in the first column) and the service which uses the corresponding file (in the second column) are:
ldif file available in desktop directory.