Copyright © Cloud Software Group, Inc. All Rights Reserved

JDBC Connection

Shared Configuration

The JDBC Connection resource describes a JDBC connection. JDBC connections are used when specifying activities from the JDBC palette.

Configuration

The Configuration tab has the following fields.

Field	Global Var?	Description
Name	No	The name to appear as the label for the resource.
Description	No	Short description of the shared resource.
Connection Type	No	Specifies the kind of JDBC connection you want to create. The connection type can be one of the following: • JDBC • JNDI • XA The type of connection determines the other configuration fields that appear.
JDBC Connection Type Configuration Fields
JDBC Driver	Yes	The name of the JDBC driver class. You can select from a list of supported drivers. If you select a supported driver, the Database URL field is populated with a template for the URL of the driver. See Database Drivers for more information about database drivers.
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, if you select the tibcosoftwareinc.jdbc.oracle.OracleDriver, the following appears in the Database URL field: jdbc:tibcosoftwareinc:oracle:// <host>:<port#>:<db_instancename> You must supply the host, port number, and database instance name in the URL.
Maximum Connections	No	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.
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. You can also set this timeout with the Config.JDBC.Connection.SetLoginTimeout custom engine property. The value of the property in the configuration file overrides the value of this field. See TIBCO ActiveMatrix BusinessWorks Administration for more information about setting custom engine properties.
JNDI Connection Type Configuration Fields
Use Shared JNDI Configuration	No	When this field is checked, the JNDI Configuration field appears, allowing you to choose a JNDI Configuration shared configuration resource. When this field is unchecked, the JNDI Context Factory, JNDI Context URL, JNDI User Name, and JNDI Password fields appear.
JNDI Configuration	No	This field only appears when the Use Shared JNDI Configuration field is checked. This field allows you to choose a JNDI Configuration shared configuration object that specifies the JNDI connection information.
JNDI Context Factory	No	This field only appears when the Use Shared JNDI Configuration field is unchecked. 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. When using IBM WebSphere, you should use the JNDI Configuration resource instead of specifying the JNDI configuration on this resource. See IBM WebSphere and JNDI Context Caching for more information. Note: TIBCO ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the Java file supplied by your JNDI service provider to the CLASSPATH environment variable to use JNDI.
JNDI Context URL	Yes	This field only appears when the Use Shared JNDI Configuration field is unchecked. This is 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 unchecked. Specify 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 unchecked. Specify 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.
JNDI DataSource Name	Yes	The JNDI name specified for the DataSource.
XA Connection Type Configuration Fields
XA DataSource Class	No	The XA DataSource class. Note: TIBCO ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the location of the class to the CLASSPATH environment variable.
Database URL	Yes	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.
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 information about this field.
User Name	Yes	User name to use when connecting to the database.
Password	Yes	Password to use when connecting to the database.

Database Drivers

The following drivers are supported, but you must obtain, install, and configure these from the appropriate vendor:

•	oracle.JDBC.driver.OracleDriver (oci)

•	oracle.JDBC.driver.OracleDriver (thin)

•	com.sybase.jdbc2.jdbc.SybDriver

•	com.timesten.jdbc.TimesTenDriver

•	com.ibm.db2.jcc.DB2Driver

•	com.mysql.jdbc.Driver

The following drivers are JDBC 2.0-compliant and should work correctly, but they are not officially supported with BusinessWorks. You must obtain, install, and configure the driver from the appropriate vendor:

•	sun.jdbc.odbc.JdbcOdbcDriver

•	weblogic.jdbc.mssqlserver4.Driver

You can download, install, and use other JDBC drivers, but TIBCO does not guarantee the drivers will function properly with TIBCO ActiveMatrix BusinessWorks. To use an unsupported driver, perform the following:

1.	Download the JDBC driver and copy the required JAR files to a location in the classpath of the TIBCO ActiveMatrix BusinessWorks Engine. For example, you can copy the files to the following location: TIBCO_HOME/tpcl/<version>/jdbc.

2.	In the JDBC Connection resource, choose Select Driver from the drop-down list in the JDBC Driver field and type in the name of the driver class in the text box within that field. Then, type in the correct URL in the Database URL field and specify the other fields in the resource.

See TIBCO ActiveMatrix BusinessWorks Release Notes for more information on the supported and tested versions of databases and database drivers.

Connection Pooling

TIBCO ActiveMatrix BusinessWorks 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.

Activities that use this JDBC Connection resource are given a connection from the pool. Once the maximum number of connections is reached, activities 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. If you want to configure a timeout value for these connections, you can set the Engine.DBConnection.idleTimeout property. See TIBCO ActiveMatrix BusinessWorks Process Design for more information.

If an activity detects a connection in the pool is invalid (for example, the database is restarted), the activity that uses the JDBC connection resource attempts to reestablish the connection.

All activities that are part of the same transaction will use the same connection in the connection pool. The first activity in a transaction attempts to reestablish an invalid connection. If a connection becomes invalid during a transaction, the transaction is rolled back and must be retried, if necessary.

Test Connection Button

The Test Connection button allows you to test that the specified configuration fields result in a valid connection to a database.

Copyright © Cloud Software Group, Inc. All Rights Reserved