...
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.
...
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.doubleproperty provides flexibility to users in handling data types.
See Execution Container Properties for more information.