Configure the Batch Management Server

You can configure the AVEVA Batch Management Server with the redundancy support enabled or disabled. Before configuring the AVEVA Batch Management Server, the Configurator checks whether a supported operating system is installed.

When you configure the AVEVA Batch Management Server feature, the Configurator does the following:

• Creates the environment variables.

• Creates the Config_A folder. If redundancy support is enabled, the Config_A share folder is created.

• Creates the AVEVA Batch Management share folder if redundancy support is enabled.

• Creates the RedCfg file if redundancy support is enabled. The details of the primary and secondary redundant server are updated in the file.

• Updates the Windows services file with AVEVA Batch Management TCP/IP application ports and exceptions.

• Registers the AVEVA Batch Management Server dll components.

• Updates the Windows firewall settings for AVEVA Batch Management Server node.

• Starts the Middleware Host service.

• Starts the Batch Management Web Server service. By default, the Service Status is "Running" and the Startup Type is "Manual". However, the Startup Type changes to "Automatic" while configuring the AVEVA Batch Management Server feature.

• Adds the AVEVA Batch Management web client site name (https://<MachineName> and https://<MachineName with full domain name>) to the trusted sites, if the the SSL Certificate is issued to the MachineName.

• Updates the AVEVA Batch Management Server input values in Windows registry.

• Creates a shortcut for Environment Display on the Start menu.

• Creates a shortcut for AVEVA Batch Management web client on the Start menu.

• Optionally configures the server to enable ArchestrA Alarms and Events.

Batch Events Prerequisites

You must have the following prerequisites to enable Batch Events:

• System Platform 2014 R2 runtime (or greater) must be installed on the AVEVA Batch Management Server and an ArchestrA Platform must be deployed before selecting the Batch Event check box. Also, the “AVEVA Batch Management Components for ArchestrA IDE” feature must be installed on the Galaxy Repository/Service Repository node before configuring Batch Events. For more information on the minimum supported version of System Platform, see Batch Management Readme.

• For advanced configuration or manual configuration of the Event Service on the AVEVA Batch Management Server, the ArchestrA IDE can be used to “Configure ArchestrA Services”. The “AVEVA Batch Management Components for ArchestrA IDE” feature must be installed on the ArchestrA IDE node to enable editing of the Event Service. Advanced configuration allows the Event Service port or cache size to be changed.

  IMPORTANT:
  - Batch Events must be reconfigured following an upgrade of App Server.
  - During network failures on AVEVA Batch Management Server node, the AVEVA Batch Management services will likely go to unknown state. As a precaution, install and configure Microsoft Loopback adapter on the AVEVA Batch Management Server node so that AVEVA Batch Management services will be in running state and there will be no interruption for batch execution.

To configure the Batch Management Server without Redundancy Support

1. Open the Configurator.

2. Click General in the left pane, clear the Enable Redundancy Support check box in the Settings area, and then click Configure.

3. Click Server in the left pane. The configuration options appear in the right pane.

   

4. In the System Configuration area, you can configure the following:

   1. Enter the IP address or the name of the computer, on which you have installed the AVEVA Batch Management History Server, in the History Server Node Name box. For more information on the computer naming conventions, refer to the Host Name Naming Conventions topic.

   2. Enter the name of the computer, on which you have installed the reporting components, in the Reporting Content Node Name box. The name cannot be an IP address or localhost and must match the "Issued To" property of the SSL certificate that was used when installing Reporting Content. This is usually the server name or a fully qualified server name. For more information on the computer naming conventions, refer to the Host Name Naming Conventions topic.

5. Select the Share AVEVA Batch Management Folder for Remote Development Clients check box to use the AVEVA Batch Management Remote Development Client. This shared folder is only available to the current logged user with 'Full Control' permissions. After creating the share, you may manually add user permissions (and provide Full Control) for any user you want to be able to access the share.

6. In the SSL Certificate area, select the certificate from the Name list. You must use the same certificate as specified under the Certificates area while configuring the Certificates option.

7. (Optional) If you want to use Batch Events, you can configure it at this point. If you do not want to use Batch Events, proceed to step 8.

   To configure Batch Events, you can configure the following:

   NOTE: The AVEVA Batch Management Server must meet the prerequisites described in "Batch Events Prerequisites".

   To configure Batch Events, you can configure the following:

8. Select the Batch Events check box.

9. Enter the name of the Galaxy Repository/Service Repository computer in the GR Node Name box.

10. Enter the name of the Galaxy whose Platform was deployed locally in the Galaxy Name box.

NOTE: If you enter an invalid Galaxy name, Batch Events may still be configured successfully, but your Event Service will not be visible in the Configure ArchestrA Services editor of any Galaxy.

11. Click Configure. A green check icon appears in the left pane when AVEVA Batch Management Server is successfully configured.

To configure the Batch Management Server with Redundancy Support

9. Open the Configurator.

10. Click General in the left pane, select the Enable Redundancy Support check box in the Settings area, and then click Configure.

11. Click Server in the left pane. The configuration options appear in the right pane.

    

    NOTE: To enable redundancy support, the computer on which you are configuring AVEVA Batch Management Server must have at least two network interface cards. Otherwise, the Local Host Name of Secondary Network and the Remote Host Name of Secondary Network fields are disabled in the Configurator. If you continue with the configuration, the AVEVA Batch Management Server will function as Master with invalid backup.

12. In the Redundant System Configuration area, you can configure the following:

    1. Enter the IP address or the name of the other AVEVA Batch Management Server in the Remote Server Node Name box.

    2. Enter the IP address or the name of the computer, on which you have installed the AVEVA Batch Management History Server, in the History Server Node Name box. For more information on the computer naming conventions, refer to the Host Name Naming Conventions topic.

    3. Enter the name of the computer, on which you have installed the reporting components, in the Reporting Content Node Name box. The name cannot be an IP address or localhost and must match the "Issued To" property of the SSL certificate that was used when installing Reporting Content. This is usually the server name or a fully qualified server name. For more information on the computer naming conventions, refer to the Host Name Naming Conventions topic.

    4. Enter the IP address or the name of the remote web server in the Remote Web Server Name box.

13. Select the Share Batch Management Folder for Remote Development Clients check box to use the Batch Management Remote Development Client. This shared folder is only available to the current logged user with 'Full Control' permissions. After creating the share, you may manually add user permissions (and provide Full Control) for any user you want to be able to access the share.

14. In the Redundant Network Configuration area, you can configure the following:

    1. Enter the logical host name of the primary network on the local AVEVA Batch Management Server in the Local Host Name of Primary Network box.

    2. Enter the logical host name of the secondary network on the local AVEVA Batch Management Server in the Local Host Name of Secondary Network box.

    3. Enter the logical host name of the primary network on the remote AVEVA Batch Management Server in the Remote Host Name of Primary Network box.

    4. Enter the logical host name of the secondary network on the remote AVEVA Batch Management Server in the Remote Host Name of Secondary Network box.

    NOTE: If you reconfigure AVEVA Batch Management Server, ensure that the Middleware Host service is not running.

15. In the SSL Certificate area, select the certificate from the Name list. You must use the same certificate as specified under the Certificates area while configuring the Certificates option.

16. (Optional) If you want to use Batch Events, you can configure it at this point. If you do not want to use Batch Events, proceed to step 9.

    NOTE: The AVEVA Batch Management Server must meet the prerequisites described in "Batch Events Prerequisites".

    To configure Batch Events, you can configure the following:

    1. Select the Batch Events check box.

    2. Enter the name of the Galaxy Repository / Service Repository computer in the GR Node Name box.

    3. Enter the name of the Galaxy whose Platform was deployed locally in the Galaxy Name box.

    IMPORTANT: If you enter an invalid Galaxy name, Batch Events may still be configured successfully, but your Event Service will not be visible in the Configure ArchestrA Services editor of any Galaxy.

17. Click Configure. A green check icon appears in the left pane when AVEVA Batch Management Server is successfully configured.