Needed for initial set up
There are a few things that need to be configured for thumbnails within Aiimi Insight Engine. This includes where they are stored. Thumbnails are shown next to as many files shown in a results list as possible. Some documents can't have a thumbnail created so a default is applied. If a file does not have a thumbnail Aiimi Insight Engine will create one based of the file and the data within it.
Any changes made to the settings regarding thumbnails will not work retroactively. Enrichment will need to be re-run for any updates to existing data.
You can choose to enable or disable thumbnails with the Enable Thumbnails checkbox.
Choose the Thumbnail Size that is shown on the screen.
Choose between Tiny, Small, Medium or Large.
Use the Quality slider to determine how clear the thumbnail is.
The smaller the size the less someone can see so quality can be sacrificed.
You can choose to show no thumbnail for files modified over a certain number of months ago. To set a modified date range enter the Maximum Modified Age in months.
To show all thumbnails despite modified date leave Maximum Modified Age empty.
If you enter 6, files last modified within 6 months will show a thumbnail.
Set a Max degree of Parallelism to determine the number of thumbnailing process that can run at the same time.
This is capped at the maximum number of logical processors available in your content agent.
Thumbnails can be processed in the content agent when it runs or as an external process. We recommend and default to the InProcess process mode.
If you see issues like runaway memory usage, consistent high CPU usage but no files processed then you should consider changing your Process mode.
The External Process is slower as it runs the thumbnail and document conversion processes separately. When using an external process it can be stopped by setting memory and runtime limits.
When changing your JSON file remember to keep any existing settings and make all the necessary changes so that it is still valid.
Select mode and choose ExternalProcess.
Set limits to automatically stop the external process.
Change the memory limit in GB to suit your needs. By default this is set to 5GB.
Change the RunTime limit in seconds to suit your needs. By default this is set to 60 seconds.
Open your appsettings.json
Update the json to point to the external process.
Add your external process as a contentUtilitesPath.
Configuring the storage for the Content Retrieval enrichment step happens here. The input folder is an area that holds documents and data that needs a thumbnail. Then there are ContentAgent resources available the files in that root folder will have thumbnails created and stored in the output folder.
Select the Storage for the queue of documents that should have thumbnails generated from the Input Storage Configuration dropdown.
Choose between File System Storage, Azure Storage or Google Storage.
Select the storage for the thumbnails from the Output Storage Configuration dropdown.
Choose between File System Storage, Azure Storage or Google Storage.
You can have a different storage configuration for the input and output. Depending on your chosen storage you will need to populate different information.
Enter the root path of the folder within Store Root.
Choose the amount of Reserved Disk Space for the folder.
Enter the reserve amount in bytes.
You may want to reserve disk space for the input and output folders. Input only holds temporary data and is removed once the thumbnail is made.
Check Error on full storage if you want to surface an error.
Enter the Endpoint Suffix for the storage account.
Enter the name of the storage account to crawl within Account Name.
Select the Account Key Type from the dropdown.
Choose the related credential from the Select Credential dropdown list.
Enter the root Azure Container ID for the Azure container.
Enter the Project ID from the Google Cloud Platform.
Enter the Bucket Location from the Google Cloud Platform.
Enter the Bucket Prefix to be added to the beginning of all buckets.
