- summary Tunable configuration settings.
On start the Web application reads configuration data from the user home directory, i.e. the user executing the application. The stander spring context instruction is used to load the file:
Spring profiles are not used, the different configuration settings are just for automatic unit tests when building. Most of the parameters have default values, se further below for a description of all properties.
|| *Property name* || *Description* || *Type* || *Default Prod Value* || *Default Test Value* || || pr.commissionFile || Master data file || String (Filename) || || || || pr.commissionTypeFile || Master data file || String (Filename) || || || || pr.facilityFile || Master data file || String (Filename) || || || || pr.companyFile || Master data file || String (Filename) || || || || pr.careServiceFile || Master data file || String (Filename) || || || || pr.mekFile || Master data file || String (Filename) || || || || pr.hsfCodes || Company mapping of ids (code in master-data) to symbol || List of Strings (comma separated) || || || || pr.tioHundraCodes || Company mapping of ids (code in master-data) to symbol || List of Strings (comma separated) || || || || pr.indexFile || File name for local copy of index mapping file. || String (Filename) || || || || pr.ftp.cron || Schedule job for fetching master data. || Cron expression || || || || pr.ftp.script || Job script file to fetch master-data according to the schedule defined in || Shell script file|| || || || pr.ftp.localPath || Local path to execute script in (current working directory) and read master-data files from || String (Directory name) || || ||
Configuration file is located under
Configuration levels are described here.