...
- VMware only: for the first license request in a VMware environment, or if the binding data has changed, use the esxi_bind command to bind the license server to its ESXi host or vCenter Server.
- Collect the fingerprint (the customer-to-vendor - or C2V - file) on the license server and (if applicable) the backup license server.
- Send the fingerprint data to Stromasys stating the license requirements based on your contract with Stromasys (product version, number of concurrent instances, is this the main or the backup license, etc.). Stromasys will send you the license data. Please also indicate if the following:
- Do you require a license with or without a passphrase (can be selected per product section). The use of a passphrase requires Charon-SSP emulator versions 4.3.x and higher and VE license server versions 1.1.x and higher.
- Do you require an AutoVE license (available from version 1.13 and higher for supported AWS AMIs)?
- Stromasys will send you a license (V2C file with license data and text file with human readable license content).
- Install the license data (the vendor-to-customer - or V2C - file) on the license server and (if applicable) on the backup license server.
- Verify the license installation.
...
Stromasys or your Stromasys VAR will provide you with an email address to which you should send the C2V file you created in the previous step.
Please also indicate if the following:
- Do you require a license with or without a passphrase (can be selected per product section). The use of a passphrase requires Charon-SSP emulator versions 4.3.x and higher and VE license server versions 1.1.x and higher.
- Do you require an AutoVE license (available from version 1.13 and higher for supported AWS AMIs)?
In response, you will receive a so-called V2C (vendor-to-customer) file which contains the license data. The content of the license (type of emulated SPARC, expiration date, number of concurrent instances, etc.) depends on your contract with Stromasys. You may also receive a text file containing the license content in human readable form.
...
Important key-specific license parameters:
| Parameter | Explanation |
|---|---|
| Platform |
...
| The platform for which the license has been created. This parameter cannot be changed by a license update. | |
| Release date |
...
| Date on which the license has been issued. | |
| Customer name |
...
| The owner of the license. This parameter cannot be changed by a license update. If a change is required, the existing license must be removed before creating a new fingerprint. | |
| License ID |
...
| In older versions, the license ID changed if the license server software was reinstalled; in newer versions, it will remain unchanged as long as the license server host instance is not re-installed. This parameter cannot be changed by a license update. If a change is required, the existing license must be removed before creating a new fingerprint. | |
| Key type |
...
| Possible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours). | |
| Expiration date |
...
| Configured number of emulator runtime hours. The remaining hours can be seen in the web interface of the license server and the emulator log file. | |
| Grace period: |
...
| Time in minutes the emulator can run after the license used by the emulator has timed out or disappeared. Configured by Stromasys when creating the license (default: 2 hours for general VE, 24 hours for AutoVE). | |
| License check interval |
...
| License check interval (1 hour). |
Important product-specific license parameters:
| Parameter | Explanation |
|---|---|
| Expiration date |
...
| The expiration date. | |
| Major version and Minor version |
...
| The major and minor product versions. | |
| Maximum CPU |
...
| Defines the maximum number of CPUs in an emulated system (emulated SPARC in the example). | |
| Maximum virtual memory |
...
| Defines the maximum amount of RAM in an emulated system. | |
| Instances allowed |
...
| Defines the maximum number of concurrently running emulated systems. | |
| Passphrase |
...
| Defines the passphrase that must be configured on the license client system. |
| Div | ||
|---|---|---|
| ||
Using the Web Interface
...
Prerequisite: access to TCP port 8084 (or an alternative port configured in the file /opt/license-server/config.ini file) of the license server must be possible.
...