Overview of the Profile Service API
14.3 Configuring the Rf Application
The Rf API is packaged as a Diameter application similar to the Sh application used for managing profile data. The Rf Diameter API can be configured and enabled by editing the Diameter configuration file located in DOMAIN_ ROOTconfigcustomdiameter.xml, or by using the Diameter console extension. Additionally, configuration of both the CDF realm and host can be specified using the cdf.realm and cdf.host initialization parameters to the Diameter Rf application. Example 14–3 shows a sample excerpt from diameter.xml that enables Rf with a CDF realm of oracle.com and host cdf.oracle.com: Example 14–3 Sample Rf Application Configuration diameter.xml application application-id3application-id accountingtrueaccounting class-namecom.bea.wcp.diameter.charging.RfApplicationclass-name param namecdf.realmname valueoracle.comvalue param param namecdf.hostname valuecdf.oracle.comvalue param application Because the RfApplication uses the Diameter base accounting messages, its Diameter application id is 3 and there is no vendor ID.14.4 Using the Offline Charging API
OWLCS provides an offline charging API to enable any deployed application to act as a CTF and issue offline charging events. This API supports both event-based and session-based charging events. The classes in package com.bea.wcp.diameter.accounting provide general support for Diameter accounting messages and sessions. Table 14–2 summarizes the classes. In addition, classes in package com.bea.wcp.diameter.charging support the Rf application specifically. Table 14–3 summarizes the classes. Table 14–2 Diameter Accounting Classes Class Description ACR An Accounting-Request message. ACA An Accounting-Answer message. ClientSession A Client-based accounting session. RecordType Accounting record type constants.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