Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter Installation and User’s Documentation | Package Management | Oracle Apps Adapter in a Clustered Environment | Configuring Polling Notifications When Integration Server Uses Terracotta | Before Configuring Polling Notifications to Execute via Scheduled Tasks
 
Before Configuring Polling Notifications to Execute via Scheduled Tasks
Before configuring your existing polling notifications to execute via scheduled tasks, ensure that:
*All polling notifications for which you want to use scheduled task functionality are disabled.
Note:
Enabling or disabling the polling notification node on one Integration Server node in the cluster will enable or disable the polling notification node on all Integration Server nodes in the cluster.
For instructions on disabling notifications, see Managing Polling Notifications.
*Each notification is present in all cluster nodes at all times.
*The Overlap function for the polling notifications is disabled.
*Polling notifications names do not exceed 400 characters.
*The value of the Integration Server configuration parameter watt.server.scheduler.threadThrottle should not be lower than the number of total polling notifications and scheduled tasks. By default the value is 75% of the total threads.
*The IS Internal functional alias (specified on the Settings > JDBC Pools screen) is configured with a database.