> Deployment Guide > Configuring a Clustered Deployment

Deployment Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Configuring a Clustered Deployment

This section describes the tasks that you must perform to configure AquaLogic Service Bus for deployment in a clustered environment.

After planning the architecture of your clustered domain, as described in Designing a Clustered Deployment, you are ready to set up AquaLogic Service Bus in a clustered environment. To do this, you must configure an administration server and managed servers, and then deploy AquaLogic Service Bus resources to the servers. You also need a router (hardware or software), if you need inbound HTTP load balance functions. The persistent configuration for a domain of WebLogic Server instances and clusters is stored in an XML configuration file (config.xml) in the config directory of the root directory of your AquaLogic Service Bus domain.

To set up and deploy AquaLogic Service Bus in a clustered domain, complete the following steps:

For information about deploying AquaLogic Service Bus on a single server, see Configuring a Single-Server Deployment.

 

Step 1. Comply with Configuration Prerequisites

This section describes prerequisites for configuring AquaLogic Service Bus to run in a clustered environment:

Note: The multicast address is used by cluster members to communicate with each other. Clustered servers must share a single, exclusive, multicast address. For each cluster on a network, the combination of multicast address and port must be unique. If two clusters on a network use the same multicast address, they should use different ports. If the clusters use different multicast addresses, they can use the same port or accept the default port, 7001. To support multicast messages, the administration server and the managed servers in a cluster must be located on the same subnet.

For more information about setting up clustered WebLogic Server instances, see Setting Up WebLogic Clusters in Using WebLogic Server Clusters.

 

Step 2. Prepare an AquaLogic Service Bus Domain

When preparing an AquaLogic Service Bus domain, you must add a definition for each managed server to the domain configuration file (config.xml), assign all managed servers to a cluster, specify the AquaLogic Service Bus components on the servers in your domain, and so on.

To prepare an AquaLogic Service Bus environment in a clustered domain, complete the tasks described in the following sections:

Creating an AquaLogic Service Bus Domain Using the Configuration Wizard

You begin the definition of an AquaLogic Service Bus deployment by creating a domain using the Configuration Wizard.

