1.1

Examples
This command connects to a SQLFire network server running on localhost:1527, and removes the JAR installation
name APP.toursjar :
sqlf remove-jar -name=APP.toursjar
This command connects to a SQLFire network server running on myserver:1234 to remove the JAR file
installation:
sqlf remove-jar -name=APP.toursjar
-client-bind-address=myserver -client-port=1234
This command connects as a peer client to a SQLFire system running on multicast port 1234, and removes the
JAR file installation:
sqlf remove-jar -name=APP.toursjar
-mcast-port=1234 -extra-conn-props=host-data=false
sqlf replace-jar
Replaces an installed JAR file with the contents of a new JAR file. The classes in the new JAR file are
automatically loaded into the SQLFire class loader and they replace any classes that were previously installed
for the same JAR identifier.
Syntax
To replace an installed JAR file with the contents of a new JAR file, use the syntax:
sqlf replace-jar -file=<path or URL> -name=<identifier>
[-bind-address=<address>]
[-client-bind-address=<address>]
[-client-port=<port>]
[-extra-conn-props=<properties>]
[-help] [-locators=<adresses>]
[-mcast-address=<address>]
[-mcast-port=<port>]
[-password[=<password>]]
[-user=<username>]
This table describes options for the sqlf replace-jar command. Default values are used if you do not specify an
option.
DescriptionOption
The local path of the new JAR file, or a URL that links to the JAR
file.
-file
This argument is required.
The unique identifier of an existing JAR installation to replace. The
identifier you provide must specify a schema name delimiter. For
example: APP.myjar.
This argument is required.
-name
The address to which this peer binds for receiving peer-to-peer
messages. By default sqlf uses the hostname, or localhost if the
hostname points to a local loopback address.
-bind-address
377
sqlf Launcher Commands