| Using License Keys > > Using License Keys > About Keys > Key Fields |
Key Fields |
INDEX
PREVIOUS
NEXT
|
This topic describes the format of a key and gives the meaning of each field. The keys are of the general form:
KEYTYPE ILOG-ProductNameAndVersion ExpiryDate KEYCHECKSUM JHostID FLAG, (application: yourapp OR options:) |
| Note |
| Not all of these fields will be present in a particular key. |
For example:
NODE ILOG-Product 6.000 31-May-2008 JGD6F3NGWJ27 2ac1445e, application: yourapp
The meaning of the various fields is explained in Table 2. Further information about the significance of these fields is given in Additional Information About Keys.
Key Field |
Description |
|---|---|
KEYTYPE |
The Key Types, that is, EVAL, NODE, SITE or RUNTIME. |
ILOG-ProductNameAndVersion |
The ILOG product name and version. |
ExpiryDate |
Depending on the licensing contract, keys may have an expiry date. |
KEYCHECKSUM |
Keys are protected by a checksum and editing any of their fields will invalidate the key. |
JHostID |
For NODE keys only. NODE keys are bound to a single machine identified by means of the jHostID. To obtain your jHostIDs you have to run the jhostid utility. |
FLAG |
For SITE and RUNTIME keys only. Indicates whether the product displays licensee messages. |
application: yourapp |
NODE and SITE keys optionally contain the name of the application that you are developing. If no application name is declared, the key is valid for an unlimited number of applications.
RUNTIME keys must contain the name of your application. You cannot deliver an application if you do not have a valid development key and its associated RUNTIME key. |
options: |
For example, a maintenance termination date. |
| Copyright © 1987-2007 ILOG S.A. All rights reserved. Documentation homepage. Legal terms. | PREVIOUS NEXT |