Huawei Distributed Message Service (DMS)
Since Camel 3.12
Only producer is supported
Huawei Cloud Distributed Message Service (DMS) component allows you to integrate with DMS provided by Huawei Cloud.
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-huaweicloud-dms</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The Huawei Distributed Message Service (DMS) component supports 2 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
|
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
Endpoint Options
The Huawei Distributed Message Service (DMS) endpoint is configured using URI syntax:
hwcloud-dms:operation
with the following path and query parameters:
Path Parameters (1 parameters)
Name | Description | Default | Type |
---|---|---|---|
Required Operation to be performed. |
String |
Query Parameters (29 parameters)
Name | Description | Default | Type |
---|---|---|---|
Required Access key for the cloud user. |
String |
||
The username of a RabbitMQ instance. This option is mandatory when creating a RabbitMQ instance. |
String |
||
The ID of an available zone. This option is mandatory when creating an instance and it cannot be an empty array. |
List |
||
DMS url. Carries higher precedence than region parameter based client initialization. |
String |
||
The message engine. Either kafka or rabbitmq. If the parameter is not specified, all instances will be queried. Enum values:
|
String |
||
The version of the message engine. This option is mandatory when creating an instance. |
String |
||
Ignore SSL verification. |
false |
boolean |
|
The id of the instance. This option is mandatory when deleting or querying an instance. |
String |
||
The password for logging in to the Kafka Manager. This option is mandatory when creating a Kafka instance. |
String |
||
The username for logging in to the Kafka Manager. This option is mandatory when creating a Kafka instance. |
String |
||
The name of the instance for creating and updating an instance. This option is mandatory when creating an instance. |
String |
||
The maximum number of partitions in a Kafka instance. This option is mandatory when creating a Kafka instance. |
int |
||
The password of a RabbitMQ instance. This option is mandatory when creating a RabbitMQ instance. |
String |
||
The product ID. This option is mandatory when creating an instance. |
String |
||
Required Cloud project ID. |
String |
||
Proxy server ip/hostname. |
String |
||
Proxy authentication password. |
String |
||
Proxy server port. |
int |
||
Proxy authentication user. |
String |
||
Required DMS service region. |
String |
||
Required Secret key for the cloud user. |
String |
||
The security group which the instance belongs to. This option is mandatory when creating an instance. |
String |
||
Configuration object for cloud service authentication. |
ServiceKeys |
||
The baseline bandwidth of a Kafka instance. This option is mandatory when creating a Kafka instance. |
String |
||
The message storage space. This option is mandatory when creating an instance. |
int |
||
The storage I/O specification. This option is mandatory when creating an instance. |
String |
||
The subnet ID. This option is mandatory when creating an instance. |
String |
||
The VPC ID. This option is mandatory when creating an instance. |
String |
||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
Usage
Message properties evaluated by the DMS producer
Header | Type | Description |
---|---|---|
|
|
Name of operation to invoke |
|
|
The message engine. Either kafka or rabbitmq |
|
|
Instance ID to invoke operation on |
|
|
The name of the instance for creating and updating an instance |
|
|
The version of the message engine |
|
|
The baseline bandwidth of a Kafka instance |
|
|
The message storage space |
|
|
The maximum number of partitions in a Kafka instance |
|
|
The username of a RabbitMQ instance |
|
|
The password of a RabbitMQ instance |
|
|
The VPC ID |
|
|
The security group which the instance belongs to |
|
|
The subnet ID |
|
|
The ID of an available zone |
|
|
The product ID |
|
|
The username for logging in to the Kafka Manager |
|
|
The password for logging in to the Kafka Manager |
|
|
The storage I/O specification |
If any of the above properties are set, they will override their corresponding query parameter.
List of Supported DMS Operations
-
createInstance
-
deleteInstance
-
listInstances
-
queryInstance
-
updateInstance
Create Instance
To create an instance, you can pass the parameters through the endpoint, the exchange properties, and the exchange body as a CreateInstanceRequestBody object or a valid JSON String representation of it. Refer to this for the Kafka parameters and the RabbitMQ parameters. If you choose to pass these parameters through the endpoint or through exchange properties, you can only input the mandatory parameters shown in those links. If you would like to have access to all the parameters, you must pass a CreateInstanceRequestBody object or a valid JSON String representation of it through the exchange body, as shown below:
from("direct:triggerRoute")
.setBody(new CreateInstanceRequestBody().withName("new-instance").withDescription("description").with*) // add remaining options
.to("hwcloud-dms:createInstance?region=cn-north-4&accessKey=********&secretKey=********&projectId=*******")
from("direct:triggerRoute")
.setBody("{\"name\":\"new-instance\",\"description\":\"description\"}") // add remaining options
.to("hwcloud-dms:createInstance?region=cn-north-4&accessKey=********&secretKey=********&projectId=*******")
Update Instance
To update an instance, you must pass the parameters through the exchange body as an UpdateInstanceRequestBody or a valid JSON String representation of it. Refer to this for the Kafka parameters and the RabbitMQ parameters. An example of how to do this is shown below:
from("direct:triggerRoute")
.setBody(new UpdateInstanceRequestBody().withName("new-instance").withDescription("description").with*) // add remaining options
.to("hwcloud-dms:updateInstance?instanceId=******®ion=cn-north-4&accessKey=********&secretKey=********&projectId=*******")
from("direct:triggerRoute")
.setBody("{\"name\":\"new-instance\",\"description\":\"description\"}") // add remaining options
.to("hwcloud-dms:updateInstance?instanceId=******®ion=cn-north-4&accessKey=********&secretKey=********&projectId=*******")
Using ServiceKey Configuration Bean
Access key and secret keys are required to authenticate against cloud DMS service. You can avoid having them being exposed
and scattered over in your endpoint uri by wrapping them inside a bean of class org.apache.camel.component.huaweicloud.common.models.ServiceKeys
.
Add it to the registry and let Camel look it up by referring the object via endpoint query parameter serviceKeys
.
Check the following code snippets:
<bean id="myServiceKeyConfig" class="org.apache.camel.component.huaweicloud.common.models.ServiceKeys">
<property name="accessKey" value="your_access_key" />
<property name="secretKey" value="your_secret_key" />
</bean>
from("direct:triggerRoute")
.to("hwcloud-dms:listInstances?region=cn-north-4&serviceKeys=#myServiceKeyConfig")