Topic 1.2.1: Wonderware Skelta Architecture

Structural Parts

The following image shows the AVEVA Workflow Management Architecture:

Architeture

Enterprise Console

This is a Web-based interface that allows authorized users to build workflow driven applications, and to participate in these applications. Organizations can create and access their business applications using Enterprise Console.

Repository

A Repository is a container that holds Business Process Management (BPM) and application-related data. It has a unique name and description.

The Repositories are stored within the Database. You can also maintain each Repository on a different Database and isolate the information from each other. AVEVA Workflow Management typically requires that you create one repository for an organization. However, sometimes there may be a need for more than one Repository. For example, you may have separate development and production environments or have a need to completely isolate applications from each other. One more compelling scenario for creating more than one Repository is that of hosted solutions, where each client needs a secure data store and isolation. In such a case, you will need to create multiple Repositories. Repositories are maintained using Enterprise Console

Services

The Server controls various service requests using Services. The Services comprises the following:

  • Workflow Engine Service: This service needs to be running for the execution and control of workflows.
  • Task Scheduler Service: This service handles the execution of all tasks that have not taken place as scheduled (escalations).
  • Communication Service: This service handles incoming e-mail and SMS communication.
  • Advanced Server Service: This service provides load balancing and failover support. This service is available only if Enterprise Edition is installed.
  • Client Service: This is used internally by AVEVA Workflow Management for provisioning and deployment.
  • Mobile Notification Service: This service is used to send notifications to the Work Tasks Pro mobile application.

    The Workflow Engine Service can exist on a single machine or on multiple machines. For Load Balancing and Failover support to function, Workflow Engine Services must be installed on multiple machines and Advanced Server Service must also be enabled on these machines

Last modified: Wednesday, 6 May 2020, 2:46 PM