The work queue configuration file

You may want to modify the configuration of Guidewire-provided work queues to improve performance. You configure attributes of a work queue and its workers in file work-queue.xml. For custom work queues, you must modify work-queue.xml to enable your work queue to operate.

File work-queue.xml contains one top-level element, which is <work-queues>. This element has one required attribute, defaultServer. In the base configuration, Guidewire sets the value of this attribute to workqueue.
  • <work-queues xmlns="http://guidewire.com/work-queue" defaultServer="#workqueue">
Note: The hash mark in front of workqueue (#workqueue) indicates that the value that follows the hash mark is a server role and not a server ID.

Attribute defaultServer requires a value. There is no default. The PolicyCenter server refuses to start if you do not provide a value for this attribute. The server also refuses to start if you set defaultServer to a role that does not exist in <registry> element in config.xml.

Work queue definitions

Within the top-level <work-queues> element in work-queue.xml, use subelement <work-queue> to define individual work queues. 

<work-queue workQueueClass="string" progressinterval="decimal">
  <worker instances="integer" throttleinterval="decimal" env="string1, string2, …" server="string"/>
</work-queue>

The <work-queue> subelement has attributes to configure a named work queue in general. The <worker> subelement has attributes to configure worker tasks on specific servers. You can declare as many workers as you want for a work queue by specifying on which servers the workers run. You can declare a set of possible environments for a worker by specifying a value or multiple comma-separated values for the env attribute.

Access work-queue.xml in Guidewire Studio at the following location:
  • configuration > config > workqueue

See also