Ready to get started?

Download a free trial of the SingleStore Driver to get started:

 Download Now

Learn more:

SingleStore Icon SingleStore JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SingleStore.

Access SingleStore Data in Mule Applications Using the CData JDBC Driver



Create a simple Mule Application that uses HTTP and SQL with the CData JDBC Driver for SingleStore to create a JSON endpoint for SingleStore data.

The CData JDBC Driver for SingleStore connects SingleStore data to Mule applications enabling read , write, update, and delete functionality with familiar SQL queries. The JDBC Driver allows users to easily create Mule applications to backup, transform, report, and analyze SingleStore data.

This article demonstrates how to use the CData JDBC Driver for SingleStore inside of a Mule project to create a Web interface for SingleStore data. The application created allows you to request SingleStore data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData JDBC Driver to create a Web interface for the 200+ available data sources.

  1. Create a new Mule Project in Anypoint Studio.
  2. Add an HTTP Connector to the Message Flow.
  3. Configure the address for the HTTP Connector.
  4. Add a Database Select Connector to the same flow, after the HTTP Connector.
  5. Create a new Connection (or edit an existing one) and configure the properties.
    • Set Connection to "Generic Connection"
    • Select the CData JDBC Driver JAR file in the Required Libraries section (e.g. cdata.jdbc.singlestore.jar).
    • Set the URL to the connection string for SingleStore

      The following connection properties are required in order to connect to data.

      • Server: The host name or IP of the server hosting the SingleStore database.
      • Port: The port of the server hosting the SingleStore database.
      • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

      Connect Using Standard Authentication

      To authenticate using standard authentication, set the following:

      • User: The user which will be used to authenticate with the SingleStore server.
      • Password: The password which will be used to authenticate with the SingleStore server.

      Connect Using Integrated Security

      As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

      Connect Using SSL Authentication

      You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

      • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
      • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
      • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
      • SSLClientCertType: The certificate type of the client store.
      • SSLServerCert: The certificate to be accepted from the server.

      Connect Using SSH Authentication

      Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

      • SSHClientCert: Set this to the name of the certificate store for the client certificate.
      • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
      • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
      • SSHClientCertType: The certificate type of the client store.
      • SSHPassword: The password that you use to authenticate with the SSH server.
      • SSHPort: The port used for SSH operations.
      • SSHServer: The SSH authentication server you are trying to authenticate against.
      • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
      • SSHUser: Set this to the username that you use to authenticate with the SSH server.

      Built-in Connection String Designer

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

      java -jar cdata.jdbc.singlestore.jar

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

    • Set the Driver class name to cdata.jdbc.singlestore.SingleStoreDriver.
    • Click Test Connection.
  6. Set the SQL Query Text to a SQL query to request SingleStore data. For example: SELECT ShipName, ShipCity FROM Orders WHERE ShipCountry = 'USA'
  7. Add a Transform Message Component to the flow.
  8. Set the Output script to the following to convert the payload to JSON:
    %dw 2.0
    output application/json
    ---
    payload
            
  9. To view your SingleStore data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The SingleStore data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with SingleStore data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the JDBC Driver for SingleStore and see the CData difference in your Mule Applications today.