Skip navigation.

eDocs Home > BEA WebLogic Integration 8.5 Documentation > Deploying WebLogic Integration Solutions > Configuring a Single-Server Deployment

Deploying WebLogic Integration Solutions

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Configuring a Single-Server Deployment

This section describes the tasks that you must perform to configure WebLogic Integration for deployment in a single WebLogic Server environment.

To set up and deploy WebLogic Integration in a single-server configuration, complete the following steps:

 

Step 1. Configure a Database

Configure one of the following databases for your domain:

For detailed information regarding configuring databases for WebLogic Platform applications, see Configuring the Production Database in Deploying WebLogic Platform Applications.

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

You can configure your database to use concurrent access.

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 specific databases, see the WebLogic Integration 8.1 Release Notes.

 

Step 2. Prepare a WebLogic Integration Domain

To prepare a WebLogic Integration environment, complete the tasks described in the following sections:

Creating a WebLogic Integration Domain Using the Configuration Wizard

You begin the definition of a 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:

  1. From the Start Menu, choose Programs—>BEA WebLogic Platform 8.1—>Configuration Wizard.

    2. The Configuration Wizard is launched. It prompts you for data with which to configure your domain.

  2. Respond to the Configuration Wizard prompts by providing the information described in the following table.

    3. In this window . . .

    Perform the following action . . .

    Create or Extend a Configuration

    Select Create a new WebLogic configuration.

    Select a Configuration Template

    Select the Basic WebLogic Integration Domain template

    Choose Express or Custom Configuration

    Select Custom.

    Configure the Administration Server

    Accept all the default values.

    Note: When you configure the administration server, we recommend that you accept the default Server Name (cgServer), as prompted by the Configuration Wizard.

    Managed Servers, Clusters, and Machine Options

    Do you want to distribute your WebLogic configuration across managed servers, clusters and physical machines? Accept the default value (No).

    Note: A WebLogic Integration domain that includes an administrative server and one or more managed servers must include a cluster. A WebLogic Integration domain that includes an administrative server and one or more managed servers without a cluster is an unsupported configuration.

    Database (JDBC) Options

    Do you want to define JDBC components, such as Connection Pools, Data Sources, and MultiPools? Select Yes.

    Configure JDBC Connection Pools

    Configure the JDBC Connection Pools for WebLogic Integration.

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

    You can choose additional Connection Pools for application use.

    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.

    Note: WebLogic Integration may not be certified with all drivers. For a list of certified drivers, see "Supported Databases and Drivers" in Supported Configurations for WebLogic Platform in Supported Configurations.

    Assign JDBC Connection Pools to MultiPools

    Configure any Multipools needed by the application. Multipools are not required for the operation of WebLogic Integration itself.

    Configure JDBC Data Sources

    Accept the defaults for cgDataSource and bpmArchDataSource. Add any application-specific data sources.

    Note: No more than one non-XA datasource can be used in the same transaction. Data sources cannot share an XA JDBC connection pool.

    Test JDBC Connection Pools and Setup JDBC Database

    Optional test.

    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.

    Messaging (JMS) Options

    Do you want to define JMS components, such as Stores, Topics, and Queues? Select Yes.

    Note: Exercise caution in changing JMS option settings. Inappropriate settings may cause WebLogic Integration to function unpredictably.

    Configure JMS Connection Factories

    Accept the defaults for cgQueue and WLI-B2B System Topic Factory.

    Configure JMS Destination Key(s)

    Configure any keys needed for the application. None are needed for the operation of WebLogic Integration.

    Configure JMS Template(s)

    Configure any templates needed for the application. None are needed for the operation of WebLogic Integration.

    Configure JMS File Stores

    Accept the defaults for rmfilestore and add any file stores needed by the application.

    Configure JMS JDBC Store

    Select the appropriate connection pool from the list, then add any JDBC stores needed by the application.

    Configure JMS Servers

    WebLogic Integration System Queues can be mixed with Application Queues within the same JMS Server.

    Assign JMS Servers to WebLogic Servers

    Accept the defaults.

    Configure JMS Topics

    Accept the defaults, and add any user-defined topics.

    Configure JMS Queues

    Accept the defaults, and add any user-defined queues.

    Configure JMS Distributed Topics

    Accept the defaults, and add any user-defined distributed topics.

    Configure JMS Distributed Queues

    Accept the defaults, and add any user-defined distributed queues.

    Assign JMS Distributed Destinations to Servers or Clusters

    Accept the defaults.

    Configure JMS Distributed Topic Members

    Accept the defaults. There should be members for each configured managed server.

    Configure JMS Distributed Queue Members

    Accept the defaults.

    Applications and Services Targeting Options

    Do you want to target servers and clusters onto which Applications, JMS component services, JDBC component services, and other services are deployed? Select Yes.

    Target Applications to Servers or Clusters

    Accept the defaults.

    Target Services to Servers or Clusters

    Accept the defaults for non-XA data sources. Configure the appropriate target for XA data sources.

    For more information, see "Creating XA Domains Using Configuration Templates" in How Do I... in Creating WebLogic Configurations Using the Configuration Wizard.

    Configure Administrative Username and Password

    Select user names and passwords.

    Configure Windows Options

    Define operating system configuration information for Windows platforms.

    Note: Windows platform users only will encounter this page while using the Configuration Wizard. Configuring Windows options is not a requirement of a cluster domain configuration.

    Configure Server Start Mode and Java SDK

    Select Production Mode, and then select either the Sun SDK or JRockit SDK.

    Create WebLogic Configuration

    Select the name of your custom domain.


     

