The IBM Integration Bus Logging Agent prerequisites
This page describes the prerequisites for installing, configuring and running the IBM Integration Bus Logging Agent.
The Logging solutions 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)
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
You must have one or more System Integration Solutions running in one or more IBM Integration Bus environment(s).
You must configure 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:
Future support may be added if customers requests so for:
|What Windows User Rights does the IBM Integration Bus Logging Agent require?|
|What firewall settings does the Nodinite IBM Integration Bus Logging Agent require?|
You need the following components:
- Windows Server
- .NET Framework
- IBM Integration Bus
The Nodinite IBM Integration Bus Logging Agent do NOT need to be installed on the same server as IBM Integration Bus. 4. IBM MQ Client binaries with the .NET redistrutable * Queues with Monitoring Events must have 'Default read ahead' set to No.
5. Configure the MSDTC with support for XA transactions
Windows 2012 R2
|.NET Framework||.NET Framework 4.6.2 or later New 5.4||Our recommendation is .NET Framework 4.8|
|IBM Integration Bus||
||Older versions may very well work, contact our Support if you need our technical assistance configuring Nodinite against older versions of the IBM Message Broker|
|IBM MQ Client||v9+
|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|
Versions prior to 5.4 make use of the .NET Framework 4.5 or later.
TIP: Make sure to monitor the log queues using the Nodinite IBM MQ Monitoring Agent.
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.
The agent requires a Windows account:
- Local named account or domain account (preferred)
Follow this guide 'How to set Logon as a Service right' for more information