Using a generated script to create the database schema for Business Process Choreographer

When you configure Business Process Choreographer, scripts are generated that creates the database objects for Business Process Choreographer.

Before you begin

This topic applies only to the Distributed platformsYou have used the administrative console or the bpeconfig.jacl script to configure Business Process Choreographer. If you used the bpeconfig.jacl script to configure Business Process Choreographer, either you used the -createDB no option to defer creating the database objects, or the bpeconfig.jacl script failed to create the database.

This topic applies only to the z/OS platformYou have used the administrative console or the bpeconfig.jacl script to configure Business Process Choreographer. If you used the bpeconfig.jacl script to configure Business Process Choreographer, you used the -createDB no option to defer creating the database objects.

If you used the administrative console deployment environment wizard to configure Business Process Choreographer, and you want to use custom table spaces for the Business Process Choreographer database, if you have not already run the DbDesignGenerator command to regenerate the necessary scripts, regenerate them as described in Using the administrative console's deployment environment wizard to configure Business Process Choreographer. If you did not regenerate the scripts to the standard location mentioned later, be sure that you use the regenerated scripts.

About this task

All the relevant configuration parameters that you provided when configuring Business Process Choreographer have been substituted in the generated files. You either want the database for a high-performance Business Process Choreographer configuration, or your database administrator must create the database for you, or both.