When you complete the domain configuration using the Configuration Wizard, your new domain is created in the location you specified.

Your WebLogic Integration domain includes two configuration files:

For more information about config.xml, see WebLogic Server Configuration Reference.

For information about wli-config.properties, see wli-config.properties Configuration File.

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.

Creating the Database Tables

When preparing a production environment (working in noniterativedev mode), you must create the WebLogic Integration database tables. For the procedure to create these tables, see "Creating the WebLogic Integration Tables" in Production Database in Managing WebLogic Integration Solutions.

For more information about conversational state database tables, 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.

 

Step 3. Configure WebLogic Integration Security

If you want to configure SSL for your domain, you can do so by using the WebLogic Server Administration Console. 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 Server

This section describes how to start, monitor, and shut down the server in your WebLogic Integration 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.

Starting the Server

To start the server, complete the following procedure:

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

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

  2. In the WebLogic Server Administration Console navigation tree, select the name the server.
  3. Select the Control tab.
  4. Click Start this Server.

    5. For more information about starting the server, see Starting and Stopping Servers in WebLogic Server Adminstration Console Online Help.

Monitoring and Shutting Down Your Server

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 server, see Monitoring a WebLogic Server Domain in Configuring and Managing WebLogic Server. For information about monitoring your WebLogic Integration domain, see "Run-Time Tuning Issues" in Performance Tips in the WebLogic Integration Solutions Best Practices FAQ.

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 Adminstration Console Online Help.

 

Step 5. Deploy a WebLogic Integration Application

Once you have configured and secured your WebLogic Integration domain and added the queues and database tables for your application to that domain, you can 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 them now using the WebLogic Server Administration Console.

Note: Async request and async request error queues, as well as database 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 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 Delay Override setting appropriately for wli.internal.egrdbms.queue. For the procedure to configure the Redelivery Delay Override, see RDBMS Event Generator.

You can update environment-specific information in your Application Views and adapter instances either before or after deploying your WebLogic Integration application:

For the procedure to deploy an EAR file, see "Configuring and Deploying a New Enterprise Application or Web Service" in Enterprise Applications in the WebLogic Server Administration Console Online Help. For a complete overview of the procedure to deploy a WebLogic Platform application, see Deploying WebLogic Platform Applications.

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 are available in the BEA dev2dev Code Library at the following URL:

http://dev2dev.bea.com/code/wli.jsp

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.

 

Step 6. Update Your Domain as Your Production Environment Changes

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.

Changing an EIS Instance

EIS instances are sometimes phased out, and new instances (possibly with new versions of EIS software, new hardware, and so on) are brought online. When this happens, WebLogic Integration administrators need to gracefully transition application views and adapter instances to the new EIS instance, and away from the old.

This situation is similar to an EIS instance failure, but not as urgent. In this case, you suspend the application views and adapter instances pointing at the old EIS instance, and then follow the instructions in EIS Instance Failover to point the application views and adapter instances to the new EIS instance.

Installing a New Version of Your Application

As your business requirements change, you may need to develop and deploy new versions of your WebLogic Integration application. To install a new version of your WebLogic Integration application, perform the following steps:

  1. Delete the application from WebLogic Server.
  2. Deploy the new version of the application.

You perform the preceding steps using the WebLogic Server Administration Console. For more information, see "Configuring and Deploying a New Enterprise Application or Web Service" in Enterprise Applications in the WebLogic Server Adminstration Console Online Help.

 

Skip navigation bar  Back to Top Previous Next