Getting Started


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

WLI Doc Home \| Starting, Stopping, and Customizing \| Previous Topic \| Next Topic \| Contents \| Index \| View as PDF

Getting Started

BEA WebLogic Integration is a single, unified platform that extends the core infrastructure and features of WebLogic Server to provide a comprehensive integration platform.

This section provides the information you need to get started with WebLogic Integration. It describes the WebLogic Server domains that are preconfigured to deploy WebLogic Integration resources, provides an overview of the components and passwords, and describes how to start WebLogic Integration in a preconfigured domain.

This section includes the following topics:

WebLogic Server Domains

A WebLogic Server domain is a collection of WebLogic Server resources managed as a single unit. A domain includes one or more instances of WebLogic Server and may include WebLogic Server clusters.

WebLogic Integration is a collection of applications and resources—EJBs, Web applications, JDBC connection pools, and so on—that are deployed in a domain to provide a unified platform for developing comprehensive e-business solutions.

Every WebLogic Server domain includes one and only one administration server; any other WebLogic Server instances in the domain are managed servers. Managed servers can be organized into clusters to simplify the task of deploying resources on a set of servers. The configuration for an entire domain is maintained on the administration server. A managed server obtains its configuration at startup from the administration server.

The configuration for a domain is defined in Extensible Markup Language (XML) and stored in a file named config.xml. This file is located in the following directory structure:

config/domain_name/config.xml

The config directory can be located under the WebLogic Server installation directory or elsewhere on the system. domain_name is the name of the domain. For convenience, the scripts required to start and stop an administration server are often located in the same directory as the config.xml file.

The administration server is the central point of control for an entire domain. The WebLogic Server Administration Console is a convenient, graphical interface used to carry out administrative tasks. Resource parameters, server instances, and deployments are defined in the config.xml file maintained by the administration server, through the WebLogic Server Administration Console.

For general information about the administration of WebLogic Server domains, see Overview of WebLogic Server Management in the BEA WebLogic Server Administration Guide.

The following section describes the preconfigured domains that are installed with WebLogic Integration. These preconfigured domains can serve as your starting point for working with the WebLogic Integration samples provided, or for developing and testing your own WebLogic Integration solutions.

WebLogic Integration Preconfigured Domains

When you install WebLogic Integration, the following preconfigured domains are created and configured:

WebLogic Integration domain
This domain is configured to support the development of solutions that employ the full range of WebLogic Integration functionality. WebLogic Integration functionality associated with application integration, data integration, business process management (BPM), and B2B integration are supported in this domain.
Enterprise application integration domain
This domain is configured to support the development of enterprise application integration solutions. The WebLogic Integration functionality associated with BPM, application integration, and data integration are supported in this domain.
BPM domain
This domain is configured to support the development of business process management solutions. The WebLogic Integration functionality associated with BPM and data integration are supported in this domain.

These preconfigured domains support three of the most common WebLogic Integration development environments. Typically, one of these preconfigured domains will meet your evaluation, development, and testing needs.

If you selected the WebLogic Integration Full Installation with Samples option during installation, a samples domain is also created to run the WebLogic Integration samples. All WebLogic Integration functionality is supported in this domain. In addition, Web applications, custom JMS queues, and other resources required to run the samples are configured.

Each of the preconfigured and sample domains share the following characteristics:

By default, each domain contains a single WebLogic Server instance. This is the administration server for the domain.

Note: For information about adding managed servers, and deploying WebLogic Integration in a clustered environment, see Deploying BEA WebLogic Integration Solutions.
The default listen port is 7001.
The JDBC connection pool required to connect to your database is configured based on the database information you provided during installation.
A default RDBMS security realm is configured to use the same database.

As you become more familiar with WebLogic Integration, you can use a preconfigured domain as the starting point for development and testing, or you can create your own domain by modeling it after one of the preconfigured domains.

Each of the domains described in this section is located under the WebLogic Integration installation directory. Table 1-1 shows the location of each domain when the product is installed in the default location.

