JDBC Call Procedure

Activity

The JDBC Call Procedure activity calls a database procedure using the specified JDBC connection.

If this activity is not part of a transaction group, the SQL statement is committed after the activity completes. If this activity is part of a transaction group, the SQL statement is committed or rolled back with the other JDBC activities in the group at the end of the transaction. For more information about creating groups for transactions, see TIBCO ActiveMatrix BusinessWorks™ Process Design.

If you want to override the default behavior of transaction groups for certain JDBC activities in a transaction group, you can check the Override Transaction Behavior field on the Advanced tab. This specifies that the activity is outside of the transaction and the SQL statement is committed when the activity completes, even if the activity is in a transaction group.

The Refresh button on this activity allows you to synchronize the activity with the contents of the database. This is useful if you make a change to the database while you are editing a process definition containing this activity in ActiveMatrix BusinessWorks.

Note: When using the jConn or Data Direct 3.3 driver and connecting to a Sybase database, stored procedures that are supposed to return multiple result sets do not return any data. To avoid this problem, you can either use the sun.jdbc.odbc.JdbcOdbcDriver instead or you can add set nocount on to your stored procedure definition.