[Version 5.0.2 and later]Creating the database for the business process container

The business process container requires a database. This topic describes how to create the database for process choreographer.

Before you begin

Your database system must already be installed and your application server must be configured to use the database, for example, as described in Configuring WebSphere Application Server for DB2 access . In a clustered 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

  1. If your database server is not on the same machine as your Enterprise Application Server, copy the DDL scripts for your database system to your database server machine.
    On Windows systems, copy the DDL files from install_root\ProcessChoreographer. On UNIX and Linux systems, copy these files from install_root/ProcessChoreographer.
  2. If you use a UNIX or Linux machine to host the database server, create a dedicated file system for the databases.
  3. On the machine hosting the database server, create the database according to the description for your database system.
  4. On each machine that runs process choreographer without a local database, you must make the remote database accessible:
    1. Install a suitable database client or JDBC driver on the application server machine.
    2. If you are not using a type-4 JDBC driver, make the new database know to the database client as follows:
      For Cloudscape
      There is nothing to do because process choreographer only supports an embedded version of Cloudscape, which does not allow 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
      The node and Internet protocol port number that hosts the database is used as the key to access the database.
      For Oracle
      The TCP net service name (TNS) is used to access the database.
      For Sybase Adaptive Server Enterprise
      The node and Internet protocol port number that hosts the database is used as the key to access the database.
    3. Verify that you can access the remote database.
  5. If you are preparing a clustered process choreographer setup, or if you intend to use Network Deployment, you must also make the database accessible to the deployment manager. On the deployment manager machine, perform the following actions:
    1. Install a suitable database client or JDBC driver on the application server machine. For the driver name, refer to the default values for Classpath (data source) for your database.
    2. If you are not using a type-4 JDBC driver, make the new database know to the database client as follows:
      For Cloudscape
      Process choreographer only supports embedded Cloudscape, which does not allow 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
      The node and Internet protocol port number that hosts the database is used as the key to access the database.
      For Oracle
      The TCP net service name (TNS) is used to access the database.
      For Sybase Adaptive Server Enterprise
      The node and Internet protocol port number that hosts the database is used as the key to access the database.
    3. Click on System Administration> Deployment Manager> Process Definition> Java Virtual Machine> Configuration Page and add the database driver to the Classpath of the deployment manager.
    4. Restart the deployment manager.

Results

The process choreographer database exists and is accessible from the application server machine.

Related tasks
Configuring WebSphere Application Server for DB2 access



Searchable topic ID:   t2data
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t2data.html

Library | Support | Terms of Use | Feedback