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 successful jobs you run.

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. When the license expires, you can no longer create objects nor submit plans.
full: This license usage is calculated based on the number of successful jobs executed. Multiple successful runs of the same job in the same job stream instance are counted only once for any calendar day (UTC timezone), this includes reruns and EVERY definitions. Unsuccessful jobs, internetwork dependencies on standard agents, and remote jobs are not calculated. The license usage information is sent to the license server you specified in the licenseServerUrl optman property, 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 14 days, all product functions are suspended. When the license expires, you can no longer create objects nor submit plans. If you want to re-activate your license, contact product support.

The number of successful jobs is calculated by the FINALPOSTREPORTS job stream, which is a successor of the FINAL job stream. The FINAL job stream is placed in production every day and runs JnextPlan before the start of a new day.

The FINALPOSTREPORTS job stream is responsible for printing post-production reports and providing statistics. To gather statistic data, the FINALPOSTREPORTS job stream runs the UpdateStats script. With HCL Workload Automation version 9.4, Fix Pack 3 and later, the UpdateStats script becomes mandatory. By default, the UpdateStats script gathers a number of statistical data, which might be irrelevant for your organization. You can therefore decide whether you want to run the whole UpdateStats script, or just the license usage statistics. To run just the license usage statistics, modify the default statement in the UpdateStats job definition by adding the -jobcountonly parameter. You can use either the Workload Designer or the composer modify command line. The following example describes both the default and the custom statements.

Default statement

Leave this task string unchanged to run the whole UpdateStats script:

UPDATESTATS SCRIPTNAME "$(install_dir)/UpdateStats"
         STREAMLOGON $(tws_user)
         RECOVERY CONTINUE
         FOLLOWS CHECKSYNC

Custom statement

Replace the default task string with the following statement to run just the license usage statistics section of the UpdateStats script:

UPDATESTATS SCRIPTNAME "$(install_dir)/UpdateStats -jobcountonly"
         STREAMLOGON $(tws_user)
         RECOVERY CONTINUE
         FOLLOWS CHECKSYN

For more information about the -jobcountonly parameter, see The logman command.

See Enabling product license management for information about the high-level steps required to set up your license server and configure HCL Workload Automation to communicate with it.

Detailed instructions about how to install and configure the license server which processes license usage information are provided in What is the HCL License & Delivery Portal (FlexNet Portal)?.

If you receive a message similar to the following, AWKFLX003E License usage information was not sent to the license server for 14 days. Object creation is now blocked, verify that information related to the license have been configured by using optman commands and check that licenseServerId and licenseServerUrl have been correctly filled. For more information about global options, see Setting global options. Contact Customer support if license data are correct.