Note: The procedure described in this section for setting up your domain is based on the assumption that you are running the Configuration Wizard in GUI mode from the Windows Start menu. For information about using the Configuration Wizard in different modes, see Creating WebLogic Configurations Using the Configuration Wizard
Note: To create an AquaLogic Service Bus domain using the Configuration Wizard, complete the following steps:
  1. From the Start Menu, choose All ProgramsArrow symbolBEA ProductsArrow symbolToolsArrow symbolConfiguration Wizard.

    2. The Configuration Wizard is launched. It prompts you for data with which to configure your domain.

  2. Respond to the Configuration Wizard prompts by providing the information described in the following table.
    3. Note: To comply with WebLogic Server resource naming rules, you must specify unique names for domains, WebLogic Server instances, JMS servers, and JMS stores. AquaLogic Service Bus has the same interoperability naming requirements as the WebLogic Messaging Bridge. For more information, see “Naming Guidelines for WebLogic Servers and Domains” in “Interoperating with Different WebLogic Server Releases” in Interoperating with Different WebLogic Server Releases or Foreign Providers in Configuring and Managing the WebLogic Messaging Bridge.
    Table 4-1 Responses to Configuration Wizard Prompts
    In this window . . .
    Perform the following action . . .
    Welcome
    Select Create a new WebLogic domain.
    Select Domain Source
    Select AquaLogic Service Bus.
    Configure Administrator Username and Password
    Enter user name and password.
    Configure Server Start Mode and JDK
    Select Production Mode. Select either the Sun SDK or JRockit SDK, or specify the location of another JDK.
    Customize Environment and Services Settings
    Select Yes.
    Configure the Administration Server
    If your configuration requires SSL, select the SSL enabled check box.
    Configure Managed Servers
    Add as many managed servers as required.

    Note: If you need a software HTTP router with WebLogic HttpClusterServlet in your domain for load balancing, add one extra server here.

    If your configuration requires SSL, select the SSL enabled check box for each managed server.
    Configure Machines
    Configure the type of physical machines used in the cluster.
    Configure Clusters
    Add a cluster.

    Note: AquaLogic Service Bus domains can support a single cluster.
    Assign Servers to Clusters
    Add the previously created managed servers to the cluster.

    Note: If you had previously configured a managed server as an HTTP router, do not add it to the cluster. Select this managed server from the Proxy Server drop-down list on the next window, Create HTTP Proxy Applications.

    Configure Machines
    Configure the type of physical machines used in the cluster.
    Assign Servers to Machines
    Assign each instance of WebLogic Server to the machine in the cluster on which it runs.
    Configure JDBC Data Sources
    Accept the default values for Name and JNDI name of wlsbjmsrpDataSource.
    Select one of the following to identify the database type and driver for the JMS Reporting Provider Data Store:
    • Oracle and BEA’s Oracle Driver (Type 4) Versions: 9.0.1, 9.2.0, 10
    • MS SQL Server and BEA’s MS SQL Server Driver (Type 4) Versions: 7.0, 2000
    Confirm that the Supports global transactions check box and Logging last resource option are selected. For more information about Logging last resource (LLR), see “Understanding the Logging Last Resource Transaction Option” in Configuring JDBC Data Sources in Configuring and Managing WebLogic JDBC.
    Enter your environment-specific database information in the remaining text boxes. For more information, see “Configure JDBC Data Sources” in Customizing Existing JDBC and JMS Settings in Creating WebLogic Configurations Using the Configuration Wizard.

    Note: Click Test Connections to verify that you can contact the database you want to use for the JMS Reporting Provider Data Store using this data source configuration.
    Run Database Scripts
    Select wlsbjmsrpDataSource from the Available JDBC Data Sources list.
    Select the version of the database from the DB Version drop-down list.
    Click Run Scripts.
    The scripts create the tables and indexes for the JMS Reporting Provider Data Store. The SQL output is displayed in the Results box and written to jdbc.log. If you want the results written to a different file, click the Log File check box and specify the file.

    Note: AquaLogic Service Bus does not automatically run database scripts for the JMS Reporting Provider Data Store the first time you start a production domain, as it does for domains in development mode. If you do not run the database scripts while creating your AquaLogic Service Bus production domain, you must run the scripts manually. The scripts are located in BEA_HOME/weblogic92/integration/common/dbscripts, where BEA_HOME is the directory in which you installed AquaLogic Service Bus.
    Configure JMS File Stores
    Accept the defaults for rmfilestore and add any file stores needed by proxy services or business services.
    Review WebLogic Domain
    Accept the default values.
    Create WebLogic Configuration
    Enter a name and location for your domain.
    Creating Domain
    After your domain is created, select Start Admin Server to start AquaLogic Service Bus when you exit the Configuration Wizard.

When you complete the domain configuration using the Configuration Wizard, your new domain is created in the location you specified.

Your AquaLogic Service Bus domain includes a configuration file (config.xml) that contains a definition for the administration server. For more information, see “config.xml” in Domain Configuration Files in Understanding Domain Configuration.

For information about configuring domains without using the Configuration Wizard, see Understanding Domain Configuration.

Adding Proxy Server or Firewall Information to your Domain Configuration

If you will be using Web services behind a proxy server or firewall, you must edit the config.xml file to include information about that proxy server or firewall.

