Build RabbitMQ-Connected ETL Processes in Google Data Fusion

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Load the CData JDBC Driver into Google Data Fusion and create ETL processes with access live RabbitMQ data.

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData API Driver for JDBC enables users to access live RabbitMQ data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping RabbitMQ data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from RabbitMQ to Google BigQuery,

Upload the CData API Driver for JDBC to Google Data Fusion

Upload the CData API Driver for JDBC to your Google Data Fusion instance to work with live RabbitMQ data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdataapi-2020.jar

  1. Open your Google Data Fusion instance
  2. Click the to add an entity and upload a driver
  3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
  4. On the "Driver configuration" tab:
    • Name: Create a name for the driver (cdata.jdbc.api) and make note of the name
    • Class name: Set the JDBC class name: (cdata.jdbc.api.APIDriver)
  5. Click "Finish"

Connect to RabbitMQ Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live RabbitMQ data in Google Data Fusion Pipelines.

  1. Navigate to the Pipeline Studio to create a new Pipeline
  2. From the "Source" options, click "Database" to add a source for the JDBC Driver
  3. Click "Properties" on the Database source to edit the properties

    NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

    • Set the Label
    • Set Reference Name to a value for any future references (i.e.: cdata-api)
    • Set Plugin Type to "jdbc"
    • Set Connection String to the JDBC URL for RabbitMQ. For example:

      jdbc:api:RTK=5246...;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

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the RabbitMQ JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

            java -jar cdata.jdbc.api.jar
            

      Fill in the connection properties and copy the connection string to the clipboard.

    • Set Import Query to a SQL query that will extract the data you want from RabbitMQ, i.e.:
      SELECT * FROM AuthAttempts
  4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
  5. Click "Properties" on the BigQuery sink to edit the properties
    • Set the Label
    • Set Reference Name to a value like api-bigquery
    • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
    • Set Dataset to a specific Google BigQuery dataset
    • Set Table to the name of the table you wish to insert RabbitMQ data into

With the Source and Sink configured, you are ready to pipe RabbitMQ data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from RabbitMQ and import it into Google BigQuery.

While this is a simple pipeline, you can create more complex RabbitMQ pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData API Driver for JDBC and start working with your live RabbitMQ data in Google Data Fusion today.

Ready to get started?

Connect to live data from RabbitMQ with the API Driver

Connect to RabbitMQ