Setting the wlai.clusterFrontEndHostAndPort Property (Optional)

When you do not use a DNS name for your cluster address, you should set the wlai.clusterFrontEndHostAndPort property to achieve load balancing and high availability for event router callback communication.

Why Set the wlai.clusterFrontEndHostAndPort Property?

The following table describes the cluster configuration in a sample cluster, for which the cluster address is:

<Cluster ClusterAddress="127.0.0.1:7001,127.0.0.1:7002" Name="MyCluster"/> 

An event router uses obtains metadata about events by communicating with an instance of WebLogic Integration through HTTP. Exactly how such communication occurs is determined by whether or not the wlai.clusterFrontEndHostAndPort property is set:

How to Set the wlai.clusterFrontEndHostAndPort Property

You must create a wlai.clusterFrontEndHostAndPort property in the WLAIStartup EJB environment properties for each managed server. For example, to set wlai.clusterFrontEndHostAndPort=127.0.0.1:7003, complete the following procedure:

Step 2. Create a WebLogic Integration Domain

To complete this step, 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.

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.

To create a WebLogic Integration domain using the Configuration Wizard, complete the following steps:

When you complete the domain configuration using the Configuration Wizard, your new domain is created in the location you specified earlier. A configuration file (config.xml) is created in the domain. It contains a definition for the administration server and each managed server in the cluster, and it assigns the managed servers to the cluster.

Note: In the steps that follow in this procedure, you will edit the config.xml file to configure your clustered domain. Therefore, we recommend that before proceeding to the next step, you save a backup copy of the config.xml file created in this step.

Step 3. Configure the Database for Your Domain

The Database Wizard is a WebLogic Integration configuration utility that facilitates the task of setting up a database for the domain you created in the preceding step.

To run the Database Wzard:

Step 4. Configure BPM Resources for One Managed Server

You must modify your domain configuration to meet this requirement. You can do this in one of two ways:

Edit the Configuration File

The config.xml file in your domain contains comments to help you quickly identify and edit the elements that must be changed. Complete the following steps to make the required changes to the domain's configuration file:

Use the WebLogic Server Administration Console

If you start the administration server in your domain before making the changes described in the preceding table, comments that were written in the config.xml file are lost. However, if the comments are lost, you can still configure your system appropriately, by following the procedures described in the following sections:

Configure BPM Master EJB for One Managed Server

Note: The following procedure is provided for reference only. Use it, for example, if the comments in your config.xml file are lost before you complete the configuration.

To configure the BPM Master EJB for a single managed server:

After you complete the required modification, the WLI-BPM Plugin Manager EJB should be targeted to a single managed server in your cluster. The following excerpt shows the edited config.xml file, which illustrates the configuration change in the Targets attribute. In this example, the EJB is targeted to a managed server named manageserver-1.

Listing 3-1 Targeting WLI-BPM Plugin Manager to a Managed Server

<Application Name="WebLogic Integration" Deployed="false"
Path="C:/bea/weblogic700/integration/lib" TwoPhase="true">

...
<EJBComponent Name="WLI-BPM Plugin Manager" Targets="manageserver-1"
URI="wlpi-master-ejb.jar"/>

...
</Application>

Configure BPM Event Topic for One Managed Server

Note: The following procedure is provided for reference only. Use it, for example, if the comments in your config.xml file are lost before you complete the configuration.

To configure a BPM Event Topic for a single managed server:

The following listing is an excerpt from a config.xml file to which the BPM Event Topic is added to the JMSServer element for a managed JMS server. (In this case, the managed server is named WLIJMSServer_manageserver1.) The section of code being highlighted in this listing is shown in bold.

Listing 3-2 Configuration for com.bea.wlpi.EventTopic

<JMSServer Name="WLIJMSServer_manageserver1"
            Targets="manageserver1 (migratable)"
            TemporaryTemplate="TemporaryTemplate"
            Store="JMSWLIStore_manageserver1">

            <JMSTopic Name="wlpiEvent" JNDIName="com.bea.wlpi.EventTopic"/>

...
</JMSServer>

Step 5. Configure Event Router WAR File for Adapters

To change your configuration, you can use the WebLogic Server Administration Console, or you can edit the config.xml file in your domain.

Using the Administration Console

Using the config.xml File

