Versions Compared

Old Version 2

changes.mady.by.user Kirill Nikolaev

Saved on

compared with

New Version 3

changes.mady.by.user Kirill Nikolaev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TopLicPage
TopLicPage

...

The license is implemented in the form of a hardware dongle (a Sentinel HASP key) or a software license. Please be careful with your license key, in case of loss or damage, the CHARON-AXPinstances will AXP instances will not run or start until the license key is replaced. For extra protection, STROMASYS recommends the use of a backup license key (purchased separately) that can replace the main license key for a restricted period of time. It is possible to specify the backup license in the CHARON-AXP configuration file to prevent CHARON-AXP from stopping in case the main license dongle is no longer accessible.

...

GeneralProducts relevantOptional

  • Physical key ID

  • License Number

  • End user name

  • Master key ID

  • License release date and time

  • Update Number

  • Purchasing Company name. In most cases the company to which the key was issued originally

  • Commercial product name

  • Commercial product code

  • Commercial product version and range of build numbers suitable for running

  • Range of CHARON-AXP virtual models available for running

  • Type of host CPU required

  • Host operating system required

  • Number of virtual CPUs enabled for virtual SMP systems

  • Minimum number of host CPU cores required

  • Minimum host memory required

  • Maximum memory emulated. If not present the value defaults to the maximum memory possible for the particular virtual system. Note that the maximum memory may not be available to the virtual system if the host computer has insufficient physical memory.

  • Maximum number of CHARON-AXP instances that can be run concurrently

  • Whether or not CHAPI (CHARON API) can be used with this product

  • Product and Field Test expiration dates (if any)

  • Product and Field Test executions counter (if any)

  • Maximum number of hosts that may run CHARON-AXP concurrently (in the case of a networking license)

  • Level of support (if any), end date of any support contract, the "First Line" Service Provider

  • Frequency of CHARON-AXP license checking during CHARON-AXP execution

  • Possibility to attach hardware QBUS/UNIBUS hardware via adapter

  • Parameter that reduces the maximum speed of the program

  • Parameter that enables the product to support additional serial lines through an option board from a company such as DIGI

  • Parameter that prohibits use of Advanced CPU Emulation. If not present the Advanced CPU Emulation is enabled

  • Parameter that enables the emulation of the IEQ11-A IEEE488 Controller (on top of the DCI-3100 IEEE488 Controller)

  • Parameter that enables the emulation of the DRV11-WA I/O controller (on top of the DCI-1100 I/O controller)

Back to Table of Contents

...

Software licenses

The CHARON-AXP Software License is a "virtual" key with exactly the same functionality as the hardware dongle.

The CHARON-AXP Software License does not require any hardware but it requires installation of the Sentinel run-time environment.

Software licenses are always network-wide on Windows, so they behave the same way as Network HASP keys.

Back to Table of Contents

Multiple licenses configuration and backup license

For any type of licensing, CHARON-AXP can use only one valid ("active") license (of given vendor code) at a time.

The "HASP View" utility displays a range of available licenses, but note that by default CHARON-AXP may use any of them as the "active" license onlyone - unless it is directly specified by the "license_key_id" parameter (see below). The utility provides the license number numbers and ID / IP address addresses of the host hosts where the active license is licenses are installed.

Warning

CHARON-AXP cannot: 

  • check all the available license keys / software licenses,
  • choose one,
  • automatically switch from one key to another (except the cases if a backup license is specified in its configuration file).

The general recommendation is to avoid usage of multiple keys in one network segment. Use only one locally installed license per host or one network license per local network segment containing several CHARON-AXP hosts.

When needed, it is possible to use a special parameter in the CHARON-AXP configuration file to specify exactly which license must be used by each particular instance of CHARON-AXP:

ParameterTypeValue
license_key_id[N], N=0 or 1Numeric

A number (decimal Sentinel key ID) that specifies regular (N=0) and backup (N=1) license keys to be used by CHARON-AXP.

Example:

set session license_key_id[0]=1877752571
set session license_key_id[1]=354850588

It is also possible to specify both regular and backup key in one line.

Example:

set session license_key_id[0]=1877752571 license_key_id[1]=354850588

