Release Notes for Red Hat Integration 2020.Q1

Red Hat Integration 2020.Q1

What's new in Red Hat Integration

Red Hat Integration Documentation Team

Abstract

Describes the Red Hat Integration platform and provides the latest details on what's new in this release.

Chapter 1. Red Hat Integration

Red Hat Integration is a unified platform for cloud-native integration and application development with end-to-end API lifecycle support. This platform provides a set of agile and flexible integration and messaging technologies that include:

  • API connectivity
  • Data transformation
  • Service composition and orchestration
  • Real-time messaging
  • Cross-datacenter message streaming
  • API management

Red Hat Integration connects applications, data, and devices across hybrid cloud architectures and delivers API-centric business services.

Chapter 2. New features

This section provides a summary of the key new features in Red Hat Integration 2020.Q1 and provides links to more detailed information on new features available in different components.

2.1. Key features

Apache Kafka
Data integration
OpenAPI 3.0
  • Red Hat Integration components support OpenAPI 3.0 and OpenAPI 2.0

2.2. Component features

For more details on what’s new in Red Hat Integration 2020.Q1 components:

Chapter 3. Debezium

Red Hat Integration 2020.Q1 includes a General Availability release of Debezium on OpenShift based on the Debezium open source project. Debezium is a distributed platform that monitors databases and creates change event streams. Debezium is built on Apache Kafka and is deployed and integrated with AMQ Streams.

Debezium captures row-level changes to a database table and passes corresponding change events to AMQ Streams. Applications can read these change event streams and access the change events in the order in which they occurred.

3.1. Database connectors

Debezium provides connectors based on Kafka Connect for the following common databases:

  • MySQL
  • PostgreSQL
  • SQL Server
  • MongoDB

When trying out the database connectors, the following database versions are recommended for this release:

Table 3.1. Recommended database versions for Debezium

DatabaseVersion(s)

MySQL

5.7, 8.0

PostgreSQL

10, 11, 12

MongoDB

3.6, 4.0, 4.2

SQL Server

2017

Note

For PostgreSQL deployments, you can use the pgoutput logical decoding output plugin, which is the default for PostgreSQL versions 10 and later.

3.2. Installation options

You can install Debezium with AMQ Streams on OpenShift or RHEL:

Important

Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend implementing any Technology Preview features in production environments.

This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope.

Chapter 4. Data Virtualization

Data Virtualization is available as a Technology Preview feature in Red Hat Integration 2020.Q1. Data Virtualization is a container-native service, based on the Teiid open source project, that provides integrated access to a range of data sources, including relational databases, MongoDB, and Salesforce, through a single uniform API.

Applications and users connect to a virtual database over standard interfaces (OData REST, or JDBC/ODBC) and can use SQL to interact with the integrated data in the same way that they would interact with a single relational database.

Important

Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend implementing any Technology Preview features in production environments.

This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope.

4.1. Enhancements

Red Hat Integration 2020.Q1 provides the following enhancements for Data Virtualization:

  • Improved Data Virtualization Operator deploys virtual databases from Maven artifacts (fat JAR, DDL) or embedded DDL.
  • TLS/SSL X.509 certificate encryption of JDBC/ODBC endpoints uses either custom certificates or OpenShift service certificates to encrypt traffic between database clients and a virtual database.
  • New monitoring capabilities automatically collect data virtualization metrics and expose them to Prometheus.
  • Added data source compatibility.
  • New user documentation:

4.2. Known issues

ENTESB-13462 - FORMAT functions for different versions of the Data Virtualization Operator return different results

When you use format functions such as FORMATBIGDECIMAL or FORMATDOUBLE to query a virtual database, the results that the functions return for negative numbers might not be formatted as expected. The format of the result depends on the underlying Java version specified by the Data Virtualization Operator. Because recent versions of the Operator switched from using Java 8 to Java 11, you might experience changes in the formatting of your query results.

In Java versions earlier than Java 11, regardless of whether you specify a minus sign character (-) as a prefix or suffix of a negative format pattern, the returned negative result string is preceded by a minus sign. However, in Java 11, if you append a minus sign to a negative format pattern, the result string that is returned has the minus sign appended to it.

If you obtain unexpected results for negative numbers that a parsing or formatting function returns, revise the pattern string for the function so that the minus sign precedes the rest of the pattern.