The following listing is an excerpt from a sample config.xml file for a domain containing an administration server with clustered managed servers. It shows the event router WAR files for two adapters, configured such that they are deployed on a single managed server in the cluster. The WebAppComponent elements are shown in bold.

Listing 3-3 Configuring BEA_WLS_DBMS_ADK and BEA_POWERENTERPRISE_3_0 Adapters

<Application Deployed="true" Name="BEA_WLS_DBMS_ADK"
Path="<WLI_HOME>/adapters/dbms/lib/BEA_WLS_DBMS_ADK.ear" TwoPhase="true">

      <ConnectorComponent Name="BEA_WLS_DBMS_ADK"
                Targets="MyCluster" URI="BEA_WLS_DBMS_ADK.rar"/>

      <WebAppComponent Name="DbmsEventRouter" Targets="MyServer-1"
                URI="BEA_WLS_DBMS_ADK_EventRouter.war"/>

      <WebAppComponent Name="BEA_WLS_DBMS_ADK_Web"
                Targets="MyCluster" URI="BEA_WLS_DBMS_ADK_Web.war"/>

</Application>

 :

<Application Deployed="true" Name="BEA_POWERENTERPRISE_3_0"
Path="<WLI_HOME>/adapters/powerenterprise/lib/
BEA_POWERENTERPRISE_3_0_EAR.ear" TwoPhase="true">

      <ConnectorComponent Description="J2EE CA adapter for
                PowerEnterprise!" Name="BEA_POWERENTERPRISE_3_0"
                Targets="MyCluster" URI="BEA_POWERENTERPRISE_3_0.rar"/>

                <WebAppComponent Name="BEA_POWERENTERPRISE_3_0_EventRouter"
                Targets="MyServer-1"
                URI="BEA_POWERENTERPRISE_3_0_EventRouter.war"/>

                <WebAppComponent Name="BEA_POWERENTERPRISE_3_0_Web"
                Targets="MyCluster" URI="BEA_POWERENTERPRISE_3_0_Web.war"/>

</Application>

Step 6. Configure an RDBMS Realm

Listing 3-4 RDBMSRealm Element

<RDBMSRealm Name="wlpiRDBMSRealm"
            DatabaseDriver="com.pointbase.jdbc.jdbcUniversalDriver"
                      DatabasePassword="none"
                      DatabaseURL="jdbc:pointbase://localhost:9094/WLIDB"
                      DatabaseUserName="none" 

                      :
                      :

Step 7. Configure a Router

If you want to configure a software router based on the built-in WebLogic HttpClusterServlet, you can do so by uncommenting a predefined section in the config.xml file in your domain.

The config.xml file in your domain contains comments to help you quickly identify and edit the elements that must be changed. Complete the following steps to make the required changes to the domain's configuration file:

Note: When you configure a hardware or software router for your cluster, messages coming from outside the cluster should be sent to the URL of the router.

Step 8. Edit the startWeblogic Command File

You must edit the startWeblogic.cmd or startWeblogic.sh file in your domain to set the -Dweblogic.management.discover parameter to true:

Listing 3-5 Start Server Command for a WebLogic Integration Clustered Domain

REM Start weblogic

%JAVA_HOME%\bin\java %JAVA_VM% %JAVA_OPTIONS% -Xmx256m 
-classpath %SVRCP% 
-Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true
-Dwli.bpm.server.evaluator.supportsNull=false
-Dweblogic.management.username= -Dweblogic.management.password=
-Dweblogic.Name=adminserver
-Dweblogic.RootDirectory=%WLI_DOMAIN_HOME%
-Djava.security.policy=%WL_HOME%\lib\weblogic.policy
-Dweblogic.management.discover=true 
-Dweblogic.ProductionModeEnabled=%STARTMODE%  weblogic.Server

For a scenario in which the administration server is restarted while managed servers are running in your domain, the administration server can discover running managed servers when -Dweblogic.management.discover is set to true.

Step 9. Set Up Managed Servers for Your Domain

This step provides instructions for extending the domain you created by adding managed servers. To add a managed server to a domain, you must create the managed server and configure WebLogic Integration components on the server.

A WebLogic Integration domain can be set up in one of the following ways:

This section provides instructions for setting up managed servers in your cluster:

Both procedures explain how to add a managed server to a domain created with one of the templates provided with the Configuration Wizard.

