Batch Processing Scheduler is used to process batches at high speed. We can set the time and start the scheduler or refresh it. Batch Processing Scheduler is located in Batch Control Board, Integration page detail and Integration Admin Tab.
SKYVVA Batch Processing Schedulers is a type of scheduled job which runs regularly bases on-time setting (ie. every 10 minutes). There are three categories of this Schedulers.
- Integration Scheduler : is a global scheduler process all interfaces on integration, it will skip either Interface group or interface that is running its scheduler.
- Interface group Scheduler: process all interfaces in the group, if the scheduler has been started then all the schedule of the interface in this group will stop automatically.
- Interface Scheduler: it will process a specific interface. It cannot be started if its interface group scheduler has already started.
This table describes the field in the Scheduler view.
| Field | Description |
| Action | The action you can apply for the scheduler |
| Scheduler | The Name of the scheduler. This is the different type of Scheduler |
| Integration or Group | The name of the integration or Integration group ( Our recommendation to not use Integration group anymore) |
| Status | The status of the scheduler (green, red, grey) |
| Comment | Comment to describe some situation e.g. stopped by admin |
| Time interval | The time interval for the scheduler run |
| Job Id | The Job Id |
| Job Name | The job name. The name is concatenated with the Id of the integration group |
| Submitted By | The user who starts the scheduler |
| Submitted | The Date and time when the Scheduler was started |
| Started | The start time |
| Next Scheduler Run | The time when the next run is started |
| Description | Description of the scheduler |
Integration Scheduler #
when you create a new Integration, You will get three kind of scheduler for each Integration.
- BatchProcess
- BatchReprocess
- Altert
BatchProcess scheduler
The BatchProcess scheduler will process attachment residing in the working basket. This is the initial processing of the attachment. First the attachment get created from the messages send from the sender application. The attachment will be kept in the working basket until this scheduler is run to process them.
The processing logic is designed to use the concept of scheduler and worker. The scheduler is the manager and will coordinate and distribute the work package to the worker. The scheduler are scheduled apex job while the worker are implemented as batch apex job. The scheduler call the worker and the worker will get the data package which contain a bundle of attachment from a certain queue and will process it e.g. deserialize attachment and post the record from the attachment into the application database.
BatchReprocess #
The BatchReprocess scheduler will process the batch of data from the working basket which has the status “Failed”. The reprocessing within an integration follow the same logic like the processing within an integration. Especially the parallel processing of queues based on free available batch apex job and the counter stand is the same.
The main advantage to have the reprocess logic separated from the process logic into a separate scheduler is that the reprocess scheduler can run at a different time interval. Normally the processing of data more important because it is the first initial processing. The reprocessing is the second processing of those batches which got failed while the first processing. Therefore you normally don’t urgently need to reprocess batch faster than to process. We recommend to set a slower interval time for the reprocess scheduler than the process scheduler e.g. 2 minutes for the process and 30 minutes for the reprocess scheduler.
Alert Scheduler #
The alert scheduler is used to scheduled alert jobs.This alert tab is used for monitoring Working Basket limit, and EOIO queues’ status. If the status of the EOIO queue(s) is ‘Hold’ or the threshold from the alert tab is smaller than the working basket value, a notify email will be sent to the assigned alert channels.
This is a new Scheduler (Alert Scheduler) to notify user email and send the message to External Email when:
- Number of Working Basket records more than the value in Threshold
- EOIO-Queue turns to status “Hold”
The Scheduler is in Scheduler Tab of Batch Control Board. It’s call Alert. Alert Tab is also created and it is used for monitoring Working Basket limit, and EOIO queue’s status. If the status of the EOIO queue(s) is ‘Hold’ or the threshold from the alert tab is smaller than the working basket value, a notification email will be sent to the assigned alert channels.
To activate this alerting, you have to set up the alert in, “Alert” tab from Batch Control Board. Input the value in Threshold including Email then Save. Start the Scheduler.
For another case to notify the mail
Interface Group Scheduler #
The interface group describe the smallest unit for the queue processing e.g. the element of the queue are data of the interface group. For each interface group a dedicated scheduler will run just to process data from this interface group. Having interface group is important when you have a lot of interfaces in your instance. Interface group divide a huge number of interface into small and smart size logical group. Unless you create an interface group you will miss 2 other scheduler which will be there when creating at least one interface group. For each interface group you will get 2 additional different type of scheduler.
[su_box title=”Note” box_color=”#2a8af0″ title_color=”#000000″] If you are using version 2.38 and then update to version 2.39, there will a duplicated of scheduler AttachmentProcess and AttachmentReprocess[/su_box]
You can configure the Scheduler by type of Interface Group, which are:
- EO
- EOIO
In this screen you can see 2 Interface group and the scheduler for each group. You will get two kind of scheduler for each group.
- BatchProcessPerInterfaceGroup
-
BatchREprocessPerInterfaceGroup
Instead of creating many integration groups we recommend to create interface group within an integration to reduce the number of integrations. Do not misused the concept of integrations to create different logical group of interfaces. For this purpose you can use interface group instead. Take care to create more than one interface group and don’t use or rely on the Skyvva default interface group / queue. If you use the default Skyvva queue you will have only one queue in your integration and therefore all interfaces for example 15 interfaces will run in the same queue. This is not a good performance. Note that with just one queue you will not have a parallelism of queues. Parallelism of queues is only possible with more than one queue.
BatchProcessPerInterfaceGroup
This is the initial processing of the Interface group.
To crate a new interface group open t the tab “Interface Group”. Than click on button ” New Interface Group” to create a interface group. Enter a name for an interface group and select the integration where the interface group belong to. Now enter type of the interface group. You can choose between the value “EO”, and “EOIO”. Next is to select the priority e.g. High, Medium or Low.The push button “Save” to save the interface group. Next step is to insert the interface into the interface group.Click on button “Add Interfaces” to add interfaces to the group. we create an EOIO interface group and therefore we have to specify the sequence number which reflect the order of the interfaces to be kept. Here interface account has to be processed first e.g. 1 and contact as second e.g. 2. Click on button “Save” to save the interface group.
To start scheduler, Go to the scheduler tab and start BatchProcessPerInterfaceGroup.
BatchREprocessPerInterfaceGroup
The BatchREprocessPerInterfaceGroup scheduler will process the batch of data from the working basket which has the status “Failed”. The reprocessing within an integration follow the same logic like the processing within an integration. Especially the parallel processing of queues based on free available batch apex job and the counter stand is the same.
Interface Scheduler #
