Exporting Configured Adapter Notifications
You can export notifications from one Integration Server to another Integration Server. You do not need to disable notifications in order to export them. In most cases, the current state of the notifications in the package that you export is retained. However, if you deploy to a different Integration Server and connect to a different database, then you should first disable the notification.
Note:
A given notification can only run on one Integration Server at a time.
After you export or deploy an adapter notification, Software AG recommends reloading the adapter values in the notification template in Designer if all of the following conditions are met:
1. The connection for the notification in the source and target Integration Server connects to the same database.
2. The connection for the notifications is configured with different schemas on the source and target Integration Server.
3. The two schemas have access to each other’s database objects.
Software AG recommends using Basic Notifications in critical environments.
With Insert Notifications, Update Notifications, Delete Notifications, and Ordered Notifications the buffer table and trigger remain in the database. When the Integration Server with the exported notifications starts, each configured notification starts to poll the data from the buffer table.
If you want to export configured notifications in a Disabled state, you need to disable the notifications before you export the package containing them. With Insert Notifications, Update Notifications, Delete Notifications, and Ordered Notifications the buffer table and trigger will be dropped when you disable the notification. When you enable the exported notification, the buffer table and trigger will be created.
When exporting the configured notifications, Software AG recommends that you export them in a Suspended state. The trigger and buffer table are not dropped in the Suspended state.
After exporting the configured notifications, the following scenarios can occur in Adapter for JDBC if the notifications are not exported in a Suspended state:
,
While reloading the package containing exported enabled notifications, or while restarting
Integration Server, if some or all of the database objects of a notification are missing, the adapter throws a warning indicating that the database objects are missing, and then disables that notification.
When enabling an exported disabled notification, if some or all of the database objects for that notification exist, the adapter throws an error indicating that the database objects exist.
When disabling an exported notification, if some of the database objects are missing, the adapter disables the notification but does not delete the existing database objects. The next time you enable the same notification, the adapter throws an error indicating that incomplete database objects exist.
To help you recover from these scenarios, Adapter for JDBC provides the following services:
pub.pollingNotificationUtils:getDatabaseObjectsForNotification to list the existing database objects of a notification.
pub.pollingNotificationUtils:dropDatabaseObjects to delete the existing database objects of a notification.
For information about polling notifications and their states, see
Polling Notifications and States.
For more information about exporting packages, see the webMethods Integration Server Administrator’s Guide for your release.