JDBC Connection Reference

The JDBC Connection resource describes a JDBC connection. JDBC connections are used with backing stores and with database concepts.

For procedures to add a JDBC shared resource, see Adding a Shared Resource.

For using Secure Sockets Layer protocol for JDBC connection between BusinessEvents and a database server, see Configuring SSL for JDBC Connection.

JDBC Connection Wizard and Configuration Tab

Field Global

Var?

Description
Wizard
File Name No The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder.

See Identifier Naming Requirements.

Unlike other resource identifiers, however, shared resource identifiers can have spaces in the name.

Configuration
Description Yes Short description of the resource.
Connection Type Yes Specifies the kind of JDBC connection you wish to create.

The connection type can be one of the following:

  • JDBC
  • JNDI

    The type of connection determines the other configuration fields that appear.

JDBC Connection Type Configuration Fields
Tip: Using global variables makes the project more portable.
JDBC Driver Yes The name of the JDBC driver class. You can select from a list of drivers or enter a driver manually. Listed drivers are as follows:
  • oracle.jdbc.OracleDriver (thin)
  • com.ibm.db2.jcc.DB2Driver (supported for database concepts only)
  • com.microsoft.sqlserver.jdbc.SQLServerDriver
  • com.mysql.jdbc.Driver

When you select a driver, the Database URL field is populated with a template for the URL for the driver.

Database URL Yes The URL to use to connect to the database. A template of the URL is supplied for the selected JDBC driver. You must supply the portions of the URL that are in angle brackets, for example, the host, port number, and database instance name.

You can configure Single Client Access Name (SCAN) for Oracle database in a cluster with numerous nodes.

For more information on configuring SCAN, see TIBCO BusinessEvents Configuration Guide.

Maximum Connections Yes The maximum number of database connections to allocate. The default maximum is 10. The minimum value that can be specified is 1.

See Connection Pooling for more details, including related settings that override this setting.

User Name Yes User name to use when connecting to the database.
Password Yes Password to use when connecting to the database.
Login Timeout Yes Time (in seconds) to wait for a successful database connection. Only JDBC drivers that support connection timeouts can use this configuration field. If the JDBC driver does not support connection timeouts, the value of this field is ignored. Most JDBC drivers support connection timeouts.
JNDI Connection Type Configuration Fields
JNDI DataSource Name Yes The JNDI name specified for the DataSource.
Use Shared JNDI Configuration No When this field is selected, the JNDI Configuration field is displayed, allowing you to choose a shared JNDI Configuration resource.

When this checkbox is not selected, the following JNDI fields are displayed:

  • JNDI Context Factory
  • JNDI Context URL
  • JNDI User Name
  • JNDI Password
JNDI Configuration No This field only appears when the Use Shared JNDI Configuration field is selected. This field allows you to choose a JNDI Configuration shared resource that specifies the JNDI connection information.
JNDI Context Factory No This field only appears when the Use Shared JNDI Configuration field is not selected.

The initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_
FACTORY). You can choose from the drop down list of supported classes, or you can type in a different InitialContextFactory class name.

JNDI Context URL Yes This field only appears when the Use Shared JNDI Configuration field is not selected.

The URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected.

See your JNDI provider documentation for the syntax of the URL.

JNDI User Name Yes This field only appears when the Use Shared JNDI Configuration field is not selected.

The user name to use when logging into the JNDI server (javax.naming.Context.SECURITY_
PRINCIPAL). If the JNDI provider does not require access control, this field can be empty.

JNDI Password Yes This field only appears when the Use Shared JNDI Configuration field is not selected.

The password for logging into the JNDI server (javax.naming.Context.SECURITY_
CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.

Use SSL Yes Specifies whether you want to use secure sockets layer (SSL) protocol for connection to the database server. This protocol authenticates the server to the client, and optionally authenticates the client to the server.

Select this field to specify SSL parameters using the Configure SSL button (see JDBC SSL Configuration Reference).

Connection Pooling

TIBCO BusinessEvents creates a pool of JDBC connections for every JDBC Connection shared resource that uses the JDBC connection type. The maximum size of this pool is specified by the Maximum Connections configuration field.

Resources such as backing stores and database concepts that use this JDBC Connection resource are given a connection from the pool. Once the maximum number of connections is reached, resources requesting a connection cannot proceed. Once a connection is freed by an activity, the connection is returned to the pool. Connections that are left open eventually times out and closed. These connections can be reopened at a later time, until the maximum number of connections specified in this field is reached.

For backing store connections, you can use additional connection pool properties, which override equivalent settings in the JDBC Connection resource.

Test Connection Button

Using the Test Connection button you can test the connection specified in the configuration of this resource.

See Enabling the Test Connection Feature for a step you must take to enable the connection to work.