- 5 minutes to read

How to enable Logging from WSO2 Enterprise Integrator solutions to Nodinite

Enable asynchronous, business-centric logging from WSO2 Enterprise Integrator to Nodinite. This guide helps you capture, format, and move business transaction logs for secure, self-service access and actionable business insights.

Tip

Use Asynchronous Logging to send logs from WSO2 Enterprise Integrator to Nodinite. Add custom code to your solution to enable this integration.

✅ Log business transactions asynchronously for reliability and performance
✅ Format logs for Nodinite and deliver them securely
✅ Empower business users with self-service log access and insights

Important

Always set OriginalMessageTypeName for searchable business data - When logging from WSO2 Enterprise Integrator, the Message Types field in your JSON Log Event is critical for enabling business intelligence features. Without proper Message Types:

  1. Search Field Expressions cannot extract Order Numbers, Customer IDs, Invoice amounts, Transaction codes, or other business identifiers
  2. Log Views can only search by timestamps and correlation IDs, not by business data
  3. Non-Events Monitoring cannot track message volumes, detect missing messages, or alert on pattern anomalies
  4. Business Process Modeling (BPM) cannot correlate transactions end-to-end across your WSO2 flows and other systems

Set OriginalMessageTypeName in your JSON Log Event before writing to intermediate storage. Plan your Message Types during development—they define how Nodinite extracts searchable business data from your logged messages.

Add custom logging code to your WSO2 Enterprise Integrator solution so you log business transactions to Nodinite.

graph LR subgraph "WSO2 Enterprise Integrator" roBroker(fal:fa-brackets-curly Custom Code)-->roSink(fal:fa-file-export Intermediate storage ) end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) -->roNI(fal:fa-cloud-arrow-down Log API) roSink --> roPS end

Diagram: Asynchronous logging flow from WSO2 Enterprise Integrator to Nodinite, using custom code, intermediate storage, and the Nodinite Pickup Log Events Service Logging Agent.

Step by step guide

Follow these steps to enable logging:

1. Create the event

Add custom logging in your flows. Use Log4J or similar frameworks, depending on your design, policy, and needs.

2. Convert the logged event to Nodinite format

Translate your logs to Nodinite JSON Log Event.

To uniquely identify the Log Agent, set a LogAgentValueId. Make the LogAgentValueId (mandatory number) configurable in your WSO2 Enterprise Integrator solution. Do not hardcode this value—use different values for each environment (e.g., Prod, Test, QA, ...).

Important

Include OriginalMessageTypeName in your JSON Log Event - This field is mandatory for business intelligence:

{
 "LogAgentValueId": 42,
 "EndPointName": "WSO2 Integration - Receive Orders",
 "EndPointUri": "http://wso2-ei:8280/services/OrderService",
 "EndPointDirection": 0,
 "EndPointTypeId": 60,
 "OriginalMessageTypeName": "PurchaseOrder#1.0",
 "ProcessingUser": "WSO2-EI-User",
 "ProcessName": "OrderIntegration",
 "ProcessingMachineName": "WSO2-SERVER-01",
 "ProcessingModuleName": "OrderMediator",
 "ProcessingModuleType": "WSO2Mediator",
 "StartLogTime": "2025-10-12T10:30:00.000Z",
 "EndLogTime": "2025-10-12T10:30:01.500Z",
 "LogMessage": "Order received from customer",
 "StateCode": 0,
 "ApplicationInterchangeId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
 "Body": "<Order><OrderId>ORD-2025-001</OrderId><CustomerId>CUST-12345</CustomerId>...</Order>"
}

Without OriginalMessageTypeName, Search Field Expressions cannot extract business data, and features like Non-Events Monitoring and BPM won't function.

Tip

Map your existing properties to standard properties and attach context and payload as needed to maximize the value of your logs. Use Context Options to add custom searchable properties.

3. Send Event to intermediate storage

Configure the Nodinite Pickup Log Events Service Logging Agent to fetch logged events from your chosen intermediate storage.

Important

Choose a local, highly available intermediate storage for best reliability.

Tip

Send logged events asynchronously to the Nodinite Log API. Use the Nodinite Pickup Service to follow the asynchronous pattern.

4. Move logged events using the Nodinite Pickup Service

The Nodinite Pickup Log Events Service Logging Agent fetches Log Events from your intermediate storage. Consume Log Events from any supported source that fits your needs.

5. Configure Message Types

Define Message Types for your WSO2 logged events. Each Message Type represents a specific message format (e.g., "PurchaseOrder#1.0", "Invoice#2.0", "CustomerUpdate#1.0"). Message Types are mandatory and determine which Search Field Expressions will extract business data from your logged messages.

6. Configure Search Field Expressions

Create Search Field Expressions bound to your Message Types. These expressions extract business identifiers (Order Numbers, Customer IDs, Invoice amounts, Transaction codes) from your logged message bodies using XPath, JSON Path, Regular Expressions, or other parsers.

7. Create Log Views

Create Role-based Log Views to visualize and search the logged data. Configure role-based access so business users can self-service search by business data extracted by your Search Field Expressions.

8. Configure Non-Events Monitoring (Optional)

Set up Non-Events Monitoring to track expected message volumes and detect missing messages from your WSO2 integrations.

9. Design BPM Processes (Optional)

Use Business Process Modeling (BPM) to correlate transactions end-to-end across your WSO2 Enterprise Integrator flows and other systems.

Next Step

Configure Message Types - Critical first step for searchable business data
Configure Search Field Expressions - Extract business identifiers
Create Log Views - Enable business user self-service

JSON Log Event - Required format for WSO2 logging
Message Types - Mandatory for business intelligence features
Search Field Expressions - Extract Order Numbers, Customer IDs, Invoice amounts
Log Views - Business-data searches and role-based access
Non-Events Monitoring - Track message volumes and detect missing messages
Business Process Modeling (BPM) - End-to-end transaction correlation
Asynchronous Logging - Recommended approach for reliability
Context Options - Additional searchable properties
Pickup Service - Fetches log events from intermediate storage
Log Agents - Identify logging sources
Roles - Role-based access control