![]() ![]() ![]() ![]() ![]() ![]() ![]() |
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.
This section describes prerequisites for configuring AquaLogic Service Bus to run in a clustered environment:
To use WebLogic Server in a clustered configuration, you must have a special cluster license. Contact your BEA representative for information about obtaining one.
All WebLogic Server instances in a cluster use the same administration server for configuration and monitoring. When you add servers to a cluster, you must specify the administration server that each will use.
Note: | You are prompted to provide a multicast address when you create a BEA AquaLogic Service Bus domain using the Configuration Wizard. (See Step 2. Prepare a AquaLogic Service Bus Domain.) |
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.
Note: | You are prompted to provide listen addresses for servers when you create a BEA AquaLogic Service Bus domain using the Configuration Wizard. (See Step 2. Prepare a AquaLogic Service Bus Domain.) |
By assigning a single IP address for your clustered servers with a different port number for each server, you can set up a clustered environment on a single machine without the need to make your machine a multihomed server.
To access such an IP address from a client, structure the IP address and port number in your URL in one of the following ways:
Table 4-1 IP Address StructureIn this case, when multiple servers are run on a single machine, that machine must be configured as a multihomed server, that is, multiple IP addresses are assigned to a single computer. Under these circumstances, you structure the cluster address as a comma-separated list of IP addresses.
For example, the following listing is an example of a cluster address specified in a config.xml
file. It specifies a static IP address for each of the four servers in a cluster named MyCluster
:
<Cluster ClusterAddress="127.0.0.1:7001,127.0.0.2:7001,127.0.0.3,127.0.0.4:7001" Name="MyCluster"/>
You can also use a DNS approach to identifying servers.
For more information on addressing issues, see “Avoiding Listen Address Problems” in Setting Up WebLogic Clusters in Using WebLogic Server Clusters.
Note: | In test environments, it is possible to have multiple WebLogic Server instances on a single machine. In these circumstances, you can have some WebLogic Server instances on the same node with different port numbers and some on different nodes with the same port number. |
Note: | The local copy of the PointBase database that is installed with WebLogic Server is for evaluation purposes only. Non-evaluation development or other use of the PointBase Server requires that a separate PointBase license be obtained by the end user directly from DataMirror. |
It is important to configure your database appropriately for production use. You must provide adequate space to store data and log messages, and follow best practices for administering your database.
Note: | You can configure your database to use concurrent access. |
For the latest information about issues regarding specific databases, see the BEA AquaLogic Service Bus Release Notes.
For information about configuring a highly available cluster, see “Configuring WebLogic JMS Clustering” in Configuring Clustered WebLogic JMS Resources in Configuring and Managing WebLogic JMS.
For information about hardware and software routers, see Using WebLogic Server Clusters.
Note: | Additional requirements apply when you design your domain to include one or more firewalls. For a description of how to add firewall information to your domain configuration file, see Adding Proxy Server or Firewall Information to your Domain Configuration. For additional information, see Communications in a Cluster in Using WebLogic Server Clusters. |
For information on how to configure the Archive, Stage, and Error directories, see “Viewing and Changing Proxy Services” in Proxy Services in the Using the AquaLogic Service Bus Console.
For more information about setting up clustered WebLogic Server instances, see Setting Up WebLogic Clusters in Using WebLogic Server Clusters.
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:
You begin the definition of an AquaLogic Service Bus deployment by creating a domain using the Configuration Wizard.
To create an AquaLogic Service Bus domain using the Configuration Wizard, complete the following steps:
The Configuration Wizard is launched. It prompts you for data with which to configure your domain.
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. |
|
|||
|
|||
|
|||
Select one of the following to identify the database type and driver for the JMS Reporting Provider Data Store:
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.
|
|||
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.
|
|||
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.
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:
config.xml
with an ASCII editor.config.xml
file:<Cluster
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"/>
config.xml
file.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:
Proxy services can consume messages from a remote queue on a separate BEA domain. In this case, AquaLogic Service Bus will not create the queue for you. The JMS queues can be created for proxy services only if the queues are on the same local AquaLogic Service Bus domain.
For information about configuring JMS resources, see Configuring and Managing WebLogic JMS.
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 Securing Inbound and Outbound Messages in the BEA AquaLogic Service Bus User 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.
This section describes the basic management tasks for the managed servers in your clustered domain:
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.
By default, when the Configuration Wizard generates an AquaLogic Service Bus cluster domain:
wliaggregator.ear)
is targeted to the first managed server in the cluster. For data aggregation to function properly, the server that wliaggregator.ear
is targeted to must be started first and must be available when other managed servers are started.msgpurger.ear
) is targeted to the first managed server in the cluster. For message purging to function properly, the server where msgpurger.ear
is targeted must be available.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.
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.
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. |
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:
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.
To add a new managed server to your AquaLogic Service Bus cluster, perform the steps below using the WebLogic Server Administration Console:
Note: | Be sure to create the directory that you specify in the FileStore definition on the new server. |
TemporaryTmplt
in the Temporary Template Name box, and click Save.QueueIn_auto_
x
, accept the default value for Template, and target the queue to the new server. 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. |
wli.reporting.jmsprovider.queue_auto_
x
, and target it to the new server.wlsb.internal.transport.task.queue.email_auto_
x
, and target it to the new server.wlsb.internal.transport.task.queue.file_auto_
x
, and target it to the new server.wlsb.internal.transport.task.queue.ftp_auto_
x
, and target it to the new server.configwiz-jms
module. Add the queues that you created in step c through step g to their corresponding distributed destinations:QueueIn_auto_
x
to dist_QueueIn_auto
.wli.reporting.jmsprovider.queue_auto_
x
to dist_wli.reporting.jmsprovider.queue_auto
.wlsb.internal.transport.task.queue.email_auto_
x
to dist_wlsb.internal.transport.task.queue.email_auto
.wlsb.internal.transport.task.queue.file_auto_
x
to dist_wlsb.internal.transport.task.queue.file_auto
.wlsb.internal.transport.task.queue.ftp_auto_
x
to dist_wlsb.internal.transport.task.queue.ftp_auto
.web.xml
file for the corresponding application. For more information, see
Load Balancing in a Cluster in Using WebLogic Server Clusters.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:
The business services are now configured for operation in the extended domain.
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:
The proxy services are now configured for operation in the extended domain.
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:
wli.reporting.purge.queue
).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.
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.
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 non-backward compatible interface changes to resources referenced by a proxy service requires a partial offline deployment to avoid causing transient problems for messages being processed. To install the new version, follow the procedure below:
For more information about shutting down managed servers, see “Control Graceful Shutdowns” in Start and Stop Servers in the WebLogic Server Administration Console Online Help.
For more information about restarting managed servers, see “Start Managed Servers from the Administration Console” in Start and Stop Servers in the WebLogic Server Administration Console Online Help.
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:
For more information about backward compatibility and installation strategies, see Installing a New Version of a Proxy Service.
![]() ![]() ![]() |