# Setting Network Server properties

You can specify Network Server properties in the following ways.

- On the command line
- In the `.bat` or unix shell script files (load the properties by executing `java -D`)
- In the `derby.properties` file

Properties specified on the command line or in the `.bat` or `.ksh` files take precedence over the properties in the `derby.properties` file. Arguments included in commands that are issued on the command line take precedence over property values.

- derby.drda.host property
  Causes the Network Server to listen on a specific network interface.
- derby.drda.keepAlive property
  Indicates whether SO_KEEPALIVE is enabled on sockets.
- derby.drda.logConnections property
  Indicates whether to log connections.
- derby.drda.maxThreads property
  Sets the maximum number of connection threads that the Network Server will allocate.
- derby.drda.minThreads property
  Sets the minimum number of connection threads that the Network Server will allocate.
- derby.drda.portNumber property
  Indicates the port number to use.
- derby.drda.securityMechanism property
  Restricts the client connections based on the security mechanism.
- derby.drda.sslMode property
  Indicates whether the client connection is encrypted or not, and whether certificate-based peer authentication is enabled.
- derby.drda.startNetworkServer property
  Indicates whether the Network Server will start automatically when you start Derby.
- derby.drda.streamOutBufferSize property
  Configures the size of the buffer for streaming blob/clob data from server to client.
- derby.drda.timeSlice property
  Sets the number of milliseconds that each connection will use before yielding to another connection.
- derby.drda.traceAll property
  Turns tracing on for all sessions.
- derby.drda.traceDirectory property
  Indicates the location of tracing files.

Parent topic: Managing the Derby Network Server
Related concepts
Overview of Derby Network Server management
Related tasks
Verifying startup