Description

The description of the database. 

A valid string. The configured default is JDBC XA Datasource.

ClassName

Specifies the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource or XADataSource interface. Change as needed for your driver.

A valid class name. 

For example: 

com.attunity.jdbc.NvXADataSource 

ClassNamefor 

OtherInterfaces 

For components that do not use ConnectionPoolDataSource, use this entry to enter the name of the driver class. This class will not be used by the adapter.

A valid class name. 

ServerName 

This setting specifies the host name of the external database server. 

Any valid string. 

PortNumber

Specifies the I/O port number on which the server is listening for connection requests. 

A valid port number. 

DatabaseName

Specifies the name of the database instance. 

Any valid string. 

User

Specifies the user name the adapter uses to connect to the database. 

Any valid string. 

Password

Specifies the password used to access the database. 

Any valid string. 

DriverProperties

The DataSource implementation may need to execute additional methods to assure a successful run. The additional methods will need to be identified in the Driver Properties. You must ensure that the driver is installed on both the app server machine and Java CAPS IDE. 

Set the driver properties according to driver vendor’s instruction. For example: 

setDefTdpName#DBSQL## 

setWorkspace#Navigator## 

Delimiter

This is the delimiter character to be used in the DriverProperties prompt. 

The default is #.

DataSource 

name 

Specifies the name of the XADataSource implementation, to which the DataSource object delegates behind the scenes when there is connection pooling or distributed transaction management being done.

The name of the XADataSource implementation. This property is Optional. In most cases, leave this box empty.

MinPoolSize

Specifies the maximum number of physical connections the pool should keep available at all times. 0 (zero) indicates that there is no maximum. 

The pool size you set depends on the transaction volume and response time of the application. If the pool size is too big, you may end up with too many connections with the database. 

A valid numeric value. The default is 0.

MaxPoolSize

Specifies the maximum number of physical connections the pool should keep available at all times. 0 (zero) indicates that there is no maximum. 

If the pool size is too big, you may end up with too many connections with the database. The pool size depends on the transaction volume and response time. 

A valid numeric value. The default is 10.

MaxIdleTime

Specifies the maximum number of seconds that a physical connection may remain unused before it is closed. 0 (zero) indicates that there is no limit. 

A valid numeric value. The default is 0.