Migrating existing JDBC applications configured with Progress DataDirect Drivers

Starting from TIBCO Business Studio for BusinessWorks 2.9.0 release, the JDBC Progress DataDirect Drivers are not supported directly.

Note:
  • Starting from TIBCO Business Studio for BusinessWorks 2.9.0, the Oracle (ojdbc8.jar) jar files are going to be shipped as out of box. However, you can also install and use the jars having different versions using the existing bwinstall <db_name>-driver command if you don't want to use the shipped jar version. Also, at runtime ensure to select the bundled jar provided or installed so applications can run with the installed jars.
  • TIBCO will no longer continue to ship the following jar files present at TIBCO -> <BW_Home> -> config -> design -> thirdparty location:

    • TIdb2

    • TIinformix

    • TImysql

    • TIoracle

    • TIpostgresql

    • TIsqlserver

Migrating from Progress DataDirect Driver configured applications to Native Driver

In TIBCO Business Studio for BusinessWorks:

In TIBCO Cloud Integration pass the Database URL in the engine variable section in the following format:

bw.application.jdbc.db_name.url=<Database Connection URL>

For example, for PostgreSQL database, use the following format: bw.application.jdbc.postgres.url=jdbc:postgresql://localhost:5432/postgres

For more information refer Configuring App Variables.

Note: If the Database Driver and Database URL fields are hard-coded with the Progess DataDirect driver details, then after importing the project to TIBCO Business Studio for BusinessWorks 2.9.0, the Database Driver field is blank and the Database URL field is populated as-is with the older URL details.

Migrating from Progress DataDirect Driver configured applications to Custom Drivers (Bring Your Own License)

After importing the project to TIBCO Business Studio for BusinessWorks 2.9.0, if you want to continue using the Progress DataDirect Drivers then you need to create a custom driver class.

  1. Create the runtime bundle just like creating a regular custom JDBC bundle. While creating this bundle provide the valid license key. To create driver.zip bundle refer Using Custom Drivers.

  2. Supplement the driver.zip on TIBCO Cloud Integration refer Supplement.

  3. Edit the manifest.json file of the tibco cloud applcation EAR and add below entry and save manifest.json

    "volumesFrom" : [

    "bwplugin/bw.customdriver"

    ]

  4. Push the application EAR and manifest.json file updated according to the above step to TIBCO Cloud Integration and add below engine variables. for more information refer Configuring App Variables.

    bw.application.dd.jdbc.db_name.driver=db_drivername

    bw.application.dd.jdbc.db_name.url="db_url"

    For example, bw.application.dd.jdbc.postgres.driver= tibcosoftwareinc.jdbc.postgresql.PostgreSQLDriver
    bw.application.dd.jdbc.postgres.url=”jdbc:tibcosoftwareinc:postgresql://localhost:5432;DatabaseName=postgres”

 

Passing Multiple Database URLs

While migrating from Progress DataDirect to Native Driver if there are multiple instances of the same database with different versions, then pass the Database URL in the VM argument in the following format separated by a hash (“#”)

-Dbw.application.jdbc.db_name.url=<Database Connection URL1>#<Database Connection URL2>

 

While migrating from Progress DataDirect to Progress DataDirect using the custom jar approach (Bring Your Own License), if there are multiple instances of the same database with different versions, then pass both the Database URL and the Driver name in the VM argument in the following format separated by a hash (“#”)

-Dbw.application.dd.jdbc.db_name.driver=tibcosoftwareinc.jdbc.db_name.db_Driver>

Note: Multiple URL separation option works only in case of the same Database having different versions. In case of multiple databases, the URL’s will be different or separate.