|
|
This section describes the tasks that you must perform to configure WebLogic Integration 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 WebLogic Integration in a clustered environment. To do this, you must configure a router (hardware or software), an administration server, and managed servers, and then deploy WebLogic Integration resources to the servers. The persistent configuration for a domain of WebLogic Server instances and clusters is stored in an XML configuration file (config.xml) on the administration server.
To set up and deploy WebLogic Integration in a clustered domain, complete the following steps:
For information about deploying WebLogic Integration on a single server, see Configuring a Single-Server Deployment. For a detailed list of deployment tasks associated with WebLogic Platform applications in general, see Deployment Checklist in Deploying WebLogic Platform Applications.
This section describes prerequisites for configuring WebLogic Integration 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 WebLogic Integration domain using the Configuration Wizard. (See Step 2. Prepare a WebLogic Integration 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 WebLogic Integration domain using the Configuration Wizard. (See Step 2. Prepare a WebLogic Integration 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 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. |
wli-config.properties by uncommenting the weblogic.wli.WliClusterName property and setting it to the name of the cluster as used in the WebLogic Server Administration Console.
For example, the following is an example of a WebLogic Integration 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 detailed information regarding configuring databases for WebLogic Platform applications, see Creating and Configuring the Production Database in Deploying WebLogic Platform Applications.
For information about database tuning requirements associated with WebLogic Integration applications, see Preparing Your Database and the database-specific notes in Maintaining Availability.
For the latest information about issues regarding specific databases, see the WebLogic Integration 8.1 Release Notes.
For information about configuring a highly available cluster, see "Configuring WebLogic JMS Clustering" in Managing WebLogic JMS in Programming WebLogic JMS.
For more information about load balancing for WebLogic Platform applications, see "Configuring Load Balancing and Failover in a Cluster" in Creating and Configuring the WebLogic Domain in Deploying WebLogic Platform Applications.
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 more information about setting up clustered WebLogic Server instances, see Setting Up WebLogic Clusters in Using WebLogic Server Clusters.
When preparing a WebLogic Integration 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 WebLogic Integration components on the servers in your domain, and so on.
To prepare a WebLogic Integration environment in a clustered domain, complete the tasks described in the following sections:
You begin the definition of a clustered WebLogic Integration deployment by creating a domain using the BEA 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. |
To create a WebLogic Integration domain using the Configuration Wizard, complete the following steps:
BEA WebLogic Platform 8.1Configuration Wizard.The Configuration Wizard is launched. It prompts you for data with which to configure your domain.
|
|||||
|
|||||
|
|||||
|
|||||
|
For a description of the correct JDBC settings for an XA domain, see "How Do I: Create a WebLogic Integration Domain Using Oracle with an XA Driver?" in
How Do I ...? in Creating WebLogic Configurations Using the Configuration Wizard.
You must configure
cgPool for WebLogic Integration to function. If the reporting data tables are referenced through a different data store than cgPool, then you must define bpmArchPool as a valid pool and configure it as the Reporting Data DataStore in the WebLogic Integration Administration Console. These configuration changes take effect on the next start of WebLogic Server. (For information on configuring the Reporting Data DataStore in the WebLogic Integration Administration Console, see "Configuring the Archive Data Store" in
System Configuration in Managing WebLogic Integration Solutions.)
If you are going to define a JDBC datastore, you must define at least one non-XA JDBC connection pool. JDBC datastores work only with non-XA JDBC connection pools.
|
|||||
Accept the defaults for
cgDataSource and bpmArchDataSource. Add any application-specific data sources.
|
|||||
|
For information about loading WebLogic Integration tables in the JDBC database, see "Creating the WebLogic Integration Tables" in Configuring a Production Database in Managing WebLogic Integration Solutions.
|
|||||
|
|||||
|
For information on the default targets for application components, see WebLogic Integration Deployment Resources..
|
|||||
|
For more information, see "Creating XA Domains Using Configuration Templates" in
How Do I... in Creating WebLogic Configurations Using the Configuration Wizard.
|
|||||
|
|||||
|
|||||
When you complete the domain configuration using the Configuration Wizard, your new domain is created in the location you specified.
For information about configuring domains without using the Configuration Wizard, see "Tools for Configuring the Target Domain" in Creating and Configuring the WebLogic Domain in Deploying WebLogic Platform Applications.
Two configuration files are created in your WebLogic Integration domain:
For information about specifying security features in your configuration by editing config.xml, see Adding Proxy Server or Firewall Information to your Domain Configuration. For more information about config.xml, see 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:<ClusterFrontendHTTPPort="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.You create database tables in a clustered environment following the same procedure as for a single-server deployment. For information about creating the WebLogic Integration database tables, see Creating the Database Tables.
If you want to configure SSL for your cluster, you can do so 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.
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 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:
For general information about configuring security for WebLogic Platform applications, see Configuring Security in Deploying WebLogic Platform Applications.
Step 4. Start and Monitor the Managed Servers in the Domain
This section describes how to start the servers in your clustered domain:
For information concerning starting servers for WebLogic Platform applications, see "Starting the Servers" in Creating and Configuring the WebLogic Domain in Deploying WebLogic Platform Applications.
To start servers in a domain for which the Node Manager is configured, complete the following procedure:
For information about starting the Node Manager, see in Configuring, Starting, and Stopping Node Manager in Configuring and Managing WebLogic Server.
For the procedure to start the WebLogic Server Administration Console (and the administration server, if necessary), see "Starting the Administration Console" in Overview of WebLogic Server System Administration in Configuring and Managing WebLogic Server.
For information about the setting the properties for Node Manager use, see "Configure Startup Arguments for Managed Servers" in "Starting Managed Servers from the Administration Console" in Starting and Stopping Servers in WebLogic Server Adminstration Console Online Help.
For information about how the Start Server command is affected by other settings made via the WebLogic Server Administration Console, see the WebLogic Server Administration Console Online Help.
Once startup is complete, you can use the WebLogic Server Administration Console to verify deployments and status. For information about using WebLogic Server Administration Console to monitor your servers, see Monitoring a WebLogic Server Domain in Creating WebLogic Configurations Using the Configuration Wizard. For information about monitoring your WebLogic Integration domain, see "Run-Time Tuning Issues" in Performance Tips in the WebLogic Integration Solutions Best Practices FAQ.
| Note: | In cluster configurations, while running business processes or using the WebLogic Integration Administration Console, the following error message may appear in the WebLogic Server console window for the WebLogic Server that hosts the 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 WebLogic Integration application, use the WebLogic Server Administration Console.
| Note: | It is recommended that you do not close the command window or press Ctrl+c to stop WebLogic Integration. |
For the procedure to shut down your application gracefully, see "Graceful Shutdown of All Servers" and "Start/Stop a Server" in Clusters in the WebLogic Server Administration Console Online Help.
Once you have configured and secured your WebLogic Integration domain, you can deploy a WebLogic Integration application to your cluster. You use the WebLogic Server Administration Console to deploy the EAR file that contains your WebLogic Integration application.
If you did not configure all the queues necessary for your application while configuring your WebLogic Integration domain as described in Creating a WebLogic Integration Domain Using the Configuration Wizard, you can configure and target them manually using the 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 WebLogic Workshop development environment. You must create these queues and tables manually for production environments. For cluster deployments, these queues should be distributed destinations with physical members on each managed server. |
| Note: | For information on how to configure these resources, see "Adding Resources Required by the Application From the wlw-manifext.xml File" in Creating and Configuring the WebLogic Domain in Deploying WebLogic Platform Applications. |
For information on how to configure JMS resources using the WebLogic Server Administration Console, see "How Do I: Deploy WebLogic Workshop Web Services to a Production Server?" in How Do I... in WebLogic Workshop Help.
| Note: | If your WebLogic Integration 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 WebLogic Server Administration Console Online Help.
| Note: | You can update environment-specific information in your Application Views and adapter instances either before or after deploying your WebLogic Integration application: |
For examples of automation scripts that build, configure, and deploy WebLogic Integration applications outside of an interactive console environment, see the WebLogic Integration Solution Samples and the PO Sample that is available in the BEA dev2dev Code Library at the following URL:
| Note: | Code samples and utilities are posted on dev2dev for your convenience. They are not products supported by BEA. |
For a complete list of tools available to automate the application deployment process, see "Automating the Promotion Process" in Overview of WebLogic Platform Development in Deploying WebLogic Platform Applications.
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:
For information about promoting WebLogic Platform applications from development environments to production environments, see "Steps to Promote WebLogic Platform Applications" in Overview of WebLogic Platform Development in Deploying WebLogic Platform Applications.
As the use of an application grows, you may need to add new managed servers to a WebLogic Server cluster to provide extra capacity. For information about adding a new managed server to a cluster, see "Adding and Removing Servers in an Existing Domain" in Creating, Configuring, and Monitoring Servers in WebLogic Server Administration Console Online Help.
Once you have added the new managed server and started it within the cluster, you can begin to move processing responsibility onto that new server. To do this, complete the following procedure.
For information about targeting a RAR component, see " Connector Component-->Configuration-->General" in the WebLogic Server Administration Console Online Help.
For information about targeting Application View EJBs, see "Deploying a New EJB Module" in EJB in the WebLogic Server Administration Console Online Help.
For information about verifying Application View status, see "Listing and Viewing Application Views" in Application Integration in the Managing WebLogic Integration Solutions.
Adapter InstancesAdapter_Instance_IDEdit Event Connections).For more information about setting target lists for event connections, see "Changing Event Generation Targets" in Application Integration in the Managing WebLogic Integration Solutions.
After completing this procedure, Application View events should be coming from (if so configured) and Application View services should be invoked on the new managed server.
The procedure for changing an EIS instance is the same in both single-server and cluster environments. For information about changing an EIS instance, see Changing an EIS Instance.
The procedure for installing a new version of your application is the same in both single-server and cluster environments. For information about installing a new version of your application, see Installing a New Version of Your Application.
|