Working With JDBC Drivers

This section describes how to set up your installation to use a driver other than the default driver.

Open Source JDBC Drivers

For open source JDBC drivers, buildomatic is set up to use a single default driver. If you want to use a driver other than the default driver, you can modify the buildomatic property files that determine the default JDBC driver.

The buildomatic JDBC driver property files are set up to point to a specific driver jar. This allows for multiple driver jar files in the same buildomatic/conf_source/db/<dbType>/jdbc folder. During the installation procedure only the default driver jar is copied to your application server.

If you want to use a newer JDBC driver version or a different JDBC driver, you can modify the buildomatic properties seen in your default_master.properties file.

PostgreSQL Example

If, for instance, you want to change the default driver used by PostgreSQL from type jdbc4 to jdbc3, edit your default_master.properties file: 

<js-install>/buildomatic/default_master.properties

When you next run a buildomatic command, such as deploy-webapp-pro, the jdbc3 driver will be copied to your application server.

MySQL Example

The buildomatic/conf_source/db/mysql/jdbc folder contains this driver file:

mariadb-java-client-1.1.2.jar

If, for instance, you want to use a JDBC driver built and distributed by the MySQL project, such as mysql-connector-java-5.1.30-bin.jar, you first need to download the driver from the MySQL Connector/J download location:

https://dev.mysql.com/downloads/connector/j/

Next, change your buildomatic configuration properties to point to this new driver.

Edit your default_master.properties file: 

<js-install>/buildomatic/default_master.properties

Uncomment and change: 

# jdbcDriverClass=com.mysql.jdbc.Driver

# maven.jdbc.groupId=mysql

# maven.jdbc.artifactId=mysql-connector-java

# maven.jdbc.version=5.1.30-bin

To: 

jdbcDriverClass=com.mysql.jdbc.Driver

maven.jdbc.groupId=mysql

maven.jdbc.artifactId=mysql-connector-java

maven.jdbc.version=5.1.30-bin

# 1) Setup Standard Oracle JDBC Driver## Uncomment and modify the value to nativejdbcDriverMaker=native## Uncomment and modify the value in order to change the default# 1a) Driver will be found here: <path>/buildomatic/conf_source/db/oracle/native.jdbc#maven.jdbc.groupId=oraclemaven.jdbc.artifactId=ojdbc6maven.jdbc.version=11.2.0.3[/code]

[/code]                        

# 1) Setup Standard SQLServer JDBC Driver## Uncomment and modify the value to nativejdbcDriverMaker=native## Uncomment and modify the value in order to change the default# Driver will be found here: <path>/buildomatic/conf_source/db/sqlserver/native.jdbc#maven.jdbc.groupId=sqlservermaven.jdbc.artifactId=sqljdbcmaven.jdbc.version=1.6[/code]                        

# 1) Setup Standard DB2 JDBC Driver## Uncomment and modify the value to nativejdbcDriverMaker=native## Uncomment and modify the value in order to change the default# Driver will be found here: <path>/buildomatic/conf_source/db/db2/native.jdbc#maven.jdbc.groupId=ibmmaven.jdbc.artifactId=db2jccmaven.jdbc.version=9.7[/code]                        

<datasource jta="false" jndi-name="java:/jdbc/jasperserver" pool-name="jasperserver" 		enabled="true" use-ccm="false">    <connection-url>jdbc:tibcosoftware:oracle//server1:1521;ServiceName=SERVICE;AlternateServers=(server2:1521,server3:1521,server4:1521);LoadBalancing=true</connection-url>    <driver>TIoracle-5.14.2.jar</driver>    <security>          <user-name>jasperserver</user-name>        <password>password</password>    </security>    <pool>        <min-pool-size>5</min-pool-size>        <max-pool-size>50</max-pool-size>        <prefill>true</prefill>    </pool>    <validation>        <validate-on-match>false</validate-on-match>        <background-validation>false</background-validation>        <check-valid-connection-sql>SELECT 1 FROM DUAL</check-valid-connection-sql>    </validation>    <statement>        <share-prepared-statements>false</share-prepared-statements>    </statement></datasource>[/code]                        

Glassfish Load Balancing Example

For Glassfish, the URL must be edited from the admin console.

Application Server Copy-to Locations

When the deploy-webapp-pro buildomatic target is executed it copies the JDBC driver to the following default locations: