The trace method of the BCGUtil class in the com.ibm.bcg.bcgdk.common package is used to set up logging of internal activity for the entire document flow. Full documentation of the method is located in BCGUtil. The following is an example code snippet that sets up logging in an XML translation step in variable workflow:
BCGUtil bcgUtil = new BCGUtil (); : : : bcgUtil.trace(BCGUtil.BCG_TRACE_SEVERITY_DEBUG, "CustomXMLTranslation", "The Schema is present", null)
Receiver logs can be found at:
ProductDir/was/profiles/bcgreceiver/logs/bcg_receiver.log
Fixed and variable workflow and sender logs (grouped together
as part of the Router component) can be found at:
ProductDir/was/profiles/bcgdocmgr/logs/bcg_router.log
By default, debug logging is not enabled. To turn it on, a property
in the log4j properties file must be set. The properties file for
receivers can be found at:
ProductDir/receiver/lib/config/receiver-was.logging.properties
The properties files for router components can be found at:
ProductDir/router/lib/config/router-was.logging.properties
In both cases, the property that needs to be set is the log4j.rootCategory property. By default this is set at error, RollingFile. This value needs to changed to debug, RollingFile. For the change to be effective, you must restart the server.