Listening service architecture for Jitterbit private agents

Introduction

The listening service can run an integration operation when an event occurs on an endpoint. It works only with supported connectors and activities, and only on private agent groups.

Architecture diagram

This diagram shows how an event message moves through the system when using a single private agent:

1. An operation containing a connector configured with an event listening activity is deployed and enabled for listening. One listening activity can be used in many operations and projects to receive the same event but process it differently.

2. The listening service within the agent will start a listener for that operation.

3. The listener will start actively listening for any event notifications from the endpoint.

4. When an event happens at the endpoint, it publishes an event notification that can be received by its subscribers.

5. The listener picks up the event notification message.

6. If there is one agent in the agent group, the listener relays the event message to the operation. If the agent group contains the minimum number to allow full listening service capabilities, the event message is passed to the agent with the least workload.

7. On receiving the event notification, the operation will trigger a downstream operation.

When the listening service is disabled, agents in an agent group communicate directly with Harmony. When enabled, and a minimum number of agent nodes are active, agents communicate with each other to form a cluster. The first agent registered is nominated as the cluster leader. The leader is responsible for receiving messages and distributing them to cluster members for processing. The cluster leader distributes the load among all the agents and ensures that no two agents process the same message.