Table 1-1 WebLogic Integration Preconfigured Domains

Domain	Location
WebLogic Integration	BEA_HOME/wlintegration2.1/config/wlidomain
Enterprise Application Integration	BEA_HOME/wlintegration2.1/config/eaidomain
Business Process Management	BEA_HOME/wlintegration2.1/config/bpmdomain
Samples	BEA_HOME/wlintegration2.1/config/samples This domain is installed only if you select the WebLogic Integration Full Installation with Samples option during installation.

A copy of each of the following files is provided in each preconfigured domain directory. These files control the initial deployment and configuration of the WebLogic Integration resources and applications for the domain:

config.xml file—XML document that describes the configuration of an entire WebLogic Server domain. The resources deployed in the domain are controlled by the config.xml file.
Start command—Command that starts the administration server for the domain. The command is platform specific: each domain directory contains either a startWeblogic.cmd file (Windows) or a startWeblogic file (UNIX).
Stop command—Command that gracefully shuts down the administration server for the domain. The command is platform specific: each domain directory contains either a stopWeblogic.cmd file (Windows) or a stopWeblogic file (UNIX).
fileRealm.properties—File in which the User, Group, and ACL objects that are created when WebLogic Server is started are stored. The file realm is the default security realm in a WebLogic Server environment.
wlai.properties—File that sets properties required to support application integration functionality. This file is located in the wlai subdirectory of any domain that supports application integration. For example, in the WebLogic Integration domain the file is config/wlidomain/wlai/wlai.properties.

An example of each of these files is provided in WebLogic Integration Sample Configuration Files.

In addition to the commands described here, a number of others are used to set up the WebLogic Integration environment. These commands are described in WebLogic Integration Commands.

When you start WebLogic Server by executing the startWebLogic command for one of the preconfigured domains (as described in Starting WebLogic Integration), the WebLogic Integration resources configured for the domain are deployed.

Administration and Design Tools

As described in Introducing BEA WebLogic Integration, WebLogic Integration includes the following design and administration tools:

WebLogic Server Administration Console
The WebLogic Server Administration Console is used to manage the WebLogic Integration resources (applications, EJBs, services, and so forth) deployed on WebLogic Server.
Application View Console
Application views provide a critical layer of abstraction between the technical implementation of an adapter built with the WebLogic Integration ADK (Adapter Development Kit) and the business data and capabilities of the target application. The Application View Console allows you to access and control adapter resources.
WebLogic Integration Studio
The Studio is a graphical interface application that facilitates process modeling by making it easy for you to define the actions (tasks, events, and decisions) required to implement the business rules for a process. Actions can invoke applications, interface with human operators, transform data formats, send and receive XML messages, send e-mail, and so on. The Studio allows you to organize actions, using drag-and-drop, into workflows based on a familiar flow-chart paradigm.
WebLogic Integration Worklist
The Worklist is a graphical application that operates in conjunction with the process engine to notify users of workflow tasks that require action on their part. The Worklist provides workflow developers a convenient way to incorporate user transactions into their workflows.
WebLogic Integration Format Builder
Data translation is an integral part of almost any enterprise application integration solution. XML is quickly becoming the standard for exchanging information between applications. The Format Builder application is a tool for creating Message Format Language (MFL) files (or message formats) that describe the content and structure of the binary data already used in your organization. In conjunction with the data integration plug-in, these message formats are used by the WebLogic Integration process engine to translate binary data to XML, and vice versa.
WebLogic Integration B2B Console
The B2B Console is a graphical tool that allows you to define, export, or import the elements required for trading exchange, supply chain management, and collaborative commerce applications. The B2B Console is also used to monitor the state of the B2B engine, trading partner sessions, delivery channels, and other elements involved in an active exchange.

In WebLogic Integration Administration and Design Tools, you will find:

Instructions for starting each tool
References to the information required to use each tool

About the WebLogic Integration Repository

The WebLogic Integration repository is the database that maintains the information required by WebLogic Integration. The following tables make up the repository.

