Creating a Logging User Interface Module

When you create your own custom logging module, you have three user interface options:

• No user interface module: This option is appropriate if your logging module has no configurable settings, or if you'd rather provide access to your logging module through mechanisms other than those used by IIS.
• Use a built-in user interface module: You can, in effect, borrow one of the user interface modules provided with the built-in IIS logging modules. The user interface module GUID specified under the Microsoft IIS Log File Format key of the /LM/LOGGING path in the metabase would be most appropriate for this use, because it provides basic configuration functionality.
• Create a new user interface module: You can create your own COM object that implements the appropriate interfaces.

You are not restricted to performing any set tasks in your user interface module.

    To create and install a logging user interface module

• Either write a COM component that implements the ILogUIPlugin interface, as defined in the ilogobj.h header file, or use one of the built-in user interface modules.
• Use regsvr32, or some other registration tool, to register the component.
• Add your logging user interface module GUID to the MD_LOG_PLUGIN_UI_ID key in the metabase.

If you decide to create a new user interface module, you should implement the module in a DLL separate from the logging module. Also, the UI module must be resident and registered on the machine on which Internet Service Manager is running. This requirement is particularly important if you intend to administer your custom logging module remotely; the logging module itself can be running on a remote machine, but the logging UI module must be local.