Working with Log Files

The Integration Service writes the workflow and session logs as binary files on the node where the service process runs. It adds a .bin extension to the log file name you configure in the session and workflow properties.

You can view log events for workflows with the Log Events window in the Workflow Monitor. When you try to access the log events from outside the workflow monitor you willl be restricted with the following error message.

When you come across a situatuion where you are only  allowed to access the log from outside the workflow monitor.

what will you do?

There is way to do this!

Configure a workflow or session to write log events to log files in the workflow or session properties. The
Integration Service writes information about the workflow or session run to a text file in addition to writing log events to a binary file. If you configure workflow or session properties to create log files, you can open the text files with any text editor or import the binary files to view logs in the Log Events window.


You can configure the following information for a workflow or session log:

• Write Backward Compatible Log File. Select this option to create a text file for workflow or session logs. If you do not select the option, the Integration Service creates the binary log only.
• Log File Directory. The directory where you want the log file created. By default, the Integration Service writes the workflow log file in the directory specified in the service process variable, $PMWorkflowLogDir
• Name. The name of the log file.

Note:

• If you enter a directory name that the Integration Service cannot access, the workflow or session fails.
• You must configure a name for the log file or the workflow or session is invalid.You can use workflow or worklet variable for the log file name.

Hope this helps.