With the new xFlow interface available, there may exist concerns that would warrant additional logging to be turned on to assist in troubleshooting a case.
This document describes the most effective ways in which one can increase logging to debug or trace levels for the xFlow microservices
CA Service Management 17.1 and higher
To turn on the logging:
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<!-- Set logging for all Akka library classes to INFO -->
<logger name="akka" level="INFO" />
<logger name="play" level="DEBUG" />
<logger name="application" level="DEBUG" />
<!-- Set logging for all Akka library classes to INFO -->
<logger name="akka" level="DEBUG" />
<root level="INFO">
<root level="DEBUG">
Additionally, Bop_logging on domsrvr/virtdb may also be needed, and is done separately, ie, from an admin command prompt, run these two bop_logging commands:
bop_logging domsrvr -f $NX_ROOT\log\domsrvr.out -n 10 -m 20000000 ON
bop_logging bpvirtdb_srvr -f $NX_ROOT\log\bpvirtdb.out -n 10 -m 20000000 ON
The above bop_logging commands will take effect immediately. One does not need to cycle xFlow or any other Services for bop_logging to take effect.
To turn off the logging:
The above items are provided for informational purposes. We do not advise turning on any sort of additional logging without first consulting with Support to see what is required to troubleshoot a given issue. If logging is improperly turned on, performance issues and other such concerns may arise, potentially causing more problems with the application, and possibly leading to the application becoming unusable.