Step | Description |
1 | A Stored Procedure Notification uses a stored procedure you created in the database to monitor an operation that happens to a database table, such as an insert, update, or delete operation. When the Stored Procedure Notification calls the stored procedure, it stores any output in the notification's publishable documents. |
2 | The notification gets a connection from the service's connection pool. Adapter connections contain connection information for the database, including JDBC driver parameters. |
3 | The notification uses the JDBC driver to connect to the database. You created and enabled the adapter connection earlier using Integration Server Administrator. |
4 | Integration Server calls the stored procedure. |
5 | The notification retrieves each row of data from the stored procedure. |
6 | Each row of data is published using the notification's publishable document. Depending on the stored procedure, the Stored Procedure Notification's publishable documents can contain any of the following: ![]() ![]() ![]() Note: When using the result set that contains nested cursors, the performance of Adapter for JDBC could degrade. Since the nested cursors are recursively processed, Adapter for JDBC may also return data that may not be required. For more details about the Integration Server publishable documents, see the Publish-Subscribe Developer’s Guide for your release. |
7 | Using an Integration Server trigger you configured to use the notification's publishable document, a flow or Java service on Integration Server is invoked to react to the data changes contained in the publishable document. |