Access XML Data in Mule Applications Using the CData JDBC Driver

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Create a simple Mule Application that uses HTTP and SQL with CData JDBC drivers to create a JSON endpoint for XML data.

The CData JDBC Driver for XML connects XML 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 XML data.

This article demonstrates how to use the CData JDBC Driver for XML inside of a Mule project to create a Web interface for XML data. The application created allows you to request XML 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.xml.jar).
    • Set the URL to the connection string for XML

      Connecting to Local or Cloud-Stored (Box, Google Drive, Amazon S3, SharePoint) XML Files

      CData Drivers let you work with XML files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.

      Setting connection properties for local files

      Set the URI property to local folder path.

      Setting connection properties for files stored in Amazon S3

      To connect to XML file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended XML files exist. In addition, at least set these properties:

      • AWSAccessKey: AWS Access Key (username)
      • AWSSecretKey: AWS Secret Key

      Setting connection properties for files stored in Box

      To connect to XML file(s) within Box, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Box.

      Dropbox

      To connect to XML file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.

      SharePoint Online (SOAP)

      To connect to XML file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. Set User, Password, and StorageBaseURL.

      SharePoint Online REST

      To connect to XML file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended XML file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.

      Google Drive

      To connect to XML file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended XML file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.

      The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

      • Document (default): Model a top-level, document view of your XML data. The data provider returns nested elements as aggregates of data.
      • FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
      • Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

      See the Modeling XML Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

      Built-in Connection String Designer

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

      		java -jar cdata.jdbc.xml.jar
      		

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

    • Set the Driver class name to cdata.jdbc.xml.XMLDriver.
    • Click Test Connection.
  6. Set the SQL Query Text to a SQL query to request XML data. For example:
    SELECT [people].[personal.age] AS age, [people].[personal.gender] AS gender, [people].[personal.name.first] AS first_name, [people].[personal.name.last] AS last_name, [vehicles].[model], FROM [people] JOIN [vehicles] ON [people].[_id] = [vehicles].[people_id]
  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 XML data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The XML 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 XML 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 XML and see the CData difference in your Mule Applications today.

Ready to get started?

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

 Download Now

Learn more:

XML Documents Icon XML JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with XML data stores.