Starting the Network Server To start the Network Server, you can invoke a script, a jar file, or a class. Starting the Network Serverfrom scripts Network Serverstarting Always shut down the Network Server properly 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 and user authorization when you run a Network Server. For details on how to configure user authentication and authorization, see "Configuring user authentication" and "Configuring user authorization" in the .

If you start the Network Server from the command line as described here, access to databases and to other files is by default restricted to the operating system account that started the Network Server. It is possible to override this default behavior. For more information, see "Restricting file permissions" in the .

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 to set the and JAVA_HOME environment variables and to add /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 $/bin, where $ is the directory where you installed .

    You can run NetworkServerControl commands only from the host that started the Network Server. The following table shows the sequence of commands.

    Commands to run the <codeph>startNetworkServer</codeph> commandThis table lists the commands to run the startNetworkServer command on UNIX and Windows systems. Operating System Command Windows set DERBY_HOME=C:\derby set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_24 set PATH=%DERBY_HOME%\bin;%PATH% startNetworkServer UNIX (Korn Shell) export DERBY_HOME=/opt/derby export JAVA_HOME=/usr/j2se export PATH="$DERBY_HOME/bin:$PATH" startNetworkServer

  • If you are a regular Java user but are new to , set the environment variable, then use a java command to invoke the derbyrun.jar or derbynet.jar file, as shown in the following table.

    Commands to invoke the <ph conref="../conrefs.dita#prod/productshortname"></ph> jar filesThis table lists the commands to invoke the jar files on UNIX and Windows systems. Operating System Command Windows set DERBY_HOME=C:\derby java -jar %DERBY_HOME%\lib\derbyrun.jar server start or java -jar %DERBY_HOME%\lib\derbynet.jar start UNIX (Korn Shell) export DERBY_HOME=/opt/derby java -jar $DERBY_HOME/lib/derbyrun.jar server start or java -jar $DERBY_HOME/lib/derbynet.jar start

    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 , you have already set . Set your classpath/modulepath to include the jar files. Then use a java command to invoke the NetworkServerControl class directly, as shown in the following tables.

    Commands to invoke the <codeph>NetworkServerControl</codeph> class via the classpathThis table lists the commands to invoke the NetworkServerControl class via the classpath on UNIX and Windows systems. Operating System Command Windows %DERBY_HOME%\bin\setNetworkServerCP java org.apache.derby.drda.NetworkServerControl start UNIX (Korn Shell) $DERBY_HOME/bin/setNetworkServerCP java org.apache.derby.drda.NetworkServerControl start
    Commands to invoke the <codeph>NetworkServerControl</codeph> class via the modulepathThis table lists the commands to invoke the NetworkServerControl class via the modulepath on UNIX and Windows systems. Operating System Command Windows %DERBY_HOME%\bin\setNetworkServerCP java -p %MODULEPATH% ^ -m org.apache.derby.server/org.apache.derby.drda.NetworkServerControl start UNIX (Korn Shell) $DERBY_HOME/bin/setNetworkServerCP java -p $MODULEPATH \ -m org.apache.derby.server/org.apache.derby.drda.NetworkServerControl start

The default system directory is the directory in which was started. (See the for more information about the default system directory.)

You can specify a different host or port number when you start the Network Server by specifying an option to the command.

  • Specify a port number other than the default (1527) by using the -p portnumber option, as shown in the following example:

    java org.apache.derby.drda.NetworkServerControl start -p 1368

  • Specify a specific interface (host name or IP address) to listen on other than the default (localhost) by using the -h option, as shown in the following example:

    $DERBY_HOME/bin/startNetworkServer -h myhost -p 1368

    where myhost is the host name or IP address.

    Before using the -h option, you should enable user authentication.

By default, the Network Server will listen to requests only on the loopback address, which means that it will only accept connections from the local host.