Configure the General Settings

You can configure the redundancy support and Foxboro DCS components support using the General Settings option in the Configurator. If you change the general settings after you have configured the AVEVA Batch Management features, you must use the Configurator to update all the required features.

To configure the General settings

1. Open the Configurator.

2. Click General in the left pane. The configuration options appear in the right pane.

   

3. In the Settings area, you can configure the following:

   • Select the Enable Redundancy Support check box to enable redundancy support for the AVEVA Batch Management product. For more information, refer to "Enable Redundancy Support".

   • Select the Enable Foxboro DCS Component Support check box to enable Foxboro DCS components support for the AVEVA Batch Management product. For more information, refer to "Enable Foxboro DCS Component Support".

4. Under Service Admin Access, perform the following:

   1. In the User Name box, type the name of the user account in the <DomainName>\<UserName> format. This account is used for running the EnvMngr, SecMngr, and HistQMngr services. Ensure that the user account has Administrator privileges.

   2. In the Password box, type the password for the user account.

5. Click Configure.

Enable Redundancy Support

This option allows you to configure a AVEVA Batch Management Redundant system. Both AVEVA Batch Management Servers involved in a redundant pair require this option to be enabled. Once you have enabled this option, other AVEVA Batch Management features are updated with parameters related to redundancy and require configuration. To ensure the correct operation of a redundant pair, verify that all the features have been completely and correctly configured.

NOTE: For AVEVA Batch Management to work in redundant mode in a secured Foxboro DCS environment, you must set the Service Admin Access Account to a user who has the same rights as the IAServices or IAInstaller users.

Set Up a Redundant Network

Before you install redundant AVEVA Batch Management Servers, you must properly configure two computers to interact on the network.

IMPORTANT: Qualified personnel must perform the redundant network configuration.

To configure the redundant pair

6. Name the two computers following AVEVA Batch Management guidelines: standard Windows server names are supported. For more information, see Host Name Naming Convention.

7. Each computer must have dual network interface cards (NICs) as the redundant pair. The two computers should have identical hardware.

8. Configure each computer for the TCP/IP protocol.

9. Set up primary and secondary NICs on both computers. Assign proper IP addresses to each NIC.

   It is critical that the two addresses assigned to the NICs on a single server are from different networks. This address difference ensures that the network connection is used for communicating the heartbeats. If these addresses differ only at the host level, redundancy does not work properly.

10. Configure the binding order of the NICs under Network Connections > Advanced > Advanced Settings so that the primary NIC is at the top of the list and the secondary NIC is on the bottom.

11. In TCP/IP settings, select the Enable LMHOSTS lookup check box. As a result, the set of four network addresses are loaded into the lmhosts file.

12. In the Configurator, enter two sets of logical host names for the computers. For example, one computer is BATCHMANAGEMENT1 and BATCHMANAGEMENTA; the other is BATCHMANAGEMENT2 and BATCHMANAGEMENTB. The logical host names for the primary network are 1 and 2. The logical host names for the secondary network are A and B.

13. Make sure that the computers can ping each other by name and they can be pinged by name from a third computer on the same network.

14. Connect the computers with a cross-over cable and then make sure that they can ping each other by IP. The IP should be on a different subnet than the primary NICs. For example, 10.1.1.1 and 10.1.1.2 works very well.

15. Modify the lmhosts file on both computers, and add the entries for the logical names and IPs. For details, see "Editing the Lmhosts File on Redundant Servers".

16. Make sure that the two computers can ping each other by their logical host names.

Enable Foxboro DCS Component Support

IMPORTANT: This option is only required when using AVEVA Batch Management with Foxboro DCS controllers using FoxDCSDriver and AIM API. This is the typical configuration when using FoxView as the HMI.

This option is not required when using IBMX or IBCli, with Foxboro Control Software (FCS) InTouch HMI or standalone. Enabling this option when not required may cause problems in the application configuration.

Foxboro DCS components support can be enabled on systems where no Foxboro DCS Software is installed. This allows users to create AVEVA Batch Management models in non Foxboro DCS machines which can later be moved to systems where Foxboro DCS software is installed and AVEVA Batch Management Foxboro DCS components are enabled.

Configuring this feature will make specific changes to some components in the Environment Display and other modules of AVEVA Batch Management. After the feature is configured, the following applications will be available in the Environment Display:

• FoxDCSDriver

• FoxDCSLink

• BatchView

Applications created in a system with Foxboro DCS components enabled will have a different set of files and databases in the Config_A folder as the ones created in a system without Foxboro DCS components enabled. Due to this difference in the folder content, the models cannot be moved or re-used between Foxboro DCS and non Foxboro DCS component setups. Make sure you have the right features configured before proceeding to create your model.

Additional Requirements for Redundant Foxboro DCS Systems