Depending on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-AXP behaves differently:
 

  1. No keys are specified
    CHARON-AXP behaves as usual (performs unqualified search for any suitable key). If no keys are found, CHARON-AXP exits.

  2. Both keys are specified
    CHARON-AXP performs qualified search for regular license key. If it is not found, CHARON-AXP performs qualified search for backup license key. If it is not found, CHARON-AXP exits.

  3. Only regular key is specified
    CHARON-AXP performs qualified search for regular license key. If it is not found, CHARON-AXP performs unqualified search for any suitable key. If it is not found, CHARON-AXP exits.

  4. Only backup key is specified
    CHARON-AXP behaves as usual (performs unqualified search for any suitable key). If no keys are found, CHARON-AXP exits.

 This parameter also specifies the license which will be used as backup one if the active license becomes expired.

Back to Table of Contents

...

Warning

Installation of Sentinel run-time (driver) described below is needed for Sentinel HASP keys (both regular and network), Sentinel HL keys (both regular and network) without "driverless" mode enabled, Sentinel HL Network keys (red dongles) - is they are going to be used network wide and Sentinel Software Licenses (SL).

Please skip installation of Sentinel run-time (driver) if you use locally connected Sentinel HL keys in "driverless" mode or going to use Sentinel HL Network key in "driverless" mode from some other host on local network. Just connect the license key to the host and proceed with collecting "*.c2v" file (see below) if the license inside your Sentinel HL key must be updated.

...

  1. Installation of the Sentinel run-time environment on the CHARON-AXP host (regular and network keys) or on the host that will distribute CHARON-AXP licenses over a local network segment (network key only). The Sentinel software is installed automatically by CHARON-AXP for Windows.
  2. Physical connection of the HASP license dongle to the CHARON-AXP host or to the host distributing the CHARON-AXP license over the local network segment.
  3. Collecting system fingerprint (*.c2v file), sending it to STROMASYS and applying update (*.v2c file) in case of software license. See the details below.
When manual installation of Sentinel run-time is required (in the case of the network license server that does not have CHARON-AXP installed):
  1. Open the CHARON-AXP kit folder
  2. Switch to the "hasp_install" subfolder
  3. Unzip the archive located in this folder
  4. Open "cmd.exe" and switch to the folder where the files were unzipped

  5. Issue:

    ...> haspdinst.exe -fr -kp -nomsg...> haspdinst.exe -install -cm
    Info

    Sentinel HL keys can be provided both in "driverless" and regular modes. To switch the Sentinel HL key to "driverless" mode it is required to install Sentinel run-time first as described above and apply a special *.v2c file that switches the key to "driverless" mode. Once it is done the Sentinel run-time can be deinstalled.

Back to Table of Contents

 

Replacement of currently installed Sentinel run-time

Replacement of currently installed Sentinel Run-time can be needed in case of installation of specific run-time provided by STROMASYS.
Below  Below please find step-by-step instructions on the run-time replacement:
 

Remove the current version of Sentinel run-time:
  • Extract content of the only ZIP file resided in “hasp_install” directory of the CHARON distribution to the same folder.
  • Run “cmd.exe” from “Start” menu of host computer
  • “cd” to the “hasp_install” directory
  • Issue the following command:
 

 

...> haspdinst.exe -fr -kp -nomsg

 

Install other Sentinel run-time:
  • “cd” to the directory whether the target run-time resides
  • Issue the following command:

 

...> haspdinst.exe -fr -kp -nomsg
Info

You do not need to perform this procedure for Sentinel HL keys - local and network ones (red dongle) used as local.

 

 

Back to Table of Contents

...

  • Install CHARON-AXP together with Sentinel run-time (Sentinel run-time is an essential part of CHARON-AXP for Windows distribution)

  • Reboot host system

  • Collect CHARON-AXP host fingerprint file ("*.c2v"):

    Open "License Update Service" utility:

    Image RemovedImage Added

    In the utility dialog popup open the "Collect Status Information" tab, then select "Installation of new protection key":

    Image RemovedImage Added

    Press "Collect Information". In the popup dialog choose the place to store the "Fingerprint.c2v" file and press "Save":

    Image RemovedImage Added

    A message should appear similar to this example, confirming the fingerprint has been collected successfully.

    Image RemovedImage Added

  • Send the ".c2v" file ("Fingerprint.c2v" in the example above) to STROMASYS

  • STOMASYS will send you a ".v2c" file in return. Put it somewhere on the CHARON-AXP host.

  • Open up the  "License Update Service" utility the way described above and open the "Apply License File" tab:
    Image Removed
    Image Added 

    Press "..." button beside the "Update File" edit-box. In the popup select the license file received from STROMASYS:
    Image Removed
    Image Added 

    Press the "Open" button and apply the license.

  • Start any web browser on this system and go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).

  • Ensure that the license appears in the “Sentinel Keys” menu.

