Java DB

Apache Derby

Derby Server and Administration Guide

Derby Getting Started
Derby Reference Manual
Derby Developer's Guide
Derby Performance Tuning
Derby Server and Admin Guide
Derby Tools and Utilities
Derby Server and Admin Guide
-Part one: Derby Server Guide
-Derby in a multi-user environment
-Using the Network Server with preexisting Derby applications
-The Network Server and JVMs
-Installing required jar files and adding them to the classpath
-Starting the Network Server
-Shutting down the Network Server
-Obtaining system information
-Accessing the Network Server by using the network client driver
-Accessing the Network Server by using a DataSource object
-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
-Managing the Derby Network Server
-Managing the Derby Network Server remotely by using the servlet interface
-Derby Network Server advanced topics
-Derby Network Server sample programs
-Part two: Derby Administration Guide
-Checking database consistency
-Backing up and restoring databases
-Replicating databases
-Logging on a separate device
-Obtaining locking information
-Reclaiming unused space

 

Shutting down by using the API

You can use the NetworkServerControl API to shut down the Network Server from within a Java application. The name of the method that you use to shutdown the Network Server is shutdown().

For example, the following command shuts down the Network Server running on the current machine using the default port number (1527):

NetworkServerControl server = new NetworkServerControl();
server.shutdown();

To shut down a server running with user authentication, you need to use a NetworkServerControl instance created with user credentials:

NetworkServerControl server = new NetworkServerControl(username, password);
server.shutdown();
 

javadb@jdbcurl.com