How To Process Large Batches
Applies to: Ephesoft Transact 4.5.x.x and above (previous versions may require slightly different settings)
Larger Batch Instances may require some additional configuration changes to process without timeouts.
Instructions:
- Change process capacity
- Larger batches should process fewer batches at the same time to avoid resources getting used up.
- In the dcma-workflows.properties, you can change the server.instance.max.process.capacity.
- Larger batches should process fewer batches at the same time to avoid resources getting used up.
- Increase timeout times
- Larger batches may take longer than the default Transact timeout time, causing Transact to restart batches prematurely
- In the application.properties, you can adjust the wait times to stop these timeouts occurring.
- Larger batches may take longer than the default Transact timeout time, causing Transact to restart batches prematurely
# Wait time for GhostScript command in minutes gs.command.wait.time=30 # Wait time for ImageMagik command in minutes imageMagik.command.wait.time=30 # Wait time for Recostar command in minutes recostar.command.wait.time=30 # Wait time for Tesseract command in minutes tesseract.command.wait.time=30 # Wait time for LibTiff command in minutes lib_tiff.command.wait.time=30
-
-
- In the dcma-workflows.properties, you can adjust the activity.restart.time
-
- Alter the Advanced Barcode plugins
- The Advanced Barcode plugins can take a longer time than other plugins.
- In both the Reader and Extraction plugins, find the Barcode Methods, and turn off as many as you’re not using.
- The Advanced Barcode plugins can take a longer time than other plugins.