To add proxy server or firewall information to your domain configuration, complete the following steps:

  1. Open config.xml with an ASCII editor.
  2. Find the line that starts with the following tag in the config.xml file:
    3. <Cluster
  3. Add the following three attributes to the Cluster attribute list:
    4. FrontendHTTPPort=”proxyPort” FrontendHTTPSPort=”proxySSLPort” FrontendHost=”proxyServerHost”

    For example, the following listing is an example of a cluster address with a firewall specified in a config.xml file for a cluster named MyCluster and a proxy server named MyProxy: 

    <Cluster ClusterAddress="127.0.0.1:7001,127.0.0.2:7001,127.0.0.3,127.0.0.4:7001" FrontendHTTPPort=”7006” FrontendHTTPSPort=”7007” FrontendHost=”MyProxy” MulticastAddress="127.0.0.5" MulticastPort="7010" Name="MyCluster"/>
  4. Save your changes and close the config.xml file.

Configuring JMS Resources

In addition to configuring JMS file stores in the Configuration Wizard, proxy services and business services that use JMS require configuration of the following resources:

For information about configuring JMS resources, see Configuring and Managing WebLogic JMS.

 

Step 3. Configure AquaLogic Service Bus Security

AquaLogic Service Bus leverages the security features of WebLogic Server to ensure message confidentiality and integrity (message-level security), secure connections between clients and WebLogic Server (transport-level security), and authentication and authorization (access control). For information about the tasks you must complete, see the AquaLogic Service Bus Security Guide.

WARNING: You must configure security separately for each AquaLogic Service Bus domain. AquaLogic Service Bus does not export or import security configurations.

If you want to configure SSL for your cluster, you can do so when creating your domain or by using the WebLogic Server Administration Console. For a domain in which security functionality is deployed in a multinode cluster, you also need to configure keystores, server certificate and private key for each managed server, and so on, for every machine in a cluster. You either need to use a separate keystore for each machine or you can use a single keystore if it is available to all machines.

 

Step 4. Starting, Stopping, and Monitoring Managed Servers

This section describes the basic management tasks for the managed servers in your clustered domain:

Starting and Stopping Managed Servers

Node Manager is a utility that enables you to start, stop, and migrate your WebLogic Server instances. You can start your managed servers using Node Manager in conjunction with the WebLogic Server Administration Console, or you can create WLST scripts to automate Node Manager functionality.

Tip: Run the setDomainEnv script before the startNodemanager script to ensure that the AquaLogic Service Bus classes are available to spawned servers. Alternatively, explicitly set classpath in the WebLogic Server Administration Console before attempting to start the server.

By default, when the Configuration Wizard generates an AquaLogic Service Bus cluster domain:

For more information on Node Manager, see Using Node Manager to Control Servers in Managing Server Startup and Shutdown. For a complete overview of methods to start and stop managed servers, see Starting and Stopping Servers in Managing Server Startup and Shutdown.

Monitoring Your Servers

Once startup is complete, you can use the AquaLogic Service Bus Console to verify the status of servers. For information about using AquaLogic Service Bus Console to monitor your servers, see “Listing and Locating Servers” in Monitoring in Using the AquaLogic Service Bus Console.

 

Step 5. Deploy an AquaLogic Service Bus Configuration

You deploy an AquaLogic Service Bus configuration in a clustered environment following the same procedure as for a single-server deployment. For a description of the deployment procedure, see Step 4. Deploy an AquaLogic Service Bus Configuration.

Note: If you have imported a configuration from a single-server environment and that configuration includes proxy services that use File, FTP, or Email transports, you must specify a Managed Server for each of those proxy services. The Managed Server drop-down list appears in the AquaLogic Service Bus Console in clustered AquaLogic Service Bus domains only.
Note: For information on how to edit the Managed Server value for a proxy service, see “Viewing and Changing Proxy Services” in Proxy Services in Using the AquaLogic Service Bus Console.

 

Step 6.Update Your Domain as Your Production Environment Changes

Production environments change over time and as application use increases. This section describes how to update your domain in response to common production environment change scenarios:

Adding a Managed Server

