# Managing the Derby Network Server remotely by using the servlet interface

You can use the servlet interface to manage the Network Server remotely. To use the servlet interface, the servlet must be registered with an Application Server, and derby.system.home must be known to the Application Server.

A Web application archive (WAR) file, derby.war, for the Derby Network Server is available in $DERBY_HOME/lib. This file registers the Network Server's servlet at the relative path /derbynet. See the documentation for your Application Server for instructions on how to install it.

For example, if derby.war is installed in WebSphere Application Server with a context root of derby, the URL of the server is:

    http://<server>[:port]/derby/derbynet

Notes:

- A servlet engine is not part of the Network Server.
- When the Network Server is started by the servlet interface, shutting down the Application Server also shuts the Network Server down, since both run in the same JVM.

The servlet takes the following optional configuration parameters:

portNumber
  Specifies the port number to be used by the Network Server.
startNetworkServerOnInit
  Specifies that the Network Server is to be started when the servlet is initialized.
tracingDirectory
  Specifies the location for trace files. If the tracing directory is not specified, the traces are placed in derby.system.home.

This section describes the servlet pages.

- Start-up page
  Use the start-up page to start the server.
- Running page
- Trace session page
- Trace directory page
- Set Network Server parameters

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
Derby Network Server advanced topics
Related reference
Derby Network Server sample programs