Altova FlowForce Server 2024 Advanced Edition

At the core of distributed execution lies the concept of execution queues.


An execution queue is a processor of jobs. It controls how job instances run. In order to run, every job instance is assigned to a target execution queue. The queue controls how many job instances (of all the jobs assigned to the queue) can be running at any one time and the delay between runs. By default, the queue settings are local to the job, but you can also define queues as standalone objects shared by multiple jobs. When multiple jobs are assigned to the same execution queue, they will share that queue for executing.


Queues benefit from the same security access mechanism as other FlowForce Server configuration objects. Namely, a user must have the Define execution queues privilege in order to create queues (see also Define Users and Roles). In addition, users can view queues and assign jobs to queues if they have appropriate container permissions (see also How Permissions Work). By default, any authenticated user gets the Queue - Use permission, which means they can assign jobs to queues. To restrict access to queues, navigate to the container where the queue is defined and change the permission of the container to Queue - No access for the role authenticated. Next, assign the permission Queue - Use to any roles or users that you need. For more information, see Restricting Access to the /public Container.


Shared queues provide a flexible mechanism to control server load on a single FlowForce machine or on a cluster. Configuring load balancing is a multi-step process that comprises the following procedures:


1.First, you need to create a queue.

2.Second, for each queue, you need to define its processing settings. For example, you can configure a queue to run only on the master, only on workers, or both. It is also possible to define basic fallback criteria. For instance, a queue may be configured to run by default on the master and all its workers; however, if all workers become unavailable, the queue will fall back to the master only.

3.Third, you need to assign jobs to the queue created previously.


To find out more about these procedures, see Queue Settings.


Note:Cross-system clusters are not supported, which means that a worker-master connection cannot be established between different OS platforms (e.g., between Linux and Windows).


Global vs local queues

You can create a queue as a standalone object (global) or within the framework of a particular job (local). Local queues do not support distributed processing. The queue must be created as a standalone object (external to the job) in order to benefit from distributed processing. For information about creating standalone and local queues, see Queue Settings.


© 2018-2024 Altova GmbH