As use of AquaLogic Service Bus grows, you can add new managed servers to your AquaLogic Service Bus cluster to increase capacity. You add a managed server to the cluster using the WebLogic Server Administration Console. Depending on your configuration, you may also need to perform administrative tasks using the AquaLogic Service Bus Console.

Adding A Managed Server to an AquaLogic Service Bus Cluster

To add a new managed server to your AquaLogic Service Bus cluster, perform the steps below using the WebLogic Server Administration Console:

  1. Verify that the managed server that you want to add to the AquaLogic Service Bus cluster is not running. Stop the server, if necessary. For information on how to stop a managed server, see Starting and Stopping Servers in Managing Server Startup and Shutdown.
  2. If you have not already done so, in the Change Center, click Lock & Edit.
  3. Expand Environment, and select Clusters. On the Summary of Clusters panel, change the cluster address to include the address of the new server.
  4. Expand Services, and select Persistent Stores. Define a new FileStore on the new server, and assign it to a non-migratable server.
    5. Note: Be sure to create the directory that you specify in the FileStore definition on the new server.
  5. Expand Services and Messaging, and then select JMS Servers. Create a new JMS server on the new server using the new FileStore, and target it to the same non-migratable server.
  6. On the Summary of JMS Servers panel, click the name of the new JMS server. Select jmsResources in the Module Containing Temporary Template list, enter TemporaryTmplt in the Temporary Template Name box, and click Save.
  7. Create the necessary queues and add them to the corresponding distributed destinations by performing the following steps:
    1. If you have not already done so, expand Services and Messaging.
    2. Select JMS Modules, and click configwiz-jms.
    3. Create a new queue named QueueIn_auto_x, accept the default value for Template, and target the queue to the new server.
      4. Note: For the names of queues specified in this step through step 8, x is the number of managed servers currently in the AquaLogic Service Bus cluster incremented by 1. For example, if you were adding a managed server to a cluster that currently contains two managed servers, then x equals 3. You would be creating QueueIn_auto_3 in this step, and the names of the queues you create in step d through step g would also end with 3.

      While defining QueueIn_auto_x, create a new subdeployment (for example, sub_new), and then select the JMS server on the new server as the target.

      Note: You will reuse this subdeployment in step d through step g, instead of creating a new subdeployment for each queue.
    4. Create wli.reporting.jmsprovider.queue_auto_x, and target it to the new server.
    5. Create wlsb.internal.transport.task.queue.email_auto_x, and target it to the new server.
    6. Create wlsb.internal.transport.task.queue.file_auto_x, and target it to the new server.
    7. Create wlsb.internal.transport.task.queue.ftp_auto_x, and target it to the new server.
    8. Create wli.reporting.jmsprovider_error.queue_auto_x, and target it to the new server.
    9. Create wlsb.internal.transport.task.queue.sftp_auto_x, and target it to the new server.
  8. Expand Services, Messaging, and JMS Modules, and then select the configwiz-jms module. Add the queues that you created in step c through step g to their corresponding distributed destinations:
    1. Add QueueIn_auto_x to dist_QueueIn_auto.
    2. Add wli.reporting.jmsprovider.queue_auto_x to dist_wli.reporting.jmsprovider.queue_auto.
    3. Add wlsb.internal.transport.task.queue.email_auto_x to dist_wlsb.internal.transport.task.queue.email_auto.
    4. Add wlsb.internal.transport.task.queue.file_auto_x to dist_wlsb.internal.transport.task.queue.file_auto.
    5. Add wlsb.internal.transport.task.queue.ftp_auto_x to dist_wlsb.internal.transport.task.queue.ftp_auto.
    6. Add wli.reporting.jmsprovider_error.queue_auto_x to dist_wli.reporting.jmsprovider_error.queue_auto.
    7. Add wlsb.internal.transport.task.queue.sftp_auto_x to dist_wlsb.internal.transport.task.queue.sftp_auto.
  9. In the Change Center, click Activate.
  10. You can now start the new managed server. For information on how to start a managed server, see Starting and Stopping Servers in Managing Server Startup and Shutdown.
  11. If your cluster has an HTTP load balancer (software or hardware), add the new managed server to the server list of the load balancer. For example, if you are using the WebLogic HttpClusterServlet, you should add the new server to the web.xml file for the corresponding application. For more information, see Load Balancing in a Cluster in Using WebLogic Server Clusters.

