WebSphere® Telecom Web Services
Server installs and runs as an application on WebSphere Application Server.
It can be deployed on various hardware configurations.
Before starting the installation process, review
the planning information to develop a deployment strategy that will
meet your network needs.
Note: If you are running WebSphere Application Server version 6.1.0.29,
the TWSS Access Gateway can
coexist in the same cluster with the Service Platform components.
However, when the Service Platform components are
deployed in a cluster running WebSphere Application Server version 7.0.0.7,
the Access Gateway must
be deployed in a separate cluster.
WebSphere Application Server supports
numerous deployment topologies. It is beyond the scope of this documentation
to provide detailed steps for each topology. Therefore deployment
information has been grouped into a number of broad categories. Throughout
the documentation the categories are used to provide a reference point. Each component has a unique deployment strategy.
Prior to deployment, review all of the planning and installation information.
Here is a list of the most commonly used topologies in a
WebSphere Application Server environment:
Note: The single server topology can be used for development or
the proof of concept. The Access Gateway, Service Policy Manager, Service Platform components,
and Web service implementations can
be installed on a single server. However, this is not recommended
for a deployment.
- Distributed topology
- The components (for example, the Web server, application server,
and databases) are physically separated onto different servers. This
type of topology might be used to verify functionality in an early
phase of a deployment.
- If you use only one server for the Access Gateway or Service Platform components,
it will limit failover redundancy.
- Vertical scaling topology
- Members of a cluster exist on the same physical machine.
Some services perform better with a small or moderate size Java heap.
This may not utilize all of the resources of a powerful machine, so
a vertically scaled deployment allows the processor and memory to
be more fully utilized, while each instance can run more efficiently
in a smaller JVM heap.
Frequently, vertical scaling is combined
with horizontal scaling to allow both the efficient use of resources
and the benefits of physical redundancy.
- Horizontal scaling topology
- Members of a cluster exist on multiple physical machines,
effectively and efficiently distributing the workload of a single
instance. HTTP redirector products can also be used to implement
horizontal scaling. Clustering is most effective in environments
that use horizontal scaling because of the ability to build in redundancy
and failover, to easily add new horizontal cluster members to increase
capacity, and to improve scalability by adding heterogeneous systems
into the cluster.
You can combine vertical and horizontal scaling
techniques to increase efficiency in the environment.
Each Web service implementation can have its own
cluster of service platform instances (WebSphere Application Server with
service platform common components installed locally). While multiple
service implementations can be deployed on a single service platform
instance, this makes it easier to size the hardware and software configurations
for each Web service implementation based on their performance capabilities.
The database is shared and clustered.
- Development topology
- The IBM® WebSphere Telecom Toolkit is
intended for developing client applications that will remotely reference
the services deployed in theWebSphere Telecom Web Services
Server.
You
can use WebSphere Integration Developer (WID)
version 6.1.0.102 to customize the Access Gateway mediation
flows. The WID plug-ins are provided so that mediation primitives
can be imported into the WID tooling palette for customization of
the message processing flows.