Ready to get started?

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

 Download Now

Learn more:

PayPal Icon PayPal ODBC Driver

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

Access PayPal Transactions, Orders, Sales, Invoices, etc. through a standard ODBC Driver interface.

Use the CData ODBC Driver for PayPal in MicroStrategy



Connect to PayPal data in MicroStrategy Developer using the CData ODBC Driver for PayPal.

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for PayPal, you gain database-like access to live PayPal data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for PayPal in MicroStrategy Developer and creating a Warehouse Catalog based on PayPal data.

The CData ODBC Driver offers unmatched performance for interacting with live PayPal data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to PayPal, the driver pushes supported SQL operations, like filters and aggregations, directly to PayPal and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze PayPal data using native MicroStrategy data types.

Connect to PayPal as an ODBC Data Source

Information for connecting to PayPal follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for PayPal must be installed on the machine hosting the connected MicroStrategy Intelligence Server).

The provider surfaces tables from two PayPal APIs. The APIs use different authentication methods.

  • The REST API uses the OAuth standard. To authenticate to the REST API, you will need to set the OAuthClientId, OAuthClientSecret, and CallbackURL properties.
  • The Classic API requires Signature API credentials. To authenticate to the Classic API, you will need to obtain an API username, password, and signature.

See the "Getting Started" chapter of the help documentation for a guide to obtaining the necessary API credentials.

To select the API you want to work with, you can set the Schema property to REST or SOAP. By default the SOAP schema will be used.

For testing purposes you can set UseSandbox to true and use sandbox credentials.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Windows

If you have not already, first specify 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.

Linux

If you are installing the CData ODBC Driver for PayPal in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData PayPal Sys] Driver = CData ODBC Driver for PayPal Description = My Description Schema = SOAP Username = sandbox-facilitator_api1.test.com Password = xyz123 Signature = zx2127

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Create a PayPal Database Instance in MicroStrategy Developer

You can connect to PayPal in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for PayPal.*

  1. Open MicroStrategy Developer and select a Project Source.
  2. Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
  3. Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
  4. In the database connection wizard, name the connection and create a new Database Login name, using filler values for the user and password.
  5. Select the DSN that you configured earlier as the ODBC data source (i.e., CData PayPal Sys).
  6. Select the newly created database connection.
  7. In the Project Source, right-click the project and open the Project configuration.
  8. Navigate to Database Instances and select the newly created database instance.
  9. Close MicroStrategy Developer and restart the connected MicroStrategy Intelligence Server to complete the database instance creation.

With the database instance configured, you will now be able to connect to PayPal data from the Warehouse Catalog and Data Import.

Connect to PayPal Data from the Warehouse Catalog

Once you have created a database instance based on the ODBC Driver for PayPal, you can connect to data from the Warehouse Catalog.

  1. Select your project and click Schema -> Warehouse Catalog.
  2. In the Read Settings for the Catalog, click Settings and set the queries to retrieve the schema:
    • To retrieve the list of tables, use the following query:
      SELECT 
        CatalogName NAME_SPACE,
        TableName TAB_NAME 
      FROM 
        SYS_TABLES
              
    • To retrieve the list of columns for selected tables, use the following query:
      SELECT DISTINCT 
        CatalogName NAME_SPACE, 
        TableName TAB_NAME, 
        ColumnName COL_NAME, 
        DataTypeName DATA_TYPE, 
        Length DATA_LEN, 
        NumericPrecision DATA_PREC, 
        NumericScale DATA_SCALE 
      FROM 
        SYS_TABLECOLUMNS 
      WHERE 
        TableName IN (#TABLE_LIST#) 
      ORDER BY
        1,2,3
              
  3. Select tables to be used in the project.

If you are interested in connecting to PayPal from other MicroStrategy products, you can read about connecting from MicroStrategy Web and connecting from MicroStrategy Desktop.


Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.