Release-April 11, 2015

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– April 11, 2015

Key Features and Benefits

DataDirect Cloud provides the following new features for this release.

ODBC Driver
  • The new Extended Options field allows you to set the value of undocumented options (WorkAround options) provided by Progress DataDirect Technical Support. This field has been added to the Advanced tab of the ODBC Cloud Driver Setup dialog box. For additional information, refer to the "Advanced Tab Options" topic.
On-Premise Connector
  • Added support for Load Balancing for On-Premise Connectors. In previous releases, the user could define groups of On-Premise Connectors to handle the failure of a particular Connector. When a Data Source failed to connect to an On-Premise Connector, the request would failover to another Connector in the group until successful or all of the Connectors were tried and failed. With this release, Connector groups support both failover and load balancing. Requests to On-Premise Data Sources are directed to all of the On-Premise Connectors defined in a Connector group, balancing the request load across all of the Connectors in the group. A round-robin algorithm is used to determine which Connector in the group a particular request is directed to. In addition, weights can be assigned to the individual Connectors in a group, allowing more traffic to be directed to one Connector versus another Connector if needed. For example, if one Connector is running on a faster server than another, a higher weight can be assigned to the Connector using the faster server. Refer to the "Using Failover and Load Balancing with an On-Premise Connector Group" topic for details.
  • Improved performance and scalability for requests to On-Premise Data Sources.
  • Addressed issues with installing On-Premise Connector updates.

Note: The On-Premise Connector must be upgraded to version 3.0 to be able to use the Connector Load Balancing Functionality and to take advantage of the On-Premise Data Source performance enhancements.

Oracle Service Cloud
  • Now supported with Oracle Service Cloud version February 2015.

Resolved Issues

  • PSC00325855. When connected to Oracle Service Cloud, the service returned an error when querying fields with NULL values in columns where NULL is allowed.

Notes and Known Issues

Even with exhaustive testing, not all issues can be immediately resolved. The following issues have been noted:

All Data Sources
  • 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.
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.

    In addition, you must update Connector Id wherever it was used, such as the definitions of Group Connectors and Authorized Users.

  • 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.
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.

  • The description of the Default View Name field is missing from the help topic for the General tab. Also, the screenshot does not show the Default View Name field.
  • $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:

  • When manually editing the ODataSchemaMap value, the table names and column names specified in the value 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.
    Note: It is highly recommended that you use the OData Schema Editor to generate the value for the ODataSchemaMap data source option. The Schema Editor takes care of table and column name casing and other syntactic details.
  • 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
  • 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.

  • 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.
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.
DataDirect Cloud ODBC and JDBC Drivers
  • 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.


Read Next

What's new