Managing the Derby Network Server remotely by using the servlet interface

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 a Web server, and derby.system.home must be known to the Web server.

A Web application archive (WAR) file, derby.war, for the Network Server is available in $/frameworks/NetworkServer/war. 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 cns, the URL of the server is:

http://<server>[:port]/derby/derbynet A servlet engine is not part of the Network Server.

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.