SQL Transaction builder inputsAdded by IBM on August 31, 2010 | Version 1 (Original)
|This topic describes the inputs for the SQL Transaction builder.
This topic describes the inputs for the SQL Transaction builder.
Table 1. SQL Transaction builder inputs
|Name||Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.|
|Isolation Level||This input allows you to specify what changes to the database by other users are visible in the transaction you are creating. Basically this tells the database whether or not you want your SQL statements to be aware of the results of other users' database actions that take place outside the context of the current transaction. |
For example, if you are doing a select at the same time someone else is doing an update, you might want to see that person's changes before they commit the changes. Isolation levels are:
Transactions are not supported.Default
Accepts the database's default isolation level configured by the administrator.Read Uncommitted
This transaction will be aware of any uncommitted changes to the database.Read Committed
This transaction will be aware of only explicitly committed changes to the database.Repeatable Read
This transaction will be aware of committed changes. However, if this transaction contains two identical SELECTs, and a commit occurs between these SELECTs that changes one of the rows visible to the first select, then the second SELECT will not see the changes to the row.Serializable
This transaction will not be aware of any changes to the database by other users.
|Transaction Steps||Listing of SQL statements to be executed as a multi-step transaction, including the DataSource associated with each SQL statement. Selectable items include: |
(required) A name for this particular step within the overall transaction being built.Data Source Name
(required) The name of the SQL DataSource builder that will provide a JDBC connection for this step.Statement Name
(required) The name of the SQL Statement builder that will provide the SQL command to be executed in the database.Transform Name
(optional) The name of the SQL Transform to XML builder that is to be used to turn the SQL Statement's result into an XML structure for use by other builders.The SQL Transaction builder allows custom transform methods to be called for a transaction step.
|Transaction Timeout Settings|
|Timeout Period||Minimum time (in seconds) before a transaction is considered to be timed out and a candidate to be automatically committed or rolled back by the builder. Once a transaction times out the builder is free to reclaim the database resources used for the transaction's execution.|
|Timeout Action||In the event of a timeout, this is the action that the builder will force on this transaction. Choices include: |
Make durable any changes to the database performed by this transaction.Rollback
Discard any changes to the database related to this transaction.
|Events, Statistics and Logging Settings|
|Log SQL Warnings||Enable this input to write to the log any SQL warnings generated as a result of executing, committing, or rolling back this transaction.|
|Log Server Stats||Enable this input to generate server statistics related to this builder instance.|
|Fire Execution Events||Enable this input to fire an event when a transaction is executed.|
|Fire Commit Events||Enable this input to fire an event when the results of this transaction are committed to the database.|
|Fire Rollback Events||Enable this input to fire an event when the results of this transaction are rolled back.|
Parent topic: SQL Transaction builder: wpf7