2.3. Symbolic Engine Configuration
All features on the Symbolic engine are completely customizable without line of code modification.
When users run operation or script, in reality is generated only a new entry in the database, all needed operations are delegated to a series of threads that have the task to monitor all transactions to be executed and running. Inside configuration file you can decide:
how the job should be awakened to carry out the necessary checks (in milliseconds); in this way you can managed the machine resurces used by Symbolic application.
the number of concurrent operations. This means that you can managed the operations or scripts that can be run simultaneously by users.
job.scripts.runner.time = 5000 Each 5 seconds a job checks if there is enqueued script to run job.operation.runner.time = 5000 Each 5 seconds a job checks if there is enqueued operation to run job.operation.controller.time = 5000 Each 5 seconds a job checks the status of running operations and scripts, to notify the status to user that run operation. job.virtmanager.polling.time = 1800000 Each 30 minutes a job check status and information of defined virtual machines thread.num.max = 100 There may be 100 operations/scripts running at a time