Home Partners Company

Release-July ​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– July 11, 2015

Key Features and Benefits

DataDirect Cloud provides the following new features for this release.

Support for Data Source Groups

A data source group allows you to combine multiple OData enabled data sources to make them look like a single data source. This allows the user to create a single OData service that can access data from multiple data sources. This is useful for applications that restrict the number of OData services they can consume.

New GA Data Sources
SugarCRM
  • The Enable Export Mode map option has been added to improve performance when querying large sets of data. When Export Mode is selected (default behavior), the precision of the timestamp values does not include seconds. When Export Mode is not selected, the precision of timestamp values includes seconds, but performance is slower.
DataDirect Cloud Management API: Data Source API
  • New resources added.
    • datasources/<datasource id/>/members: get, add, and update members to a data source group. Supports the following methods:
      • GET
      • PUT
      • POST
    • datasources/<datasource-id>/members/<member_datasource_id>: deletes a member data source from a data source group. Supports the following method:
      • DELETE
    • datasources/<datasource_id>/model. Creates and refreshes the OData model.
      • A POST request to this end point creates or refreshes the OData model for a data source.  Model creation is Asynchronous
      • A GET request to this end point reports the status of the model creation for the data source.
  • Change to datasources/<datasource_id>/map. The model option for the payload of this endpoint is deprecated. Instead, use datasources/<datasource_id>/model.
DataDirect Cloud Management API: Connectors API
  • The DELETE method has been deprecated for the following endpoints.
    • /connectors/<connector-ID>/authuser
    • /connectors/<connector-ID>/members 
  • To delete one or more connectors from a connector group, issue a PUT request to the /connectors/<connector-ID>/members endpoint and remove the connectors to be deleted from the members array in the request payload.
On-Premise Connector
  • The Resources tab allows you to increase the maximum and minimum memory size, and the number of concurrent requests. Note that in most cases, the default memory allocated to the On-Premise Connector is sufficient.
  • The Version tab of the Configuration Tool allows you to easily identify the version of the On-Premise Connector components.
  • The Configuration Tool can now be launched from the installer. To keep installation of the On-Premise Connector simple, the installer does not prompt the user for every possible configuration setting. Launching the Configuration Tool allows users to further tune their On-Premise Connector. For example, the installer does not prompt the user for the memory and concurrent threads settings shown in the new Resources tab.
DataDirect Cloud JDBC Driver
  • Added support for Statement.Cancel.
DataDirect Cloud ODBC Driver
  • Added support for SQLCancel.

Changes

  • Help Spots in the User Interface

    Help spots have been added to introduce new features. When you click a help spot, a pop-up window is displayed, describing the new features. The window may include navigation buttons to additional help windows. If you want to keep the help window active, click "Remind me later". Otherwise, click "I've got it" to permanently dismiss the help spot.

    In this release, you'll see a help spot on the Data Sources button in the left navigation bar when you first open DataDirect Cloud.

Resolved Issues

  • PSC333696. An error was returned when specifying more than one configOption in the ExtendedOptions field in the setup dialog.
Apache Hive
  • When calling getColumns on a table that contains a decimal column against Cloudera 4.5, a NullPointerException is returned by the DataDirect Cloud Connectivity service.
  • When attempting to use OData against Cloudera 4.5 with a table with a decimal column, the operation might fail.
DB2
  • The ExtendedOptions data source field was shown twice on the DB2 Data Source setup dialog.
OData
  • OData results are now available for up to 10 minutes after the last fetch of data for the result. Previously, OData results were available for 10 minutes after the initial query was executed. The 10 minutes was fixed. This meant that the if the result was large enough that it took longer than 10 minutes to fetch all of the results, you would get an error that the results were no longer available before you got to the end of the results.

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.
Apache Hive
  • When calling getColumns on a table that contains a decimal column against Cloudera 4.5, a NullPointerException is returned by the DataDirect Cloud Connectivity service.
  • When attempting to use OData against Cloudera 4.5 with a table with a decimal column, the operation might fail.
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.
OData
  • The OData metadata description for decimal columns specifies a scale value that is equal to the precision of the column. This causes problems for applications such as Salesforce Lightning connect that expect the Precision to be greater than the scale.
  • The indexOf scalar function returns a value that is off by 1. This will likely cause queries that use indexOf in the $filter query parameter to return incorrect results.
  • $expand only supports one level deep.

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


    The following queries are supported:
    Customers?$expand=Orders
    Customers?$expand=Contacts
    Customers?$expand=Orders,Contacts


    However, this query is not supported:
    Customers?$expand=Orders,OrderItems

    OrderItems is a second level entity with respect to Customers. To query Orders and OrderItems, the query must be rooted at Orders. For example:
    Orders?$expand=OrderItems
    Orders(id)?$expand=OrderItems


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

patch-whats-new

Read Next

What's new