Persistent Batch Jobs

Questions
1

Currently, every time we redeploy our production environment via a GitHub actions workflow, our established batch process jobs under the servoy admin page gets reset and has to be manually re-established. Just wondering if there is a way to keep them persistent across deployments

1 Like
2

Hi,

You need to modify the servoy.properties included in your distribution.

line below will be there

BatchManager.numberOfBatchClients=1. // Number of batch jobs

lines below will need adding

batchProcess.0.args=my Arg

batchProcess.0.disabled=false

batchProcess.0.password= //password

batchProcess.0.solutionName=batch_processors. // your solution name

batchProcess.0.userName=batchprocessor. // user for batch jobs

When you have added back into your production server, all the entries will be in the servoy.properties on the production server. You can copy them from there.

We have multiple customers with batch jobs and have a servoy.properties for all of them. When we build a war file we just select the correct .properties file for them.

Richard

3

Essentially what Richard said above. All that comes from the servoy.properties file. I suggest setting it up on your local developer and exiting Servoy (properties file is written to disk when Servoy exits). Then open up the servoy.properties file and copy the BatchManager.numberOfBatchClients and batchProcess.* lines into the property file in github that you’re using with your deployment.