TIBCO® Data Virtualization (TDV) 8.8.1
Open Documentation View Release Notes
The TIBCO® Data Virtualization (TDV) 8.8.1 release has three distribution types:
- On-premises installations that utilize our platform specific installer binaries or patch archives.
- Container and Kubernetes runtime environments that use our container distribution (i.e. Docker files and Helm charts). The container distribution can be used in private and public cloud environments (for example, Azure).
- AWS Marketplace offering for those that don’t want to manage nor host a TDV installation.
For more information on the products and components included in TDV, refer to the TDV Installation and Upgrade Guide. For more information on the products and components in Business Directory, refer to the TDV Business Directory Guide.
TDV 8.8 is a Long Term Support Release. For information about the TDV LTS Support refer to TIBCO Data Virtualization Long-Term Support (LTS) Releases.
TDV 8.8.1 includes features and enhancements in the following areas.
Server Improvements
- Caching Improvements:
- In-progress cache refreshes can now be canceled in TDV Studio manually or programmatically by invoking an API.
- Access control for cached resources have been streamlined.
- Direct references to cache target table(s) are prohibited, allowing them only as replacements for cached resources.
- The CACHE RESOURCES page of the Web Manager now has a Message column that provides more details about the Cache cancel operations.
- Workload Management - Provision has been made to create request limit rules on users groups and claims.
- BCP files will be cleared automatically after a TDV Server restart.
- Server runtime monitoring - Status log has been enhanced with thread dumps to capture wait/blocking times and to capture server start time/up time.
- JSON_TABLE function has been extended to include COSTREAM ARRAYS clause with INDEX-ing support.
- A new configuration has been included to set a wildcard identifier to be used with JSON_TABLE row paths.
- TDV Server has been upgraded to use JDK-17.0.13.
Security
- Principal Restrictions
- The existing access control model has been extended to prevent direct access to data source assets.
- Privilege management has been streamlined - Column-level privileges are implicitly maintained only once they have been explicitly set by the user.
- Controls in Studio have been simplified to allow for the scope of resources onto which the changes should be applied and the scope of privilege changes to be applied to be selected independently.
- READ privileges are automatically assigned on parent and ancestor containers when it is detected that any of SELECT, INSERT, UPDATE, DELETE or EXECUTE privileges are assigned on a given resource - The same implicit assignments are applied when privilege assignment is propagated on dependencies and/or dependents.
- PAM Module improvements
- Login requests routed through the PAM module will now be applied only to the users who belong to the specific domain that has been configured to use the module.
- The PAM login module will now also fetch the client IP address (in addition to the account credentials) to validate the clients attempting to access TDV.
- SSL Certificate-based authentication - TDV 8.8.1 will support certificate-based (client-based) authentication using a mapping table. Previously any user found in the certificate key chain was allowed access to TDV. With this new functionality, an additional check is implemented for an attribute of the certificate with a mapping table that contains information about TDV principals.
- Azure domain support in TDV has been migrated from the ADAL to MSAL library..
KPI Module Improvements
- The Description column of the metrics_requests table can be searched for matching results.
- An hourly retention of KPI metrics has been added to the Metrics configuration screen.
- Query plan column has been added to the metrics_requests table.
Data Source Improvements
Documentation Enhancements
- A Troubleshooting Guide has been provided to include some Frequently asked questions and a possible solution that was provided in the past to help resolve the issue.
- User Guide documentation has been improved to include specific instructions on the resources that should and should not be saved under the My Home directory of the Studio Modeler Resource Tree.