1.0

Syntax
SQLJ.INSTALL_JAR(IN JAR_FILE_PATH VARCHAR(32672),
IN QUALIFIED_JAR_NAME VARCHAR(32672),
IN DEPLOY INTEGER)
The path and physical name of the JAR file to add. For example:
z:\todays_build\tours.jar
JAR_FILE_PATH
Use a file system path appropriate for the operating system (such as
z:\filename.jar or /opt/filename.jar). You cannot specify a HTTP
URL to use for loading the JAR file.
Note: The JAR file path must be available on the specific SQLFire data
store to which the client is connected. If the client connects directly to a
known SQLFire server, then only that server requires the JAR file to be
available at the specified path when the procedure executes. However, if
a client connects using a locator then they may be connected to any available
server in the distributed system. In this case, the JAR file path should be
available to all members of the SQLFire cluster (for example, from a
fileshare location such as z:\) to ensure that the procedure can execute.
After installing the JAR file to one SQLFire member, the JAR is available to all
other members in the distributed system, including members that join the
distributed system at a later time.
The SQLFire name of the JAR file, qualified by a valid schema name. Two
examples are:
MYSCHEMA.Sample1
-- a delimited identifier
MYSCHEMA."Sample2"
QUALIFIED_JAR_NAME
You can use the JAR name in subsequent calls to SQLJ.REPLACE_JAR or
SQLJ.REMOVE_JAR.
This integer argument is used to specify an alias for the JAR file. However,
SQLFire ignores this argument, so it is normally set to 0.
DEPLOY
Example
-- SQL statement
CALL SQLJ.INSTALL_JAR('tours.jar', 'APP.Sample1', 0)
-- SQL statement
-- using a quoted identifier for the
-- SQLFire jar name
CALL SQLJ.INSTALL_JAR('tours.jar', 'APP."Sample2"', 0)
SQLJ.REMOVE_JAR
The SQLJ.REMOVE_JAR system procedure removes an installed JAR file from SQLFire.
Syntax
SQLJ.REMOVE_JAR(IN QUALIFIED_JAR_NAME VARCHAR(32672),
IN UNDEPLOY INTEGER)
565
SQL Language Reference