Table of Contents

DMA configuration related to client applications

Configuring client communication settings

Users can define whether DataMiner Cube has to automatically detect the settings to be used when establishing a connection toward a certain DataMiner Agent.

If it is set to automatically detect the connection settings, Cube will connect to a DataMiner Agent according to the communication settings defined on the DataMiner Agent to which it is connecting. As a consequence, no settings will have to be changed when a user opens multiple instances of DataMiner Cube, all pointing to different DataMiner Agents.

.NET Remoting with or without eventing

By default, clients connecting to a DataMiner Agent use .NET Remoting with eventing.

  • .NET Remoting with eventing: When a client uses .NET Remoting with eventing, the DataMiner Agent will send server-initiated notifications to the client. When a client application such as DataMiner Cube connects to a DataMiner Agent, it will open a random port on the client to which the DMA will send its notifications.

  • .NET Remoting without eventing: When a client uses .NET Remoting without eventing, the DataMiner Agent will not send server-initiated notifications to the client. Instead, the client application will continuously poll the DataMiner Agent for notifications.


When a fallback from polling to eventing occurs, an information event is generated that contains the IP address and port that the events are sent to. Clients can use this information to detect why they cannot receive events via the callback method. When a client connects, the log files and diagnostic info also contain the external client IP address as seen from the DataMiner Agent.

Manual configuration of client communication settings

To customize how Cube connects to a DMA for a specific computer:

  1. In the Cube header bar, click the user icon, and select Settings.

  2. Go to the computer tab of the Settings window.

  3. On the Connection page, next to Connection type, select one of the following options:

    • Auto: DataMiner will automatically select the connection settings.
    • Remoting: DataMiner will communicate using .NET Remoting.

      • This option is used by default.

      • The default port used for Remoting is port 8004.

      • By default, eventing is used, but the client will automatically fall back to polling if the callback port cannot be reached (e.g. if a firewall blocks the requests).

    • Web Services: Legacy option available prior to DataMiner 10.0.0 [CU6]/10.0.11. As WSE is deprecated, this option is no longer available in recent DataMiner versions. Connecting via web services is not possible if WSE is not installed on the DMA.

  1. If necessary, adjust the settings for the selected connection type:

    • Destination port: Select this option to specify a custom destination port number. If you specify “-1”, the port will be detected automatically.

    • Polling interval: The frequency at which the client application should poll the DMA, in milliseconds. If you want to use remoting and there are firewalls in your network or NAT is used, make sure this option is selected, to ensure that polling is used instead of eventing. For Web Services, this option is enabled by default.

    • Use data compression (Remoting only): Determines whether data are compressed or not. By default, this option is selected, in order to reduce network traffic.

    • Custom binding IP address (Remoting only): Only needed in case the server cannot automatically resolve the IP address that it needs to send callback events to the client, which can be the case when a VPN connection is used. The option only applies when eventing has been configured.

  • You can also configure this in the DataMiner Cube logon screen, before you actually log on. See Overriding the default connection type.
  • The procedure above only applies to the one computer where it is done. If you want to change the default client communication settings for a DMA, you can do so in the file ConnectionSettings.txt. See ConnectionSettings.txt.

Managing client versions

From DataMiner 10.2.0 [CU3]/10.2.6 onwards, Cube can automatically update to a more recent version than the DataMiner version installed on the server. This way, users can use the latest Cube features as soon as these are released without having to wait for a server upgrade. However, in the Cube system settings, you can configure limitations on which client version should be used:

  1. In DataMiner Cube, go to System Center > System settings > Manage client versions.

  2. Select which client versions should be used:

    • Allow automatic updates: This will allow automatic updates to higher versions of Cube, depending on the configuration in the Cube start window.


      When a new DMA is added to a cluster, that DMA will by default use this setting. If you use a different setting, keep in mind that you will still need to adjust this for this DMA.

    • Force the matching release version: This will force users to always use the Cube version that was shipped with the current DataMiner upgrade package.

    • Force a specific version: This will force users to always use a particular Cube version. When you select this option, a dialog will be displayed where you will need to select a and versions.txt file. You can obtain these files from the folder /Webpages/DataMinerCubeStandAlone/ in an upgrade package or on another DataMiner Agent (e.g. a staging platform).

      • If you are using a hotfix package with a Cube fix, use the option Force a specific version. Otherwise, users connecting to the DMA may use a more recent Cube version, obtained through, that does not yet contain the fix.
      • If the machines where the Cube clients are deployed do not have any internet connectivity, and as an Administrator you want them to update to a higher DataMiner Cube version than is deployed on the server, there are two options. You can use the MSI installer, or you can extract the and versions.txt files from the\Webpages\DataMinerCubeStandalone folder in the DataMiner upgrade package containing the Cube version you want, and enforce the use of this version.