In the FIM 2010 architecture, the FIM Portal represents the user interface you use to configure your FIM environment. The FIM Portal is implemented as Windows SharePoint Services application and is accessible by using a web browser such as Internet Explorer.
To configure FIM portal tracing, you need update the configuration file called Web.config that is typically located in the following folder:
The tracing configuration is stored under the <system.diagnostics> element you need to add to your configuration file.
The following screenshot shows an example for this:
When you configure FIM Portal tracing, you can defie trace listeners to consume the related information and the trace level. Examples for listeners are an
XmlWriterTraceListener to write the related information into a XML file or the
EventLogTraceListener to write the related information into one of the Event Viewer’s log files.
Depending on how much information you need, you can fine-tune the level of information that is stored. For example, you can configure tracing to only log errors.
The following XML code shows an example for the required settings to write FIM Portal tracing information into a files that are located in the C:\Logs folder on your hard drive:
"System.Diagnostics.XmlWriterTraceListener, System, Version=126.96.36.199,
"LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack"
The following XML code shows an example for the required settings to write FIM Portal error information into the Forefront Identity Manager section log file of the Event Viewer:
"System.Diagnostics.EventLogTraceListener, System, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b77a5c561934e089"
"LogicalOperationStack, DateTime, Timestamp, Callstack"
To enable FIM portal tracing, you need to:
To disable FIM portal tracing, you need to:
The first configuration example in this article uses the XmlWriterTraceListener to write information to a XML file on your hard drive. While you can use any tool that is suited to display XML data to open and read the trace files,
it can be difficult to evaluate the log files using a generic XML file viewer. As a best practice for reading
XmlWriterTraceListener based trace files, you should consider using the Windows Communication Foundation (WCF) Service Trace Viewer Tool to open the trace files. The Service Trace Viewer Tool is included in the .Net
If want to install the Service Trace Viewer Tool but you don't want to install the entire SDK, you can, for example, use the web-installer of the
Windows SDK for Windows Server 2008 and .Net Framework 3.5:
Using this method enables you to uncheck the components you don't want to install:
When you use the ExceptionEventLogListener to write tracing information into an event log file, you can certainly use the event viewer to evaluate the related messages. However, depending on how many entries you have in your log
file, it might be more convenient to access the trace file data by using PowerShell.
The following script code shows a simple method to display the logged information: