Apache Derby网络服务器与管理指南v10.14.2.0

需积分: 2 197 浏览量更新于2024-07-16 收藏 322KB PDF 举报

"Apache Derby数据库管理手册，版本10.14.2.0，涵盖了Derby在多用户环境下的使用，特别是Derby网络服务器的配置、管理和应用。" Apache Derby是一款开源的关系型数据库管理系统，它轻量级、嵌入式，并且完全符合Java数据库连接（JDBC）和SQL标准。本手册主要关注的是Derby在网络服务器模式下的操作，这使得它可以在多用户环境中高效地运行。 1. **Derby in a Multi-User Environment** 当需要在多个用户间共享数据时，Derby可以通过其Network Server功能提供服务。这种方式下，Derby不再运行在单一的应用进程中，而是作为一个独立的服务，允许多个应用程序和用户同时访问数据库。 2. **Derby in a Server Framework** 在服务器框架中，Derby的Network Server允许远程连接，这样用户可以不在同一台机器上也能访问数据库。这对于分布式系统或者需要远程数据存取的情况非常有用。 3. **Using the Network Server with Preexisting Derby Applications** 对于已经存在的Derby应用程序，无需进行大的改动即可与Network Server配合使用。只需确保正确的jar文件被安装并添加到类路径中，然后配置应用程序连接到Network Server。 4. **The Network Server and Java Virtual Machines (JVMs)** Network Server通常在一个单独的JVM中运行，而客户端应用程序则在它们自己的JVM中运行。这种分离提供了更好的资源管理和安全性。 5. **Installing Required Jar Files and Adding Them to the Classpath** 运行Network Server需要特定的Derby库文件，如`derbynet.jar`和`derbyclient.jar`。这些必须添加到系统的类路径中，以便正确识别和加载服务器及其客户端组件。 6. **Starting and Shutting Down the Network Server** 启动Network Server通常通过命令行完成，可以使用`java -jar derbyrun.jar server start`命令。关闭服务器则使用`stop`命令。了解如何启动和停止服务器是管理员的基本技能。 7. **Managing the Derby Network Server** 管理包括设置端口号、配置安全性、监控性能和日志记录等。例如，通过修改配置文件可以改变服务器监听的端口，以避免与其他服务冲突。 8. **Accessing the Network Server** 客户端可以使用网络客户驱动程序或DataSource对象来连接到Network Server。对于分布式事务处理，Derby还支持XA接口。 9. **Differences between Running Derby in Embedded Mode and Using the Network Server** 嵌入式模式下，Derby直接运行在应用程序的JVM中，而Network Server模式提供了更高级的并发控制和远程访问能力，但可能需要更多的系统资源。 10. **Setting Port Numbers** 为了防止端口冲突，可以通过配置参数指定服务器使用的端口。这包括数据库通信的默认端口1527以及可能的JMX管理端口。此手册详细解释了如何设置和管理Derby Network Server，对于那些希望在多用户环境中部署和维护Derby数据库的IT专业人员来说，是一份非常宝贵的参考资料。

Derby Server and Administration Guide

There are several ways to manage the Derby Network Server, including:

• Through the command line

• By using .bat and .ksh scripts

• With your own Java program (written using the Network Server API)

• By setting Network Server properties

By default a security manager will be installed with a basic security policy when a

Network Server is started. This policy file is called server.policy and is part

of derbynet.jar. For information about policy files, granting permissions, and

property expansion, see "Default Policy Implementation and Policy File Syntax"

at http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html

and "Policy File Creation and Management" at

http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyGuide.html.

Using the Network Server with preexisting Derby applications explains how to change

existing Java applications that currently run against Derby in embedded mode to run

against the Derby Network Server.

Managing the Derby Network Server explains how to manage the Network Server by

using the command line, including starting and stopping it.

Derby Network Server advanced topics contains advanced topics for Derby Network

Server users.

Because of the differences in JDBC drivers that are used, you might encounter

differences in functionality when running Derby in the Network Server framework as

