Starting the Network Server

To start the Network Server, you can invoke a script, a jar file, or
a class.

Important: Note that you should always properly shut down the Network Server
after use, because failure to do so might result in unpredictable side-effects,
such as blocked ports on the server.

You are strongly urged to enable user authentication when you run a
Network Server.
For details on how to configure user authentication, please consult
the "Working with user authentication" section in the Developer's Guide.
You are also urged to install a Java security manager with a
customized security policy. For details on how to do this, see
Customizing the Network Server's security policy.

You can start the Network Server in any of the following ways:

If you are relatively new to the Java programming language, follow the
instructions in "Setting up your environment" in
Getting Started with Derby to set the
DERBY_HOME
and JAVA_HOME environment variables and to add
DERBY_HOME/bin
to your path. Then use the startNetworkServer.bat
script to start the Network Server on Windows machines and the startNetworkServer
script to start the Network Server on UNIX systems. These scripts are located
in $DERBY_HOME/bin,
where $DERBY_HOME is the
directory where you installed Derby.

You
can run NetworkServerControl commands only from the host that started the
Network Server.

To see the command syntax, invoke derbyrun.jar server or
derbynet.jar with no arguments.

If you are familiar with both the Java programming language and Derby,
you have already set
DERBY_HOME.
Set your classpath to include the
Derby
jar files. Then use a java command to invoke the
NetworkServerControl class directly.