Creating Servers

Note

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

Solution Manager administrators have several ways to create servers:

  1. Click a cluster node cluster_node and select new-server-text-btn on the emerging menu.

    Create new server from cluster

    Create new server from the cluster

  2. Click a group node and select new-server-text-btn on the emerging menu. Thus, you can create a server of the same type as the group.

    Create new server from a group node

    Create new server from a group node

  3. Click a server node server_node and select copy-server-text-btn on the emerging menu. Thus, you can create a server initialized with the same information as the selected server.

    Copy an existent server

    Copy an existent server

  4. When you create a cluster, Solution Manager Administration Tool will suggest you to create a new server. Accept the suggestion.

    Suggestion for creating a server

    Suggestion for creating a server

Whatever path you follow, the following dialog will open to create a new server:

Dialog to create a server

Dialog to create a server

As part of the server definition, this dialog considers the following fields:

  • Name: Descriptive name for the server. You cannot assign duplicated names to the servers of the Solution Manager.

  • Description: Extensive description about the server. This field is optional.

  • Host: IP or name of the host where the Denodo server is installed. Take into account that, if you use the License Manager, this field must match the exact host address of the installation machine, in order to properly resolve its license.

  • Port: Port where the Denodo server is listening for incoming requests.

  • Type: Type of server in the Denodo Platform, which can be one of the following:

    • Virtual DataPort.
    • Scheduler. Notice that Kerberos is not enabled in the Denodo Scheduler servers.
    • ITPilot Browser Pool or ITPilot Verification. This kind of servers are only intended to provide a license dynamically through the License Manager. Revisions and promotions are not supported for these servers.
    • Data Catalog. It is not necessary to define the Data Catalog servers in Solution Manager to get the license. You can add Data Catalog servers in a cluster to provide optional synchronization with the Virtual DataPort servers during the deployment process.
  • Default database: Default database for authentication. This parameter is only required in the Virtual DataPort servers.

  • User: User name used to connect to the server.

    Important

    In servers of Data Catalog type the user must have at least the data_catalog_admin role in order to be able to synchronize the catalog metadata during the deployment process.

  • Password: Password used for authentication.

  • Use Kerberos with user/password above: Check this option if you want to use Kerberos authentication to connect to the server. A Kerberos ticket will be generated from the values of the fields User and Password. This option only applies to the Virtual DataPort servers when Kerberos is configured in the Solution Manager Server.

  • Authenticate with current user credentials for creating revisions: Check this option if you want to create the revisions with the credentials of the user that is logged in the Solution Manager Administration Tool. The values from the fields User and Password will be used otherwise.

Note

You cannot assign the same combination of host and port to more than one server of the Solution Manager.