B Profile Service Provider Configuration Reference (profile.xml)

The following chapter provides a complete reference to the profile provider configuration file, profile.xml, in the following sections:

Section B.1, "Overview of profile.xml"
Section B.2, "Graphical Representation"
Section B.3, "Editing profile.xml"
Section B.4, "XML Schema"
Section B.5, "Example profile.xml File"
Section B.6, "XML Element Description"

B.1 Overview of profile.xml

The profile.xml file configures attributes of a profile service provider, such as:

The name of the provider
The class name of the provider implementation
Optional arguments passed to the provider
Mapping rules for using the provider.

profile.xml is stored in the DOMAIN_DIR/config/custom subdirectory where DOMAIN_DIR is the root directory of the OWLCS domain.

B.2 Graphical Representation

Figure B-1 shows the element hierarchy of the profile.xml file.

Figure B-1 Element Hierarchy of profile.xml

Description of "Figure B-1 Element Hierarchy of profile.xml"

B.3 Editing profile.xml

Oracle recommends using the Administration Console profile service extension to modify profile.xml indirectly, rather than editing the file by hand. Using the Administration Console ensures that the profile.xml document always contains valid XML. See Configuring Profile Providers Using the Administration Console in Developing Applications with OWLCS.

You may need to manually view or edit profile.xml to troubleshoot problem configurations, repair corrupted files, or to roll out custom profile provider configurations to a large number of machines when installing or upgrading OWLCS. When you manually edit profile.xml, you must reboot servers to apply your changes.

B.3.1 Steps for Editing profile.xml

If you need to modify profile.xml on a production system, follow these steps:

Use a text editor to open the DOMAIN_DIR/config/custom/profile.xml file, where DOMAIN_DIR is the root directory of the OWLCS domain.
Modify the profile.xml file as necessary. See "XML Element Description" for a full description of the XML elements.
Save your changes and exit the text editor.
Reboot or start servers to have your changes take effect:
Test the updated system to validate the configuration.

B.4 XML Schema

The full schema for the profile.xml file is bundled within the profile-service-descriptor-binding.jar library, installed in the WLSS_HOME/server/lib/wlss directory.

B.5 Example profile.xml File

See Developing Custom Profile Providers in Developing SIP Applications for sample listings of profile.xml configuration files.

B.6 XML Element Description

The following sections describe each XML element in profile.xml.

B.6.1 profile-service

The top level profile-service element contains the entire profile service configuration.

B.6.2 mapping

Specifies how requests for profile data are mapped to profile provider implementations.

B.6.2.1 map-by

Specifies the technique used for mapping documents to providers:

router uses a custom router class, specified by map-by-router, to determine the provider.
prefix uses the specified map-by-prefix entry to map documents to a provider.
provider-name uses the specified name element in the provider entry to map documents to a provider.

B.6.2.2 map-by-prefix

Specifies the prefix used to map documents to profile providers when mapping by prefix.

B.6.2.3 map-by-router

Specifies the router class (implementing com.bea.wcp.profile.ProfileRouter) used to map documents to profile providers with router-based mapping.

B.6.3 provider

Configures the profile provider implementation and startup options.

B.6.3.1 name

Specifies a name for the provider configuration. The name element is also used for mapping documents to the provider if you specify the provider-name mapping technique.

B.6.3.2 provider-class

Specifies the profile provider class (implementing com.bea.wcp.profile.ProfileServiceSpi).

B.6.3.3 param

Uses the name and value elements to specify optional parameters to the provider implementation.