Table 1-2 WebLogic Integration Repository Tables

This set of tables . . .	Contains . . .
Common tables (also known as the XML repository)	XML, DTDs, XLST style sheets, and other entities used by WebLogic Integration
Workflow tables	Static workflows and dynamic run-time information
JMS queue tables	Message state (dynamic)
B2B configuration tables	Static configuration information required to support B2B integration. For more information about the data stored in these tables, see Working with the Repository in Administering B2B Integration.
Persistence tables	Persistence state (dynamic)

For the information required to initialize the repository for a domain, see Domain Configuration Requirements.

WebLogic Integration Users and Passwords

The following users and passwords are configured when you install the product.

Table 1-3 Default User Names and Passwords

User Name	Default Password	Description	Update Considerations
system	security	Login used to: Boot WebLogic Server Access the WebLogic Server Administration Console Access the B2B Console Access the Application View Console	Update this password from the WebLogic Server Administration Console.
wlcsystem	wlcsystem	Internal login used by the B2B Engine.	Update this password only from the B2B Console. Warning: Do not update this password using the WebLogic Server Administration Console.
wlpisystem	wlpisystem	Internal login used by the process engine.	Warning: Do not update this password.
admin	security	Default BPM logins are used to log on and connect to the process engine or XML repository from the WebLogic Integration Studio, Worklist, and Format Builder clients.	Update (add or delete) user names from the Studio. Update an existing user password from the WebLogic Server Administration Console.
mary	password
joe	password

To ensure system security, you can change the default passwords, as described in Updating Passwords.

When you install WebLogic Integration, a default fileRealm security realm is configured. The fileRealm.properties file reflects the initial configuration of this security realm. In addition to the fileRealm (which always exists) a default RDBMSRealm is also available to support BPM security. For additional information about the BPM security model, and instructions for enabling the RDBMSRealm or setting up an alternate BPM security realm, see Understanding the BPM Security Model.

Security issues related to WebLogic Integration B2B functionality are discussed in Implementing Security with B2B Integration.

Domain Configuration Requirements

Before you can start WebLogic Integration in a preconfigured domain, you must configure the database repository for the domain appropriately. When you install WebLogic Integration, you must specify the access information required to connect to the following two databases:

Samples database
The access information provided during installation is used to configure the JDBC connection pool and the RDBMSRealm security realm for the samples domain. The JDBC and RDBMS configuration for the specified database is defined in the config.xml file for the domain.
Production database
The access information provided during installation is used to configure the JDBC connection pool and the RDBMSRealm for the WebLogic Integration domain (config\wlidomain), enterprise application integration domain (config\eaidomain), and BPM domain (config\bpmdomain). The JDBC and RDBMS configuration for the specified database is defined in the config.xml file for each of these domains.

Typically, you will be using only two of the domains described here: the samples domain and the preconfigured production domain that most closely meets your development and testing requirements. In such cases you need to configure only two domains.

If you plan to use more than one of the preconfigured production domains, you may want to specify a different database for the additional production domain you will use. Although sharing a database may not be problematic, we recommend that you keep the data for different domains segregated in discrete databases.

For example, if you plan to use the WebLogic Integration domain as your primary development and testing domain, and the BPM domain as your secondary development and testing domain, you may want the BPM domain to use a database other than the production database specified during installation.

The WebLogic Integration database configuration wizard automates the process of updating the configuration for a domain. The procedure for updating to a new database is described in Specifying a New Database for a Domain.

Before you can start WebLogic Integration in a given domain, you must initialize the database for the domain. Some database configuration tasks are required by all domains; others are domain-specific. The following table summarizes the requirements for all domains.

Table 1-4 Database Configuration Requirements