Procedure

  1. This topic applies only to the Distributed platformsLocate the generated (or regenerated) createBPCDB script, or createSchema_BPC.sql if you are using a remote DB2 on z/OS database.This topic applies only to the z/OS platformLocate the generated createSchema_BPC.sql script.
    • This topic applies only to the Distributed platformsIf you configured Business Process Choreographer in a network deployment environment using the administrative console or by running the bpeconfig.jacl script in connected mode, the createBPCDB or createSchema_BPC.sql script will be generated on the node of the deployment manager.
    • This topic applies only to the z/OS platformIf you configured Business Process Choreographer in a network deployment environment using the administrative console or by running the bpeconfig.jacl script in connected mode, the createSchema_BPC.sql script will be generated on the node of the deployment manager.
    • This topic applies only to the Distributed platformsIf you configured Business Process Choreographer on a standalone server using the administrative console or by running the bpeconfig.jacl script in connected mode, the createBPCDB or createSchema_BPC.sql script will be generated on the node on the node of the stand-alone server.
    • This topic applies only to the Distributed platformsIf you configured Business Process Choreographer by running the bpeconfig.jacl script in disconnected mode, the createBPCDB or createSchema_BPC.sql script will be generated on the node where you invoked wsadmin.
    • This topic applies only to the z/OS platformIf you configured Business Process Choreographer by running the bpeconfig.jacl script in disconnected mode, the createSchema_BPC.sql script will be generated on the node of the stand-alone server.
    This topic applies only to the z/OS platformThere is an ASCII SQL script, named createSchema_BPC.sql, and an equivalent EBCDIC DDL script, named createSchema_BPC.ddl:
    • If you specified a schema qualifier, both files are normally located in profile_root/dbscripts/ProcessChoreographer/database_type/database_name/database_schema.
    • If you did not specify a schema qualifier, both files are normally located in profile_root/dbscripts/ProcessChoreographer/database_type/database_name.
    This topic applies only to the Distributed platforms
    • For Linux operating systemFor UNIX operating system
      • If you specified a schema qualifier, the generated script is normally: profile_root/dbscripts/ProcessChoreographer/database_type/database_name/database_schema/createBPCDB.sh, or profile_root/dbscripts/ProcessChoreographer/database_type/database_name/database_schema/createSchema_BPC.sql if you are using a remote DB2 on z/OS database.
      • If you did not specify a schema qualifier, the generated script is normally: profile_root/dbscripts/ProcessChoreographer/database_type/database_name/createBPCDB.sh, or profile_root/dbscripts/ProcessChoreographer/database_type/database_name/createSchema_BPC.sql if you are using a remote DB2 on z/OS database.
    • For Windows operating system
      • If you specified a schema qualifier, the generated script is: profile_root\dbscripts\ProcessChoreographer\database_type\database_name\database_schema\createBPCDB.bat, or profile_root\dbscripts\ProcessChoreographer\database_type\database_name\database_schema\createSchema_BPC.sql if you are using a remote DB2 on z/OS database.
      • If you did not specify a schema qualifier, the generated script is: profile_root\dbscripts\ProcessChoreographer\database_type\database_name\createBPCDB.bat, or profile_root\dbscripts\ProcessChoreographer\database_type\database_name\createSchema_BPC.sql if you are using a remote DB2 on z/OS database.
    Where:
    profile_root
    is on the node of your stand-alone server or in a network deployment environment on the node of the deployment manager.
    database_type
    is one of the following strings, which identify the database systems that are supported by the generated scripts:
    • This topic applies only to the Distributed platformsDB2®
    • DB2zOS
    • This topic applies only to the Distributed platformsOracle
    • This topic applies only to the Distributed platformsSQLServer
    database_name
    is the name of your database.
    database_schema
    is the name of the schema, if you are using one.
  2. This topic applies only to the z/OS platformCreate the DB2 for z/OS® database manually.
  3. This topic applies only to the Distributed platformsIf the database does not yet exist, get your database administrator to create the database and user IDs according to the values you planned in Planning the BPEDB database and Planning security, user IDs, and authorizations.
    Note: This step is not necessary if your database is one of the following, because the generated script will create the database:
    • DB2 for Linux, UNIX, or Windows local database
  4. If the database is remote, copy the generated script to the database host. If you are not authorized to perform this, give your database administrator a copy of the script and discuss your requirements with the administrator.
  5. You or your database administrator can use the DBDesignGeneration utility to generate the required script files for creating and configuring the database:
    1. For a high-performance system, specify the allocation of disks and table spaces that you planned in step 5 of Planning the BPEDB database.
    2. This topic applies only to the z/OS platformIf you used the administrative console to configure Business Process Choreographer use the storage group name. The default value is SYSDEFLT.
    3. This topic applies only to the Distributed platformsIf you used the administrative console to configure Business Process Choreographer:
      • This topic applies only to the Distributed platformsFor DB2 on z/OS: Use the storage group name, the default value is SYSDEFLT.
      • If you do not want the table spaces to be created in your database system's default location for new table spaces, specify the table space directory while using the DbDesignGenerator utility.
  6. Run the script on the database host using one of the following commands:
    Option Description
    This topic applies only to the Distributed platformsFor DB2 on Linux, UNIX, or Windows This topic applies only to the Distributed platformsThis topic applies only to the Distributed platforms
    createBPCDB.sh
    createBPCDB.bat
    Note: You can specify the createDB parameter after the command to create a local database. Skip this parameter if you have already created the required database.
    For DB2 on z/OS For the ASCII version:
    db2 -tf createSchema_BPC.sql
    For the EBCDIC version:
    db2 -tf createSchema_BPC.ddl
    This topic applies only to the Distributed platformsFor an Oracle database This topic applies only to the Distributed platformsThis topic applies only to the Distributed platforms
    createBPCDB.sh
    createBPCDB.bat
    This topic applies only to the Distributed platformsFor an SQL Server database This topic applies only to the Distributed platformsThis topic applies only to the Distributed platforms
    createBPCDB.sh
    createBPCDB.bat
    Note: You can specify the createDB parameter after the command to create a local database. Skip this parameter if you have already created the required database.
  7. For all existing Business Process Choreographer configurations, configure Java™ Database Connectivity (JDBC) to access the database remotely. Perform the following steps:
    • On each node that hosts a member of the cluster where you configured Business Process Choreographer.
    • On any server that runs Business Process Choreographer.
    1. If the database server is different from the Business Process Choreographer server, install a suitable type-2 database client or type-4 JDBC driver on the server that hosts the application server.
    2. This topic applies only to the z/OS platformIf you are using a type-2 JDBC driver, make the new database known to the database client. The database must be catalogued and accessible through an alias name.This topic applies only to the Distributed platformsIf you are using a type-2 JDBC driver, make the new database known to the database client by performing the following: This topic applies only to the Distributed platforms
      For DB2 Universal Database™
      The database must be cataloged and accessible through an alias name.
      For DB2 for z/OS
      The database must be cataloged and accessible through an alias name.
      This topic applies only to the Distributed platformsFor Microsoft SQL Server
      This topic applies only to the Distributed platformsThis step does not apply because only type-4 JDBC providers are supported.
      This topic applies only to the Distributed platformsFor Oracle
      This topic applies only to the Distributed platformsThe TCP net service name (TNS) is used to access the database.
    3. Using the administrative console, test the connection to the database.
      1. Click Resources > JDBC > Business Integration Data Sources
      2. If necessary, select a different scope and click Apply.
        Note: For clustered Business Process Choreographer configurations, the data source is defined at the cluster level. For non-clustered configurations, the data source is defined at the server level.
      3. Locate and select the data source with the JNDI name jdbc/BPEDB.
      4. Click Test connection.
      5. You should see a message indicating that the test connection was successful.

Results

The Business Process Choreographer database exists.