By default, the DataHub program is configured to act as an OPC UA server. To change this or any default settings, you can follow these steps:
Right click on the DataHub system-tray icon and choose .
In the Properties window, select OPC UA. 

Ensure that the box is checked to enable the OPC UA server, or uncheck the box to disable it.
These basic UA server settings can be modified if necessary.
![]() | |
Any changes made here will restart the OPC UA server when you click the button. |
Protocol To disable any of the available protocols, uncheck its box.
Port The port number can be changed by double-clicking it, or by using the button.
Computer Name/IP You can change the host name or IP address, which will then be integrated into the server URL visible to a connecting client. The default is the host name.
Endpoint Name You can enter an endpoint name for this OPC UA server. This
will be integrated into the server URL visible to a connecting
client. The default is
CogentDataHub/DataAccess.
![]() | |
Some UA clients cannot connect to a UA server unless the server name is left blank. For these cases, the DataHub instance can be configured with a blank server name as follows:
The DataHub UA server will restart with a blank user name, allowing a UA client to connect to it using a simple Endpoint URL, for example: opc.tcp://192.168.1.1:52310/ |
![]() | |
Some UA clients may require some or all of the following information about the DataHub OPC UA server:
|
To make it easy to get started, the OPC UA server is configured with minimal security settings. If you want to modify or enhance security, click the button to open the UA Server Properties window, shown below. Otherwise, you can skip this step.

The General tab of the UA Server Properties dialog lets you modify the default Security Policies and User Token Policies for each Server URL.
Security Policies Disabling None for
opc.tcp and http will
require connecting clients to support encryption for these
connections. HTTPS is already encrypted, so
None need not be disabled for
https.
User Token Policies Disabling Anonymous will require the connecting client to provide a username/password or certificate to log in.
Putting all this together, below are some suggested settings you can use to secure your OPC UA server.
opc.tcp://...| Security Policies | User Token Policies | ||
|---|---|---|---|
| Off | None | Off | Anonymous |
| On | Basic128Rsa15 | On | User Name |
| On | Basic256 | On | Certificate |
http://...| Security Policies | User Token Policies | ||
|---|---|---|---|
| Off | None | Off | Anonymous |
| On | Basic128Rsa15 | On | User Name |
| On | Basic256 | On | Certificate |
https://...| Security Policies | User Token Policies | ||
|---|---|---|---|
| On | None | Off | Anonymous |
| On | User Name | ||
| On | Certificate | ||
![]() | |
Any changes made here will restart the OPC UA server when you click the button. |
In the Client Certificate Receiving section, ensure that the Automatically accept untrusted certificates box is not checked.

Otherwise, all clients will be accepted as trusted.
The Continue to accept client certificates when they expire option allows expired certificates to be used, and also keeps the UA server and client connected if their system clocks ever get out of synch. For more information, please see the Advanced feature of the OPC UA Server section.
Click the button to accept the revised configuration (or Cancel to reject it) and close the UA Server Properties window.
You can use the button to make a copy of this server's endpoint, if necessary.
Click the button in the Properties window to accept the configuration.
These are the most common changes you might want to make to the default configuration for the OPC UA server. For other configuration options and more details about the OPC UA server, please refer to the OPC UA Server section of the Properties Window chapter.