Foxboro DCS Systems also have the following requirements:

• The primary network must be used for communication between the AVEVA Batch Management clients and the AVEVA Batch Management Servers. The secondary network is used for the Foxboro DCS control and I/O network (the Mesh control network or the Nodebus). The secondary network is also used for AVEVA Batch Management Server communication functions, such as to communicate a heartbeat signal and to detect the heartbeat signal of its partner server.

• Hosts – The Hosts file contains Foxboro DCS network information. To ensure communications through NICs that are not on the Nodebus or Mesh network, do not make changes to the Hosts file.

• WINS – The WINS protocol must be unbound from the Nodebus or Mesh NIC.

Edit the Lmhosts File on Redundant Servers

The lmhosts file is located in the following folder on the servers: …\windows\system32\drivers\etc.

The lmhosts file contains any aliases and all network addresses of AVEVA Batch Management Servers.

You must edit the lmhosts file on each redundant server to prevent redundancy manager (RedMngr) from binding an improper IP address.

The names that you use to identify your redundant networks must be different from the computer names. In previous versions of the product, the primary network was identified by the network name of the computer. The only place that the network names should be used is in the host file.

The file content is the same for the master and backup computers. Note that the entries correspond to the entries in the RedCfg file. The #PRE entries cause the entries to be preloaded at system startup. Using #PRE entries is recommended for improved performance.

IP addresses and computer names shown here are examples.

10.40.20.75 BatchMaster #PRE

10.40.20.75 BatchManagement1 #PRE

10.199.199.9 BatchManagementA #PRE

10.40.20.55 BatchBackup #PRE

10.40.20.55 BatchManagement2 #PRE

10.199.199.8 BatchManagementB #PRE

10.40.20.65 RunClient1 #PRE

10.40.20.66 DevClient1 #PRE

10.40.20.67 HistoryServer #PRE

Example Redundant Server Architecture for Batch Management with Foxboro DCS

Use the following architecture example if you are creating a redundant system for AVEVA Batch Management with Foxboro DCS.

This information consists of specific examples for RedCfg and lmhosts files.

The following figure shows an example configuration for redundancy for Foxboro DCS systems.

RedCfg and Lmhosts File Examples

In the example shown in the previous figure, two computers, AW7003 and AW7004 represent a master server and a backup server.

The computer names and network IP addresses shown in this example are used as the entries in the RedCfg and lmhosts files. You must substitute the appropriate IP addresses and hostnames as defined by your system administrator.

NOTE: The RedCfg file is created automatically by the Configurator.

RedCfg File Example

The computer named AW7003 would have a RedCfg file as follows:

AW7004

<blank line>

\\AW7004\config_A\

<blank line>

AW7003PN

AW7003SN

AW7004PN

AW7004SN

<blank line>

The computer named AW7004 would have a RedCfg file as follows:

AW7003

<blank line>

\\AW7003\config_A\

<blank line>

AW7004PN

AW7004SN

AW7003PN

AW7003SN

<blank line>

In this example, the names AW7003PN, AW7003SN, AW7004PN, and AW7004SN are defined in the lmhosts file on each computer.

RedCfg File Structure

The RedCfg file has the following structure:

Line 1: The remote computer name

Line 2: Blank, not used

Line 3: The path to the remote computer config_A directory

Line 4: Blank, not used

Line 5: The local hostname for primary network

(cannot be a computer name)

Line 6: The local hostname for secondary network (blank if not used)

Line 7: The remote hostname for primary network (cannot be a computer name)

Line 8: The remote hostname for secondary network (blank if not used)

Line 9: Blank, not used

NOTE: The last line of the RedCfg file must be blank (that is, a carriage return.) The line numbers shown are for reference only. They are not actually entered in the file.

Lmhosts File

The lmhosts file contains the structure described below. The lmhosts file is located in the following folder on your computer:

C:\windows\system32\drivers\etc

The file is the same for all stations. Note that the names entered correspond to the entries in the RedCfg file. The #PRE entries cause the entries to be preloaded when your system is started. Using PRE entries is recommended for improved performance.

10.40.20.181 AW7003 #PRE

10.40.20.181 AW7003PN #PRE

151.128.8.65 AW7003SN #PRE

10.40.20.182 AW7004 #PRE

10.40.20.182 AW7004PN #PRE

151.128.8.66 AW7004SN #PRE

10.40.20.183 AW7005 #PRE

10.40.20.184 AW7006 #PRE

10.40.20.185 HistoryServer #PRE

Hosts File

The Hosts file contains Foxboro DCS network information and is located in the following folder on your computer:

C:\windows\system32\drivers\etc

You do not need to change the Hosts file because AVEVA Batch Management with Foxboro DCS components software does not use this file.