To use the Network Server and network client driver, add the
following jar file to your server classpath/modulepath.
Adding this file to your classpath/modulepath has the effect of including all of the
Derby classes. These classes are in the following jar files, which you can also add
to your classpath/modulepath separately:
- derbyshared.jar
This jar file contains
code which is common to all Derby
configurations.
- derbynet.jar
This jar file contains
the Network Server code. It must be in your classpath/modulepath to start the Network
Server.
- derby.jar
This jar file contains the
Derby database engine code.
It must be in the classpath/modulepath in order for the Network Server to access
Derby databases.
derby.jar is included in the Class-Path
attribute of derbynet.jar's manifest file. If you have
derbynet.jar in the classpath/modulepath and derby.jar is
in the same directory as derbynet.jar, it is not necessary to
include derby.jar explicitly.
- derbyclient.jar
This jar file contains the
Derby Network Client JDBC
driver that is necessary for communication with the Network Server. It must be
in the classpath/modulepath of the application on the client side in order to access
Derby databases over a
network.
- derbytools.jar
This jar file
contains the standard Derby
tools, such as ij, sysinfo,
and dblook.
This jar file also contains the Derby DataSources.
- derbyoptionaltools.jar
This jar file
contains additional Derby
tools, such as the Lucene plug-in.
The derbyoptionaltools.jar file is not needed in
your classpath/modulepath to run the Network Server, but it is automatically included
by derbyrun.jar.
All of the jar files are in the
$DERBY_HOME/lib
directory.
Derby provides script
files for setting the classpath/modulepath to work with the Network Server. The scripts are
located in the
$DERBY_HOME/bin
directory.
- setNetworkClientCP.bat (Windows)
- setNetworkClientCP (UNIX)
- setNetworkServerCP.bat (Windows)
- setNetworkServerCP (UNIX)