The following table lists and describes all the terms used for and in the license file.
|
Term |
Description |
|---|---|
|
instID |
Installation ID. This is the unique identifier of the system (database) that has been installed. Unless unspecified is defined, the Installation ID is created by the product the first time it is started. instID is used as the unique search criterion for an installation in a license file. |
|
product |
This refers to the actual Beta product. It describes the installation defined by the Installation ID, and is the name of the schema that specifies which entries can be made for this product in the license file. Add-ons and enhancement facilities are declared as articles within the product. |
|
start |
The starting date of a license period in format yyyy-mm-dd. Before this date, the license is invalid. |
|
termination |
The end date of a license period in format yyyy-mm-dd. After this date, the license is invalid and will terminate after x days, depending on the license term and the license policy. |
|
licenseTerm |
This field shows the license termination type, either permanent or temporary. permanent: The product has been purchased. temporary: The product has been acquired for a specific period of time. This can be a one-off fee for a defined period of time, or the rental for the product. |
|
licenseType |
The license type indicates the conditions of contract and which units of measurement are to be applied. There are three license types: MIPS Usage Server |
|
licensePolicy |
The license policy defines how a product will behave under certain circumstances: enforced: This parameter specifies that when a product reaches a specific threshold value without being renewed, it will not allow any further functions, or that the system stops or cannot be started when a mainframe used with a MIPS license is upgraded. tolerant: Threshold values can be exceeded, but the deviations are logged. A mainframe with a MIPS license can be upgraded, but a warning will be issued stating the goodwill period. |
|
installationType |
The installation type specifies how the product can be used and includes the boundary conditions for this use: Trial: This type of installation enables a product or product component to be tested. It can be used when installing the product for the first time. Test: This is a fully-fledged product installation that is not being used for production, but for tests or integration tests instead, with a variety of other software. Its purpose would be to map the infrastructure of the productive system. Production: A fully-fledged production system. Standby: These are systems that are kept on standby for emergencies, or are only used for production in transitional situations. |
|
cpuType |
This value defines the processor type (tttt – the last four digits of the serial number) and the number of configured processors (cc). |
|
serverName |
The DNS name is used to check dedicated servers. |
|
article name |
Name of an add-on ("Base" indicates the base product). |
|
period |
The period of validity of an add-on (does not apply to Base). value: The starting point of the period of validity. value2: The end of the period of validity. |
|
goodwill |
The number of days the product can still be used if certain parameters in the license file are invalid, e.g. invalid cpuType or serverName. Once the goodwill period has elapsed, the product will stop, regardless of the license period. |
|
warning |
When a license is due to expire, a warning message will be issued from this point in time onward. |
|
<?xml version="1.0" encoding="UTF-8"?> |
Any manipulation of the license file will invalidate it.