Install & Configure an Agent

Self-Hosted

Installing an agent is done using the DataZen Manager application. The DataZen Manager must be started using administrive privileges on the machine where the agent is to be installed.

For detailed instructions on how to install the self-hosted agent, please refer to the installation instructions provided in this document.

For information on how to secure access to your agent using HTTP/S connections, see the security section.

Container

You can download a preview of the Enzo DataZen Docker Container. Once you have downloaded the container, you can build your own image and open the necessary ports to connect to your endpoints. Configuring a Docker Container can be an advanced operation and may require help from DevOps engineers.

The latest release of the Docker image can be found on the Docker Hub website. Once running, you can use the DataZen Manager to upgrade it to the latest version.

The container version of the DataZen agent uses environment variables. Although these environment variables are provided for a container deployment, they may also be used when running EnzoDS.exe as a console application.

ENZODS_CONTAINER	Should be set to 1. As an alternative.
ENZODS_ANONYMOUS	When set to 1, this setting enables anonymous authentication.
ENZODS_URI	Overrides the HTTP listening URL for this agent.
ENZODS_DEBUG	When set to 1, outputs additional connection debugging information to the console

Configuration File

The configuration file EnzoDS.exe.config is located in the same directory as the agent. Although this file contains important DLL redirect directives, it contains a single configuration option: the listening URL of the agent under its appSettings section.

<appSettings>
        <add key="listenerUrl" value="http://*:9559" />
</appSettings>

The value property can contain multiple entries separated by a comma. This allows you to configure the agent to listen on multiple ports. The following example instructs the agent to listen on the localhost only on port 9559 and on 443 for both remote and local connections:

http://localhost:9559,https://SERVERNAME:443

Depending on the version of your agent, the 443 port number may be required when specifying an HTTPS listener.

If the port is currently in use or if the NT user starting the agent does not have enough privileges, the agent will throw and display errors similar to these:

ERROR - FAILED TO START: Failed to listen on prefix 'http://localhost:9559/' because it conflicts with an existing registration on the machine.

ERROR - FAILED TO START: Access is denied

For Access Denied errors, either run the agent in privilege mode, or use netsh to grant users access to the port (ex: netsh http add urlacl url=http://+:9559/ user=Everyone)