Overview of Configuration Files
This topic provides an overview of configuration files stored in the application-data and instance-data directories. The paths to the application-data directory and instance-data directories depend on your operating system.
Application-data directory
The application-data directory (table below) contains two configuration files (flowforceserver.ini and flowforceweb.ini) that enable you to configure global configuration settings (currently, the language used in server logs and in error messages).
FlowForce Server application-data directory (APPDATADIR) | |
|---|---|
Linux | /var/opt/Altova/FlowForceServer2025 |
macOS | /var/Altova/FlowForceServer2025 |
Windows | C:\ProgramData\Altova\FlowForceServer2025 |
Instance-data directory
The instance-data directory stores data generated by FlowForce Server and its users. This can be data related to jobs, triggers, system functions, server logs, and other files. The instance-data directory also contains two .ini configuration files. Administrators can edit the .ini configuration files with a text editor, as an alternative to changing settings from the Web Administration Interface, the Setup page, and from the Command Line Interface.
The instance-data directories shown below are default paths. You can also select your custom location of the instance-data directory via the FlowForce Server Setup page.
FlowForce Server instance-data directory (INSTANCEDIR) | |
|---|---|
Linux | /var/opt/Altova/FlowForceServer/data |
macOS | /var/Altova/FlowForceServer/data |
Windows | C:\ProgramData\Altova\FlowForceServer\data |
List of installed FlowForce instances
The flowforceinstances.json file contains a list of FlowForce instances that are managed by the FlowForce Server Setup page. The table below shows the path to this file on different operating systems. This file is for information purposes only.
File with the list of FlowForce instances (INSTANCELIST) | |
|---|---|
Linux | /var/opt/Altova/SharedBetweenVersions |
macOS | /var/Altova/SharedBetweenVersions |
Windows | C:\ProgramData\Altova\SharedBetweenVersions |
Contents of APPDATADIR
The list below summarizes the configuration files in the application-data directory.
flowforceserver.ini | Stores global configuration settings of FlowForce Server (currently, the language used in server logs and in error messages).
|
flowforceweb.ini | Stores global configuration settings of FlowForce Web Server (currently, the language of the Web administration interface).
Note: Do not confuse this file with the flowforceweb.ini file stored in the INSTANCEDIR directory (described below).
|
Contents of INSTANCEDIR
The list below describes the contents of the instance-data directory.
cache.db | This database file stores data related to the caching feature of FlowForce (see Cache Job Results).
|
state.db | This database file stores the volatile (that is, not configured) state of FlowForce.
|
ffweb.log flowforce.log | These files store the log of messages from FlowForce Web Server and FlowForce Server, respectively. This is applicable to Windows and macOS systems. On Debian, Ubuntu and CentOS or later, the log is written to the system log (/var/log/syslog).
|
flowforce.db | This database file stores the FlowForce Server object system, user data, active jobs, roles, and others.
|
flowforcelog.db | This database file stores the FlowForce Server logs.
|
flowforce.ini | This configuration file defines the port and listening interfaces of FlowForce Server. See also Instance Parameters in Configuration Files.
|
flowforceweb.ini | This configuration file defines the port and listening interfaces of FlowForce Web Server. See also Instance Parameters in Configuration Files.
|
files | Stores files associated with deployed functions.
|
logs | Contains captured output from job execution steps.
|
tmp | Stores temporary files.
|
tools | When other Altova server products (such as MapForce Server or StyleVision Server) are installed alongside FlowForce Server, this directory stores .tool files which enable FlowForce Server to work with these products. If this directory is empty, you can manually copy any tool files from the installation directory of the relevant product to this directory.
You may need to edit a .tool file to set environment variables that may be required to execute MapForce mappings and StyleVision transformations (see Environment Settings).
|