The following sections provide a complete reference to the profile provider configuration file, profile.xml
:
The profile.xml
file configures attributes of a profile service provider, such as:
profile.xml
is stored in the DOMAIN_DIR/config/custom
subdirectory where DOMAIN_DIR
is the root directory of the WebLogic SIP Server domain.
Figure 4-1 shows the element hierarchy of the profile.xml
file.
BEA 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 WebLogic SIP Server.
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 WebLogic SIP Server. When you manually edit profile.xml
, you must reboot servers to apply your changes.
If you need to modify profile.xml
on a production system, follow these steps:
/config/custom/profile.xml
file, where DOMAIN_DIR
is the root directory of the WebLogic SIP Server domain.profile.xml
file as necessary. See XML Element Description for a full description of the XML elements.
The full schema for the profile.xml
file is available at http://www.bea.com/ns/wlcp/wlss/profile/300. The schema file is also bundled within the profile-service-descriptor-binding.jar
library, installed in the WL_HOME/server/lib/wlss
directory.
See
Developing Custom Profile Providers in Developing Applications with WebLogic SIP Server for sample listings of profile.xml
configuration files.
The following sections describe each XML element in profile.xml
.
The top level profile-service
element contains the entire profile service configuration.
Specifies how requests for profile data are mapped to profile provider implementations.
Specifies the technique used for mapping documents to providers:
Specifies the prefix used to map documents to profile providers when mapping by prefix.
Specifies the router class (implementing com.bea.wcp.profile.ProfileRouter
) used to map documents to profile providers with router-based mapping.
Configures the profile provider implementation and startup options.
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.
Specifies the profile provider class (implementing com.bea.wcp.profile.ProfileServiceSpi
).
Uses the name
and value
elements to specify optional parameters to the provider implementation.