Concepts

Edit online

Optimize has six components or activities that access the Optimize database component sets:

  • analysis.engine Analytic Engine
  • process.history Analytic Engine
  • process.model Analytic Engine
  • process.work Analytic Engine
  • common.directory Analytic Engine

A typical Optimize configuration of database connection pools involves four connections:

  • analysis.engine Analytic Engine through a pool to the Analysis database component set
  • process.history Analytic Engine and process.work Analytic Engine through a single pool to the Process Tracker database component set
  • process.model Analytic Engine through a pool to the Process Audit Log database component set
  • common.directory Analytic Engine through a pool to the IBM My webMethods Server database component set

See the following figure.

Figure 1. Connecting Optimize database activities to Optimize database component sets: typical configuration
Connecting Optimize database activities to Optimize database component sets

In high-volume situations, you may be able to improve performance by assigning separate database connection pools to:

  • The process.history Analytic Engine and process.work Analytic Engine Optimize database activities; both connect to the Process Tracker database component set.
  • The analysis.engine Analytic Engine Optimize database activities; connects to the Analysis database component set.

See the following figure.

Figure 2. Connecting Optimize database activities to Optimize database component sets: high-volume configuration
Connecting Optimize database activities to Optimize database component sets for high volume configuration
Note: You must define a minimum of one database connection pool per database schema. In an Optimize configuration with four database schemas as shown in the figures above, you must define a minimum of four database connection pools.

Multiple Analytic Engines

Edit online

In an environment with multiple Analytic Engines, each Analytic Engine has a separate set of four database activities (analysis.engine, process.history,process.model, and process.work) that connect to the same database schemas. You can reuse the first Analytic Engine's database connection pool definition for the second Analytic Engine, or you can give each Analytic Engine its own database connection pool definition as shown in the figure below.

Figure 3. Connecting Optimize database activities to Optimize database component sets: two Analytic Engines
Connecting Optimize database activities to Optimize database component sets: Two Analytic Engines