Saving Logs For More Than One Run

By default, when you configure a workflow or session to create log files, the Integration Service creates one log file for the workflow or session. The Integration Service overwrites the log file when you run the workflow again. To create a log file for more than one workflow or session run, configure the workflow or session to archive logs in the following ways:

• By run
• By time stamp

Configuring the Session:
Goto Config Object-->Loog Options-->Save session log by

Configuring the Workflow
Goto Edit Workflow-->Properties-->Save Workflow log by

In the drop dow ther eare two options vz. Session Runs and Session Timestamp.


Archiving Logs by Run:

If you archive log files by run, specify the number of text log files you want the Integration Service to create.i.e.,set Save session log for these runs to the no. of logs you want.The Integration Service creates the number of historical log files you specify, plus the most recent log file. If you specify 5 runs, the Integration Service creates the most recent workflow log, plus historical logs zero to 5, for a total of six logs. You can specify up to 2,147,483,647 historical logs. If you specify zero logs, the Integration Service creates only the most recent workflow log file.

The Integration Service uses the following naming convention to create historical logs:
<session or workflow name>.n
where n=0 for the first historical log. The variable increments by one for each workflow or session run.


Archiving Log Files by Time Stamp:

When you archive logs by time stamp, the Integration Service creates an unlimited number of binary and text file logs.click  Working with Log Files to see how to create text log files.  You can see that Save session log for these runs will be disabled. The Integration Service adds a time stamp to the text and binary log file names. It appends the year, month, day, hour, and minute of the workflow or session completion to the log file. The resulting log file name is <session or workflow log name>.yyyymmddhhmi.

Note:

• When you run concurrent workflows with the same instance name, the Integration Service appends a timestamp to the log file name, even if you configure the workflow to archive logs by run.
• To prevent filling the log directory, periodically purge or back up log files when using the time stamp option.

Hope this helps.