Adding a database driver to the Messaging Gateway

Last Updated: 31 Dec 2018

The Messaging Gateway already includes database drivers for Oracle and SQL Server. You can add additional drivers or change the existing ones as required.

The drivers are maintained in the c:\cag\jdbc directory. Each driver is a jar file, and has to be renamed to a filename from d1.jar to d9.jar. This mechanism has been so designed since the Messaging Gateway's classpath cannot be changed, thus necessitating file renames.

In the default installation, the files d1 and d2 are the drivers for Oracle and SQL Server respectively. The files d3 to d9 are dummy files - replace them with your own driver jar.

Since renaming a file may cause you to lose track of them, a comments text file has been included. Ensure that you update the comments file on any change.

Additionally, its recommended that a copy of the driver jar files be placed in the drivercopy directory, with their original names. While this directory is not used by the Messaging Gateway, it is a useful reference to assist you.

Note that the default Oracle driver is not compatible with Oracle 12c. It only supports SIDs, not service names; update to the latest jdbc driver to avail of these features. A newer driver 'ojdbc7.jar' is present in the drivercopy directory - replace d1.jar with it if required.

Note that the Messaging Gateway uses the provided d1.jar Oracle driver for its own connectivity to its private Oracle Database. Should you face stability issues with the Messaging Gateway, revert to the originally-provided d1.jar.

The Messaging Gateway is compatible with class versions upto Java 8. Note that updating the Java installation on your OS does not increase this limit.