Skip to Content

Logging tab of the Activity Property panel

In addition to the default information that is collected in the processes.log when you execute a process, you can specify information to be logged for each activity in the process. When you test the process in the BMC Atrium Orchestrator Development Studio application, the log entries for the activity are written to the console window and to the processes.log file on the computer where BMC Atrium Orchestrator Development Studio is installed. When the process is executed on the grid, the entries are written to the processes.log file on the peer that executes the process.

By default, when the BMC Atrium Orchestrator product runs a process on the grid, it logs only process starting and ending information. However, you can use the Logging tab to configure logging for additional information about each activity in the process.

The Logging tab enables you to configure process log messages to write before, after, or before and after the activity executes. The log message can include static text as well as the value of one or more designated context items at the time of the activity's execution.

When processes are run on the grid, the log levels indicate the priority, or urgency, of the message. The for levels, in ascending order of priority are: debug, info, warn, and error. The log messages for an activity are written to the log only when the activity log level priority is greater than or equal to the logging level set for the grid where the process is executed. For example, if you set the log level for the activity at info, the message will be written to the executing peer's processes.log file if the logging level for the grid is set to debug or info, but not if the logging level for the grid is set to warn or error.

Warning

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

When processes are tested in BMC Atrium Orchestrator Development Studio, all configured log messages are written to the console window and to the processes.log on the computer where BMC Atrium Orchestrator Development Studio is running.

Warning

Best practice

While developing a workflow, log the following items to assist with troubleshooting:

  • adapter requests
  • adapter responses
  • the value of context items before and after they are changed
  • the results of any complicated transform


This section contains the following topic:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

(archive) BMC Atrium Orchestrator Platform 7.6.03