...
| Setting | Description | |||||
|---|---|---|---|---|---|---|
UDR Type | Type of UDR to be created and populated. | |||||
Database | Profile name of the database that the agent will connect to and retrieve data from. The list is populated each time the configuration dialog is opened. For further information about database profile setup, see 8.5 Database Profile. Refresh must be selected if changes have been made in the customer database. This will update the presented information in the Source tab.
| |||||
Use Default Database Schema | Select this check box to use the default database schema for the chosen database and user.
| |||||
| Use Prepared Call | Enable this checkbox to allow the Database Collection agent to use prepareCall when using the agent to conduct the SQL operations. When left unchecked, the SQL Forwarding Database Collection agent will use preparedStatement for all its SQL operations. | |||||
Table Name | Name of the working table in the selected Database, in which the data to be collected resides. The list is populated each time a new Database is selected. For further information and an example of a working table, see Working Table in 9.11.3.3 Tables and Stored Procedures.
| |||||
Transaction ID Column | Name of the column in the selected Table, which is utilized for the transaction ID. The list is populated each time a Table Name is selected. The column must be of the data type number, with at least twelve digits. | |||||
Remove | If enabled, this option will remove the collected data rows from the working table. If you select this option, you can also configure the Commit Window Size in the Advanced tab, which is 1000 by default. | |||||
Mark as Collected | If enabled, this option will assign the value | |||||
Run SP | If enabled, this option executes a user defined stored procedure that is responsible for the handling, most often removal, of the collected data.
For further information and an example of such a stored procedure, see After Collection Stored Procedure in 9.11.3.3 Tables and Stored Procedures. | |||||
Ignore | Select to have the collected data remain in the table even after collection. Note that while the data state remains unchanged after collection, the transaction ID value is updated. By keeping the data in the table you can collect it repeatedly while designing and testing a workflow, for example. |
...