Extract, Transform, and Load Google Drive Data in Informatica PowerCenter



Create a simple Workflow for Google Drive data in Informatica PowerCenter.

Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData ODBC Driver for Google Drive, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's powerful data transportation and manipulation features. This tutorial shows how to create a simple Workflow in Informatica PowerCenter to extract Google Drive data and load it into a flat file.

Add Google Drive as an ODBC Data Source

If you have not already, install the driver on the PowerCenter server and client machines. On both machines, specify the connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

You can connect to Google APIs on behalf of individual users or on behalf of a domain. Google uses the OAuth authentication standard. See the "Getting Started" section of the help documentation for a guide.

Create an ETL Workflow in PowerCenter

Follow the steps below to create a workflow in PowerCenter to pull Google Drive data and push it into a flat file.

Create a Source Using the ODBC Driver

  1. In the powrmart.ini file found in %INFA_HOME%\clients\PowerCenterClient\client\bin, add the following line to the ODBCDLL section:
    CData=PMODBC.DLL
  2. In PowerCenter Workflow Manager, add a new ODBC relational connection, set the user name and password properties to the user for the machine on which the ODBC Driver is installed, and set the connect string to the System DSN for the driver (CData GoogleDrive Sys).
  3. In PowerCenter Designer, connect to your repository and open your folder.
  4. Select the Source Analyzer, click the sources menu, and select Import from Database...
  5. In the drop-down menu for ODBC data source, select the DSN you previously configured (CData GoogleDrive Sys).
  6. Click connect and select the tables and views to include.
  7. Click OK.

Create a Flat File Target Based on the Source

  1. Select the Targets Analyzer and drag and drop the previously created source onto the workspace. Using the existing source copies the columns into the target.
  2. Right-click the new target, click edit, and change the database type to flat file.

Create a Mapping to Between Google Drive Data and a Flat File

  1. Click on the Mapping Designer.
  2. Drag the source and target to the workspace (name the new mapping, if prompted).
  3. Right-click on the workspace and select Autolink by Name.
  4. Drag the columns from the source qualifier to the target definition.
  5. Save the folder (Ctrl + S).

Create Workflow Based on the Mapping

With the source, target, and mapping created and saved, you are now ready to create the workflow.

  1. Right-click the mapping and select generate workflow to open the Workflow Generation wizard.
  2. Create a workflow with a non-reusable session.
  3. Ensure that you have properly configured the connection object (to the relational connection we created earlier) and set the prefixes.
  4. Configure the Connection as needed.
  5. Review the Workflow and click Finish.

With a workflow created, you can open the PowerCenter Workflow Manager to access and start the workflow, quickly transferring Google Drive data into a flat file. With the ODBC Driver for Google Drive, you can configure sources and targets in PowerCenter to integrate Google Drive data into any of the elegant and powerful features in Informatica PowerCenter.

Ready to get started?

Download a free trial of the Google Drive ODBC Driver to get started:

 Download Now

Learn more:

Google Drive Icon Google Drive ODBC Driver

The Google Drive ODBC Driver is a powerful tool that allows you to connect with live data from Google Drive, directly from any applications that support ODBC connectivity.

Access Google Drive data like you would a database, including Files, Changes, Apps, etc. through a standard ODBC Driver interface.