Java DB

Apache Derby

Derby Server and Administration Guide

Derby Getting Started
Derby Reference Manual
Derby Developer's Guide
Derby Performance Tuning
Derby Server and Admin Guide
Derby Tools and Utilities
Derby Server and Admin Guide

-Purpose of this guide

-Part one: Derby Server Guide

-Derby in a multi-user environment

-Derby in a server framework

-Connectivity configurations
-Multiple-client features available in Derby

-The Derby Network Server
-Embedded servers
-How to start an embedded server from an application
-Embedded server example

-About this guide and the Network Server documentation

-Using the Network Server with preexisting Derby applications

-The Network Server and JVMs
-Installing required jar files and adding them to the classpath
-Starting the Network Server

-Starting the Network Server from a Java application
-Starting the Network Server on IPv6/Ipv4 dual stack Windows machines

-Shutting down the Network Server

-Shutting down by using the command line
-Shutting down by using the API

-Obtaining system information

-Obtaining system information by using the command line
-Obtaining system information by using the API

-Accessing the Network Server by using the network client driver

-Network client security
-Network client tracing
-Network client driver examples

-Accessing the Network Server by using a DataSource object

-DataSource access examples

-XA and the Network Server

-Using XA with the network client driver

-Using the Derby tools with the Network Server

-Using the Derby ij tool with the Network Server
-Using the Derby dblook tool with the Network Server

-Differences between running Derby in embedded mode and using the Network Server

-Differences between the embedded client and the network client driver
-Updatable Result Sets
-Error message differences
-User authentication differences

-Differences in JDBC 3. 0 methods
-Differences using the Connection. setReadOnly method

-Setting port numbers

-Managing the Derby Network Server

-Using the NetworkServerControl API

-Setting Network Server properties

-derby.drda.host property
-derby.drda.keepAlive property
-derby. drda. logConnections property
-derby.drda.maxThreads property
-derby.drda.minThreads property
-derby.drda.portNumber property
-derby. drda. securityMechanism property
-derby.drda.sslMode property
-derby. drda. startNetworkServer property
-derby. drda. streamOutBufferSize property
-derby.drda.timeSlice property
-derby.drda.traceAll property
-derby. drda. traceDirectory property

-Verifying Startup

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

-Start-up page
-Running page
-Trace session page
-Trace directory page
-Set Network Server parameters

-Derby Network Server advanced topics

-Network Server security
-Running the Network Server under the security manager

-Basic Network Server security policy
-Customizing the Network Server's security policy
-Running the Network Server without a security policy

-Running the Network Server with User Authentication
-Network encryption and authentication with SSL/TLS

-Key and certificate handling
-Starting the server with SSL/TLS
-Running the client with SSL/TLS
-Other server commands

-Configuring the Network Server to handle connections
-Controlling logging by using the log file
-Controlling tracing by using the trace facility

-Turning on the trace facility
-Turning off the trace facility

-Derby Network Server sample programs

-The NsSample sample program

-Running the NsSample sample program

-Network Server sample programs for embedded and client connections

-Overview of the SimpleNetworkServerSample program
-Running the SimpleNetworkServerSample program
-Connecting a client to the Network Server with the SimpleNetworkClientSample program
-Running the SimpleNetworkClientSample program

-Part two: Derby Administration Guide

-Checking database consistency

-The SYSCS_CHECK_TABLE function
-Sample SYSCS_CHECK_TABLE error messages
-Sample SYSCS_CHECK_TABLE queries

-Backing up and restoring databases

-Backing up a database

-Offline backups
-Online backups

-When the log is in a non-default location
-Backing up encrypted databases

-Restoring a database from a backup copy
-Creating a database from a backup copy
-Roll-forward recovery

-Replicating databases

-Starting and running replication
-Stopping replication
-Forcing a failover
-Replication and security
-Replication failure handling

-Logging on a separate device

-Using the logDevice= logDirectoryPath attribute
-Example of creating a log in a non-default location
-Example of moving a log manually
-Issues for logging in a non-default location

-Obtaining locking information

-Monitoring deadlocks

-Reclaiming unused space

		Search documentation:

Controlling logging by using the log file The Network Server uses the `derby.log` file to log problems that it encounters. It also logs connections when the property `derby.drda.logConnections` is set to `true`. The `derby.log` file is created when the Derby server is started. The Network Server then records the time and version. If a log file exists, it is overwritten, unless the property `derby.infolog.append` is set to `true`. When the Network Server is logging connections, it also logs the Connection Number; this log message is written both to the `derby.log` file and to the Network Server console. To turn on connection logging, you can use the servlet interface or you can issue the following command: java org.apache.derby.drda.NetworkServerControl logconnections on [-h <hostname>] [-p <portnumber>] To turn connection logging off you can use the servlet interface or you can issue the following command: java org.apache.derby.drda.NetworkServerControl logconnections off [-h <hostname>][-p <portnumber>] See the Derby Developer's Guide for more information about the `derby.log` file. Parent topic: Derby Network Server advanced topics Related concepts Network Server security Network encryption and authentication with SSL/TLS Related tasks Running the Network Server under the security manager Running the Network Server with User Authentication Configuring the Network Server to handle connections Controlling tracing by using the trace facility

	javadb@jdbcurl.com