# Using the Network Server with preexisting Derby applications

You must modify Java applications that currently run against Derby in embedded mode so that they work with the Derby Network Server. The topics in this section discuss these changes.

- The Network Server and JVMs
- Installing required jar files and adding them to the classpath
- Starting the Network Server
  To start the Network Server, you can invoke a script, a jar file, or a class.
- Shutting down the Network Server
  If user authentication is disabled, a Derby database will shut down normally when the Network Server is shut down. If user authentication is enabled, you must explicitly shut down the database before shutting down the Network Server by specifying a valid Derby user name and password.
- Obtaining system information
- Accessing the Network Server by using the network client driver
  When connecting to the Network Server, your application needs to load a driver and connection URL that is specific to the Network Server. In addition, you must specify a user name and password if you are using authentication.
- 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
- Setting port numbers

Parent topic: Part one: Derby Server Guide
Related concepts
Derby in a multi-user environment
Managing the Derby Network Server
Managing the Derby Network Server remotely by using the servlet interface
Derby Network Server advanced topics
Related reference
Derby Network Server sample programs