<< Click to Display Table of Contents >>
Configuring Properties |
The Ada tab contains specific configurations for this Driver.
Ada Tab
The available options on this tab are described on the next table.
Available options on the Ada tab
Option |
Description |
---|---|
Login URL |
URL of the login to the Stattus4 Ada system |
Realm |
Complement to the login, which must include the name or identifier of the authentication domain (Realm) |
Client Id |
Login name of the Stattus4 Ada system |
Client Secret |
Password for the login |
API URL |
URL of the Stattus4 Ada system's REST API where the web services are located |
The Setup tab contains general configurations for this Driver. This tab is divided into the following groups:
•General configurations: Configurations of a Driver's physical layer, time-out, and initialization mode (have no effect for this Driver)
•Connection management: Configurations on how a Driver keeps a connection and which recovery policy is used on failure (have no effect for this Driver)
•Logging options: Controls the generation of log files
Setup tab
General options on the Setup tab
Option |
Description |
---|---|
Physical Layer |
For this Driver, the only option available is None, that is, no physical interface is available |
Timeout |
This option has no effect for this Driver |
Communication check time |
This option has no effect for this Driver |
Start driver OFFLINE |
This option has no effect for this Driver |
Options on the Connection management group
Option |
Description |
---|---|
Mode |
This option has no effect for this Driver |
Retry failed connection every ... seconds |
This option has no effect for this Driver |
Give up after ... failed retries |
This option has no effect for this Driver |
Disconnect if non-responsive for ... seconds |
This option has no effect for this Driver |
Options on the Logging Options group
Option |
Description |
---|---|
Log to File |
Enable this option and configure the name of a file to write a log. Log files can be large, so use this option for short periods of time, only for testing and debugging purposes. If the %PROCESS% macro is used in the log file name, it is replaced by the identifier of the current process. This option is particularly useful when using several instances of the same Driver in Elipse E3, Elipse Power, or Elipse Water, thus allowing each instance to generate a separate log file. For example, when configuring this option with value "c:\e3logs\drivers\ada_%PROCESS%.log", it generates a file named c:\e3logs\drivers\ada_00000FDA.log for process 0FDAh. Users can also use the %DATE% macro in the file name. In this case a log file is generated every day, in the format aaaa_mm_dd. For example, when configuring this option with value "c:\e3logs\drivers\ada_%DATE%.log", it generates a file named c:\e3logs\drivers\ada_2005_12_31.log in 12/31/2005 and a file named c:\e3logs\drivers\ada_2006_01_01.log in 01/01/2006. Similarly, the %DATE_HOUR% macro generates one log file per hour, in the format aaaa_mm_dd_hh |
File size limit (MB) |
Configure the size limit of a log file, in megabytes. A value equal to 0 (zero) means that there is no size limit for a log file |