opposed to running it embedded in a user application. Refer to Using the Network

Server with preexisting Derby applications for a complete list of the differences between

embedded and Network Server configurations.

Embedded servers

Because Derby is written in the Java programming language, you have great flexibility in

how you choose to configure your deployment.

For example, you can run Derby, the JDBC server framework, and another application in

the same JVM as a single process.

How to start an embedded server from an application

In one thread, the embedding application starts the local JDBC driver for its own access.

Connection conn = DriverManager.getConnection(

"jdbc:derby:sample");

In another thread, the same application starts the server framework to allow remote

access. Starting the server framework from within the application allows both the server

and the application to run in the same JVM.

Embedded server example

You can start the Network Server in another thread automatically when Derby starts by

setting the derby.drda.startNetworkServer property, or you can start it by using a

program.

See Setting Network Server properties for details on this property.

The following example shows how to start the Network Server by using a program:

import org.apache.derby.drda.NetworkServerControl;

import java.net.InetAddress;

NetworkServerControl server = new NetworkServerControl

(InetAddress.getByName("localhost"),1527);

server.start(null);

Derby Server and Administration Guide

The program that starts the Network Server can access the database by using either

the embedded driver or the Network Client driver. The server framework's attempt to

boot the local JDBC driver is ignored because it has already been booted within the

application's JVM. The server framework simply accesses the instance of Derby that is

already booted. There is no conflict between the application and the server framework.

The remote client can then connect through the Derby client driver:

String nsURL="jdbc:derby://localhost:1527/sample";

java.util.Properties props = new java.util.Properties();

props.setProperty("user","usr");

props.setProperty("password","pwd");

Connection conn = DriverManager.getConnection(nsURL, props);

/*interact with Derby*/

Statement s = conn.createStatement();

ResultSet rs = s.executeQuery(

"SELECT * FROM HotelBookings");

About this guide and the Network Server documentation

This guide assumes that you are familiar with Derby features and tuning.

Before reading this guide, you should first learn about basic Derby functionality by

reading the Derby Developer's Guide. Also, because multi-user environments typically

have performance and tuning issues, you should read Tuning Derby.

Using the Network Server with preexisting Derby applications

You must modify Java applications that currently run against Derby in embedded mode

so that they work with the Derby Network Server.

The topics in this section discuss these changes.

The Network Server and Java Virtual Machines (JVMs)

The Derby Network Server is compatible with Java Platform, Standard Edition (Java SE)

6 and above.

Installing required jar files and adding them to the classpath

To use the Network Server and network client driver, add the following jar file to your

server classpath.

• derbyrun.jar

Adding this file to your classpath has the effect of including all of the Derby classes in

your classpath. These classes are in the following jar files, which you can also add to

your classpath separately:

• derbynet.jar

This jar file contains the Network Server code. It must be in your classpath to start

the Network Server.

• derby.jar

This jar file contains the Derby database engine code. It must be in the classpath

in order for the Network Server to access Derby databases. derby.jar is

included in the Class-Path attribute of derbynet.jar's manifest file. If you

Derby Server and Administration Guide

have derbynet.jar in the classpath and derby.jar is in the same directory as

derbynet.jar, it is not necessary to include derby.jar explicitly.

• derbyclient.jar

This jar file contains the Derby Network Client JDBC driver that is necessary

for communication with the Network Server. It must be in the classpath of the

application on the client side in order to access Derby databases over a network.

• derbytools.jar

This jar file contains the standard Derby tools, such as ij, sysinfo, and dblook.

The derbytools.jar file is not needed in your classpath to run the Network

Server, but it is automatically included by derbyrun.jar.

• derbyoptionaltools.jar

This jar file contains additional Derby tools, such as the Lucene plug-in. The

derbyoptionaltools.jar file is not needed in your classpath to run the

Network Server, but it is automatically included by derbyrun.jar.

All of the jar files are in the $DERBY_HOME/lib directory.

Derby provides script files for setting the classpath to work with the Network Server. The

