6.2.1.4 How Licenses are Pooled by the ISV Server
When the ISV server processes all its licenses in the license file, it combines as many as possible into single pools of licenses. In order for two licenses to be combined into a single license pool, the following license fields must match exactly:
- Product Name
- Product Version
- License Sharing specification
- License Timezone specification
- License Platform list
- Both licenses must be counted or uncounted
- License node-locked hostid
- Both licenses must be user-based or host-based (or neither)
- Neither license can be a named-user license
- License password
Once pooled, the following fields are processed as shown:
| Field | Result |
|---|---|
| count | both counts added together |
| exp-date | earlier date is remembered |
| hold | maximum of the 2 values |
| max_roam | minimum of the 2 values |
| min_checkout | maximum of the 2 values |
| min_timeout | maximum of the 2 values |
| soft_limit | both soft_limit values added together |
| contract | if original is empty, use new |
| customer | if original is empty, use new |
| issuer | if original is empty, use new |
| type | if original is empty, use new |
For all other fields, the field in the original license (i.e., the first to appear in the license file) is used.
Note that different named_user licenses are never combined into one license pool.
The id of a license can affect license pooling as follows: A license that doesn't specify an id (or specifies 0), will pool with any other license that it would normally pool with. However, a nonzero id will only pool with the same ID# (assuming all the other attributes make it eligible to pool).