For this task... | Use these tools... |
1. To ensure that the same data is not published multiple times, design and test your stored procedure so that whenever the stored procedure is invoked, you are assured that it provides the correct data. | User-dependent |
2. Create an adapter connection. For details, see
Overview of Adapter Connections. | Integration Server Administrator |
3. Configure the notification and specify the:  Adapter connectionStored procedurePublishable document to contain the data. There is a single publishable document used for all events associated with the notification.For more details about the Integration Server publishable documents, see the Publish-Subscribe Developer’s Guide for your release. Any output data fields to be contained in the publishable documentFor instructions for configuring this type of notification, see
Configuring StoredProcedureNotifications. | Designer |
4. If you plan to use an Integration Server flow or Java service, design it to react to the data changes contained in the notification's publishable document. Create the Integration Server trigger to use the notification's publishable document. For details, see the webMethods Service Development Help for your release. | Designer |
5. Schedule and enable the adapter notification. When you enable the notification, the Integration Server Scheduler invokes the notification and continues to do so periodically, based on the polling schedule parameters you created earlier. For instructions for scheduling and enabling notifications, see
Managing Polling Notifications. | Integration Server Administrator |
6. Manage the notification. For details, see
Overview of Package Management,
Overview of Adapter Notifications, and
Overview of Logging and Exception Handling. | Designer and Integration Server Administrator |