Updating Business Service Configurations for an Expanded Cluster

If your AquaLogic Service Bus configuration includes one or more business services that use JMS request/response functionality, then you must also perform the following procedure using the AquaLogic Service Bus Console after adding the new managed server to the cluster:

  1. In the Change Center, click Create to create a session.
  2. Using the Project Explorer, locate and select a business service that uses JMS request/response. Business services of this type display Messaging Service as their Service Type.
  3. At the bottom of the View Details page, click Edit.
  4. If there is a cluster address in the endpoint URI, add the new server to the cluster address.
  5. On the Edit a Business Service - Summary page, click Save.
  6. Repeat step 2 through step 5 for each remaining business service that uses JMS request/response.
  7. In the Change Center, click Activate.

The business services are now configured for operation in the extended domain.

Note: For business services that use a JMS MesageID correlation scheme, you must edit the connection factory settings to add an entry to the table mapping managed servers to queues. For information on how to configure queues and topic destinations, see “JMS Server Targeting” under JMS Server Configuration, in WebLogic Server Administration Console Online Help

Updating Proxy Service Configurations for an Expanded Cluster

If your AquaLogic Service Bus configuration includes one or more proxy services that use JMS endpoints with cluster addresses, then you must also perform the following procedure using the AquaLogic Service Bus Console after adding the new managed server to the cluster:

  1. In the Change Center, click Create to create a session.
  2. Using the Project Explorer, locate and select a proxy service that uses JMS endpoints with cluster addresses.
  3. At the bottom of the View Details page, click Edit.
  4. If there is a cluster address in the endpoint URI, add the new server to the cluster address.
  5. On the Edit a Proxy Service - Summary page, click Save.
  6. Repeat step 2 through step 5 for each remaining proxy service that uses JMS endpoints with cluster addresses.
  7. In the Change Center, click Activate.

The proxy services are now configured for operation in the extended domain.

Dropping a Managed Server

Using WebLogic Server administration tools, you can drop a managed server from your AquaLogic Service Bus cluster. Before deciding to drop a managed server, you should take into account the following considerations:

For information about dropping a managed server from a cluster, see “Delete Managed Servers” in Configure Domains in the WebLogic Server Administration Console Online Help.

Changing a Business Service in a Cluster

The procedure for changing a business service is the same in both single-server and cluster environments. For information about changing a business service, see Changing a Business Service.

However, the procedure for deploying changes to a business service in a cluster depends on the types of changes made to the business service and the nature of any other changes that might be deployed simultaneously. For more information, see the description of installation strategies in the following section.

Installing a New Version of a Proxy Service in a Cluster

As your business requirements change, you may need to make changes to your proxy services. You can make these changes dynamically online, partially offline, or completely offline. If your changes are backward compatible (that is, you are making no changes to interfaces), you can make your changes dynamically online using the AquaLogic Service Bus Console. Making other types of changes should be done partially or completely offline, which requires additional system administration steps.

For information about performing online updates, see Online Configuration Updates.

Making changes that include non-backward compatible changes to proxy service interfaces requires complete offline deployment. To install the new version, follow the procedure below while all servers are operational:

  1. Quiesce all inbound messages.
  2. Confirm all asynchronous backlogged messages have been processed.
  3. Make the necessary changes in the proxy service, and test to verify the proxy service operates as required.
  4. Resume accepting inbound messages.

For more information about backward compatibility and installation strategies, see Installing a New Version of a Proxy Service.


  Back to Top       Previous  Next