System Administrator’s Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Managing and Configuring Native MM7 Communication Services

The following section describes configuration and maintenance attributes and operations for the communication service that exposes Native MM7 interfaces. The sections also provide a workflow for the configuration:

 

Native MM7

This section contains a description of the configuration attributes and operations available for Native MM7 network protocol plug-in instances.

To see a
Refer to
Detailed list of necessary for managing and configuring a plug-in instance
Properties for Native MM7
Configuration workflow
Configuration Workflow for Native MM7
List of operations and attributes related to management and provisioning
Provisioning Workflow for Native MM7
Reference of management attributes and operations
Reference: Attributes and Operations for Native MM7

Properties for Native MM7

Property
Description
Managed object in Administration Console
<domain name>Arrow symbolOCSGArrow symbol<server name>Arrow symbolCommunication ServicesArrow symbol<plug-in instance ID>
MBean
Domain=com.bea.wlcp.wlng
Name=wlng_nt
InstanceName is same as plug-in instance ID
Type=com.bea.wlcp.wlng.plugin.mm7.management.Mm7MBean
Network protocol plug-in service ID
Plugin_multimedia_messaging_mm7
Network protocol plug-in instance ID
The ID is given when the plug-in instance is created, see Managing and Configuring the Plug-in Manager.
Supported Address Scheme
tel
mailto
short
North interfaces
com.bea.wlcp.wlng.mm7.plugin.MmsPlugin
com.bea.wlcp.wlng.mm7.callback.MmsVaspCallback
Service type
Mm7
Exposes to the service communication layer a Java representation of:
3GPP TS 23.140 V5.3.0 (REL-5-MM7-1-2.xsd)
Interfaces with the network nodes using:
MM7 (REL-5-MM7-1-0 or REL-5-MM7-1-2 )
Deployment artifacts
Plugin_multimedia_messaging_mm7.jar
mm7_service.jar
1_0_mm7_vasp.war
1_2_mm7_vasp.war
packaged in wlng_nt_multimedia_messaging_mm7.ear
mm7.war
mm7_callback_client.jar,
packaged in wlng_at_multimedia_messaging_mm7.ear

Configuration Workflow for Native MM7

Below is an outline for configuring the plug-in using the Oracle Communications Services Gatekeeper Administration Console:

  1. Create one or more instances of the plug-in service: see Managing and Configuring the Plug-in Manager. Use the plug-in service ID as detailed in Properties for Native MM7.
  2. 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.
  3. Configure the behavior of the plug-in instance:
  4. Specify heartbeat behavior, see Configuring Heartbeats.
  5. Set up the routing rules to the plug-in instance: see Configuring the Plug-in Manager. Use the plug-in instance ID and address schemes detailed in Properties for Native MM7.
  6. Provide the administrator of the MM7 server with the URL to which the MM7 server should deliver mobile-originated messages and delivery reports:
    • For REL-5-MM7-1-0 the default URL is http://<IP Address of NT server>:<port>/1_0_mm7_vasp/mms_vasp
    • For REL-5-MM7-1-2 the default URL is http://<IP Address of NT server>:<port>/1_2_mm7_vasp/mms_vasp
  7. If desired, create and load a node SLA, see:

    8. Defining Global Node and Service Provider Group Node SLAs

    Managing Application SLAs

Continue with the provisioning of service provider accounts and application accounts.

Provisioning Workflow for Native MM7

  1. 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 Oracle Communications Services Gatekeeper for polling, use Operation: addVASIDMapping. Use the following operations to manage the offline registrations:
  2. To register online notifications, that is, to manage registrations for mobile originated messages on behalf of an application, use: Operation: removeVASIDMapping. Use the following operations to manage the online registrations:

Reference: Attributes and Operations for Native MM7

Managed object: Communication Services-><plug-in instance ID>

MBean: com.bea.wlcp.wlng.plugin.multimediamessaging.mm7.management.MessagingManagementMBean

Below is a list of attributes and operations for configuration and maintenance:

Attribute: Mm7RelayServerAddress

Scope: Cluster

Unit: n/a

Format: String

Specifies the address of the MM7 Relay Server. The address is an HTTP URL.

Attribute: HTTPBasicAuthentication

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies if HTTP basic authentication shall be used for authentication with the MM7 server.

Set to true if HTTP basic authentication shall be used, otherwise false.

If true, Attribute: HTTPBasicAuthenticationUsername and Attribute: HTTPBasicAuthenticationPassword must be specified.

Attribute: HTTPBasicAuthenticationUsername

Scope: Cluster

Unit: n/a

Format: String

The username to use for HTTP basic authentication towards the MM7 server. This is equivalent to the Application Instance ID.

Attribute: HTTPBasicAuthenticationPassword

Scope: Cluster

Unit: n/a

Format: String

The password to use for HTTP basic authentication towards the MM7 server.

Attribute: XSDVersion

Scope: Cluster

Unit: n/a

Format: String [REL-5-MM7-1-0, REL-5-MM7-1-2]

Specifies the xsd version that should be used for requests towards the MMSC.

Enter one of the following:

Operation: addVASIDMapping

Scope: Cluster

Adds the service provider VAS ID and the Oracle Communications Services Gatekeeper VAS ID mapping for use with the submit request.

Signature: 

addVASIDMapping(spVasID: String, wlngVasID: String)

Table 31-1 addVASIDMapping
addVASIDMapping
 
Parameter
Description
spVasID
The service provider’s VAS ID.
wlngVasID
The VAS ID that is to be sent to the MMSC.

