Adapter for JDBC 10.3 | webMethods Adapter for JDBC Documentation | webMethods Adapter for JDBC Installation and User’s Documentation | Package Management | Adapter for JDBC in a Clustered Environment | Polling Notification Support in Integration Server Clusters
 
Polling Notification Support in Integration Server Clusters
 
Considerations for Polling Notifications Executing via Scheduled Tasks
Adapter for JDBC enables the coordinated execution of polling notifications within an Integration Server cluster. Adapter for JDBC provides the ability to enable multiple instances of the same polling notification in your cluster, and to coordinate their schedules and execution. This provides enhanced quality of service by allowing configurations for automated failover between notifications and distributed processing of polling notifications.
Important:
Adapter for JDBC supports enabling the same polling notification on multiple Integration Server instances connecting to the same backend database to achieve automated failover, only when the multiple Integration Servers share the same ISInternal database. If you attempt to use the same polling notification on multiple Integration Servers pointing to the same backend database but using separate ISInternal databases, you may encounter abnormal results.
With Integration Server 10.3, Adapter for JDBC uses Integration Server Scheduler to support polling notifications. On enabling a polling notification, a new Integration Server scheduled task is created, which polls the backend resource at the given interval. Do not manually edit or change scheduled tasks. Each polling notification creates an Integration Server scheduled task. When a notification is disabled, the scheduled task in Integration Server is removed.
Important:
All adapter polling notifications must be in a disabled state on all nodes in the Integration Server cluster before you disable the cluster.