WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Integrating with Parlay X Multimedia Messaging over MM7

The Parlay X Multimedia Messaging over MM7 Web service sends a message to an MMSC (Multimedia Message Service Center) using the MM7 interface for onward transmission. The Mm7Callback MDB (Message Driven Bean) performs this operation when called with the onMessage ( ) method, and when the message is sent from the MM7 Protocol Converter.

The Parlay X Multimedia Messaging over MM7 Web service defines interfaces for MessageNotification, SendMessage, ReceiveMessage, and MmsNotification Manager. The MMS message to be exchanged between client and server must be in the form of one or more attachments with appropriate content. This is defined by SOAP messages with attachments.

The Telecom Web Services Access Gateway receives the MMS SOAP messages with attachments. The Access Gateway then passes the SOAP message to the Telecom Web Services Server (TWSS) Web service implementation. The Access Gateway handles the MMS SOAP message attachments by either caching it in-memory or by using database tables. For more information on Access Gateway attachment handling, refer the following topics:

In the MMS MM7 Web service implementation, you can also configure the method in which attachments are handled in the SI layer by using the InMemoryAttachmentHandling setting in the TWSS Administration Console. If InMemoryAttachmentHandling is set to true, then the attachments are handled in-memory. If it is set to false, then the retrieval and attachment process will be implemented.

Call flows

The following are examples of call flows showing how the SendMessage interface is invoked using Synchronous and Asynchronous mode. In these examples, the call flow begins when the Access Gateway is configured to pass through the SOAP attachments to TWSS.
Note: If you set the InMemoryAttachmentHandling attribute of the Multimedia Messaging Web Service value to true, the MBean sendMessage call flow mode becomes Synchronous. If it is set to false, it is then treaded in Asynchronous mode. The default value for this attribute is false, and implies that the default call flow for the sendMessage operation will function in Asynchronous mode.

Asynchronous mode

  1. The Data Handler is configured to act before the invocation of SendMessage.
  2. The Data Handler retrieves the SOAP attachments, then stores the attachments in an Attachment content table and the metadata in a metadata table.
  3. The Attachments are removed from the original SOAP message.
  4. The SendMessage operation is invoked.
  5. The control flows to the Attachment Layer.
  6. The Attachment Layer retrieves the attachments and passes them to the connector.

Synchronous mode

  1. The Data Handler is configured to act before the invocation of SendMessage.
  2. The Data Handler, on identifying the mode of operation as Synchronous, performs no further processing and passes control to the next layer.
  3. The SendMessage operation is invoked.
  4. The control flows to the Attachment Layer.
  5. The Attachment Layer retrieves the attachments from the message context and passes them to the connector.

The following is an example call flow showing how the ReceiveMessage interface is invoked. In this example, the call flow begins when the Access Gateway is configured to pass through the SOAP attachments to TWSS.

  1. The Attachment layer receives the MMS message containing attachments.
  2. The Attachment layer retrieves the attachments and stores them in the attachment database.
  3. The Client is notified of reception when the MMS message invokes notifyMessageReception and passes.
  4. The Client invokes getMessage to retrieve the MMS message.
  5. The getMessage interface marks the expiration time to the current time in the Receive Data Table.
  6. The Data Handler is configured to act after the invocation of getMessage.
  7. The Data Handler retrieves the attachments and metadata from the attachment database, then adds them as SOAP attachments.
  8. The attachments and metadata are deleted from the attachment database.

Interfaces

Note: These interfaces are provided as Web services–except for MessageNotification, which is used as a client only.
SendMessage
sendMessage
Submits a request to send an MMS message.
getMessageDeliveryStatus
Retrieves the status of a specified previous send request.
ReceiveMessage
getReceivedMessages
Retrieves all of the MMS messages having a specified correlator.
getMessage
Retrieves the entire MMS message identified by messageRefIdentifier.
getMessageURIs
Not supported.
MessageNotificationManager
startMessageNotification
Initiates notifications to the application for a specified MMS service activation number and criterion.
stopMessageNotification
Ends notifications to the application for a specific startMessageNotification operation.
MessageNotification
notifyMessageReception
Notifies the application when an MMS message sent by the application has been received.
notifyMessageDeliveryReceipt
Notifies the application of the disposition of an MMS message sent by the application: the message was delivered successfully, the message could not be delivered before time expired, or notification is not supported for one or more of the recipient addresses.

Usage records

The interfaces for Parlay X Multimedia Messaging over MM7 generate usage records as follows.
Interface Usage records written
SendMessage: sendMessage 1 usage record per target without delivery confirmation
SendMessage: getMessageDeliveryStatus 1 usage record per operation
ReceiveMessage: getReceivedMessages 1 usage record per operation
ReceiveMessage: getMessage 1 usage record per operation
ReceiveMessage: getMessageURIs None
MessageNotificationManager: startMessageNotification 1 usage record per operation
MessageNotificationManager: stopMessageNotification 1 usage record per operation
MessageNotification: notifyMessageReception None
MessageNotification: notifyMessageDeliveryReceipt 1 usage record per target

For more details, refer to the topic Usage records for Parlay X Multimedia Messaging over MM7.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.