Introduction
There are two ways the ImageMaster Content Services for File Shares get aware of the documents on the file shares:
-
A component called “inspector” goes through all the documents in the file share, triggered by a schedule defined in the configuration.
-
A “watch” feature monitors the file share. The ImageMaster Content Services for File Shares subscribes to notifications from the file share server for events such as new item creation, item renaming, and attribute changes.
Archived items are replaced by stubs. The stub is a link file containing a URL that may be used to get the original document content. The service is 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, the required web services are likely integrated into a custom delivery file. This file, represented by an EAR, is ready for upload to a J2EE application server such as JBoss or WildFly. For further details, see the 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.