New Features and Functionality (4.1)
- Jenni Wallin
- Yeok Hong Ng (Deactivated)
- Yuri Au Yong
In this section, you can see information about the new features and functionality in this release.
- 1 New Features
- 2 Enhancements
New Features
The following new functionality has been added in this release:
Authentication and Access
Access Controller - Access Group Name
Ref: XE-12026
To support additional IDP setups, we have now added the possibility to use a dot (.) in the Access Group name. The valid characters are A-Z, a-z, 0-9, '-', '.' and '_', see Groups Tab(4.1).
Support for 2-way Authentication for Web Services Agents and Profiles
Ref: XE-11679
The Web Services agents and profiles now have the option to use mutual TLS for enhanced security, see Web Service Profile (4.1) and Web Service(4.1).
New Connectors
Netia FTP Agent
Ref: XE-11802
The Netia FTP agent is now available which is a collection agent for batch workflow configurations. With the Netia FTP agent you can collect files from remote file systems and forward into a workflow using the standard FTP (RFC 959) protocol, see Netia FTP(4.1).
Telco agents for FTAM and FTP
Ref: XE-6131, XE-6135, XE-6136, XE-6137
In Usage Engine there are now four new batch agents, FTAM Ericsson IOG, FTAM Siemens EWSD, FTP Nokia DX200, and FTP Nokia NMSC.
Integration
Avro Encoding and Decoding
Ref: XE-11766
New built-in decoders and encoders have been added for decoding and encoding messages encoded in Avro using a schema registry, replacing the need to write a static Ultra definition, see Decoder(4.1), Encoder(4.1), and Avro Decoder/Encoder(4.1) for decoder or encoder-specific information. Additionally, several limitations on supported Avro schema types in the existing Ultra support have been removed, see Avro Support(4.1).
BER Indefinite Lenght Encoding
Ref: XE-12419
W now support encoding ASN.1 to BER using Indefinite Length encoding, which is a first step towards fully supporting CER (Canonical Encoding Rules), see External - ASN.1 Formats(4.1)
MariaDB Support
Support for using MariaDB has now been added in a couple of areas.
MariaDB in Database Profile
Ref: XE-13110
The MariaDB database type can be used with Reference Data Management. In order to use this database type, a database driver is required to connect to the MariaDB database. This driver must be stored in the platform container. See MariaDB (4.1) for more information.
Reference Data Management Supports MariaDB
Ref: XE-13109
The Reference Data profile allows you to select the tables to be available for querying and editing via the Reference Data Management dashboard or RESTful interface. You can now select MariaDB in the Reference Data profile configuration, see Reference Data Profile (4.1).
Database Table to Support tableGetMetaInfo Function
Ref: XE-11719, XE-11756
The database table now supports the tableGetMetaInfo function. This function returns the column name, column type and index status for a given table object in a given table, see Database Table Functions (4.1) .
Log Files UI
Ref: XE-13132
You can now view the following log files in Desktop:
Pico
Debug
APL
Error
See Log Files (4.1) for details about the Log Files view.
Enhancements
The following enhancement of existing features has been included in this release.
SAP HANA
Duplicate UDR Supports SAP HANA and PostgreSQL Database
Ref: XE-11761
When using Duplicate UDR you can now select between file system or database for storing information pertaining to Duplicate UDRs, such as the metadata and the contents of the duplicated UDRs when configuring the Duplicate UDR profile, see Duplicate UDR (4.1) for more information.
Data Veracity Supports SAP HANA Database
Ref: XE-11751
Data Veracity now allows you to store all Data Veracity records and metadata in SAP HANA. You can now select Database profiles configured with SAP HANA on the Data Veracity profile.
Data Veracity agents will also now be able to connect to SAP HANA to manipulate any Data Veracity records stored on the database, see Data Veracity (4.1).
5G
5G Profile Supports Multiple Primary NRF Address in HTTP/2 Server Agent
Ref: XE-11675
When using the 5G profile in HTTP/2 Server agent, you can enter one or more primary NRF addresses in the NRF Address (Primary) table, see HTTP/2 Server Agent Configuration(4.1).
5G Profile Allows Retry for Failed Connections to Multiple NRF Address in HTTP/2 Server Agent
Ref: XE-12222
When multiple NRF addresses are used in 5G profile in HTTP/2 Server agent, users can configure the number of retries and interval for a failed NRF address before the agent proceed to connect to the next available address. This can be done by selecting the new Enable Registration Retry option in the 5G tab.
See HTTP/2 Server Agent Configuration(4.1) for more information.
Dynamic Fields in Aggregation Profile
Ref: XE-12669
It is now possible to configure the Aggregation profile with dynamic fields in the Advanced Properties tab using ${} syntax, see Aggregation (4.1) and
Kafka Agents Support mTLS
Ref: XE-11722
You can now configure to use mTLS in Kafka agents, see https://docs.cloudera.com/documentation/kafka/latest/topics/kafka_security.html for more information.
User Security Improvements
Ref: XE-12201
Enhanced user security is now enabled by default upon deployment of the Platform pod. The property mz.security.user.control.enabled is now set to true in the values.yaml file.
Furthermore, the enhanced user security property mz.security.user.password.reset.enabled has been removed. With the property removed, by default, any new users registered into the system will now be prompted to change their password on their first login.
See Enhanced User Security (4.1) for more information.
Support for OpenShift 4.15
Ref: XE-8557
OpenShift is now updated to support version 4.15. For more information, see System Requirements - OpenShift.