Installing database drivers for Information Designer
To be able to access data from a JDBC-compliant data source with Information Services, you must install the appropriate JDBC driver on the computer that is running Spotfire Server.
About this task
To install drivers on the server, you can either install the drivers manually by logging in to the computer running Spotfire Server, or you can deploy a package (.spk) with the driver and install it to the Spotfire Server in the server administration pages.
Installing JDBC drivers manually
If you have administrator access to the computer running the Spotfire Server, you can log in to the computer and install JDBC drivers manually.
Procedure
Installing JDBC drivers in the server administration pages
About this task
To install JDBC drivers through the server administration pages, you must first create a Spotfire package (.spk) with the JDBC driver, and then deploy it to the Spotfire Server.
Before you begin
- To install and use JDBC drivers with this method, Information Services must be configured to run as an external process (this is the default), and not in-process with the main Spotfire Server process.
Building a Spotfire package with a JDBC driver
Before you begin
- Download the Spotfire Package Builder console from the Spotfire Developer software. See Downloading Spotfire Developer.
Procedure
Example package description
<?xml version="1.0" encoding="utf-8"?>
<PackageDescription
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
SchemaVersion="2.0"
Name="driver-name"
Version="1.0.0.0"
SeriesId="67c46837-64f0-4a4f-bd32-c7496dc7490a"
IntendedClient="InformationServices"
Type="JdbcDriver"
Capability="INFORMATION_SERVICES">
<File SourceFile="driver-name.jar" TargetFilename="driver-name.jar" Type="File"/>
</PackageDescription>
Deploying your JDBC driver in the server administration pages
When you have created your Spotfire package, you must deploy it to a deployment area, and then fetch and update the new drivers for each Information Services instance.
Procedure
Results
The JDBC drivers in the selected deployment area are installed to <installation-dir>\nm\services\InformationServices\is-drivers on the computer running the Spotfire Server. Any drivers that were removed or changed in the deployment area are also removed or updated.
Troubleshooting
Validation of data source template error: Driver not found
When you add or edit a data source template in the Spotfire Server configuration tool, if the corresponding JDBC driver is installed to the is-drivers directory (if you installed it in the server administration pages), the tool cannot find the driver to validate the template. An error message is shown stating that the driver cannot be found, but you can ignore the message and save the configuration.
Drivers installed to multiple locations
If the same driver class is installed in both directories (<installation dir>/tomcat/custom-ext-informationservices and <installation-dir>\nm\services\InformationServices\is-drivers) on the same Spotfire Server, the driver in the is-drivers directory is prioritized.
In versions 12.1 and later, Information Services runs in its own
subprocess, and uses the new default extensions directory
<installation
dir>/tomcat/custom-ext-informationservices for JDBC drivers. When
you upgrade from an earlier version, all your JDBC drivers remain in the
previous default directory,
<installation dir>/tomcat/custom-ext, and
the configuration property
information-services.external-process.use-legacy-extensions
is set to
true. This way, Information Services can also use
drivers from the
custom-ext folder.
After upgrading, it is recommended that you manually move
Information Services-related JDBC drivers to the
custom-ext-informationservices directory. After
you have moved your drivers, set the configuration property
information-services.external-process.use-legacy-extensions
to
false.
What to do next
To connect to an external data source, you must also add and/or enable a data source template that matches the database and the specific database driver.