The Scheduler service executes tasks at set times or intervals. It is mainly used to execute the Send/Receive function, as well as to execute time rules that are configured in the Rules on documents (EBA DMS client, Adminstration menu).
Time Rules are complex time settings that can alert or notify us or our superiors of specific time periods within the document lifecycle (critical or informative).
Time rules are available for each time field (a field added to a document with time attributes) that is added to a scanned or imported document.
- Port: The default port is 8072. Please note if you have this port already occupied or if you have multiple instances of EBA Application Services installed. In this case each instance must have its own port.
- Idle timeout: The default value is 60 minutes, which means that the service automatically terminates the process after 60 minutes, regardless of the status of the process.
- Server name or address: IP address or name of the server where the EBA application services are running.
This tab is used to configure the execution of tasks at the desired time. You can set an interval or a timer – you can set only one interval with two different tasks, and you can set any timers.
One Time Tasks
A tab where you can set and manage tasks that are run by a single script and run independently of system tasks.
The Scheduler monitor allows us to view the active processes that the scheduler service is running or is currently running. Each process has its own PID, so that it is easier to navigate between the log files.
Similar to the scheduler monitor, this tab gives us a list of processes that have been completed. These records are stored for a maximum of 7 days.
The reports record the activities that have been performed with the Send/Receive function, without technical details.
The reports contain descriptions of the performed tasks, summaries and possible errors in the execution of the send/accept function.
This tab stores information about all executed requests by the scheduler service. All information about the automation process for the service is stored here when the logging level is set to Debug.
All activities related to the service itself are monitored here. If the service is unresponsive or “crashes”, then it will be logged in these logs.
Messaging & Logging
Each service has a list of possible errors with a defined priority, and for each of these you can set the system to send you a notification if an error occurs.
In the Logging section you can configure where the logs are logged and for how many days they are kept.
You can also set the logging level, the default level is Debug.