OPC UA Browser
Since Camel 3.15
Only producer is supported
The Milo Client component provides access to OPC UA servers using the Eclipse Milo™ implementation.
Java 11+: This component requires Java 11+ 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>
URI format
The URI syntax of the endpoint is:
milo-browse:opc.tcp://[user:password@]host:port/path/to/service?node=RAW(nsu=urn:foo:bar;s=item-1)
Please refer to the Milo Client component for further details about the construction of the URI.
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 Browser component supports 24 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
A virtual client id to force the creation of a new connection instance. |
String |
||
All default options for client configurations. |
MiloClientConfiguration |
||
A suffix for endpoint URI when discovering. |
String |
||
An alternative discovery URI. |
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 |
|
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 |
|
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 |
||
Channel lifetime in milliseconds. |
Long |
||
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 |
||
The maximum number of pending publish requests. |
Long |
||
The maximum number of bytes a response message may have. |
Long |
||
Autowired Instance for managing client connections. |
MiloClientConnectionManager |
||
Override the server reported endpoint host with the host from the endpoint URI. |
false |
boolean |
|
The product URI. |
String |
||
The requested publishing interval in milliseconds. |
1_000.0 |
Double |
|
Request timeout in milliseconds. |
Long |
||
Session name. |
String |
||
Session timeout in milliseconds. |
Long |
Endpoint Options
The OPC UA Browser endpoint is configured using URI syntax:
milo-browse:endpointUri
with the following path and query parameters:
Query Parameters (29 parameters)
Name | Description | Default | Type |
---|---|---|---|
A virtual client id to force the creation of a new connection instance. |
String |
||
When browsing recursively into sub-types, what’s the maximum search depth for diving into the tree. Default value notice: Maximum depth for browsing recursively (only if recursive = true). |
3 |
int |
|
The direction to browse (forward, inverse, …). Default value notice: The direction to browse; see org.eclipse.milo.opcua.stack.core.types.enumerated.BrowseDirection. Enum values:
|
Forward |
BrowseDirection |
|
A suffix for endpoint URI when discovering. |
String |
||
An alternative discovery URI. |
String |
||
Filter out node ids to limit browsing. Default value notice: Regular filter expression matching node ids. |
None |
String |
|
Whether to include sub-types for browsing; only applicable for non-recursive browsing. |
true |
boolean |
|
The maximum number node ids requested per server call. Default value notice: Maximum number of node ids requested per browse call (applies to browsing sub-types only; only if recursive = true). |
10 |
int |
|
The node definition (see Node ID). Default value notice: Root folder as per OPC-UA spec. |
ns=0;id=84 |
String |
|
The mask indicating the node classes of interest in browsing. Default value notice: Comma-separated node class list; see org.eclipse.milo.opcua.stack.core.types.enumerated.NodeClass. |
Variable,Object,DataType |
String |
|
Whether to browse recursively into sub-types, ignores includeSubTypes setting as it’s implied to be set to true. Default value notice: Whether to recursively browse sub-types: truefalse. |
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 |
|
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 |
||
Channel lifetime in milliseconds. |
Long |
||
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 |
||
The maximum number of pending publish requests. |
Long |
||
The maximum number of bytes a response message may have. |
Long |
||
Override the server reported endpoint host with the host from the endpoint URI. |
false |
boolean |
|
The product URI. |
String |
||
The requested publishing interval in milliseconds. |
1_000.0 |
Double |
|
Request timeout in milliseconds. |
Long |
||
Session name. |
String |
||
Session timeout in milliseconds. |
Long |
Message Headers
The OPC UA Browser component supports 1 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
Constant: |
The node ids. |
List |
Client
The browse component shares the same base options like the Camel Milo Client component, e.g. concerning topics like discovery, security policies, the construction of node ids, etc.
Please refer to the documentation of the Camel Milo Client component for further details.
Browsing
The main use of this component is to be able to determine the nodes values to be retrieved or to be written by first browsing the node tree of the OPC-UA server, e.g. to avoid hard-coding a significant number of node ids within the configuration of Camel routes. The component is designed to work in conjunction with the Camel Milo Client component as illustrated in the following example:
from("direct:start")
// Browse sub tree
.setHeader("CamelMiloNodeIds", constant(Arrays.asList("ns=1;s=folder-id")))
.enrich("milo-browse:opc.tcp://localhost:4334", (oldExchange, newExchange) -> newExchange)
// Filter specific ids
.filter(...)
// Retrieve the values for the nodes of interest
.enrich("milo-client:opc.tcp://localhost:4334", (oldExchange, newExchange) -> newExchange)
Spring Boot Auto-Configuration
When using milo-browse 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 |