1.1

Table Of Contents
Note: After you install a JAR le, you cannot modify any of the individual classes or resources within
the JAR le. Instead, you must replace the entire JAR le to update a class.
Replacing a JAR File
Use the sqlf replace-jar command to replace an installed JAR le with a new JAR. Specify the identier of an
existing JAR installation when using the command, as in:
sqlf replace-jar -name=APP.toursjar -file=c:\tours2.jar
-client-bind-address=locator_address
-client-port=locator_port
When you replace a JAR le, SQLFire loads the new classes right away without your having to reboot.
Removing an Installed JAR File
Specify the JAR identier with the sqlf remove-jar command to remove an installed JAR le. For example, the
following command removes the class les associated with the APP.toursjar JAR installation:
sqlf remove-jar -name=APP.toursjar
-client-bind-address=locator_address
-client-port=locator_port
Code Your Applications
In your SQLFire applications, you can load the installed classes either by indirectly referencing them in the code
or by directly using java.lang.Class.forName.
You load resources the way you normally would, using the standard java.lang.Class.getResourceAsStream, a
mechanism that allows an application to access resources dened in the classpath without knowing where or
how they are stored.
You do not need to make any changes to the way code interacts with SQLFire and its JDBC driver. An application
can safely attempt to boot SQLFire, even though it is already running, without any errors. Applications connect
to SQLFire in the usual manner.
Note: The method getResource is not supported.
Alternate Methods for Managing JAR Files
SQLFire also provides system procedures that you can use to interactively install and manage JAR les from a
client connection. Keep in mind that the procedures have certain limitations compared to using sqlf commands
to manage JAR les.
This topic contains the following sections:
Restrictions for Managing JAR Files Using System Procedures on page 124
Installing a JAR File on page 124
Installing a JAR File Directly into SYS.JARS on page 124
Replacing a JAR File on page 125
Removing an Installed JAR File on page 125
See also JAR Installation Procedures on page 594 for more information about the procedures used to manage
installed JAR les.
123
Storing and Loading JAR Files in SQLFire