WebSphere® Telecom Web Services Server includes the Access Gateway, the Service Policy Manager, a set of Service Platform components, and a number of Web service implementations. All of these can be installed across multiple servers in the network.
When planning to install Telecom Web Services Server, you must consider how you want to deploy the components in your network.
Decide which set of Web service implementations you want deployed in your network. The Service Platform components are deployed locally with the Web service implementations, and are distributed among each Service Platform application server node in the cluster.
The Service Policy Manager can be installed in the same cluster with the Service Platform components and the Web service implementations, or it can be installed in a separate cluster of its own. The Service Policy Manager console is normally deployed within the same cluster as its runtime component.
Regardless of the desired network configuration, the components should be installed into a clustered environment with a deployment manager and a managed cell. A common configuration has two clusters: an Access Gateway cluster and a Service Platform cluster. From the vantage point of WebSphere Application Server, the use of separate clusters means that each node is treated as a separate managed entity.
Each component requires WebSphere Application Server. The Access Gateway requires WebSphere ESB, which includes WebSphere Application Server.
For a complete list of software requirements, including supported application server and database versions, refer to the topic Hardware and software requirements.