WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Planning to install WAP Push over SMPP

Here is a summary of the TWSS components, database tables, and other network elements that are required when you deploy WAP Push over SMPP.

This topic provides information about what is needed in the network in order to deploy the Web service implementation. The order in which the information is presented does not represent the order in which the elements should be installed.

Access Gateway

The Access Gateway must be installed in the network and is typically in a different cluster than the Web service implementation. All incoming calls are routed through message processing flows, which are deployed on the Access Gateway. A default WAP Push message processing flow is provided and should be deployed, unless you are using a custom message processing flow.

Service Policy Manager

The Service Policy Manager must be installed in the network, either in the Service Platform cluster or in its own cluster. The Service Policy Manager manages policies associated with the Web service implementation. When the database tables are created, they are populated with default policies. For information about default policies, see the Reference section of this information center.

TWSS Administration Console

The console must be installed on the deployment manager node for the cluster where the Web service is deployed.The console is used to configure the Web service implementations and the Service Platform components and to specify how they should be invoked. It is also used to administer MBeans that are included in the EAR files for the Web service implementations. It is managed through JMX.

The console plug-in acts as an extension to the WebSphere Integrated Solutions Console.

Service Platform components

The Service Platform components must be installed on the same cluster node as the Web service implementation. If the cluster is configured to synchronize, you can deploy the Service Platform components on the network deployment manager node. Some Service Platform components may be optional and, if so, are noted as optional in the following list. Interactions with other Service Platform components are also noted.
Table 1. Service Platform components for WAP Push over SMPP
Service Platform component Required? Remarks
Admission Control No When the Admission Control component Web service is available, the Web service implementation issues a VerifyAdmittableRequest to the Admission Control component to determine if the service request can be processed.
Traffic Shaping No Recommended in an integrated environment–that is, in a full setup where all of the TWSS components (Access Gateway, Service Policy Manager, and so forth) coexist.
Network Resources No Recommended in an integrated environment.
Notification Management No Not used.
PX Notification No Not used.
Address Masking No When deployed, the Address Masking component Web service works in conjunction with the Address Masking mediation primitive (part of the processing flow for the Access Gateway).
Fault and Alarm Yes Issues a RecordFaultRequest request to the Fault and Alarm component to generate a fault or an alarm when the following conditions occur:
  • A WAP Push over SMPP fault condition is detected.
  • An Admission Control component Web service fault occurs.
  • A Usage Record component Web service fault occurs.
Usage Record No Recommended. When the Usage Record component Web service is available, the Web service implementation uses it to record information about services rendered for status and billing purposes.

JMS Queues

When you deploy WAP Push over SMPP, multiple JMS queues are required for use by the Web service.

When setting up the service integration buses, the First Steps script will configure a permanent file store or datastore. If you choose to configure the file store manually, the file store should be stored on a mounted NFS drive. Each instance of the Web service in the cluster should use the same permanent store directory path.
Note: When you use the First Steps script to automate your configuration, the service integration buses are defined for you. However, you will need to provide a file system directory on the NFS shared drive.

Database

Database tables must be created to store WAP Push message data, configuration data, and policy data. You can use a single database to store this data, or you can create a unique database for each type of data. When you use the First Steps script, the required tables are created for a single database configuration.

If you choose to use multiple unique databases, or if you prefer to configure the database tables manually, you can find additional information in the topic Planning for the database.

DB2® and Oracle databases are supported.

Other interactions

The WAP Push over SMPP Web service implementation accepts requests for sending WAP Push messages and controls various checks that are done to ensure the requests are valid. The process then forwards the requests to the appropriate network elements for downstream processing. The following interactions are important:
  • HTTP proxy: An HTTP proxy needs to be configured. WebSphere® Application Server includes an HTTP proxy that can be used for this purpose.
  • SMSC: WAP Push over SMPP connects with the SMS message center and sends WAP Push messages to it.
  • SMPP JCA Adapter: SMPP connector passes every message to the SMSC as it arrives to the SMPP connector layer.



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