OPC UA Server
Since Camel 2.19
Both producer and consumer are supported
The Milo Server component provides an OPC UA server using the Eclipse Milo™ implementation.
Java 9+: This component requires Java 9+ at runtime.
Maven users will need to add the following dependency to their pom.xml for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-milo</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>Messages sent to the endpoint from Camel will be available from the OPC UA server to OPC UA Clients. Value write requests from OPC UA Client will trigger messages which are sent into Apache Camel.
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 OPC UA Server component supports 20 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
The application name. | String | ||
The application URI. | String | ||
Set the addresses of the local addresses the server should bind to. | String | ||
Server build info. | BuildInfo | ||
The URI of the namespace, defaults to urn:org:apache:camel. | urn:org:apache:camel | String | |
The path to be appended to the end of the endpoint url. (doesn’t need to start with '/'). | String | ||
The TCP port the server binds to. | int | ||
The product URI. | String | ||
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 | |
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 | |
Server certificate. | X509Certificate | ||
Server certificate manager. | CertificateManager | ||
Validator for client certificates. | ServerCertificateValidator | ||
Validator for client certificates using default file based approach. | String | ||
Enable anonymous authentication, disabled by default. | false | boolean | |
Security policies. | Set | ||
Security policies by URI or name. Multiple policies can be separated by comma. | String | ||
Set user password combinations in the form of user1:pwd1,user2:pwd2 Usernames and passwords will be URL decoded. | String | ||
Set the UserTokenPolicy used when. Enum values:
| SecurityPolicy |
Endpoint Options
The OPC UA Server endpoint is configured using URI syntax:
milo-server:itemId
with the following path and query parameters:
Query Parameters (4 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
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 | |
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | ExceptionHandler | ||
Sets the exchange pattern when the consumer creates an exchange. Enum values:
| ExchangePattern | ||
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 |
Spring Boot Auto-Configuration
When using milo-server with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-milo-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>The component supports 72 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
A set of allowed security policy URIs. Default is to accept all and use the highest. | String | ||
The application name. | Apache Camel adapter for Eclipse Milo | String | |
The application URI. | String | ||
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 | |
Channel lifetime in milliseconds. | Long | ||
A virtual client id to force the creation of a new connection instance. | String | ||
All default options for client configurations. The option is a org.apache.camel.component.milo.client.MiloClientConfiguration type. | MiloClientConfiguration | ||
A suffix for endpoint URI when discovering. | String | ||
An alternative discovery URI. | String | ||
Whether to enable auto configuration of the milo-browse component. This is enabled by default. | Boolean | ||
The name of the key in the keystore file. | String | ||
The key password. | String | ||
The keystore password. | String | ||
The key store type. | String | ||
The URL where the key should be loaded from. | 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 | |
The maximum number of pending publish requests. | Long | ||
The maximum number of bytes a response message may have. | Long | ||
Instance for managing client connections. The option is a org.apache.camel.component.milo.client.MiloClientConnectionManager type. | MiloClientConnectionManager | ||
Override the server reported endpoint host with the host from the endpoint URI. | false | Boolean | |
The product URI. | String | ||
Request timeout in milliseconds. | Long | ||
The requested publishing interval in milliseconds. | Double | ||
Session name. | String | ||
Session timeout in milliseconds. | Long | ||
A set of allowed security policy URIs. Default is to accept all and use the highest. | String | ||
The application name. | Apache Camel adapter for Eclipse Milo | String | |
The application URI. | String | ||
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 | |
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 | |
Channel lifetime in milliseconds. | Long | ||
A virtual client id to force the creation of a new connection instance. | String | ||
All default options for client configurations. The option is a org.apache.camel.component.milo.client.MiloClientConfiguration type. | MiloClientConfiguration | ||
A suffix for endpoint URI when discovering. | String | ||
An alternative discovery URI. | String | ||
Whether to enable auto configuration of the milo-client component. This is enabled by default. | Boolean | ||
The name of the key in the keystore file. | String | ||
The key password. | String | ||
The keystore password. | String | ||
The key store type. | String | ||
The URL where the key should be loaded from. | 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 | |
The maximum number of pending publish requests. | Long | ||
The maximum number of bytes a response message may have. | Long | ||
Instance for managing client connections. The option is a org.apache.camel.component.milo.client.MiloClientConnectionManager type. | MiloClientConnectionManager | ||
Override the server reported endpoint host with the host from the endpoint URI. | false | Boolean | |
The product URI. | String | ||
Request timeout in milliseconds. | Long | ||
The requested publishing interval in milliseconds. | Double | ||
Session name. | String | ||
Session timeout in milliseconds. | Long | ||
The application name. | String | ||
The application URI. | String | ||
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 | |
Set the addresses of the local addresses the server should bind to. | String | ||
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 | |
Server build info. The option is a org.eclipse.milo.opcua.stack.core.types.structured.BuildInfo type. | BuildInfo | ||
Server certificate. The option is a java.security.cert.X509Certificate type. | X509Certificate | ||
Server certificate manager. The option is a org.eclipse.milo.opcua.stack.core.security.CertificateManager type. | CertificateManager | ||
Validator for client certificates. The option is a org.eclipse.milo.opcua.stack.server.security.ServerCertificateValidator type. | ServerCertificateValidator | ||
Validator for client certificates using default file based approach. | String | ||
Enable anonymous authentication, disabled by default. | false | Boolean | |
Whether to enable auto configuration of the milo-server component. This is enabled by default. | Boolean | ||
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 | |
The URI of the namespace, defaults to urn:org:apache:camel. | urn:org:apache:camel | String | |
The path to be appended to the end of the endpoint url. (doesn’t need to start with '/'). | String | ||
The TCP port the server binds to. | Integer | ||
The product URI. | String | ||
Security policies. | Set | ||
Security policies by URI or name. Multiple policies can be separated by comma. | String | ||
Set user password combinations in the form of user1:pwd1,user2:pwd2 Usernames and passwords will be URL decoded. | String | ||
Set the UserTokenPolicy used when. | SecurityPolicy |