Task ID	Database Configuration Task	Required for
1	Create the following repository tables: Common tables (also known collectively as the XML repository)—Set of database tables that store XML, DTDs, XLST style sheets, and other entities used by WebLogic Integration Workflow tables—Set of database tables that store static workflows and dynamic run-time information JMS Queue tables—Set of database tables that store the message state (dynamic)	All preconfigured domains: config\samples config\wlidomain config\eaidomain config\bpmdomain
2	Populate the common tables with the required data (for example XML schemas).	All preconfigured domains: config\samples config\wlidomain config\eaidomain config\bpmdomain
3	Create the following repository tables: B2B configuration tables—Set of database tables that contain the static information required to configure your environment for B2B integration. The data stored in these tables is discussed in Working with the Repository in Administering B2B Integration. Persistence tables—Set of database tables in which the persistence state is stored. (dynamic)	config\samples config\wlidomain
4	Load the system data required to support the WebLogic Integration B2B functionality. Each supported business protocol requires the following: Business protocol definition Set of system logic plug-in definitions	config\samples config\wlidomain
5	Load the configuration data and workflows required by the samples.	config\samples
6	Configure the application view for the End-to-End sample application.	config\samples

Configuring the Database for a Domain

The WebLogic Integration database configuration wizard is a tool that enables you to automate database configuration tasks. The wizard provides the following options:

Switch Database
This option prompts you to specify a database type and provide other information required to access the database. The wizard updates the JDBC connection pool and RDBMSRealm configurations in the config.xml file for the domain. It also updates the domain-specific environment settings used by the wizard to create the database.
Create Database
This option creates the tables required by the domain and loads data appropriate to the domain. For example, for the WebLogic Integration domain, the command performs Tasks 1, 2, 3, and 4 (described in Table 1-4). For the BPM domain, this option performs Tasks 1 and 2. Before creating the required tables, this option also prompts for database access information. The current settings are displayed; you can accept them, or you can specify the information required to connect to and initialize a different database. In other words, this command can be used to both switch and initialize the database for a domain.

Note: Although the WebLogic Integration database configuration wizard is available for the samples domain, the Create Database option does not complete tasks 5 and 6 for the samples domain. In order to use the samples domain, you must set up and start the server in the samples domain by executing the RunSamples command. See the following section, Configuring and Starting the Samples Domain.
Migrate Database
This option updates a selected WebLogic Integration 2.0 database, as required, to work with WebLogic Integration 2.1. For information about migrating from WebLogic Integration 2.0 or a previous release, see Migrating to BEA WebLogic Integration Release 2.1.

Before starting WebLogic Integration in the WebLogic Integration domain, enterprise application integration domain, or BPM domain, as described in Starting WebLogic Integration, you must use the WebLogic Integration database configuration wizard to create and initialize the required database. For instructions, see Using the Database Configuration Wizard.

The information you need to set up and start the samples domain is described in the following section.

Configuring and Starting the Samples Domain

When you execute the RunSamples.cmd (Windows) or RunSamples (UNIX) command for the first time after installing WebLogic Integration, or after you have switched the samples domain to a new database, the command performs the following tasks:

Creates the required repository tables in the database. See Table 1-4.
Loads the system data and sample configuration data required for B2B integration
Starts WebLogic Integration in the samples domain
Configures the application view for the WebLogic Integration sample application
Imports the workflow package containing the sample workflows
Launches your default Web browser and displays the samples launcher page

Note: To successfully display the samples launcher page, your Web browser must meet the requirements described in Web Browser Configuration Requirements.

Execute the RunSamples command by performing the steps appropriate for your platform:

On Windows:

Choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Samples—>Run Samples.
On UNIX:
1. Go to the samples/bin directory (under the WebLogic Integration installation directory).
2. Execute the RunSamples command.
  Example: If WebLogic Integration is installed in the default location, enter the following commands:
  cd BEA_HOME/wlintegration2.1/samples/bin
  . ./RunSamples

When the RunSamples command is executed on a Windows system, a command window is opened. On both Windows and UNIX platforms, command progress and messages are displayed in a command window. Several minutes may be required for all tasks to complete. When the command has completed, the following actions occur:

The following message is displayed in the command window:

