...
The Authorization Server uses a platform to run and can be configured to store provisioned scopes and registered clients either in file-based storage or database storage. Currently, only Oracle and PostgreSQL databases are supported for database storage, see https://infozone.atlassian.net/wiki/spaces/MD92/pages/109478291/Authorization + Server + User+'s + Guide.
Anchor | ||||
---|---|---|---|---|
|
...
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 Agent Configuration or Encoder Agent 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.
Anchor | ||||
---|---|---|---|---|
|
...
Pico
Debug
APL
Error
See Log Files for details abou about the Log Files view.
Scroll pagebreak |
---|
...
With the, mzsh desktopadmin
command you can shut down all Deskops and Legacy Desktops connected to the Platform, see desktopadmin.
Anchor | ||||
---|---|---|---|---|
|
...
Ref: XE-10621
A new dialog with downloadable items have now been added to make it easier to download the Desktop Launcher , mzcli client and DevKit.
...
You can open the dialog from the User Settings menu, see User Settings.
...
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.
Anchor | ||||
---|---|---|---|---|
|
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 for more information.
Scroll pagebreak |
---|
Anchor | ||||
---|---|---|---|---|
|
...
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 Agent for more information.
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Support for Python 3.12 has now been added when using the Python Agents.
Scroll pagebreak |
---|
Anchor | ||
---|---|---|
|
...
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.
Anchor | ||||
---|---|---|---|---|
|
Ref: XE-13526
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 Profile for more information.
Configurable Maximum Response Size for HTTP/2 Client
Ref: XE-13740
Users can now set a maximum size limit for responses received by the HTTP/2 Client. To configure the maximum response size, use the Max Response Content Length field introduced in the Client tab of HTTP/2 Client agent configuration.
See HTTP/2 Client Agent Configuration for more information.
Data Type Conversion Property for SAP JCo ABAP Type P
Ref: XE-14878
A new property is introduced to define the data type used for converting values when mapping to SAP JCo ABAP Type P (Binary Coded Decimal). The saprfc.bcd.double
property provides flexibility to users in handling data types.
See Execution Container Properties for more information. 
SAP RFC Processor Agent Supports Execution Time Threshold Configuration
Ref:XE-14268
Two additional options; the Enable Logging for Execution Exceeding Time Threshold checkbox and Execution Threshold Time (min) field are added to the SAP RFC Processor agent configuration to allow users to configure the execution time threshold.
When an RFC Function takes too long, any attempt to abort the workflow will be logged in the System Log.
See SAP RFC Processor Agent Configuration for more information.