With Digibee, connect IBM MQ queues and topics to Salesforce, Workday, Kafka, and cloud platforms with no firewall changes.
Additional SaaS pipelines deploy at the same usage-based pricing.
Cloud pipelines access z/OS data with no inbound firewall ports opened.
MQ stays live; Digibee routes its events to Kafka and SaaS.
Ingest events from Kafka topics sourced by the IBM MQ Kafka Connector. Deliver MQ-originated data to the cloud, supporting AVRO schemas for enterprise-grade event streaming.
Edge Router inside the customer data center creates outbound-only encrypted tunnels to IBM MQ, DB2, and z/OS with no inbound firewall ports.
Calls SOAP/WSDL interfaces from IBM App Connect Enterprise and IBM WebSphere directly. No REST translation layer needed. SOAP V2 and V3 supported.
Query IBM DB2 records and feed results into Salesforce, Workday, or ServiceNow integration pipelines.
Connect IBM MQ SaaS on AWS to Workday and ServiceNow seamlessly. Create a centralized, automated operational environment.
Bridge legacy IBM MQ queues to Kafka event streams. Feed transactional data to analytics engines for instant decisions.
Eliminate manual data entry and route IBM MQ purchase order messages directly to Salesforce CRM.
Expose IBM MQ and DB2 core-banking transactions to modern cloud services without touching the mainframe.
Digibee's JMS Connector and JMS Trigger connect to IBM MQ using standard JMS credentials (hostname, port, channel name, and queue manager). Pipelines can publish to MQ queues and topics or consume from them, with configurable consumer parallelism.
No. Digibee does not replace IBM MQ—it extends it. IBM MQ remains the authoritative transactional message bus; Digibee adds the cloud-native orchestration layer that routes MQ messages to SaaS applications, Kafka, and cloud systems MQ cannot natively reach. For net-new SaaS integration workloads where deploying a full CP4I environment is impractical, Digibee is the right fit.
Most joint deployments start with a single JMS Trigger pipeline consuming from one IBM MQ queue and routing messages to a SaaS application such as Salesforce or Workday. For on-premises MQ environments, an Edge Router deploys adjacent to the queue manager to establish ZTNA connectivity, typically a one-day infrastructure task. A working first pipeline can be configured in 30 minutes once ZTNA is established.
Yes. Digibee acts as a high-speed modernization bridge for z/OS environments. By consuming messages from IBM MQ queues or querying DB2 databases directly, Digibee transforms legacy EBCDIC or COBOL data structures into modern JSON APIs—powering web and mobile apps with real-time mainframe data without a rip-and-replace project.
Digibee provides ongoing platform support through its standard SLA tiers, with built-in monitoring, alerting, and pipeline observability. Digibee handles pipeline logic and JMS connector behavior; the customer's IBM MQ team handles the MQ infrastructure. IBM DB2 connectivity requires a one-time driver activation via Digibee support before the initial deployment.