Question:
What happens if the Server Messaging Service is not running?
Answer:
If Server Messaging is not running, the following modules would be affected:
-
Real-time document sync across machines: If a file is uploaded to the document tray on one machine, it will no longer automatically appear on other machines without a manual page refresh.
-
Settings change propagation: Configuration changes made in DocuWare Settings (e.g., adding a new document tray) would not propagate to other components in real time.
BPS background processes — These processes depend on Server Messaging.
Affected processes include:
-
AutoIndex jobs (including File Cabinet Events)
-
Transfer/Sync processes
-
Deletion processes
-
Request processes
Other modules that may be affected:
-
Workflow Designer cache invalidation: Workflow Designer uses the Garnet message bus (Server Messaging) to validate its in-memory settings and token caches. Without Server Messaging, stale configuration data could persist on each node.
-
Document change event notifications: The publish-subscribe pattern that notifies system components when documents are uploaded, modified, or deleted, would stop functioning. This breaks downstream triggers like workflow initiation and necessary AutoIndex changes.
-
Intelligent Indexing: Documents sent to Intelligent Indexing may not be processed immediately, resulting in delayed indexing.
KBA is applicable to On-Premise systems ONLY!