Spotfire webplayer server uses log4net(as of version 6.5) for logging variety of information which can be helpful for performance, usage, errors and other sort of tracking.
Log4net provides variety of ways(loggers) to persist the logs for e.g in database, via emails, filters etc.
if you ever decide to change the output from default files to something else and are not using teh inbuild action_logs you may need to modify the log4net settings and chances are you could run into some syntax issue preventing log4net itself from working.
In those case it may be nice to be able to enable logging of log4net itself. To do so here are the steps
Log4net provides variety of ways(loggers) to persist the logs for e.g in database, via emails, filters etc.
if you ever decide to change the output from default files to something else and are not using teh inbuild action_logs you may need to modify the log4net settings and chances are you could run into some syntax issue preventing log4net itself from working.
In those case it may be nice to be able to enable logging of log4net itself. To do so here are the steps
Open <Web Player install dir>\webroot\Web.config, add the appSettings and the system.diagnostics tag below the <configSections></ configSections> section:
====================
[…]
</configSections>
<appSettings>
<add key="log4net.Internal.Debug" value="true"/>
</appSettings>
<system.diagnostics>
<trace autoflush="true">
<listeners>
<add
name=" textWriterTraceListener"
type=" System.Diagnostics. TextWriterTraceListener"
initializeData="C:\Program Files (x86)\TIBCO\Spotfire Web Player\3.2.1\webroot\Logs\ log4netlog.txt" />
</listeners>
</trace>
</system.diagnostics>
===============
The initializeData parameter specifies where the log should be placed, so make sure to change this to something that suits you. Save Web.config, restart the Web Player application pool from IIS Manager, open a browser and go the Web Player URL.
You should not see a new logfile with log4net issues if any
Comments
Post a Comment