Red Hat Summitこのコンテンツは選択した言語では利用できません。
Chapter 37. Azure Storage Queue Service Component
Available as of Camel version 2.19
The Azure Queue component supports storing and retrieving the messages to/from Azure Storage Queue service.
Prerequisites
You must have a valid Windows Azure Storage account. More information is available at Azure Documentation Portal.
37.1. URI Format
azure-queue://accountName/queueName[?options]
azure-queue://accountName/queueName[?options]
The queue will be created if it does not already exist.
You can append query options to the URI in the following format, ?options=value&option2=value&…
For example in order to get a message content from the queue messageQueue in the camelazure storage account and, use the following snippet:
from("azure-queue:/camelazure/messageQueue").
to("file://queuedirectory");
from("azure-queue:/camelazure/messageQueue").
to("file://queuedirectory");37.2. URI Options
The Azure Storage Queue Service component has no options.
The Azure Storage Queue Service endpoint is configured using URI syntax:
azure-queue:containerAndQueueUri
azure-queue:containerAndQueueUriwith the following path and query parameters:
37.2.1. Path Parameters (1 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| containerAndQueueUri | Required Container Queue compact Uri | String |
37.2.2. Query Parameters (10 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| azureQueueClient (common) | The queue service client | CloudQueue | |
| credentials (common) | Set the storage credentials, required in most cases | StorageCredentials | |
| bridgeErrorHandler (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean |
| exceptionHandler (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | ExceptionHandler | |
| exchangePattern (consumer) | Sets the exchange pattern when the consumer creates an exchange. | ExchangePattern | |
| messageTimeToLive (producer) | Message Time To Live in seconds | int | |
| messageVisibilityDelay (producer) | Message Visibility Delay in seconds | int | |
| operation (producer) | Queue service operation hint to the producer | listQueues | QueueServiceOperations |
| queuePrefix (producer) | Set a prefix which can be used for listing the queues | String | |
| synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
Required Azure Storage Queue Service component options
You have to provide the containerAndQueue URI and the credentials.
37.3. Usage
37.3.1. Message headers evaluated by the Azure Storage Queue Service producer
| Header | Type | Description |
|---|---|---|
37.3.2. Message headers set by the Azure Storage Queue Service producer
| Header | Type | Description |
|---|---|---|
37.3.3. Message headers set by the Azure Storage Queue Service producer consumer
| Header | Type | Description |
|---|---|---|
37.3.4. Azure Queue Client configuration
If your Camel Application is running behind a firewall or if you need to have more control over the Azure Queue Client configuration, you can create your own instance:
StorageCredentials credentials = new StorageCredentialsAccountAndKey("camelazure", "thekey");
CloudQueue client = new CloudQueue("camelazure", credentials);
registry.bind("azureQueueClient", client);
StorageCredentials credentials = new StorageCredentialsAccountAndKey("camelazure", "thekey");
CloudQueue client = new CloudQueue("camelazure", credentials);
registry.bind("azureQueueClient", client);and refer to it in your Camel azure-queue component configuration:
from("azure-queue:/camelazure/messageQueue?azureQueueClient=#client")
.to("mock:result");
from("azure-queue:/camelazure/messageQueue?azureQueueClient=#client")
.to("mock:result");37.4. Dependencies
Maven users will need to add the following dependency to their pom.xml.
pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-azure</artifactId>
<version>${camel-version}</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-azure</artifactId>
<version>${camel-version}</version>
</dependency>
where ${camel-version} must be replaced by the actual version of Camel (2.19.0 or higher).
37.5. See Also
- Configuring Camel
- Component
- Endpoint
- Getting Started
- Azure Component
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}