|
But, in the previous versions of IIS, you would see the
below:
So, in this article I will explain how to configure
IIS7.0 site for ODBC logging. You still want to check out this KB for the database,
table related information which needs to be created prior to this IIS
configuration change.
Changing LogFile Format and the
customLogPluginClsid
To configure ODBC, you might need to know the log plugin
ID for the ODBC logging. In IIS 6.0, it was LogModuleId, and if you do a search
for “ODBC logging” in your Metabase.XML file, you might find this property with
value “{FF16065B-DE82-11CF-BC0A-00AA006111E0}”. We are going to use the same in
IIS 7.0, but in the ApplicationHost.config file as customLogPluginClsid.
You need to find the <logFile> node in
ApplicationHost.config, and that should look like below:
<logFile
customLogPluginClsid="{FF16065B-DE82-11CF-BC0A-00AA006111E0}" logFormat="Custom"
/>
Below are the AppCmds to do this:
appcmd set site /site.name:"Default Web Site"
/logFile.customLogPluginClsid:"{FF16065B-DE82-11CF-BC0A-00AA006111E0}"
appcmd site set /site.name:"Default Web Site" /logFile.logFormat:"Custom"
Now, we have just configured IIS to use ODBC logging for
our default website. We still need to configure the required DSN name,
table-name, username and password to do the ODBC logging.
|