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.

For more information about database drivers, see 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 oracle.jdbc.driver.OracleDriver (thin),, the following appears in the Database URL field:

jdbc:oracle:thin:@<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.

For more information about this field, see Connection Pooling.

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. For more information about setting custom engine properties, see TIBCO ActiveMatrix BusinessWorks™ Administration.

License Key Yes Enter a valid license key provided for the Progress DataDirect driver. This value is necessary only when you are using Progress DataDirect driver.

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. For more information, see IBM WebSphere and JNDI Context Caching.

Note: 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.

For the syntax of the URL, see your JNDI provider documentation.

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: 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 oracle.jdbc.xa.client.OracleXADataSource, the following appears in the Database URL field:

jdbc:oracle:thin:@<host>:<port#>:<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.

For more information about this field, see Connection Pooling.

User Name

Yes

User name to use when connecting to the database.

Password

Yes

Password to use when connecting to the database.

Migrating existing JDBC applications configured with TIBCO Database Drivers Supplement

Starting from ActiveMatrix BusinessWorks 5.15.1 release, TIBCO® Database Drivers Supplement™ is not supported. Migrate any existing JDBC applications configured using the same to either vendor supplied native drivers or Progress DataDirect drivers procured with a valid license key.

Migrating from TIBCO Database Drivers Supplement configured application to native driver

If the Database URL is not configured using a Global Variable, pass the following property in bwengine.tra and designer.tra to apply the property for all applications deployed in that particular TIBCO_HOME:

java.property.bw.plugin.jdbc.<DBCConnectionResourceName>.dburl= <Database Connection URL>

You can also apply this property specifically for an application by adding this property under <TIBCO_HOME>\tra\domain\<domain_name>\application\<application_name>\<application_name>-Process_Archive.tra.

Warning: Do not redeploy the application as it removes entries from the application’s tra file.

When a Database URL is configured using a Global Variable, you can edit the Global variable value accordingly and redeploy the applications. 

Note: If you are working on a TIBCO_HOME which is upgraded from a previous version to TIBCO ActiveMatrix BusinessWorks 5.15.1, to upgrade applications to the latest TIBCO ActiveMatrix BusinessWorks, use Upgrade option on applications in Admin UI. For more information, see "Upgrading an application" in TIBCO BusinessWorks Administration.
Note: If you are using JCONN3.jar to connect with a Sybase 16 database instance, use the java.property.bw.plugin.jdbc.<JDBCConnectionResourceName>.driver=<Database Driver URL> property additionally.

Migrating from TIBCO Database Drivers Supplement configured application to Progress DataDirect Driver:

Pass the following properties in bwengine.tra and designer.tra to apply the property for all applications deployed in that particular TIBCO_HOME.

  • java.property.bw.plugin.jdbc.<JDBCConnectionResourceName>.driver= <Database Driver URL>

    JDBCConnectionResourceName is the name of JDBC Connection Resource.

  • java.property.bw.plugin.jdbc.<DBCConnectionResourceName>.dburl= <Database Connection URL>

  • java.property.bw.plugin.jdbc.licenseKey=<License Key of Progress DataDirect driver>

You can also apply these properties specifically for an application by adding them under <TIBCO_HOME>\tra\domain\<domain_name>\application\<application_name>\<application_name>-Process_Archive.tra.