Message Prioritization Workflow Queues
Many of the tasks listed in the table can be executed synchronously (synchronous web service, in-memory workflows, and so on).
Any synchronous execution does not go through queues and is not affected. Synchronous executions are done immediately and priority has not impact. However, the priority is passed to other workflows initiated by such workflows.
Property | Default | Impact |
---|---|---|
Workflow Queue | ||
com.tibco.cim.workflow.priority. importscheme | 0 | Import classification through UI |
com.tibco.cim.workflow.priority. workitem.expiryrecompute | 0 | Recomputation of expiry date of workitem when a record associated with the workitem changes, and expiry method is COMPUTE |
com.tibco.cim.workflow.priority.import.filewatcher | 0 | Import through file watcher |
com.tibco.cim.workflow.priority. importscheme.filewatcher | 0 | Import classification through file watcher |
com.tibco.cim.workflow.priority.upload.filewatcher | 0 | Upload through file watcher |
com.tibco.cim.workflow.priority. uploadimport.filewatcher | 0 | Upload and import through file watcher |
com.tibco.cim.workflow.priority.sync. filewatcher | 0 | Synchronization through file watcher |
com.tibco.cim.workflow.priority. validatesync.filewatcher | 0 | Validation of sync through file watcher |
com.tibco.cim.workflow.priority. dataserviceupdate.filewatcher | 0 | Import metadata through file watcher |
com.tibco.cim.workflow.priority. dataservicequery.filewatcher | 0 | Export metadata through file watcher |
com.tibco.cim.workflow.priority. exportrecords.filewatcher | 0 | Export records through file watcher |
com.tibco.cim.workflow.priority.purge. filewatcher | 0 | Purge through file watcher |
com.tibco.cim.workflow.priority.event. resubmit | 0 | Resubmit event |
com.tibco.cim.workflow.priority. workitem.timeout | 0 | Send timeout message to workflow for workitem timeout |
com.tibco.cim.workflow.priority.event. checkwaiting | 0 | Check for a queued event |
com.tibco.cim.workflow.priority.event. timeout | 0 | Timeout of suspended event |
com.tibco.cim.workflow.priority. workitem.notify | 0 | Generation of workitem notifications |
Async Queue | ||
com.tibco.cim.async.priority. changenotif | 0 | Prepare and generate change notifications |
com.tibco.cim.async.priority.syncstatus | 0 | Compute sync status |
com.tibco.cim.async.priority. extractscheme | 0 | Extract and assign classifications to records |
Workflow Queue | ||
com.tibco.cim.workflow.priority.import | 4 | Import through UI |
com.tibco.cim.workflow.priority. massupdate | 4 | mass update of records through UI |
com.tibco.cim.workflow.priority. validatesync | 4 | Validation of sync through UI |
com.tibco.cim.workflow.priority.upload | 4 | Upload of data source through UI |
com.tibco.cim.workflow.priority.sync | 4 | Sync though UI |
com.tibco.cim.workflow.priority. exportrecords | 4 | Export records through UI |
com.tibco.cim.workflow.priority.sync. webservice | 4 | Sync initiation through web services |
com.tibco.cim.workflow.priority. dataserviceupdate | 4 | Import metadata through UI |
com.tibco.cim.workflow.priority. dataservicequery | 4 | Export metadata through UI |
com.tibco.cim.workflow.priority. recordmsg | 4 | “Send message”, RFCIN, TIBCO MDM through record actions (send message) from UI |
com.tibco.cim.workflow.priority. recordmsg.ws | 4 | Initiate workflow from web service |
com.tibco.cim.workflow.priority. jms | 4 | JMS messages received |
Async Queue | ||
com.tibco.cim.async.priority.preload | 4 | Preloads records and record keys when server starts |
Workflow Queue | ||
com.tibco.cim.workflow.priority.event. cancel | 9 | Event cancellation |
com.tibco.cim.workflow.priority. restartmsg | 9 | Restart message (for workflow). Restart messages may be generated in various scenarios a) Suspended workflow is restarted based on event received on queue (integration scenarios) b) When a waiting event is takeout out of QUEUEENTRY and started c) InitiateWorkflow activity restarts a suspended workflow |
com.tibco.cim.workflow.priority. restartbatch | 9 | Restart message (for workflow) for batch processes. Such processes were suspended as the work was split in multiple threads and run in parallel |
com.tibco.cim.workflow.priority. workitem.submit | 9 | Submit of workitem from UI |
com.tibco.cim.workflow.priority. recordops | 9 | Record add/modify/delete from UI |
com.tibco.cim.workflow.priority. recordops.ws | 9 | Record add/modify/delete from Web service |
com.tibco.cim.workflow.priority. dataserviceupdate.ws | 9 | Import metadata through web service |
com.tibco.cim.workflow.priority. workitem.submit.ws | 9 | Submit of workitem from web service |
Copyright © Cloud Software Group, Inc. All rights reserved.