The JDBC Connection resource describes a JDBC connection. JDBC connections are used with backing store (see TIBCO BusinessEvents Administration) and with database concepts (available in the TIBCO BusinessEvents Data Modeling add-on). This section provides a reference to the fields. For procedures see Adding a Shared Resource.
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 Identifiers (Names).Unlike other resource identifiers, however, shared resource identifiers can have spaces in the name. Specifies the kind of JDBC connection you wish to create. The connection type can be one of the following:
•
•
• The type of connection determines the other configuration fields that appear. 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:com.ibm.db2.jcc.DB2Driver (supported for database concepts only)When you select a driver, the Database URL field is populated with a template for the URL for the driver. 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. 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. 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. Use Shared JNDI Configuration When this field is checked, the JNDI Configuration field appears, allowing you to choose a shared JNDI Configuration resource. This field only appears when the Use Shared JNDI Configuration field is checked. This field allows you to choose a JNDI Configuration shared resource that specifies the JNDI connection information. 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. 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. 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. 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. Note: BusinessEvents attempts to find the class. However, you may need to add the location of the class to the CLASSPATH environment variable in the be-engine.tra file. The URL to use to connect to the database. A template of the URL is supplied for the selected XA DataSource class. You must supply the portions of the URL that are in angle brackets (<>). For example, if you select the tibcosoftwareinc.jdbcx.oracle.OracleDataSource, the following appears in the Database URL field:jdbc:tibcosoftwareinc:oracle://<host>:
<port#>;SID=<db_instancename>You must supply the host, port number, and database instance name in the URL. 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 information about this field. 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 will eventually time out and be 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. See Chapter 15, JDBC Backing Store Configuration in TIBCO BusinessEvents Administration for details.The Test Connection button allows you to test the connection specified in the configuration of this resource. See To Add a Shared Resource for a step you must take to enable the connection to work.
Copyright © TIBCO Software Inc. All Rights Reserved.