Starting the Admin Tool

To start the Admin Tool, go to the bin directory of the registry and run the registry-admin script.

On a Windows system:

cd <JWSDP_HOME>\registry\bin
admin-tool [options]... 

On a UNIX system:

cd <JWSDP_HOME>/registry/bin [options]... 

The <JWSDP_HOME> location is the directory where you installed the Java WSDP.

To exit the Admin Tool, use the quit command.

Batch Mode

To run the Admin Tool in batch mode, specify the -command option on the command line when you start the Admin Tool.

For example, the following command executes the ls command:

java -jar ~/jwsdp-1.6/registry/lib/admin-tool.jar -command "ls 

The Admin Tool echoes your commands and the tool's responses to the screen and then exits after your commands have been executed.

Make sure that you properly escape any characters that are significant to your shell.

Interactive Mode

To run the Admin Tool in interactive mode, start the Admin Tool shell by specifying no options on the command line:

java -jar <JWSDP_HOME>/registry/lib/admin-tool.jar 

The Admin Tool displays the following prompt and waits for your input:


Admin Tool Command-line Options

The Admin Tool recognizes the command-line options listed in Synopsis and described in Options.


[-alias alias] [-command commands] [-debug] [-help]
-keypass keypass [-localdir localdir] [-locale locale]
[-registry url] [-root locator [-create]]
[-sqlselect SQL_statement] [-v | -verbose] 



The alias to use when accessing the user's certificate in the keystore. At this release, this option is not meaningful.


The Admin Tool command sequence to run instead of getting commands from the interactive shell. Use a semicolon (;) to separate multiple commands. It is not necessary to include a quit command in commands. If you need to use a semicolon that is not a command separator, precede it by a backslash:


The shell in which you run the Admin Tool may require you to escape the backslash with a second backslash:


If any command contains spaces, enclose the entire command sequence in single or double quotes so that the tool will treat the sequence as one command-line parameter instead of several. If your shell also interprets a semicolon as separating shell commands, you always have to put sequences of multiple Admin Tool commands in quotation marks.


If necessary, create the RegistryPackage specified by the -root option as well as any parent RegistryPackage objects as needed. This option is valid only if the user running the Admin Tool is authorized to create objects.


Outputs extra information that is useful when debugging.


Provides a list of these options.


The password to use when accessing a user's certificate in the keystore. At this release, this option is not meaningful.


The base directory in the local file system for commands that relate to files in the local file system.


The locale (for example, en or fr_CA) to use for selecting the resource bundle to use for error and status messages. The default is determined by the JavaTM Virtual Machine.


The URL of the ebXML registry to which to connect. The default is http://localhost:8080/soar/registry/soap.


The locator (for example, /registry/userData) of the RegistryPackage to use as the base for those commands that treat the repository as a tree of RegistryPackage objects that each contain other RegistryObject and RegistryPackage objects. The default is the RegistryPackage that is defined for all users' data: /registry/userData.


Execute SQL_statement to select registry objects. This should be a complete SQL statement that starts with select. The SQL statement must be enclosed in quotation marks, but it does not have to be terminated by a semicolon.

-v | -verbose

Specifies the verbose output of status messages.