- 2 minutes to read

Logging using the WCF Log API

This page explains how to use the (deprecated) WCF-based Log API in Nodinite for logging events, including supported protocols and MSMQ integration. If you are considering WCF, we strongly recommend reviewing modern asynchronous alternatives first.

What you'll find on this page:

✅ Supported protocols for WCF-based logging
✅ MSMQ integration for asynchronous event delivery
✅ Configuration tips for WCF Activation and IIS
✅ Migration guidance to modern asynchronous logging

Before you even think about creating a synchronous solution using WCF, please read the Asynchronous Logging user guide first. Modern asynchronous approaches are more robust and future-proof.

Important

This feature is deprecated! For new solutions, use REST-based or asynchronous logging with the Pickup Service.

WCF supports the following protocols

  • HTTP (synchronous and asynchronous)
  • HTTPS (synchronous and asynchronous)
  • TCP (synchronous and asynchronous)
  • MSMQ (asynchronous)

From .NET-based clients, the Log API may enlist in distributed transactions if logging is a mandatory part of your custom solution. See DTC for additional information.

Note

WCF Activation must be properly installed using Server Manager (Add roles and features).

WCF Activation
WCF Activation features in Windows Server Manager.

Name of the services found on the address (replace localhost as appropriate)

Default address is http://localhost/Nodinite/LogAPI/

  • LogApiService.svc (HTTP)
  • LogApiServiceSecure.svc (HTTPS)
  • LogApiServiceOneWay.svc (MSMQ)
  • LogApiServiceSessionful.svc (TCP)
  • LogApiServiceBase.svc (HTTP, This service is an alive checker and supports updating of the Log API itself)

Log API - MSMQ

The Log API can pick up events logged to MSMQ and put them into Nodinite for processing and archiving.

To support MSMQ, you should add net.msmq as a protocol in IIS
png_IISAdvancedSettings
IIS Advanced Settings: Add net.msmq protocol for MSMQ support.

png_IISEnabledProtocols
IIS Enabled Protocols: Ensure net.msmq is listed for MSMQ integration.

For troubleshooting MSMQ queue access issues, see: Log API MSMQ queue access denied


Next Step