WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Installing Telecom Web Services Server on multiple clusters

Some installations might require a more complex environment for deploying the Telecom Web Services Server product (TWSS) . The Access Gateway, the Service Policy Manager, and the Service Platform components are installed on separate clusters.

About this task
This scenario guides you through setting up an environment to deploy the TWSS components on separate clusters:
  • Cluster for the Access Gateway
  • Cluster for the Service Policy Manager and the Service Platform components
Note: The Telecom Web Services Server installers and First Steps script have to run for each deployment manager that is used. If each cluster has a unique deployment manager, the Telecom Web Services Server installers and the First Steps script will run separately. If all of the clusters are controlled by a single deployment manager, then the Telecom Web Services Server installer and the First Steps script will only need to be run once.

It is important to note that the First Steps script deploys and configures all of the base components and services that are installed on the server where it runs. Configurations in which a single server is shared between multiple clusters, and a different set of services is deployed on each cluster, are not supported.

Other installation configurations are possible, and it is beyond the scope of this document to detail all of the possible options. However, you can use this scenario to extrapolate a configuration that works for your network.

  1. Review the prerequisites information to ensure that you have the correct operating system, hardware, and software needed to complete the installation.
  2. Configure the operating system for each server where you plan to install Telecom Web Services Server (TWSS) components.
  3. Install the database server software on the database server node. Optionally, install the database client on the deployment manager node.
  4. Install the prerequisite software.
    1. Install WebSphere® Application Server version 7.0.0.7 or version 6.1.0.29 on the clusters where you install the Service Policy Manager and Service Platform components.
    2. Install WebSphere Enterprise Service Bus version 6.2.0.2 or 7.0.0.1 (which includes WebSphere Application Server) on the Access Gateway cluster.
    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.
  5. Create the following three groups in the user registry:
    • TWSSAdminGroup
    • PolicyAdminGroup
    • NotifyAdminGroup
    Note: The group names are used in the First Steps script panel:
  6. Create the clusters for the Access Gateway and the Service Platform components. (This scenario assumes that the Service Policy Manager and all of the Web service implementations are in a single cluster. However, they can be in different clusters if needed.)
    1. Create the Access Gateway cluster. Assign a descriptive name to the cluster, such as AccessGateway.
    2. Create the cluster for the Service Platform components. Assign a descriptive name to the cluster, such as Services.
  7. Use the Telecom Web Services Server base installer to install the Access Gateway on the AccessGateway cluster. There are two installation procedures available: Interactive installer and Silent.
  8. Use the Telecom Web Services Server base installer to install the following components on the Services cluster. There are two installation procedures available: Interactive installer and Silent.
    • Service Policy Manager
    • Service Platform components
    • TWSS Administration Console
    • Parlay Administration Console (if needed)
    • First Steps configuration script
  9. Use the TWSS Services installer to install the required service implementations on the Services cluster. In addition, the First Steps script will need to be installed in each cluster. There are two installation procedures available: Interactive installer and Silent.

    The services installer will have the required database support files and the connector support component for a variety of services. This includes services such as the Parlay and SMPP connectors.

  10. From the database server, create and initialize the database using crtsrvDb2 or crtsrvOra. This is provided as part of the TWSS base installation.

    The create-database script (crtsrv*) is not visible on the Feature installation panel. It is installed only if you select the features that require them. For more details, refer to the topic Customizing the installation response file for Telecom Web Services Server base components.

  11. Run the First Steps script on the Access Gateway cluster to configure your system. The wizard performs the following tasks:
    • Configure common resources for WebSphere Application Server
    • Configure common resources for the Access Gateway
    • Process all configurations for each server instance (syncServers)
  12. Run the First Steps script on the Services cluster to configure your system. The wizard configures the common resources for WebSphere Application Server.
  13. 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.



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