The 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
database engine
- As an embedded server,
in which case it is embedded within another Java application,
and both the Network Server framework and the
database engine are loaded by the Java application
You can use Java Management Extensions (JMX) technology to monitor and manage
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 for
information about starting and shutting down the Network Server using the
servlet interface.