1.1.1

2. Install the license in SQLFire. Choose one of the following options:
• On each data store member in the distributed system, add the vFabric SQLFire Enterprise serial number
directly to the sqlfire.properties file. See Option 1: Install Licenses Using sqlfire.properties on page 25; or
• Create a file that contains both the vFabric SQLFire Enterprise serial number, and copy the file to the
vFabric serial number directory on all SQLFire data store members. See Option 2: Install Licenses Using
Serial Number Files on page 26.
3. If you have obtained unique serial numbers for your other distributed systems, install the unique serial numbers
on the other distributed systems by using one of the options described in step 2.
How vFabric SQLFire Manages Licensing
Before you install vFabric SQLFire licenses, understand how SQLFire manages your licensing information.
• How vFabric SQLFire Finds and Verifies Your License on page 24
• License Working Directory on page 24
• Local VMware vFabric Directories on page 25
How vFabric SQLFire Finds and Verifies Your License
SQLFire has a default license that it uses if it cannot locate any other valid licensing.
Non-default licensing is verified using a combination of the product sqlfire.jar file and the serial numbers
you provide, or a license may be acquired dynamically from the vFabric License Server.
SQLFire uses the first valid licensing it finds in this list:
1.
Serial number specified by the license-serial-number boot property.
2. Dynamic licensing provided from a serial number file stored in the local VMware vFabric serial number
directory, configured by specifying license-serial-number=dynamic as a boot property.
3. Dynamic licensing provided by the vFabric License Server, configured by specifying
license-serial-number=dynamic as a boot property.
If SQLFire cannot validate any of the specified licensing in the above list, the member process does not start
and throws an exception.
If no licensing is specified, SQLFire uses the default evaluation licensing shipped with the product.
License Working Directory
SQLFire stores licensing information in a directory on your system. It writes to the first writable directory it
finds in this list:
1.
The value of the license-working-dir boot property, if specified for the member.
2. The SQLFire member's current working directory as determined by
System.getProperty("user.dir") at startup.
These are the files that SQLFire writes:
1.
License state files with names ending with -license.cfg. Example: vf.sf-license.cfg.
2.
License events files with names ending with -events.txt. Example: vf.sf-events.txt.
Note: Leave these files alone. Do not edit or delete these files, and do not alter the permissions on the
files or the directory where these files are located. These files are created using the default permissions
of the user who is starting up the SQLFire process. To stop or start the SQLFire process, a user needs
write permissions for this directory and the files in it. Make sure that the permissions for each user are
sufficient; otherwise SQLFire may throw an exception during stop or start.
vFabric SQLFire User's Guide24
Getting Started with vFabric SQLFire