Using a Constructed Document Key to Manage Profile Data
13.3 Configuring and Packaging Profile Providers
Providers must be deployed as a shared Java EE library, because all other deployed applications must be able to access the implementation. See Creating Shared Java EE Libraries and Optional Packages. For most profile providers, you can simply package the implementation classes in a JAR file. Then register the library with OWLCS using the instructions in See Deploying Shared Java EE Libraries and Dependent Applications. After installing the provider as a library, you must also identify the provider class as a provider in a profile.xml file. The name element uniquely identifies a provider configuration, and the class element identifies the Java class that implements the profile service API interfaces. One or more context parameters can also be defined for the provider, which are delivered to the implementation class in the register method. For example, context parameters might be used to identify backing stores to use for retrieving profile data. Example 13–1 shows a sample configuration for a provider that accesses data using XCAP. Example 13–1 Provider Mapping in profile.xml profile-service xmlns=http:www.bea.comnswlcpwlssprofile300 xmlns:sec=http:www.bea.comnsweblogic90security xmlns:xsi=http:www.w3.org2001XMLSchema=instance xmlns:wls=http;www.bea.comnsweblogic90securitywls mapping map-byprovider-namemap-by mapping provider namexcapname provider-classcom.mycompany.profile.XcapProfileProviderprovider-class param nameservername valueexample.comname param ... provider profile-service13.3.1 Mapping Profile Requests to Profile Providers
When an application makes a request using the Profile Service API, OWLCS must find a corresponding provider to process the request. By default, OWLCS maps the prefix of the requested URL to a provider name element defined in profile.xml. For example, with the basic configuration shown in Example 13–1 , OWLCS would map Profile Service API requests beginning with xcap: to the provider class com.mycompany.profile.XcapProfileProvider. Alternately, you can define a mapping entry in profile.xml that lists the prefixes corresponding to each named provider. Example 13–2 shows a mapping with two alternate prefixes. Example 13–2 Mapping a Provider to Multiple Prefixes ... mapping map-byprefixmap-by provider 13-4 Developers Guide provider-namexcapprovider-name doc-prefixsipdoc-prefix doc-prefixsubscribedoc-prefix provider by-prefix mapping ... If the explicit mapping capabilities of profile.xml are insufficient, you can create a custom mapping class that implements the com.bea.wcp.profile.ProfileRouter interface, and then identify that class in the map-by-router element. Example 13–3 shows an example configuration. Example 13–3 Using a Custom Mapping Class ... mapping map-by-router classcom.bea.wcp.profile.ExampleRouterclass map-by-router mapping ...13.4 Configuring Profile Providers Using the Administration Console
You can optionally use the Administration Console to create or modify a profile.xml file. To do so, you must enable the profile provider console extension in the config.xml file for your domain. Example 13–4 Enabling the Profile Service Resource in config.xml ... custom-resource nameProfileServicename targetAdminServertarget descriptor-file-namecustomprofile.xmldescriptor-file-name resource-classcom.bea.wcp.profile.descriptor.resource.ProfileServiceResourcere source-class descriptor-bean-classcom.bea.wcp.profile.descriptor.beans.ProfileServiceBeande scriptor-bean-class custom-resource domain The profile provider extension appears under the SipServer node in the left pane of the console, and enables you to configure new provider classes and mapping behavior.Parts
» Oracle Fusion Middleware Online Documentation Library
» Multiple Responses Differences from HTTP Servlets
» Receiving Responses Differences from HTTP Servlets
» Proxy Functions Differences from HTTP Servlets
» Servlet Request Servlet Response
» Application Management Role of a Servlet Container
» Sends a 200 response to the CANCEL request.
» Sends a 487 response to the INVITE request to be cancelled.
» Invokes a doCancel method on the SIP servlet. This allows the application to
» Utility Functions Role of a Servlet Container
» Overview of Converged Applications
» Assembling and Packaging a Converged Application
» Using the Converged Application Example
» Overview of Header Format APIs and Configuration Summary of Compact Headers
» Assigning Header Formats with WlssSipServletMessage
» Summary of API and Configuration Behavior
» Applications Must Not Create Threads
» Servlets Must Be Non-Blocking
» Store all Application Data in the Session
» All Session Data Must Be Serializable
» Use setAttribute to Modify Session Data in “No-Call” Scope
» Mark SIP Servlets as Distributable
» Session Expiration Best Practices
» Observe Best Practices for Java EE Applications
» Application Composition Model Oracle Fusion Middleware Online Documentation Library
» Using the Default Application Router
» Configuring a Custom Application Router
» Session Key-Based Request Targeting
» Overview of SIP Servlet Security
» Role Mapping Features Oracle Fusion Middleware Online Documentation Library
» Using Implicit Role Assignment
» Important Requirements Assigning Roles Using security-role-assignment
» weblogic.xml Deployment Descriptor Reference
» Specifying a Predefined Logging Level
» Customizing Log Records Enabling Message Logging
» Overview Specifying Content Types for Unencrypted Logging
» Example Message Log Configuration and Output
» Configuring Log File Rotation
» Introduction Installing the Web Services
» Configuring Web Services Presence Web Services Interface Descriptions
» Code Example Interface: PresenceConsumer, Operation: subscribePresence
» Code Example Interface: PresenceNotification, Operation: subscriptionEnded
» Code Example Interface PresenceSupplier, Operation: publish and Oracle Specific Unpublish
» Code Example Interface: PresenceSupplier, Operation: getOpenSubscriptions
» Code Example Interface: PresenceSupplier, Operation: updateSubscriptionAuthorization
» Code Example Interface: PresenceSupplier, Operation: getMyWatchers
» Code Example Interface: PresenceSupplier, Operation: getSubscribedAttributes
» Code Example Interface: PresenceSupplier, Operation: blockSubscription
» OWLCS Parlay X Presence Custom Error Codes
» Removing a Buddy from a Buddy List Manipulating your presence rules document
» Exceptions Buddy List Manager API
» Introduction Oracle Fusion Middleware Online Documentation Library
» Configuring Web Services Oracle Fusion Middleware Online Documentation Library
» Messaging Web Services Interface Descriptions
» Code Example Interface MessageNotificationManager, Operation: startMessageNotification
» Code Example Interface ReceiveMessage, Operation: getReceivedMessages
» Code Example Interface: ReceiveMessage, Operation: getMessage
» Configuration Workflow for Parlay X 2.1 Third Party CallSIP
» Attributes and Operations for Parlay X 2.1 Third Party Call
» Statement of Compliance Oracle Fusion Middleware Online Documentation Library
» Diameter Protocol Packages Oracle Fusion Middleware Online Documentation Library
» Implementing a Diameter Application
» Working with Diameter Sessions
» Sending Request Messages Working with Diameter Messages
» Creating New Attributes Working with AVPs
» Creating Converged Diameter and SIP Applications
» Overview of Profile Service API and Sh Interface Support
» Using a Constructed Document Key to Manage Profile Data
» Prerequisites for Listener Implementations Implementing ProfileListener
» Overview of the Profile Service API
» Implementing Profile Service API Methods
» Mapping Profile Requests to Profile Providers
» Configuring Profile Providers Using the Administration Console
» Overview of Rf Interface Support
» Understanding Offline Charging Events
» Specifying the Session Expiration
» Sending Asynchronous Events Implementing Session-Based Charging
» Accessing the Rf Application Implementing Event-Based Charging
» Using the Accounting Session State
» Configuring the Rf Application Overview of Ro Interface Support
» Handling Re-Auth-Request Messages Implementing Session-Based Charging
» Handling Failures Oracle Fusion Middleware Online Documentation Library
» Components Architecture User Messaging Service Overview
» Creating a J2EE Application Module
» Types of Addresses Addressing a Message
» Creating Address Objects Addressing a Message
» Creating a Recipient with a Failover Address
» API Reference for Class AddressFactory
» API Reference for Interface Address
» Deploying the Application Testing the Application
» Overview of Development Configuring the E-Mail Driver Deploying the Application
» Testing the Application Using the UMS EJB Client API to Build a Client Echo Application
» Creating a New Application Server Connection
» Overview of Parlay X Messaging Operations
» sendMessage Operation Send Message Interface
» getReceivedMessages Operation getMessage Operation getMessageURIs Operation
» Running the Pre-Built Sample Testing the Sample
» Creating a Channel Editing a Channel
Show more