Service Platform components provide common service implementation functions when deployed on the WebSphere® Application Server platform. Service Platform components are reusable and provide supporting functions for the TWSS service implementations as well as for custom Web service implementations.
The Service Platform components are installed by the Telecom Web Services Server (TWSS) base installer. The Web service implementations are installed separately, by the TWSS services installer. Both installers are intended for use only on the deployment manager node.
The Admission Control component Web service protects the platform on which the Service Platform components runs from overload conditions and can control the types of traffic which is admitted into the platform. The Admission Control component Web service offers two types of admission limit enforcement: locally tracked limits and cluster-wide tracked limits.
Each Web service implementation has the ability to integrate with a privacy system. 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.
The Traffic Shaping component Web service controls the flow of outbound traffic, from Service Platform components to the network resources. The Traffic Shaping component Web service implements a distributed token bucket algorithm that allows for specifying the maximum burst and maximum sustained average rate of traffic emitted from the cluster.
The Network Resources component Web service provides a way to define specifications for network resources (elements) with which the service platform will interact. Specifications that you design using the Network Resources component Web service are used to tailor the way in which the service platform behaves toward each resource.
The Notification Management component Web service, captures information about active notifications on the service platform for use by administrators who are monitoring the network. It provides functionality that administers registration, termination, and query notifications.
The Notification Management component Web service uses the DB2® or Oracle databases, which must be initialized by using the First Steps script.
This component is used by several Web service implementations as a support service for delivering outbound Web service notifications This component uses a JMS queue (which is optional), which requires a service integration bus called TWSSBus.
The Address Masking component Web service can be used to hide the real identity of a subscriber from any third-party application (TPA).
The Address Masking component Web service has been deployed as a Service Platform component, and the service policy values required for Address Masking needs to be configured in the Service Policy Manager. The version 7.1 Access Gateway and Service Policy Manager both are required prerequisites for using this feature.
The Fault and Alarm component Web service can be deployed to capture faults and alarms that occur for each deployed Web service implementation, for the Admission Control component Web service, and for the Usage Record component Web service. It can write fault and alarm information to the common event infrastructure (CEI) repository. If you plan to use the CEI repository to capture fault and alarm data, you must enable the CEI service and configure a data source for it.
The CEI service uses the database included with WebSphere Application Server, but it can be configured to use DB2®, Oracle or another database supported by WebSphere Application Server.