Connect AlloyDB Data to Claris FileMaker via ESS using an ODBC Driver and the CData SQL Gateway

Claris FileMaker is a low-code platform that enables users to quickly create custom apps to manage and automate data workflows. Using the CData ODBC Driver for AlloyDB and the CData SQL Gateway, FileMaker connects to AlloyDB data through its ESS (External SQL Source) feature, allowing you to work with AlloyDB records as if they were native FileMaker tables.

In this article, we configure and use the CData ODBC Driver for AlloyDB and the CData SQL Gateway, along with the MySQL ODBC Driver, to connect to AlloyDB data using the ESS functionality in FileMaker.

Create an ODBC Data Source for AlloyDB

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

The following connection properties are usually required in order to connect to AlloyDB.

• Server: The host name or IP of the server hosting the AlloyDB database.
• User: The user which will be used to authenticate with the AlloyDB server.
• Password: The password which will be used to authenticate with the AlloyDB server.

You can also optionally set the following:

• Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
• Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

Authenticating with Standard Authentication

Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

No further action is required to leverage Standard Authentication to connect.

Authenticating with pg_hba.conf Auth Schemes

There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

Find instructions about authentication setup on the AlloyDB Server here.

Authenticating with MD5 Authentication

This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

Authenticating with SASL Authentication

This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

Authenticating with Kerberos

The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Configuring the CData SQL Gateway

The CData SQL Gateway bridges non-SQL data sources (like SaaS applications, APIs, and NoSQL databases) with SQL-based tools (like FileMaker, MySQL clients, and BI tools).

In simple terms, it exposes any CData driver-supported source - for example, AlloyDB - as a standard MySQL or SQL Server endpoint.

See the SQL Gateway Overview to set up AlloyDB data connectivity as a virtual MySQL database. Set up a MySQL remoting service that listens for MySQL requests from clients, and configure the service through the SQL Gateway UI (as shown below). Save the user credentials (Username and Password) for future use.

👁 Add a new service in CData SQL Gateway
👁 Add a new user and save the credentials

Once you establish the connection, you can use the CData SQL Gateway to access AlloyDB data through the MySQL protocol.

Installing the MySQL ODBC Driver

Follow the steps below to install and configure the MySQL ODBC Driver:

1. Download and install the latest 64-bit Windows version of the MySQL ODBC Unicode Driver from this link.
2. Launch ODBC Data Sources (64-bit) from Windows search. Open the System DSN tab, click Add, select MySQL ODBC Unicode Driver from the Create New Data Source window, and click Finish.
👁 Create a new data source using the latest MySQL ODBC Unicode Driver

3. Enter the following connection details in the MySQL Connector/ODBC Data Source Configuration window:
   • Data Source Name: Enter a DSN of your choice
   • TCP/IP Server: localhost
   • Port: Enter the port set in the SQL Gateway (for this procedure, use "3307")
   • User: Enter the username set in the CData SQL Gateway
   • Password: Enter the password set in the CData SQL Gateway
   • Database: CData AlloyDB Sys
   👁 Configure the MySQL ODBC Driver using CData SQL Gateway credentials
   
4. Click Test to verify that the "Connection Successful" dialog box appears. Then click OK to save the configuration details.

You have now successfully configured the MySQL ODBC Driver.

Use FileMaker ESS function to load AlloyDB data

In this section, we explore how to use the ESS (External SQL Source) feature to retrieve data in the FileMaker application. Follow the given steps to complete the process:

1. Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
👁 Create a new application in FileMaker Pro

2. Enter a desired filename and click Save.
3. In Manage Database, remove the Tables and Fields from the respective tabs. Select the Relationships tab and click Add Table.
👁 Add a table in the Manage Database window in FileMaker Pro

4. In Specify Table, expand the Data Source dropdown menu and select Add ODBC Data Source. Click OK.
👁 Add an ODBC Data Source in the Specify Table window

5. In Select ODBC Data Source, select the previously configured MySQL ODBC driver and click Continue.
👁 Select the newly configured MySQL ODBC Unicode Driver

6. In the Edit Data Source window, enter the following details:
• Name: This field will be auto-filled. Enter a new name of choice if necessary.
• Type: Select "ODBC".
• Under Authentication, select the Specify username and password radio button and enter the following details:
• User name: Enter the username set in the CData SQL Gateway.
• Password: Enter the password set in the CData SQL Gateway.
• Catalog Name: CData AlloyDB Sys
7. Click OK.
👁 Configure the data source in FileMaker

8. View the tables from AlloyDB populated under the Data Source section. Select the table of your choice and click OK.
👁 Add a new table in the Specify Table window

9. The Relationships tab now displays the selected table and its metadata. Click OK.
👁 The new table gets added in the Relationships tab

10. Select the table from the Layout dropdown. The AlloyDB table data appears on the screen. (As shown)
👁 The AlloyDB table data is displayed in FileMaker Pro

Get Started Today

Download a free 30-day trial of CData ODBC Driver for AlloyDB to integrate AlloyDB data into Claris FileMaker and use AlloyDB data in your FileMaker applications.

Contact our Support Team if you have any questions.