This document explains how to enable logging for Workflow Tables impact and reorganizations.
Below is an explanation of how this is done when using the GeneXus IDE and also when using the Business Process Deployer.
Sometimes when we need to reorganize Workflow Tables or when we have to impact them, an error occurs showing no specific details. This may happen when a new Upgrade of GeneXus is installed. In such case, it is useful to enable the logging, and then look for errors in the .log file created, as follows:
It is as simple as enabling the Generator's logging. The logging properties can be found under Preferences by clicking on the corresponding Generator node.
For example, for a .Net environment:
The properties to be set for the Generator are:
Set the Generators 'Log level' property to value "All" (or any level desired) and execute the reorganization or impact.
Set property 'Log JDBC Activity' with value "Yes", and property "Detail" to the desired level, for example: "High", and then execute the reorganization or impact.
To do this we must run the Business Process Deployer as follows:
GXBPDeployer -netlogfile "C:\deploy.log" -netloglevel 0
netlogfile: defines the path to the JDBC log file. In the above example, all errors will be logged in the "C:\deploy.log" file.
netloglevel: defines the level of errors that will be logged. Possible values are:
0 - OFF
1 - FATAL
2 - ERROR
3 - WARN
4 - INFO
5 - DEBUG
6 - ALL
Execute 'GXBPDEployer.jar' using the following parameters, and use the deploy file created:
java -jar GXBPDEployer.jar -jdbclogfile "C:\deploy.log" -jdbclogdetail 0
jdblogfile: defines the path to the JDBC log file. In the example above, all errors will be logged in the "C:\deploy.log" file.
jdbclogdetail: defines the level of errors that will be logged. Possible values are:
0 - HIGH
1 - MEDIUM
2 - LOW