FlowForce Server Application Data
This topic describes the contents of the FlowForce Server application data directory. This information can be useful during manual data migration to a major FlowForce Server version or if you want to change some of the FlowForce Server configuration settings by editing .ini files.
The application data directory stores data generated by both FlowForce Server and its users, such as jobs, triggers, system functions, server logs, and other files.
The application data directory also contains several .ini style 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, or from the Command Line Interface.
The path to the application data directory depends on the operating system and platform and is as follows.
The following table lists the main files and folders in the application data directory.
Stores global configuration settings of FlowForce Server (currently, the language used in server logs and in error messages).
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 data directory (described below).
This database file stores data related to the caching feature of FlowForce (see Caching Job Results ).
This database file stores the volatile (that is, not configured) state of FlowForce.
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 ).
This database file stores the FlowForce Server object system, user data, active jobs, roles, and others.
This database file stores the FlowForce Server logs.
This configuration file defines the port and listening interfaces of FlowForce Server. See also Configuration File Reference.
This configuration file defines the port and listening interfaces of FlowForce Web Server. See also Configuration File Reference.
Stores files associated with deployed functions.
Contains captured output from job execution steps.
Stores temporary files.
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 copy manually any tool files from the installation directory of the respective product to this directory.
You may need to edit a .tool file in order to set environment variables that may be required to execute MapForce mappings or StyleVision transformations (see Environment Settings).