Overview
Boomi licensing follows the connections an account holds, and connections accumulate: one per project, per environment, per partner. By the time a renewal arrives, nobody can say which are active, which belong to retired projects and which carry a few documents a day.
Challenge
The renewal proposal listed far more connections than the integration team believed it used. Several had been created for projects that ended years earlier, and a few simple SFTP-to-database flows ran very high volumes on connections priced the same as complex orchestrations. The team needed numbers and a defensible position before the renewal date.
Environment
A Boomi account with development, test and production environments, several local and cloud runtimes, and integrations between enrolment, claims and partner file exchanges.
Approach
AceMQ pulled execution counts per connection and process from the platform's reporting and APIs for a full year, classified each connection as active, dormant or duplicated, and sorted the active ones by complexity. Two simple high-volume file flows were designed as small Spring Boot services; complex EDI and orchestration stayed on Boomi. AceMQ does not resell Boomi and gave the renewal position as evidence.
Solution
- Exported a year of execution counts per connection and process
- Classified connections as active, dormant or duplicated across all environments
- Found connections left from retired projects and shared ones configured several ways
- Ranked active flows by complexity and by document volume
- Designed two simple SFTP-to-database flows as small Spring Boot services with parallel running
- Documented which integrations belong on Boomi and the criteria for the next one
- Prepared the renewal position with the connection count the team could defend
Outcome
The administrator went into renewal with a connection count it could defend line by line, retired the dormant connections, and had a tested path for moving two high-volume flows to services. The team also gained criteria for deciding where the next integration should live.