Installing required jar files and adding them to the classpath

To use the Network Server and network client driver, add the following jar file to your server classpath:

derbyrun.jar

Adding this file to your classpath has the effect of including all of the Derby classes in your classpath. These classes are in the following jar files, which you can also add to your classpath separately:

derbynet.jar
This jar file contains the Network Server code. It must be in your classpath to start the Network Server.
derby.jar
This jar file contains the Derby database engine code. It must be in the classpath 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 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 of the application on the client side in order to access Derby databases over a network.

All of the jar files are in the $DERBY_HOME/lib directory.

Derby provides script files for setting the classpath 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)

See Managing the Derby Network Server and Getting Started with Java DB for more information on setting the classpath.