PDFlib Text Extraction Toolkit (TET) Manual

0.2 Applying the TET License Key
Using TET for production purposes requires a valid TET license key. Once you purchased
a TET license you must apply your license key in order to allow processing of arbitrarily
large documents. There are several methods for applying the license key; choose one of
the methods detailed below.
Note TET license keys are platform-dependent, and can only be used on the platform for which they
have been purchased.
Entering the license key in the Windows installer. Windows users can enter the license
key when they install TET using the supplied installer. This is the recommended
method on Windows. If you do not have write access to the registry or cannot use the installer,
refer to one of the alternate methods below instead.
Entering the license key in a license file. Set an environment (shell) variable which
points to a license file before TET functions are called. If you are using the TET library
you can alternatively set the path to the license file by setting the licensefile parameter
with the TET_set_option( ) function. The license file must be a text file according to the
sample below; you can use the license file template licensekeys.txt which is contained in
all TET distributions. Lines beginning with a ’#’ characters contain comments, and will
be ignored; the second line contains version information for the license file itself:
# Licensing information for PDFlib GmbH products
PDFlib license file 1.0
TET 3.0 ...your license key...
The details of setting environment variables vary across systems, but a typical statement
for a Unix shell looks as follows:
export PDFLIBLICENSEFILE="/path/to/licensekeys.txt"
On IBM eServer iSeries the license file can be specified as follows:
ADDENVVAR ENVVAR(PDFLIBLICENSEFILE) VALUE() LEVEL(*SYS)
This command can be specified in the startup program QSTRUP and will work for all
PDFlib GmbH products.
Multi-system license files on iSeries and zSeries. License keys for iSeries and zSeries
are system-specific and therefore cannot be shared among multiple systems. In order to
facilitate resource sharing and work with a single license file which can be shared by
multiple systems, the following license file format can be used to hold multiple systemspecific
keys in a single file:
PDFlib license file 2.0
# Licensing information for PDFlib GmbH products
TET 3.0 ...your license key... ...CPU ID1...
TET 3.0 ...your license key... ...CPU ID2...
Note the changed version number in the first line and the presence of multiple license
keys, followed by the corresponding CPU ID.
8 Chapter 0: First Steps with TET