Back
IBM MQ
Download 
docker pull solace/solace-pubsub-connector-ibmmq
Click to Copy!
View Documentation
Asset Type:
Connectors
Provider:
Provider: Solace
Category:
Messaging/Eventing
Endpoint:
Source, Target
Support:
Solace – Support Available
Contact Us

IBM MQ

The Solace PubSub+ Connector for IBM MQ bridges data between the Solace PubSub+ Event Broker and IBM MQ providing a flexible and efficient way to integrate IBM MQ application data with your Solace-backed, event-driven architecture and the Event Mesh. The connector uses IBM MQ Classes for JMS to connect to MQ Queue Managers and access their endpoints and makes use of MQ-specific features as exposed via the MQ Classes for JMS.

This 2-way integration is configured via “workflows” in your connector instance. A workflow is a source-to-processing-to-target data pipeline configured within the connector runtime. Each workflow (you can have up to 20 defined per connector instance), defines a source (e.g. PubSub+ queue), any header processing necessary for the target, and a target destination (e.g. an IBM MQ Queue Manager queue/topic). When active, events will stream across these Workflows.

Show more

Features & Use Cases

The connector is available as:

  • A runnable package based on a Java JAR file including a start script
  • A container image suitable for running in a container runtime such as Docker or Podman

The PubSub+ Connector for IBM MQ is a “self-contained connector” from Solace. All self-contained connectors share a common architecture and provide a number of enterprise services to the connectors such as:

  • A local management server accessible over HTTP(s) and JMX exposing endpoints for:
    • Health check
    • Metrics monitoring
    • Log file access
    • Workflow adminstration (start & stop workflows)
  • A common set of configuration options for:
    • logging – log levels, log file size, archive and rollover rules, appenders to export to other log services
    • security setup for management endpoints – authentication and authorization to the endpoints, TLS for HTTPS endpoints
  • Various runtime deployment options:
    • Standalone
    • Active_Standby – for redundancy (you can have more than 1 standby instance)
    • Active_Active – for horizontal scaling (where the source of data will support multiple active consumers such as a non-exclusive queue in PubSub+)

Still have questions?

Explore Other Connectors Get in Touch