Adapter Development Kit 9.12 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Using the Sample Adapter | Phase 4: Adding Polling Notifications
 
Phase 4: Adding Polling Notifications
 
Implementing the Polling Notification Template
Revising Code From Phases 1, 2, and 3
Compiling the Phase 4 Implementation
Configuring and Testing the Polling Notification Nodes
Disabling the Phase 4 Implementation
In this phase, the sample provides a polling notification template that you can configure polling notification nodes to poll the Sample Server and determine whether the checks have cleared or bounced, or whether accounts have negative balances. This section describes how to:
*Implement the polling notification template.
*Revise adapter definition, and adapter connection classes.
*Compile the phase 4 implementation.
*Configure two polling notification nodes (one for check clearing/bouncing, the other for negative balances).
Each node generates a document that will be used to contain the affected portion of the Sample Server data, and to inform the Integration Server of the changes.
*Create an Integration Server trigger and a flow service for each polling notification node.
The notifications publish the resulting documents to the triggers. Upon receiving a document generated by the polling notification, the trigger causes the Integration Server to invoke a flow service registered with the trigger to process the document's data. In the Sample Adapter, the flow service invokes the pub.flow:savePipelineToFile service. This service simply saves the contents of the pipeline from the polling notification event to a file. This service is used as a debugging tool. It is provided here simply to demonstrate the use of the notification. In a real adapter, you perform some kind of action with the notification data.
*Schedule and enabling the polling notification nodes.
*Test the polling notification nodes.
*Disable the phase 4 implementation