Licensing for AVEVA Work Tasks

Prerequisites

• Ensure that the AVEVA License Manager and AVEVA License Server is installed on a machine, which is on the local network and can be accessed by all the AVEVA Work Tasks servers and clients.

• In the AVEVA License Configurator, ensure that you provide the details of the machine where the License Manager and License Server are installed.

• Ensure that the AVEVA LICAPI is installed as a prerequisite during the AVEVA Work Tasks installation.

Types of Licenses

The following are the types of licenses and their precedence, when all these licenses are available together:

1. Single Server

2. Load Balanced Server

Scenarios

• If load balance is enabled during Farm configuration, then the Load Balanced Server license is acquired, based on its availability. The Advance Server Service is installed and is enabled.

• If load balance is disabled during Farm configuration, then either the Single Server license is acquired, based on the availability. The Advance Server Service is installed and is disabled.

• To use Forms Designer, the Forms Server license has to be acquired. The Forms Server license is released when the Client service is stopped. The Forms license should be activated on all Web server(s) rendering the Forms.

• If the corecount license is activated and acquired along with any of the Standard licenses, then the client connection license is not checked, and there is no limit for the number of user connections.

• If "CPU Cores" count license is activated, then the "CPU Cores" count must depend on the system CPU Core count.

  For example: If the system has a 4 Core Processor, then the "CPU Cores" count in the license must be 4 or above.

Services

Workflow Engine Service

• The Workflow Engine service starts only when the following conditions are met:

  • The license is activated.

  • The concworkflow and/or developer features are available.

• When you start the Workflow Engine Service, the concworkflow and corecount license features will get acquired based on the License type. However, after this service is stopped, the license features acquired above are released.

• Before starting the Workflow Engine Service, the license availability is checked. If any server license is not activated and available, then the Workflow Engine Service is not started.

• The Workflow Engine Service checks the license periodically i.e. at an interval of 24 hours.

  • Consider a scenario where the user deactivates the server license when the license has been activated and the Workflow Engine service is running. After 24 hours, if the Workflow Engine Service is still running but the license is deactivated, then the grace period for the license is activated. A warning message is displayed to the Administrator through an exception email. The Workflow Engine Service service checks for license activation every day. If the license is not yet activated after the 7th day, then the Workflow Engine Service service is stopped. If the license is activated, then the Workflow Engine Service service will continue to run. .

• The licenses acquired by the Advance Server service and the Workflow Engine Service will be released when the Client Service is stopped.

• You can log on to the Enterprise Console only if the Client service and the Workflow Engine Service are running.