About Adapter Notifications and Publishable Document Types
Adapter notifications determine whether an event has occurred on the adapter's resource and then sends the notification data to Integration Server in the form of a published document. For example, if you are using the JDBC Adapter and a change occurs in a database table that an adapter notification is monitoring, the adapter notification publishes a document containing data from the event and sends it to Integration Server.
There are two types of adapter notifications:
Polling notifications, which poll the resource for events that occur on the resource.
Listener notifications, which work with listeners to detect and process events that occur on the adapter resource.
Each adapter notification has an associated publishable document type
. When you create an adapter notification in
Designer,
Integration Server automatically generates a corresponding publishable document type.
Designer assigns the publishable document type the same name as the adapter notification, but appends PublishDocument to the name. You can use the adapter notification publishable document type in triggers and flow services just as you would any other publishable document type.
The adapter notification publishable document type is directly tied to its associated adapter notification. Integration Server automatically propagates the changes from the adapter notification to the publishable document type. That is, when working in Package Navigator view, Designer treats an adapter notification and its publishable document type as a single unit. If you perform an action on the adapter notification, Designer performs the same action on the publishable document type. For example, if you rename the adapter notification, Designer automatically renames the publishable document type. If you move, cut, copy, or paste the adapter notification Designer moves, cuts, copies, or pastes the publishable document type.
The Connection alias name property for the adapter notification publishable document type will initially have the default messaging connection alias that is configured in Integration Server. This means that the default messaging connection alias will be used to publish and receive instances of the adapter notification publishable document type. Any changes to the Connection alias name property of the adapter notification publishable document type will be propagated to its associated adapter notification.
For information about how to create and modify adapter notifications, see the appropriate adapter user’s guide.