Info

Content of the installed software license is not shown by the Sentinel HASP Admin Control Center.To see it run the "HASP View" utility from the CHARON-AXP "Utilities" menu (see above):Image RemovedImage Added

 

Back to Table of Contents

...

New license keys from Sentinel, so called "Sentinel HL" can work in 2 modes:

  1. Regular. The key behaves as normal Sentinel HASP key.
  2. "Driverless". Sentinel HL keys do not require installation of any specific run-time or drivers since they unitize HID drivers, which are an integral part of the Windows operating system.

...

To access Sentinel Admin Control Center start any web browser, enter http://localhost:1947 and press Enter. Web interface of the Sentinel Admin Control Center will appear.

 Example:

Image RemovedImage Added

This example demonstrates that 4 license keys are available:

  1. Network key ("HASP-HL NetTime") on the host "XEON4WAYW7"

  2. Network key installed locally

  3. HASP-HL installed locally

  4. Network-wide software license on the host "RH64"


Sentinel Admin Control Center reports that there is one opened session on key (4). The other keys are not being used at the moment

For a more detailed description of Sentinel Admin Control Center, please refer to its "Help" section.

...

Disable remote keys access 

A helpful feature of Sentinel Admin Control Center is the ability to disable access to remote keys. If the network key is installed locally, access to the key from remote hosts can be disabled. The following examples demonstrate how this can be done.

To disable access to remote keys switch to the "Access to Remote License Managers" tab and uncheck the "Allow Access to Remote Licenses" checkbox. Then press the "Submit" button to apply this change:

Image RemovedImage Added

To disable access to the locally installed license key from remote hosts switch to the "Access from Remote Clients" tab and uncheck the "Allow Access from Remote Clients" checkbox. Then press "Submit" button to apply this setting:

Image RemovedImage Added

Back to Table of Contents

...

  1. Collect the specific information about the "RecipientHost" to issue a transfer license: run the "License Update Service" utility on the "RecipientHost" (see above), choose the "Transfer License" tab and pressthe "..." button adjacent to the "Save Recipient Information" edit-box:

     Image RemovedImage Added
    In the popup choose a directory an file name for the recipient information.
    Press the "Collect and Save Information" button to create the recipient information file.
     

  2. Copy the recipient file to the "SourceHost".

    Info
    The recipient file is an ASCII file, so use "ascii" option in case of FTP transfer.

           

  3. On "SourceHost", run "License Update Service" utility, select "Transfer License" tab and the particular license to transfer in the big edit-box.Press the "..." button adjacent to the "Read the recipient information from file" edit-box, choose the just transferred recipient file,  press the "Open" button.
    Press the "..." button adjacent to the "Generate the license transfer file to" edit-box, choose the target directory and enter the desired name of the transfer file (*.h2h), then press the "Save" button.
    Press the "Generate License Transfer File" button to create the license transfer file in the specified folder.
     

  4. Copy the resulting "*.h2h" file to the "RecipientHost".

    Info
    "*.h2h" file is an ASCII file, so use the "ascii" option in case of FTP transfer.

          

  5. On the "RecipientHost", apply the license transfer file ("*.h2h") the same way as a regular software license (see above).
  6. Start any web browser on the "RecipientHost" and go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
  7. Ensure that the license appears in the “Sentinel Keys” menu.
Back to Table of Contents

Software License Removal
It is also possible to remove a Software License completely from a host, the license will then be stored in a specific transfer license file "*.h2h", so it can be re-applied if needed.To remove a Software License completely from a host, follow the license transfer procedure described above. It is possible to use the fingerprint of the "SourceHost" (instead of the one from the "RecipientHost") for the transfer procedure.
Back to Table of Contents

...