![]() |
VOOZH | about |
This article shows how to use the CData JDBC Driver for Oracle Eloqua to integrate with the External SQL Sources (ESS) feature in FileMaker Pro, which allows you to link records in FileMaker Pro with related records in your other operational data stores.
You will use the MySQL Remoting feature to access Oracle Eloqua as a remote MySQL database. The CData JDBC Driver for Oracle Eloqua implements both the JDBC and MySQL standards to integrate with applications like FileMaker Pro that support connections to traditional databases like MySQL but not generic JDBC connections.
There are two data access modes in FileMaker Pro:
The JDBC driver is part of a data access chain. Compared to a native ODBC integration, FileMaker Pro integrations that use MySQL remoting have several additional components. This article shows how to link each of the following components with FileMaker Pro:
On Windows, FileMaker Pro requires the official MySQL driver, the MySQL Connector\ODBC (currently, the best option is Connector\ODBC 8.0.11).
On macOS, FileMaker Pro requires the Actual Technologies Open Databases ODBC driver.
An ODBC driver manager.
On Windows, the driver manager is built in. On macOS, you will need to install a driver manager before installing the ODBC driver; install the iODBC driver manager.
Follow the steps below to enable the MySQL Remoting feature:
Open Terminal and change to the lib subfolder in the installation folder.
$ cd "/Applications/CData/CData JDBC Driver for Oracle Eloqua/lib"
oracleeloqua = "User=user;Password=password;Company=CData;"
There are two authentication methods available for connecting to Oracle Eloqua: Login and OAuth. The Login method requires you to have the Company, User, and Password of the user.
If you do not have access to the username and password or do not wish to require them, you can use OAuth authentication. OAuth is better suited for allowing other users to access their own data. Using login credentials is better suited for accessing your own data.
See the help documentation for more information about the available connection properties and other configuration options for remoting.
Start the MySQL daemon by specifying the configuration file or settings on the command line. The example below uses the included sample configuration file.
$ java -jar cdata.jdbc.oracleeloqua.jar -f "cdata.jdbc.oracleeloqua.remoting.ini"
After connecting successfully to Oracle Eloqua and starting the MySQL daemon, create a MySQL ODBC data source. When working with ODBC data sources, you specify connection properties in a DSN (data source name).
If you have not already obtained an ODBC driver and driver manager, refer to "Outlining the ESS Setup" to determine the components supported for your platform.
Follow the steps below to use the iODBC graphical administrator tool:
You can use the built-in Microsoft ODBC Data Source Administrator to create the ODBC DSN.
Shadow tables exist in an external SQL source but can be used in much the same way as other tables in your FileMaker database; you can add them in the relationships graph, browse data, and create layouts on them.
After specifying the username and password for the DSN, you can add Oracle Eloqua tables to the relationships graph. You can now scroll through, sort, edit, and summarize Oracle Eloqua data by clicking View -> Browse Mode, just as you would a remote MySQL database.
👁 Tables to be linked to the external data source in the relationships graph. (Salesforce is shown.)Download a free trial of the Eloqua Driver to get started:
Download NowLearn more:
👁 Oracle Eloqua IconRapidly create and deploy powerful Java applications that integrate with Eloqua marketing automation platform including Contacts, Campaigns, Emails, Activities, and more!