14 posts tagged with "Connectors"

As someone who entered the technology and iPaaS industry without a technical background, I have always been amazed at how Boomi has enabled me to achieve the same high-level technical outcomes as traditional developers, all while staying low-code. One of my first integration projects involved interacting with Salesforce's API. Boomi's branded connector allowed me to easily authenticate, interact with objects, and import profiles without needing to dig through API documentation.

You've deployed a custom connector to Boomi. Listener processes are running. Everything looks fine until someone notices messages stopped flowing an hour ago. No alert fired, no error in the UI, just a silent queue and a gap in process reporting.

If you've been there, here's what's actually happening: Boomi Platform knows whether your listener is aware of the deployment state and whether it started up successfully, but it has no built-in way to know if your connector can actually still reach the external system it's talking to. That visibility gap is what the updateStatus APIs are designed to close.

In this post, we'll walk through the three updateStatus overloads on the Listener interface and show exactly how to apply them using the Boomi Event Streams connector with a real-world example covering the most common scenarios you'll run into as a connector developer.

Listeners in Boomi run across multiple JVM instances depending on your runtime type:

• Basic runtime: single JVM, one instance
• Runtime cluster: N cluster nodes, each running the listener independently
• Runtime cloud: up to N execution worker instances per tenant

Previously, all of these collapsed into a single top-level status: listening, paused, or errored. That's fine for a single-node basic runtime. But if you're running a Runtime cluster or Runtime cloud with a dozen workers or nodes, it leaves a real blind spot. Here's what that blind spot looks like in practice.

If you have ever written a listener connector, you can unit-test your parsing, config, and models. But the moment your code calls listener.submit(...), you are talking to the runtime, and the runtime is not in your test. That path stayed untested, or you deployed to a Boomi Runtime and watched the logs.

Connector SDK 2.30.1 adds a small package, com.boomi.connector.testutil.listen, that puts a working stand-in for the Boomi Runtime inside your test. The centerpiece is SimpleListener: a real, in-memory Listener you hand to your operation. It records what you submit, closes payloads the way a Runtime does, tracks status updates, runs batches through their real single-use lifecycle, and lets you script what the process "returns."

Ever needed to show certain operations only to specific connector instances? As a connector developer, you often need to control which operations are available — based on the connector instance a user is working with. Maybe you have standard and advanced operations in the same connector, and you want to gate the advanced ones behind a specific configuration. Or perhaps you're building a connector family where different editions expose different capabilities.

Connector tagging gives you exactly this control. By declaring tags on operations in your connector descriptor and assigning tags to connector instances via the ConnectorMetadata API, you can dynamically show or hide operations based on the tags present on a given connector.

The AI world is moving fast, and everyone’s trying to bring generative AI into their apps, from auto-generating content to building smarter assistants. But let’s be real, integrating it into real systems can be a headache. Industry analysis shows that over 65% of AI projects hit delays, often because teams get stuck managing APIs, auth flows, and security instead of building the features they actually care about.

That’s where Boomi’s Amazon Bedrock connector comes in! It bridges the Boomi Platform and Amazon Bedrock’s powerful generative AI capabilities, so you no longer have to manage REST API calls, request signatures, or authentication flows.

Every connector developer has bumped into the limitations of the default Custom Properties table at some point. Fixed labels, generic fields, and features like encryption don’t always reflect what your users actually need. The good news? The latest SDK (2.28.3) enhancements finally give you the freedom to shape this table the way you want, and it’s much simpler than you might expect.

Here’s how you can transform the default table into something that truly fits your connector and why these changes matter.

Have you ever built a connector that sends data into a process and then just waits, wondering what happens next? You’re not alone, we’ve all been there. The good news is that with Connector SDK 2.28.3, your connectors can finally stop guessing and start learning!

Earlier SDKs let connectors send data and maybe get a status, but not the actual output. The new document retrieval feature in SDK 2.28.3 changes that, letting listener connectors not just send data but also receive the documents and properties a process generates. Now your connectors can react to real outcomes, adapt intelligently, and deliver what developers rely on.

Connectors are the lifeblood of Boomi Integration powering data movement, synchronization, and real-time events across systems. The Boomi Connector SDK gives you the flexibility to create custom connectors tailored to your specific integration needs. Combined with the Cursor Integrated Development Environment you can create a high-performance workspace to accelerate connector development.

This blog walks you through preparing your workspace, integrating documentation, applying coding rules, and automating setup so you can start building robust connectors quickly and consistently.

As developers, we've all been there - staring at a failing test suite, wondering why our mocks aren't working as expected. Testing can be particularly challenging when building connectors that integrate with external systems. You need to simulate responses from systems you don't control, mock complex behaviors, and ensure your connector handles all edge cases correctly. In this blog post, we'll explore how to refactor your connector code for enhanced testability using standard Mockito, completely bypassing the common drawbacks of PowerMock.

When building connectors on the Boomi Enterprise Platform, the connector-descriptor.xml plays a key role; it defines how the platform dynamically builds the user interface for creating connections and operations. With recent updates to the Connector SDK and platform, developers now have the flexibility to design custom sections within the connection configuration. This means you can group related fields into separate, clearly labeled tabs, each with its own summary—making the UI cleaner and easier to navigate.

Connectors are the main components in Boomi Integration. If you use the Integration product and have built integration processes, you’ve used connectors to some extent. Connectors give your integrations life. They can pull data from cloud services, push data to local disks or repositories, or even listen to real-time events. This provides you with a set of tools, libraries and resources to build connectors to suit your needs.

As an Integration Developer, you aim to craft efficient integrations that deliver rapid results and optimal performance. Optimizing the connector configuration is a crucial step that can yield significant benefits. While this might seem like a small tweak, it can have a massive impact on your system's performance. Whether it's faster execution, reduced resource usage, or smoother integrations, the right optimizations can transform bottlenecks into seamless workflows. When every second counts, an efficient connector can make all the difference for large-scale operations.

Thinking about building a Boomi connector? One crucial element is how your connector handles data, specifically how it accepts and processes that data. As a connector developer, you're creating a bridge that needs to handle complex configurations while remaining user-friendly.

Boomi offers various property types, each serving a specific purpose. Choosing the right one is essential to ensure your connector is smooth, efficient, and intuitive.