Oracle® Communications Service Broker Signaling Domain Configuration Guide Release 6.0 Part Number E23526-02 |
|
|
View PDF |
The following sections describe how to configure Service Broker SMPP SSUs using the Service Broker Administration Console and Java MBeans.
The SMPP SSU enables Service Broker to communicate with Short Message System Centers (SMSCs) through the Short Message Peer-to-Peer protocol.
When configuring the SMPP SSU, you set up the following:
SMPP network entities, which define the SMSCs to which the SMPP SSU routes submit_sm messages generated by IM-UIX-SMS. See "Configuring SMPP Network Entities" for more information.
SMSC connections, which define parameters of connections that the SMPP SSU establishes with SMSCs. See "Setting Up SMSC Connections" for more information.
Incoming routing rules, which define the IM-UIX-SMS instance to which the SMPP SSU routes a delivery_sm message received from an SMSC. See "Configuring Incoming Routing Rules" for more information.
SMPP network entities are SMSCs to which the SMPP SSU routes submit_sm messages generated by IM-UIX-SMS. You set up rules that define the following:
ID of the SMSCs to which the SMPP SSU routes the message
Alias to be set in the IM-UIX-SMS configuration to route the message to the SMSC with a specified ID. To provide continuous operation in situations when an SMSC fails, you can map the same alias to multiple SMSCs. If one of the specified SMSCs fails, the SMPP SSU routes the message to another SMSC mapped to the same alias.
Parameters of the heartbeat mechanism. Using this mechanism, the SMPP SSU regularly sends requests to an SMSC. If the SMPP SSU does not receive a response from the SMSC within the specified period of time, the SMPP SSU considers this SMSC inactive. The SMPP SSU does not send any further requests to this SMSC.
You can set up these parameters using the Administration Console and Java MBeans.
To configure SMPP network entities:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP SSU node.
In the SMPP SSU configuration pane, click the SSU SMPP tab and then the SMPP Network Entities subtab.
The SMPP Network Entity configuration pane appears. This pane displays a table. The table contains rules that define to which SMSC the short message is routed. Each row in the table represents a single rule.
To create a new rule, at the bottom of the SMPP Network Entities configuration pane, click New.
The New dialog box appears.
Fill in the fields described in Table 8-1.
Table 8-1 SMPP Network Entities Parameters
Field | Descriptions |
---|---|
Name |
Specifies the name of the rule. |
Alias |
Specifies the SIP URI of the IM to which the SMPP SSU routes an incoming session. The alias has the following format:
To provide continuous operation in situations when an SMSC fails, you can map the same alias to multiple SMSCs. If one of the specified SMSCs fails, the SMPP SSU routes the message to another SMSC mapped to the same alias. |
Heartbeat |
Specifies whether or not the SMPP SSU uses the heartbeat mechanism to regularly check whether the SMSC is active. Possible values:
Default value: ON |
SMSC Identifier |
Specifies the ID of the SMSC to which the SMPP SSU routes the submit_sm message if the value of the Default SMSC Alias parameter set in the IM-UIX-SMS configuration and the value of the Alias parameter match. |
Response Timeout |
Specifies the time interval, in seconds, during which the SMPP SSU waits for a response from the SMSC. If the response timeout expires, and the SMPP SSU still does not receive a response, the SMPP SSU considers the SMSC inactive. |
Active Interval |
Specifies the time interval, in seconds, for sending heartbeat requests from the SMPP SSU to the SMSC. This field is used if the previous heartbeat test showed that the SMSC is active. |
Inactive Interval |
Specifies the time interval, in seconds, for sending heartbeat requests from the SMPP SSU to the SMSC. This field is used if the previous heartbeat test showed that the SMSC is inactive. |
Click Apply.
Figure 8-1 shows the hierarchy of the configuration MBeans that you use to configure SMPP network entities. See "SMPP SSU Configuration MBeans Reference" for object names of these MBeans.
Each SMPP network entity is represented by SmppNetworkEntityMBean. You need to create a separate instance of SmppNetworkEntityMBean for each network entity.
To create an SMPP network entity:
Create an instance of SmppNetworkEntityMBean by invoking the following operation of SmppNetworkEntitiesMBean:
ObjectName createSmppNetworkEntity(string EntityName)
Set the following attributes of the newly created instance of SmppNetworkEntityMBean:
Name
Alias
Heartbeat
SmscId
ResponseTimeout
ActiveInterval
InactiveInterval
See Table 8-1 for more information about these attributes.
To route a submit_sm message to an SMSC, you set up connection between the SMPP SSU and SMSCs. Setting up a connection requires configuration of the following parameters:
General parameters, which define parameters which are common for all connections to SMSCs.
SMSC connection parameters, which define settings required for each connection. When setting up a connection, you map SMSC IDs specified in SMPP Network Entities, to physical addresses of SMSCs.
Credential store parameters, which define settings for secure storage of connection passwords.
You can set up these parameters using the Administration Console and Java MBeans.
General parameters define parameters which are common for all connections to SMSCs. You can configure general parameters using the Administration Console or Java MBeans.
To configure general parameters:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP node.
In the SMPP configuration pane, click the SMPP tab and then the General subtab.
Fill in the fields described in Table 8-2.
Click Apply.
Figure 8-2 shows the hierarchy of the configuration MBeans that you use to configure connections to SMSCs. See "SMPP SSU Configuration MBeans Reference" for the object names of these MBeans.
To configure general parameters:
Set the eventTimeoutMs attribute of eventTimeoutMsMBean as described in Table 8-2.
Set the protocolVersion attribute of protocolVersionMBean as described in Table 8-2.
See "SMPP SSU Configuration MBeans Reference" for more information about these MBeans.
Connection parameters define settings required for each connection.When setting up a connection, you map SMSC IDs specified in SMPP Network Entities, to physical addresses of SMSCs.
You can configure connection parameters using the Administration Console or Java MBeans.
To configure connection parameters:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP node.
In the SMPP configuration pane, click the SMPP tab and then the SMSC subtab.
Fill in the fields described in Table 8-3.
Table 8-3 SMSc Connections Parameters
Field | Descriptions |
---|---|
SMSC Identifier |
Specifies the ID of the SMSC for which you set up a connection. The value that you specify in this parameter must correspond to the SmscId parameter which you set in the SMPP Network Entities configuration. |
SMSC Address |
Specifies the host name or IP address of the SMSC to which the SMPP SSU routes a submit_sm message. |
SMSC Port |
Specifies the port of the SMSC to which the SMPP SSU routes a submit_sm message. |
ESME System ID |
Specifies the ID of the External Short Messaging Entity (ESME) that the SMPP SSU uses to bind to the SMSC. |
ESME Credential Key |
Specifies the key that the SMPP SSU uses to retrieve the ESME password from the credential store. See "Securing Connection Pools" for more information about specifying a password for a key. |
ESME System Type |
Specifies the type of the ESME system that the SMPP SSU uses to bind to the SMSC. |
ESME Address Ton |
Specifies the Type Of Number of the ESME address that the SMPP SSU uses to bind to the SMSC. |
ESME Address NPI |
Specifies the Numbering Plan Indicator of the ESME address that the SMPP SSU uses to bind to the SMSC. |
ESME Address Range |
Specifies the range of the ESME address that SMPP SSU uses to bind to the SMSC. Default value: .* |
Local Address |
Specifies the local address (hostname or IP) used to connect to the SMSC. To use any address, leave this parameter empty. |
ESME Port |
Specifies the local TCP port used to connect to the SMSC. Use -1 for any port. Default value: -1 |
Bind Type |
Specifies the type of connection to the SMSC. Possible values:
Default value: TRANSCEIVER |
Connection Pool Size |
Specifies the size of the connection pool. Default value: 1 |
Connection Timer (sec) |
Specifies the time, in seconds, that the SMPP SSU waits between connection attempts to the SMSC. Default value: 30 |
Request Timeout (ms) |
Specifies the period of time, in milliseconds, that the SMPP SSU waits to consider the request timed out. Default value: 10000 |
Enquire Link Timer (sec) |
Specifies the frequency, in seconds, with which the SMPP SSU sends a Enquire Link PDU on each SMSC connection. To disable sending a Enquire Link PDU, enter 0. Default value: 30 |
Window Size |
Specifies the maximum number of pending requests for each TCP connection. To disable limitation, enter 0. Default value: 0 |
Connection Acquire Timeout (ms) |
Specifies the timeout, in milliseconds, that the SMPP SSU waits for an available connection when no connections are currently available. This parameter is applicable only when the value of the windowSize parameter is greater than 0. Default value: 1000 |
Target |
Specifies the name of the managed server to which this configuration applies. If you leave this parameter empty, the configuration applies to all managed servers. |
Figure 8-3 shows the hierarchy of the configuration MBeans that you use to configure connections with SMSCs. See "SMPP SSU Configuration MBeans Reference" for the object names of these MBeans.
Each connection to an SMSC is represented by an instance of SmscMBean. You need to create a separate instance of SmscMBean for each connection. When you create an instance of SmscMBean, the set of child MBeans are created. Each child MBean represent a single parameter of the connection.
For example, SmscIdMBean has the SmscId attribute that represents the SMSC ID parameter. Similarly, smscAddressMBean has the smscAddress attribute that represents the SMSC Address parameter.
To configure connections to SMSCs:
Create an instance of SmscMBean by invoking the following operation of SmppConfigMBean:
void addSMSC()
Set the attributes of the child MBeans as described in Table 8-4.
Table 8-4 SmscMBean Child MBeans and Their Attributes
MBean | Attribute |
---|---|
SMSCIdMBean |
SMSCId |
bindTypeMBean |
bindType |
connectTimerSecMBean |
connectTimerSec |
connectionAcquireTimeoutMsMBean |
connectionAcquireTimeoutMs |
connectionPoolSizeMBean |
connectionPoolSize |
enquireLinkTimerSecMBean |
enquireLinkTimerSec |
esmeAddressNpiMBean |
esmeAddressNpi |
esmeAddressRangeMBean |
esmeAddressRange |
esmeAddressTonMBean |
esmeAddressTon |
esmeCredentialKeyMBean |
esmeCredentialKey |
esmeSystemIdMBean |
esmeSystemId |
esmeSystemTypeMBean |
esmeSystemType |
localAddressMBean |
localAddress |
localPortMBean |
localPort |
requestTimeoutMsMBean |
requestTimeoutMs |
smscAddressMBean |
smscAddress |
smscPortMBean |
smscPort |
targetMBean |
target |
windowSizeMBean |
windowSize |
See Table 8-3 for more information about these attributes.
When communicating with SMSCs, Service Broker acts as an External Short Messaging Entity (ESME). A connection between an ESME and SMSC can be established if the ESME provides a proper password. This password is stored in the credential store under a certain key. You specify this key by defining the ESME Credential Key parameter when setting up connection pools (for more information, see Table 8-3).
You must specify passwords for different keys using the Administration Console or Java MBeans.
To specify a password for a connection:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP node.
In the SMPP configuration pane, click the SMPP tab and then the Credential Store subtab.
In the Password area, fill in the fields described in Table 8-5:
Field | Descriptions |
---|---|
Key |
Specifies the key that the SMPP SSU uses to retrieve the ESME password from the credential store. You provide the key to be used for each connection pool. See "Setting Up Connection Pools" for more information. |
Password |
Specifies the password for the specified key. |
One-way |
Specifies how the SMPP SSU stores and retrieves the password. Do one of the following:
|
Click Set Password.
Figure 8-4 shows the hierarchy of the configuration MBeans that you use to specify the password for connections to SMSCs. See "SMPP SSU Configuration MBeans Reference" for the object names of these MBeans.
To set up the password:
Invoke the following operation of CredentialStoreMBean:
void setPassword (string Key, string Password, boolean One-way)
See Table 8-5 for more information about these parameters.
Invoke the following operation of CredentialStoreMBean:
boolean validatePassword()
The SMPP SSU stores connections and their passwords in the encrypted file known as Credential Store. You specify the name and location of the Credential Store file using the Java system property javax.net.ssl.keyStore. See "Configuring Security", Oracle Communications Server Broker System Administrator's Guide for more information.
You can set up the key store password using the Administration Console or Java MBeans.
To set up the key store password:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP node.
In the SMPP configuration pane, click the SMPP tab and then the Credential Store subtab.
In the KeyStore area, fill in the fields described in Table 8-6:
To set up the credential store password with Java MBeans, you use the same MBeans as described in "Setting Up a Connection Pool Password with Java MBeans".
To set up the key store password:
Invoke the following operation of CredentialStoreMBean:
void setKeystore (string Key, string KeystorePassword, string KeystoreURL)
See Table 8-6 for more information about these parameters.
You can check whether a key exists in the Credential store and delete keys. You can manage keys using the Administration Console or Java MBeans.
To check whether a key exists in the credential store:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP node.
In the SMPP SSU configuration pane, click the SMPP tab and then the Credential Store subtab.
In the General area, in the Key field, enter the key whose existence you want to check.
Click Contains Key?.
The message which informs you whether the key exists, appears.
To close the message, click OK.
To delete a specified key from the credential store:
In the Credential Store tab, in the General area, in the Key field, enter the key and then click Delete Key
To delete all keys from the credential store:
In the Credential Store tab, in the General area, click Delete All Keys.
To manage keys in the credential store with Java MBeans, you use the same MBeans as described in "Setting Up a Connection Pool Password with Java MBeans".
To check whether a key exists in the credential store:
Invoke the following operations of CredentialStoreMBean:
boolean containsKey (string Key)
To delete a specified key from the credential store:
Invoke the following operations of CredentialStoreMBean
void deleteKey (string Key)
To delete all keys from the credential store:
Invoke the following operations of CredentialStoreMBean:
void clear ()
Incoming routing rules define the IM-UIX-SMS instance to which the SMPP SSU routes a delivery_sm message received from the SMSC. For each rule, you define the following parameters:
Conditions:
Destination address
Service Type
Alias of the IM-UIX-SMS instance to which the SMPP SSU routes the message if both conditions are met
You can set up incoming routing rules using the Administration Console and Java MBeans.
To configure incoming routing rules:
In the navigation tree in the domain navigation pane, expand OCSB.
Expand the Signaling Tier node.
Select the SMPP SSU node.
The SMPP SSU configuration pane appears.
In the SMPP SSU configuration pane, click the SSU SMPP tab and then the Incoming Routing Rules subtab.
The Incoming Routing Rules configuration pane appears. This pane displays a table. The table contains rules that define to which instance of IM-UIX-SMS the delivery_sm message is routed. Each row in the table represents a single rule.
To create a new rule, at the bottom of the Incoming Routing Rules configuration pane, click New.
The New dialog box appears.
Fill in the fields described in Table 8-7.
Table 8-7 Incoming Routing Rules Parameters
Field | Descriptions |
---|---|
Name |
Specifies the name of the rule. |
SMPP Destination Address |
Specifies the destination address to be set in the delivery_sm message. |
Service Type |
Specifies the service type to be set in the delivery_sm message. |
Alias |
Specifies the alias of the IM-UIX-SMS instance. The SMPP SSU routes the delivery_sm message to this instance if the destination address and service type set in the delivery_sm message match the values set in SMPP Destination Address and Service Type parameters. |
Click Apply.
Figure 8-5 shows the hierarchy of the configuration MBeans that you use to configure incoming routing rules. See "SMPP SSU Configuration MBeans Reference" for object names of these MBeans.
Each incoming routing rule is represented by SmppIncomingRoutingRuleMBean.
You need to create a separate instance of SmppIncomingRoutingRuleMBean for each incoming routing rule.
To create an incoming routing rule:
Create an instance of SmppIncomingRoutingRuleMBean by invoking the following operation of SmppIncomingRoutingRulesMBean:
ObjectName createSmppIncomingRoutingRule(string RuleName)
Set the following attributes of the newly created instance of SmppIncomingRoutingRuleMBean:
Name
SmppDestinationAddress
ServiceType
Alias
See Table 8-7 for more information about these attributes.
The following sections provide reference information for the SMPP SSU configuration MBeans.
Note:
MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.SmppSsuMBean is the root MBean for configuring SMPP SSU.
com.convergin:Type=SmppSsu,Version=MBean_Version,Location=AdminServer,Name=ssusmpp.ssusmpp
Created automatically.
None
ObjectName getSmppIncomingRoutingRules()
Returns a reference to the instance of SmppIncomingRoutingRulesMBean.
ObjectName getSmppNetworkEntities()
Returns a reference to the instance of SmppNetworkEntitiesMBean.
SmppIncomingRoutingRulesMBean is the root MBean for configuring SMPP incoming routing rules. These rules define the instance of IM-UIX-SMS to which the SMPP SSU routes a delivery_sm message received from the SMSC. Using SmppIncomingRoutingRulesMBean, you need to create a separate instance of SmppIncomingRoutingRuleMBean for each rule.
com.convergin:Type=SmppIncomingRoutingRules,Version=MBean_Version,Location=AdminServer,Name=ssusmpp.smpp_inbound_routing
Created automatically.
None
ObjectName getSmppIncomingRoutingRule()
Returns a reference to the instance of SmppIncomingRoutingRuleMBean
ObjectName createSmppIncomingRoutingRule()
Creates an instance of SmppIncomingRoutingRuleMBean
void destroySmppIncomingRoutingRule()
Destroys an instance of SmppIncomingRoutingRuleMBean
ObjectName lookupSmppIncomingRoutingRule()
Searches for an instance of SmppIncomingRoutingRuleMBean
SmppIncomingRoutingRuleMBean enables you to set up a single incoming routing rule. This rule defines the instance of IM-UIX-SMS to which the SMPP SSU routes a delivery_sm message received from the SMSC. You need to create a separate instance of SmppIncomingRoutingRuleMBean for each rule.
com.convergin:Type=SmppIncomingRoutingRule,Version=MBean_Version,Location=AdminServer,Name=ssusmpp.incoming_routing_rule_name
SmppIncomingRoutingRules.createSmppIncomingRoutingRule()
Name
SmppDestAddress
ServiceType
Alias
For more information about these attributes, see Table 8-7.
None
SmppNetworkEntitiesMBean is the root MBean for defining SMSCs to which the SMMP SSU routes a submit_sm message generated by IM-UIX-SMS. Using SmppNetworkEntitiesMBean, you need to create a separate instance of SmppNetworkEntityMBean for each SMSC.
com.convergin:Type=SmppNetworkEntities,Version=MBean_Version,Location=AdminServer,Name=ssusmpp.smpp_outbound_routing
Created automatically.
None
ObjectName getSmppNetworkEntity()
Returns a reference to the instance of SmppNetworkEntityMBean
ObjectName createSmppNetworkEntity()
Creates an instance of SmppNetworkEntityMBean
void destroySmppNetworkEntity()
Destroys an instance of SmppNetworkEntityMBean
ObjectName lookupSmppNetworkEntity()
Searches for an instance of SmppNetworkEntityMBean
SmppNetworkEntityMBean enables you to define the SMSC to which the SMPP SSU routes a submit_sm message generated by IM-UIX-SMS. You need to create a separate instance of SmppNetworkEntityMBean for each SMSC.
com.convergin:Type=SmppNetworkEntity,Version=MBean_Version,Location=AdminServer,Name=ssusmpp.network_entity_name
SmppNetworkEntities.createSmppNetworkEntity()
Name
Alias
Heartbeat
SmscId
ResponseTimeout
ActiveInterval
InactiveInterval
For more information about these attributes, see Table 8-1.
None
SmppConfigMBean is the root MBean for configuration of connections that the SMPP SSU establishes with SMSCs. Using SmppConfigMBean, you need to create a separate instance of SmscMBean for each SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol
Created automatically.
None
void addSMSC()
Creates a new instance of SmscMBean
void removeSMSC()
Removes an instance of SmscMBean
SmscMBean enables you to configure a connection with a single SMSC. SmscMBean is created with a set of child MBeans. Each child MBean represents a configuration parameter of the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index]
SmppConfig.addSMSC()
None
void CloneIt()
Clones the current instance of SmscMBean.
SMSCIdMBean enables you to specify the ID of the SMSC to which the SMPP SSU routes a submit_sm message.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=2.0.0,name0=smppConfig,name1=SMSC[SMSC_index],name2=SMSCId
Created automatically.
SMSCId
See Table 8-3 for more information about this attribute.
None
bindTypeMBean enables you to specify the type of connection to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=bindType
Created automatically.
BindType
See Table 8-3 for more information about this attribute.
None
connectTimerSecMBean enables you to specify the time in seconds between each connection attempt to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=connectTimerSec
Created automatically.
ConnectTimerSec
See Table 8-3 for more information about this attribute.
None
connectionAcquireTimeoutMsMBean enables you to specify the timeout in milliseconds that the SMPP SSU waits for an available connection when no connections are currently available. This parameter is applicable only when the value of the windowSize parameter is greater than 0.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=connectionAcquireTimeoutMs
Created automatically.
ConnectionAcquireTimeoutMs
See Table 8-3 for more information about this attribute.
None
connectionPoolSizeMBean enables you to specify the number of connections used towards the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=connectionPoolSize
Created automatically.
ConnectionPoolSize
See Table 8-3 for more information about this attribute.
None
enquireLinkTimerSecMBean enables you to specify the frequency in seconds that Enquire Link PDU's are sent on each SMSC connection.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=enquireLinkTimerSec
Created automatically.
EnquireLinkTimerSec
See Table 8-3 for more information about this attribute.
None
esmeAddressNpiMBean enables you to specify the ESME address Numbering Plan Indicator used when binding to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeAddressNpi
Created automatically.
EsmeAddressNpi
See Table 8-3 for more information about this attribute.
None
esmeAddressRangeMBean enables you to specify the ESME address range used when binding to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeAddressRange
Created automatically.
EsmeAddressRange
See Table 8-3 for more information about this attribute.
None
esmeAddressTonMBean enables you to specify the ESME address Type Of Number used when binding to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeAddressTon
Created automatically.
EsmeAddressTon
See Table 8-3 for more information about this attribute.
None
esmeCredentialKeyMBean enables you to specify the key used to retrieve the ESME password from the credential store.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeCredentialKey
Created automatically.
EsmeCredentialKey
See Table 8-3 for more information about this attribute.
None
esmeSystemIdMBean enables you to specify the ESME system ID used when binding to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeSystemId
Created automatically.
EsmeSystemId
See Table 8-3 for more information about this attribute.
None
esmeSystemTypeMBean enables you to specify the ESME system type used when binding to the SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=esmeSystemType
Created automatically.
EsmeSystemType
See Table 8-3 for more information about this attribute.
None
localAddressMBean enables you to specify the local address (hostname or IP) used to connect to SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=localAddress
Created automatically.
LocalAddress
See Table 8-3 for more information about this attribute.
None
localPortMBean enables you to specify the local port used when connecting to SMSC.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=localPort
Created automatically.
LocalPort
See Table 8-3 for more information about this attribute.
None
requestTimeoutMsMBean enables you to specify the number of milliseconds until a request is considered to have timed out.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=requestTimeoutMs
Created automatically.
RequestTimeoutMs
See Table 8-3 for more information about this attribute.
None
smscAddressMBean enables you to specify the SMSC host name or IP address.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=smscAddress
Created automatically.
SmscAddress
See Table 8-3 for more information about this attribute.
None
smscPortMBean enables you to specify the SMSC port.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=smscPort
Created automatically.
SmscPort
See Table 8-3 for more information about this attribute.
None
targetMBean enables you to specify the target managed server this configuration applies to. If omitted, the configuration applies to all managed servers.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=target
Created automatically.
Target
See Table 8-3 for more information about this attribute.
None
windowSizeMBean enables you to specify the allowed window of unacknowledged SMPP requests sent to the SMSC per connection.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.protocol.smpp. esme,version=MBean_Version,name0=smppConfig,name1=SMSC[SMSC_index],name2=windowSize
Created automatically.
WindowSize
See Table 8-3 for more information about this attribute.
None
EventTimeoutMsMBean enables you to specify the number of milliseconds until inbound event is considered to have timed out.
Created automatically.
EventTimeoutMs
See Table 8-3 for more information about this attribute.
None
ProtocolVersionMBean enables you to specify the SMPP protocol version supported by SMPP Protocol Adapter.
Created automatically.
ProtocolVersion
See Table 8-3 for more information about this attribute.
None