WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Integrating the Web service implementations with other components

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.

Integrating with Service Platform components

The Service Platform components facilitate rapid development of the Web service implementations. You can deploy the Service Platform components and then disable any that are unused.
Note: For more information on how to disable service platform components, see the topic Disabling Service Platform components for Web services in the Administering section of the information center.

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.

Notes about the table:
  1. You should deploy the Traffic Shaping component Web service and the Network Resources component Web service whenever you plan to use the Web service implementations 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.
  2. You should deploy both the Notification Management component Web service and the PX Notification component Web service together with any Web service implementation that generates or handles notifications. (There is one exception: for WAP Push over SMPP, only PX Notification is required.)
Table 1. Interoperability between Web service implementations and Service Platform components
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

Integrating with system administration consoles

The following is required for integrating the system administration console.
  • The TWSS Administration Console is required if you plan to deploy any of the following:
    • Web service implementations based on SIP/IMS
    • The Parlay X Payment (PostPaid) Web service implementation
    • The Parlay X Address List Manager over XCAP Web service implementation
    • Web service implementations based on Direct Connect protocols
    • The Service Platform components

Use the TWSS Administration Console to manage and configure the Service Platform components and Web service implementations.

Use the Parlay Administration Console to configure the Parlay Connector. The Parlay Connector is needed only for the Parlay-based Web service implementations:
  • Parlay X Terminal Status over Parlay
  • Parlay X Terminal Location over Parlay
  • Parlay X SMS over Parlay
  • Parlay X Call Handling over Parlay
  • Parlay X Call Notification over Parlay
  • Parlay X Third Party Call over Parlay
Note: Both the TWSS and Parlay consoles are never installed on the node, instead they are installed on the dmgr machine. The administration consoles are distinct from, and should not be confused with, the Service Policy Manager console.

Integrating with a privacy Web service

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.

Performance

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.




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