- 3 minutes to read

Custom Logging, FAQ, Troubleshooting, Message Types Custom Logging, OriginalMessageTypeName, Message Type, business intelligence, Search Fields Why is OriginalMessageTypeName mandatory for business intelligence? Learn how Message Types enable searchable business data.

Why OriginalMessageTypeName is Mandatory

Why is OriginalMessageTypeName mandatory for business intelligence?

OriginalMessageTypeName is the foundation for all business intelligence features in Nodinite. Without it, you lose business-data search, volume monitoring, end-to-end correlation, and self-service analytics.

What Breaks Without OriginalMessageTypeName

When you omit OriginalMessageTypeName from your JSON Log Event, these features stop working:

1. Search Field Expressions Cannot Extract Business Data

Search Field Expressions extract Order Numbers, Customer IDs, Invoice amounts, and Transaction codes from your logged message bodies. Search Fields are bound to Message Types—without OriginalMessageTypeName, Nodinite doesn't know which extraction rules to apply.

Result: Business users can only search by timestamps and correlation IDs, not by "Order 12345" or "Customer ACME".

2. Log Views Lose Business-Data Filtering

Log Views enable business teams to self-service search: "Show me all failed PurchaseOrders last week" or "Export invoices >$10K for customer X". Log Views filter by Message Type.

Result: Without Message Types, Log Views can only show generic "all logs"—no business context, no role-based filtering by message format.

3. Non-Events Monitoring Cannot Track Message Volumes

Non-Events Monitoring detects anomalies: "Expected 5,000 PurchaseOrders/hour, only received 200—alert Operations". Volume tracking requires Message Types to distinguish "PurchaseOrder#1.0" from "Invoice#2.0".

Result: Cannot detect missing expected messages, silent batch job failures, or volume anomalies.

4. BPM Cannot Correlate End-to-End Transactions

Business Process Modeling (BPM) correlates transactions across systems: "Show me Order 12345's journey from webMethods → Custom API → IBM Sterling → SAP". BPM uses Message Types + ApplicationInterchangeId.

Result: No end-to-end transaction visualization across platforms.

How to Set OriginalMessageTypeName

Include OriginalMessageTypeName in your JSON Log Event:

{
  "LogAgentValueId": 42,
  "EndPointName": "Custom Integration - Receive Orders",
  "OriginalMessageTypeName": "PurchaseOrder#1.0",
  "ApplicationInterchangeId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "Body": "<Order><OrderId>PO-2025-001</OrderId>...</Order>"
}

Naming convention: Use {MessageName}#{Version} format (e.g., "Invoice#2.0", "CustomerUpdate#1.0") to clearly identify message formats and support versioning.

Plan Message Types Before Development

Message Types cannot be changed after events are logged—they're immutable. Define your Message Types during development:

  1. Identify message formats - PurchaseOrder, Invoice, CustomerUpdate, PaymentConfirmation
  2. Plan versioning strategy - "PurchaseOrder#1.0", "PurchaseOrder#2.0" (when schema changes)
  3. Configure Message Types in Nodinite - Before logging starts
  4. Create Search Field Expressions - Extract business identifiers (Order Numbers, Customer IDs, amounts)
  5. Include OriginalMessageTypeName - In every JSON Log Event

Without planning Message Types first, you get technical logs with no business intelligence.

Related Topics:
Message Types Overview
Search Field Expressions
JSON Log Event Format

See all FAQs: Troubleshooting Overview

Next Step

Back to Custom Logging Overview