Connect to RabbitMQ from a Connection Pool in WebLogic

The CData JDBC Driver for RabbitMQ enables you to follow standard procedures to integrate RabbitMQ data into Java Web applications. This article shows how to deploy the CData JDBC Driver for RabbitMQ in WebLogic Server.

Deploy the JDBC Driver in WebLogic Server

To deploy the driver, add the driver JAR to your classpath. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory.

If you want to add the driver to all domains, prepend the path to the JAR to the WEBLOGIC_CLASSPATH environment variable in WL_HOME\common\bin\commEnv.cmd/sh. This script is located in WL_HOME\common\bin\. For example:

set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.api.jar;%WEBLOGIC_CLASSPATH%

In WebLogic 12.2.1 if you want to add the driver to a specific domain, you can simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.

Earlier versions require that you manually add the driver to the classpath: Prepend the following to the PRE_CLASSPATH environment variable in setDomainEnv.cmd/sh. This script is located in the bin subfolder of the folder for that domain.

set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.api.jar;%PRE_CLASSPATH%

After making these changes, restart the server.

Create a JDBC Data Source for RabbitMQ

After deploying the driver, log into the WebLogic Administration Console and create the connection.

1. In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
2. On the JDBC Data Source Properties page, enter the following information:
   • Name: Enter a user-friendly name; for example, apijdbc.
   • JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/API.

   • Database Type: Select Other.

   

3. Click Next to use the default options. On the last page, enter the following information and click Test Configuration:

   • Driver Class Name: Enter the driver class, cdata.jdbc.api.APIDriver.

   • URL: Enter the JDBC URL. A typical JDBC URL is below:

     jdbc: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

     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.

     
   • Database User Name: Enter the username, if not specified in the JDBC URL.
   • Password: Enter the password, if not specified in the JDBC URL.
   

After selecting the server where you want to deploy the JDBC data source, you can now connect to RabbitMQ data.

More WebLogic Integration

The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the WebLogic Data Sources chapter of the Oracle Fusion Middleware documentation.