Creating New Attributes Working with AVPs
12.5 Using a Constructed Document Key to Manage Profile Data
OWLCS provides a helper class, com.bea.wcp.profile.ProfileService, to help you easily retrieve a profile data document. The getDocument method takes a constructed document key, and returns a read-only org.w3c.dom.Document object. To modify the document, you make and edit a copy, then send the modified document and key as arguments to the putDocument method. OWLCS caches the documents returned from the profile service for the duration of the service method invocation for example, when a doRequest method is invoked. If the service method requests the same profile document multiple times, the subsequent requests are served from the cache rather than by re-querying the HSS. Example 12–1 shows a sample SIP Servlet that obtains and modifies profile data. Example 12–1 Sample Servlet Using ProfileService to Retrieve and Write User Profile Data package demo; import com.bea.wcp.profile.; import javax.servlet.sip.SipServletRequest; import javax.servlet.sip.SipServlet; import org.w3c.dom.Document; import java.io.IOException; public class MyServlet extends SipServlet { private ProfileService psvc; public void init { psvc = ProfileService getServletContext.getAttributeProfileService.PROFILE_SERVICE; } protected void doInviteSipServletRequest req throws IOException { String docSel = sh: + req.getTo + IMSUserState; Obtain and change a profile document. Document doc = psvc.getDocumentdocSel; Document is read only. Document docCopy = Document doc.cloneNodetrue; Modify the copy using DOM. psvc.putDocumentdocSel, docCopy; Apply the changes. } } UserState sh:urireference_ typeCS-Domain | PS-Domain sh:sip:useroracle.comUserStatePS-Domain Charging information sh:urireference_type sh:sip:useroracle.comCharging information MSISDN sh:urireference_type sh:sip:useroracle.comMSISDN Note: If Diameter Sh client node services are not available on the OWLCS instance when getDocument the profile service throws a No registered provider for protocol exception. Table 12–2 Cont. Summary of Document Selector Elements for Sh Data Reference Requests Data Reference Type Required Document Selector Elements Example Document SelectorParts
» 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