Release-December 13, 2014

Progress DataDirect Cloud™

Progress DataDirect Cloud enables simple, fast connections to cloud and on-premise data regardless of source—SaaS apps, big data stores, or social networks—using a single standards-based ODBC or JDBC driver , or OData enabled application. For example, an organization might want to use a reporting application to predict travel budgets by analyzing travel data stored in the cloud. DataDirect Cloud can provide connectivity with simple configuration instead of extensive coding. In addition, when you install the DataDirect Cloud On-Premise Connector on a machine behind your firewall, you can connect to on-premise data sources using DataDirect Cloud, without opening ports or otherwise configuring the fire wall. The On-Premise Connector establishes a secure connection back to DataDirect Cloud when needed to provide access to the on-premise data stores.

DataDirect Cloud– December 13, 2014

Key Features and Benefits

DataDirect Cloud provides the following new features for this release.

New GA Data Stores
Support for Querying External Objects in Salesforce
  • DataDirect Cloud has been tested with Salesforce Lightning Connect. Using the DataDirect Cloud OData interface you can access data in your On-Premise and Cloud databases from within Salesforce without having to import the data into Salesforce. The data in the On-Premise and Cloud databases is accessed in real time. This eliminates the need for time-consuming imports and alleviates worries that the imported data is out of date.
  • The following data stores provide GA support for querying external objects in Salesforce using OData:
    • Amazon Redshift
    • DB2 UDB, DB2 for z/OS, DB2 i
    • Eloqua
    • Google Analytics
    • Microsoft Dynamics CRM
    • Microsoft SQL Server and Microsoft Azure
    • MySQL
    • Oracle
    • Oracle Service Cloud
    • PostgreSQL
    • Progress OpenEdge
    • Progress Rollbase
    • Salesforce
  • The following beta data stores provide beta support for querying external objects in Salesforce using OData:
    • FinancialForce
    • Greenplum
    • HubSpot
    • Informix
    • ServiceMax
    • Sugar CRM
    • Sybase
    • Veeva CRM
Data Source Configuration Screens Redesigned
  • Options with similar functionality have been grouped into tabs.
  • Name-value pair options, formerly implemented using the Map Options and Custom Properties connection parameters, have been broken up into multiple controls.
  • OData Data Model GUI editor has been added.
  • Automatically refresh a Data Source. If any of the options in the Set Map Options control group have changed, the data source map is refreshed when the data source is saved. This group of options specify how the Cloud data source objects are mapped to tables. This applies to the following Data Stores:
    • Google Analytics
    • Microsoft Dynamics CRM
    • Oracle Service Cloud
    • Progress Rollbase
    • Salesforce
    • Financial Force
    • Service Max
    • Sugar CRM
    • Veeva CRM
  • Added a Refresh button to the Data Source Mapping tab to manually refresh the data source map for the above data sources. A map may need to be refreshed manually if a new object has been created in the backend data source. The new object will not be visible until the map is refreshed.
  • Automatic refresh of OData Data Model when the OData Schema Map option is changed, either explicitly or through the OData Data Model editor.
  • Added a Refresh button to the Data Source OData tab to manually refresh the OData data model. The data model may need to be refreshed manually if a new object or table has been created in the backend data source. The new object will not be visible until the data model is refreshed.
Enhanced Control for Security
  • The new Crypto Protocol Version connection option allows you to specify a comma-separated list of the SSL and TLS protocol versions that can be used in creating an SSL connection to the Data Source. This parameter applies to On-Premise Data Sources when SSL is enabled using the Encryption Method connection parameter. The client must send the highest version that it supports in the client hello. According to Good security practices, you should use TLSv1 or higher, due to known vulnerabilities in the SSLv2 and SSLv3 protocols.
  • Disabled the SSLv3 protocol on all DataDirect Cloud services and web pages. In a previous release, the SSLv3 protocol was disabled for Web User Interface pages and the interfaces for ODBC, JDBC and OData access to address the POODLE SSL vulnerability. This release disables SSLv3 for the remaining services used for accessing On-Premise data sources. See Alert (TA 14-290A) SSL 3.0 Protocol Vulnerability and POODLE Attack at for more information.

Known Issues

