Database Connection Pools
Database connections allow database servers and software to interact with each other in an efficient manner. Of course, this statement still holds true in TORO Integrate's environment.
Using registered database connection pools, services will be able communicate with your databases and perform operations against them. You're also free to remove and update existing pools, as well as enable or disable them.
More about SQL services...
TORO Integrate uses JDBC drivers to connect to certain databases. The table below describes which drivers are available in Java and should be compatible with TORO Integrate:
|Driver||Name||Built-in Driver||XA Support|
||Microsoft SQL Server (JTurbo Driver)||No||Emulated|
||IBM DB2 (jcc4)||No||Natively|
||Microsoft SQL Server (Sprinta Driver)||No||Emulated|
||Informix Dynamic Server||No||Natively|
||Microsoft SQL Server||Yes||Natively|
||PointBase Embedded Server||No||Emulated|
||Sybase (jConnect 4.2 and earlier)||No||Emulated|
||Sybase (jConnect 5.2)||No||Emulated|
||Hypersonic SQL (v1.2 and earlier)||No||Emulated|
||InstantDB (v3.13 and earlier)||No||Emulated|
||jTDS (Sybase), jTDS (SQL Server)||Yes||Natively|
||Oracle OCI 8, Oracle OCI 9+, Oracle Thin||No||Natively|
||InstantDB (v3.14 and later)||No||Natively|
||MySQL (mm.MySQL Driver)||No||Emulated|
||Hypersonic SQL (v1.3 and later)||No||Emulated|
||Hypersonic SQL (v2.0+ Remote), Hypersonic SQL (v2.0+ File)||Yes||Natively|
||PostgreSQL (v7.0 and later)||Yes||Natively on PostgreSQL 8 only|
||PostgreSQL (v6.5 and earlier)||No||Emulated|
In addition to the drivers above, TORO Integrate also supports the installation of other database drivers. For more
information, please read about Installing Additional Database Drivers. To use XA
transactions, the JDBC driver must implement
Check your license!
The availability of database drivers will depend on the type of license you have installed.
The properties below are used to described database connections. TORO Integrate, which uses Bitronix underneath, will use these configuration fields when connecting to the target database. You can learn more about these properties in Bitronix's JDBC Configuration Pools page.
|Field Name||Required||Default Value||Description|
||Name of the database connection.|
||Whether or not to enable XA transactions.|
||The JDBC driver for the database you are connecting to.|
||The URL of the JDBC database you are connecting to.|
||Username to use when connecting to the database.|
||Password to use when connecting to the database.|
||Controls how many connections are filled into the pool when the pool is empty but the
||Controls how long (in seconds) the pool waits between attempts to create new connections.|
||Controls how long (in seconds) to wait for a pool connection request to succeed before being aborted (and throwing an exception).|
|Allow Local Transactions||false||
||Whether or not you want to be able to run SQL statements outside of XA transactions scope.|
|Apply XA Transaction Timeout||false||
||Whether or not the transaction timeout will be passed to the resource via
|Enlist to XA Automatically||false||
||Controls whether connections from the
|Defer Connection Release||false||
||Set this parameter to
|Enable JDBC4 Connection Test||false||
||If your JDBC driver supports JDBC4, this method of testing the connection is likely much more efficient than using the
|Ignore Recovery Failures||false||
||Determines whether recovery errors should be ignored or not. This is useful in development environments.|
|Maximum Idle Time||false||
||When the pool is above the
||Sets the default isolation level. All of the four standard values (
|Minimum Pool Size||false||
||The minimum number of active connections the pool will try to keep.|
|Maximum Pool Size||false||
||The maximum number of active connections allowed in the pool.|
|Prepared Statements Cache Size||false||
||Controls how many prepared statements are cached (per connection) by Bitronix.|
|Share Transaction Connections||false||
||Determines whether or not connections share the same thread context.|
||In contrast with
|Two-Phase Commit Order Position||false||
||Controls the position of this resource during the 2PC protocol execution; used to guarantee the order of commits.|
||Required for crash recovery; uses
|Use Transaction Manager Join||false||
||Set this parameter to
A database connection's status indicates the current state of the database connection. It is manually set by starting or stopping a database connection. Certain actions would only be available on certain states; for example, you may configure the properties of a database connection only if it stopped.
The following are the different possible connection statuses:
Indicates that there is an established connection between TORO Integrate and the database. Connectivity is required if any of your integrations need to use the database. A database connection with this status is shown with a green visual indicator in the UI.
Indicates that there is no established connection between TORO Integrate and the database. A database connection with this status is shown with a red visual indicator in the UI.
Databases, as Seen in the User Interface
To view the existing database connection pools of your instance, open the Coder Navigator view, navigate to your instance's entry, and under your entry, expand the Databases section.
To perform an action on a database connection pool in Coder, right click its entry and select from the list of actions in the context menu that will appear. Depending on the state of your pool, some actions may or may not be executable.
Meanwhile, in the Server Admin UI, you typically would have to select the connections and click on the buttons at the top of the list of database connection pools in order to perform an action.