AMQP Connector supports AMQP by using a Camel event listener. Processes that connect to AMQP can triggered upon an event such as arrival of an AMQP message or a file in a file system.
AMQP enables one connection or one broker to support multiple queues using an over-the-wire format, similar to JMS providers, ApacheMQ or a Microsoft Azure service bus. You can access different file systems and enable different types of file processing, based on the connector definitions. These connectors run on an agent and where applicable, are accessible from the cloud.
Note: When you connect to files, your performance might be impacted by the speed of the underlying file systems.
When you publish a process that uses the AMQP connector, the binding details are stored in a catalog file (entrypoints.xml) that determines how to route the message.
The message payload is defined by the connector.
You can use the same AMQP connection to connect to the source as well as a target. When you trigger a process, "fan out" is supported, so one message can spawn multiple processes.