Even with exhaustive testing, not all issues can be immediately resolved. We are working to fix the following:

  • Google Analytics
    • Once a Google Analytics OAuth profile is created for a specific Google account, changing the Google Account associated with the profile results in "the configuration options used to open the database do not match the options used to create the database" error being returned for any existing data sources.
    • In this release, creating a Google Analytics OAuth profile with the Data Source Management API is not supported.
    • When you create a Google Analytics data source and "Authorize with Google", the default view connection option is presented with a list of views for you to choose. The default view affects how DataDirect Cloud generates queries against your Google Analytics data. While executing queries you may receive an error, "No view was specified". If you receive this error, you can set the Create Mapping option to the forceNew value in your data source to work around the error.
  • OData –
    • $expand only supports one level deep.

      For example, with the entity hierarchy:
      |- Orders
      | |- OrderItems
      |- Contacts

      The following queries are supported:

      However, this query is not supported:

      OrderItems is a second level entity with respect to Customers. To query Orders and OrderItems, the query must be rooted at Orders. For example:

    • The table names and column names specified in the ODataSchemaMap data source option are case-sensitive. The case of the table and column names must match the case of the tables and column names reported by the data source.
    • When using the substring function on properties that map to a CHAR column in the data source, it is data source dependent as to whether the substring function treats the trailing spaces as significant. When going against Oracle, the trailing spaces are preserved. When going against other data sources, the trailing spaces are discarded.
    • The $expand clause is not supported with OpenEdge data sources.
    • The day scalar function is not working when specified in a $filter clause when querying a DB2 data source.
  • Oracle Service Cloud
    • When you create a custom object, your Oracle Service Cloud administrator must enable all four columns of the Object Fields tab of the Object Designer, or you cannot query against the custom objects.
    • The initial connection when the relational map is created can take some time. It is even possible to receive an error "504: Gateway Timeout". When this happens, DataDirect Cloud continues to build the map in the background such that subsequent connection attempts are successful and have full access to the relational map.
  • Microsoft Dynamics CRM – The initial on-premise connection when the relational map is created can take some time. It is even possible to receive an error "504: Gateway Timeout". When this happens, DataDirect Cloud continues to build the map in the background such that subsequent connection attempts are successful and have full access to the relational map.
  • On-Premise Connector
    • Uninstalling and re-installing the On-Premise Connector causes the Connector Id of the On-Premise Connector to change. Any DataDirect Cloud data sources using the old Connector Id must be updated to use the new Connector Id. Installing to a new directory allows both the old and new On-Premise Connector to exist side-by-side. However, you must update the Connector Id option in previously-defined DataDirect Cloud data sources to point to the new On-Premise Connector.
    • Changing the name used to register an On-Premise Connector using an older On-Premise Connector Configuration Tool may cause the connector to fail to register itself with D2C and cause 504 Gateway timeout errors to be returned. Installing the latest On-Premise Connector may resolve this issue.
    • It is recommended that Login Timeout not be disabled (set to 0) for a Data Source.
  • Using setByte to set parameter values fails when the data source does not support the TINYINT SQL type. Use setShort or setInt to set the parameter value instead of setByte.
  • Testing has shown the following two errors from Microsoft Dynamics CRM Online when executing queries against the ImportData and TeamTemplate tables:
    • Attribute errortype on Entity ImportData is of type picklist but has Child Attributes Count 0
    • Attribute issystem on Entity TeamTemplate is of type bit but has Child Attributes Count 0
    Note: We have filed a case with Microsoft and are waiting to hear back about the cause of the issue.
  • OpenEdge 10.2b – Setting the MaxPooledStatements data source option in an OpenEdge data store to a value other than zero can cause statement not prepared errors to be returned in some situations.
  • See the files d2cjdbcreadme.txt and d2codbcreadme.txt for the latest notes when accessing DataDirect Cloud through the DataDirect Cloud ODBC and JDBC drivers. These files are located in the installation directory for the ODBC and JDBC drivers.

Third Party Acknowledgments

Third party acknowledgments are listed on the following Web page.

Connect any application to any data source anywhere

Explore all DataDirect Connectors

A product specialist will be glad to get in touch with you

Contact Us