Trace configuration
| Trace logging is deactivated by default in Net iD Portal. Customers are responsible for ensuring that access to trace files is restricted according to their internal security policies. |
This page describes how to verify that trace logging is disabled and how to safely configure trace output when trace is required for troubleshooting.
Services and their configuration files
Here are the services that can generate trace file information, and their respective configuration file:
- Commander
-
Commander\SecMaker.NiP.Commander.exe.config - GenericService
-
GenericService\SecMaker.NiP.GS.exe.config - TimerService
-
TimerService\SecMaker.NiP.TS.exe.config - WebServiceApplication
-
WebServiceApplication\Web.config - WebServiceExternal
-
WebServiceExternal\Web.config
Enable trace logging
| Trace logging should not remain activated after troubleshooting is completed. |
In some cases, Pointsharp may require customers to provide trace logs for troubleshooting.
If Log4net needs to be activated, make sure to redirect the trace files to another directory.
Activate Log4net
In the configuration files, set the following value:
<log4net threshold="ON"> (1)| 1 | OFF, logging is turned off ON, logging is turned on. |
Redirect trace output
In the configuration files, set the value attribute to the full path of your choice:
<param name="File" value="C:\Temp\Trace.txt"/> (1)| 1 | Set the full path to the trace file. |
Disable trace logging
After the required trace information has been collected:
-
Deactivate Log4net and set log4net threshold to
OFF. -
Delete the existing trace files. See Redirect Trace Output for where the files are located.
Trace server configuration
Make sure to disable Trace Server activation in Net iD Portal:
-
Net iD Portal ⇒ General settings ⇒ Trace server activation: Off
If Trace Server needs to be activated, redirect the path to, for example, C:\Temp\ by setting:
-
Trace server – Path in Net iD Portal under General settings