The following section describes configuration and maintenance attributes and operations for the communication service that exposes native SMPP interfaces. The sections also provide a workflow for the configuration:
This section contains a description of the configuration attributes and operations available for Native SMPP network protocol plug-in instances and the Native SMPP Facade.
Applications interact with the Native SMPP Facade and the Native SMPP Plug-in instances interact with an SMPP SMSC.
Unlike other Service Facades, the Native SMPP Service Facade is deployed in the Network Tier, so applications using the SMPP Native Communication Service need to be able to connect directly to the Network Tier. The network and any firewall need to be configured to allow connecting to the ports defined for the Native SMPP Service Facade.
There is no fail-over between Network Tier servers, so in order to support high-availability features, redundant SMSCs and redundant network cards are required.
To optimize system utilization the application and the SMSC should load balance the request between all Network Tier servers.
In certain configurations, network-triggered messages for an application can arrive at a Network Tier server that does not have a bind to that application,. In this case, it is possible to turn on a feature that allows that server to place the message in a JMS queue from which a Network Tier server that does have a bind to the application can pick the message up and forward it on to the application. This is done by setting Attribute: OfflineMO of the Native SMPP Service Facade (sms_smpp_connector). Messages stay alive for a configurable length of time. After the time has elapsed, the messages are removed and an EDR is written.
Note: | When running the Native SMPP communication service, you may receive the following exception from your NT servers. |
Note: | ERROR com.bea.wlcp.wlng.legacy.smpp.connector.SmppChannelProcessor - Could not find request for received response |
Note: | This exception can be ignored |
The ID is given when the plug-in instance is created, see Managing and Configuring the Plug-in Manager.
|
|
See deployment artifacts for Native SMPP Faces, in Properties for Native SMPP Facade
|
Below is an outline for configuring the Native SMPP Communication Service using the Oracle Communications Services Gatekeeper Administration Console:
Continue with the provisioning of service provider accounts and application accounts.
Continue with the provisioning of service provider accounts and application accounts.
Managed object: Communication Services->sms_smpp_connector
MBean: com.bea.wlcp.wlng.legacy.smpp.connector.management.LegacySmppMBean
Below is a list of attributes and operations for configuration and maintenance:
Specifies the default port applications use to connect to the Native SMPP Communication Service. Specific ports can be defined using Operation: addApplicationSpecificSettings.
Operation: updateAllListenerPorts must be invoked after this operation in order to update the listener port.
Specifies the server address applications use to connect to the Native SMPP Communication Service. The address can be expressed as an IP-address or as a host name. The address or host name must resolve to a local address.
Specifies whether or not the JMS-based routing functionality for network-triggered messages is turned on. If it is on, a message that comes in from the network to an NT server that does not have an active bind to the appropriate application can be placed in a JMS queue from which another server that does have an active bind can fetch it and send it to the application. The default is false.
The time that the message stays alive in the JMS queue is configurable. The default value is 3600000 milliseconds. To change this value, in the administrative console:
Controls what will happen on application binds/unbinds.
If true, the following applies:
As long as there are transmitting capable connections (TX, TRX) setup from applications, TX and TRX connections will be kept open to SMSCs.
As long as there are receiving capable connections (RX, TRX) setup from applications, RX and TRX connections will be kept open to SMSCs.
If false, the binding rules are more strict:
As long as there are TX connections setup from applications, TX connections will be kept open to SMSCs.
As long as there are RX connections setup from applications, RX connections will be kept open to SMSCs.
As long as there are TRX connections setup from applications, TRX connections will be kept open to SMSCs
Specifies the SMSC system ID. This is sent to an application upon a successful BIND request from the application.
Specifies the maximum time-out value for the time period between an application’s network connection setup request and BIND request.
If the time-out value is reached, the connection is terminated.
Specifies the maximum time-out period allowed between the Native SMPP service sends a request to an application and a response to the request is received.
If the time-out value is reached, the connection is terminated.
Specifies the maximum time-out period allowed for inactivity between an application’s request towards the Native SMPP service.
If the time-out value is reached, the connection is terminated.
Specifies the minimum time-out period between the Native SMPP service’s sending of ENQUIRE LINK requests to an application.
Specifies connection details for an application with a given application instance ID.
addApplicationSpecificSettings(applicationInstanceGroupId: String, acceptPort: int, maxSession: int, subsequentOperationsAllowed: Boolean, notificationEnabled: Boolean, addressRange: String)
|
|||
Specifies the address range to listen for network-triggered short messages. Only messages that are sent to this address range will be forwarded to the application.
|
Deletes connection details for an application with a given application instance ID. When removed, the application has no longer access to the Native SMPP Service.
Operation: updateAllListenerPorts must be invoked after this operation in order to update the listener port.
deleteApplicationSpecificSettings(applicationInstanceGroupId: String)
Displays a list of the application instance IDs that have connection details specified.
listApplicationSpecificSettings()
Displays a list of all ports that the Native SMPP Facade listens to and their status.
Port: <Port number> Status: <Status indicator>
Where <Status indicator> is one of the following:
listListenerPortStatus()
Displays a list of all ports that the Native SMPP Facade listens to. A list of all port in status: normal. See Operation: listListenerPortsStatus.
listOpenedPorts()
Stops the Native SMPP Facade from listening to a given port. The Native SMPP Facade must previously have opened the port for listening.
stopPort(port: int)
Creates all server sockets based on the current configuration for all registered applications, see Operation: listApplicationSpecificSettings.
This operation must be invoked after any of these operations have been performed:
It must also be invoked after any changes to Attribute: ServerPort
updateAllListenerPorts()
Managed object: Communication Services-><plug-in instance ID>
MBean: com.bea.wlcp.wlng.plugin.legacy.smpp.management.SmppPluginMBeanImpl
Below is a list of attributes and operations for configuration and maintenance:
Displays the state of the connection between the plug-in instance and the SMSC. True if the transmitter is successfully connected to the SMPP server; false if not.
Format: int enumeration [1, 3]
Specifies how the plug-in shall bind to the SMSC.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies how the plug-in shall respond to an SMSC if a network triggered short message cannot be delivered to the application that subscribed for notifications on incoming short messages.
It specifies the error code to used in the command_status field, see section 5.1.3 command_status in SMPP Protocol Specification v3.4.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the value of the timer used when sending Enquire Link requests.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the Enquire Link Timer value. The plug-in instance performs an Enquire Link operation to the SMSC to keep the connection alive. The time between enquiries is specified by this timer value.
Note: | To turn off the sending of Enquire Link, set the timer value to 0. |
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Format: String formatted as a regular expression.
Specifies the ESME address range. Specifies the address range of the SMSes to be sent to the plug-in instance by the SMSC. The address range is specified as a UNIX regular expression.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the ESME Numbering Plan Indicator (NPI).
Used for destination address and as a default for originating address. Also used for both destination address and originating address during bind operation. Use:
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the password used by the plug-in instance when connecting to the SMSC as an ESME.
Specifies the system ID used by the plug-in instance when connecting to the SMSC as an ESME.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the system type used by the plug-in instance when connecting to the SMSC as an ESME.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the ESME Type Of Number (TON). Used for destination address and as a default for originating address. Also used for both destination address and originating address during bind operation. Use:
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the local server address used when connecting to the SMPP SMSC. The address can be expressed as an IP-address or as a host name. The address or host name must resolve to a local address.
Enter default
to not specify an address implicitly, but to use the default address of the server.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the local port the plug-in uses when connecting to the SMPP SMSC.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the maximum number of connections to use towards the SMPP SMSC.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies whether to delete SMPP session information from storage after the receipt of query response with final message state.
The final message states contains all states except Enroute(=1)
Specifies whether to deleteSMPP session information from storage after receipt of the delivery report with final message state.
The final message states contains all states except Enroute(=1)
Specifies whether to cancel SMPP session information from storage after receipt of the cancel sm response.
Specifies the maximum number of times to try to reconnect to the SMPP SMSC.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the maximum number of times to try to connect to the SMPP SMSC before a reconnect is attempted.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the value of the timer used when sending requests to the SMSC.
The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Displays the version of the SMPP protocol being used.
Specifies the SMSC address as an IP-address or a host name. The setting will not be applied until the plug-in service is restarted or Operation: resetConnections is performed.
Specifies the port used by the SMSC. The setting will not be applied in until the plug-in service is restarted or Operation: resetConnections is performed.
Displays a list of the status of each connection with the SMSC.
The information returned is either:
Connections status: [deactivated]
Connections status: [activated]
bindType: [<Bind type>]
Configured connections: [<number of connections>]
bind links : [ <number of bound links> ]
listConnectionsStatus()
Resets the connections to the SMSC.
This operation needs to be invoked in order for the settings in the configuration attributes of the plug-in instance to take affect.
resetConnections()