In this scenario, the Access Gateway,
the Service Policy Manager,
and the Service Platform components are
deployed together on the same cluster.
About this task
This scenario guides you through the steps on how to set
up a single-clustered environment.
Note: This deployment is recommended
for most installations. You will only need to run the installation
scripts on the deployment manager.
- Review the prerequisites information
to ensure that you have the correct operating system, hardware, and
software needed to complete the installation.
- Configure the operating system for each
server where you plan to install Telecom Web Services Server (TWSS)
components.
- Install the database server software on
the database server node. Optionally, install the database client
on the deployment manager node.
- Install the WebSphere® Enterprise Service
Bus (ESB)
product on each server.
The WebSphere Application Server product
is embedded within WebSphere ESB.
Make sure that WebSphere Application Server is
at the version level that is required to run the TWSS Service Platform components.
- Create the following three groups in the user
registry:
- TWSSAdminGroup
- PolicyAdminGroup
- NotifyAdminGroup
Note: The group names are used in the First Steps script.
- You start with a clean profile,
by using the WebSphere Application Server manageProfiles command
to delete the old profile, and then use the profile management tool
to create a new profile.
- Create the cluster. You
can give the cluster a descriptive name, such as TWSScluster.
Note: Make
sure to use the ESB profile for the Access Gateway on
ESB.
- Use the Telecom Web Services Server base
installer to install the TWSS base components. There are two installation procedures available:
Interactive installer and Silent.
- Use the TWSS Services installer to install
one or more Web service implementations. There are two installation procedures available:
Interactive installer and Silent.
- Run the First Steps script to
configure your system.
The First Steps script configures
WebSphere, Access Gateway, Service Policy Manager, Service Platform components,
and Service implementations. This is based on the user input provided
by the First Steps script on
the configuration panel or response file.
The First Steps script also
publishes necessary changes and software to each server instance in
the cluster. The First Steps script also
deploys any application EARs that are selected in the installation.
- If necessary, use the TWSS Administration Console to
perform additional configuration for your Web services.
Note: Connections
to the backend network elements–such as SMPP, MLP, Parlay gateway,
and MM7 servers–generally need to be configured after the system is
started. You can perform this configuration using the TWSS Administration Console.
Additionally, the Parlay Administration Console can
be used for the parlay gateway configuration.