Setting the Has Dedicated Queue Flag to True
In order to set the ‘has dedicated queue’ flag for a specific process, check out the workflow template, select the Set dedicated queue checkbox on the Properties tab of the template. Check in the template.
Setting Dedicated Queue Processing for All Newly Created Workflow Templates
If every workflow process requires its own queue, set the following wt.properties property value to true:
wt.workflow.engine.dedicatedQueue=true
|
|
All workflow templates created after this property has been set to true will have Has Dedicated Queue flag set to true. Setting the property to true does not retroactively set the flag to true for the workflow templates that were already in existence.
|
Setting Dedicated Queue Processing per Workflow Process Initiated from a Particular Workflow Template
Instead of forcing all the processes of a particular template to use the same dedicated queue, it is possible to configure Windchill to spawn a new queue for every instance of a process initiated from a template that has the Has Dedicated Queue flag set to true. All the new queues that are initiated are process queues. In order to achieve this, set the following property in the wt.property file to true:
wt.workflow.engine.dedicatedQueuePerProcess=true
|
|
This property is set globally; there is no way to set the property on a per template basis. Pay special attention to the hard limit on process queues. When the limit is reached, any new processes will throw an exception and fail to start. Given that the number of workflow processes can change dynamically, use special caution with this property.
|
