Versions Compared

Old Version 7

changes.mady.by.user Ian Crawford

Saved on

compared with

New Version 8

changes.mady.by.user Ian Crawford

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FieldDescription
System LanguageThe system language code specifies which language should be used for login screens and for all non interactive messages.
Default Character SetThe character set PhixFlow assumes when reading from or writing to any plain text or CSV file. Please note that this must be a character set supported by the Java virtual machine and that multi byte settings such as UTF8 (e.g. for Japanese etc.) are supported.
Line Separator StyleThe user can specify a default line separator style that will be used by File Exporters where no particular line separator has been specified. If the user does not specify a default style here then the default will revert to be the default of the operating system on which the PhixFlow server is running. In addition you can specify the line separator on each file exporter where a particular exporter needs to use a style other than the system default.
Data Storage GroupThe Data Storage Group to use when creating tables to store Stream data. This field is interpreted differently depending on the underlying database:
On Oracle, a Data Storage Group is equivalent to a Tablespace.
On SQL Server, a Data Storage Group is equivalent to a Filegroup.
If no Data Storage Group is specified, the database user's default setting will be used.
Default Stream StorageThis specifies the default Storage Type when creating a new Stream.
  • Database: Store the data in a regular table within the PhixFlow database. This is the most common option
  • Database (Partitioned): Store the data in a partitioned table within the PhixFlow database. This option provides improved performance for rollback and archiving of very large Streamsets. The option is only available if "partitioning" is available within your database installation.
  • In Memory: Data for the Stream will not be written to the database. This option can be used (for example) when you want to aggregate large amounts of unsorted data which can then be written to a stored Stream.
Effective DateEffective date to be used when date override is in use.
Schema VersionRead only: the version of the schema currently installed.
Licence KeyThis is the Licence Key for your PhixFlow Installation which is provided by PhixFlow Customer Support. If PhixFlow is not configured with a valid key, analysis tasks will not run and an error message will be displayed in the log file.

A Licence key can sometimes be associated with an expiry date. If the licence has expired an additional field will show the expiry date. After a licence has expired PhixFlow will generate warning messages in the analysis logs for 28 days beyond the expiry date. After this time analysis tasks will cease to run.

Delete Log Messages after Days

If this field is set, a System Task, when run, deletes Log Messages and Managed Files for Log Files older than this number of days.

See Task Plans for how to set up and run a System Task.

Archive deleted log messages to file

Whether to archive Log Messages to file before deletion. Archived Log Messages are written to archive files in the Archive Directory (see above).

There is no option to archive Managed File entries to file before deleting them.

Default Password PolicyThe password policy selected by default when creating new users. Password Policies can be edited in the Password Policies List
Allow Reset Configuration

Before performing a 'Reset Configuration' the administrator must tick this checkbox to allow access to reset the configuration.

WARNING: Resetting the configuration will delete all configuration data in the PhixFlow Instance.

See Configuration Reset for how to reset the configuration

...