Dropping the messaging engine tables

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
If you also want to move your Business Automation Workflow databases, back up and restore them in this step. Even if you are using the existing databases, you must drop the previous service integration bus (SIB) messaging tables before you start the new deployment environment.

Procedure

  1. Optional: If you want to move your Business Automation Workflow databases, use your database utility to back up each of your source databases and restore them to another database instance or schema.
    Make sure that they match the database information that you specified when you updated the BPMConfig properties file, including the following properties:
    • hostname
    • port
    • database name
    • schema
    • user
    • password
  2. Manually drop the existing messaging engine tables in the messaging database of your new deployment environment before you start the deployment environment.
    Important:

    If you are using Db2® for z/OS® as your database, do not select the option to automatically create messaging engine tables. This option is not supported on Db2 for z/OS and results in an exception when WebSphere® Application Server attempts to create the tables.

    Instead, you must manually create the messaging engine tables by running the createSchema_Messaging.sql script in coordination with your database administrator. For more information, see Creating Db2 for z/OS database objects using the Db2 command line processor: for Windows

    Tip: The messaging engine table names use the SIB prefix.