To instruct the correct configuration for managing the total number of Batch Instances to be run by a Single Server running Ephesoft.
For more information on how to configure the pickup service on a Multi-Server Cluster click here
Pick up service runs as a scheduler service which keeps a watch on batch_instance table. Every time a batch is ready to be picked i.e. it is not locked by any other process and it’s status is NEW, this service takes a lock on that batch and executes the workflow for that batch. Configuration Parameters (dcma-workflows.properties)
dcma.pickup.cronjob.expression This parameter specifies the schedule for which Pick up service will run. This is specified as a cron job expression. Default value: dcma.pickup.cronjob.expression=0 0/1 * ? * * For this value, pick up service will be invoked every one minute.
server.instance.max.process.capacity This parameter specifies the max number of Running batch instances that a server instance can process. Default value: server.instance. max.process.capacity=5
server.instance.pick.capacity This parameter specifies the max number of batches that a pick up service is executing at one go (i.e. in one iteration). Default value: server.instance.pick.capacity=3
Resume Service Configuration
Resume service, like pick up service, also runs as a scheduler service. This service also keeps an eye on batch_instance table. It picks the batches that are locked by another server instance which is not active now or has gone down (as detected by HeartBeat service). It takes a lock on those batches and resumes the workflow for them.
Coniguration Parameters (dcma-workflows.properties) dcma.resume.cronjob.expression This parameter specifies the schedule for which Resume service will run. This is specified as a cron job expression. Default value:dcma.resume.cronjob.expression=0 0/1 * ? * *
server.instance.resume.capacity This parameter specifies the max number of batches that the resume service is resuming at one go (i.e. in one iteration). Default value: server.instance.resume.capacity=4
Workflow configuration for deploying and sending mails when workflow is gets an error. When the batch instance is getting into error, then a mail is sent via following configuration mention below: Coniguration Parameters (dcma-workflows.properties) workflow.error.from_mail This parameter specifies the mail sent from email id when some error occurs while batch processing. Default value: firstname.lastname@example.org
workflow.deploy This parameter specifies the deploying the changes to database when some changes occur in the workflow. Default value: Workflow.deploy=true
workflow.error.subject This parameter specifies the subject for mail when some error occurs while batch processing Default value: workflow.error.subject=Error in workflow execution!!
workflow.error.to_mail This parameter specifies the mail to when some error occurs while batch processing. Default value: email@example.com
Web Service configuration sends the batch instance in Grid Computing Batch Class using REST web services. Coniguration Parameters (dcma-workflows.properties) wb.folderPath This parameter specifies the folder path to be picked from the ftp location for processing batch in Grid Computing Batch Class. Default value: wb.folderPath=test
wb.hostURL This parameter specifies the host URL for sending the batch instance from one ephesoft instance to another. Default value: wb.hostURL=http://localhost:8080/dcma/rest
dcma.batch.status.cronjob.expression This parameter specifies the schedule for fetching the batch instance status of remote batch instance executing on another ephesoft instance server. This is specified as a cron job expression. Default value: dcma.batch.status.cronjob.expression=0 0/1 * ? * *