The Business Process Choreographer requires a database. The Business Process Choreographer database (BPEDB) is used for this purpose.
The Business Process Choreographer database is only used by Business Process Choreographer.
Each deployment target (either server or cluster) can be configured to support Business Process Choreographer applications. Each Business Process Choreographer deployment target must have its own database. Databases cannot be shared between deployment targets.
Configuring the Business Process Choreographer database can be complex and requires many parameters. Therefore, it is performed as a post profile creation step. The Business Process Choreographer Sample configuration, which can be set up when creating or augmenting a stand-alone server profile through the Profile wizard, is based on Cloudscape and requires a minimal set of parameters. However, it is not suitable for production purposes.
The Business Process Choreographer Sample configuration cannot be created under other circumstances since Cloudscape is not supported by the Business Process Choreographer database in network deployment environments. When you select the Business Process Choreographer Sample configuration option, the Profile wizard invokes the standard Business Process Choreographer configuration script (bpeconfig.jacl) with the appropriate parameters, which you must supply. This script creates the Cloudscape database for the sample configuration.
All the scripts to create and manage the Business Process Choreographer database can be found in the directory install_root/dbscripts/ProcessChoreographer/dbType. These scripts are described in detail in Using scripts to administer Business Process Choreographer.
There are scripts to create the database (for simple setups), to create tablespaces, dbspaces, and the schema (for advanced setups), to clear the schema, to drop the schema, and to drop the tablespaces or dbspaces. These scripts can either be run manually by a database administrator or you can run the bpeconfig.jacl script, which will invoke the scripts for you.
If an appropriate JDBC provider does not exist one is created.
The data source name is:
BPEDataSourcedbType
The data source JNDI name is:
jdbc/BPEDB
Many tables are created. See the generated scripts to see which tables are generated for the given database product.
install_root/dbscripts/ProcessChoreographer/dbTypedirectory.
The user credentials that you provide in the Profile wizard must have the permissions necessary to create tablespaces, tables, indexes, and stored procedures. For the Create a new (local) database option, the user identity must have the necessary privileges to create a new database.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)