Your choice of topology and setup affects which Business Process Choreographer configuration paths you can use.
You can also use this script to configure a Business Process Archive Manager, but not on the same deployment target where Business Process Choreographer is configured.
When configuring the Business Process Choreographer Explorer in the administrative console, or using the bpeconfig.jacl configuration script or clientconfig.jacl configuration script there is an option to configure the Business Process Choreographer Explorer reporting function.
If you migrated an existing Business Process Choreographer configuration, any Business Process Choreographer Observer configuration is not migrated. To use the Business Process Choreographer Explorer reporting function you must enable it, as described in Enabling the Business Process Choreographer Explorer reporting function after migration.
Choices | Restrictions | Suitable configuration path | |||
---|---|---|---|---|---|
Are you planning a production system? | What is the deployment target? | Type of Business Process Choreographer configuration | Can it use a separate database? | Which message stores are supported for the messaging engine? | Configuration path name and possible configuration tools |
No | Stand-alone server | Basic sample (without the sample organization) |
Yes, the BPEDB database can be any supported database. | Only the shared DB2® CMNDB database | "Basic sample" using the Profile Management Tool to create an advanced Process Server or Process Center profile, and select the Business Process Choreographer option. |
No, the BPEDB database is created (using the schema name BPEDB) in the common database, CMNDB, which can only be DB2. | "Basic sample" using the Profile Management Tool to create a typical Process Server or Process Center profile. | ||||
"Basic sample" using the Installer to create a typical installation of Process Server or Process Center | |||||
Sample including a 15 person organization, and substitution is enabled. | No, the BPEDB database is created (using the schema name BPEDB) in the common database, CMNDB, which can only be DB2 Express. | "Sample with organization" using the Installer to create a custom install of the Process Server. | |||
Yes | Cluster | Choice of deployment environment patterns:
|
Yes, the BPEDB database can be any supported database. | Any supported database. | "Production deployment environment" using the Administrative Console. |
Flexible custom configuration | "Flexible custom configuration" using
one of:
|
||||
Stand-alone server | |||||
Yes | Any network deployment server or cluster where Business Process Choreographer is not configured. | Business Process Archive | The BPARCDB archive database must be separate from the BPEDB database. It must be of the same database type that is used by the Business Process Choreographer configuration. | Does not have its own messaging engine. Uses the same messaging engine as the Business Process Choreographer configuration. | "Business Process Archive" using:
|