Home Partners Company

Release-May 7, 2016

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.

For an overview of features in the March 26, 2016 product release, see the Release Notes at Release-March 26, 2016.

DataDirect Cloud– May 7, 2016

New Features

DataDirect Cloud Management API
  • Enhanced capabilities for the OAuthProfiles Get Statistics API. Previously, the API returned only the number of data sources that use the specified OAuthProfile. Now it can returns additional useful information such as the ID of the data store, and the ID, name, and description of the dataSource.

    The sample server response definition is defined as:

    {
       "dataSourcesLinked": <count>,
       "dataStoreId": <id>,
       "dataSources": [
       {
          "id": <dataSourceId>,
          "name": "<datasourcename>",
          "description":"<description>"
       },
       {
       ...
       }
     ]
    }
    

     

Oracle Service Cloud
  • Web Service Fetch Size connection option has been added to the Advanced tab of the data source setup definition. Adjust the value for this option to get rid of a “poor performing query” error.
ODBC Driver
    Updated to use version 1.0.2g of the OpenSSL library, which fixes the following security vulnerabilities:
    • "missing Memory allocation success checks in doapr_outch function in crypto/bio/b_print.c" (CVE-2016-2842)
    • "Cross-protocol attack on TLS using SSLv2 (DROWN)" (CVE-2016-0800) 
    • "memory issues in BIO_*printf functions" (CVE-2016-0799)
    • "Memory leak in SRP database lookups" (CVE-2016-0798)
    •  "Double-free in DSA code" (CVE-2016-0705)
    • “Side channel attack on modular exponentiation" (CVE-2016-0702)

    For more information, refer to the OpenSSL announcements at https://www.openssl.org/news/secadv/

    Resolved Issues

    OData
    • When configuring OData Search options in the OData Schema Map Editor, the Search index type menu is no longer empty. This issue applied to DB2 and Microsoft SQL Server data stores.
    ODBC Driver
    • 37622. DataDirect Cloud ODBC driver installation failed on CentOS.
    On-Premise Connector
    • The support matrix has been updated to clarify that installing a 32-bit On-Premise Connector on a 64-bit Windows machine is not a supported configuration.
    SugarCRM
    • The Map Option enableExportMode has been removed from the configuration dialog. The default behavior has changed from true to false, that is, Export Mode is not enabled. Any existing data sources that were created using the previous default behavior will maintain that behavior. It is highly recommended that you migrate to a configuration with the new default behavior. This can be accomplished by deleting configOptions=(enableExportMode=true) from your data source.

    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 DataDirect Cloud 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.
    • Validation message is not displayed when a user enters a Start Date value less than the End Date value in Create/Update Google Analytics page.
    OData
    • $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.
    SugarCRM
    • Data sources that are using the deprecated enableExportMode option will still see a problem until they are migrated to the new data source configuration.
    DataDirect Cloud JDBC Drivers
    • See the file d2cjdbcreadme.txt for the latest notes when accessing DataDirect Cloud through the DataDirect Cloud JDBC drivers. These files are located in the installation directory for the JDBC drivers.
    DataDirect Cloud ODBC Drivers
    • See the file d2codbcreadme.txt for the latest notes when accessing DataDirect Cloud through the DataDirect Cloud ODBC drivers. These files are located in the installation directory for the ODBC drivers.

    Third Party Acknowledgments

    Third party acknowledgments are listed on the following Web page.

patch-whats-new

Read Next

What's new