> Deploying WebLogic Integration Solutions
> Configuring a Single-Server Deployment

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

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.
Note: 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 9.2 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 All ProgramsArrow symbolBEA ProductsArrow symbolToolsArrow symbolConfiguration Wizard.

    2. This displays the Welcome page in the BEA WebLogic Configuration Wizard dialog box (see Figure 2-1).

    Figure 2-1 Configuration Wizard Welcome Page


    Configuration Wizard Welcome Page

  2. Select Create a new WebLogic domain and click Next. This displays the Select Domain Source page in the Configuration Wizard dialog box.

    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 2-1 lists the pages and the options that you need to select to create the domain successfully.

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

    4. Table 2-1 Configuring the Domain Using the Configuration Wizard
    Page in the Configuration Wizard Dialog Box
    Recommendation Action
    Select Domain Source
    Select Generate a domain configured automatically to support the following BEA Products option for the following BEA Products:
    • WebLogic Server (Required)
    • WebLogic Integration
    Click Next to proceed.
    Configure Administrator Username and Password
    Specify the following mandatory credentials:
    User name = weblogic
    User password = weblogic
    Confirm user password = weblogic
    Click Next to proceed.
    Configure Server Start Node and JDK
    Select Development Mode in the WebLogic Domain Startup Mode column.
    Select Sun SDK 1.5.0_04 @ <BASE Directory>:\bea\jdk150_04 in the BEA Supplied JDKs column.
    Click Next to proceed.
    Customize Environment and Service Settings
    Click Yes, to configure the settings defined in the domain source.
    Click Next to proceed.
    Configure the Administration Server
    Accept all the default values and click Next.

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

    Configure Managed Servers
    If you want to distribute your WebLogic configuration across managed servers, click Add, enter a name and the required configuration details.
    Click Next.
    Configure Clusters
    If you want to distribute your WebLogic configuration across managed clusters, click Add, enter a name and the required configuration details.
    Click Next.
    Configure Machines
    If you want to distribute your WebLogic configuration across physical machines, click Add, enter a name and the required configuration details.
    Click Next.
    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.

    Database (JDBC) Options
    Do you want to define JDBC components, such as Connection Pools, Data Sources, and MultiPools? Select Yes.
    Run Database Scripts
    Click on cgDataSource-nonXA in the Available JDBC Database Scripts, select all the SQL scripts from the Available SQL Files and Database Loading Options and click Run Scripts.
    Perform the above procedure for p13nDataSource in the Available JDBC Database Scripts.
    Click Next.
    Configure JMS File Stores
    Accept the defaults and add any file stores needed by the application.
    Click Next.
    Review WebLogic Domain
    This page gives detail of your domain, click Next.
    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>\bea\user_projects\domains
    • Application Location: <Base Directory>\bea\user_projects\applications
    After the domain is created successfully, the Creating Domain page is displayed
    Select the Start Admin Server check box and click Done to proceed.

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 Understanding Domain Configuration.

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

For information about configuring domains, see "Setting Up WebLogic Domains" in BEA Products Installation and Configuration Documentation.

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 Configuring a 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 Security.

 

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 and Stopping Servers: Quick Reference.

Starting the Server

To start the server, complete the following procedure:

From the Start Menu, choose All ProgramsArrow symbolBEA ProductsArrow symbolUser ProjectsArrow symbolDomain NameArrow symbolAdmin Server Console.

For more information about starting the server, see Starting and Stopping Servers: Quick Reference.

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

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 Control graceful shutdowns.

 

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


  Back to Top       Previous  Next