Testing Your Setup
Given that you're adding a good few JAR files to the CLASSPATH, it's a good idea to test the setup before trying to run the examples. As noted in my earlier Derby article, the Derby distribution includes a handy tool for verifying that your CLASSPATH is correctly configured. This command is:
On my system, this produces the following:
--------- Derby Information -------- JRE - JDBC: J2SE 5.0 - JDBC 3.0 [C:\java\db-derby-10.1.2.1-bin\lib\db2jcc_license_c.jar] 2.4 - (17) [C:\java\db-derby-10.1.2.1-bin\lib\db2jcc.jar] 2.4 - (17) [C:\java\db-derby-10.1.2.1-bin\lib\derbyclient.jar] 10.1.2.1 - (330608) [C:\derby\db-derby-10.1.2.1-bin\lib\derby.jar] 10.1.2.1 - (330608) [C:\derby\db-derby-10.1.2.1-bin\lib\derbytools.jar] 10.1.2.1 - (330608) [C:\derby\db-derby-10.1.2.1-bin\lib\derbynet.jar] 10.1.2.1 - (330608)
Notice the Derby-specific JAR files at the end of the listing. If you get similar output, you should be ready to run the server.