Scheduler service implementation in IBM App Connect.
Here in this blog, we are going to learn about Scheduler service implementation in IBM App Connect.
The Scheduler node is the latest addition to IBM App Connect Enterprise Version 12.0.9.0. Its primary advantage lies in reducing the amount of ESQL code in the compute node to start the Timeout Control node in the IBM App Connect Enterprise. This reduction is possible because we can configure the number of hits required for the application within the settings of the Scheduler node.
One significant benefit of the Scheduler node is that it doesn’t require external dependencies in IBM App Connect Enterprise. Moreover, it offers support for seconds, minutes, hours, day, date, month and year providing flexibility in scheduling.
There are two features in this node
- We can run the flow in the repeat interval that means we can run the flow for every second, every minute, every hour, as well as on specific days at particular times by enabling repeat interval present in the scheduler control in the Scheduler Node
- We can run the flow in the calendar that means we can run the flow on specific month, Date and specific times by enabling calendar present in the scheduler control in the Scheduler Node
In this flow we selected the calendar and we configured flow to run for every year once on 11th SEP 12:30 then deployed in to server and the flow will start only on the SEP 11th on 12:30 only
Now we can see the file which contains data and that file comes when the application is stated it will generate the file
It’s important to note the key differences between the Scheduler node in IBM App Connect Enterprise Version 12.0.9.0 and the Timeout Notification node in other versions:
- The Scheduler node supports intervals of seconds, minutes, and hours, whereas the Timeout Notification node supports only seconds.
- The Scheduler node supports day filtering, while the Timeout Notification node does not.
- Calendar support is available for the Scheduler node, whereas it is not supported by the Timeout Notification node.
- The Scheduler node offers time zone support, which the Timeout Notification node lacks.
- Finally, the Scheduler node supports running on flow start, a feature not supported by the Timeout Notification node.
