- 3 minutes to read

Release Notes

Prerequisites for the Nodinite IBM Integration Bus Logging Agent

This page describes the prerequisites for installing, configuring and running the Nodinite IBM Integration Bus Logging Agent.

The Logging solution involves the following parts:

  • Emitting IBM Monitoring Events (involves changes to configuration files on your server with IBM Integration bus workflows)
    • IBM MQ Queues as destinations for IBM Monitoring Events
  • IBM Integration Bus Logging Agent (must be installed and have access to queues)
graph LR subgraph "IIB / ACE Solution" roWCFApplication(fal:fa-globe IIB Workflow)--> roWCFTracing(fal:fa-bolt Monitoring Events
Monitoring Profile) roFolder(fal:fa-list IBM MQ Queue) roWCFTracing --> roFolder end subgraph "Nodinite Server" roPS(fal:fa-truck-pickup Nodinite Logging Agent) roFolder --> |TCP| roPS end

Log Events and Payload

  • You must have one or more System Integration Solutions running in one or more IBM Integration Bus environment(s).

  • You must configure IIB/ACE to emit Monitor Events

  • Also, The IBM Integration Bus Log Agent harvests all your events and messages that stem from IBM Integration Bus Monitor Events with a queue destination. Currently, the following queue providers are supported:

    Upon request, we may add future support for the following:

    • MQTT
Verified Topic
Software Requirements
What Windows User Rights does the IBM Integration Bus Logging Agent require
What firewall settings does the Nodinite IBM Integration Bus Logging Agent require?

Software Requirements

You need the following components:

  1. Windows Server

  2. .NET Framework

  3. IBM Integration Bus

    You are not required to install the Nodinite IBM Integration Bus Logging Agent on the same server hosting the IBM Integration Bus solution; our recommendations is that you install it locally on the Nodinite application server.

  4. IBM MQ Client binaries with the .NET redistributable
    Default read ahead
    Queues with Monitoring Events must have 'Default read ahead' set to No.

  5. Configure the MSDTC with support for XA transactions

Product
Windows Server Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later New 6.0 Our recommendation is .NET Framework 4.8.1 or later
IBM Integration Bus
  • 12
  • 11
  • 10
  • 9
 Older versions may very well work; contact our Support if you need echnical assistance configuring Nodinite against older versions of the IBM Message Broker
IBM MQ Client V9.2
V9.1

v9.0
v8.05+
v7.5+
 Matching the highest version of IBM MQ in use with the IIB for the Logging
MSDTC Windows roles and features Configure MSDTC as documented with additional demand on 'XA transactions' being allowed

If you need IBM MQ Client 9.3 or later, please contact our support.

Versions 6.0 and later make use of the .NET Framework 4.8 or later.
Versions 5.4 and subsequently make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.

Tip

Make sure to monitor the log queues using the Nodinite IBM MQ Monitoring Agent.

What Windows User Rights does the IBM Integration Bus Logging Agent require?

Privileges

The IBM Integration Bus Logging Agent requires privileges to run as a Windows Service and access rights to consume messages on queues on the configured queue managers.

Windows User Rights

The agent requires a Windows account:

What firewall settings does the Nodinite IBM Integration Bus Logging Agent require?

The Nodinite IBM Integration Bus Logging Agent has the same prerequisites as the Nodinite IBM MQ Monitoring Agent.

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite IBM Integration Bus Logging Agent exist in the Troubleshooting user guide.

Next Step

Install IBM Integration Bus Logging Agent
Administration

Log Agents
LogAPI