Async Framework and Queue Management Overview

The Async Administrator web application enables administrators to manage the Async Framework. This framework provides background execution processing for a Landmark system, In managing the Async Framework, the administrator aims to achieve a balance of business processing needs, online responsiveness, and overall system stability.

The Async Framework provides several components and tools to help manage the execution workload. Administrators can define jobs and job streams, and schedule recurring and non-recurring jobs. Recurring jobs and ad-hoc incoming background actions can be assigned to specific queues with varying priorities and with appropriate limits on the maximum number of actions that can be processed concurrently. In these ways, you can manage the processing load for your system so that jobs finish in a timely manner and the system as a whole has the necessary resources available at all times for both foreground and background processing.

Key concepts

  • Async Action Request

    Async action requests represent processing tasks that are intended to be run in the background. The request includes information about the action, its parameters, and any scheduling details.

  • Async Action Trigger

    Triggers represent an actual execution or instance of a request. For requests with a recurring schedule, there are then multiple triggers, one for each execution needed. Triggers are the entities that are queued, and through queue mapping can be assigned to specific queues in order to control the processing priority and workload.

  • Queue

    A sequential list to store tasks for processing. Administrators can create additional queues as necessary.

  • Synchronized Groups and Background Groups

    Synchronized groups and background groups provide additional ways to control trigger processing. Synchronized groups allow only one member of the group to be processed at a time. In background groups, the triggers are ordered so that each one waits for the previous trigger to be done processing.

  • Jobs and Job Streams

    Administrators can define jobs in order to perform actions for a specific business class, and then create job streams to perform a sequence of jobs.