Covered in this article
Amqp component pages
Created on Updated on
AMQP component

AMQP component

A open standard application layer protocol for passing business messages between applications or organizations.

Latest changelog

1.3.1 (May 22, 2020)

  • Update sailor version to 2.6.7

To see the full changelog please use the following link.

Description

A component designed to talk to Advanced Message Queuing Protocol, (AMQP) APIs. AMQP is an open standard for passing business messages between applications or organisations (see amqp.org for more).

AMQP component establishes an asynchronous communications with queues and topics to publish or consume records.

How works

The consumer will register a non-exclusive non-durable queue with autodelete=true and without any dead-letter. Name of the queue will be dynamically generated based on the USER_ID, FLOW_ID prefixed with eio_consumer_. This queue will be bound to the exchange with specified bound key or multiple bound keys that are specified in one string separated by commas.

Requirements

Environment variables

This component will automatically encrypt data that is sent to the queue when following environment variables are set:

  • ELASTICIO_MESSAGE_CRYPTO_IV - vector for symmetric encryption
  • ELASTICIO_MESSAGE_CRYPTO_PASSWORD - password for symmetric encryption

These variables are by default available in the platform environment. Data will be encrypted using symmetric AES-256 encryption.

Credentials

This component expects user to provide a AMQP URL, username and password should be embedded as part of the URL, for example amqp://foo:bar@server. You can also use URL syntax to provide further parameters and any other options (e.g. vHost or port).

Credentials

Triggers

Consume

Will consume the incoming message object that contains body with the payload. If the exchange doesn’t exist it will be created on start.

Optionally you can use # or * to wildcard. For more information check the tutorial provided at the RabbitMQ site.

Consume

Actions

Publish

Will publish the messages into an exchange. This exchange will be created on start if it doesn’t exists.

Publish

Known limitations

Following limitations of the component are known:

  • You can not publish to the default exchange.
  • All published exchanges are topic exchanges by default. However, with the topic exchanges one can emulate direct and fanout exchanges.