About Adding an iFIX Collector Instance

This topic provides guidelines on how to configure the iFIX collector using Configuration Hub based on the running mode of iFIX. It also describes the collector behaviour and recommended configuration in each case.
iFIX Running Mode Recommended Configuration for the iFIX Collector Collector Behaviour After You Add the Collector Instance

iFIX is running in service mode and is secured.

The iFIX Alarms and Events and the OPC Alarms and Events Servers are running as service.

 Configure the iFIX collector services under a user account under which iFIX is running as a service. While adding an instance of the iFIX collector or the iFIX Alarms and Events collector using Configuration Hub, select Service Under Specific User Account.
  • The iFIX collector starts running as a service. It appears in the collectors list in Configuration Hub.
  • You can run the collector at a command prompt using the Collector Start action. A shortcut is created in the Windows Start menu so that you can run the collector in the command-line mode.
  • By default, when not started as an SCU task, the iFIX collector points to the iFIX nodename. You must configure the iFIX node in the Collector Configuration section in Historian Administrator.

iFIX is running as a service and is not secured.

The iFIX Alarms and Events and the OPC Alarms and Events servers are running as service.

 You can configure the iFIX collector service using a local system account or a specific user account.
  • The iFIX collector starts running as a service.
  • You can run the collector at a command prompt using the Collector Start action. A shortcut is created in the Windows Start menu so that you can run the collector in the command-line mode.
  • By default, when not started as an SCU task, the iFIX collector points to the iFIX nodename. You must configure the iFIX node in the Collector Configuration section in Historian Administrator.
iFIX is not running as a service mode and is secured. Configure the iFIX collector services under a user account that is added in the IFIXUSERS group. Do not configure as a local system service. While adding an instance of the iFIX collector or the iFIX Alarms and Events collector using Configuration Hub, select Service Under Specific User Account.
  • Since Remote Collector Manager tries to start the collector as a service, and iFIX is not running as a service, an error message appears while adding a collector instance. However, the instance is configured successfully although it does not appear in the collectors list in Configuration Hub.
  • A shortcut is created in the Windows Start menu so that you can run the collector in the command-line mode, and the related registry folder is created.
  • You must start the collector manually for the first time using the shortcut. It will then connect to the Historian server, and it will then appear in the collectors list in Configuration Hub.
  • Once connected to server, you can start/stop it at a command prompt.
iFIX is not running as a service mode, and is not secured. You can configure the iFIX collector service using a local system account or a specific user account.
  • Since Remote Collector Manager tries to start the collector as a service, and iFIX is not running as a service, an error message appears while adding a collector instance. However, the instance is configured successfully.
  • A shortcut is created in the Windows Start menu so that you can run the collector in the command-line mode, and the related registry folder is created.
  • You must start the collector manually for the first time using the shortcut. It will then connect to the Historian server.
  • Once connected to server, you can start/stop it at a command prompt.
iFIX is not running. You can configure the iFIX collector service using a local system account or a specific user account, as per the security configuration of iFIX.
  • Since Remote Collector Manager tries to start the collector as a service, and iFIX is not running as a service, an error message appears while adding a collector instance. However, the instance is configured successfully although it does not appear in the collectors list in Configuration Hub.
  • A shortcut is created in the Windows Start menu so that you can run the collector in the command-line mode, and the related registry folder is created.
  • After you start iFIX, you must start the collector manually for the first time using the shortcut. It will then connect to the Historian server.
  • Once connected to server, you can start/stop it at a command prompt.