When GlobalCapture needs to get information about a field, list values, template data or other information during processing, it has to reach out to the GlobalSearch API or GlobalCapture API to get information. This data can be cached in memory to avoid polling of an API. If the Engine encounters a scenario where it is interacting with a field, list value, template it does not have stored in memory it will reach out to the API to get the information and then cache it. Doing this can increase performance and eliminate the back and forth from the Capture Engine to the API.
Step-by-step guide
| Info |
|---|
If your GlobalCapture environment has a lot of templates (50+) you will likely see a big performance improvement from adding Template caching |
Navigate to your GlobalCapture Engine directory, by default this is C:\GetSmart\CaptureServices\GlobalCapture_1.
Open GlobalCapture.exe.config in a text editor of your choice
In the <appSettings> section add the following values:
Code Block <add key="ListTimeout" value="120" ></>add> <add key="EngineAllocationTimeout" value="120" ></>add> <add key="TemplateTimeout" value="120" ></>add> <add key="FieldTimeout" value="720" ></>add> <add key="LicenseTimeout" value="10"></add>
Restart the GlobalCapture_# service, where # is the engine ID.
| Info |
|---|
The timeout values are in minutes, so 720 minutes = 12 hours Available 2.4, GlobalCapture engine config <add key="LicenseTimeout" value="10"></add>. The value is in minutes. They key is used to cache the |
...
| Info |
|---|
If you have multiple Capture Engines this will need to be performed on each one. |
Related articles
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
| Page Properties | ||
|---|---|---|
| ||
|