Home Services Partners Company

Release-October 25, 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– October 25, 2014

Key Features and Benefits

DataDirect Cloud provides the following new features for this release.

On-Premise Connector:
  • Added support for connecting through a proxy server.

  • Added a Proxy tab to the On-Premise Connector Configuration Tool to allow you to specify proxy information.

  • Added a Status tab to the On-Premise Connector Configuration Tool to provide a way to test and show the status of the connections and components needed for the operation of the On-Premise Connector.

Changes

  • Google Analytics

    • The localhost Redirect URI is now http://localhost/DataDirectCloud.This local server instance is required for the Token Tool. The redirect URL must be updated in the Google Developer's Console for your Google project. Refer to the DataDirect Cloud help topic "Defining OAuth Authentication for Google Analytics" for more information.

    • The new showDeprecatedObjects mapping option allows you to show dimensions and metrics that Google Analytics has marked as deprecated. Enabling this workaround means that your queries can continue to work while you work on rewriting the queries and table definitions to migrate from the deprecated objects.

    • The new defaultView mapping options was previously a connection option. It allows you to set a valid view name. At connection time, the DataDirect Cloud connectivity service looks up the name and adds a WHERE viewid= to each WHERE clause that supports viewId and does not have an explicit viewId in the user's query.

    • You must set the map option createMap=forcenew for any data sources that have already been created.

Resolved Issues

  • PSC00316235: Resolved an issue where entering a value for the Oracle Service Cloud Login URL that begins with "http://" would cause DataDirectCloud to return "Connection string error at" when trying to connect and would render the data source unusable. The connection will still fail, but now correcting the setting allows subsequent connection attempts to succeed. The value that should be entered for this connection parameter is the host name of the Oracle Service Cloud site to which you are trying to connect; for example, mysite.custhelp.com.

  • PSC00316237: Resolved an "Unexpected token" error when executing a query against Oracle Service Cloud that contains a LIMIT clause after the FROM clause.

  • PSC00316239: Resolved an "ArrayIndexOutOfBoundsException" when executing a stored procedure with an empty argument list against Oracle Service Cloud.

Known Issues

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

  • 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

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

  • Reinstalling the On-Premise Connector changes the Connector ID. Any On-Premise data sources defined in DataDirect Cloud must be updated with the new Connector ID.

  • On-Premise Connector

    • Upgrading an existing installation causes new On-Premise Connecter services to be installed but does not remove the existing services. This causes problems with the On-Premise Connector operation. It is recommended that either the On-Premise Connector be installed to a new directory, or the existing On-Premise Connector be uninstalled and then the new version installed.

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

patch-whats-new

Read Next

What's new