Administration Guide › Aggregation and Correlation Engines (ACE1 and ACE2) › Default Engine Management

Default Engine Management

ACE2 is an evolution of ACE1. CA plans to phase out ACE1 in upcoming releases. New functionality is being developed only for ACE2. If you are upgrading, all current metrics that existed before the upgrade are still calculated by ACE1. Only new metrics are handled by ACE2. CA recommends working with ACE2 as the default engine.

All contract parties are assigned to ACE2. This means that all new metrics, including metrics in new contracts and new metrics in existing contracts that were created before the upgrade to 8.0, are directed to ACE2. This only applies to newly added metrics. The system does not force the migration of existing content.

If you want work with ACE1 as the default engine, you can do so by changing the system configuration property named "isACE2defaultengine" from 1 to 0. This causes the assignment of new contract parties to ACE1.

Note: Once CA Business Service Insight is installed, all existing contract parties are moved to ACE2. Turning that feature off by selecting 0 for this value, does not move contract parties back to ACE1. That process must be done manually.

ACE Transition Service

The ACE Transition Service is an installed service added to CA Business Service Insight as of version 8.2 to migrate calculation of metrics from ACE1 into ACE 2.

The service notifies metrics that have migrated into ACE2 about recalculations required due to events that occur during the migration phase.

Migration involves 2-steps:

• Mark the metric for migration into ACE2 from the user interface. The ID in the global rules table for the "Assigned_PSL_instance_id" changes to -1.
• The ACE Transition Service processes the relevant metrics and sets the calculation start date including recalculations, if needed.

Note: When ACE1 is performing calculations at the same time that migration is initiated, the Transition Service does not migrate the metric (yet) and ACE1 completes the current calculations. The processes do not collide.

When ACE1 is currently processing a calculation when migration is initiated, ACE1 marks the recalculation date to start from, not the Transition Service. There are no collisions between processes.

Calculation and Upgrade to 8.2

By default, ACE2 is assigned to all metrics created after upgrade to version 8.2. The migration process is the responsibility of ACE2. The ACE1 engine (PSL_Writer) marks the recalculation date (if any exist) for metrics waiting to be migrated into ACE2 but that ACE1 currently supervises.

During the migration process in T_global_rules, the following flags are set:

ACE Transition Service Cases

This section lists the possible ACE Transition Service cases.

Remove PSLWriter Service Cases

This section lists "Remove PSL_Writer Service" cases.