Please enable JavaScript to view this site.

Altova FlowForce Server 2020 

When other Altova servers are installed alongside FlowForce Server, a file with the .tool extension is installed as well for each executable tool that runs under FlowForce Server management. FlowForce Server scans the DATADIR\tools and INSTALLDIR\tools directories for .tool files, with the former directory taking precedence over the latter.

FlowForce Server application data directory (DATADIR)

Linux

/var/opt/Altova/FlowForceServer2020/data

macOS

/var/Altova/FlowForceServer2020/data

Windows

C:\ProgramData\Altova\FlowForceServer2020\data

 

FlowForce Server installation directory (INSTALLDIR)

Linux

/opt/Altova/FlowForceServer2020/

macOS

/usr/local/Altova/FlowForceServer2020/

Windows

C:\Program Files\Altova\FlowForceServer2020\

C:\Program Files (x86)\Altova\FlowForceServer2020\

 

The DATADIR\tools directory is normally empty, and it is where you place any customized tool files, while the installation process manages the INSTALLDIR\tools directory and the tool files contained therein must not be edited.

 

Application pools

For every found .tool file (identified by name), FlowForce Server creates an application pool. Application pools, therefore, group running tool process instances, and FlowForce Server will manage those instances as configured in the tool files.

 

When FlowForce enforces the rules regarding the lifetime of tool process instances, all these events may produce informational messages in the log, for example:

 

Starting instance {id} of {tool} for {session}.

Starting {commandline}.

Instance {id} of {tool} for {session} is now idle.

Shutting down instance {id} of {tool} for {session}; sitting idle for too long.

Shutting down instance {id} of {tool} for {session}; maximum reuse count reached.

Instance {id} of {tool} for {session} unexpectedly ceased communication.

Instance {id} of {tool} for {session} attached to job instance {instanceid}.

 

The info messages listed above do not indicate licensing or queueing issues. Instead, they make it possible to track down potential problems, for example, by offering information about processes that were running at a particular time. Note that, if steps or jobs fail, this will produce a separate log message.

 

Tool file configuration

Although it is not always necessary, tool files can be edited. Specifically, they provide the following configuration options:

 

1.The executable path, under the [Tool] section. Changing this path might be necessary in certain cases, when you would need to make .tool files of older versions execute newer versions, or vice versa.

2.The [Environment] section. You can add or edit this section in order to define environment variables required by the tool, see Setting Environment Variables.

 

Important:

 

Do not change any tool file settings other than the ones mentioned above, unless advised by Altova Support.

It is not possible to define custom tools.

© 2020 Altova GmbH