Support for Multiple Batch Servers

AVEVA Batch Management supports logging data from multiple Batch Servers to a single History Server. Ideally large batch systems are divided into several smaller AVEVA Batch Management installations, where each area of the plant is modeled separately and multiple Batch Servers can share the load of processing. However, it is recommended to have a single Batch History database with a single reporting and administration interface. To support this, each Batch Server can be configured with a Batch Server Name and a Batch Server ID.

The Batch Server Name is a unique name that represents its location or operational focus (it is not a computer name). The Batch Server ID is a character from the alphabet A-Z. This is used to create unique Batch Log IDs, which are used for identifying each batch. Each time a Batch Server is running, all its historical transactions are associated with the server’s configured unique Batch Server Name. This allows you to query data for all Batch Servers or just a specific Batch Server.

You can configure the Batch Server Name and Batch Server ID values for each Batch Server using the Edit System Parameters within the Environment Editor. For more information on System Parameters, see "Viewing and Modifying System Parameters".

Note: If you do not set the Batch Server Name, all historical data will be logged to the <Blank> Batch Server.
If you do not configure the Batch Server ID, it would be possible for two Batch Servers to generate the same Batch Log ID, which is invalid.
If you have a single Batch Server, you do not need to configure either of these parameters.

When you configure these values, ensure the following:

• If you are editing the values on a Batch Server redundant pair, you only need to set the value on the master. It will be synchronized to the backup since the values should be the same on the master and backup.

• The Batch Server Name and Batch Server ID values should ideally be set before running the batch system or configuring batch security.

• It is recommended that you do not change the Batch Server Name after it has been defined. Still if you would need to, make sure the status of all batches is Done or Aborted and they are cleaned from the Batch Schedule. Existing data will continue to be associated with the Batch Server Name from the time the transaction was generated.

• After changing the Batch Server Name, make sure you Exit and Shutdown from Environment Display, and then restart.

  Note: [For Foxboro DCS Component systems only] To get your AlarmComment data to log with a specific Batch Server Name, you must copy the sysparms.txt file from your Batch Server Config_A directory to your AlarmComment clients AVEVA Batch Management\HistQ directory.