WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Creating the cluster for Service Platform components and Web service implementations

You can create a separate cluster for the Service Platform components. This cluster will also contain the Web service implementations, which you will install on the same servers as the Service Platform components.

Before you begin
You must have completed the following steps:
Note: Ensure that your application server node names do not contain the hyphen (-) character. If necessary, you can use the WebSphere® Application Server renameNode command to change the names.
About this task

The cluster for the Service Platform components and Web service implementations must be created on WebSphere Application Server Network Deployment, version 6.1.0.29 or 7.0.0.7.

A simple cluster is illustrated in the following diagram. In the illustration, the Service Platform components are deployed on the same node as the Web service implementations, as required. The TWSS Administration Console is deployed on the deployment manager node, as required. There are unique database instances for theUsage Record component Web service and the Service Platform component configuration data. However, this is not required.

Example topology for a Web services cluster

If possible, use the default profiles for WebSphere Application Server Network Deployment. Also, avoid customizing the profile with the Profile Management Tool. If you need to use an advanced profile, do not select the for development profile. Doing so can cause problems with the WebSphere Application Server SIP container.

After you have installed the prerequisite software, you must federate the application server nodes into the deployment manager. Then, you can create the cluster using the Integrated Solutions Console. You can create the first cluster member from one of the application servers you federated into the deployment manager. After you have created each application server, you must add each application server to the network deployment manager cell. Additional cluster members can be added using the Integrated Solutions Console at a later time, as needed.

  1. On the physical server where you plan to install the deployment manager, install WebSphere Application Server version 7.0.0.7 or 6.1.0.29, using the launchpad. When prompted to select the WebSphere Application Server environments, select Cell (deployment manager and a managed node).

    Refer to the WebSphere Application Server information center for detailed information about the installation.

  2. On each physical server where you plan to install an application server, install WebSphere Application Server version 7.0.0.7 or 6.1.0.29, using the launchpad. When prompted to select the WebSphere Application Server environments, select Application server.

    Refer to the WebSphere Application Server information center for detailed information about the installation.

  3. Before you can add the application servers to the deployment manager, you may need to update the hosts file on each physical server.
    1. Click Security > Global security and enable both administrative security and application security.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Security > Secure administration, applications, and infrastructure.

      Refer to the WebSphere Application Server information center for detailed information about the installation.

    2. Open the hosts file in a text editor. The hosts file is in the /etc/hosts directory.
    3. Verify that there is a unique entry for the IP address of the server. By default there is a localhost entry, for example:
      127.0.0.1 	host_name.
      domain.com	host_name	localhost.localdomain
      localhost
      Replace the default entry with the following line:
      127.0.0.1		localhost.localdomain	localhost
    4. Then add a new line that specifies the IP address of the server.
      ip_address	host_name.domain.com	host_name
      Where:
      • ip_address is the IP address of the server.
      • host_name is the host name of the server.
      • domain is the domain of the server.
      For example:
      9.32.175.169	testbox.myco.com
      testbox
      Note: Node names cannot include the hyphen (-) character. You can use the WebSphere Application Server renameNode command to change the name.
    5. Save and close the hosts file.
    6. Repeat this step for each application server.
  4. Use the addNode command to add the application server to the cell.
    1. On the physical server that you want to add to the deployment manager, change to the bin directory for the application server profile. For example:
      cd was_profile_root/bin

    2. To add a node, run the addNode command. For example:
      ./addNode.sh dmgr.domain.com
      Where:
      • dmgr.domain.com is the fully qualified host name of the deployment manager server.
    3. To verify that the application servers were added to the cell, review the addNode.log. When you run the addNode command, a message displays in the location where the addNode.log is stored, for example: was_profile_root/AppSrv01/logs.
    4. Repeat this step for each application server that will be added to the cell.
  5. Start the deployment manager, nodes, and servers:
    1. Start the deployment manager. Run the following command:
      • AIX was_profile_root/bin/startManager.sh
      • Linux was_profile_root/bin/startManager.sh
      • Solaris was_profile_root/bin/startManager.sh

      Where:

      • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).
    2. Start the nodes. Run the following command:
      • AIX was_profile_root/bin/startNode.sh
      • Linux was_profile_root/bin/startNode.sh
      • Solaris was_profile_root/bin/startNode.sh

      Where:

      • The was_profile_root path contains the name of a federated node profile (for example, Custom01).
    3. Start the servers. Run the following command:
      • AIX was_profile_root/bin/startServer.sh server_name -username user_name -password password
      • Linux was_profile_root/bin/startServer.sh server_name -username user_name -password password
      • Solaris was_profile_root/bin/startServer.sh server_name -username user_name -password password
      Note: The user_name and password parameters are required only when security is enabled.

      Where:

      • The was_profile_root path contains the name of the application server profile (for example, AppSrv01).
      • server_name is name of the application server.
      • user_name represents your WebSphere Application Server administrator user ID.
      • password represents the password associated with your user_name.
  6. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  7. Federate the application server into the deployment manager cell.
    1. If both server processes are running, use the administrative console for the deployment manager to add the application server node into the cell.
    2. Click System administration > Nodes > Add Node. Then follow the wizard to add the node into the cell. If both processes are on the same machine, you can use localhost for the host name.
      Note: The SOAP port for the application server node is 8880 unless you changed the port during profile creation.
  8. Create the cluster using the Integrated Solutions Console. The detailed procedure is found in the topic Creating clusters in the WebSphere Application Server information center.
  9. Create an HTTP proxy server and associate it with the cluster that you have created. Refer to the WebSphere Application Server information center for additional information about setting up the proxy server.
  10. Create a SIP proxy server if you plan to deploy SIP-based Web service implementations, and associate the proxy server with the cluster that you have created.
  11. Enable replication for SIP sessions if you plan to deploy SIP-based Web service implementations. Refer to the WebSphere Application Server information center for additional information about replicating SIP sessions.
    Note: It is necessary to define user groups in the user registry. Three group names will be requested by the TWSS First Steps configuration script. The group names are configurable; and the following names are recommended:
    • PolicyAdminGroup
    • TWSSAdminGroup
    • NotifyMgmtAdminGroup



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