Splunk Search

Issues adding FileMaker driver to DB Connect

On_fire
Engager

I have Splunk version 5.0.2, build 149561 and DB Connect 1.0.8 running on an Ubuntu server 12.10.

I am trying to use DB Connect to connect to my FileMaker Server Advanced 12 and index some data, however it keeps throwing obscure errors. Any help to get this working would greatly appreciated already. Below are the errors that I get and what I have done so far.


When I try to to Fetch Database Names I get:


ERROR com.splunk.config.SplunkConfigurationException: Error instantiating typeClass com.filemaker.jdbc.Driver for database type filemaker: com.splunk.config.SplunkConfigurationException: Unable to create instance of class com.filemaker.jdbc.Driver




When I try to save the connection I get:


Encountered the following error while trying to save: In handler 'dbx-databases': Unknown error while validating database connection




I also get the following in the Splunk log:


ERROR AdminManager - Unknown error while validating database connection




Here is what I have done so far: (As per the DB Connect documentation)

I downloaded the driver (xDBC update for FileMaker Pro and FileMaker Server - version 12.3.103a) from:
http://www.filemaker.com/support/downloads/

And extracted the exe file and copied the jar from the JDBC folder to:

/opt/splunk/etc/apps/dbx/bin/lib

I changed the owner and permissions of fmjdbc.jar to match the other files in the folder.

I then copied:

/opt/splunk/etc/apps/dbx/default/database_types.conf

to

/opt/splunk/etc/apps/dbx/local/database_types.conf

and added a section to the top for FileMaker (Complete file):

http://pastebin.com/FBKfKegj

0 Karma
1 Solution

ziegfried
Influencer

The database_types.conf stanza you added uses the typeClass parameter. You should always use jdbcDriverClass instead as typeClass is only applicable to those database types that are defined by default. Here's an example how your stanza should look like for Filemaker:

[filemaker]
displayName = Filemaker
jdbcDriverClass = com.filemaker.jdbc.Driver
defaultPort = 2399
connectionUrlFormat = jdbc:filemaker://{0}/{2}

(This is not tested, but it might work)

View solution in original post

ziegfried
Influencer

The database_types.conf stanza you added uses the typeClass parameter. You should always use jdbcDriverClass instead as typeClass is only applicable to those database types that are defined by default. Here's an example how your stanza should look like for Filemaker:

[filemaker]
displayName = Filemaker
jdbcDriverClass = com.filemaker.jdbc.Driver
defaultPort = 2399
connectionUrlFormat = jdbc:filemaker://{0}/{2}

(This is not tested, but it might work)

On_fire
Engager

Thanks! This was exactly it.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...