Verifying Your Installation

Testing your Local Installation

First, verify that the installation automatically appended your CLASSPATH with the interclient.jar file.

Second, on Windows NT/95, select the InterServer Configuration Utility icon in the InterClient program group and start the InterServer service or application (usually, but not necessarily, on your InterBase server). On Unix the interserver service is started automatically by inetd if your /etc/services and /etc/inetd.conf are configured properly.

Finally, on Windows NT/95, select the Communication Diagnostics icon from the InterClient program group. If Java is installed on your local machine and interclient.jar is in your CLASSPATH, then a GUI will appear for making a test connection using the locally installed driver. Alternatively, and on Unix, you may invoke the Communiation Diagnostics Utility from the command line using

    java interbase.interclient.utils.CommDiag

Testing an Applet Configuration

CommDiag may also be run as an applet on clients in which neither the JDK nor InterClient is installed. Using a Java enabled browser, browse CommDiag.html or CommDiagForNetscape.html off a web server which has InterClient deployed. If you run InterClient applets such as CommDiag through a browser, then you may need to remove the interclient.jar from your local CLASSPATH to avoid a security exception.

You may also run CommDiag through the appletviewer:

    unset CLASSPATH
    appletviewer CommDiag.html

You may need to unset your CLASSPATH temporarily in your command session when viewing a local applet, otherwise you could receive a java.lang.IllegalAccessError. CommDiag.html contains an applet tag which references the interclient.jar archive.

Untrusted applets are not allowed to open network connections to arbitrary hosts, except for the host that provided the .class files. This is either the host where the html page came from, or the host specified in the codebase parameter in the applet tag, with codebase taking precendence. Therefore, untrusted applets, will only operate if InterServer is installed on the same web server host that serves the interclient.jar file. If you choose to deploy InterServer on another host then you must digitally sign your applet together with the interclient.jar file so that the entire applet is trusted.

Be sure to name the originating host exactly as it was specified when the applet was loaded into the browser. That is, if you load an HTML page using the URL

    http://foo.state.edu/~me/CommDiag.html

then your applet will be able to connect to its host only by using the name foo.state.edu in the jdbc URL

    jdbc:interbase://foo.state.edu//databases/employee.gdb

Using the IP address for foo.state.edu won't work, and using a "shorthand" form of the host name, like foo.state instead of foo.state.edu, won't work.