Loading the database with system information in a network deployment environment

When you create a deployment environment, the bootstrapProcessServerData command must be completed successfully before you try to start or use Workflow Server or Workflow Center.

Run the bootstrapProcessServerData command successfully at least once for each deployment environment before you start by using the environment:

1. If you deferred DB table creation or you work with an SQL Server database that uses Windows authentication (sqlServerWinAuth=true), manually run the bootstrapProcessServerData command after the database tables are created.
   Note: When you created the deployment environment either by setting the bpm.de.deferSchemaCreation parameter to false for the BPMConfig command or by enabling Create Tables in the Deployment Environment wizard, the bootstrapProcessServerData command is run automatically.

   • For Linux® and UNIX, run DMgr profile_root/bin/bootstrapProcessServerData.sh -clusterName cluster_name, where cluster_name is the deployment environment's application cluster for a three-cluster setup and is case sensitive.
   • For Windows, run DMgr profile_root/bin/bootstrapProcessServerData.bat -clusterName cluster_name, where cluster_name is the deployment environment's application cluster for a three-cluster setup and is case sensitive.

   Note: For Windows, ensure that the command prompt is opened using Run as an Administrator.
2. Check the bootstrapProcessServerData log for errors. If there are issues, correct them and rerun the bootstrapProcessServerData command until it is successful.
   The log file is located at DMgr profile_root/logs/bootstrapProcesServerData.clusterName.log.