Adapter Development Kit 6.5 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Polling Notifications | Cluster Support for Polling Notifications | Configuration Settings | Adapter-Specific Settings
 
Adapter-Specific Settings
Within the configuration directory of the adapter's package, the clusterProperties.cnf provides settings that specify a callback scheme, and place limits on which coordination modes can be applied to notification nodes for the adapter. The clusterProperties.cnf file is an XML file in which settings may be provided globally for the adapter or specifically to a particular notification template. Template-specific settings use the template class name to set the scope of the setting.
The following example includes all of the major constructs of a clusterProperties.cnf file:
<?xml version="1.0"?>
<clusterProps>
<pollingNotifications>
<callbackScheme>1</callbackScheme>
<runtimeModeLimit>distribute</runtimeModeLimit>
<template className="com.wm.adapter.wmarttest.notification.LatchedPollingNot
ification">
<callbackScheme>1</callbackScheme>
<runtimeModeLimit>standby</runtimeModeLimit>
</template>
</pollingNotifications>
<listenerNotifications>
<callbackScheme>1</callbackScheme>
</listenerNotifications>
<listeners>
<runtimeModeLimit>standby</runtimeModeLimit>
</listeners>
</clusterProps>
The outer <clusterProps> wrapper contains the following three elements:
*<pollingNotifications> wraps settings for clustered polling notifications.
*<listenerNotifications> is for future use. Copy wrapper and contents from the example.
*<listeners> is for future use. Copy wrapper and contents from the example.
The <pollingNotifications> wrapper should contain a global <callbackScheme> and a <runtimeModeLimit> setting that provide the adapter's default values. These can be followed by any number of template wrappers, which contain the <callbackScheme> and <runtimeModeLimit> settings specific to each template. Template-specific settings are applied to notification nodes created from the associated template name.
The <callbackScheme> setting controls how callback coordination is performed, while <runtimeModeLimit> constrains the coordination mode setting that can be set for a notification node. Valid values for these settings are included in the following tables.
Values for callbackScheme Setting
When callbackScheme is set to...
The following Coordination Modes are set:
Enable/Disable
Startup/Shutdown
Resume/Suspend
0
No Coordination
No Coordination
No Coordination
1(default)
Coordinated
No Coordination
No Coordination
2
No Coordination
Coordinated
No Coordination
3
Coordinated
Coordinated
No Coordination
4
No Coordination
No Coordination
Coordinated
5
No Coordination
Coordinated
Coordinated
6
Coordinated
No Coordination
Coordinated
7
Coordinated
Coordinated
Coordinated
Values for runtimeModeLimit Setting
runtimeModelLimit Value
Result
disable
Nodes created using this template cannot be coordinated across a cluster. Nodes will be forced to coordination mode "disabled".
standby (default)
Nodes can be coordinated in "standby" mode or coordination may be disabled.
distribute
Nodes can be coordinated in "distributed" or "standby" mode, or coordination may be disabled.
When a polling notification is created or registered on a cluster-aware Integration Server, the Integration Server will look for a clusterProperties.cnf file in the adapter's config directory. If the file contains no entry for the notification's template, a new <template> entry is created using the settings specified globally for all polling notifications. If the file is completely absent or unreadable, the file will be created using the default settings identified above.