Please enable JavaScript to view this site.

Altova FlowForce Server 2020 

FlowForce Server provides a logging mechanism to register all kinds of events and the time when they occurred (such as job outcome events, configuration change events, errors, and so on). You can view all the log events from a dedicated page, see Viewing the Job Log. Note that the log events can significantly increase the size of the FlowForce Server internal database over time. For this reason, the log must be periodically archived or cleaned up using the archive-log or truncate-log /system/maintenance functions.


The logging that takes place in FlowForce Server can be of two types:


1.Default system logging that does not require manual intervention of any kind. This kind of logging is taken care of by the system and does register all events, but keeps the size of each log record up to a certain limit, for better system stability and performance. If the system logging does not provide enough level of detail, or if you find out that log entries (such as parameter values in steps) are truncated because they are too long, you can use explicit logging, as described next.

2.Optional (explicit) logging that you can enforce from the job configuration page. The job configuration page provides a Log ff_ic_log button that you can optionally enable next to each parameter which you are interested to track in the log. Doing so will log the full value of that parameter when the job runs. In addition, you can embed any FlowForce expression inside the log expression function in order to request that that expression be logged explicitly. Again, this will log the expression in full and its value will not be truncated. FlowForce Server does not limit the size of entries logged as a result of explicit logging.


If you do not want to use explicit logging for whatever reason, you can alternatively change the default size of log entries maintained by the system.


Changing the default log size to a higher value may impact system stability and performance, so exercise this option carefully. The recommended approach is to use explicit logging, as mentioned above.


To change the default size of log entries:


1.Log on to the FlowForce Web administration interface.

2.Go to Administration | Settings and change the parameters grouped under "Logging limits".


Notice that there are two kinds of logged entries: string types and list types. Consequently, there are two parameters to control the size of each type.


Default string value logging limit

Specifies the default length of log entries that are of type "string". If a log entry exceeds this value then long arbitrary values such as file paths will be truncated.

Default list value logging limit

Same as above, applies to log entries that are of type "list".

Recurse into sublists

This setting affects jobs which operate on lists that contain other lists as children. Set this value to instruct FlowForce to look N levels deep for logging purposes.

© 2020 Altova GmbH