Creating a separate background processing queue and queue mapping

  1. In the Infor Rich Client, select Async Administrator > Async Framework Components > Queues.
  2. Select Actions > Create.
  3. Specify this information:
    Name
    Provide a name for the queue.
    Description
    Provide a description of the queue.
    Priority
    Select the priority for any processing that is performed by the queue using this queue mapping. Options are Critical, High, Above Normal, Normal, Below Normal, Low, and None. None means the action is never executed. Normal is the default.
    Max Active Actions
    Select the maximum number of active actions or worker threads for the queue. This controls the number of triggers that can be processed concurrently by the queue. The recommended number is 2. You can adjust this number. Base adjustments on system resources and the volume of data that is processed.
    Suspended
    Select whether the queue is suspended. If a queue is suspended, the queue does not start the processing of any more triggers. Triggers that are already started continue to be processed.
    Save History
    Select whether to save the queue history. If you select True, then triggers are not deleted from the database when they have finished. No matter what setting you use here, triggers that are unsuccessfully processed are saved. The default, and general recommendation is to not save history. Saving history leads to large numbers of accumulated finished triggers.
    System Queue
    Select whether the queue is a system queue, one that is internal to the system, for example, the email queue. This is not a system queue, so leave this field cleared.
  4. Click Save.
  5. Select the Queue Mappings tab.
  6. Click Create.
  7. Specify this information:
    Actor
    Select an actor to use to determine whether a background execution task is assigned to this queue. If you leave this field blank, all actors are used.
    Data Area
    Select the application data area.
    Class
    Select EmployeeAbsencePlan.
    Action
    Select EmployeeAbsencePlanCalculation.
    Save History
    Select whether to save the queue history. The valid values are Queue Default, Yes, and No. Select Yes with caution. It can result in a large number of accumulated trigger history records. Queue Default is the default. Whether history is saved is determined by the setting for the queue.
    Log Producer Name
    This is the log producer to use for problems or exception from triggers matching this queue mapping. If this field is blank, then the standard Async Logger is used.
  8. Click Save.