Index Changes
This is version 3. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]
Beta Document for v2.1

Table of Contents

Implementing the HTTP Binding Component in a Cluster

The HTTP BC has no load balancing and failover mechanisms of its own, but Sun provides the HTTP Load Balancer to perform these functions. The Load Balancer is a web server plug-in that accepts HTTP and HTTPS requests and distributes them to application server instances in a cluster. This allows the HTTP BC to be scaled horizontally, running on multiple instances in a cluster. The Load Balancer gives you several advantages by managing the workload across cluster instances. If you use the HTTP Load Balancer, you need to configure the load balancer for each instance in the cluster.

You can read more information about clustering for the HTTP BC and using the HTTP Load Balancer at Clustering Support For the HTTP Binding Component. For detailed information about the HTTP Load Balancer, see Configuring HTTP Load Balancing in the Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide.

To Add the HTTP Binding Component to the Cluster

The HTTP BC is not dependent on any shared libraries, so you only need to add the binding component to the cluster.

  1. Add the HTTP BC to the cluster as described in To Add a GlassFish ESB Component to a Cluster.
    The name of the HTTP BC node is sun-http-binding.
  2. Modify any runtime properties as you normally would for the HTTP BC.
    For more information, see HTTP Binding Component Runtime Properties.

To Configure the HTTP BC Port Numbers for Clustering

Each component instance in the cluster must have exclusive access to the resource, so a unique port number must be assigned to each instance. When you define service ports for the URL, use variables instead of actual port numbers in the soap:address element. This allows the client to direct HTTP requests to the default port, which is defined in the HTTP BC runtime properties. The value of the variable is resolved by the HTTP BC based on the configured default values used when the application was deployed.

Note - If you reinstall the HTTP BC, you need to reconfigure the default ports for each component instance. The BC also needs to be configured for each server instance in the cluster.
  1. In the WSDL files for the HTTP BC, change any hard-coded HTTP and HTTPS port numbers in the soap:address elements to variables.
    Use the following variables:
    • ${HttpDefaultPort}}} for the HTTP port
    • ${HttpsDefaultPOrt}}} for the HTTPS port
      For example, instead of using this URL:
      <soap:address location="http://localhost:18181/Synchronous"/>
      Use the following URL:
      <soap:address location="http://localhost:${HttpDefaultPort}/Synchronous"/>
  2. If it is not already enabled, enable the HTTP BC on the target cluster. Do the following to enable the BC:
    1. On the GlassFish Admin Console, expand JBI, expand Components, and then select sun-http-binding.
    2. Click the Targets tab.
    3. In the Targets list, select the check box next to the cluster and then click Start.
  3. To configure the BC, click the Configuration tab and then do the following:
    1. In the View/Update Instance field, select the first instance to configure.
    2. Verify the default values for the HTTP Port Number and the Default HTTPS Port Number properties.
      Important - These values are chosen automatically and must be different for each instance. If there is a port conflict, you can change the default port numbers but it is recommended that you use the default values.
    3. Click Save.
    4. Repeat the above steps for each instance in the cluster, verifying that the port numbers are unique for each instance.

Previous Next

Return to GlassFish ESB Documentation Home

JSPWiki v2.4.100
« Home Index Changes Prefs
This particular version was published on 12-May-09 11:41 AM, -0700 by CarolT