Boomi Support
Last reviewed by Scott Sternloff
AceMQ supports the Boomi processes and AtomSphere integrations you run in production — Atoms exhausting heap under concurrent load, processes stalling on connector timeouts, EDI trading partner issues halting order flows, and environment configurations that looked right but break under real throughput. Every ticket reaches a named senior engineer who knows Boomi's failure modes, not a help desk.
Support quotes answered within 1 hour, by a senior engineer.
Planning a build, upgrade or migration instead? See AceMQ Boomi consulting and services.
Customers
Partners
Incident Triage
These are real symptoms from real Boomi production environments — and the first thing our engineers check when one comes in.
| Symptom you're seeing | What we check first | Typical resolution |
|---|---|---|
| Boomi Atom running out of memory, processes failing or restarting | JVM heap allocation against concurrent execution count and document size. Processes materializing large XML or JSON payloads in full — especially maps on large bodies — exhaust heap under concurrency. Check whether asynchronous processing is configured where synchronous blocking is the real issue. | 1–3 hours |
| Boomi process executions queuing up, throughput dropping under load | Atom thread pool configuration against the concurrency your processes need. The default worker thread count is often undersized for production workloads that grew since initial deployment. Also check whether queued processes are waiting on a slow backend connector rather than a thread pool constraint. | 1–3 hours |
| Connector timing out or returning intermittent errors against a backend | Connection pool limit and timeout settings on the connector component. A pool exhausted below concurrent demand makes processes queue waiting for a connection — the timeout then hits the connection wait, not the remote API. Check pool size, max wait time, and whether idle connections are being released. | 1–2 hours |
| EDI process failing — 997 acknowledgement not received or rejected | ISA control number sequence, functional group configuration, and partner-specific interchange settings. A 997 rejection usually means an envelope mismatch — incorrect ISA06 qualifier, duplicate control number, or functional group ID not matching what the trading partner expects. Check the trading partner profile against the partner's specifications. | 1–3 hours |
| Boomi process deployed successfully but not executing on schedule | Atom status on the process's assigned Atom or Molecule — a scheduled process silently stops running when its Atom is unhealthy or the schedule listener has stalled. Also verify the schedule is attached to the correct Atom environment and the process component version promoted matches what you expect. | Same day |
| Boomi API gateway returning 500 or not routing requests to the backend | API component configuration — shared server port binding, SSL certificate validity, and the route mapping between the API endpoint and the backing Boomi process. A certificate expiry on the shared web server will bring down all APIs on that Atom simultaneously. | 1–2 hours |
| Documents processed twice after an Atom restart or process re-deployment | Whether the process uses a start shape with a connector that supports 'Get' with acknowledgement, or whether reprocessing is triggered by the restart polling documents not yet fully committed. Boomi's at-least-once behavior means idempotency handling must be explicit in your process design, not assumed. | 2–4 hours |
| Boomi Molecule node failing to join the cluster after restart | Network connectivity between Molecule nodes on the Atom working directory share. Molecules require shared storage — typically NFS — and if the mount is unavailable or permissions changed, the node starts but cannot see the shared working directory and fails to join. Also check whether the head node is healthy before investigating satellite nodes. | 1–3 hours |
Resolution times reflect typical Boomi engagements under an active AceMQ support contract. Every P1 closes with a written root-cause analysis.
What's Included
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
Atoms failing, processes stalling, EDI order flows halted, or API gateway returning errors. A senior engineer joins a live bridge within 15 minutes with access to diagnose — not a ticket acknowledgement or a request to open a Boomi support case.
JVM sizing against actual concurrent process load, connection pool right-sizing, identification of dormant connectors consuming license entitlements, and Atom consolidation where sprawl has driven unnecessary per-connection cost.
Heap profiling against real document sizes, map and transformation review for memory-inefficient patterns, thread pool configuration against actual throughput, and asynchronous execution pattern design for high-volume scenarios.
Every P1 closes with a written RCA: what failed, why, the fix applied, and the process, connector, or Atom configuration change that prevents recurrence. Delivered as standard on every production incident.
Database, Salesforce, SAP, HTTP/S, AS2, SFTP, and VAN connectors configured for the delivery semantics and error handling your integrations need. EDI acknowledgement handling, trading partner profile configuration, and interchange issue resolution.
Boomi Atom runtime upgrades, connector version management across environments, Molecule topology changes, and migration off Boomi entirely where the per-connection licensing math has stopped working.
Why AceMQ
Boomi per-connection licensing is often reviewed at contract renewal, not during the year. We track active connection usage against entitlements, identify dormant or consolidatable connectors, and fix the underlying architecture before you renew at the wrong tier.
The same senior engineers stay on your account. When a P1 call comes in at 3 a.m., diagnosis starts immediately — not after twenty minutes of someone learning your integration estate from scratch.
Most Boomi incidents touch a backend system as much as the Boomi process itself — SAP connection limits, Salesforce API governor limits, database pool exhaustion. We debug both sides, not just the Atom.
You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass to a Boomi-knowledgeable resource, and no escalation approval between you and someone who can actually fix the integration.
Boomi supports the AtomSphere platform. Your process design, map logic, connector configuration, JVM sizing, and the backend systems on both ends of your integrations are yours — and that is where incidents originate.
Engineers across 26+ countries and every time zone. Your 3 a.m. EDI failure is someone's mid-afternoon, not an overnight skeleton crew waiting for a region to wake up.
Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.
Escalation Path
Every tier reaches a senior Boomi engineer. There is no tier-1 triage layer to get through.
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
15-minute P1 response, 24/7.
A response time, not a resolution time.
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Pricing
AceMQ Boomi support contracts typically run $24,000–72,000 a year, depending on SLA level, scope (number of clusters or nodes, and environments) and deployment (self-managed, cloud-managed or Kubernetes).
| What moves the price | How it changes the contract |
|---|---|
| SLA level | Business-hours cover costs less than 24/7 cover with a 15-minute emergency response. |
| Scope | More clusters or nodes, and more environments, make a larger contract. |
| Deployment | Self-managed, cloud-managed and Kubernetes estates need different amounts of hands-on work. |
Covering several technologies under one contract, for example RabbitMQ, Kafka and Redis, earns an aggressive discount.
Support In Practice
Boomi support and remediation work from AceMQ. Each card links to the full write-up: the integration estate, what AceMQ diagnosed or changed, and the result.
Government Systems Integrator
A Boomi integration estate depended on RabbitMQ with no automated failover and no way to replay messages after an outage. AceMQ designed the DR model and the replay path, both under audit constraints.
Boomi
RabbitMQ
KubernetesIndustrial Equipment Manufacturer
Stopping month-end Atom restarts caused by maps that loaded entire order files into heap while several scheduled processes ran at once.
Boomi
PostgreSQLAutomotive Parts Supplier
Tracing rejected 997 acknowledgements on outbound 856 advance ship notices to interchange control numbers drawn from two different ranges.
BoomiRegional Benefits Administrator
Inventorying every Boomi connection by execution volume ahead of a renewal, then moving two simple high-volume flows off the platform.
Boomi
Spring FrameworkSupport options
AceMQ offers Boomi support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for the integrations your team runs, proactive monitoring that finds heap, retention and EDI problems first, Boomi operated in your own account, and the Atoms and Molecules run on AceMQ infrastructure. Basic runtimes, runtime clusters and public runtime clouds are covered.
You run it, we back you up
Best for: Integration teams that run their own Boomi processes and need senior cover when a nightly batch fails.
You run it, we watch it with you
Best for: Estates where a nightly process that failed for weeks is not an acceptable surprise.
We run it in your cloud or data centre
Best for: Teams that want Boomi run to a standard inside their own account without an integration on-call rota.
We host it and run it, as a service
Best for: Teams that want Boomi integrations run end to end without owning the runtime hosts.
| Who does what | Tier 1 24/7 support | Tier 2 Proactive monitoring | Tier 3 Managed, your infrastructure | Tier 4 Fully managed by AceMQ |
|---|---|---|---|---|
| Who runs Boomi day to day? | Your team | Your team, with AceMQ reviews | AceMQ | AceMQ |
| Where does it run? | Your infrastructure | Your infrastructure | Your cloud account or data centre | AceMQ infrastructure |
| 24/7 incident response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response |
| Health checks and CVE alerts | On request | Scheduled | Included | Included |
| Patching and upgrades | Your team, AceMQ advises | Planned with AceMQ | Done by AceMQ | Done by AceMQ |
| Monitoring and on-call | Your team | Your team | AceMQ | AceMQ |
| Data, keys and accounts | Yours | Yours | Yours | Your data, hosted by AceMQ |
Every Tier can start as an ad hoc engagement or an annual partnership, and you can move up or down a Tier as your team changes.
One partner for Boomi
Support is one part of what AceMQ does for Boomi. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.
24/7 emergency incident response with a 15-minute SLA, root cause analysis on every P1, Atom memory and performance tuning, connector and pool configuration, EDI and trading partner issue resolution, Boomi platform upgrades, and per-connection license cost governance. Every ticket is handled by a named senior engineer on your account — no tier-1 triage and no per-incident charge.
Typically the combination of JVM heap allocation and process design. Boomi maps operating on large document bodies materialize the entire document in memory — one large payload is manageable; ten concurrent ones at the default JVM heap settings are not. We profile heap usage against your actual concurrent process executions, review map logic for full-document materialization, and size the JVM to real load rather than adding Atoms to paper over the problem.
Boomi supports the AtomSphere platform as a product. We support the integrations you built on it. Process design, map logic, connector pool configuration, JVM sizing, EDI trading partner configuration, and the backend systems on both ends of your integrations are outside Boomi's support boundary and inside ours. The two are complementary — we also help you build a clean, evidenced case when an issue is a genuine platform defect.
Yes, and EDI failures are usually traceable to a small set of causes: ISA control number mismatches, partner-specific functional group configuration that was set at go-live and not updated, 997 acknowledgement handling that doesn't match the partner's expectation, or connectivity issues on the AS2 or SFTP channel. We triage the specific interchange and trading partner profile before assuming the issue is on our side.
Yes, including Molecule clusters on-premise, on AWS, on Azure, and on Google Cloud. Molecule failures have a different diagnostic profile than single-Atom failures — shared working directory access, head node health, and inter-node connectivity are all factors before looking at the application layer. We support the infrastructure layer alongside the Boomi processes rather than treating it as someone else's problem.
No. Boomi renamed its runtime terms: an Atom is now a basic runtime, a Molecule a runtime cluster, and an Atom Cloud a runtime cloud, with the shared Boomi-hosted clouds called public runtime clouds. The software and its failure modes are the same. We support the basic runtimes and runtime clusters you host, private runtime clouds, and processes deployed to a public runtime cloud, where Boomi runs the infrastructure but process design, maps and connector settings remain yours.
With access and a baseline. You add our engineers as users on your Boomi account with a role scoped to what you want us to do, and grant access to the hosts or clusters behind any runtimes you run yourself. We then review runtime health, JVM settings, scheduled processes, connector usage and recent execution errors, and give you a written list of risks before the first incident, so Boomi support begins with known problems.
Yes. AceMQ works on Boomi in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
Every AceMQ proposal is tailored to your requirements: your Boomi environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Boomi is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
Reactive cover, proactive reviews, or AceMQ running Boomi for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.
Production incident right now?Email a Boomi Architect
Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.
305-204-2607info@acemq.comPrefer to talk now? Call us directly or use the consultation tab to find a time that works.
