Distributed pools

The information in this topic is applicable only for on-premises deployments.

DSO uses distributed pools to process multiple distributed operations at the same time. This simultaneous processing minimizes delays and significantly increases the output of distributed operations when DSO activity is heavy.

Distributed pools are server objects. They are created in the Distributed Pool editor, and they are stored in the Distributed Pool form.

Related topics

Creating-and-modifying-distributed-pools

After defining a pool, you must associate DSO filter or escalation actions with the pool (see Creating-workflow-to-perform-DSO-operations).

Pending distributed operations in a pool are queued and then executed in the order received (FIFO: first in, first out). Therefore, when setting up pools, consider the interdependencies between the forms in an application. All distributed operations associated with one form and all distributed operations on interdependent forms should use the same pool to ensure that the operations are executed in the correct order.

You can use different pools for unrelated distributed operations or when sending data-only or independent copies of requests to different destinations. For example, suppose your system is experiencing heavy distributed activity, and multiple data-only or independent copy transfers are pending from different applications. Because these operations do not need to be completed in a particular order, you can assign them to different pools.

You can designate one pool as the default pool or use the system default pool. If you do not create any distributed pools or if you assign a pending distributed operation to a nonexistent pool, the operation is handled by the default pool.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*