LDBDC(1)

NAME
ldbdc - lightweight database dumper client

SYNOPSIS
ldbdc --server host:port --database name [--sql query] [--insert file] [--identity subject] [--output file] [--verbose] [--help]

DESCRIPTION

ldbdc inserts a LIGO lightweight XML file into the specified database and/or executes an SQL query returning the results as a LIGO lightweight XML to the standard output or a file.

OPTIONS

-s,--server host:port
    connect to ldbd server at host on port. If port is not specified, then the default of 49999 is used

-j,--identity subject
    Use subject as the subject of the server's identity certificate. If no identity is specified, the client assumes that it should expect an ldbdserver service certificate issued by the DOE for the hostname specifed by host (see AUTHENTICATION below)

-d,--database name
    interact with the database called name on host

-i,--insert file
    insert the data in the LIGO lightweight XML file names file into the database

-q,--query query
    Execute the SQL query query at the specified database and return the results of the query as a LIGO lightweight XML file

-o,--output file
    Write the returned LIGO lightweight XML file to file insted of the standard output.

-v,--verbose
    print lots of debugging information during execution

-h,--help
    print a brief usage message

DIAGNOSTICS

An exit status of 0 means that the no errors ocourred, 1 means that there was an error communicating with the server and 2 means that the server returned an error to the client.

EXAMPLES

ldbdc --server metaserver.phys.uwm.edu --database uwm_dev --insert test.xml Inserts the LIGO lightweight XML file test.xml into the uwm_dev database at metaserver.phys.uwm.edu

ldbdc --server metaserver.phys.uwm.edu:60000 --database uwm_dev --query "SELECT * FROM SNGL_INSPIRAL" --output inspiralevents.xml Retrieves all the entries from the SNGL_INSPIRAL table in the uwm_dev database at metaserver.phys.uwm.edu on port 60000 and writes the results to the file inspiralevents.xml

AUTHENTICATION

The ldbd package uses Globus GSI authentication using X.509 cerficates issued by a the DOEgrid certificate authority. Before running the client to connect to a server, the user must obtain an X.509 certificate and communcate the subject of the certificate to the database administrator so the the server can authenticate the client user. The user must also run the grid-proxy-init program to give the client access to the users key.

The client program also expects the server to authenticate itself. To do this the client needs to know the subject of the certificate that the server is presenting. The is done by either specifying the subject directly with the --identity option or by letting the client assume that the server will present an ldbdserver service certificate issued by DOEgrids for the host that the server runs on. For example if the --host option is myhost.com, then the client will expect the server to present a certificate with the subject: /O=doesciencegrid.org/OU=Services/CN=ldbdserver/myhost.com

COPYRIGHT

Copyright (C) 2003 Duncan Brown.

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

SEE ALSO

ldbdd(8)

AUTHOR

Duncan Brown <duncan@gravity.phys.uwm.edu>

BUGS

If the query produces a large amount of data, it can take the server a long time to parse it into LIGO lightweight XML. This is due to the code in the server being a prototype algorithm which will be optimised soon.