Body

Version 9.4 offers enabling various traces for application components using a script from the command line. This script allows to turn ON and OFF tracing for various components and specify tracing levels.

Until now, application components could be traced using the System Management Console or the API tester using midifyTraces
Typical scenario to generate traces is that the logs are needed at a specific time for a specific amount of time. The new script manageTraceableComponent.sh will turn ON/OFF tracing for the components mentioned in the command line.

This script would allow only one traceable component at a time. The script can be triggered using the following format -
manageTraceableComponent.sh -Action ADD -Type API -Level DEBUG -Name createOrder
manageTraceableComponent.sh -Action DELETE -Type API -Level DEBUG -Name createOrder

Wrapper scripts can be created for each of the traceable components to be scheduled, either for enabling tracing or for  disabling. CRON jobs can also be configured to run this scripts for a particular schedule to help capture the logs for the required duration.

For instance, a script startScheduleOrderAgentTracing.sh can be created with the following content-
${INSTALL_DIR}/bin/manageTraceableComponent.sh -Action ADD -Type AGENTS -Level DEBUG -Name SCHEDULE_ORDER_E1 -ServerName OrderAgentServer

Similarly another script stopScheduleOrderAgentTracing.sh can be created with a similar content to stop the tracing.
${INSTALL_DIR}/bin/manageTraceableComponent.sh -Action DELETE -Type AGENTS -Level DEBUG -Name SCHEDULE_ORDER_E1 -ServerName OrderAgentServer