Azure Blob Egress Connector
Version: 17.07
Supported Since: 17.07
What is an Azure Blob Egress Connector?
Azure Blob Egress Connector can be used to push files to an Azure Blob container.
When sending messages to a blob container, UltraESB engine expects the file content as the message payload and file name as a variable. However, this connector can be configured to override the file name of the original file with an arbitrary file name.
| Azure credentials associated with an account which has write permission to the target container will be necessary when configuring this connector. |
| In order to use the Azure Blob Egress Connector, you must first select the Azure Connector dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the Azure Connector dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the Azure connector dependency. |
Out Ports
On Exception |
The message will be emitted from this out port if the processing element fails to push the message content to the target container. |
Side Ports
Connector Operation |
This port is used to connect operational elements to the Egress Connector. By-default, user does not have to connect any operational element and the default connector operation will be used. |
Parameters
* marked fields are mandatory
Azure Account Name |
Basic |
Azure Account Name is required. |
Azure Account Key |
Basic |
Azure Account Key is required. |
Default Endpoints protocol * |
Basic |
Name of the endpoints protocol to be used, which is located in the configured Azure storage account. |
Destination container name * |
Basic |
Name of the Azure container, which is located in the configured Azure storage account. |
File Name location * |
Basic |
File name for the payload to be saved (if there is an original name to the file, it will be preserved if this property is not provided). In-order to construct the file name, you can use message headers, message properties, additional variables set,message ID, message context ID, and message context properties in following formats respectively. @{message.headers.<name>} @{message.properties.<name>} @{variable.<name>} @{message.id} @{mc.id} @{mc.properties.<name>} |
Sample Use Case
In this case, assume that an Agency wants to backup all of their large binary files to an Azure blob storage, in-order to save their local storage space for new files.
Figure 1. Integration Flow
File Listener will be configured as below to pick only required files from the source folder
Figure 2. File Listener configuration
Azure Egress Connector will be configured as below to push Azure objects.
Figure 3. Azure Blob Egress Connector configuration
Figure 4. Configuration of Add New Transport Header
Product and company names and marks mentioned are the property of their respective owners and are mentioned for identification purposes only.
In this topic
In this topic