Deploying WebLogic Integration Solutions

     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 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.

 

Step 1. Comply with Configuration Prerequisites

This section describes prerequisites for configuring Oracle WebLogic Integration to run in a clustered environment:

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.

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

 

Step 2. Prepare the WLI Domain

You begin the definition of a WLI deployment by creating a domain using the Domain Configuration Wizard.

Note: The procedure described in this section for setting up your domain is based on the assumption that you are running the Domain Configuration Wizard in GUI mode from the Windows Start menu. For information about using the Domain Configuration Wizard in different modes, see Creating WebLogic Domains Using the Configuration Wizard.

To create a WLI domain using the Domain Configuration Wizard, complete the following steps:

  1. From the Start Menu, choose All ProgramsArrow symbolOracle WebLogic Arrow symbolWebLogic Server 10gR3 Arrow symbolToolsArrow symbolConfiguration Wizard.

    2. The Welcome page of the Oracle WebLogic Configuration Wizard appears.

  2. Select Create a new WebLogic domain and click Next. The Select Domain Source page appears.

    3. 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.

    Table 4-1 Configuring the Domain Using the Configuration Wizard
    Page in the Configuration Wizard Dialog Box
    Action
    Select Domain Source
    Select Generate a domain configured automatically to support the following Products, and select the following products:
    • WebLogic Server (Required)
    • WebLogic Integration
    Configure Administrator Username and Password
    Specify the username and password.
    Configure Server Start Mode and Java JDK
    Select Production Mode, and then select either the Sun SDK or Oracle SDK.
    Note: When running Oracle WebLogic Integration in a cluster with Oracle JRockit, the JVM may report a Stack Overflow. If not addressed, the problem can eventually result in a JVM core dump. To prevent the stack overflow issue, you must set the Thread Stack Size parameter appropriately.
    Note: If the thread stack size has not been set, the default value depends on the threading system and the platform on which Oracle JRockit is running:
    • 32-bit Default
      On either Windows or Linux IA32 machines, the default thread stack size values for native threads are:
      Win32: 64 kB
      Linux32: 128 kB
    • 64-bit Default
      On either Windows or Linux IA64 machines, the default thread stack size values for native threads are:
      Win64: 320 kB
      Linux64: 1 MB
    Customize Environment and Service Settings
    Select Yes, to configure the settings defined in the domain source.
    Configure RDBMS Security Store Database
    Choose to create, change or remove RDBMS support or retain the template settings. You can specify the database type, driver, class name, user credentials, and connection details.
    Create the RDBMS tables in your datastore prior to booting your domain. The scripts required by a Database Administrator are available in server/lib directory of Oracle WebLogic Server.
    Configure the Administration Server
    Select or enter the administration server machine name or IP address for the Listen address.

    Note: When you configure the administration server, we recommend that you accept the default server name (AdminServer).

    Configure Managed Servers
    Add as many managed servers as required.

    Note: If you need a HTTP router for load balancing, add it here.
    Configure Clusters
    Add a cluster and define the multicast address.
    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: WLI is intended to work with no more than one WLI cluster per domain. The domain can also include a Oracle WebLogic Server cluster.
    Assign Servers to Clusters
    Add all of 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.
    Configure Machines
    Configure the type of physical machines used in the cluster.
    Assign Servers to Machines
    Assign each instance of Oracle WebLogic Server to the machine in the cluster on which it runs.

    Note: For information about creating a multi-node cluster (different managed servers on different machines) see “Creating and Starting a Managed Server on a Remote Machine: Main Steps” in Creating Templates and Domains Using the pack and unpack Commands.
    Configure JDBC Data Sources
    Configure each data source with information about the database that you want to use.
    Run Database Scripts
    Run the scripts in the cgDataSource-nonXA and p13nDataSource data sources.
    Configure JMS File Stores
    Define configuration settings for the JMS file stores.
    Review WebLogic Domain
    Review the selections you made so far.
    Create WebLogic Domain
    On the Create WebLogic Domain page, specify the following values for each field and click Create:
    • Domain name: Give a domain name
    • Domain Location: <Base Directory>\user_projects\domains
    • Application Location: <Base Directory>\user_projects\applications
    After the domain is created successfully, select the Start Admin Server check box and then select Done.

Editing Domain Configuration Files

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.

Adding Proxy Server or Firewall Information to Domain Configuration

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:

  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.

 

Step 3. Configure Oracle WebLogic Integration Security

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:

 

Step 4. Start and Monitor the Managed Servers in the Domain

This section describes how to start the servers in your clustered domain:

Starting the Managed Servers

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>
  1. If you have not done so already, start the Node Manager on each machine that hosts managed servers.

    2. For information about starting the Node Manager, see Node Manager Administrator's Guide.

  2. If you have not done so already, start the Oracle WebLogic Server Administration Console.

    3. 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.

  3. In the Oracle WebLogic Server Administration Console navigation tree, select the name of each managed server, in turn.
  4. Select the Configuration tab, and then select the Remote Start tab. Set the properties for Node Manager to use for the managed server.

    5. For information about the setting the properties for Node Manager use, see Starting and Stopping Servers in Oracle WebLogic Server Administration Console Online Help.

  5. Select the Control tab.
  6. Click Start this Server.

    7. 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.

Monitoring and Shutting Down Your Servers

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.

 

Step 5. Deploy a WLI Application

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.

  Back to Top       Previous  Next