# Managing the Derby Network Server

The Derby Network Server can be run in either of these configurations:

- As a stand-alone server, in which case it is an independent Java process embedding the Derby database engine
- As an embedded server, in which case it is embedded within another Java application, and both the Network Server framework and the Derby database engine are loaded by the Java application

You can use Java Management Extensions (JMX) technology to monitor and manage Derby and the Network Server. For information on how to do this, visit the wiki page http://wiki.apache.org/db-derby/DerbyJMX and refer to the API documentation for the packages `org.apache.derby.mbeans` and `org.apache.derby.mbeans.drda`. For information on JMX technology, see http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/.

You can manage the Network Server by using shell scripts, the command line, or the Network Server API. The Network Server can also be managed remotely from a web server by using a servlet interface. See Managing the Derby Network Server remotely by using the servlet interface for information about starting and shutting down the Network Server using the servlet interface.

- Overview
- Setting Network Server properties
- Verifying Startup
  To verify that the Derby Network Server is currently running, use the ping command.

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