Campaign Manager Server overview

The Campaign Manager Server controls the execution of a campaign, maintains all the runtime information about each campaign, and forwards the data to the DeltaV Batch Historian. The Batch Executive must be running before the Campaign Manager can be started.

Refer to the DeltaV Batch Application Manager help for more information on configuring the Campaign Manager Server, including such actions as setting campaign locks, setting up confirmation and verification requirements for Campaign Manager actions, and selecting when journal settings are cleared.

The Campaign Manager becomes redundant when enabled on a Redundant Batch system. Therefore, you must enable the Redundant Batch subsystem in order to have a redundant Campaign Manager. A redundant subsystem provides a mechanism to switchover to a new machine in the event of an interruption to the active node. Refer to DeltaV Books Online for more information on how the Redundant Batch subsystem works, what can cause a switchover and how to configure the Redundant Batch system.

In the event of a switchover, a message is displayed in the Campaign Manager Operator Interface explaining that a switchover of the Campaign Manager is in progress. Any other dialogs that are open at the time are closed automatically. Additionally, any multiple step action is cancelled. A multiple step action is one that requires processing over multiple batches in the campaign (for example creating a campaign with more than one batch or editing multiple batches). Any cancelled action may need to be repeated.