Home Partners Company

Release-November 8, 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– November 8, 2014

Key Features and Benefits

DataDirect Cloud provides the following new features for this release.

On-Premise Connector:

The DataDirect Cloud On-Premise Connector now supports failover. Users can now define groups of On-Premise Connectors using the DataDirect Cloud Management API. An On-Premise Connector Group defines a set of On-Premise Connectors that can be used to provide failover capability if one or more of the Connectors in the group has a problem. The Connector Group defines the list of Connectors in the group, the sequence in which the Connectors are tried, a timeout value that specifies how long to wait for an individual connection to be established, a retry delay and a list of users that are authorized to use the Connector group.

  • When defining an On-Premise data source, a Connector Group ID can be specified as the Connector ID of the data source instead of specifying a specific Connector Id. When a Group Connector ID is used for a data source and a connection is requested for that data source the Data Access Service uses the first On-Premise Connector in the group to establish the connection. If the connection succeeds, the application is successfully connected to the data source. If the connection fails, the DataDirect Cloud connectivity service then uses the next On-Premise Connector in the group to attempt to connect to the data source. If that connection fails, the next connector in the group is used. This continues until a connection is successfully established or all of the On-Premise Connectors in the group have been tried and failed. In the latter case, an error indicating that the connection could not be established is returned to the application. This connection time failover is supported for queries executed from the DataDirect Cloud ODBC driver or JDBC driver, or through the OData API.

  • Failover is also supported at execute time for fetch operations using either the DataDirect Cloud ODBC driver or the DataDirect Cloud JDBC driver. If a SELECT statement is executed and a connection failure or connection timeout occurs during the execution of the statement, the driver attempts to reconnect to the data source, which would trigger the failover sequence above. If the connect is re-established, the SELECT statement is re-executed. The Select failover is not supported if a query is executed through the OData API.

    This functionality is implemented in the cloud-based Data Access Service and works with existing installations of the On-Premise Connector.
Management API: Connector API

New HTTP methods are defined for the following existing On-Premise Connector API URLs.

https://service.datadirectcloud.com/api/mgmt/connectors

Method Description
POST Creates an On-Premise Connector Group

Method Description
DELETE Deletes an On-Premise Connector Group

The following new HTTP methods and URLs were added to the On-Premise Connector API

https://service.datadirectcloud.com/api/mgmt/connectors/<connector-id>/members

Method Description
POST Adds one or more On-Premise Connectors to an On-Premise Connector Group
GET Retrieves the list of On-Premise Connectors contained in the On-Premise Connector Group
PUT Replaces the list of On-Premise Connectors contained in the On-Premise Connector Group with a new list of Connectors
DELETE Removes one or more On-Premise Connectors from an On-Premise Connector Group

The request and / or response payload for the following existing On-Premise Connector API HTTP methods and URLs have changed.

https://service.datadirectcloud.com/api/mgmt/connectors/<connector-id>

Method Description
GET The response now includes a connectorGroup object if the Connector ID references an On-Premise Connector Group. The connectorGroup option contains the connection timeout and retry delay specified for the group, and also contains the list of On-Premise Connectors that make up the group.
PUT The request payload can now optionally include a connectorGroup object if the connector id references an On-Premise Connector Group. The connectorGroup option contains the connection timeout and retry delay specified for the group and also contains the list of On-Premise Connectors that make up the group. The response also now includes a connectorGroup object if the Connector ID references an On-Premise Connector Group

See the Connector API section in the Data Direct Cloud Management API documentation for details of these changes.

Management API: Data Source API
  • Disable OEM end user access to Management API. OEMs now have the option to disable access to the DataDirect Cloud Management API for their end users. If an OEM has disabled access to the Management API, its end users will get an error message if they try to query any of the DataDirect Cloud Management API URLs. Currently ,access to the Management API can be disabled for all or none of an OEM's end users. An OEM must contact Progress Sales or Support to disable end user access to the Management API.

  • Allow an OEM Admin user to create data sources on behalf of its end users. If an OEM has disabled access to the Management API for its end user, the OEM Admin user must create data sources for the end users.

    A new query parameter, user, is now supported by the following existing Data Source API HTTP methods and URLs. See the Data Source API section in the Data Direct Cloud Management API documentation for details of these changes.

    https://service.datadirectcloud.com/api/mgmt/datasources

    Method Description
    POST Creates a data source for the OEM end user specified by the user query parameter

    https://service.datadirectcloud.com/api/mgmt/datasources/<datasource-id>

    Method Description
    GET Lists the data source information for the specified data source that belongs to the OEM end user specified by the user query parameter.
    PUT Updates the data source information for the specified data source that belongs to the OEM end user specified by the user query parameter.
    DELETE Deletes the data the specified data source that belongs to the OEM end user specified by the user query parameter.

    https://service.datadirectcloud.com/api/mgmt/datasources/<datasource-id>/test

    Method Description
    POST Performs a test connect to the specified data source that belongs to the OEM end user specified by the user query parameter

    https://service.datadirectcloud.com/api/mgmt/datasources/<datasource-id>/map

    Method Description
    POST For certain Cloud Data Sources, refreshes schema and/or OData Data Model for the specified data source that belongs to the OEM end user specified by the user query parameter.
POODLE SSLv3

Disabled SSLv3 protocol on the DataDirect Cloud Web User Interface pages and the interfaces for ODBC, JDBC and OData access to address the POODLE SSL vulnerability. See Alert (TA 14-290A) SSL 3.0 Protocol Vulnerability and POODLE Attack at https://www.us-cert.gov/ncas/alerts/TA14-290A for more information.

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

    • 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