WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Creating the cluster for the Access Gateway

The Access Gateway normally resides in a separate cluster from the TWSS Service Platform components. When setting up the cluster for the Access Gateway, you first install the deployment manager. Then you install the standalone servers and add them to the deployment manager. Finally, before you install the WebSphere® Telecom Web Services Server components, you create the clusters.

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

A simple Access Gateway cluster is illustrated in the following diagram. The message processing flows are deployed on one or more nodes in the cluster, and they exchange data with the shared database (TWSSDB).

Example topology for an Access Gateway cluster

Use the ESBProfile for the WebSphere Application Server Network Deployment and WebSphere Enterprise Service Bus. If you need to use an advanced profile, do not select the for development profile. It may cause problems with the WebSphere Application Server SIP container.

You must use the WebSphere Enterprise Service Bus tools for creating new profiles and application servers.

When you install a fix pack, you can check the log that is generated during the installation to verify that the fix pack was installed successfully. If the installation was successful, you should see INSTCONFSUCCESS as the last entry in the log. If you select the default installation path during the installation of WebSphere Enterprise Service Bus, the logs are stored in the following directory:
  • AIX /usr/ibm/WebSphere/ESB/logs/update/
  • Linux /opt/ibm/WebSphere/ESB/logs/update/
  • Solaris /opt/ibm/WebSphere/ESB/logs/update/

To set up a clustered configuration, you must configure cell-managed server nodes on several servers, with the deployment manager on its own server. Refer to the WebSphere ESB Information Center for additional information about this installation scenario.

  1. On the server where you plan to install the deployment manager, install the following prerequisite software:
    1. Install WebSphere Enterprise Service Bus version 6.1. If you use the launchpad installer, the WebSphere ESB installation will install the required version of WebSphere Application Server Network Deployment.
      Important: Do not attempt to install WebSphere Enterprise Service Bus to a directory path that includes National Language Characters. If the path contains National Language Characters, the installation will not complete.
    2. Install WebSphere Enterprise Service Bus version 6.2.0.2 or 7.0.0.1 (Fix Pack 2), using the detailed installation instructions provided with the fix pack.
  2. Create a deployment manager profile using the WebSphere ESB Profile creation wizard:
    1. Switch to the directory esb_root/firststeps/esb, where esb_root represents the installation location of the WebSphere ESB.
    2. Issue the following command to start the WebSphere First steps console: ./firststeps.sh
    3. From the console, launch the Profile creation wizard.
    Refer to the WebSphere ESB information center for additional information about creating a deployment manager profile.
  3. Start the deployment manager using either the First Steps script for Dmgr01 or the ./startManager.sh command.
  4. On each server where you plan to install application servers, install the following prerequisite software:
    1. Install WebSphere Enterprise Service Bus version 6.1. If you use the launchpad installer, the WebSphere ESB installation will install the required version of WebSphere Application Server Network Deployment.
      Important: Do not attempt to install WebSphere Enterprise Service Bus to a directory path that includes National Language Characters. If the path contains National Language Characters, the installation will not complete.
    2. Install WebSphere Enterprise Service Bus version 6.2.0.2 or 7.0.0.1 (Fix Pack 2), using the detailed installation instructions provided with the fix pack.
  5. Before you can add the application servers to the deployment manager, you may need to update the hosts file on each physical server. The following steps must be completed on each server where you have created application servers.
    1. Open the hosts file in a text editor. The hosts file is in the following directory: /etc/hosts
    2. Verify that there is a unique entry for the IP address of the server. By default there is a localhost entry, such as:
      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
    3. 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:
      192.0.2.21	testbox.example.com testbox
      Note: Node names cannot include the hyphen (-) character. You can use the WebSphere Application Server renameNode command to change the name.
    4. Save and close the hosts file.
    5. Repeat this step for each application server.
  6. Create a custom profile on each application server node using the WebSphere ESB Profile Creation wizard:
    1. Switch to the directory esb_root/firststeps/esb, where esb_root represents the installation location of the WebSphere ESB.
    2. Issue the following command to start the WebSphere First steps console: ./firststeps.sh
    3. From the console, launch the Profile creation wizard.
    Refer to the WebSphere ESB information center for additional information about creating a custom profile.
  7. 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.
  8. Create the cluster using the Integrated Solutions Console.

    When creating new application servers, select defaultESBServer (the Default Server template for WebSphere ESB). Do not select default (the WebSphere Default Server template).

    The detailed procedure is found in the topic Creating a cluster in the WebSphere ESB information center.

  9. 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.
  10. 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.
  11. Start the cluster:
    1. In the navigation pane, click Servers > Clusters.
    2. Select the check box for the cluster.
    3. Click Start.
  12. Create an HTTP proxy server and associate the proxy server with the cluster that you have created. Refer to the WebSphere ESB Information Center for additional information on setting up the proxy server.



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