Enabling application-specific logging in Process Designer

You can enable application-specific logging to redirect script log messages to unique files for easier troubleshooting and debugging of your process applications in Business Automation Workflow.

About this task

Application-specific logging redirects script log messages to unique files, making it easier to isolate and analyze logging output for specific process applications. When you enable application-specific logging, you can specify a custom file name and set the logging level to control the amount of detail captured in the log files.

Application-specific logging redirects script log messages to files outside SystemOut.log. You can use a separate log file for each process application, or you can use the global fallback logger that is defined in 100custom.xml.

In the <process-apps-logging-config/> section of 100custom.xml, administrators can configure the fields that control process application logging, including the base file path where separate log files are created and whether the global fallback logger is enabled. The base file path is required for both per-process-application log files and the global fallback logger.

Enabling the global logger does not affect per-process-application loggers. If application-specific logging is enabled in Process Designer for a process application, that process application writes to its own log file. If application-specific logging is disabled for a process application, and the global logger is enabled in 100custom.xml, that process application writes to the shared global log file instead of to its own log file.

To enable application-specific logging for a process application:

Procedure

  1. Open the process application in Process Designer.
  2. Click the Overview tab.
  3. In the Custom logging section, select the Custom logging enabled checkbox.
  4. In the File name field, enter a name for the custom log file.
    The file name you specify is used to create the log file where script log messages are redirected. For example, if you enter T11.log, script log messages are written to a file named T11.log.
  5. From the Log level list, select the logging level.
    The log level determines the amount of detail captured in the log file. Available log levels include:
    • INFO - Captures informational messages, warnings, and errors
    • WARNING - Captures warning messages and errors
    • ERROR - Captures only error messages
    • DEBUG - Captures debug messages
  6. Save your changes.

Results

Application-specific logging is enabled for the process application. Script log messages are now redirected to the specified log file at the configured logging level.