We are running DNN in a complex high-available solution (internet bank) which involves several Windows services, web services etc. besided the usual DNN site. As of today we have several different event logs spread across the solution, but we would like to centralize these and are thinking about the possibilities to use the DNN EventLog, mainly because we already have a viewer for this through DNN. Now, what would be the "best practice" method of doing this?

As it seems, the event log funtionality in DNN is designed to work in a DNN website, and seem to have been designed only to run in that context. This of course is not really be a suprise, as DNN is a CMS webbased CMS system. Does this mean that in order to utilize the DNN Event Log we would have to write our own Business Layer functions to interact with the EventLog stored procedures in the DNN DAL or is there a better way?

If you have any other ideas, comments, thought, experiences about this, feel free to post them here. Thanks.

We have actually considered this approach as well but I am not sure about how "web service friendly" DNN is. Is it something that is officially supported kind of considering that DNN is mainly intended as a CMS, at least originaly? You can of course use Web services and DNN in parallel (we do that already), but I am not sure what support is there to use the web services in DNN. I know it can usually be all kind of problems with nested web.config etc. And what about shared PortalSettings etc, will it work without to much trouble?

Any pointers to best practice for Web services in DNN would be apprechiated.