Messaging Web Services Interface Descriptions
9.5.4 Interface MessageNotificationManager, Operation: stopMessageNotification
This operation stops message notification at an endpoint for a user. If a user no longer has notification endpoints, all received messages for that user are no longer stored.9.5.4.1 Code Example
msgNotiMgrClient.stopMessageNotificationcorrelator;9.5.5 Interface ReceiveMessage, Operation: getReceivedMessages
This operation returns a set of incoming messages for a given user. Messages may only be received after notification has been enabled by invoking the startMessageNotifcation operation in the MessageNotificationManager interface.9.5.5.1 Code Example
MapString, Object params = new HashMapString, Object; params.putBindingProvider.ENDPOINT_ADDRESS_PROPERTY, http:webservicehost:7001receiveMessageEndpoint; ReceiveMessageClient recvMsgClient = new ReceiveMessageClientparams; ListMessageReference msgs = recvMsgClient.getReceivedMessagessip:receiverexample.com, MessagePriority.DEFAULT; for MessageReference ref : msgs { System.out.printlnto: +ref.getMessageServiceActivationNumber; System.out.printlnfrom: +ref.getSenderAddress; System.out.printlnsubject: +ref.getSubject; String id = ref.getMessageIdentifier; if id == null || id.isEmpty { System.out.printlnmessage: +ref.getMessage; } else { Table 9–8 Interface MessageNotificationManager, Operation: stopMessageNotification Argument Type Required Description correlator String yes The correlator associated with an invocation of the startMessageNotification operation. Table 9–9 Interface ReceiveMessage, Operation: getReceivedMessages Argument Type Required Description registrationIdentifier StringSipURI yes The recipient SIP address for incoming messages. priority MessagePriority no This value is ignored. Return Value Type Description references ListMessageReference A list of messages received for this user. Each item may either have a message identifier or message content, but is not guaranteed to have both an identifier and content. 9-6 Developers Guide System.out.printlnID: +id; } }9.5.6 Interface: ReceiveMessage, Operation: getMessage
This operation receives an incoming message as an attachment. Messages may only be received after notification has been enabled by invoking the startMessageNotifcation operation in the MessageNotificationManager interface.9.5.6.1 Code Example
ListMessageReference msgs = recvMsgClient.getReceivedMessagessip:receiverexample.com, MessagePriority.DEFAULT; for MessageReference ref : msgs { String id = ref.getMessageIdentifier; String msgContent; if id == null || id.isEmpty { msgContent = ref.getMessage; } else { System.out.printlnID: + id; recvMsgClient.getMessageid; DataHandler dh = recvMsgClient.getAttachment; ByteArrayOutputStream baos = new ByteArrayOutputStream; BufferedOutputStream out = new BufferedOutputStreambaos; dh.writeToout; out.flush; msgContent = baos.toString; } System.out.printlnmessage: + msgContent; } Table 9–10 Oracle WebLogic Communication ServicesInterface: ReceiveMessage, Operation: getMessage Argument Type Required Description messageIdentifier String yes A string identifying the incoming message. This string is obtained either from the notifyMessageReception callback, or the getReceivedMessages operation invocation. Return Value Type Description na na After invoking the getMessage operation, the message content is stored in an attachment of type DataHandler.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