# Managing the Derby Network Server

The Derby Network Server can be run in either of the following 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, see Using Java Management Extensions (JMX) technology.

You can manage the Network Server by using shell scripts, the command line, or the Network Server API.

- Overview of Derby Network Server management
  You can start the Derby Network Server by using the command line or by using the Derby Network Server API.
- Setting Network Server properties
  You can specify Network Server properties in the following ways.
- 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
Using Java Management Extensions (JMX) technology
Managing the Derby Network Server remotely by using the servlet interface
Derby Network Server advanced topics
Related reference
Derby Network Server sample programs