7. Other Tools and Features

The Handle System Server distribution also includes a few other small utilities for maintaining a handle server.

DBTool

DBTool is a graphical utility for operating directly on a handle server's database.

DBTool can be invoked using the command:

java -cp handle.jar net.handle.apps.db_tool.DBTool <server dir>

WARNING: RUN ONLY ON A HANDLE SERVER THAT IS NOT RUNNING.

DBList/DBRemove

If you would like to operate directly on a handle server's database, but without a GUI, there are two other utilities: DBList and DBRemove. DBList will list all the handles in a handle server database. It can be invoked using the command:

java -cp handle.jar net.handle.apps.db_tool.DBList <server dir>

WARNING: RUN ONLY ON A HANDLE SERVER THAT IS NOT RUNNING.

DBRemove will remove a specified handle from the database. It can be run using the command:

java -cp handle.jar net.handle.apps.db_tool.DBRemove <server dir> <handle>

WARNING: RUN ONLY ON A HANDLE SERVER THAT IS NOT RUNNING.

Resolver

The Handle System Server distribution includes a simple resolver GUI that may be preferable over the resolution facilities in the Handle Administration Tool. It can be run using the command:

java -cp handle.jar net.handle.apps.gui.resolver.Main

There is also a command line resolver that can be run using the command:

java -cp handle.jar net.handle.apps.simple.HDLTrace <handle>

Test Tool

This tool performs client and local/global server diagnostic tests.

This tool is run from the command line and requires certain arguments. The following commands should be run in the same directory as the `handle.jar' file.

• Client Test - with no arguments:

  Sends a request to each global server and tests each interface. Also pings each server within the site and reports average round trip time and percent packet loss.

  java -cp handle.jar net.handle.apps.test.Test client

• Client Test - with naming authority argument:

  Sends a request to server corresponding to specified naming authority and tests each interface. Also pings each server and reports average round trip time and percent packet loss

  java -cp handle.jar net.handle.apps.test.Test client <NA>

  Example:

  java -cp handle.jar net.handle.apps.test.Test client 0.NA

• Server Test:

  Tests local server by sending a request to the server and testing each interface.

  java -cp handle.jar net.handle.apps.test.Test server <config.dct>

  Example:

  java -cp handle.jar net.handle.apps.test.Test server \hs\svr_1

• Write Test:

  Tests handle operations: add, add value, modify value, delete value, delete. If `admpriv.bin' is not located in the same directory as `config.dct', user will be prompted for location.

  java -cp handle.jar net.handle.apps.test.Test write <config.dct>

  Example:

  java -cp handle.jar net.handle.apps.test.Test write \hs\svr_1

• Test All:

  Performs server test, write test, and global sites client test.

  java -cp handle.jar net.handle.apps.test.Test all <config.dct>

  Example:

  java -cp handle.jar net.handle.apps.test.Test all \hs\svr_1

Key Util

The Key Util program allows decrypting and encrypting of private key files. It can be invoked using the command:

java -cp handle.jar net.handle.apps.tools.KeyUtil <privkey.bin>

GetRootInfo

GetRootInfo retrieves a current copy of the global service information for the Handle System. This is the information found in the `root_info' file.

Usage:

java -cp handle.jar net.handle.apps.tools.GetRootInfo <root-server> <port> <out-file>

GetSiteInfo

GetSiteInfo retrieves the service information for a handle server. This is the information found in the `siteinfo.bin' file.

Usage:

java -cp handle.jar net.handle.apps.tools.GetSiteInfo <server> <port> <out-file>

DoCheckpoint

DoCheckpoint is a command line tool to send a checkpoint/backup command to all of the handle servers in a specified site. Execution is done with the following command:

java -cp handle.jar net.handle.apps.tools.DoCheckpoint [siteinfo] [admin-hdl] [admin-index] [keytype] [key]

Keytype can be either PRIVATE or SECRET. If PRIVATE, then key is the name of a file where the private key is stored. If SECRET, then key is the secret key itself.