IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan to configure Business Process Choreographer > Plan for a custom configuration

Plan the databases for Business Process Choreographer

Plan the databases for Business Process Choreographer. Depending on your Business Process Choreographer setup, you might need to plan to create up to three databases, or none (if all the databases are put in the CMNDB common database). Each Business Process Archive Manager also needs a database, which can also reside in the common database. However, for production systems, you should plan to have all the Business Process Choreographer databases as separate, high-performance databases.

Business Process Choreographer can share a database with other process server components. The BPEDB database is used by the Business Flow Manager and the Human Task Manager. For a production system plan to have a dedicated database for each deployment target where Business Process Choreographer is configured.

If you have multiple Business Process Choreographer configurations, then each of these needs its own database or database schema. The Business Process Choreographer database tables cannot be shared between multiple Business Process Choreographer configurations.

The Business Process Choreographer messaging engines can either share the database used by the SCA messaging engines, or have their own BPEME database. For more information about which databases are supported for your selected configuration path, see t1pl_topology.html#t1pl_topology__decide or t1pl_topology.html#t1pl_topology__zdecide.


Procedure

  1. For a production system:

    1. If performance is important, plan to use a separate database for Business Process Choreographer, as described in Plan the BPEDB database, otherwise, plan to use the CMNDB common database.

    2. For high-load setups, for example, a large cluster with very high messaging rates, consider improving the performance by using a separate database for the Business Process Choreographer messaging engine. This allows the database logging to be parallelized, which can help to prevent it from becoming a bottleneck.

      • If you use the administrative console to configure Business Process Choreographer, and you want a separate database for the Business Process Choreographer messaging engine, perform Plan the messaging engine database, otherwise plan to use the default database that is used by the Service Component Architecture.

      • If you use the bpeconfig.jacl configuration script to configure Business Process Choreographer, Business Process Choreographer will use the same database as a message store that is used by SCA. Business Process Choreographer will use its own schema in the same database.

    3. Optional: Use the database design tool to interactively create the database design file and the SQL script files that the database administrator can use to create all three databases that you planned in the previous steps. There are significant advantages to using this tool:

      • You can run the tool as often as necessary to refine the database design parameters, without the risk of breaking them, rather than editing the provided template SQL files manually.

      • If you have used a database design file, the next time that you migrate to a newer version of this product, you can generate the schema update SQL scripts.

      • If you create a database design file for a test configuration, it is convenient to be able to make of copy of the design file and make minor changes to it for the databases for your production system.

      • Using the tool, you can also define the data sources for all three databases.

      Important: When using the database design tool to create a deployment environment, after you have configured the common database, Business Process Choreographer is shown as being "complete". This is because there is a valid default, that causes the tables for Business Process Choreographer to be created in the common database. However, this default is not suitable for production systems. For a production system, make sure that you configure a dedicated database for each deployment target where Business Process Choreographer is configured.

  2. For a non-production system where simplicity of setup is more important than performance, your options depend on the configuration path that you have chosen:

    • If you will use the Installer or Profile Management Tool to create the "Basic sample" or the "Sample with organization" Business Process Choreographer configuration, a separate default BPEDB database is created, which is also used by the Business Process Choreographer Explorer reporting function. For the Business Process Choreographer messaging engine, the default is to have a separate default database (BPEME). If you use pmt.sh, you can also select to share the CMNDB database.

    • If you will use pmt.sh to create a deployment environment that includes a Business Process Choreographer configuration, Business Process Choreographer, and the Business Process Choreographer messaging engine will all use the CMNDB database. Therefore, you do not need to do any database planning for Business Process Choreographer.

  3. If you will configure one or more Business Process Archive Manager configurations, perform Plan the Business Process Archive database for each Business Process Archive Manager configuration.


Results

You have planned all the databases for your Business Process Choreographer configuration.