- 6 minutes to read

Release Notes

Troubleshooting the IBM Integration Bus Logging Agent

Easily resolve issues and get expert answers for your Nodinite IBM Integration Bus Logging Agent. This page provides troubleshooting steps, frequently asked questions, and direct support options to keep your integration monitoring running smoothly.

✅ Step-by-step troubleshooting for common issues
✅ Direct links to configuration and monitoring guides
✅ Answers to frequently asked questions
✅ Access to expert support and documentation

If you have any issues that you cannot solve, please contact our Support, or send us an email at support@nodinite.com

FAQ

How do I add IBM Integration Bus Logging with Nodinite?

Adding an arbitrary number of IBM Integration Bus queue managers for Nodinite to monitor is a simple and straightforward process that only requires proper access rights. Just follow the steps detailed in the Configuration user guide.

Which IBM Integration Bus versions are supported?

IBM Integration Bus 8.x, 9.x, 10.x and IBM App Connect Enterprise (ACE) 11.x, 12.x are fully supported. Both on-premise (Windows, Linux, AIX) and IBM Cloud deployments work. Community Edition and Enterprise Edition supported.

Can I log binary payloads (PDFs, images) from IBM IIB flows?

Yes—Base64 encoding supported. IBM Monitoring Profiles capture BLOB payloads (binary) automatically. Nodinite stores Base64-encoded representation. Useful for SOAP attachments, FTP file transfers, email attachments, scanned documents (insurance claims, healthcare patient records).

Size limit: Tested to 50MB per event. For very large binaries (>50MB), consider storing in separate blob storage (Azure Blob, AWS S3, IBM Cloud Object Storage) and logging the blob URL + hash in Nodinite.

How do I handle high-volume flows (1M+ messages/day)?

IBM Monitoring Profiles support high throughput with minimal overhead (<3% latency impact). For 1M messages/day (694 messages/minute average, 2,000 peak):

MQ Queue: MAXDEPTH 500,000 messages (~10GB) buffers 6-8 hour peak volumes. Configure queue on SSD storage for performance.

Nodinite Agent: Deploy on dedicated server (4-core, 16GB RAM typical). Agent processes 100-500 messages/second (MQGET batch size 100, parallel workers 8-16).

Scalability: Tested to 50M events/day per Nodinite instance (distributed across multiple agent instances). For higher volumes, deploy multiple Nodinite environments (by business unit, by geography).

Can I monitor IBM MQ queue depths used by Nodinite?

Yes—use IBM MQ Monitoring Agent to monitor SYSTEM.BROKER.MONITORING.EVENTS queue depth in real-time. Configure alerts:

  • Queue depth >400,000 messages (80% of MAXDEPTH 500,000): "Nodinite agent likely stopped consuming, investigate before queue fills"
  • Queue depth growth rate >10,000 messages/minute: "Monitoring Event production exceeds consumption, possible agent performance issue"
  • Queue age >4 hours: "Oldest message stuck in queue for 4 hours, agent may have stopped"

Proactive monitoring prevents audit trail gaps. Operations team receives alert 2-6 hours before queue fills (time to investigate agent status, restart if needed, increase MAXDEPTH if volumes higher than expected).

What happens if SYSTEM.BROKER.MONITORING.EVENTS MQ queue fills up?

Monitoring Events are rejected when queue hits MAXDEPTH limit—events lost, audit trail incomplete. Prevention: Increase MAXDEPTH to 500,000 messages (~10GB) for 12-24 hour buffering during network outages/maintenance. Configure Non-Events Monitoring to alert if queue depth exceeds 80% threshold (e.g., ">400,000 messages = Nodinite agent likely stopped consuming"). Operations team investigates before queue fills.

Recovery: If queue fills, increase MAXDEPTH immediately, restart Nodinite agent to consume backlog. For prevented event loss: Configure IBM ACE Dead Letter Queue (DLQ) as backup (complex setup, not recommended for first implementation).

How do I correlate transactions across multiple IBM IIB message flows?

Use MQMD.CorrelId propagation pattern. First flow (e.g., HTTPInput receives REST request) generates UUID: DECLARE correlationId CHAR UUID(); Sets MQMD.CorrelId: SET OutputRoot.MQMD.CorrelId = CAST(correlationId AS BLOB); All downstream flows inherit MQMD.CorrelId automatically (IIB default behavior). All flows log with same CorrelId.

Nodinite groups events by ApplicationInterchangeId (mapped from MQMD.CorrelId). Configure BPM with expected flow sequence (Flow1 → Flow2 → Flow3 → Flow4 → Flow5 → Flow6). Support team searches by Order Number → sees all 6 flows color-coded (green/yellow/red). Root cause visible instantly (e.g., Flow4 "ChargePayment" shows PaymentGatewayTimeout exception).

What retention policies should I use for different message types?

Configure per-type based on compliance requirements:

  • Financial transactions (ACH payments, wire transfers, credit cards): 7 years (SOX/PCI-DSS mandatory)
  • Healthcare HL7 (patient admissions, lab results, prescriptions): 10 years (HIPAA medical records retention)
  • Customer orders (e-commerce, B2B): 3-5 years (warranty/returns support, tax audits)
  • Debug/development logs: 30-90 days (troubleshooting recent issues only)
  • Audit trails (user actions, configuration changes): 7-10 years (compliance investigations)

Cost optimization: Shorter retention = lower SQL Server storage costs. Archive old events to cheap blob storage (Azure Blob $0.002/GB/month, AWS S3 Glacier $0.001/GB/month) if regulatory requirements mandate longer retention but searchability not required after N years.

How do I Monitor IBM MQ with Nodinite?

Review the Nodinite IBM MQ Monitoring Agent for step-by-step instructions.

How do I Monitor IBM DataPower?

Review the Nodinite IBM DataPower Monitoring Agent.

How do I specify which version of AMQMDNET.DLL to use?

You may need to adjust the '%agent name%.exe.config' file to specify the exact version to use for your environment.

  • Adjust the example with the proper folder and version in use in the target environment.
  • Restart the agent and review the diagnostics.log.json file for details.

Version example 8.0.0.5 

<dependentAssembly>
    <assemblyIdentity name="amqmdnet" publicKeyToken="dd3cb1c9aae9ec97" culture="neutral" />
    <codeBase version="8.0.0.5" href="file:///C:\Program Files (x86)\IBM\WebSphere MQ\bin\amqmdnet.dll" />
    <bindingRedirect oldVersion="0.0.0.0-8.0.0.5" newVersion="8.0.0.5" />
</dependentAssembly>

Version example 9.1.0.7 

<dependentAssembly>
    <assemblyIdentity name="amqmdnet" publicKeyToken="dd3cb1c9aae9ec97" culture="neutral" />
    <codeBase version="9.1.0.7" href="file:///C:\Program Files (x86)\IBM\WebSphere MQ\bin\amqmdnet.dll" />
    <bindingRedirect oldVersion="0.0.0.0-9.1.0.7" newVersion="9.1.0.7" />
</dependentAssembly>

Version example 9.3

The 9.3 client requires .NET Framework 4.8. The agent is currently built using the 4.6.2 run-time. If you need support for 9.3, please contact our support to get an updated version of the agent.