Inside Automation Engine > Executing Objects > AE Priority

AE Priority

The AE priority influences the processing of tasks within an AE system. It can be used for clients and tasks, although with very different impacts.

The variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS contains entries for both priority types in which the administrator can specify default values:

AE priority

Setting

Client priority

Key CLIENT_PRIORITY - Priority of the clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.

Task priority

Key TASK_PRIORITY - Default priority for all the objects of a client

You can also specify a priority in the Attributes tab of an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task. The priority specified in here then only applies for the particular object and overrides the entry made in TASK_PRIORITY.

Client Priority

An AE system consists of the system client 0000 and up to 9999 userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management.-defined clients. The Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. processes all messages sent by them, with the client priority determining the order in which they are processed. Clients of a higher priority are always given priority to clients of a lower priority regardless of the order in which the messages were originally sent. The "first-in-first-out" principle applies when there are two clients with the same priority. The message arriving first is processed first.

Task Priority

Task priority is not the same as client priority! The priority specified for tasks influences the starting order of tasks that are in a waiting condition. The taskAn executable object that is running. Tasks are also referred to as activities. with the highest priority is started first. It does, however, not influence the further processing of these tasks.

The following listShows entities in a grid view shows possible waiting conditions:

The priority of the individual tasks is shown in the Activity Window and can also be changed here. Use the command Modify AE priority in the context menu. The value specified in here is then valid for this particular execution! If the task is started again, the previously defined priority applies.

As mentioned above, the priority does not influence the processing order of tasks. It serves to define their starting order. Therefore, changing the priority of activated tasks does only show a result for tasks that are in a waiting condition.

The default value "0" has been preset in the Attributes tab of objects. Hence, the priority specified in the variable UC_CLIENT_SETTINGS (key TASK_PRIORITY) applies.

For tasks of the same priority, the "First in/first out" principle applies.

See also:

Activity Window

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH