Skip to main content
Feedback

IntegratD Logging - Partner connection

Logging emission is supported through connection to one of the following messaging platforms:

Connection information must be completed by the developer. Ideally, this connection should be shared across your Boomi Process Flows, which is the recommended Boomi practice.

Once the connection information is completed, the Test Connection option should be utilized to confirm connecting to the selected messaging platform.

ElementDescriptionRequiredDefault
MQ Connection TypeThe selected MQ Messaging PlatformMandatory
Common Across Platforms
User AuthenticationSecurity Credentials to access the Messaging PlatformOptional
Log QueueLog messages are directed to queues within the messaging platform of choice. The queue name can be altered as required to support policies and standardsMandatoryINTEGRATD.BOOMI.LOG
Fail Flow on ErrorIn the event of an error within the connector itself should that failure propagate up and fail the Boomi Execution or not. By default, this is turned off in strict adherence to the connector design goal of being a pass-thru connector.OptionalFalse
ActiveMQ Classic or Artemis
MQ ServerThe hostname or IP Address of the ActiveMQ ServerMandatory
MQ Server PortThe listener port of the ActiveMQ ServerOptional61616
Rabbit MQ
MQ ServerThe hostname or IP Address of the Rabbit MQ ServerMandatory
MQ Server PortThe listener port of the Rabbit MQ ServerOptional5672
IBM MQ
Queue ManagerIBM MQ Queue Manager to connect toMandatory
Path to JSON CCDTCCDT which describes queue managers and their connection information. https://www.ibm.com/docs/en/ibm-mq/9.2.x?topic=tables-configuring-json-format-ccdt This path must be accessible to the runtime environment.Mandatory

Additional resources

On this Page