JDBC Adapter Properties
The JDBC adapter properties form is comprised of common properties and properties specific to the adapter.
Common properties are located at the top of the form. These fields define the attributes associated with the LDAP entry. See
Common Properties and Actions for information about properties not listed here, as well as instructions on using the form and importing and exporting LDAP entries.
In addition to
common properties, the following properties are available to configure the JDBC adapter:
Database Driver Class
drivers
The name of the JDBC driver class. This is specific to the database to which the adapter connects. For example, oracle.jdbc.driver.OracleDriver is the driver class for the Oracle Thin Driver. For more information, consult your driver manual.
Database Supports Auto Commit
autoCommitSupported
Identifies whether the underlying database supports the auto-commit facility. Specify true or false.
|
If Database Supports Auto Commit is set to false and you are using an Oracle database type, the property would be reset to true internally by the software. However, for other database types, it is your responsibility to provide valid and consistent values for Database Supports Auto Commit and Use Database Auto Commit.
|
Database Type
databaseType
The type of database to which the adapter connects. Select between Oracle or Non-Oracle.
Database URL
url
The JDBC URL used to establish the connection. For example, the URL for an Oracle Thin Driver could be in the following format:
jdbc:oracle:thin:@hostname:1521:databaseName
|
If you are using Oracle with Single Client Access Name (SCAN), the URL would be in the following format:
jdbc:oracle:thin:@hostname:1521/databaseName
|
Database User
dbuser
The default user who can connect to the database.
Maximum Cache Size
maxCacheSize
The maximum number of connections to cache. The default value is 10. Connection pooling is always active.
Maximum Context Age
maxContextAge
The maximum time, in seconds, a connection stays active if not used. The default is 60.
Maximum Query Size
maxQuerySize
The maximum number of rows returned from a database query. The default value is 2000. The JDBC drivers silently drop anything beyond the maximum.
Maximum Thread Count
socketAccess.maxThreadCount
The maximum number of concurrent threads used by the JDBC adapter. The default value is 10. Setting this value higher allows more concurrent connections, but also requires more resources (memory and CPU cycles).
Password
passwd
The default password to use when making the connection to the database.
Result Set Scrolling Capability
resultSetScrollingCapability
The scrolling capability for result sets that are generated when executing SQL queries.
◦ Default
◦ TYPE_FORWARD_ONLY—The cursor can move in the forward direction only, thereby rendering the result sets unscrollable. For most databases, such a setting is redundant since the default behavior itself provides for result sets that are unscrollable.
Secret
secret.text
A string used to sign and validate requests sent to the adapter.
Secret 2
secret.text2
Another string used to sign and validate requests sent to the adapter. This property generates a more comprehensive request signature, and can be used instead of or in addition to the Secret property.
Secret Algorithm
secret.algorithm
The algorithm used to encrypt secrets. Valid values for this property are SHA-1 and MD5.
Use Database Auto Commit
autoCommit
Specifies whether the auto-commit facility provided by the underlying database should be used. Select true or false.
◦ The Database Supports Auto Commit property must be set to true before the auto-commit facility is used.
◦ If Database Supports Auto Commit is false, then the value you enter here is disregarded. However, the changes caused by the execution of SQL statements would be explicitly committed.
|
If Database Supports Auto Commit is set to false and you are using an Oracle database type, the property would be reset to true internally by the software. However, for other database types, it is your responsibility to provide valid and consistent values for Database Supports Auto Commit and Use Database Auto Commit.
|
Dynamic Properties Configuration
Configuration information for a service or adapter can be updated while the service or adapter is running, allowing you to update properties without requiring a restart.
The Time To Live property specifies the time that elapses, in minutes, before the properties for a service or adapter are automatically reloaded. Properties are only automatically reloaded if they are being accessed. By default, the properties do not expire.
Additional Properties
If a property is not defined on the form, you can add it in the Additional Properties field. When adding additional properties, the property name format includes the name of the adapter entry (the service name) followed by the property name. For example:
<service_name>.dbuser
In the appropriate fields, specify the property used by the service or adapter and the value of that property. Click Add next to the new property name to open a text box in which you can modify the property value.
If the value becomes too long to view in its entirety, an Edit action appears. Click Edit to open a new browser window with a larger text area.