Trailer:
REM
REM
==============================================================
REM The program will stop when the server is shut down
REM WARNING: Killing this command will kill the server too!!!
REM ======================================================+=======
REM

RunSamples execution successful

Your default Web browser is launched, and the samples launcher is displayed.

The RunSamples command both configures the samples database as required, and starts WebLogic Integration in the samples domain (the server is booted in the background). After you execute the RunSamples command for the first time, and the database is properly configured, you can start WebLogic Integration in the samples domain in either of the following ways:

Start WebLogic Integration normally, as described in Starting WebLogic Integration. After the server starts, you can view the samples launcher page as described in Starting the Samples Launcher.
Execute the RunSamples command again.
When you execute the RunSamples command after the samples database is properly configured, you are prompted with the following message:
The WebLogic Integration repository has already been created
and populated, possibly from a previous run of this RunSamples
script. Do you want to destroy all the current data in the
repository and create and populate the WebLogic Integration
repository, again?
Y for Yes, N for No
If you answer N to this prompt, the RunSamples command skips the steps for creating and populating the repository and runs only the steps for booting the WebLogic Server in the samples domain and displaying the samples launcher page in your Web browser.

If you answer Y to this prompt the RunSamples command recreates and repopulates the repository. It then boots WebLogic Server and displays the samples launcher page in your Web browser. When you answer Y the RunSamples command destroys all the data currently in the repository and reloads the sample data into the repository. Answer Y only when the current sample data has been altered or removed and you want a fresh or unaltered version of the sample data in the repository.

Note: If you quit the browser while the server is still running, you can display the samples launcher page as described in Starting the Samples Launcher.

Starting WebLogic Integration

As described in WebLogic Integration Preconfigured Domains, when you execute the startWeblogic.cmd (Windows) or startWeblogic (UNIX) command for a domain, WebLogic Server is started, and the WebLogic Integration applications and resources specified in the config.xml file for the domain are deployed on the server.

The following sections provide instructions for executing the start command on a Windows or UNIX system.

Starting WebLogic Integration on Windows

On a Windows system, you can start WebLogic Integration through menus or from the command line.

Note: If you are already running an instance of WebLogic Server that uses the same listen port as the one to be used by the server you are starting, you must stop the first server before executing the start command.

Starting WebLogic Integration Through Menus

To start WebLogic Integration using menus, do one of the following:

