See WCSysAdminGuide.pdf

PublisherQueue and PublisherQueue1

The PublisherQueue and PublisherQueue1 are used by Visualization Services to manage the publishing of CAD data. These queues are created when the first user publishes a job through Windchill Visualization Services.

All submitted publish jobs are added to PublisherQueue. When the job executes in

this queue, it is added to a free publishing queue. Publishing queues are named.PublisherQueueN (where N is a sequential integer starting at 1). By default,PublisherQueue1 is created; additional publisher queues (for example,.PublisherQueue2, PublisherQueue3, and so on) can be created with the Windchill Queue Manager.

At many customer sites, publisher queues are heavily used and execute jobs that

run for a long time (possibly, hours). Typically, CAD data is published following checkin. The objects stored in the queue entries are com.ptc.wvs.server.publish.Publi违规广告 objects.

The details of publish jobs can be viewed from the publish monitor. From the publish monitor, you can see the queue entries that log information about publishing failures. If a job has failed, use the information in the publish monitor to investigate why it failed and, after fixing the problem, resubmit the job for publishing.

WfPropagationQueue

The WfPropagationQueue is used by workflow (and its associated tasks) to propagate all state changes to Workflow objects. This includes any routing expressions and transition expressions associated with those state changes.

The workflow queues are likely to be used heavily when many concurrent Windchill users are completing workflow tasks. Also, they are likely to be used heavily in scenarios where Windchill business objects are created that use life cycles which in turn use workflows.

Failed entries in workflow queues mean that something failed to process correctly. In most cases, a failed workflow queue entry corresponds to a stack trace in the method server log. Analyze the queue entry failure by checking the method server log to determine the cause of the failure. Sometimes, the message listed in the queue manager can be enough to determine the cause of the failure.

You should examine workflow queues when the workflow activities associated with the queues do not appear to be executing properly. Additionally, it is good practice to periodically check the queues to clean out old entries.

WfScheduleQueue

The WfScheduleQueue is used by workflow (and its associated tasks) to queue all timed events. Deadline checks for any workflow object with a deadline set and expression-based Synchronization Robots are executed within this queue.The workflow queues are likely to be used heavily when many concurrent Windchill users are completing workflow tasks. Also, they are likely to be used heavily in scenarios where Windchill business objects are created that use life cycles which in turn use workflows.

Failed entries in workflow queues mean that something failed to process correctly. In most cases, a failed workflow queue entry corresponds to a stack trace in the method server log. Analyze the queue entry failure by checking the method server log to determine the cause of the failure. Sometimes, the message listed in the queue manager can be enough to determine the cause of the failure.

You should examine workflow queues when the workflow activities associated with the queues do not appear to be executing properly. Additionally, it is good practice to periodically check the queues to clean out old entries.

WfUserWorkQueue

The WfUserWorkQueue is used by workflow (and its associated tasks) to instantiate workflow robots and execute workflow robot actions.The workflow queues are likely to be used heavily when many concurrentWindchill users are completing workflow tasks. Also, they are likely to be usedheavily in scenarios where Windchill business objects are created that use life

cycles which in turn use workflows.

Failed entries in workflow queues mean that something failed to process correctly. In most cases, a failed workflow queue entry corresponds to a stack trace in the method server log. Analyze the queue entry failure by checking the method server log to determine the cause of the failure. Sometimes, the message listed in the queue manager can be enough to determine the cause of the failure.

You should examine workflow queues when the workflow activities associated with the queues do not appear to be executing properly. Additionally, it is a good practice to periodically check the queues to clean out old entries.

CleanUpScheduleQueue

TheCleanUpScheduleQueueisusedbytheStandardRecentlyVisitedService,StandardPurgeService, and the StandardCollectionService services:

   The StandardRecentlyVisitedService uses this queue to remove the oldest items from all recently visited lists when the total number of list items exceeds the value specified for the wt.recent.objectStackSize property located in the wt.properties file. The default value for this property is 100.A QueueEntry is scheduled to run at midnight the first time the StandardRecentlyVisitedService is started. Every time the QueueEntry runs itre-schedules itself to run again at midnight on the following day.The StandardPurgeService uses this queue to cleanup canceled purge jobs.The QueueEntry is only created if the wt.queue.executeQueues property is setto true. By default this property is set to true.A QueueEntry is scheduled to run every midnight. When the queue runs itdeletes cancelled purge jobs older than a day and which also have a status ofAwaiting preview.Note: Purge jobs with a status of Awaiting preview are not visible to usersviewing the user interface.

StandardCollectionService uses this queue to disable queries with invalidcriterion. This QueueEntry is only created if the both the wt.queue.executeQueues and wt.dataops.objectcol.cleanUpEnabled properties are set to true. By default both of these properties are set to true.

A QueueEntry is scheduled to run at midnight once every seven days. It disables queries with invalid criterion. For example, a query that has a folder Reschedule Indicates that the queue entry has been executed and automatically rescheduled.Severe Indicates that an unexpected problem occurred when the entry was executing. Setting this state also stops the queue

from which the entry was executing.

State Description

8-4 Windchill System Administrator’s Guide

reference that has been deleted. Disabled queries are not visible to users

viewing the Query Manager user interface