Operation: addVASPIDMapping

Scope: Cluster

Adds the service provider VASP ID and the Oracle Communications Services Gatekeeper VASP ID mapping for use with the SubmitReq operation.

Signature: 

addVASPIDMapping(spVaspID: String, wlngVaspID: String)

Table 31-2 addVASPIDMapping
addVASPIDMapping
 
Parameter
Description
spVaspID
The service provider’s VASP ID.
wlngVaspID
The VASP ID that is to be sent to the MMSC.

Operation: enableReceiveMmsNotification

Scope: Cluster

Sets up delivery notification for network-triggered message delivery. Messages matching this configuration result in a callback to the application via the DeliverReq operation.

Signature: 

enableReceiveMmsNotification(Address: String, appInstGroupID: String, applicationURI: String)

Table 31-3 enableReceiveMmsNotification
enableReceiveMmsNotification
 
Parameter
Description
Address
The destination address of the MMS
appInstGroupID
The application instance group ID associated with this notification
applicationURI
The URI where the application can be reached

Operation: enableStatusReporting

Scope: Cluster

Sets up status report notification for delivery status and read-reply status for application-initiated messages.

Signature:

enableStatusReporting(appInstGroupID: String, applicationURI: String)

Table 31-4 enableStatusReporting
enableStatusReporting
 
Parameter
Description
appInstGroupID
The application instance group ID associated with this notification
applicationURI
The URI where the application can be reached

Operation: getReceiveMmsNotificationForAddress

Scope: Cluster

Checks to see if a notification is already set up for this exact address. If no entry is returned, the address can be used to set up a new notification

Signature:

getReceiveMmsNotificationForAddress(Address: String)

Table 31-5 getReceiveMmsNotificationForAddress
getReceiveMmsNotifcationForAddress
 
Parameter
Description
Address
The destination address of the MMS

Operation: getReceiveMmsNotificationMatches

Scope: Cluster

Searches existing configurations for Receive Mms notifications for an address pattern, using regular expressions. If there are no matching configurations, null is returned. This can be used to find out which application is registered for notifications for a specific address.

Note: The operation returns at most 1 match. If there are multiple entries, only the first will be returned, although in normal operation overlapping entries should not be possible.

Signature:

getReceiveMmsNotificationMatches(Address: String)

Table 31-6 getReceiveMmsNotificationMatches
getReceiveMmsNotifcationMatches
 
Parameter
Description
Address
The destination address pattern of the MMS: for example, 1234 or .@oracle.com

Operation: listAllVASIDMapping

Scope: Cluster

Lists all VAS ID mappings

Signature: 

listAllVASIDMapping()

Table 31-7 listAllVASIDMapping
listOfflineNotificationInfo
 
Parameter
Description
-
-

Operation: listAllVASPIDMapping

Scope: Cluster

Lists all VASP ID mappings

Signature: 

listAllVASPIDMapping()

Table 31-8 listALLVASPIDMapping
listALLVASPIDMapping
 
Parameter
Description
-
-

Operation: listReceiveMmsNotifications

Scope: Cluster

Lists all established delivery notifications

Signature: 

listReceiveMmsNotifications()

Table 31-9 listReceiveMmsNotifications
listReceiveMmsNotifications
 
Parameter
Description
-
-

Operation: listStatusReportingNotifications

Scope: Cluster

Lists all established status report notifications

Signature: 

listStatusReportingNotifications()

Table 31-10 listStatusReporting
listStatusReporting
 
Parameter
Description
-
-

Operation: listVASIDMapping

Scope: Cluster

Lists the VAS ID mapping that corresponds to the specified spVasID

Signature: 

listVASIDMapping(spVasID: String)

Table 31-11 listVASIDMapping
listVASIDMapping
 
Parameter
Description
spVasID
The service provider VAS ID to be matched.

Operation: listVASPIDMapping

Scope: Cluster

Lists the VASP ID mapping that corresponds to the specified spVaspID

Signature: 

listVASPIDMapping(spVaspID: String)

Table 31-12 listVASPIDMapping
listVASPIDMapping
 
Parameter
Description
spVaspID
The service provider VASP ID to be matched.

Operation: removeReceiveMmsNotification

Scope: Cluster

Removes an existing delivery notification

Signature: 

removeReceiveMmsNotification(address: String)

Table 31-13 removeReceiveMmsNotification
removeReceiveMmsNotification
 
Parameter
Description
address
The destination address of the MMS

Operation: removeStatusReporting

Scope: Cluster

Removes an existing status report notification.

Signature: 

removeStatusReporting(applicationInstanceGroupID: String)

Table 31-14 removeStatusReporting
removeStatusReporting
 
Parameter
Description
applicationInstanceGroupID
The application instance group ID associated with the notification.

Operation: removeVASIDMapping

Scope: Cluster

Removes an established VAS ID mapping.

Signature: 

removeVASIDMapping(spVasID: String)

Table 31-15 removeVASIDMapping
removeVASIDMapping
 
Parameter
Description
spVasID
The service provider VAS ID whose mapping is to be removed

Operation: removeVASPIDMapping

Scope: Cluster

Removes an established VASP ID mapping.

Signature: 

removeVASIPDMapping(spVasID: String)

Table 31-16 removeVASPIDMapping
removeVASPIDMapping
 
Parameter
Description
spVaspID
The service provider VASP ID whose mapping is to be removed


  Back to Top       Previous  Next