- 0 minutes to read

Release Notes

Managing WCF Applications

Learn how to manage the WCF Diagnostics Tracing Feature.

Share and delegate Understand your application and data Save money
Quickly provide self-service access for your business and other stakeholders Get insights from logged data Just 1 Nodinite license is required regardless of the number of WCF Enabled Applications

Features

You can manage:

  • Enable/Disable Logging
  • Manage properties that determine run-time behaviour
  • Configure Message Types for business intelligence

Logging Features

You can manage the following properties for logging:

  • Pickup folder - This is the folder where your WCF Application writes to and that eventually the Pickup Log Events Service Logging Agent will fetch from
  • LogAgentId - your user-defined identity of the Log Agent
  • traceOutputOptions = None - Not in use yet but must exist in the config file
  • DefaultMessageType - Default Message Type to use for all WCF messages (e.g., "OrderService#1.0"). Critical for enabling Search Field Expressions
  • MessageTypeFromBody - When true, extracts Message Type from WCF message body using XPath /MessageLogTraceRecord/Envelope/Body (namespace#node). Falls back to DefaultMessageType if extraction fails
  • Name - as used in the config file, if you change the default name you must change all occurrences

Important

DefaultMessageType and MessageTypeFromBody are critical for business intelligence

These two properties determine how Message Types are assigned to your WCF diagnostic events:

  • DefaultMessageType: Set this to a meaningful business transaction name (e.g., "OrderService#1.0", "CustomerAPI#2.0"). This enables Search Field Expressions to extract business data from your WCF messages.
  • MessageTypeFromBody: When true, automatically extracts Message Type from the WCF message body (namespace and first child element). This is useful when WCF applications handle multiple message types.

Without proper Message Type configuration, Search Field Expressions cannot extract business data (Order IDs, Customer Numbers, etc.), Log Views cannot provide self-service search, and Business Process Modeling (BPM) cannot correlate transactions.

Support

Contact our Support for additional guidance if you fail to resolve any installation/download problems.

Tip

Additional information to aid the troubleshooting may exist in the Windows Event Logs.

Next Step

After configuring WCF Diagnostics Tracing properties, complete these steps:

  1. Configuration - Configure DefaultMessageType and MessageTypeFromBody in your WCF application config file
  2. Message Types - Define business transaction types in Nodinite Administration (Critical first step)
  3. Search Field Expressions - Configure extraction of business data from WCF messages
  4. Logging WCF diagnostic tracing feature - Understand the complete logging flow