Example:

The following query specifies the negative format pattern, #,0;#0-.

SELECT FORMATBIGDECIMAL((99 - 10000000), '#,##0;###0-')

Depending on the version of the Operator, one of the following results is returned:

DV Operators using Java 8
-9,999,901
DV Operators using Java 11

9,999,901-

To achieve the same result as with Java 8, modify the formatting pattern for the query to ,#0;-#.

ENTESB-13144 - Redirect URLs set for virtual databases in Red Hat Single Sign-On do not work

Redirects that you configure for the data virtualization service in Red Hat Single Sign-On are not working correctly.

For OData clients to establish secure connections to endpoints of a virtual database, the data virtualization service must be able to authenticate security tokens that it receives from Single Sign-On. Currently, because the data virtualization service is unable to read TLS/SSL certificates from Single Sign-On, attempts to validate the tokens on a secure channel are unsuccessful.

As a temporary workaround, disable secure connections between the data virtualization service and Single Sign-On by adding the following property to the custom resource (CR) for the virtual database, and then redeploy the virtual database:

  - name: KEYCLOAK_DISABLE_TRUST_MANAGER
     value:  "true"

Afterwards, use a tool such as Postman to issue the OData HTTP requests to the service endpoint. Browser clients cannot connect to the endpoint.

Important

This setting prevents Data Virtualization from validating SSO certificates over secure HTTPS. However, the certificate itself is exchanged over a secure connection. The unsecured HTTP connection is for validation only, and applies to an internal OpenShift server channel. Single Sign-On continues to transmit the token to the Data Virtualization service over a secure channel. This setting should only be used for development and is not for use in a production environment.

4.3. Migration considerations

You can migrate virtual database that you developed for JBoss Data Virtualization or Teiid deployments. For information about migrating legacy virtual databases to Data Virtualization, see Using Data Virtualization.

Chapter 5. Service Registry

Service Registry is available as a Technology Preview feature in Red Hat Integration 2020.Q1. Service Registry is a datastore for standard event schemas and API designs that is based on the Apicurio Registry open source community project. Developers can use Service Registry to manage and share the structure of their data using a REST interface. For example, client applications can dynamically push or pull the latest updates to or from Service Registry without needing to redeploy.

You can also use Service Registry to create rules that govern how registry content evolves over time. For example, this includes rules for content validation and version compatibility.

Important

Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend implementing any Technology Preview features in production environments.

This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope.

5.1. Enhancements

Service Registry provides the following enhancements in this Technology Preview:

Maven plug-in
Integrates Service Registry functionality with a standard Maven build and provides register and download actions.
Kafka Streams storage
Supports storage in Red Hat AMQ Streams 1.4 or 1.3 using a Kafka Streams-based image.
Kafka Connect
Provides Kafka Connect converters for Apache Avro and Kafka Connect JSON schemas.
Additional serializer/deserializers (SerDes)
  • JSON Schema SerDes - Supports optional validation during serialization/deserialization.
  • Protobuf SerDes - Uses the File Descriptor and DynamicMessage support in Google Protobuf to implement serialization/deserialization.
Additional artifact types
  • Protobuf File Descriptor - An additional artifact type that stores the binary Protobuf File Descriptor format.
  • GraphQL - GraphQL schema artifacts can be added to Service Registry. Syntax validation is supported.
  • Kafka Connect schema - Kafka Connect has its own schema format for JSON data, which is similar to Avro. Syntax validation is supported.
Artifact lifecycle states
Artifacts have the following states: ENABLED, DISABLED, and DEPRECATED. The Registry REST API has a new endpoint to manipulate the state of an artifact.
Canonicalization
When searching for an artifact version by content, Service Registry canonicalizes the content so that it does not need to be byte-identical. The content only needs to be functionally equivalent.
New user documentation

Chapter 6. Red Hat Integration Operators

Red Hat Integration provides Operators to enable you to automate the deployment of Red Hat Integration components on OpenShift. This section provides links to detailed information on how to use Operators for different components.

6.1. Fuse Operators

6.2. 3scale Operators

6.3. AMQ Operators

6.4. Data Operators

Additional resources

For more details on Operators in OpenShift:

Legal Notice

Copyright © 2021 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.