Link RabbitMQ with FileMaker Pro

This article shows how to use the CData JDBC Driver for RabbitMQ 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 RabbitMQ as a remote MySQL database. The CData JDBC Driver for RabbitMQ 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.

Selecting a FileMaker Pro Integration

Use the JDBC the JDBC driver to create an external SQL source (ESS). The remote data can be modified in FileMaker Pro and tables can be used in the relationships graph like standard FileMaker Pro tables.

Outlining the ESS Setup

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:

1. The CData JDBC driver.
2. The CData MySQL Remoting daemon (included with the driver).
3. An ODBC driver for MySQL.

   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.

4. 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.

Start the Remoting Daemon

Follow the steps below to enable the MySQL Remoting feature:

1. Open Terminal and change to the lib subfolder in the installation folder.

   $ cd "/Applications/CData/CData JDBC Driver for RabbitMQ/lib"
   

2. Edit the configuration file (cdata.jdbc.api.remoting.ini by default):
   • Update the [databases] section with the JDBC Connection URL for RabbitMQ:

     	api = "Profile=C:\profiles\\RabbitMQ.apip;AuthScheme=Basic;URL=http://localhost:15672;User=guest;Password=guest;"
     	

     About RabbitMQ Management HTTP API

     RabbitMQ is an open-source message broker that supports multiple messaging protocols. The RabbitMQ Management HTTP API provides HTTP-based access to management and monitoring data for a RabbitMQ server. The API exposes information about virtual hosts, exchanges, queues, bindings, connections, channels, consumers, users, permissions, policies, and cluster-wide statistics.

     The Management plugin must be enabled on the RabbitMQ server for the HTTP API to be available. By default, the management interface listens on port 15672.

     Using Basic Authentication

     RabbitMQ Management HTTP API uses HTTP Basic authentication. You must supply the username and password of a RabbitMQ management user.

     To enable access to the management API:

     1. Ensure the RabbitMQ Management plugin is enabled on your server (rabbitmq-plugins enable rabbitmq_management).
     2. Use an existing management user or create one with the appropriate management tag (management, policymaker, monitoring, or administrator).
     3. Note the full base URL of your RabbitMQ Management HTTP API (e.g., http://localhost:15672).

     After configuring your RabbitMQ server, set the following connection properties to connect:

     • AuthScheme: Set this to Basic.
     • URL: Set this to the base URL of your RabbitMQ Management HTTP API (e.g., http://localhost:15672).
     • User: Set this to your RabbitMQ management username (e.g., guest).
     • Password: Set this to your RabbitMQ management password.

     Example connection string:

     Profile=C:\profiles\RabbitMQ.apip;AuthScheme=Basic;URL=http://localhost:15672;User=guest;Password=guest;
     

     Available Tables

     The RabbitMQ profile provides access to the following tables:

     • Overview - Cluster-wide statistics and information about the RabbitMQ node
     • Nodes - Information about individual nodes in the RabbitMQ cluster
     • NodeMemory - Detailed memory usage breakdown for a specific cluster node
     • Connections - List of all open AMQP connections to the broker
     • Channels - List of all open AMQP channels across all connections
     • Consumers - List of all consumers registered across all queues
     • Exchanges - List of exchanges declared across all virtual hosts
     • Queues - List of queues declared across all virtual hosts
     • Bindings - List of all bindings between exchanges and queues
     • VirtualHosts - List of virtual hosts configured on the broker
     • VhostPermissions - User permissions within a specific virtual host
     • Users - List of all RabbitMQ users
     • Permissions - Permission records for all users across all virtual hosts
     • TopicPermissions - Topic-level permission records for all users
     • Policies - List of policies applied to queues and exchanges in virtual hosts
     • OperatorPolicies - List of operator policies applied to queues in virtual hosts
     • Parameters - List of component parameters (e.g., federation, shovel) per virtual host
     • GlobalParameters - List of global parameters that apply across all virtual hosts
     • VhostLimits - Resource limits configured for specific virtual hosts
     • UserLimits - Resource limits configured for specific users
     • FeatureFlags - List of feature flags and their enabled/disabled state on the node
     • DeprecatedFeatures - List of deprecated features and their usage state
     • AuthAttempts - Authentication attempt statistics for the node
     • ClusterName - The name of the RabbitMQ cluster
     • WhoAmI - Information about the currently authenticated management user
     • ExchangeBindingsSource - Bindings for which a specific exchange is the source
     • ExchangeBindingsDestination - Bindings for which a specific exchange is the destination
     • QueueBindings - Bindings for a specific queue within a virtual host

     See the help documentation for more information about the available connection properties and other configuration options for remoting.

3. 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.api.jar -f "cdata.jdbc.api.remoting.ini"
   

Create the DSN

After connecting successfully to RabbitMQ 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.

macOS

Follow the steps below to use the iODBC graphical administrator tool:

1. Open iODBC by searching in the launchpad.
2. On the System DSN tab, click Add and select Actual Open Source Databases.
3. Provide the following information to complete the wizard:
   • Name: Enter the DSN.
   • Server: Enter 127.0.0.1 or the address of the machine where the MySQL daemon is running.
   • Port: Enter the port that the daemon is listening on. For example, 3306.
   • Database: Enter the name of a database specified in the config file for the daemon. For example, API.
   • In the Metadata tab, check the boxes for:
     • "Ignore schema in column specifications"
     • "Don't use INFORMATION_SCHEMA for metadata"
4. Click Test Connection and enter your credentials in the dialog.

Windows

You can use the built-in Microsoft ODBC Data Source Administrator to create the ODBC DSN.

1. From the Control Panel, select Set Up Data Sources (ODBC). The ODBC Data Source Administrator is displayed.
2. On the System DSN tab, click Add and select the MySQL ODBC driver.
3. Provide the following information to complete the wizard:
   • Name: Enter the DSN.
   • Server: Enter 127.0.0.1 or the address of the machine where the MySQL daemon is running.
   • Port: Enter the port that the daemon is listening on. For example, 3306.
   • Database: Enter the name of a database specified in the config file for the daemon. For example, API.
   • In the Metadata tab, check the boxes for:
     • "Ignore schema in column specifications"
     • "Don't use INFORMATION_SCHEMA for metadata"
4. Click Test Connection and enter your credentials in the dialog.

Create RabbitMQ Shadow Tables

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.

1. Click File -> Manage -> Database.
2. On the Relationships tab of the resulting dialog, click the Add a Table button in the Table/Relationships section.
3. In the Data Source menu, select Add ODBC Data Source and then select the DSN you created in the previous section.

After specifying the username and password for the DSN, you can add RabbitMQ tables to the relationships graph. You can now scroll through, sort, and summarize RabbitMQ data by clicking View -> Browse Mode, just as you would a remote MySQL database.