Kofax TotalAgility Streaming Service Logging
Article # 3039671 - Page views: 50
Issue
In instances, it might be necessary to enable extended logging in the TotalAgility Streaming Service. This article outlines the steps on how to perform enable this.
Solution
Location of config file
The Agility.Server.StreamingService.exe.config file can be found at different locations depending on your deplyment.
- Combined Web/App Server: %INSTALLDIR%\TotalAgility\CoreWorkerService
- Dedicated App Server: %INSTALLDIR%\TotalAgility\CoreWorkerService
- Dedicated Web Server: %INSTALLDIR%\TotalAgility\Agility.Server.Web\bin
Unity Logging
To enable unity logging, uncomment the 2 sections below in the Agility.Server.StreamingService.exe.config file.
<add name="fileLogger" type="System.Diagnostics.TextWriterTraceListener" initializeData="LogFile.log" /> <remove name="Default" />
<extension type="Agility.Server.Common.Logging.LogMethodRegistration, Agility.Server.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d86c87abe4a71948" />
For the first section, make the below changes:
- Change name from "fileLogger" to "KTALog" (mandatory)
- Change initializeData to the location where the log file should be generated (optional)
WCF Activity Tracing
To enable WCF activity tracing, uncomment the below section in the Agility.Server.StreamingService.exe.config file.
<sources> <source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"> <listeners> <add name="traceListener" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\log\Traces3.svclog" /> </listeners> </source> </sources>
Optionally, change initializeData to the location where the log file should be generated.
NOTE: The Kofax TotalAgility Streaming Service needs to be restarted after making any changes
Level of Complexity
Easy
Applies to
Product | Version | Build | Environment | Hardware |
---|---|---|---|---|
KTA | 7.7+ |