Overview

This property file is used to configure the workflow i.e. how different services will be executed. This file consists of following four types of service configurations:

  • Pickup Service Configuration.
  • Resume Service Configuration.
  • Workflow Configuration.
  • Web Service Configuration.

Configuration

dcma-workflows.properties

Following is the list of configurable properties:

  • PickUpService Configuration

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 and its status is NEW/READY/LOCKED, this service takes a lock on that batch and triggers the workflow for that batch. Priority of batches to be picked up by pick up service is READY > LOCKED > NEW.

 

[table caption=”Just test table” width=”800″ colwidth=”20|100|50″ colalign=”left|left|center|left|right”]
Configurable property,Type~~of value,Value~~options,Description
dcma.pickup.cronjob.expression,String,”Any valid cron expression.~~Default Value:~~0 0/1 * ? * *~~(For this value, pick up service will be invoked every one minute.)”,This parameter specifies the schedule for which Pick up service will run. This is specified as a cron job expression.
server.instance.max.~~process.capacity,Integer,Any Integer Value.~~Default value: 5,This parameter specifies the max number of RUNNING batch instances that a server instance can process at a given instance of time.
server.instance.pick.capacity,Integer,Any Integer Value.~~Default value: 3,”This parameter specifies the maximum number of batches that a pickup service will pick in 1 round of execution, such that ‘batches picked up <=( max process capacity ‘RUNNING state batches)'”

[/table]

 

  • 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.

 

[table caption=”” width=”800″ colwidth=”20|100|50″ colalign=”left|left|center|left|right”]
Configurable property,Type~~of value,Value~~options,Description
dcma.resume.cronjob.expression,String,”Any valid cron expression.~~Default Value:~~0 0/1 * ? * *~~(For this value, resume service will be invoked every one minute.)”,This parameter specifies the schedule for which resume service will run. This is specified as a cron job expression.
server.instance.resume.capacity,Integer,Any Integer Value.~~Default value: 4,This parameter specifies the max number of batches that a resume service can pick at one go (i.e. in one iteration).

[/table]

 

  • Other Configuration

Workflow configuration for deploying and sending mails when an error occurs in the workflow. When a batch instance goes into error, then a mail is sent via following configuration mentioned below:

 

[table caption=”” width=”800″ colwidth=”20|100|50″ colalign=”left|left|center|left|right”]
Configurable property,Type~~of value,Value~~options,Description
workflow.error.from_mail,String,Any valid email id.~~Default Value: enterprise.support@ephesoft.com,”This parameter specifies the e-mail id from which the mail should be sent, when some error occurs during batch processing.”
workflow.deploy,String,True~~False~~Default Value=true,”This parameter re-deploys all the available workflows in the system. Should be set only once during the new installations or upgrades.”
workflow.error.subject,String,Valid e-mail subject.~~Default Value: Error in workflow execution!!,This parameter specifies the subject for mail to be sent when some error occurs during batch processing.
workflow.error.to_mail,String,Any valid email id.~~Default Value:~~ enterprise.support@ephesoft.com,This parameter specifies the e-mail id to which the mail should be sent when some error occurs while batch processing.
newWorkflows.basePath,String,”Valid path of directory.~~Default Value:~~{Application}\\SharedFolders/workflows”,This parameter specifies the path where all jpdl(s) are placed when a new workflow or plugin is deployed.
[/table]

 

  • WebService Configuration

These configurations should only be set in case of configuring Grid Computing workflow.

 

[table caption=”” width=”800″ colwidth=”20|100|50″ colalign=”left|left|center|left|right”]
Configurable property,Type~~of value,Value~~options,Description
wb.folderPath,String,Any valid path of ftp folder.~~Default Value:~~test,This parameter specifies the folder path to be picked from the ftp location for processing batch in Grid Computing Batch Class.
wb.hostURL,String,”Valid URL.~~Default value: ~~http://localhost:8080/dcma/rest “,This parameter specifies the host URL for sending the batch instance from one Ephesoft instance to another.
dcma.batch.status.cronjob.expression,String,Any Integer Value.~~Default value: 0 0/1 * ? * * ,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.
[/table]

 

Dependency

For e-mail on error functionality, it depends on the mail configuration done in “mail.properties” property file.