db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1662) Document derbyrun.jar
Date Thu, 04 Jan 2007 05:55:27 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462142

Andrew McIntyre commented on DERBY-1662:

> As for "server" being an alias for org.apache.derby.drda.NetworkServerControl -- I don't
think this is documented anywhere yet, is it?

I'm not sure, but considering the description of this issue, probably not. There is actually
another way to run NetworkServerControl as well: 'java -jar derbynet.jar {NetworkServerControl
command}' (so you'll find that 'java -jar derbynet.jar' and 'java -jar derbyrun.jar server'
do the same thing, and it's also accessible by running 'java org.apache.derby.drda.NetworkServerControl'
with derbyrun.jar or derbynet.jar in your classpath, of course. :-)  )

I think it might be useful to have the Getting Started guide introduce derbyrun.jar, and discuss
what each of the possible invocations will do. There are four possible invocations, run 'java
-jar derbyrun.jar' with no arguments to see the help for derbyrun.jar.

Looking at the admin guide, I'm thinking that besides needing an update, the content in 'starting
the network server,' 'altering the startNetworkServer script' and 'starting the network server
without a script' can be combined into the starting the network server' page, which then describes
the various ways to invoke the network server from the command line. The content of the 'altering
the startNetworkServer script' needs to be updated (really, removed and replaced with) using
the DERBY_OPTS environment variable to set derby.system.home and to just pass arguments in.

export DERBY_OPTS=-Dderby.system.home=/opt/derby
startNetworkServer -p 1368

will start the network server on port 1368, with a system home directory of /opt/derby. The
options when using the java invocations can be set similarly, e.g.

java -Dderby.system.home=/opt/derby -jar derbyrun.jar server start


java -Dderby.system.home=/opt/derby -jar derbynet.jar start -p 1368

or even:

export DERBY_OPTS=-Dderby.system.home=/opt/derby
java $DERBY_OPTS org.apache.derby.drda.NetworkServerControl start -h -p 1638

Although maybe instead of going into all the possible command line invocations, the best thing
to do for the moment in the admin guide may be just a mention that another alternative to
the scripts exists: derbyrun.jar

> Document derbyrun.jar
> ---------------------
>                 Key: DERBY-1662
>                 URL: https://issues.apache.org/jira/browse/DERBY-1662
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: David Van Couvering
>         Assigned To: Kim Haase
>            Priority: Minor
> The documentation for ij in the Tools Guide only describes how to start ij the old way.
 It should also describe how to start it using derbyrun.jar. 
> I wonder if the same is true for the other tools, although I haven't investigated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message