Requirement: BPM5 creates Log Files which over time can limit the amount of disk space available on your Server, causing poor performance or preventing processing entirely. So, you want to prevent the creation of Log Files. If you find an error that requires troubleshooting, you can always re-enable the output to Log Files.
How to Update the Configuration File:
In this case, you will want to update the Configuration File for each Service installed on your BPM5 Server. We will use the Notification Service for the remainder of this example.
<allEvents switchValue="All" name="All Events">
<listeners>
<add name="Bluespring.NotificationService.Console"/>
<add name="Bluespring.NotificationService.EventLog"/>
<add name="Bluespring.NotificationService.LogFile"/>
</listeners>
</allEvents>
The Source Listeners define 3 different outputs: the Console, the Event Log and the Log File. We want to suppress output to the Log File, so we update the configuration file to turn the Log File configuration into comments. Note: for troubleshooting purposes, we may want to output to the Log File again at a later date. Accordingly, Bluespring does not recommend deleting the Log File Source Listener entirely from the file; instead, comment out the Source Listener, so it is easy to reenable at a later date, if necessary.
To make the text in a configuration file into a comment, enclose it within an XML tag: <!--, which ends in, -->, i.e. <!-- Enclosed text is a comment -->
So, your Source Listeners become:
<allEvents switchValue="All" name="All Events">
<listeners>
<add name="Bluespring.NotificationService.Console"/>
<add name="Bluespring.NotificationService.EventLog"/>
<!--<add name="Bluespring.NotificationService.LogFile"/>-->
</listeners>
</allEvents>
Notice the Bluespring.NotificationService.LogFile is now enclosed as a comment, thereby suppressing the output of logging information to a Log File. To reenable the output of logging information to a Log File, simply remove the comment tags, at both the beginning and end of the line.
