1.0

SQLFire does not prevent you from storing these standard JAR files, but the classes are never loaded from the
JAR file.
• Classes that are supplied with your Java environment (for example, sun.*)
SQLFire can load classes from any number of JAR files from any number of schemas.
Create JAR files intended for SQLFire class loading in the same way that you would create a JAR file for
including in a user's classpath. For example:
jar cf travelagent.jar travelagent/*.class
Different IDEs have tools to generate a list of contents for a JAR file based on your application. If your application
requires classes from other JAR files, you have the following options:
• Extract the required third-party classes from their JAR files, and include only those classes in your JAR file.
Use this option when you need only a small subset of the classes in the third-party JAR file.
• Store the entire third-party JAR file in the database.
Use this option when you need most or all of the classes in the third-party JAR file, because you can then
upgrade your application and third-party logic independently of one another.
• Deploy the third-party JAR file in the user's class path.
Use this option when the necessary classes are already installed on a user's computer.
Manage JAR Files in SQLFire
When you install a JAR file, you specify a unique SQLFire JAR name, which is a SQL92Identifier. SQLFire
installs the JAR file and automatically loads the JAR file classes into its class loader, and it becomes available
to all members of the distributed system (including members that join the system at a later time).
SQLFire provides sqlf commands to install, replace, and remove JAR files as described in these sections:
• Installing a JAR File on page 114
• Manage JAR Files in SQLFire on page 112
• Removing an Installed JAR File on page 115
Installing a JAR File
To install a JAR file to a SQLFire distributed, use the sqlf install-jar command. For example, the following
command installs the tours.jar file to the APP schema:
sqlf install-jar -name=APP.toursjar -file=c:\tours.jar
-client-bind-address=locator_address
-client-port=locator_port
If the SQLFire distributed system uses multicast for discovery instead of a locator, specify the multicast properties
instead, as in:
sqlf install-jar -name=toursjar -file=c:\tours.jar
-mcast-address=multicast_address
-mcast-port=multicast_port
The -name that you provide for the JAR must be a unique identifier. You must include a schema name to qualify
the identifier. You can use the identifier with later calls to sqlf replace-jar or sqlf remove-jar.
The -file option specifies the location of the JAR file to install using either a local path or a URL.
After installing the JAR to the distributed system, SQLFire automatically loads the JAR file classes into its class
loader; you do not need to explicitly load classes after installing the JAR. The JAR and its classes are available
to all members of the SQLFire distributed system, including those that later join the cluster.
vFabric SQLFire User's Guide112
Developing Applications with SQLFire