Support for Non-Redistributable Database Drivers

Due to licensing restrictions, Broadcom can no longer ship JDBC drivers for the Oracle database management system. Open source driver(s) exist for SQL Server and Sybase (JTDS) and will continue to be shipped with the product.
To connect
Automic Automation Intelligence
to any Oracle database (scheduler database or
Automic Automation Intelligence
database), the following procedure is required.
  1. Ensure that the Java version you have installed is Java 1.8.x.
    No other versions of java are supported at this time.
  2. To determine the version of Java you have installed, enter the following command from a command line:
    • java -version
  3. Install Oracle Instant Client (which can be downloaded from the Oracle website):
    All testing has been done with the
    Basic
    package, version v19.3.0.0.0, however the
    Light
    package should also work.  Additional tools packages are not required (SQL*Plus, Tools, SDK, etc)
  4. Locate the ojdbc8.jar file from the installation.
    • Ubuntu:
      /usr/lib/oracle/19.3/client64/lib/ojdbc8.jar
    • Windows: Unzip the installation package to a directory of your choice.  The file is in the root of the unzipped packageFigure ojdbc8.jar file from the installation
    • RHEL:
      • /usr/lib/oracle/19.3/client64/lib/ojdbc8.jar
  5. Copy
    ojdbc8.jar
    from the installation directory (above) to the
    {Automic_Automation_Intelligence}/jboss/standalone/deployments
    directory on the
    Automic Automation Intelligence
    platform server.
    You should now be able to run the Config Tool and the
    Automic Automation Intelligence
    server.
    No changes are required for
    Automic Automation Intelligence
    INSIGHT. The Oracle driver has been packaged and licensed for distribution by Tibco Software and made available as part of the embedded BI server.
Internal Notes:
In order for JBOSS to recognize the Oracle driver, it needs to be declared as a
module
to the server and the jar file must reside in the deployments directory.  Changes were required to
META-INF/jboss-deployment-structure.xml
directory inside the
jaws.ear
file to register the module. The module is registered as
optional
, so for non-Oracle or existing installations, there should be no additional warnings or errors related to this change.
In addition, the Config Tool classpath must be modified in the MAINFEST.MF to reference the driver so the class can be loaded by running java -jar, as is done in the
./run.sh
or
run.bat
scripts.  Relative pathing is used in the classpath so that a single copy of the jar file is used for both the JBOSS server and the Config Tool.
The telltale sign that the jar file is not in the correct location, or does not have the correct name, or is not readable, or some other problem is that you will see the following message in the hibernate.log:
java.sql.SQLException: No suitable driver
A similar message appears in the configtool.log if not properly configured:
java.sql.SQLException: No suitable driver found for jdbc:oracle:thin:@ . . . . . . . .