bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Configuration Wizard Template Reference

BPM Domain Template

The business process management (BPM) Domain template can be used to create a domain that supports WebLogic Integration business process management (BPM) and data integration functionality.

This section describes the BPM Domain template and provides the information you need to configure a fully functional domain based on the BPM Domain template.

This section includes the following topics:

- Template Description

- Creating a Domain Based on the BPM Domain Template

- Security Compatibility

- Configuration and Supporting Files

- Applications and Resources

Template Description

The BPM Domain template creates a domain that supports the following WebLogic Integration functionality:

- Business process management (BPM)

- Data integration

The BPM Domain template supports only two of the four Configuration Wizard server types:

- Single Server (Standalone Server)

- Admin Server with Clustered Managed Server(s)

The BPM Domain template does not support:

- Admin Server with Managed Server(s)

- Managed Server (with owning Admin Server Configuration)

Note: These options are not intended for use with the BPM Domain template. If you select the Admin Server with Managed Server(s) or Managed Server option, an invalid configuration will result.

Purpose

The BPM Domain template is intended to create a domain that supports the development and testing of applications that employ BPM and data integration functionality, but which do not require application integration, B2B integration, WebLogic Portal or WebLogic Workshop functionality.

Creating a Domain Based on the BPM Domain Template

This section describes how to create a fully functional domain based on the BPM Domain template. It includes the following topics:

- Process Overview

- Running the Database Wizard

- Completing the Configuration of a Clustered Domain

Process Overview

Figure 9-1 provides an overview of the steps required to create a standalone server or clustered server domain based on the BPM Domain template.

Figure 9-1 Creating a Domain Based on the BPM Domain Template

Note: In the Configuration Wizard, the Configure Standalone/Administrative Server dialog box presents a default server name, myserver. We recommend that you accept the default name. If you choose to rename the administrative server, you must rename DOMAIN_HOME/applications/DefaultWebApp_myserver to DOMAIN_HOME/applications/DefaultWebApp_servername

Here, DOMAIN_HOME represents the root directory of the custom domain you created using the Configuration Wizard (for example, c:\bea\user_projects\mydomain) and servername represents the name you assigned to the administrative server in the dialog box.

For additional information about the Configuration Wizard prompts, see Using the Configuration Wizard at the following URL:

http://e-docs.bea.com/platform/docs70/confgwiz/index.html

The following sections provide the information you need to run the Database Wizard and complete the configuration of a clustered domain.

Note: Before you run the Database Wizard, make the changes required to complete the configuration of a clustered domain, or start the administrative server, we recommend that you back up the DOMAIN_HOME/config.xml file. This will allow you to easily restore the initial configuration. In addition, the config.xml file created by the BPM Domain template contains comments which are lost when you run the Database Wizard or start the administrative server.

Running the Database Wizard

When you use the Configuration Wizard to create a domain based on the BPM Domain template, a domain-specific version of the Database Wizard is installed in the DOMAIN_HOME directory. You must run the Database Wizard for the domain to initialize the database repository with the required tables and system data. For instructions, see "Using the Database Wizard" in Customizing WebLogic Integration in Starting, Stopping, and Customizing BEA WebLogic Integration at the following URL:

http://e-docs.bea.com/wli/docs70/config/custom.htm

Until you have used the Database Wizard to initialize the WebLogic Integration database, you will be unable to start any server in the new domain.

Completing the Configuration of a Clustered Domain

If you selected the Admin Server with Clustered Managed Server(s) option, there are several tasks that must be performed to complete the configuration.

The following table lists each required configuration task and provides a cross-reference to the detailed procedure, which can be found in Configuring a Clustered Deployment in Deploying BEA WebLogic Integration Solutions at the following URL:

http://e-docs.bea.com/wli/docs70/deploy/config.htm

Table 9-1 Completing the Configuration of a Clustered Domain

To complete this task . . . | Refer to . . .
--- | ---
Edit the config.xml file to target the WLI-BPM Plugin Manager (wlpi-master-ejb.jar) and the BPM EventTopic JMS topic (com.bea.wlpi.EventTopic) to a single managed server. | Step 4. Configure BPM Resources for One Managed Server
Set the -Dweblogic.management.discover parameter to true in the StartWeblogic command for the administrative server. | Step 8. Edit the startWeblogic Command File
For any managed server configured on a machine remote from the administrative server, you must do the following: 1. Install WebLogic Platform on the remote machine. At a minimum, you must install WebLogic Integration. 2. Copy the files required to start the managed server from the administrative server DOMAIN_HOME directory to a corresponding directory on the machine hosting the managed server. Update the files as required. | Step 9. Set Up Managed Servers for Your Domain

At a minimum, you must complete the tasks listed in the table. Depending on how you intend to use the domain, additional steps may be required to configure an RDBMS security realm, configure a software router, secure your server environment, configure the servers for automatic restart, or configure for migration of resources from a failed to a healthy node. See Configuring a Clustered Deployment in Deploying BEA WebLogic Integration Solutions for details.

