Derby provides batch and shell scripts for users in Windows and UNIX environments that can be used to start IJ. By calling the appropriate script you will start ij and be able to connect with a simple command. These scripts set the ij.protocol property, which simplifies the process of connecting to a database by eliminating the need to specify the protocol portion of the connection URL. The scripts are found in the %DERBY_HOME%/frameworks/ directory tree. You can also customize the ij scripts to suit your environment.
If you are starting ij from a command line, be sure that derbyrun.jar is in your classpath (for pre-10.2 distributions derbytools.jar and usually derby.jar were required in the classpath). If you are using Derby as a client/server environment, start the server before connecting to the Derby database. You can start ij by running the ij scripts for your environment in the %DERBY_HOME%/frameworks/embedded/bin/ directory or in the %DERBY_HOME%/frameworks/NetworkServer/bin/ directory.
java [<options>] org.apache.derby.tools.ij
[-p <propertyFile>] [<inputFile>]
The command
line items are: Start the JVM.
The options that the JVM uses. You can use the -D command to set ij properties (see Starting ij using properties) or system properties, such as Derby properties.
A file you can use to set ij properties (instead of the -D command). The property file should be in the format created by the java.tools.Properties.save methods, which is the same format as the derby.properties file.
A file from which to read commands. The ij tool exits at the end of the file or an exit command. Using an input file causes ij to print out the commands as it runs them. If you reroute standard input, ij does not print out the commands. If you do not supply an input file, ij reads from the standard input.
For detailed information about ij commands, see ij commands and errors reference.