IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan to configure Business Process Choreographer > Plan for a custom configuration

Plan for the Business Process Archive

If you configure a Business Process Archive Manager, you can move the data associated with completed process instances and human tasks from the BPEDB database to a separate archive database.

To familiarize yourself with the Business Process Archive Manager elements, architecture, and possible configurations, read BPEL process archiving overview.

The Business Process Archive Manager requires its own database. To access the archived process instance and human task data, you can either use the Business Process Archive Explorer or use the Process Archive Manager EJB API to allow a custom client to access the archived data. If you do not perform any database cleanup procedures or archiving, your runtime database will steadily grow in size, which can result in a gradual deterioration in the database performance.


Procedure

  1. For each top-level BPEL process and top-level human task, consider the retention, archiving, and deletion requirements:

    1. How long should they be retained in the Business Process Choreographer database before being deleted or moved to the archive?

    2. If they will be archived, which archive will they be moved to, and who requires access to them?
    3. Verify that your archive policy is coordinated with your cleanup procedures to ensure that no instances that should be archived are deleted from the Business Process Choreographer database. For more information about cleanup procedures, refer to Cleanup procedures for Business Process Choreographer.
  2. Decide how many Business Process Archive Manager configurations you need. Keep the following in mind:

    • Each Business Process Archive Manager configuration can only be used to archive data from one Business Process Choreographer configuration.

    • You can have multiple Business Process Archive Manager configurations that archive data from the same Business Process Choreographer configuration.
    • Federation of data between Business Process Archive databases is not a feature that is built into IBM BPM Advanced.

    • An example of when you might want multiple Business Process Archive Manager configurations is when process instances and task instances that belong to different applications are processed on the same Business Process Choreographer configuration.

  3. For each Business Process Archive Manager configuration, perform Plan for the Business Process Archive Manager.
  4. Decide how many Business Process Archive Explorer configurations you need. Unless you are going to develop your own custom client that can connect to and work with Business Process Archive Manager configurations, you probably need one Business Process Archive Explorer configuration for each Business Process Archive Manager configuration.

  5. For each Business Process Archive Explorer configuration, perform Plan for the Business Process Choreographer Explorer and Business Process Archive Explorer.

  6. If you want your own custom client to access archived process instances and human tasks, refer to Business Process Archive Manager EJB API support.