Field | Description/Action |
Connection alias name | The name of the JMS connection alias configured on Integration Server. If the connection alias is a Broker Cluster configured with Multisend Guaranteed policy, you must add the watt property watt.art.notification.jmsSend.usePublicService and set it to true. Note: Adapter Runtime does not support LOCAL_TRANSACTION and XA_TRANSACTION type JMS connection alias. |
Destination name | The name of the destination from which you want the JMS trigger to receive messages. |
Destination type | Whether the destination is a Queue (default) or a Topic. |
Field | Description/Action |
Base Name | The base name used to generate the Resource Name created by Adapter for JDBC. Note: For OS/390 DB2 7.2, the Base Name you create below must be no more than five characters because triggers on OS/390 name cannot be more than eight characters. |
Publish Locally | Specifies whether to publish the notification's publishable document to the local Integration Server. By default, this option is not selected, that is, if the Broker is configured to Integration Server, the publishable document is published to the Broker; otherwise the publishable document is published to the local Integration Server. Selecting the Publish Locally option reduces performance problems, if Integration Server is connecting to a remotely located Broker that is in turn triggering a service on the local Integration Server. |
Resource Type | Types are buffer table, trigger, and sequence. The base name and resource type determine the following Resource Name. |
Resource Name | To ensure uniqueness, the resource name combines the following elements. You cannot edit this name. ![]() ![]() ![]() |
File Record Format | The format of the file record. Optional field used by DB2 for AS/400 V4R5 only. |
Database Name | The name of the database where the buffer tables will be created. Optional field used by DB2 for OS/390 only. |
Table Space Name | The table space where the buffer tables will be created. Optional field used by DB2 for OS/390 only. |
Field | Description/Action |
Table Alias | The table alias is automatically assigned when you select more than one table in the Table Name field. The default is t1. |
Table Name | Select a table name. The default for the associated catalog name is current catalog. The default for the associated schema name is current schema. The table name must not contain a period. If the table name does contain a period, Designer will throw an error. Note: Informix databases do not allow you to specify a catalog and database name because you can only access the current catalog. |
Type | The table type displays automatically based on the table you select. |
Field | Description/Action |
Expression | The column name or SQL expression. |
Column Type | The column data type defined in the database table. |
JDBC Type | The JDBC type of the corresponding Output Field. |
Output Field Type | The data type of the output field. Adapter for JDBC automatically converts database-specific types to Java data types. For a list of JDBC type to Java type mappings, see
JDBC Data Type to Java Data Type
Mappings. |
Output Field | The name of the field containing the output from the SELECT operation. An output field name displays when you select an expression. You can also modify the output field names as required. |
Maximum Row | Specifies the number of rows to be retrieved from the buffer table. This field is useful when you are working with a large number of records and you want to limit the number of documents sent each time the notification polls. Use a value of 0 to indicate no limit on the number of rows retrieved. |
Query Time Out | Specify the query time out value in seconds. This value is the amount of time Adapter for JDBC waits for the notification to execute before stopping the SQL operation. The default value is -1. Use the default value to have the notification use the value indicated on the watt.adapter.JDBC.QueryTimeout property as the time out. If you specify a value equal to 0, or if the watt.adapter.JDBC.QueryTimeout property is not set, the notification executes without a time out. If you specify a value greater than 0, the notification executes with the specified value as the time out. Note: -1 is the only permissible negative value for this field. For more information about the watt.adapter.JDBC.QueryTimeout property, see
Forcing a Timeout During Long-Running SQL
Operations in Services and Notifications. |