Resource adaptor configuration properties apply to when the resource adaptor is acting as a server and for service-managed client sessions. The only configuration properties used in bound mode are the two properties that reference the profiles (BoundSessionConfigurationProfileTable and BoundSessionConfigurationProfileNames), as well as SmppResponseReceivedTimeout and SmppStateCheckingEnabled. See Profile Configuration for information about configuration of bound sessions.

Warning

We do not recommend using service-managed client or server sessions and bound sessions in a single entity. So do not set both SmppBindAddresses and BoundSessionConfigurationProfile…​, or open a session from the provider of an entity that has either of these set.

The resource adaptor will handle these cases but they are not supported for live production environments.
Table 1. Resource Adaptor Configuration Properties
Property Name Type Default Comment

SmppBindAddresses

String

Allows a different bind address (network address and port combination) to be specified for each node in a cluster. See note below.

SmppListenAddress

String

Local IP address to listen on (empty = listen on all addresses). SmppBindAddresses should be used in preference to this.

SmppListenPort

Integer

2775

Local TCP port to listen on. SmppBindAddresses should be used in preference to this.

SmppSessionInitTimeout

Long

30000

Timeout (in ms) for session init, an SMPP_TIMEOUT_SESSION_INIT event will be fired if session was not bound this amount of time after TCP connection opened

SmppEnquireLinkTimeout

Long

60000

Timeout (in ms) for link enquiry, an SMPP_TIMEOUT_ENQUIRE_LINK event will be fired periodically using this interval

SmppInactivityTimeout

Long

120000

Timeout (in ms) for session inactivity, an SMPP_TIMEOUT_INACTIVITY event will be fired if session is inactive for this amount of time

SmppResponseReceivedTimeout

Long

11000

Timeout (in ms) for receiving a response from the a peer, an SMPP_TIMEOUT_RESPONSE_RECEIVED will be fired if this amount of time passes

SmppResponseSentTimeout

Long

10000

Timeout (in ms) for a service to send a response to an incoming request, resource adaptor will send a GENERIC_NACK it this amount of time passes

SmppStateCheckingEnabled

Boolean

true

Determines whether stack checks for correct session state when sending/receiving messages.

BoundSessionConfigurationProfileTable

String

The profile table containing bound session configuration profiles.

BoundSessionConfigurationProfileNames

String

The names of the bound session configuration profiles.

Notes

SmppSessionInitTimeout, SmppEnquireLinkTimeout and SmppInactivityTimeout

These properties control timers in the resource adaptor and fire a SLEE event when the timeout elapses.

Important

The resource adaptor does not send any messages or perform any other action as a result of these timeouts elapsing, other than to fire an event so the service managing the session can take some action.

The exception to this is that if the inactivity timeout fires for a second time, the resource adaptor assumes the service has not closed the connection as it supposed to, and closes it itself.

SmppBindAddresses, SmppListenAddress and SmppListenPort

These properties are used to specify an address and port for a TCP listen socket.

Tip We recommend always using SmppBindAddresses. SmppListenAddress and SmppListenPort exist for compatibility with deployment scripts that used a previous version of the resource adaptor.

The SmppBindAddresses property allows a different bind address (network address and port combination) to be specified for each node in a cluster.

It is a string property with the format

{node}address:port,{node}address:port,...

This allows entities running on two nodes on the same host to use different ports, for example:

{101}0.0.0.0:2775,{102}0.0.0.0:2776

It also allows entities running on different hosts to specify an interface to listen on that is specific to each host, for example:

{101}192.168.1.100:2775,{102}192.168.1.101:2775
Important If SmppBindAddresses is empty, then SmppListenAddress and SmppListenPort will be used, and the same bind address will be used on all nodes. This configuration is not recommended.

Active Reconfiguration

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.

Tip When BoundSessionConfigurationProfileNames is updated, the resource adaptor will compare the new value with the previous one to determine which sessions need to be stopped, started or reconfigured.
Previous page Next page