Security Compatibility

The default security mode for the BPM Domain template is the WebLogic Server 6.x file-based realm in compatibility mode (FileRealm). The new WebLogic Server 7.0 LDAP-based realm is not supported with WebLogic Integration functionality.

If you are migrating from a WebLogic Integration 2.1 RDBMS realm, see "Migrating from the RDBMS Realm" in Migrating WebLogic Integration 2.1 to WebLogic Integration 7.0 in the BEA WebLogic Integration Migration Guide at the following URL:

http://e-docs.bea.com/wli/docs70/migrate/berlin.htm

For more information about WebLogic Platform security, refer to Introduction to WebLogic Platform 7.0 Security at the following URL:

http://edocs.bea.com/platform/docs70/secintro/index.html

Configuration and Supporting Files

The following table summarizes the configuration and supporting files included in a domain based on the BPM Domain template.

Table 9-2 BPM Domain Directories and Files

Files | Description
--- | ---
| The root of the domain contains the config.xml file, Windows and UNIX versions of the startWebLogic command (the command used to start the administrative server), wliconfig command (the command used to start the Database Wizard), and other WebLogic Integration specific commands. For additional information, see WebLogic Integration Sample Configuration Files and WebLogic Integration Commands in Starting, Stopping, and Customizing BEA WebLogic Integration at the following URL: http://e-docs.bea.com/wli/docs70/config/index.htm
| The applications directory initially contains only the DefaultWebApp_myserver directory. If you named your administrative server something other than myserver, you should not attempt to start the server until you have renamed this directory to DefaultWebApp_servername.
| The dbInfo directory contains commands used by the Database Wizard to create and populate the database repository for the domain. For information about setDBVars and related commands, see WebLogic Integration Commands in Starting, Stopping, and Customizing BEA WebLogic Integration at the following URL: http://e-docs.bea.com/wli/docs70/config/keycmd.htm
| The scripts directory contains the SwitchBB.xml file, which is used by the Database Wizard to update the configuration to a new database.

Applications and Resources

This section provides a summary of the applications and resources configured in a domain based on the BPM Domain template. The targets indicated represent the initial configuration. If you selected Admin Server with Clustered Managed Server(s), you must modify the configuration for the WLI-BPM Plugin Manager and the BPM EventTopic JMS Topic to target a single managed server. See Completing the Configuration of a Clustered Domain.

Table 9-3 BPM Domain Configuration Summary

Resource | If you selected Single Server (Standalone Server) | If you selected Admin Server with Clustered Managed Server(s)
--- | --- | ---
| A single server, myserver, is configured. | An administrative server, myserver, and one or more managed servers are created as defined in the Configuration Wizard.
| No cluster is created. | A single cluster, named as specified in the Configuration Wizard, is created. All managed servers defined are assigned to the single cluster.
| The target for the following WebLogic Integration components is the administrative server: WLI Error Listener WLI Repository WLI-BPM Event Processor WLI-BPM Initialization WLI-BPM Plugin Manager WLI-BPM Server WLI-DI BPM Plug-in WLI-DI BPM Plug-in Help | The target for the following WebLogic Integration components is the cluster: WLI Error Listener WLI-BPM Event Processor WLI-BPM Initialization WLI-BPM Plugin Manager WLI-BPM Server WLI-DI BPM Plug-in WLI-DI BPM Plug-in Help The target for the following component is both the administrative and the cluster: WLI Repository
Note: A number of the WebLogic Integration JAR and WAR files displayed in the navigation tree are not defined in the initial DOMAIN_HOME/config.xml file and therefore, no target is defined for these components. These JAR and WAR files are displayed because they are included in the definition of the WebLogic Integration application in the WLI_HOME/lib/META-INF/application.xml file.
| The target for all JDBC services is the administrative server. | The target for all JDBC services is the cluster.
| A single JMS server, WLIJMSServer, is defined. The target for all JMS services is the administrative server. | The target for the following JMS services is the cluster: wlpiFactory wlpiQueueFactory A JMS server is defined for each managed server (for example, WLIJMSServer_managed). The target is the managed server for which the JMS server has been defined and is migratable.
| The target for the WLPIXML_Registry is the administrative server. | The target for the WLPIXML_Registry is the administrative server.
| The target for the wlpiMailSession is the administrative server. | The target for the wlpiMailSession is the cluster.
| The security configuration is not dependent on the server type selected. As described in Security Compatibility, the default security mode for the BPM Domain template is the WebLogic Server 6.x file-based realm in compatibility mode (FileRealm). For information about setting up and managing security for WebLogic Integration solutions, see Using WebLogic Integration Security in Deploying BEA WebLogic Integration Solutions at the following URL: http://e-docs.bea.com/wli/docs70/deploy/secure.htm

Note: Once you start the administrative server for your new domain, you can view the application components by type (for example, EJB, Web Application, or Connector Component) in the WebLogic Administration Console.