Core components

The core components of AVEVA Work Tasks are as follows:

Server

A Server is a machine on which the Client Service, Advance Server Service, Communication Service, Task Scheduler, Mobile Notification Service, and Workflow Engine are installed. If the load balancing feature is enabled during the Farm configuration, the Load Balanced Server License is acquired and the Advance Server service is installed and enabled. These services can be installed on a single server or on multiple servers. In the case of Developer and Professional Editions, all services are installed on the same server, whereas in the case of Load Balanced Server, the services are installed on multiple servers.

The primary role of the Server is to control workflow execution and schedule tasks. The Workflow Engine and the Task Scheduler are services that control workflow execution. The Communication service manages communication and notifications. The Advance Server service enables load balancing.

Client

A Client is a machine in which the Central Configuration and the Enterprise Console are enabled. If the load balancing feature is enabled during the Farm configuration, the Load Balanced Server License is acquired and the Advance Server service is installed and enabled.

Farm Database

A Farm Database is a machine that contains information about the Enterprise Console, location of the Central Configuration, and configuration settings at a global and server (machine) level. These settings are specified in the Farm Configuration Wizard database.

Central Configuration

The Central Configuration enables you to define, create and manage repositories for workflows and execute them. A Repository refers to a database that contains workflow definitions, queues, calendars, settings, and workflow execution data for an application.

The location and settings for the Central Configuration are specified from the Farm Configuration Wizard. The Repository settings are stored in the database specified for the repository.

Enterprise Console

This is a Web-based interface that allows authorized users to build workflow driven applications and also allows users to participate in these applications. The console enables central administration of all workflows associated with a repository. Activities that can be performed from the Enterprise Console include workflow categorization, workflow design, associating workflows with lists, events, initiating workflows for new workflow creation, publishing workflows, creation, management and association of Forms with workflows and viewing reports. The Enterprise Console also enables administrators to set up and manage queues and calendars for use in workflows.

• One Enterprise Console can be mapped to one or more Repositories; however users can login only to their respective Repositories.

• One or more Enterprise Consoles can be configured for the same repository.

• The Enterprise Console can be configured for more than one repository.

• The Enterprise Console is defined and managed using the Farm Configuration Wizard.

Repository

A Repository is a database that contains workflow definitions, queues, calendars, settings, workflow execution data and Business Activity Monitoring (BAM) data. Data Sources for Repositories are defined in the Central Configuration.

A Repository can also be created for each client in a hosted environment (Application Service Provider environment).

Note: Workflows existing in two different Repositories cannot interact with each other. User Sources (also known as Resource Providers) are specific to a repository although multiple user providers are possible per repository. A Resource Provider is a user data source such as Active Directory or an application's custom data source.
Example: If you are defining workflows for your organization, the organization must be defined as a AVEVA Work Tasks Repository. Repositories are created from the Central Configuration.

Repository Data Source

A Repository Data Source is connection information specific to a repository database. AVEVA Work Tasks services use a Repository Data Source to connect to the database.

Forms

The Forms is an easy to use drag and drop interface used for designing forms. You can use forms designer to quickly design forms, maintain form templates, and define business logic. The Forms are used to trigger Workflows.

Farm

A Farm is a collection of Servers and Client services working as a single logical entity to provide the AVEVA Work Tasks solution. The Farm configuration is achieved through the Farm configuration wizard.

The following image displays the various components of AVEVA Work Tasks and how these components interface with each other.