Adding a DBC Configuration

The Database Connection Configurations (DBC) page lists existing configurations. Click the pen icon to edit any configuration.

  1. Click Add New.
  2. Specify this information.
    Name
    Specify the name of the database connection.
    Driver
    Specify the JDBC driver in use for the database connection.
    JDBC URL
    Specify the connection string for the database connection.
    Schema
    Optionally, specify the database connection schema.
    Username
    Specify the database connection user name.
    Password
    Specify the database connection password.
    Keys
    Optionally, map the DBC Configuration to one or more keys. These can be used for tenant mapping.
    Pool Settings
    Click to expand and optional change how the database pooling is configured.
    • Min idle connections: The minimum number of connections that can remain idle in the pool, without extra ones being created, or zero to create none.
    • Max idle connections: The maximum number of connections that can remain idle in the pool, without extra ones being released, or negative for no limit.
    • Max total connections: The maximum number of active connections that can be allocated from this pool at the same time, or negative for no limit.
    • Max wait millis: The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception, or -1 to wait indefinitely.
    • Time between evictions runs millis: The number of milliseconds to sleep between runs of the idle object evictor thread. When non-positive, no idle object evictor thread will be run.
    • Num tests per eviction run: The number of objects to examine during each run of the idle object evictor thread (if any).
    • Min evictable idle time millis: The minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any).
    • Soft min evictable idle time millis: The minimum amount of time a connection may sit idle in the pool before it is eligible for eviction by the idle connection evictor, with the extra condition that at least 'minIdle' connections remain in the pool. When minEvictableIdleTimeMillis is set to a positive value, minEvictableIdleTimeMillis is examined first by the idle connection evictor. For examle, when idle connections are visited by the evictor, idle time is first compared against minEvictableIdleTimeMillis (without considering the number of idle connections in the pool) and then against softMinEvictableIdleTimeMillis, including the minIdle constraint.
    • Test on borrow: The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and we will attempt to borrow another.
    • Test on create: The indication of whether objects will be validated after creation. If the object fails to validate, the borrow attempt that triggered the object creation will fail.
    • Test on return: The indication of whether objects will be validated before being returned to the pool.
    • Test while idle: The indication of whether objects will be validated by the idle object evictor (if any). If an object fails to validate, it will be dropped from the pool.
    Note: There are Grid counters for DBC pooling. These can be viewed for each node on the node page.