EntireX on all applicable platforms must have a valid license key. A full EntireX license includes an unlimited number of end-user licenses (EntireX Runtime on single-user workstations). Your current EntireX license file provides full details.
If the license key does not match for a component, the component cannot be used. The license is checked during installation and when the component is started.
The following checks are performed:
the validity of the license key file (no changes may be made to license key file)
the expiration date of the license file
whether the component is licensed
whether a component is licensed on the particular platform
For EntireX Broker and the DCOM daemon, the license file is checked once daily. If the license file is due to expire in the next 30 days, a warning is issued.
For EntireX Broker, this is written to the log file.
DCOM writes additional information on license expiration (number of days remaining, expiration date) to file $EXXDIR/$EXXVERS/etc/dcom.err.
Note:
The documentation delivered with this product covers all components of
EntireX on all platforms, including those for which you may not have a valid
license. The inclusion of a component or feature in this documentation does not
imply that this component/feature is available for your installed version of
the product.
On UNIX and Windows platforms, the XML file is requested during installation and must be provided by the user performing the installation. The location of license file after installation is shown below
| Operating System | Location of License Key File |
|---|---|
| Windows | \Program Files\Common Files\Software AG\Lkey |
| UNIX | $SAG/common/LKey |
For future flexibility, the location of the license file is no longer fixed. Although the location after installation is as mentioned above, the license file can moved to a different location. The new file entirex.config at a fixed location contains the path to the license file. The location of this file is shown below:
| Operating System | Location entirex.config |
|---|---|
| Windows | <INSTALLDIR>\Software AG\EntireX\etc |
| UNIX | $SAG/exx/v80/etc |
File entirex.config contains an entry for the path of the license file, under Windows for example:
entirex.license.file="C:\Program Files\Common Files\Software AG\Lkey\exx80.xml"
If you want to change the location of the license file, adapt the entry in entirex.config accordingly.
Normally the EntireX license key is delivered directly on tape or DVD as file EXXvrs.LICS. This file contains the license information necessary to start EntireX broker. It is no longer necessary to transfer the file to the host file system.
However, if you received the EntireX license key file EXXvrs.LICS by e-mail or diskette, you need to transfer this file to the host file system, using FTP. You will need:
an FTP client (comes with Windows) and an FTP server on the mainframe, or
an FTP server on Windows and an FTP client on the mainframe.
To transfer license file EXXvrs.LICS to your
mainframe host
Transfer the file EXXvrs.XML to the host, using FTP.
As the target of the host, use the data set EXXvrs.LICS provided with the EntireX kit or allocate a new data set on z/OS with the following attributes:
DSORG=PS RECFM=FB BLKSIZE=800 LRECL=80
You must use binary transfer mode to transfer the file EXXvrs.XML to the host. This ensures that the license key remains unaltered.
Note:
You cannot "cut and paste" the certificate using a 3270 emulator
due to format incompatibilities: the mainframe is an EBCDIC system, whereas the
certificate is an ASCII-formatted binary file.
Ensure that the LICENSE DD card in the EntireX Broker startup JCL references data set EXXvrs.LICS.
open <host> <userid> <password> binary put EXXvrs.xml '<hlq>.EXXvrs.LICS' close bye
