...
Field | Description |
---|---|
Import File Location | The default base directory path for files to be imported into Geneva. This field can be left blank. See File Collectors for further details. |
Export File Location | The default base directory path for files to be exported into Geneva. This field can be left blank. See File Exporters for further details. |
Template Location | The location templates when doing excel downloads. |
Archive Directory | The default base directory path for data to be archived. This field can be left blank. |
Restore Directory | The default base directory path for data to be restored from. This field can be left blank. |
Application Location | The location of the PhixFlow installation. |
Plugin Location | The location of any PhixFlow plugin applications. |
Temporary File Location | The location of any PhixFlow temporary files that are generated. |
Performance File Location | The location of the resultant analysis performance files when the system tuning 'Generate Performance Files' check box has been ticked. |
Restricted Directory | The root directory path that all files read using File Collectors must reside under. Note that this value is not editable through the GUI and must be set directly within the database. |
File Upload Directory | The root location of all uploaded files and all processed incoming email's.The sub directory structure of the resultant (uploaded files/processed email's) is the following:- Uploaded Files: /FileCollector Name/in/YYYYMMDD/UniqueId/ where YYYYMMDD represents received email messages. Uploaded files/processed emails are saved in standard sub-directories as follows: .../tag/in/yyyymmdd/uid/ where tag is the File Collector tag or the #tag extracted from an email subject line, or default yyyymmdd is the date the files were uploaded and UniqueId is a 32 character unique identifier.Incoming Email's: /YYYYMMDD/EmailId/ where YYYYMMDD represents the date the email was read and processed by PhixFlow and EmailId / received uid is a 32 character unique emailidentifier .For Email's each EmailIdeach Eemail message received, the folder will contain a file called body.txt representing the main body content of the email and also any corresponding email attachments. |
System Tuning tab
The following fields are configured on the System Tuning tab:
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Thread Pool Size | The number of threads that can be in the pool at any time. This is an advanced option which should not be updated without advice from the PhixFlow support team. This is generally a small multiple of the number of CPU cores on your machine. | ||||||
Write Processes Per Stream Set | This is an advanced tuning feature which enables PhixFlow to multi-thread the process of writing Stream Data to the database. The value of this parameter is dependent upon machine versus database performance. | ||||||
Database Flush Size | Defines how frequently objects are written to disc. This is an advanced option which should not be updated without advice from the PhixFlow support team. | ||||||
Delete Batch Size | Defines the default number of rows to be deleted from a Stream in a single transaction when Archiving or Rolling back data. This is an advanced option which should not be updated without advice from the PhixFlow support team. | ||||||
Default Page Size | Defines the default number of rows to be loaded into to a grid when displayed in PhixFlow. This is an advanced option which should not be updated without advice from the PhixFlow support team. After changing this field you will need to restart the browser or reload the application (User → Reload Application) to apply the new default page size. | ||||||
Maximum Page/Chart Size | This value defines the largest number of records that can be downloaded from a chart in a single file. Downloads with more than this number of records will be split into multiple files which are zipped together. | ||||||
Default Buffer Size | When reading in data from a collector, this defines how many rows are held in memory before passing them on for processing. This means that if PhixFlow is reading in 10,000,000 records, it doesn't have to wait until all have been loaded before it begins to process them, but can begin processing after the first 2000 have been read. This is an advanced option which should not be updated without advice from the PhixFlow support team. | ||||||
| If checked, the Pipe Cache sizes below, and per Pipe, are strictly enforced; a pipe lookup which tries to cache too many records will fail and an error will be reported. If not checked, exceeding the cache size on a pipe will result in a warning message. | ||||||
Default Pipe Cache Size | This value is used when a pipe's cache size has not been set. | ||||||
Max Pipe Cache Size | This value is the maximum value that Cache Size can be set to on any pipe; a pipe with a Cache Size greater than this will generate a run-time error. | ||||||
Result Expiry Time (sec) | The length of time the PhixFlow front end application will wait for a result from an asynchronous query before abandoning it. This is an advanced option which should not be updated without advice from the PhixFlow support team. | ||||||
Maximum File Size Attachment (MB) | Outgoing Email's will only attach files (zipped or unzipped) that do not exceed this configuration limit. An extra message will appear in the email's message subject/body indicating to the recipient that a file attachment has been removed due to this size restriction. PhixFlow will not impose any upper limit to the size of the attached files if this field is left blank, hence in this case the underlying email servers will determine if the message is sent/received correctly or not. | ||||||
Maximum Exporters Errors | If required, you can set the maximum number of errors found, before exporters will stop attempting to export records. This is useful where you process large number of records and do not want to wait until all records are processed in case of errors occurred. This value can be overridden in Exporters. | ||||||
Generate Performance Stats | If checked, PhixFlow will generate performance statistics whilst the analysis engine is running. | ||||||
Log Statistics to File | If checked, logging is enabled and Processing Statistics are written to file. | ||||||
Stats File Logging Seconds | A period in seconds controlling how often statistical data is written to file. | ||||||
Log Statistics to DB | If checked, logging is enabled and Processing Statistics are written to the database. See Processing Statistics for further detail. | ||||||
Stats DB Logging Seconds | A period in seconds controlling how often statistical data is written to the database. |
...
Field | Description |
---|---|
Default Domain | The default Domain which will be initially selected on the login screen. |
Active Directory Login Group | Names of Active Directory Groups whose members are allowed to log in into the PhixFlow. Names can be separated by a semicolon. Use {instance} to include the PhixFlow instance name. |
Form Icons
...
The form provides the standard form icons.
...