To start the server in the WebLogic Integration domain (config\wlidomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Start Server.
To start the server in the enterprise application integration domain (config\eaidomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Additional Preconfigured Domain—>EAI Domain—>Start Server.
To start the server in the BPM domain (config\bpmdomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Additional Preconfigured Domain—>BPM Domain—>Start Server.
To start the server in the samples domain (config\samples), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Samples—>Start Server.

Note: The first time you start WebLogic Integration in the samples domain, use the RunSamples command, as described in Configuring and Starting the Samples Domain.

A command window is launched, and startup messages are displayed. When the messages described in Startup Complete Messages are displayed, startup has completed successfully.

Starting WebLogic Integration from the Command Line

To start WebLogic Integration from the command line:

Choose Start—>Run.
Enter cmd in the Open text box and click OK.
In the command window, go to the directory for the appropriate domain.
For example, if WebLogic Integration is installed in the default location, and you want to start the WebLogic Integration domain, enter the following:
cd \bea\wlintegration2.1\config\wlidomain
For the default location of each preconfigured domain, see WebLogic Integration Preconfigured Domains.
Start the server by entering:
```
startWeblogic
```

When the messages described in Startup Complete Messages are displayed, startup has completed successfully.

Starting WebLogic Integration on UNIX

To start WebLogic Integration on a UNIX system:

Go the directory for the appropriate domain.
For example, if WebLogic Integration is installed in the default location, and you want to start the WebLogic Integration domain, enter the following:
cd BEA_HOME/wlintegration2.1/config/wlidomain
For the default location of each preconfigured domain, see WebLogic Integration Preconfigured Domains.
Start the server by entering:
```
. ./startWeblogic
```

When the messages described in the following section are displayed, startup has completed successfully.

Startup Complete Messages

When the following messages are displayed, WebLogic Integration has started successfully:

<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice> 
<WebLogicServer> <ListenThread listening on port 7001>
<Oct 1, 2001 10:04:17 AM EDT> <Notice> <WebLogicServer> 
<Started WebLogic Admin Server "myserver" for domain "domain_name" 
running in Development Mode>Initialized WebLogic Integration Plugin Framework version 1.0
Started WebLogic Integration - BPM Server version 2.1

Depending on the configuration of the domain, additional messages may be displayed.

To shut down WebLogic Integration gracefully, run the stopWebLogic command, as described in Stopping WebLogic Integration on Windows. Do not stop the server by closing the command window or by pressing Ctrl+c.

Stopping WebLogic Integration

You can stop your entire WebLogic Integration system—WebLogic Server and all the WebLogic Integration applications and resources deployed in a preconfigured domain—by executing the stopWeblogic.cmd (Windows) or stopWeblogic (UNIX) command located in the domain directory. The following sections provide instructions for executing the stop command on a Windows or UNIX system.

Stopping WebLogic Integration on Windows

The following sections provide instructions for stopping WebLogic Integration through menus or from the command line.

Stopping WebLogic Integration Through Menus

To stop WebLogic Integration using menus, do one of the following:

To stop the server in a WebLogic Integration domain (config\wlidomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Stop Server.
To stop the server in an enterprise application integration domain (config\eaidomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Additional Preconfigured Domain—>EAI Domain—>Stop Server.
To stop the server in a BPM domain (config\bpmdomain), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Additional Preconfigured Domain—>BPM Domain—>Stop Server.
To stop the server in a samples domain (config\samples), choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Samples—>Stop Server.

A command window opens briefly. It displays a message indicating that a shutdown request has been sent to the server. Shutdown progress messages are then displayed in the original command window, as shown in the following figure. When you are returned to the command prompt, shutdown is complete.

Figure 1-1 Shutdown Sequence Messages

Once WebLogic Server and all applications are terminated, you can restart WebLogic Integration, as described in Starting WebLogic Integration on Windows.

Stopping WebLogic Integration from the Command Line

To stop WebLogic Integration from the command line:

Choose Start—>Run.
Enter cmd in the Open text box, and then click OK.
In the command window, go to the directory for the appropriate domain.
For example, if WebLogic Integration is installed in the default location, and you want to start the WebLogic Integration domain, enter the following:
cd \bea\wlintegration2.1\config\wlidomain
For the default location for each preconfigured domain, see WebLogic Integration Preconfigured Domains.
Stop WebLogic Integration by entering:
```
stopWeblogic
```
Shutdown messages are displayed, as shown in Figure 1-1.

Stopping WebLogic Integration on UNIX

To stop WebLogic Integration on a UNIX system:

Go the directory for the appropriate domain.
For example, if WebLogic Integration is installed in the default location, and you want to stop the WebLogic Integration domain, enter the following:
cd BEA_HOME/wlintegration2.1/collaborate/config/wlidomain
For the default location of each preconfigured domain, see WebLogic Integration Preconfigured Domains.
Stop WebLogic Integration by entering:
```
. ./stopWeblogic
```
Shutdown messages are displayed, as shown in Figure 1-1.

Next Steps

To learn how to start each of the WebLogic Integration administration and design tools, see WebLogic Integration Administration and Design Tools.

We highly recommend that you explore the sample applications. This is one of the best ways to learn how you can use WebLogic Integration to connect Web applications, databases, enterprise information systems, processes, and business partners.

If you have not already done so, we recommend that you:

Configure the samples domain as described in Configuring and Starting the Samples Domain.
Run the WebLogic Integration sample application.

The WebLogic Integration sample (listed as "WLI sample" on the samples launcher page), showcases how you can use many of the features of WebLogic Integration to integrate existing systems, streamline complex business processes, and connect business partners. Learning to Use BEA WebLogic Integration guides you through this example.