Synchronization
Any imports and updates documents through the synchronization APIs, either directly or through the FileSystem Importer, which itself relies on those APIs. The processing is asynchronous: documents are created and updated as the messages dropped on ActiveMQ, or on SQS in the cloud, are consumed.
Any can also send its own documents to another queue, for instance the one of another Any instance.
This module does not create the queues: they come from the messaging configuration, described in Queues. It designates the ones Any reads and the ones it feeds, and delimits the contents concerned.
Input and output are independent: an installation can just receive, just push, or do both.
Mode
Mode determines the system on the other side:
- Any/Any Cloud: an Any instance in the cloud
- Any/Any On-Premise: another on-premise Any instance
- Any/External repository: an external source
Only the modes whose messaging is configured are offered: the cloud goes through the AWS messaging, the other two through the local messaging. The chosen mode then determines the queues offered on input and output.
Input configuration
The input configuration defines the queues that are listened to in order to import documents. Disabling the input stops reading the messages.
Activated: enables reading the messages of the queue
Input queue name: queue to read, among those declared for the chosen mode
Output configuration
The output configuration defines which documents are sent and on which queue they are exported, with their metadata. Every change on those documents is pushed into the output queue through an Any synchronization message.
Activated: enables sending the messages into the queue
Output queue name: queue to feed, among those declared for the chosen mode
Source name: name assigned to the sync.source metadata of the contents synchronized on the remote repository. That metadata finds the contents that are synchronized.
Set of the contents to synchronize
GQL query or predicates: query that identifies the contents to synchronize.
Changing the query and saving the module automatically triggers the synchronization of the contents and removes those that no longer match the query.
When the output is disabled, the contents already synchronized are preserved on the remote repository. An action then appears, to send a deletion message for those contents.
Relations and packages are handled by this synchronization feature.