USER MANUALS

Change the Host Name in the Virtual DataPort Server

When the Virtual DataPort server runs on Linux or Unix, by default it only listens to connections on localhost (the loopback interface). To allow connections from remote clients, you have to configure the host name or IP address remote clients will use to reach the host where the Virtual DataPort server runs.

If the Virtual DataPort server runs on Windows, you do not need to do this.

You can change this graphically or from the command line. Both ways are equivalent.

The host name or IP address provided has to be reachable by the clients that connect to the Virtual DataPort server.

Changing the Host Name of the Denodo Servers Graphically

To graphically change the host name of the Virtual DataPort Server follow these steps:

  1. Open the Denodo Control Center.

  2. Click Configure.

  3. Click JVM Options.

  4. Click the tab RMI host.

  5. In the field Virtual DataPort Server/ITPilot Wrapper Server, enter the IP address or name of this host.

    You do not need to change the values of the fields below. The web container listens to connections on all the network interfaces of the host. The other Denodo components are only accessed by other components running on the same host (the Scheduler server is only accessed by the Scheduler administration tool, which runs on the local web container).

  6. Click Ok.

  7. Restart the Virtual DataPort server to pick up the changes.

Changing the Host Name of the Denodo Servers from the Command Line

Follow these steps to change the host name of the Virtual DataPort Server from the command line:

  1. Edit the file <DENODO_HOME>/conf/vdp/VDBConfiguration.properties

  2. Set the value of the property com.denodo.vdb.vdbinterface.server.VDBManagerImpl.registryURL to the IP address or name of this host. You should have one line like this:

com.denodo.vdb.vdbinterface.server.VDBManagerImpl.registryURL=dv-server-1.denodo.com

  1. Execute the script <DENODO_HOME>/bin/regenerateFiles

    This propagates this change to the startup scripts of Virtual DataPort.

  2. Restart the Virtual DataPort server to pick up the changes.

Add feedback