IntegratD Logging - Partner connector
The IntegratD Platform is the unified metadata-centric Integration Visibility and Management Platform designed to empower business users across the Integration ecosphere.
With the IntegratD Logging connector, you can emit logging information about the currently executing Boomi Process flow where it can be consumed by IntegratD for Boomi.
Boomi developers decide what, when, and how to emit logging information during Boomi processing pipelines by wiring up the connector at appropriate points in the Boomi Process Flow.
Design architecture
The connector is designed to be the following:
- Seamless
The connector captures all standard Boomi information including runtime and process information as well as all process and document properties (dynamic and otherwise) without any developer intervention. Payloads are optionally captured based on connector settings.
- Pass-Thru
The connector does not alter or obstruct the flow of data in any way. Its primary role is observational — to log information for auditing or monitoring purposes — and it must preserve the integrity and intent of all data passing through it. The component is non-intrusive and strictly functions with read-only in behavior in relation to the Boomi Process Execution.
- Messaging Driven and De-Coupled
The connector is designed with a clear separation of concerns, allowing logging emission to operate independently from logging consumption. It supports integration with multiple popular messaging platforms. This decoupled architecture promotes flexibility and scalability, enabling seamless integration into diverse enterprise environments. By abstracting the messaging layer, the component simplifies downstream processing and supports future platform expansion with minimal changes.
Connector configuration
Connector configuration involves two distinct configuration steps:
-
Connection – The connector needs to communicate with a supported messaging infrastructure platform for logging emission. Each platform has predefined configuration settings that need to be completed and tested via the Test Connection action.
-
Operation – The connector needs to know what type of event to emit. This approach creates a reusable connection and operation components which can be utilized across connector instances for all logging emission both within the current Boomi Process and across different Boomi Processes. This reusability is the Boomi recommended practice.
Supported editions
Java version requirement
Due to changes in messaging support after Java 8, this component is supported only on Java 11 and higher on a Boomi runtime or a runtime cluster. Java 8 included certain messaging features by default that are no longer available in newer Java versions, and this component is designed to align with the updated Java 11+ environment for consistent and reliable operation.
Prerequisites
- Messaging Platform – Logging Emission Support
Logging emission is supported through the specific well-known messaging platforms. One of these messaging platforms must be configured and accessible from the Boomi runtime or runtime cluster and can operate in either containerized or non-containerized environments, depending on the deployment architecture.
- IntegratD Platform – Logging Consumption Support
All versions of IntegratD for Boomi are supported for logging consumption. The IntegratD platform must be properly installed and configured within the target deployment infrastructure and the Boomi module must be enabled and configured according to recommended practices to ensure successful log message processing. For more information refer to www.mqattach.com.
Tracked properties
This connector has the following tracked properties that you can set or reference to indicate logging emission identifiers:
-
Transaction Id – The Boomi Execution Id unique to this Boomi execution. By default, this will be determined using the Execution propery Execution Id. This can be optionally set to a specific identifier, although this is not recommended to ensure uniqueness.
-
Job Id – The top-level Boomi Execution Id to this Boomi execution. This will be by default determined using the Execution property Top Level Execution Id. This can be optionally set to a specific identifier if this execution is part of a bigger overall job linked to a specific identifier.
Connector document properties
This connector has the following optional document properties that you can set or reference to add context to a Boomi execution. This contextual information will be used by the IntegratD platform during logging consumption.
| Connector Dynamic Property | Explanation | Default | Purpose within IntegratD |
|---|---|---|---|
| Transaction Company | The company name to link the Process Execution to | The Default IntegratD Company | Security - Transaction Visibility |
| Transaction Department | The department within the company to link a Process Execution. This must be a configured Department against the Company | None – By default executions are not linked to a department | Security - Transaction Visibility |
| Job Name | The Top-Level Name to Log for the Top-Level Execution | Boomi Execution Process Name if not already set | Informational - Transaction the Top-Level Name |
| Transaction Name | Execution Name to log for Boomi Execution | Boomi Execution Process Name | Informational - Transaction Name |
| Transaction Error Message | In a Failure Log Event this will be used as the Reason for the Failure | Message from the try-catch output or the business rule shape | Informational - Reason for Transaction Failure |
| Step Name | During the Logging of Event the Step Name to use | The Shape Name or description of the Shape | Step Description within the Execution Flow |
| Progress Perc | In a Progress Event this will be used to determine Execution Progress Percentage | 0 | Updates the Progress Display for Execution Flow |
| Incoming Document Count | Incoming number of Documents | Execution Property Document Count | Informational – Incoming Document Count |
| Process Name | Boomi Execution Process Name | Execution Property Process Name | Informational – The Boomi Process Name |
| Process Id | Boomi Execution Process Identifier | Execution Property Process Id | Informational – Boomi Process Identifier |
| Account Id | Boomi Execution Account Identifier | Execution Property - Account Id | Informational – Boomi Account Identifier |
| Runtime Id | Boomi Runtime Execution Id | Execution Property – Runtime Id | Informational – Boomi Runtime Identifier |
| Runtime Name | Boomi Runtime Execution Name | Execution Property – Runtime Name | Informational – Boomi Runtime Name |
