SMPP Resource Adaptor Guide

The Short Message Peer-to-Peer Protocol (SMPP) resource adaptor provides support for writing SMPP services that can act in either a External Short Message Entity (ESME) or Message Center (MC) role.

It supports persistent "bound" connections to a Message Centre, in which the resource adaptor is responsible for all session-related logic (connecting, binding, etc.), as well as generic SMPP services, in which the service is responsible for managing the session.

When using service-managed sessions, services can function as ESME or MC nodes, or both (an RE or Routing Entity). The type of node is determined automatically when the service sends or receives its first PDUs in a session. For example, if a service creates a session and then sends an OUTBIND request, then this is MC behaviour so the node is treated as an MC from that point on, until the end of the session. Similarly if a node creates a session, and then sends a BIND_TRANSMITTER request then this is ESME behaviour. The node type determines what PDUs are allowed to be sent or received in a session. For example, an MC cannot send SUBMIT_SM requests because this is not allowed by the SMPP protocol.

When using bound connections, services may only function as ESME nodes. They cannot open or close SMPP sessions, or send or receive session-related requests.

Other documentation for the SMPP Resource Adaptor can be found on the SMPP Resource Adaptor product page.

The resource adaptor supports active reconfiguration. You can update most configuration properties without having to deactivate the resource adaptor entity. The only properties that cannot be updated while the entity is active are SmppListenAddress, SmppListenPort and SmppBindAddresses.

Certain considerations must be taken into account when specifying these values.

ENQUIRE_LINK request messages are sent if no message has been received in the time specified by EnquireLinkInterval.

The ultimate determination of when to disconnect and reconnect is made according to the value of InactivityTimeout. If no messages have been received (including ENQUIRE_LINK or ENQUIRE_LINK_RESP) within this time, then the session is closed.

So it is important that the value of InactivityTimeout be sufficiently larger than EnquireLinkInterval for the desired number of ENQUIRE_LINK attempts to have occurred before the connection is closed.

For example, for the resource adaptor to close the connection after 6 seconds, and have a single ENQUIRE_LINK attempt before that, you might set:

To close the connection after 8 seconds, and have two ENQUIRE_LINK attempts before that, you might use:

This configuration property is specified as a comma-delimited list, and may contain status codes or their symbolic names as defined in the SMPP specification.

The default value is: ESME_RINVSRCADR, ESME_RBINDFAIL, ESME_RINVPASWD, ESME_RINVSYSID, ESME_RINVSRCTON, ESME_RINVSRCNPI, ESME_RINVSYSTYP.

A configuration reload can be triggered in the Rhino command line console:

When using the Rhino Element Manager, you can edit and save an unchanged resource adaptor entity configuration to achieve the same result.

There is one of these per entity. It is registered when the entity is created.

It has attributes for the number of bound sessions, the internal state and links to the bound session MBeans.

The internal state refers to whether the entity regards itself as active and functioning (which is independent of the SLEE container’s view of that state). The possible states are INACTIVE, INITIALISING, INITIALISATION_FAILED, ACTIVE and STOPPING.

There is one of these per bound session. It is registered when a bound session name is read from the BoundSessionConfigurationProfileNames configuration property, and deregistered if the bound session is removed from that list.

It has attributes for the bound session name, state, and a link to the entity.

It also has an operation to force an immediate reconnect.

The bound session states are: NEW, DISCONNECTED, CONNECTED, BOUND, RECONNECTING and UNBOUND.

The resource adaptor will not emit any bind request or response events since the session is already bound. The events SMPP_TIMEOUT_SESSION_INIT, SMPP_TIMEOUT_INACTIVITY, SMPP_TIMEOUT_ENQUIRE_LINK, SMPP_NEW_SESSION and SMPP_END_SESSION are not emitted by this resource adaptor since these timeouts are not relevant to SBBs in this mode.

The SMPP_TIMEOUT_RESPONSE_RECEIVED event will be emitted if a response to a request is not received in time (see SmppResponseReceivedTimeout in the configuration properties table below).

Class: com.opencloud.slee.resources.smpp.SmppSessionEvent

Class: com.opencloud.slee.resources.smpp.SmppRequestEvent

Class: com.opencloud.slee.resources.smpp.SmppResponseEvent

Class: com.opencloud.slee.resources.smpp.SmppErrorEvent