Dropping the messaging engine tables

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 messaging engine 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.
    You must 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.
    Tip: The messaging engine table names use the SIB prefix.