Skip to main content

Azure Storage Outbound Adapter

ConnXio (CX) lets customers receive messages from the CX pipeline by configuring connections to Azure Storage accounts. We currently support messages as blobs or files. This page details how to configure Azure storage connections and what functionality is available by delivering files through this medium.

Limitations​

Azure Storage provides a modern interface for file and message transfer which is robust, fast and cheap. By leveraging the Azure infrastructure Microsoft has turned storage into a powerhouse in and of itself which CX takes full advantage of. Essentially this means that there are very few limitations on the technology itself, this enables CX to handle an almost unlimited amount of messages, different types of files and metadata through the Azure Storage technology. The only real limitation is the CX-wide limit of 100mb per message.

Configuring Azure Storage delivery​

To configure CX to start sending your messages select the Azure Storage option in "Outbound Connections" shape:

img

A new window pops up, we will be using blob communication as an example. Add data as seen below:

img

  • Adapter Name: The logical name of the adapter. This is shown in the configuration view on close.
  • Storage type: Select storage type to use. Types include: Blob, File, Queue and Table.
  • Connection String Security Configuration: Reference to the Security Configuration that contains the relevant connection properties.
  • Container Name: The name of the container. This container must exist before CX start picking messages. We will not create it for you.
  • Outbound Filename Pattern: Uses variable replacement to generate file names, this is described in detail on the variable replacement page.
  • Send Acknowledgement: Is explained here.
  • Duplicate Detection: Terminate the message if the exact same has been processed any time the last five days. ConnXio does not guarantee that no duplicates will be sent.
  • Termination Status: The status used for logged in when a duplicate is terminated. If left empty, the status will default to 'Terminated'

For Azure Files the only difference is the directory field which specifies which directory CX should target for file pickup. If this is kept blank the root directory is used.

Retry​

Retry on all outbound adapters is currently handled by the linear retry described on the Retry page. This may change in the future as we are looking into enabling backoff retry.