Protegrity client has been extracted to a new Script-Languages-Container

Detail name	Value
Changelog Number	30332
Type	Improvement
Status	Open

Background

In order to enable customers to exchange and update the protegrity client, the protegrity-binaries were removed from the Database package. They are now available as separate Script-Language-Container.

Improvement

The new Protegrity client can be installed as a Script Languages Container in BucketFS (see Adding new packages to existing script languages). As a result, the activation syntax has changed slightly (specifically the ALTER SESSION command), while the Protegrity UDFs remain unchanged.

The Protegrity SLC can be provided to customers on demand. Please contact Exasol Support if you need to use this functionality.

Changed behavior

1. Protegrity Binaries need to be installed separately as a Script-Languages-Container into BucketFS 2. The activation syntax changed from a) `SCRIPT_LANGUAGES='... PROTEGRITY=udfplugin:///applicationprotector_rest ...'` => `... PROTEGRITY=localzmq+protobuf:///<path_to_protegrity_slc_in_bucketfs>#/exaudf/main/protegrity ...` b) `SCRIPT_LANGUAGES='... PROTEGRITY_UA=udfplugin:///applicationprotector_rest_ua ...'` => `... PROTEGRITY_UA=localzmq+protobuf:///<path_to_protegrity_slc_in_bucketfs>#/exaudf/main/protegrity_ua ...` The Protegrity SLC can be provided to customers on demand. Please contact Exasol Support if you need to use this functionality.