| Download Docs | Site Map | Glossary | |
|
|
|||
| bea.com | products | dev2dev | support | askBEA |
|
|
|
|||||||
 |
| e-docs > WebLogic Platform > WebLogic Integration > Starting, Stopping, and Customizing > Getting Started |
|
Starting, Stopping, and Customizing
|
Getting Started
BEA WebLogic Integration extends the core infrastructure and features of WebLogic Server to provide a complete solution for developing, deploying, and integrating applications and business processes from within and across the enterprise.
This section provides the information you need to get started with WebLogic Integration. It explains how to configure a WebLogic Server domain to deploy WebLogic Integration resources. It also provides an overview of the components and passwords, and it describes how to start WebLogic Integration in a sample or custom 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:
domain/config.xml
The name of the directory (that is, the value of domain) is the name of the domain, which can be located anywhere on your system. 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 sections describe the WebLogic Integration samples domain and the WebLogic Integration configuration templates that can be used with the BEA Configuration Wizard to create custom domains. The samples domain can be used to explore the capabilities and features demonstrated in the sample applications.
As the starting point for developing and testing your own WebLogic Integration solutions, we recommend using a custom domain based on one of the configuration templates provided with WebLogic Integration.
WebLogic Integration Samples Domain
A samples domain is created in which you can run the WebLogic Integration sample applications if you performed one of the following sets of tasks during installation:
All WebLogic Integration functionality is supported in the samples domain. In addition, Web applications, custom JMS queues, and other resources required to run the samples are configured.
The WebLogic Integration samples domain is configured as follows:
Note: For information about adding managed servers and deploying WebLogic Integration in a clustered environment, see Deploying BEA WebLogic Integration Solutions.
The samples domain directory also contains several files used to control the deployment and configuration of WebLogic Integration resources and applications for the domain:
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.
WebLogic Integration Configuration Templates
The BEA Configuration Wizard, which is described in Using the Configuration Wizard, is a tool that can be used to create new WebLogic Server domains. The servers included in a domain created with the Configuration Wizard, and the resources—EJBs, Web applications, JDBC connection pools, and so on—that are deployed on each server, depend on the Configuration Wizard template you select and your responses to the Configuration Wizard prompts.
When you install WebLogic Integration as part of BEA WebLogic Platform, the Configuration Wizard templates described in the following table are available for use with the Configuration Wizard.
These templates support the creation of the three most commonly used WebLogic Integration development environments. In most situations, you can expect a domain created with one of these templates to meet your evaluation, development, and testing needs.
Detailed information about each template is provided in Configuration Wizard Template Reference.
As described in Using the Configuration Wizard, when you use the Configuration Wizard to set up the domain configuration stored on the server, you are prompted to assign a domain name (domain) and to specify the location in which the domain directory will be installed. The files required by the server are installed in the specified location under the domain directory.
For example, if you accept the default location, BEA_HOME/user_projects, the files required by the administration server are installed in the following directory:
BEA_HOME/user_projects/domain
By convention, DOMAIN_HOME is used to indicate this complete path to the root of a domain.
Like the WebLogic Integration samples domain, the following files are required by the administration server in a domain created using one of the WebLogic Integration domain templates:
An example of each of these files is provided in WebLogic Integration Sample Configuration Files.
Depending on the template you select to create the domain, additional commands may be included. For a complete description of the files and commands installed by each template, see Configuration Wizard Template Reference. For a description of the available WebLogic Integration commands, see WebLogic Integration Commands.
As you become more familiar with WebLogic Integration, you can customize a domain created with the Configuration Wizard, as described in Creating and Customizing a New Domain.
Administration and Design Tools
As described in Introducing BEA WebLogic Integration, WebLogic Integration includes the following design and administration tools:
Note: The Worklist client application is deprecated as of this release of WebLogic Integration. For information about the features that are replacing the Worklist, see the BEA WebLogic Integration Release Notes.
In WebLogic Integration Administration and Design Tools, you will find:
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.
For the information required to initialize the repository for a domain, see Domain Configuration Requirements.
WebLogic Integration Users and Passwords
Default users and passwords are configured in two domains:
Table 1-2 describes these users and passwords.
To maximize system security, you can change the default passwords, as described in Updating Passwords. When you create a domain based on one of the configuration templates, 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
The following database configuration tasks must be performed in any WebLogic Integration domain:
The config.xml file contains domain configuration information which is used to connect to the JDBC connection pools. After a domain is created using the Configuration Wizard, the WebLogic Integration Database Wizard is run, to set the database configuration information. For additional information see the following section, Configuring the Database for a Domain.
In the WebLogic Integration samples domain and new domains created with the Configuration Wizard, the JDBC connection pools are configured to use a default PointBase database.
Warning: Do not update the database configuration information in the config.xml file for the domain directly. The config.xml file is updated with the database configuration information from the setDBVars and setDBVarsExt files. These files are located in the DOMAIN_HOME\dbinfo\database_type directory, where DOMAIN_HOME represents the full pathname of the domain (including the name of the domain) and database_type specifies the name of the database, for example oracle. We recommend that you avoid modifying the config.xml file directly because any changes you make may be overwritten if the switchdb script or the switch database option of the Database Wizard is run. Update the database configuration information using the Database Wizard. If you must make manual modifications, update the setDBVars and setDBVarsExt files and then regenerate the config.xml file by running the switchdb script or the switch database option of the Database Wizard. For more information about the switchdb command, see switchdb.
Before you can start the server in a WebLogic Integration domain, you must first initialize the database specified in the config.xml file. The following table summarizes the initialization requirements.
The following tools are available to assist you in the database initialization process:
Configuring the Database for a Domain
The WebLogic Integration Database Wizard is a tool that automates database configuration tasks. When you use the Configuration Wizard to create a WebLogic Integration domain, a domain-specific version of the Database Wizard is installed in the new domain. If you have installed the samples domain, a domain-specific version of the Database Wizard is also included in that domain.
The Database Wizard provides the following options:
For example, if you use the Configuration Wizard to create a domain that supports B2B functionality, the version of the Database Wizard installed in the domain performs Tasks 1, 2, 3, and 4 (described in Table 1-3) when you select this option. If you use the Configuration Wizard to create a domain that supports EAI functionality, the version of the Database Wizard installed in the domain performs Tasks 1 and 2 when you select this option.
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 option can be used to both switch and initialize the database for a domain.
Note: Although a domain-specific version of the Database Wizard is available in the samples domain, the Create Database option does not complete tasks 5 and 6 for that domain. To use the samples domain, you must set up and start the server in that domain by executing the RunSamples command. See the following section, Configuring and Starting the Samples Domain.
When you use the Configuration Wizard to create a new domain, you must use the Database Wizard to initialize the repository. For instructions, see Using the Database Wizard. After you have initialized the repository, you can start the administration server for the domain, as described in Starting WebLogic Integration.
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 used the Database Wizard to switch the samples domain to a new database, the command performs the following tasks:
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:
Choose Start
When the RunSamples command is executed on a Windows system, a command window is opened.
For example, enter the following commands:
cd SAMPLES_HOME/integration/samples/bin
. ./RunSamples
On both Windows and UNIX platforms, command progress and messages are displayed. Several minutes may be required for all tasks to complete. When the command has completed, the following actions occur:
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
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:
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 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 Samples Domain, 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:
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:
For example, if you created mydomain in the c:\bea\user_projects directory, enter the following:
cd \bea\user_projects\mydomain
startWeblogic
When the messages described in Startup Complete Messages are displayed, startup has completed successfully.
Starting WebLogic Integration on UNIX
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.
To start WebLogic Integration on a UNIX system:
For example, if you created mydomain in the /home/bea/user_projects directory, enter the following:
cd /home/bea/user_projects/mydomain
. ./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>
<BPM> <000000> <Started WebLogic Integration - BPM Server version 7.0>
<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice>
<Management> <141052> <Application Poller started for development server.>
<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice>
<WebLogicServer> <000354> <Thread "ListenThread.Default" listening on port 7001>
<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice>
<WebLogicServer> <000331> <Started WebLogic Admin Server
"myserver" for domain "samples" running in Development Mode>
<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice>
<WebLogicServer> <000365> <Server state changed to RUNNING>
<Month DD, YYYY hh:mm:ss meridianAbbreviation Timezone> <Notice>
<WebLogicServer> <000360> <Server started in RUNNING mode>
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
To stop WebLogic Integration, complete the following procedure:
For example, if you created mydomain in the c:\bea\user_projects directory, enter the following:
cd \bea\user_projects\mydomain
stopWeblogic
Stopping WebLogic Integration on UNIX
To stop WebLogic Integration on a UNIX system:
For example, if you created mydomain in the /home/bea/user_projects directory, enter the following:
cd /home/bea/user_projects/mydomain
. ./stopWeblogic
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:
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.
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
