Creating Servers


Only global administrators and Solution Manager administrators can create servers. More information is available in the Authorization section.


It is not possible to create servers in automated cloud mode environments.

To create a server, click on a cluster (cluster_node), and on the popup that will show up, click new-server-text-btn.

You can also create a server based on the configuration of an existing server, click on that server and on the popup that will show up, click copy-server-text-btn.

The Tool will display the panel to create a server.

Create server panel

Create server panel

Enter the value for the following fields:

  • Name. Name of the server. This name has to be unique. You cannot assign the same name to two servers, even if they are in different environments or clusters.

  • Description (optional). Description of the server.

  • Host. Name of the host where the Denodo server runs. Enter the full host name of the machine, not an alias. That is because what you enter here has to match what that machine considers it is its host name. See more about this in the section How Licenses Work. Alternatively, you can enter the IP address the host. However, entering a host name is better because the host name of a host is usually more permanent than its IP.

  • Port. Port where the server component listens to incoming requests.

  • Type. Type of server component. Its value can be:

    • Virtual DataPort

    • Scheduler

    • ITPilot Browser Pool or ITPilot Verification. This kind of servers are only intended to provide a license dynamically through the License Manager. These services do not support revisions or promotions.

    • Data Catalog. The Data Catalog servers in a cluster can be synchronized with the Virtual DataPort servers during the deployment process.


      Data Catalog servers must be registered in the Solution Manager in order to start.

  • User and Password. Credentials to connect to the server. Required fields if Authenticate with current user credentials for creating revisions is not selected.

  • Use Kerberos with user/password above. Select this to use Kerberos authentication to connect to the server. A Kerberos ticket will be obtained using the values of the fields User and Password. This option is only available for Virtual DataPort servers and if Kerberos is enabled in the Solution Manager.

    The Solution Manager will not be able to deploy revisions to Scheduler when Scheduler has Kerberos authentication enabled.

  • Authenticate with current user credentials for creating revisions. Select this to create the revisions using the credentials of the user that is logged in the Solution Manager, instead of the credentials of this dialog.


    This option requires that the server supports the same authentication method used by the current user. Otherwise it cannot be connected by pass-through.

    For example, if the user is authenticated by Kerberos, the target server must support Kerberos authentication.

  • Server enabled. If you clear this, the server will be ignored when deploying a revision. The disabled servers are displayed in gray in the environments tree.

  • License Scenario. If the license scenario of the environment of this server is PRODUCTION and the license allows servers of type HOT BACKUP or COLD BACKUP, you can assign a custom backup scenario to this server. To do this, click Default to change to Custom mode and then, select HOT BACKUP or COLD BACKUP.

    Otherwise, this option is not displayed.

    The license scenario assigned to the server is a custom license scenario
  • Infrastructure settings. This section allows to specify information about the platform where the server is running. This option is only available for Virtual DataPort servers. This information is useful for FinOps monitoring.

    • Provider. On premise or cloud provider where the server is running.

    • Region. The region associated to the provider.

    Infrastructure settings


You cannot register two servers with the same host name and port.

Add feedback