Configuration requirements

PI AF collectives have the following configuration requirements:

• PI AF collectives are supported for PI AF 2.1 or later.

• The PI AF application service computers must be in a domain; workgroups are not allowed.

• The PI AF application service version must be the same on all PI AF collective computers.

• The PI AF collective consists of at least two PI AF servers (machine hosting PI AF application service). The PI AF client is not required on either PI AF server, but If you install it, your work with PI AF will be more convenient.

• The PI AF SQL database on the primary and secondary servers must have the same name. By default its name is PIFD.

• The Named Pipes and TCP/IP protocols must be enabled for the instances where the PI AF SQL databases are installed.

• Using a Clustered PI AF server as the Primary collective member can cause issues with the Host value. The AF Cluster name assigned as the Host value is not persisted. Ultimately, this may cause connection issues. To correct the issue, change the value assigned to the "reportIPaddress" setting in the AFService.exe.config file from its default setting of "false" to the AF Cluster's IP address:

  Default Value for reportIPAddress	Using AF Cluster's IP Address for reportIPAddress
  <add key="reportIPAddress" value="false"/>	<add key="reportIPAddress" value="192.168.255.255"/>