In order to connect to Data Virtuality Server it is important to know which ports are being used for network communication. This is especially true if you have a secure environment and all network traffic has to be firewall enabled. Problems can arise if you either try to connect to a wrong port or if the port is not accessible through the firewall. The server is shipped with some default ports which you can find at the very bottom of %pathToDVserver%/standalone/configuration/dvserver-standalone.xml on Linux or %pathToDVserver%\standalone\configuration\dvserver-standalone.xml on Windows. This is an example of the file which might look like the one you are using right now:
As the snippet suggests, there are several ports for various usages. The main ones are for JDBC and ODBC connections. For example, the Data Virtuality Studio uses JDBC or JDBC over SSL connections whereas Tableau requires ODBC connections. Information about how to configure secure ODBC connections can be found further in this section. You should also make sure that there are no services or programs running on the machine which hosts the Data Virtuality Server which may conflict in socket bindings. If, for example, you already have a process running and this process uses port 9999, you might not be able to connect to the server via this port. Even worse, sockets that are already in use may prevent the server from starting.
If you have any conflicts, change either the affected ports of Data Virtuality Server or the ones of the other process. Alternatively, you can use the property port-offset in order to increment all used ports by a specific value. If you set the offset from 0 to 10000 your server will now use ports 41000 (JDBC), 41001 (JDBC over SSL), 45432 (ODBC) and so forth. This is a simple way to prevent conflicts but you should carefully adjust firewall rules and consider some documentation about the changes.
Configure Proxy Settings
It is possible that you deployed the Data Virtuality Server within an environment that uses an HTTP proxy server and the Data Virtuality Server needs to be configured to use this proxy. This is, as well as the port management, done through the dvserver-standalone.xml. You can specify the IP address and the port of the proxy that Data Virtuality Server shall communicate with as well as a list of hosts which are directly contacted (without any proxy interference). Find the </extensions> end tag and place the configuration right after it:
Note that the value for http.nonProxyHosts can contain a list with multiple hosts (separated by '|') that are communicated with directly. For example: value="localhost|clr.mycomp.org|*.mycomp.local", where '*' denotes the wildcard. There are also properties named https.proxyHost and https.proxyPort for configuring secure proxy connections.
Enable ODBC over SSL connections
To enable a secure ODBC connection, you need a certificate which you import into a Java keystore. Add some lines in dvserver-standalone.xml to point to this store and append a socket binding for the ODBC over SSL connection. As with the default ports, don't forget to enable firewall rules if necessary and do not specify ports that are already in use by some other process. If you are not in possession of a certificate, you can create one with the tool keytool that is shipped with most Java SDKs. The tool is found in the Java installation subfolder %JavaDir%/bin on Linux or %JavaDir%\bin on Windows. The following code creates a new certificate and stores it in a keystore which you specify.
Replace the placeholder %pathToStore% with the location where you want to place the keystore. You will be prompted to enter a password for future access of the keystore. Provide one and note it down. Now you have to add two entries in dvserver-standalone.xml:
(a note: security domain "dv-security" was called "teiid-security" in versions prior to 2.4 ) and