This section describes the tasks that you must perform to configure Oracle WebLogic Integration (WLI) 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 WLI in a clustered environment. To do this, you must configure a router (hardware or software), an administration server, and managed servers, and then deploy WLI resources to the servers. The persistent configuration for a domain of Oracle WebLogic Server instances and clusters is stored in an XML configuration file (config.xml
) on the administration server.
To set up and deploy WLI in a clustered domain, complete the following steps:
For information about deploying WLI on a single server, see Configuring a Single-Server Deployment.
This section describes prerequisites for configuring Oracle WebLogic Integration to run in a clustered environment:
All Oracle 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 listen addresses for servers when you create a WLI domain using the Domain Configuration Wizard. (See Step 2. Prepare the WLI 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:
In 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 Oracle WebLogic Server instances on a single machine. In these circumstances, you can have some Oracle WebLogic Server instances on the same node with different port numbers and some on different nodes with the same port number. |
wli-config.properties
by uncommenting the weblogic.wli.WliClusterName
property and setting it to the name of the cluster as used in the Oracle WebLogic Server Administration Console.
For example, the following is an example of a WLI target, wliCluster
, specified in a wli-config.properties
file:
weblogic.wli.WliClusterName=wliCluster
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 information about database tuning requirements associated with WLI applications, see Preparing Your Database and the database-specific notes in Maintaining Availability.
For the latest information about issues regarding specific databases, see the Oracle WebLogic Integration 10g Release 3 (10.3) Release Notes.
For information about configuring a highly available cluster, see Programming WebLogic JMS.
For information about hardware and software routers, see Using Oracle 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 Domain Configuration. For more information, see Communications in a Cluster in Using WebLogic Server Clusters. |
For more information about setting up clustered Oracle WebLogic Server instances, see Setting Up WebLogic Clusters in Using WebLogic Server Clusters.
You begin the definition of a WLI deployment by creating a domain using the Domain Configuration Wizard.
To create a WLI domain using the Domain Configuration Wizard, complete the following steps:
The Welcome page of the Oracle WebLogic Configuration Wizard appears.
As you proceed through the Configuration Wizard, several pages will appear in a sequence. You need to specify your settings on each page and click Next to proceed to the subsequent page.Table 4-1 lists the pages and the options that you need to select to create the domain successfully.
|
|||||
|
|||||
|
|||||
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.
|
|||||
|
|||||
|
|||||
|
Two configuration files are created in your WLI domain:
For information about specifying security features in your configuration by editing config.xml
, see Adding Proxy Server or Firewall Information to Domain Configuration. For more information about config.xml
, see
Oracle WebLogic Server Configuration Reference.
For information about wli-config.properties
, see wli-config.properties Configuration File.
If you will be using a Web service 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.
If you want to configure SSL for your cluster, you can do so by using the Oracle 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.
The security administrator also has to make sure that the contents of shared or individual keystores in a cluster is consistent. Inconsistencies can be introduced when adding new certificates, if private keys must also be added. For example, if you add certificates for remote trading partners using the Oracle WebLogic Integration Administration Console, they can optionally be imported in the identity keystore used by each managed server in a cluster. However, this mechanism is not available (for security reasons) if private keys must be inserted in these keystores.
For information about the tasks you must complete, see:
This section describes how to start the servers in your clustered domain:
To start servers in a domain for which the Node Manager is configured, complete the following procedure:
Note: | You can also start managed servers from the command line by using the following command from <domain-directory>/bin : |
Note: | startManagedWebLogic.cmd <managed-server-name> <admin-url> |
For information about starting the Node Manager, see Node Manager Administrator's Guide.
For the procedure to start the Oracle WebLogic Server Administration Console (and the administration server, if necessary), see “Starting the Administration Console” in Overview of Oracle WebLogic Server System Administration in Configuring and Managing Oracle WebLogic Server.
For information about the setting the properties for Node Manager use, see Starting and Stopping Servers in Oracle WebLogic Server Administration Console Online Help.
For information about how the Start Server command is affected by other settings made via the Oracle WebLogic Server Administration Console, see the Oracle WebLogic Server Administration Console Online Help.
Once startup is complete, you can use the Oracle WebLogic Server Administration Console to verify deployments and status. For information about using Oracle WebLogic Server Administration Console to monitor your servers, see “Monitoring a Oracle WebLogic Server Domain” in Oracle WebLogic Server Performance and Tuning. For information about monitoring your WLI domain, see “Run-Time Tuning Issues” in Performance Tips.
Note: | In cluster configurations, while running business processes or using the Oracle WebLogic Integration Administration Console, the following error message may appear in the Oracle WebLogic Server console window for the Oracle WebLogic Server that hosts the Oracle WebLogic Server Administration Console: |
Note: | Failed to initialize clustered process configuration backend |
Note: | If you encounter this problem, you must set the ClusterAddress attribute for the cluster. To learn how, see “Cluster Address” in Setting up WebLogic Clusters in Using WebLogic Server Clusters. |
If you need to shut down your WLI application, use the Oracle WebLogic Server Administration Console.
Note: | It is recommended that you do not close the command window or press Ctrl+c to stop WLI. |
For the procedure to shut down your application gracefully, see “Graceful Shutdown of All Servers” and “Start/Stop a Server” in Oracle WebLogic Server Administration Console Online Help.
Once you have configured and secured your WLI domain, you can deploy a WLI application to your cluster. You use the Oracle WebLogic Server Administration Console to deploy the EAR file that contains your WLI application.
The queues necessary for your application must be created manually using the Oracle WebLogic Server Administration Console.
Note: | Async request and async request error queues, as well as conversational state tables, are created automatically for applications in the Oracle Workshop for WebLogic development environment. For production environments, however, you must create these queues and tables manually. For cluster deployments, these queues must be distributed destinations with physical members on each managed server. |
For information about configuring JMS resources using the Oracle WebLogic Server Administration Console, see Deploying Applications to Oracle WebLogic Server.
Note: | If your WLI solution uses the RDBMS Event Generator, be sure to configure the redelivery settings appropriately for its queues. For the procedure to configure the redelivery settings, see RDBMS Event Generator. |
For the procedure to deploy an EAR file, see “Configuring and Deploying a New Enterprise Application or Web Service” in Enterprise Applications in Oracle WebLogic Server Administration Console Online Help.
For examples of automation scripts that build, configure, and deploy WLI applications outside of an interactive console environment, see WebLogic Integration Sample Code.
Note: | Code samples and utilities are posted on Oracle Technology Network (OTN) for your convenience. They are not supported by Oracle. |