Introduction
There are two ways the ImageMaster Content Services for File Shares get aware of the documents on the file shares:
-
By going through all the documents inside the file share (component called inspector is responsible for this). This behavior is triggered on a schedule defined in operation time inside the configuration.
-
A so called watch feature. The ImageMaster Content Services for File Shares subscribe for notifications to get from the file share server messages on events like new item creation, item renaming, item attributes being changed.
Archived items are replaced by stubs. The stub is a link file containing URL that may be used to get the original document content (the ImageMaster Content Services for File Shares are responsible to process the call to the mentioned URL, to retrieve data from ImageMaster and to provide it to the user. This is done by the Retrieval service).
In an existing ImageMaster environment, it is likely that the required ImageMaster web services have already been integrated into a (potentially customer-specific) delivery file. This file is represented by an EAR file that is ready for upload on an appropriate J2EE application server such as JBoss or WildFly. For further details see the corresponding ImageMaster installation manual [IM ImageMaster].
The service needs the permissions to access the ImageMaster web service and an underlying file share. The customization of rules and mappings is typically done by an administrator via the corresponding section in the ImageMaster AdminClient [UM AdminClient].
For a general ImageMaster overview see the product description [T Product Description]. Additionally, see the latest release notes [T Release Notes] for known defects and usage restrictions that may apply to your specific environment.