- 5 minutes to read

Message Types

Unlock robust, flexible integrations and advanced content identification with Nodinite Message Types. This page shows you how to define, manage, and leverage message types for seamless integration, powerful search, and precise logging—across XML, JSON, EDI, and more.

✅ Identify and manage every message type for full integration clarity
✅ Enable advanced search and filtering with custom search fields
✅ Support XML, JSON, EDI, and custom formats for maximum flexibility
✅ Empower DevOps and business teams with automated, schema-driven management

System integration solutions communicate by exchanging messages as part of a business conversation. Participants agree on the name and content for each message type, usually following a business standard, such as the UN standard for EDI Despatch Advice.

A Message Type object defines a unique name for a message type and specifies the type of data the message contains. Nodinite stores Message Types in the configuration database and uses them with Search Fields to extract values for advanced search and to enforce restrictions in Log Views.

graph LR subgraph "MessageTypes" roMTPurchaseOrder(fal:fa-file Papinet.PurchaseOrder/2.31) roMTOrder(fal:fa-file EDIFACT.ORDRSP.D96A) end subgraph "Search Field Expressions" roSFEOrderIdFromEdifact(fal:fa-flask RegEx with Capturing Groups) roSFEOrderIdFromXML(fal:fa-flask XPath) end subgraph "Search Fields" roSFOrderId(fal:fa-magnifying-glass-plus Order Number) end roMTPurchaseOrder --- roSFEOrderIdFromXML roSFEOrderIdFromXML --- roSFOrderId roMTOrder ---roSFEOrderIdFromEdifact roSFEOrderIdFromEdifact --- roSFOrderId

Nodinite can correlate transactions such as order/order response in different formats, even when transmitted across multiple integration brokers and over long time intervals.

  • All logged messages within Nodinite must have a well-known Message Type.
  • For a message type that specifies XML conforming to a particular schema collection, the message must contain valid, well-formed XML.
  • For a message type that specifies no validation or schema, Nodinite accepts any message content—including binary data, XML, or even empty messages (such as API calls where only HTTP headers are logged).

A Message Type is a member of a Service in the Repository Model and represents the type of message for a logged event. Examples include:

Messages can be displayed for end-users in a user-friendly format using Stylesheets.

Origin of Message Types

Message Types originate from the process of logging. Messages cannot be logged without a Message Type. The proposed Message Type from the Logging Agent Configuration is retained and stored as the Original Message Type.

  • For custom logging, the Message Type is defined by your custom code.
  • All logged messages are processed by the Logging Service. During processing, the Message Type is determined, one way or another.

When a message is logged to Nodinite, it is unprocessed. Once the Logging Service has handled unprocessed messages and those pending re-indexing, the message becomes processed.

Automated Deployments

Devops Manage Nodinite Message Types as part of your DevOps routine.

As part of your Azure DevOps routine, you can programmatically create or manage Message Types by invoking the Nodinite Web API.

Microsoft BizTalk Server

The Logging Service provides special support for Microsoft BizTalk Server. When BizTalk solutions use pipeline components with a defined schema, the Message Type is well-known. For Passthru pipeline components, the message type is unknown and must be handled. Nodinite offers several options.

  • For Nodinite Logging Agents, the Message Type is created using our logic.

    Important

    Avoid the built-in Unparsed Interchange and Serialized Interchange. Always set a default message type in the Advanced tab of the Endpoint for the message exchange.

Passthru

Using any of the Passthru pipeline components results in logged messages being either Unparsed Interchange or Serialized Interchange, depending on direction.

XML Content

If the content is UTF-8 encoded (the default for BizTalk Server) and is XML, Nodinite resolves the Message Type in the same way as BizTalk: by combining the target namespace and the root node name, for example:

urn:oasis:names:draft:ubl:schema:xsd:DespatchAdvice-2#DespatchAdvice

Non-XML Content

For flat file and EDI-based messaging, the Logging Service queries the BizTalk Server Configuration database (BizTalkMgmtDB) for additional information to resolve the current schema used for the message exchange.

Tip

For BizTalk Server, even if Passthru pipeline components are used, the message type will still be known to Nodinite.

Message Types Set on Endpoint

For BizTalk Server, when the message type is either "Unparsed Interchange" or "Serialized Interchange", you can configure the Nodinite Endpoint to set a superseding pre-defined Message Type.

Unprocessed Message

Unprocessed

Processed Message

Processed

If the message is JSON, XML, or EDIFACT based, the Logging Service extracts the Message Type from the message payload. The Original Message Type is kept at the record level, but Nodinite uses the extracted value as the Message Type. This enables advanced Search Fields.

Note

You can override the logic by providing your own defined message type as a Context Option.

XML

For XML messages, Nodinite extracts the Message Type from the Target Namespace combined with the root node, for example (Orders/1.0#Order).

EDIFACT

For EDIFACT messages, Nodinite sets the Message Type using the value from the UNA field.

JSON

For JSON messages with the schema property set, Nodinite sets the Message Type accordingly.

Read more about JSON schema in the following user guide: 'Defining JSON Messages with JSON Schema'

Search Fields

Values for Search Fields are extracted during message processing. You can reprocess or re-index messages based on the Message Type if you add or change the configuration for a Search Fields.
Reindex Action menu item Re-index operation available in the Action menu.

Note

Adding Search Fields and Search Field Expressions on Message Types increases workload. Be sure to configure and use this powerful feature wisely.

Removal of Old Messages Based on Message Type (Days to Keep)

This topic is detailed in the Add or manage Message Type user guide.

Custom Metadata

As with all entities in the Nodinite Repository Model, a Message Type can have any number of Custom Metadata fields assigned, supporting flexible documentation and governance.

Custom Fields

Similarly, a Message Type can have any number of Custom Fields assigned, enabling tailored information management for your integration landscape.

Next Step

Add or manage Message Types
Add or manage Search Field
Add or manage Service
Message Type Overview

Repository Model
Services
Logging Service
Log API
Search Fields
Log Views
Stylesheets