The business process container requires a database. This topic
describes how to create the database for Business Process Choreographer.
Why and when to perform this task
In a clustered Business Process Choreographer setup, one database
serves all the business process containers in the WebSphere
® cluster. In a non-clustered
setup, the database is dedicated to the business process container on one
application server.
Steps for this task
- On the machine that hosts the database server, create the database according
to the description for your database system.
- On each machine that runs Business Process
Choreographer without a local database, you must make the remote database
accessible:
- Install a suitable database client or Java™ Database
Connectivity (JDBC) driver on the application server machine.
- If you are not using a type-4 JDBC driver, make the new database
known to the database client as follows:
- For Cloudscape™
- No action is required, because Business Process Choreographer supports
only the embedded version of Cloudscape, which does not support remote access.
The Cloudscape Network
Server is not supported, because it has no XA support.
- For DB2
Universal Database™
- The database must be cataloged and accessible through an alias name.
- For Informix® Dynamic
Server
- This step does not apply because only the type-4 JDBC provider is supported.
- For Microsoft® SQL Server
- This step does not apply because only type-4 JDBC providers are supported.
- For Oracle
- The TCP net service name (TNS) is used to access the database.
- Test the connection to the database.
- Click
- If necessary, select a different scope and click Apply.
For clustered Business Process Choreographer configurations, the data source
can be defined at the cell level or server level. For non-clustered configurations,
the data source is defined at the server level.
- Click
- Locate the appropriate data source, BPEDataSourcedatabase.
For example, BPEDataSourceCloudscape.
- Select the check box for the data source, and click Test connection.
- You should see a message indicating that the test connection was successful.
- If you use Network Deployment, you must also make the database
accessible to the deployment manager. On the deployment manager
machine, perform the following actions:
- Install a suitable database client or JDBC driver on the application
server machine.
- If you are not using a type-4 JDBC driver, make the new database
known to the database client as follows:
- For Cloudscape
- Business Process Choreographer supports only embedded Cloudscape,
which does not support remote access. Cloudscape Network Server is not supported,
because it has no XA support.
- For DB2
Universal Database
- The database must be cataloged and accessible through an alias name.
- For Informix Dynamic
Server
- This step does not apply because only the type-4 JDBC provider is supported.
- For Microsoft SQL Server
- This step does not apply because only type-4 JDBC providers are supported.
- For Oracle
- The TCP net service name (TNS) is used to access the database.
- Add the database driver to the class path of the deployment
manager. Click . Then in the Additional Properties section,
click , and add to the Classpath for
the deployment manager the path for your database driver as described in the
following table.
JDBC driver |
JDBC driver path to add to the deployment
manager's classpath |
DB2® Universal JDBC Driver on Windows®, Linux®, and UNIX® |
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar
|
DB2 CLI provider |
${DB2_JDBC_DRIVER_PATH}/db2java.zip
|
Informix |
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbc.jar
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbcx.jar
|
Microsoft SQL Server (DataDirect ConnectJDBC
driver) |
${CONNECTJDBC_JDBC_DRIVER_PATH}/sqlserver.jar
${CONNECTJDBC_JDBC_DRIVER_PATH}/base.jar
${CONNECTJDBC_JDBC_DRIVER_PATH}/util.jar
${CONNECTJDBC_JDBC_DRIVER_PATH}/../spy/spy.jar
|
Oracle |
${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar
|
- Save your changes.
- If you did not resolve the WebSphere environment variable in
the JDBC driver path, make sure that the appropriate environment variable
is defined. To check, click , select the node dmgr.
- Restart the deployment manager.
- Test the connection to the database.
- Click
- If necessary, select a different scope and click Apply.
For clustered Business Process Choreographer configurations, the data source
can be defined at the cell level or server level. For non-clustered configurations,
the data source is defined at the server level.
- Click
- Locate the appropriate data source, BPEDataSourcedatabase.
For example, BPEDataSourceCloudscape.
- Select the check box for the data source, and click Test connection.
- You should see a message indicating that the test connection was successful.
Result
The Business Process Choreographer database exists and is accessible
from the application server machine and from the deployment manager.
What to do next
Continue configuring
in the
parent topic at step
4.