Getting Started
Basic Concepts
Tutorials
Advanced Concepts
How-to Guides
Building integration flows
Data transformation
Integration patterns
Developing Components
Tenant Management
Components
CRM Components
ERP Components
E-Commerce Components
Basic Components
Utility Components
References
Sailor
Component Descriptor
Covered in this article
Related articles
Contracts and Workspaces Understanding credentials Data Sample Overview Creating your first integration flow Getting Started What is an integration component? What is an integration flow? What is a tenant? Take a tour of the product Creating a webhook flow Building a component in Java Building a component in Node.js Content-Based Routing Deploying a component How-to Guides Managing flow history Managing OAuth Clients Managing user roles in a tenant Managing Workspaces Mapping data Building real-time flows Sending data to a list of recipients REST API component Managing your SSH keys Managing your Teams/Components Allmysms component Amazon MWS component AppDirect Component AWS Lambda component AWS SNS component Bazaarvoice component ChannelAdvisor component Code component Configuration component CSV component Docusign component Dun-and-bradstreet component Ebay component Edifact-parser component Email component Exact Online component Filter component Google PubSub component Google-shopping component Google-translate component Goto-webinar component Google Spreadsheets component Components JDBC Component JDBC Component JDBC Component Jsonata component Key-value-component component Ldap component Lightspeed-ecom component Lightspeed-retail component Lionbridge-translation component Magento1 component Magento2 component Mailchimp component Mandrillapp component Mapper component Microsoft Dynamics CRM component MsSQL component NetSuite component ODATA component Outlook component Petstore-nodejs component Pipedrive component Postgresql component Quickbooks-component component Request-reply component Rest API component Router component Salesforce-cpq component Salesfoce Component Sdl-translate component Sftp component Shopify-admin component Shopware component Simple-trigger component Smarty-streets component Soap component Splitter component Stripe component Sugar-crm component Timer component Twitter component Webhook component Xml component Component Descriptor Structure References Sailor compatibility matrix View Classes

AMQP component


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).

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.

Actions

Publish

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

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.

License

Apache-2.0 © elastic.io GmbH