About the SMPP Resource Adaptor

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.


Resource Adaptor Configuration

How to configure general settings for a resource adaptor entity

Profile Configuration

How to use profiles to configure bound sessions


Events fired by the resource adaptor when messages are received


The management beans which can be used to view the state of bound sessions

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

Next page