Queuing tab

On this tab, you specify how to store successful and failed jobs. You can also specify when and how many times the StreamServer should try to resend a failed job from the queue.

Setting	Description
Store successful jobs	Select the type of data to store for successful jobs. • No – Select to store nothing. • Store information only – Select to store job information. • Store information and job – Select to store job information and the job. This option enables jobs to be resent from the queue. Successful jobs remain in the queues as long as specified in the Platform configuration dialog box (see Configure Platform dialog box – Generic layer mode).
Store failed jobs	Select the type of data to store for failed jobs. • No – Select to store nothing. • Store information only – Select to store job information. • Store information and job – Select to store job information and the job. This option enables jobs to be resent from the queue. Failed jobs remain in the queues as long as specified in the Platform configuration dialog box (see Configure Platform dialog box – Generic layer mode).
Retries	The maximum number of times the StreamServer should try to resend a failed job from the queue.
Retry delay (ms)	The time (milliseconds) the StreamServer should wait before it tries to resend a failed job from the queue.
Queue can be shared	Enable sharing of the queue. If several StreamServer applications in the same application domain are used for load balancing and failover, they must be able to share queues. You must, in each Design Center Project (one Project per StreamServer application), enable sharing for all queues to be shared. Note: If you disable sharing for a queue in Project A, and enable sharing for the same queue in Project B, then StreamServer B can consume StreamServer A’s jobs. StreamServer A cannot consume StreamServer B’s jobs in this case.