scripts are located in the $DERBY_HOME/bin directory.

• setNetworkClientCP.bat (Windows)

• setNetworkClientCP (UNIX)

• setNetworkServerCP.bat (Windows)

• setNetworkServerCP (UNIX)

See Managing the Derby Network Server and Getting Started with Derby for more

information on setting the classpath.

Starting the Network Server

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

> Important: 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 Derby Security Guide.

You are also urged to install a Java security manager with a customized security

policy. For details on how to do this, see "Configuring Java security," also in the

Derby Security Guide. By default a security manager will be installed with a default

security policy when a Network Server is started. This default policy file is called

server.policy and is part of derbynet.jar. There is also a template.policy

file in derbynet.jar which can be used as starting point for a customized server

policy file. For more information about policy files, granting permissions, and

property expansion, see "Default Policy Implementation and Policy File Syntax"

at http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html

and "Policy File Creation and Management" at

http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyGuide.html.

If you are running Java SE 7 or later, and if you start the Derby Network Server from

the command line as described here, access to databases and to other Derby 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 Derby Security Guide.

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

Derby Server and Administration Guide

• 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. The following table shows the sequence of commands.

Table 1. Commands to run the startNetworkServer command

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 Derby, set the DERBY_HOME

environment variable, then use a java command to invoke the derbyrun.jar or

derbynet.jar file, as shown in the following table.

Table 2. Commands to invoke the Derby jar files

Operating

System Command

Windows

set DERBY_HOME=C:\derby

java -jar %DERBY_HOME%\lib\derbyrun.jar server

start

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

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 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, as

shown in the following table.

Table 3. Commands to invoke the NetworkServerControl class

Operating

System Command

Windows

%DERBY_HOME%\bin\setNetworkServerCP

java org.apache.derby.drda.NetworkServerControl

start

Derby Server and Administration Guide

Operating

System Command

UNIX (Korn Shell)

$DERBY_HOME/bin/setNetworkServerCP

java org.apache.derby.drda.NetworkServerControl

start

The default system directory is the directory in which Derby was started. (See the Derby

Developer's Guide 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.

Remember: Before using the -h option, you should run under the Java

security manager with a customized security policy and 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.

Starting the Network Server from a Java application

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.

There are two ways to start the Network Server from a Java application.

• You can include the following line in the derby.properties file:

derby.drda.startNetworkServer=true

This starts the server on the default port, 1527, listening on localhost (all

interfaces).

To specify a different port or a specific interface in the derby.properties file,

include the following lines, respectively:

derby.drda.portNumber=1110

derby.drda.host=myhost

You can also specify the startNetworkServer and portNumber properties by

using a Java command:

java -Dderby.drda.startNetworkServer=true \

-Dderby.drda.portNumber=1110 \

-Dderby.drda.host=myhost yourApp

• You can use the NetworkServerControl API to start the Network Server from a

separate thread within a Java application:

NetworkServerControl server = new NetworkServerControl();

server.start (null);

Starting the Network Server on IPv6/IPv4 dual stack Windows machines

Add the following JVM properties to the command when you start the server on an

IPv6/IPv4 dual stack Windows machine.

剩余91页未读，继续阅读

luren85

粉丝: 10
资源: 22

Apache Derby网络服务器与管理指南v10.14.2.0

db-derby-10.14.2.0-lib.zip

SQLPrompt-10.14.0.4064.exe 支持SSMS 19.1

derbydev-v10.14.2.0.pdf

derbytools-v10.14.2.0.pdf

Apache Derby Developer's Guide v10.14.2.0

rh-java-common-jdepend-2.9.1-10.14.el7.noarch.rpm

rh-maven33-javacc-5.0-10.14.el7.noarch.rpm

rh-maven33-javacc-demo-5.0-10.14.el7.noarch.rpm

rh-maven33-javacc-manual-5.0-10.14.el7.noarch.rpm

rh-maven33-javacc-javadoc-5.0-10.14.el7.noarch.rpm

最新资源