|
Attribute
|
Description
|
Range of Values
|
Default Value
|
|
Name
|
This attribute returns the name of this data source.
|
String
|
MyJDBC Tx Data Source
|
|
JNDI Name
|
Sets the JNDI path to where this TxDataSource is bound. Applications that look up the JNDI path will get a javax.sql.DataSource instance that corresponds to this TxDataSource. Note that the old style usage of DriverManager.getConnection() or Driver.Connect() has been deprecated in favor of looking up a datasource to obtain a connection.
|
Valid JNDI name
|
Null
|
|
Pool Name
|
This attribute allows the user to set the name of the connection pool that is associated with this TxDataSource. Calls to getConnection() on this TxDataSource will return a connection from the associated connection pool.
|
Valid connection pool name
|
Null
|
|
Enable Two-Phase Commit
|
This attribute allows the user to enable or disable the two phase commitment of transactions. Enable Two-Phase Commit allows non-XA JDBC drivers to pretend to participate in a the JDBC connection is the only participant in the transaction, but it is asking for trouble to have more than one resource participating in a transaction where one of them (the JDBC driver) is pretending to be an XA resource. There is a possibility of heuristic failures in such a situation. Set Enable Two-PhaseCommit (true) should be used only if you have no option (no decent XA driver available for a particular database, for example).
If this TxDataSource is associated with an XA connection pool, or if there is only one resource participating in the distributed transaction, then this setting is ignored.
|
Boolean
Enabled = Selected
Not Enabled = Not Selected
|
Not Selected
|
|
Row Prefetch Enabled
|
Set to True to enable row prefetching between client and WebLogic Server for each ResultSet. When an external client does JDBC access through WebLogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access. The WebLogic Server will ignore this setting and not use row prefetching when the client and WebLogic Server are in the same JVM.
|
Boolean
Enabled = Selected
Not Enabled = Not Selected
|
Not Selected
|
|
Row Prefetch Size
|
The number of rows that will be prefetched between the client and WebLogic Server for each ResultSet. The optimal value is very dependent on the particulars of the query. Generally, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations.
|
Legal Minimum = 2
Legal Maximum = 65536
|
Default = 48
|
|
Stream Chunk Size
|
Determines the data chunk size for streaming datatypes. Streaming datatypes (for example resulting from a call to getBinarySTream())will be pulled in Stream Chunk Size-sized chunks from the WebLogic Server to the client as needed.
|
Legal Minimun = 1
Legal Maximum= 65,536
Units in bytes.
|
Default = 256
|