Add a Managed Server to an Existing Installation

Complete the following steps to add a managed server to a WebLogic Integration domain:

Note: The procedures in this section are based on the assumption that your domain is named mydomain, and that it resides in the default location: BEA_HOME\user_projects.

Step 1. Create a New Managed Server

Step 2. Update the Domain Configuration for the New Managed Server (Optional)

You must add a managed server to the configuration for a domain before you can start that server. You may add a managed server to the domain configuration when you are creating the domain, or you may add it after a domain has been created. Therefore, this step is optional. Use the following guidelines to determine whether you need to complete it:

To update your domain configuration for a new managed server, complete the following procedure:

Add a Managed Server in a New Location

To add a managed server to a domain in which the administration server and the clustered managed servers reside on different machines, complete the following steps:

Step 1. Copy the Contents of Your Preconfigured Domain to the New Location

To set up a managed server in a new location, copy the contents of the domain directory you created to the new location, and modify them.

Complete the following procedure:

Note: If you set up a mixed cluster environment (that is, a cluster in which some instances of WebLogic Integration run on Windows systems and others run on UNIX systems), you may encounter a particular problem with carriage return characters. The carriage return character used in scripts run on Windows systems is ^M. Sometimes these characters remain in a file that is copied from a Windows system to a UNIX system. If the Windows carriage returns persist on a UNIX system, simply open the file and delete the ^M characters before running your script. You can do this using any text editor, or you can use the dos2unix command on Solaris systems. The dos2unix utility converts characters in the DOS extended character set to the corresponding ISO standard characters.

If you use FTP to transfer your ASCII files from a Windows system to a UNIX system, you can avoid this problem with carriage return characters by choosing the default ASCII mode.

Step 2. Modify the Contents of the Directory You Copied

Note: The following instructions are based on the assumption that you copied a domain directory named mydomain to the following location: BEA_HOME/user_projects.

To modify the contents of the directory you copied to the new location, delete all files and directories from BEA_HOME/user_projects, except those listed in the following table.

Step 3. Create a Managed Server

Step 4. Update the Domain Configuration for the New Managed Server (Optional)

You must add a managed server to the configuration for a domain before you can start that server. You may add a managed server to the domain configuration when you are creating the domain, or you may add it after a domain has been created. Therefore this step is optional.

Step 10. Configure WebLogic Integration for Automatic Restart

Whether WebLogic Integration is deployed in a clustered environment or a nonclustered environment, you can configure your system to automatically restart servers that have shut down because of a system crash, hardware reboot, server failure, and so on. You can do this by configuring the Node Manager in one of two ways:

Step 11. Configure WebLogic Integration for Migration from Failed to Healthy Node

Step 12. Configure WebLogic Integration Security

If you want to configure SSL for your cluster, you can do so by uncommenting predefined sections (one section in each Server element) in the config.xml file in your domain.

The config.xml file contains comments to help you quickly identify and edit the elements that must be changed. To configure SSL and modify the configuration file for your domain, complete the following procedure:

For a domain in which B2B integration functionality is deployed in a multinode cluster, you also need to configure keystores, server certificates, startWeblogic scripts, and so on, for every machine in a cluster.

For information about the tasks you must complete, see:

Warning: If your domain is based on the WLI Domain or EAI Domain template, and if you want to configure keystores for your domain, you must set the Deployed attribute in the WebLogic Integration Application element to false before you can configure keystores.

The following listing is an excerpt from a config.xml file for a WebLogic Integration domain, which shows the Deployed attribute set to false.

Listing 3-6 Setting the Deployed Attribute Before Configuring Keystores

<Application Name="WebLogic Integration" Deployed="false"
Path="C:/bea/weblogic700/integration/lib" TwoPhase="true">

Step 13. Start the Servers in the Domain

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

Before You Start the Servers

Complete the following procedure before you start the servers in your domain:

Starting Servers in a Domain for Which the Node Manager Is Not Configured

To start servers in a domain for which the Node Manager is not configured, complete the following procedure:

Starting Servers in a Domain for Which the Node Manager Is Configured

To start servers in a domain for which the Node Manager is configured, complete the following procedure:

Monitoring and Shutting Down Your Servers

When startup is complete, you can use the WebLogic Server Administration Console to verify deployments and status.