Edit general information for an IDAS

To edit general information

1. In the Operations Control Management Console tree, expand a server group, and then expand a server.

2. Expand Configuration Editor, expand System Configuration, and then expand Data Acquisition.

3. Right-click the name of the IDAS to edit, and then click Properties. The Properties dialog box appears.

4. Click the General tab.

   

5. To change the name of the computer on which the IDAS runs, click Modify and then type the new name in the IDAS Node box. If you are creating a new IDAS definition or modifying an existing one, make sure that the IDAS software is installed on the target computer.

   Note: If the target IDAS node is also a Historian node, it does not work as a remote IDAS. Choose a node that has the IDAS software installed, but without the Historian Server software installed.

6. Specify the failover or store-and-forward option:

   • If you don’t want to use failover or store-and-forward, select No Failover or Store/Forward.

   • To specify a backup IDAS, select Failover Node.

     Enter the name of the computer on which the redundant IDAS runs. You must use the fully qualified name of the computer, or the IP address. Verify that the IDAS software is installed on the target failover computer. If the failure of the primary IDAS is detected by the system, the failover IDAS is automatically started. The failover IDAS is shut down after the primary IDAS is back online.

     Note: Failover is only supported with remote IDAS versions prior to 2023.

   • To enable store-and-forward, select Store/Forward Path.

     Enter an absolute path (for example C:\IDASStoreForward). The Store/Forward Path is used to cache metadata about historized tags. Additionally, when communications to the Historian server are interrupted, it’s used to historize the data. Always use the same store/forward path for the same IDAS; changing the path might leave behind unprocessed data that has not yet been sent to the Historian.

     If the IDAS is on the same physical computer as the Historian, the InSQLConfiguration virtual service account must have full file system permissions on this folder. If this is a remote IDAS, the aahSupervisor virtual service account must have full file system permissions on this folder.

     If the Store/Forward Path is incorrect, or the permissions are not set correctly, the store-and-forward functionality will fail.

7. Click OK.