To make full use of the Web service implementations that are available with TWSS, deploy them to use the corresponding Web service APIs. Each Web service implementation can coexist with other network components. Considerations for setting up this coexistence vary, depending on which Web service implementations you plan to deploy.
The following table summarizes which Service Platform components should be deployed with each Web service implementation. Install the Service Platform components locally on each application server in a cluster where the Web service implementations are deployed.
Web service | Admission Control | Traffic Shaping (see note 1) |
Network Resources (see note 1) |
Notification Management | PX Notification | AddressMasking | Fault and Alarm | Usage Record |
---|---|---|---|---|---|---|---|---|
Call Notification (SIP) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Optional |
Presence | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Recommended |
Terminal Status (SIP) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Recommended |
Call Handling (SIP/IMS) | Recommended | Optional | Recommended | Optional | Optional | Optional | Recommended | Recommended |
Third Party Call (SIP) | Optional | Optional | Optional | Optional | Optional | Optional | Recommended | Recommended |
Payment | Optional | Optional | Optional | Optional | Optional | Optional | Recommended | Required |
Address List | Recommended | Optional | Optional | Optional | Optional | Optional | Recommended | Recommended |
WAP Push | Optional | Recommended | Recommended | Optional | Required (see note 2) |
Optional | Required | Recommended |
SMS (SMPP) | Optional | Recommended | Recommended | Required (see note 2) |
Required (see note 2) |
Optional | Required | Recommended |
Terminal Location (MLP) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Optional |
MMS (MM7) | Optional | Optional | Optional | Required | Required | Optional | Required | Optional |
Terminal Status (Parlay) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Optional |
Terminal Location (Parlay) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Optional |
SMS (Parlay) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Required | Optional |
Call Handling (Parlay) | Recommended | Optional | Recommended | Optional | Optional | Optional | Recommended | Optional |
Call Notification (Parlay) | Optional | Optional | Optional | Required (see note 2) |
Required (see note 2) |
Optional | Recommended | Optional |
Third Party Call (Parlay) | Optional | Optional | Optional | Optional | Optional | Optional | Recommended | Recommended |
Use the TWSS Administration Console to manage and configure the Service Platform components and Web service implementations.
Each Web service implementation has the ability to integrate with a privacy service. When each Web service implementation is deployed, the privacy component endpoint is enabled in order to protect the Web service implementation and prevent unauthorized access. If a privacy service does not exist in the network, disable the privacy client. For more information, refer to the topic Configuring privacy integration.
The performance of any given Web service implementation is influenced by several factors including the performance of the network, the performance of the database, and on the way in which the front end to the network (which, in the case of TWSS, is the Access Gateway) is configured.