Estimate the application server resources that you need for Business
Process Choreographer. Each business process container requires
the following resources to run properly. The names shown are the default names
that are used in a standard installation of Business Process Choreographer.
The
activation specifications for the process server are found in the administrative
console under .
- BPEApiActivationSpec
- BPEInternalActivationSpec
- HTMInternalActivationSpec
The concurrency of the process navigation depends on the number of
concurrent endpoints set in BPEInternalActivationSpec and HTMInternalActivationSpec
(for processes containing human tasks).
One data source, to read and
write business process state information to a database: jdbc/BPEDB
For
each possible concurrent navigation step in a long-running process instance:
- One Java™ database connectivity (JDBC) connection to BPEDB
- One concurrent endpoint session on the BPEInternalActivationSpec
- Two JDBC connections to the messaging data store (JMS): one each for get
and put
- Additional database connections if you are using the Business Process
Choreographer API to start processes or to interact with running processes
- Additional JMS sessions, to support system overloads situations where
additional messages are generated and need to be served
Restriction: The number of concurrent endpoints sessions
(m) must not exceed 90% of the number of JDBC connections
to the process server database BPEDB and must not exceed half the number of
JDBC connections to the messaging databases.
For
example, to process up to 30 navigational steps concurrently, you need 30
concurrent endpoints on the BPEInternalActivationSpec. This requires 30 *
1..1 JDBC connections to the process server database and at least 60 JDBC
connections on the messaging database
Your estimate for the maximum
number of parallel JDBC connections that are required at any time provides
the value for p, which is used in the following steps.