# Installing required jar files and adding them to the classpath

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

- derbynet.jar

  This jar file contains the Network Server code. It is only necessary for the process that starts the Network Server in addition to the standard Derby .jar files.

- derby.jar

  This file must be in your classpath to use any of the Derby Network Server functions.

- derbyclient.jar

  This jar file must be in your class path to use the Network Client driver. The jar file is necessary for client-side communication with the Network Server using the Derby Network Client driver. It needs to be in the client-side classpath to use the Network Client driver to access Derby.

Derby provides script files for setting the classpath to work with the Network Server. The scripts are located in the $DERBY_HOME\frameworks\NetworkServer\bin directory.

- setNetworkClientCP.bat (Windows)
- setNetworkClientCP.ksh (UNIX)
- setNetworkServerCP.bat (Windows)
- setNetworkServerCP.ksh (UNIX)

See Managing the Derby Network Server and Getting Started with Derby for more information on setting the classpath.
Parent topic: Using the Network Server with preexisting Derby applications
Related concepts
The Network Server and JVMs
Accessing the Network Server by using the network client driver
Accessing the Network Server by using a DataSource
XA and the Network Server
Using the Derby tools with the Network Server
Differences between running Derby in embedded mode and using the Network Server
Related tasks
Starting the Network Server
Shutting down the Network Server
Obtaining system information
Setting port numbers