Managing and Configuring Multimedia Messaging Communication Services
The following section describes configuration and maintenance attributes and operations for the communication services that expose Parlay X 2.1 Multimedia Messaging Web Services interfaces. The sections also provide a workflow for the configuration:
This section contains a description of the configuration attributes and operations available for Parlay X 2.1 MultiMedia Messaging/MM7 network protocol plug-in instances.
To see a
Refer to
Detailed list of necessary for managing and configuring a plug-in instance
Exposes to the service communication layer a Java representation of:
Parlay X 3.0 Part 5: Multimedia Messaging
Interfaces with the network nodes using:
MM7
Deployment artifacts
Plugin_px21_multimedia_messaging_mm7.jar, px21_multimedia_messaging_service.jar and multimedia_messaging_mm7.war, packaged in wlng_nt_multimedia_messaging_px21.ear
px21_multimedia_messaging_callback.jar and px21_multimedia_messaging.war, packaged in wlng_at_multimedia_messaging_px21.ear
Configuration Workflow for Parlay X 2.1 MultiMedia Messaging/MM7
Below is an outline for configuring the plug-in using the Network Gatekeeper Management Console:
Using the Management Console or an MBean browser, select the MBean for the plug-in instance. The MBean display name is the same as the plug-in instance ID given when the plug-in instance was created.
Provide the administrator of the MM7 server with the URL to which the MM7 server should deliver mobile-originated messages and delivery reports. The default URL is http://<WLNG NT IP Address>:<port>/<server>:<port>/<context-root>/<Plug-in instance ID>
Continue with the provisioning of service provider accounts and application accounts.
Provisioning Workflow for Parlay X 2.1 MultiMedia Messaging/MM7
To register offline notifications, that is, to specify that mobile originated messages should not result in notifications to an application, but instead be stored in Network Gatekeeper for polling, use Operation: enableReceiveMms. Use the following operations to manage the offline registrations:
To register online notifications, that is, to manage registrations for mobile originated messages on behalf of an application, use: Operation: startMessageNotification. Use the following operations to manage the online registrations:
The username to use for HTTP basic authentication towards the MM7 server.
Attribute: HTTPBasicAuthenticationPassword
Scope: Cluster
Unit: n/a
Format: String
The password to use for HTTP basic authentication towards the MM7 server.
Attribute: DefaultPriority
Scope: Cluster
Unit: n/a
Format: String
Specifies the default priority for sent MMSes. Enter one the following:
normal
high
low
Attribute: MM7Version
Scope: Cluster
Unit: n/a
Format: String
Specifies the version of the MM7 protocol to be used. Applicable versions are:
5.3.0
Attribute: Mm7relayserverAddress
Scope: Cluster
Unit: n/a
Format: String
Specifies the address to the MM7 Relay Server. The address is an HTTP URL.
Attribute: VaspId
Scope: Cluster
Unit: n/a
Format: String
Specifies the VASP (Value Added Service Provider) ID to be used for the plug-in instance when connecting to the MMSC.
Attribute: VasId
Scope: Cluster
Unit: n/a
Format: String
Specifies the VAS (Value Added Service) ID to be used for the plug-in instance when connecting to the MMSC.
Attribute: RequestDeliveryReportFlag
Scope: Cluster
Unit: n/a
Format: Integer
Specifies how the plug-in instance requests and handles delivery reports for sent messages. Enter one of the following:
0: Delivery notifications are not processed, which means that no polling functionality is available to the applications using the communication service.
1: Delivery notifications are processed if the application provided a receiptRequest in the SendMessage requests or the application provided a tunnelled parameter with ID com.bea.wlcp.wlng.plugin.multimediamessaging.RequestDeliveryReportFlag with the value true in the SOAP header of the SendMessage request.
2: Delivery notifications are always processed.
Attribute: XSDVersion
Scope: Server
Unit: n/a
Format: String [REL-5-MM7-1-0, REL-5-MM7-1-2]
The MM7 xsd version that should be used for requests towards the MMSC.
Enter one of the following:
REL-5-MM7-1-0 to use an altered version of the REL-5-MM7-1-0.xsd. The altered version allows use of delivery notifications when the MMC-S requires this version of the xsd. This is a requirement when connecting to, among others, Comverse MMSCs.
REL-5-MM7-1-2, to use REL-5-MM7-1-2.xsd.
Operation: enableReceiveMms
Scope: Cluster
Adds an offline notification for applications that will poll for mobile originated messages. Mobile originated messages matching this notification will not result in a callback to an application. Instead the application has to use the correlator returned by this method and poll for new messages.
Returns the correlator uniquely identifying the new notification.
Creates an online notification on behalf of an application. Produces the same results as if an application registered for notifications using the method startMessageNotification in Parlay X 2.1 Multimedia Messaging interface MessageNotificationManager.
This operation can be used, for example, if the application is not allowed to register for notifications by restrictions defined in its SLA. Returns a correlator that uniquely identifies the notification.
