License computation model

About this task

Use the license computation model to keep track of your license usage and maintain compliance. You can buy a trial license, which lasts 30 days before it expires, or a standard license, which calculates the number of completed jobs you run on z-centric and dynamic agents. All the information required for activating your license is provided in the e-mail you receive after completing your subscription.

You can choose between the following license types:
trial
This license lasts for 30 days starting from your subscription day, irrespective of the number of jobs you run on z-centric and dynamic agents. When the license expires, you can no longer submit jobs on these agents.
full
This license usage is calculated based on the number of completed jobs executed. Multiple completed runs of the same job in the same application instance are counted multiple times. Jobs that did not complete successfully are not counted. The license usage information is sent to the license server that you specified in the LICENSEURL of the HTTPOPTS statement, where it is processed. If the license server cannot be contacted, the information is stored locally and an error message is displayed. If the license server cannot be contacted for more than 30 days, you can no longer submit jobs on z-centric and dynamic agents.

If your license expires, you can re-activate it by contacting the product support.

To activate the license, perform the following steps:
  1. In the mail confirming your license, find:
    • The instructions about how to obtain the ID of the license server which processes license usage information
    • The URL of the license server which processes license usage information
  2. Set this information respectively in the LICENSEID and LICENSEURL of the HTTPOPTS statement.

The number of completed jobs is calculated by the daily planning process when the new current plan is created. The jobs are counted starting from the latest time when the usage information was sent to the license server.

To secure the communication between the Z controller and license server, perform the following procedure. For detailed information about logging in to and using the FlexNet End-User Portal, see the FlexNet Operations End-User Portal Help Library.
  1. From the FlexNet End-User Portal, create your device to run the license server and set the password for the license server administrator.
  2. Map your license entitlement to the license server.
  3. From your workstation, generate a private/public key pair. The key pair must be in RSA 2048-bit format. The private key must be in PKCS#8 format, and the public key format must be in DER format.
    You can use any available third-party tool to generate the key pair. The following example shows a key pair generation by using OpenSSL:
    # Generate private key.
    $openssl genrsa -out private_key.pem 2048
    # Get the public key.
    $openssl rsa -in private_key.pem -pubout -outform DER -out public_key.der
    # Convert private key to pkcs8 format to use it 
    $openssl pkcs8 -topk8 -inform PEM -outform PEM -in private_key.pem -out private_out_key.pem -nocrypt
    
  4. Upload the public key to the license server by using the FlexNet Embedded License Server Administrator command-line tool (flexnetlsadmin.bat) provided by Flexera. For details about downloading FlexNet Embedded, see FlexNet Licensing.
    Issue the following command:
    flexnetlsadmin.bat -server https://[license server host]/api/1.0/instances/[license server ID]
    -authorize admin [license sever admin password] -uploadPublicKey [local path to public key (in DER format)]
    where:
    license server host
    URL of the license server that processes the information about the license usage.
    license server ID
    ID of the license server that processes the information about the license usage.
    license server admin password
    Password that you have set for the license server administrator.
    local path to public key
    Local path to the public key, which is a DER file.

To configure the Z controller to enable you to schedule jobs on z-centric and dynamic agents, see Enabling jobs submission on z-centric and dynamic agents.