Best practices for Business Activity Monitor integration

This topic recommends best practices for integrating the Business Activity Monitor server with the Process Analyzer and configuring the Business Activity Monitor project.

Business Activity Monitor server

The application server that hosts the Business Activity Monitor server (for example, JBoss) should be configured with maximum available memory. On 32-bit UNIX, the maximum memory is 3.5 GB; on Microsoft Windows, the maximum memory that can be configured for the JVM is 1.5 GB.

The Business Activity Monitor database server may be collocated with the Business Activity Monitor server since the Business Activity Monitor database does not require a large amount of space and does not impose a heavy load on the CPU.

The Business Activity Monitor database and the Process Analyzer database should reside on separate servers.

Business Activity Monitor project

Memory usage is a primary consideration when configuring a Business Activity Monitor project. Each additional measure in a stateful view or cube, additional dashboard object, and additional rule and alert combination has significant impact on memory usage. FileNet recommends monitoring memory usage as you add these items to the Business Activity Monitor project—it is best to make one change at a time. For example, add one user-defined field, and create the dashboard object, rules, and alert using that field. Check the system memory usage at each addition before continuing to the next item.

The following are additional tips for configuring the Business Activity Monitor project:

Deploy Business Activity Monitor configuration from development to production

When new Business Activity Monitor functionality has been validated in a development environment, you can deploy the changes in the Business Activity Monitor project to the production environment. FileNet recommends the following general steps:

  1. On the production Business Activity Monitor server, delete all elements (event stream, views, and so on) that have been changed in the development environment. Be sure to delete any depending elements.
  2. Export the entire project from the development environment and import it in the production environment.

Backup and restore

See Back up Business Activity Monitor and Restore Business Activity Monitor for instructions.