WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Administering WAP Push over SMPP

After you deploy WAP Push over SMPP, you can use the TWSS Administration Console to change the deployment configuration properties for the Web service and related Service Platform components.

You can receive additional information on specific properties from the online help in the TWSS Administration Console. Click More information about this page at the top right corner of the panel. Help for the module is then displayed in a separate browser window.

TWSS Administration Console settings

This Web service implementation adds the following configurable settings to the TWSS Administration Console:
  • Global: Policy values that are used for all services.
    • Common Service Settings: Use these settings to configure naming schemes for groups. The Access Gateway uses the IBM® XDMS component to resolve groups, and it can define and configure groups apart from the group scheme.
      • Country and code: The local country and code.
      • Address plan: The local address plan.
      • Enable Transaction Monitoring: Whether or not to enable transaction monitoring.
      • Supported Group Scheme: A comma-separated list of URI schemes that the service treats as a group URI. This setting must be coordinated with the Group List Manager component configuration. The default value is glmgroup.
      For more information about these settings, refer to the topic Group schema configuration.

  • Services: Default values used for WAP Push over SMPP:
    • WAPPush Service: The following properties can be configured:
      • Purge Enabled: True if cleanup activity occurs for expired delivery status data; false if cleanup activity does not occur. The default value is false.
      • Purge Interval: The time interval, in minutes, used to trigger the cleanup operation for expired delivery status data.
      • Purge Block: The number of records to retrieve each time there is a query to find expired data records. In effect, the cleanup operation is limited to cleaning up this much data during each purge interval. A value of 0 indicates that all records found should be removed. The default value is 1000.
      • Service Enabled: True if the WAP Push over SMPP service is enabled; false if it is not enabled. The default value is true.
      • Network Resource Name: The name of the network resource. Must match the name specified in Network Resources > Network Resources Configuration > resource_name for WAP Push over SMPP. The default value is WAP10_PUSH_SMPP.
  • Network Resources: Configure network elements to prepare them to receive messages from WAP Push over SMPP.
    • WAP Push Backends: You can configure the following properties for the WAP Push SMPP Network Mapper:
      • Backend Name: The name of the backend server that will communicate with the SMSC.
      • Hostname: The host name for the target SMSC.
      • Port: The port of the target SMSC. The default value is 2775.
      • System ID: The System ID that is used to bind to the SMSC.
      • Password: The password for the System ID.
      • System Type: The type of ESMC system that is requesting to bind as a transceiver with the SMSC. The input string must be 12 characters or less. The default value is a null string.
      • Max Message Size: The maximum allowable size, in bytes, of an individual message as stipulated by the SMSC. When an incoming message is larger than MaxMessageSize, it will be split into multiple messages (segmented) before sending. If the incoming message is larger than the maximum allowed by the protocol but smaller than MaxMessageSize, the message will be sent using the SMPP message_payload protocol. Valid values are 0 through 64000. The default value is 245. When the value is 0, no segmentation will occur.
      • Max Targets Size: The maximum number of targets allowed in a single message, according to the protocol specification or network support. Valid values are 0 through 255. The default value is 255. When the value is 0, no maximum number is enforced.
      • Confirmed Delivery: True if a delivery receipt will be requested on each message sent to the SMSC; false if not. The default value is false.
      • Data Coding: The type of encoding (DataCoding or DCS value) used for messages on the target SMSC. There are two possible values for WAP messages: 0x04 and 0x05.
        • To set DataCoding to 0x04, select 8_bit_binary_GSM_23_038_a.
        • To set DataCoding to 0x05, select any other value.
        The default value is ISO-8859-1.
      • Type of Bind to SMSC: The bind type to send to the SMSC. TWSS supports three types of bindings, which are defined in the SMPP Protocol Specification. The field is a drop-down list containing the following choices:
        • Transceiver(Trx): The connection can be used both for sending Mobile Terminated (MT) messages to the SMSC and for receiving Mobile Originated (MO) messages from the SMSC.
        • Transmitter(Tx): The backend will be used only for sending Mobile Terminated (MT) messages. Any Mobile Originated (MO) messages sent from the SMSC using the connection will be discarded.
        • Receiver(Rx): The backend will not be used for sending Mobile Terminated (MT) messages. It will be used only for receiving Mobile Originated (MO) message sent from the SMSC. Note that outbound enquire_link operation are not initiated on back ends that use Rx mode binding.
        The default value is Transceiver(Trx).
      • Type of Message: The way in which SMS messages are to be sent. The field is a drop-down list containing the following choices:
        • SynchronousSMS: Send SMS messages in synchronous fashion. If you choose this setting, you will need to configure connection pool settings at the following location in the Integrated Solutions Console: Resource adapters > SMPP v3.4 JCA Connector > J2C connection factories > PX21_SMS_SMPPJ2CCF > Connection pools.
        • StatusLessSMS: Send SMS messages in synchronous fashion and maintain the status of SMS in the database. If you choose this setting, you will also need to configure connection pool settings in the Integrated Solutions Console.
        • AsynchronousSMS: Send SMS messages in asynchronous fashion. This is the default value.
        Note: In TWSS version 7.0, the Enable Synchronous SMS and Enable StatusLess SMS controls were used to specify the message type. These controls are no longer used, and your existing setting is not preserved when you migrate to version 7.1. The default message type is SynchronousSMS, when you migrate from TWSS 7.0 to TWSS 7.1 After installing version 7.1, you will need to set Type of Message explicitly.
    • WAP Push Alias Details: The following properties can be configured:
      • Alias: Defines a mapping between the backend server details and a range of target addresses configured as SMS service policies. For every alias, at least one of the backends must be configured with a valid value.
      • Primary Backend Server: The primary backend server for handling messages.
      • Secondary Backend Server: The secondary backend server for handling messages, used when the primary server is not available.
    • WAP Push SMPP enquire_link and Bind Settings: The following properties can be configured:
      Note: Enquire_link requests sent to the servers in a cluster are handled by only one server in that cluster.
      • Enable enquire_link Service: True if the enquire_link service is enabled, false if disabled. The default value is false.
      • enquire_link Interval: The time interval, in minutes, to be used between enquire_link calls. Valid values are 1 through 60. The default value is 5.
      • service_type Usage: Specifies the value of the SMPP PDU field used for sending charging information to a backend server or used to identify the type of service in the delivery response. The field is a drop-down list containing the following choices:
        • For WAP and SMS over SMPP co-deployment: Use if you are deploying the WAP Push Web service together with SMS over SMPP on the same server.
        • For passing charging information: Use if you are not deploying the two services together. (This is the default value.)
      • service_type Value: Specifies the value of the service_type field to be set in the SMPP PDU that is sent to a backend server or included in the delivery response.
        • If service_type Usage is set to For WAP and SMS over SMPP co-deployment, then service_type Value is used for sending charging information to the SMSC. It is a text string of up to five characters. The default value is WAP. In addition to setting service_type Value, use the service.config.messaging.Billing policy to identify the desired charging code. The policy value is used to populate the billing_identification field in the PDU.
        • If service_type Usage is set to For passing charging information, then service_type Value is not required. Instead, define the service.custom.messaging.ServiceType policy. The policy value is used to populate the service_type field in the PDU. Note that in this case you cannot deploy the WAP Push Web service together with SMS over SMPP on the same server.
    • WAPPush SMPP ESMC Settings:

      The SMPP-based Web service implementations (SMS over SMPP and WAP Push over SMPP), use predefined values when communicating with the Short Message Service Center (SMSC). The values are used in each message sent to the SMSC. You can modify these values using the TWSS Administration Console.

      For more information, refer to the topic Configuring communication with the SMSC.

  • Common Components: Click the name of a Service Platform component–for example Fault Alarm Client or Usage Record Client–to configure it to work with this Web service implementation. If you leave the endpoint URI empty for a component, then the component is disabled.

Policies

Policy attributes are retrieved from the Service Policy Manager and are passed to the WAP Push over SMPP Web service in the SOAP headers. If the policies are not found in the SOAP header, the Web service uses the values that are defined in the TWSS Administration Console.

For information about default policy configuration, refer to the following topic: Default service policies for WAP Push over SMPP.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.