New Features
The following features have been added in this release of TIBCO DataSynapse GridServer® Manager:
Release Type & Core Support
Long-Term Support (LTS) Support
DataSynapse GridServer® Manager 7.2.0 is a LTS Release. For more information about the DataSynapse GridServer® Manager LTS Support, see TIBCO LTS Policy.
Azul OpenJDK Integration
Azul Java 17.0.12 is now fully supported across all GridServer components.
Note:
Oracle Java 17 is the default Engine JRE for Win64 and Linux64.
-
When running the Engine on Azul Java 17 you need to configure specific JVM parameters for the Engine and Driver Software Development Kit (SDK) components. Grid-library support is available for Linux 64-bit and Windows 64-bit.
-
No installation or configuration changes are required for the Broker and Manager to support Azul OpenJDK 17.
Apache Tomcat® Upgrade
The bundled Apache Tomcat server has been upgraded to version 9.0.113.
Platform, Component, & Compiler Upgrades
Additional Platform Support
DataSynapse GridServer® Manager 7.2.0 is now supported on Rocky Linux 10, Red Hat Enterprise Linux (RHEL) 10, and Windows Server 2025.
Component Upgrades
To ensure optimal security and performance, the following third-party dependencies have been upgraded:
-
Python 3.10.6 applies to Python Bridge, drivers, and associated examples.
-
.NET 8
-
OpenSSL 3.0.14
New Compiler Support
Integration for modern compilers has been added to leverage the latest features and optimizations for third-party libraries. This includes GCC 11.5 for Linux and VC17 for Windows. For the updated list of supported TIBCO Software, platforms, and third-party software, see the Readme file provided with TIBCO DataSynapse GridServer® Manager.
High Availability Enhancements
Secondary Director Acts as Primary
Failover reliability has been significantly enhanced. In the event of a Primary Director outage, the Secondary Director now automatically assumes the Primary role and can execute the following critical operations:
-
Update Broker configurations (including modifying Broker sharing)
-
Update Engine and Engine Daemon configurations
-
Add new Brokers to the GridServer.
-
Perform Grid Libraries Deployment
-
Manage the Service Type Registry
Comprehensive REST API Additions
This release vastly expands the programmatic control by introducing new REST APIs that mirror functionalities previously only available through the user interface:
Broker Admin and Configuration
New APIs support all Broker Admin capabilities. A notable addition is the
updateBrokerConfigurationAPI, enabling programmatic modifications to broker settings. Additionally, a purge-broker API has been introduced.
Broker Routing
The administrators can now list, add, delete, or update routing details by performing CRUD (Create, Read, Update, Delete) operations on broker routing properties.
Engine Configuration
You can now programmatically adjust Engine parameters and log levels without interacting with the user interface.
EngineDaemonAdmin
The offline Engine Daemons can be efficiently removed from the Director. This is specifically designed for automated daemon management in cloud environments characterized by frequent provisioning and de-provisioning.
Run-As Credential
You can programmatically retrieve a list of Run-As Credential users, as well as add or delete a Run-As credential user.
Added REST API for Manager Diagnostics Logs
Access a new programmatic method for fetching integration and troubleshooting data, including Manager Logs, Environment configurations, and Task Queues.
Service Logs and Service Admin
You can search service logs for specific service sessions to monitor instances and retrieve the
grid-library.xml configuration file for designated grid libraries.
Added REST API for Service Test
A new endpoint allows users to trigger Linpack tests directly for the job admin scheduler.
User Interface (UI) Improvements
Altered Configuration Highlighting
A configuration row is highlighted if the value is altered after comparing it with the system's default value, allowing the administrators to identify easily customized settings.
Table Row Numbering
To improve data visibility and ease of navigation, row numbers have been added to tabular pages across the application. This includes, but is not limited to the following UI pages:
-
Engine Daemons
-
Engine Admin
-
Service Types
-
User Admin
Changes in Functionality
The following changes in functionality have been made in this release of TIBCO DataSynapse GridServer® Manager:
Windows Engine Deployment
DataSynapse GridServer® Manager 7.2.0 introduces a new installation process for the Windows Engine. This update provides a unified experience that mirrors the existing Linux Engine installation workflow. The Windows Engine installer is delivered as a
.tar.gz archive. This packaging ensures consistent delivery across different operating systems. You can now manage engine installation and execution on Windows using a built-in command-line interface.
Updated Windows Runtime Dependencies
Updated the application runtime requirements by replacing legacy Visual C++ 2013 libraries (
msvcp120.dll, msvcr120.dll) with Visual C++ 2015-2022 redistributables (msvcp140.dll, vcruntime140.dll). This change ensures full compatibility and optimized performance across modern environments, including Windows Server 2016 through Windows Server 2025.
Updated Build Tooling Requirements
In DataSynapse GridServer® Manager Software Development Kit (SDK), all the core C++ and .NET components are now bundled with Visual Code 16. However, to maintain developer flexibility, the provided SDK example projects continue to be bundled with Visual Code 15 build configurations. You should ensure that the appropriate redistributables are installed for their target environment.
.NET Runtime Update
DataSynapse GridServer® Manager 7.2.0 introduces an upgrade to the underlying .NET runtime. The platform now supports .NET 8, moving from the previous .NET 6 version. This update affects both the .NET driver and the .NET bridge components. This ensures compatibility with the latest .NET framework. For details on changes in functionality since the last major release of this product, see the section Upgrading GridServer in the TIBCO DataSynapse GridServer® Manager Installation Guide.
Deprecated and Removed Features
The following feature has been deprecated or removed as of this release of TIBCO DataSynapse GridServer® Manager:
Removed Features
Removed Support for 32-bit Artifacts
DataSynapse GridServer® Manager 7.2.0 no longer supports 32-bit artifacts. This change impacts Windows (Win32) and Linux platforms.
Removed Support for SOAP APIs
The SOAP API functionality has been deprecated and so the support for SOAP API is removed from the Gridserver. The following table lists the removed SOAP APIs and their corresponding REST API replacements: | SOAP API | REST API | | --- | --- | | com.datasynapse.gridserver.admin.BatchAdmin | com.datasynapse.gridserver.rest.BatchAdmin. | | com.datasynapse.gridserver.admin.BrokerAdmin | com.datasynapse.gridserver.rest.BrokerAdmin | | com.datasynapse.gridserver.admin.DriverAdmin | com.datasynapse.gridserver.rest.DriverAdmin | | com.datasynapse.gridserver.admin.EngineAdmin | com.datasynapse.gridserver.rest.EngineAdmin | | com.datasynapse.gridserver.admin.EngineDaemonAdmin | com.datasynapse.gridserver.rest.EngineDaemonAdmin | | com.datasynapse.gridserver.admin.ManagerAdmin | com.datasynapse.gridserver.rest.ManagerAdmin | | com.datasynapse.gridserver.admin.ServiceAdmin | com.datasynapse.gridserver.rest.ServiceAdmin | | com.datasynapse.gridserver.admin.UserAdmin | com.datasynapse.gridserver.rest.UserAdmin | | com.datasynapse.webservices.gridserver.admin.BatchAdmin | com.datasynapse.webservices.gridserver.rest.BatchAdmin | | com.datasynapse.webservices.gridserver.admin.BrokerAdmin | com.datasynapse.webservices.gridserver.rest.BrokerAdmin | | com.datasynapse.webservices.gridserver.admin.DriverAdmin | com.datasynapse.webservices.gridserver.rest.DriverAdmin | | com.datasynapse.webservices.gridserver.admin.EngineAdmin | com.datasynapse.webservices.gridserver.rest.EngineAdmin | | com.datasynapse.webservices.gridserver.admin.EngineDaemonAdmin | com.datasynapse.webservices.gridserver.rest.EngineDaemonAdmin | | com.datasynapse.webservices.gridserver.admin.ManagerAdmin | com.datasynapse.webservices.gridserver.rest.ManagerAdmin | | com.datasynapse.webservices.gridserver.admin.ServiceAdmin | com.datasynapse.webservices.gridserver.rest.ServiceAdmin | | com.datasynapse.webservices.gridserver.admin.UserAdmin | com.datasynapse.webservices.gridserver.rest.UserAdmin |
Migration and Compatibility
The following information provides migration procedures and a compatibility matrix for this release of TIBCO DataSynapse GridServer® Manager:
.NET Runtime Update
In DataSynapse GridServer® Manager 7.2.0, the underlying .NET runtime has been upgraded from .NET 6 to .NET 8. This update affects both the .NET driver and the .NET bridge components. There is no change to the configured serviceType. The value NET5 continues to be used for .NET-based services and remains valid. Internally, it now targets .NET 8. Ensure that your application code, libraries, and dependencies are compatible with .NET 8. Projects must be recompiled to guarantee compatibility and runtime stability. For details on how to migrate from a previous release to the current release, see the section Upgrading GridServer in the TIBCO GridServer® Installation Guide.
Closed Issues
The following issues have been fixed in this release of TIBCO DataSynapse GridServer® Manager:
C++ Specific
| Key | Summary |
|---|---|
| GS-17793 | The OpenSSL library requires an updated version 3.x. |
Documentation
| Key | Summary |
|---|---|
| GS-15287 | C++ API documentation is not consistent with the Java API documentation . In the Java API, Service and ServiceInvocationHandler methods consistently return an invocation ID. However, the C++ API documentation used varying terms, including handler id, id, service id, and invocation id (new invocation id)'. |
Drivers-All
| Key | Summary |
|---|---|
| GS-18964 | There is an issue where the DSDriver in GridServer 7.1.0 would overwrite the Root Logger level settings of integrated Java applications. The driver.properties file often defaulted to a Finest logging level, which caused rapid disk storage consumption. the DSLogLevelOverWritten parameter If the GridServer application is integrated within another Java application and you want to prevent the overwriting of Root Logger level setting with GridServer Log Level setting, then set The DSLogLevelOverWritten parameter is introduced to prevent the GridServer Log Level setting from overwriting the Root Logger level setting. When you set this parameter to false, the DataSynapse Logger does not change the Root Logger level. When you set the DSLogLevelOverWritten parameter to false, the DataSynapse Logger does not change the Root Logger level. |
| GS-16447 | A security vulnerability is identified in the driver's internal web server ports. This issue involved an XSS vulnerability in the driver when you access the driver's file sharing port through HTTP. |
Engine
| Key | Summary |
|---|---|
| GS-19271 | You must install the required Visual C++ Redistributable libraries as a prerequisite for Engine installation. The legacy Visual C++ 2013 runtime DLLs (msvcp120.dll, msvcr120.dll) are replaced with Visual C++ 2016 and later runtime DLLs (msvcp140.dll, vcruntime140.dll). |
| GS-19242 | The Python example of Linux64 failed to run. A Python ServiceInvocationException is observed with the message, Task failed after 3 retries. Last failure: Engine crashed. This issue occurs when setting up a combo server, configuring the linux64 engine, extracting the linux64 SDK, and running the Python example after exporting LD_ LIBRARY_PATH and PATH variables. To resolve this issue, changes were implemented to set correctly the ds.PYTH_MODULE_PATH environment variable. The setManagerProperties method calledaddProperties method now tracks whether the password is already encoded, preventing double encryption and the Invalid Password error. |
| GS-18969 | When the primary director is down, the secondary director becomes Acting as Primary. In such a case, the secondary director is not able to perform the following operations: - Update Broker configurations (change broker sharing) - Update Engine configuration - Update Engine Daemon configuration - Add a broker to the grid. - Perform Grid Libraries Deployment |
Manager
| Key | Summary |
|---|---|
| GS-18910 | A new parameter needs to be added to handle Browser active session timeout. |
| GS-18844 | When a single Driver submits multiple jobs, some jobs containing a large number of tasks could cause delays in the completion of other jobs with a smaller number of tasks. To mitigate this issue, a new configuration parameter, Equal weight tasks dispatch is introduced that ensures more equitable task dispatching. If a small job takes longer than the usual time to complete, then setting the Equal weight tasks dispatch parameter to true prevents delays in the completion of smaller jobs, even when a large job has many tasks. The default value of the Equal weight tasks dispatch parameter is false. |
| GS-18610 | Critical and high-priority Common Vulnerabilities and Exposures (CVEs) detected in the Manager and Engine components are resolved. AngularJS updated version 1.8.3 enhances UI stability and security. |
| GS-17648 | You cannot assign a role to an LDAP user if no email is entered. |
| GS-17645 | When changing a non-SSL server to an SSL server, the Manager (Broker) ID changes when re-configuring the server. |
Note:
For changing the non-SSL server to an SSL server, ensure that the Manager ID before and after reconfiguration is the same. You must manually input the old server ID during configuration.
| Key | Summary |
|---|---|
| GS-16590 | In GridServer user interface (UI), if a value of the configuration row differs from the default value, then it highlights the altered configuration row with a distinct color. |
| GS-16589 | In the GridServer user interface (UI), row numbers are displayed across all pages where data is presented in a tabular format. |
Operating Systems
| Key | Summary |
|---|---|
| GS-18794 | Apache Tomcat should be upgraded to 9.0.113. |
| GS-18527 | GridServer requires support for Rocky Linux 9. |
REST API
| Key | Summary |
|---|---|
| GS-19415 | A new REST API is needed for adding, removing and fetching list of Run-As Credentials. |
| GS-18618 | New REST APIs are required to manage various engine configuration parameters. The new REST APIs are introduced that performs all operations available for the Engine Configuration tab. You can change the engine settings, such as log levels, through an automated interface. |
| GS-15890 | Administrators had to remove manually offline daemon entries. With the new REST API methods, you can now purge offline daemons. |
Security
| Key | Summary |
|---|---|
| GS-18610 | Critical and high-priority Common Vulnerabilities and Exposures (CVEs) detected in the Manager and Engine components are resolved. AngularJS updated version 1.8.3 enhances UI stability and security. |
Services
| Key | Summary |
|---|---|
| GS-19013 | When you set the Synchronize Resources to Engines property to false under Admin > System Admin > Manager Configuration > Resource Deployment, the following error is displayed, Grid Library has not been deployed. Manually updating the Grid Libraries on the Engine side did not resolve this issue. The service would only run successfully if you set the Synchronize Resources to Engines property to true. This is resolved. The Manager can now find the Grid Library when the Synchronize Resources to Engines property is set to false. |
Note:
When the
Synchronize Resources to Engines property is set to false , the Grid Library must be placed manually along with the signature file (.#extracted file) under <Engine_directory>/resources/gridlib/ (default location) or at the custom Grid Library path. The custom Grid Library path is the location of the Grid Libraries, set through Engine Configuration > Grid Library Path . This should only be set if not using Grid Library Synchronization.
Upgrade and Migration
| Key | Summary |
|---|---|
| GS-17656 | Access to internal JDK packages, which were previously available, is now restricted. So, in the Command-Line Argument in the Engine JVM section under Grid Components > Engine > Engine Configurations use the following parameters: --add-``exports=java.desktop/com.sun.beans.editors=ALL-``UNNAMED Select the engine configuration file based on your operating system. |
Note:
This parameter is only necessary for Java 17. Do not include it for lower Java versions, such as Java 8 and Java 11.
Known Issues
This section lists known issues in this release of TIBCO DataSynapse GridServer® Manager:
Engine, Engine Daemon
| Key | Summary/Workaround |
|---|---|
| GS-19447 | Summary: When you upgrade to GridServer (GS) 7.2.0, the gcc34 and gcc49 compilers are no longer supported. If you upgrade from an earlier GS version where you configured gcc34 or gcc49 as the Engine GCC built version, the cached engine configuration may continue to reference an unsupported GCC version. |
Workaround: Refresh the cached engine configuration on Linux engines by performing following steps:
-
Open the Engine Configuration UI in GS 7.2.0.
-
Change Engine GCC built version from
gcc83togcc115, then save the change. -
Change Engine GCC built version from
gcc115back togcc83, then save the change again. This action forces the regeneration of the cached configuration. It also updates thex4088.defaultfile underengineDistros.
| Key | Summary |
|---|---|
| GS-19250 | Summary: GridServer UI and SDK artifacts for .NET 8 are incorrectly named as .NET 5 artifacts. |
| GS-19127 | Summary: Under Windows Authentication mode, GridServer may fail to restart after the LGPL JAR file is applied. HTTP Status 404–Not Found error occurs on the Web UI. This occurs when the domain configuration is saved prior to the JAR deployment. |
| GS-17640 | Summary: When move Engines from GridServer version 6.3.1_hotfix05 to GridServer version 7.1.0, sometimes the win32 and win64 Engines do not move to the GridServer 7.1.0 server. The server running is the SSL server using a self-signed certificate. 1. After the Engines are online on GridServer version 6.3.1, change the Primary Director URL from 631 to 710 in the Engine Configuration. 2. Check after some time (for example, 15 secs), the GridServer version 7.1.0 Primary Director URL reflects in the engined.log file and that the Engine is trying to connect to the GridServer version 7.1.0 server. 3. Then copy the GridServer version 7.1.0 certificates to the Engine directory. |
Manager
| Key | Summary/Workaround |
|---|---|
| GS-19285 | Summary: There is an issue for the GridServer 7.2.0 startup on RHEL 10 machines due to the missing compatibility libraries for Apache Tomcat Native. To resolve the Grid Server startup issue on RHEL 10, install the libxcrypt-compat package. This package provides the necessary compatibility library for the POSIX crypt() API. 1. Run the following command in your terminal: sudo dnf install libxcrypt-compat 2. After installing the package, start the Grid Server. The server starts successfully. |
| GS-17691 | Summary: Task collection generates an excessive amount of logs at the FINE level. |
| GS-17647 | Summary: On Windows Engines, the logs engine-stderrxxx.log and engine-stdoutxxx.log are not generated as expected. |
| GS-17646 | Summary: If you use DSConfigureOnStartup=true in the installation.properties file to re-configure the server, it causes a Grid Cache problem. Grid Cache is not properly initialized after the server is up. For SSL server - Install SSL server using Silent installation mode - Install SSL server using UI installation mode (before installing an SSL server, a non-SSL server must not be installed) |
Note:
For changing the non-SSL server to an SSL server, ensure that the Manager ID before and after reconfiguration is the same. You must manually enter the old server ID during configuration. For the non-SSL server (for converting a Broker to a Director or from Director to a Broker).
-
Ensure that the Manager ID before and after reconfiguration is the same. You must manually enter the old server ID during configuration. For an already running server 1. Purge the offline Broker from Grid Components > Broker Admin. 2. Stop the server.
-
Go to
DS_DATA/cacheand delete theold_offline_broker_id.brokerfile. -
Start the server.
Services
| Key | Summary |
|---|---|
| GS-17423 | Summary Service Priority Changed Event is not captured through Kafka Event Streaming. |
TIBCO Documentation and Support Services
For information about this product, you can read the documentation, contact TIBCO Support, and join TIBCO Community.
How to Access TIBCO Documentation
Documentation for TIBCO products is available on the Product Documentation website, mainly in HTML and PDF formats. The Product Documentation website is updated frequently and is more current than any other documentation included with the product.
Product-Specific Documentation
Documentation for TIBCO DataSynapse GridServer® Manager is available on the TIBCO DataSynapse GridServer® Manager Product Documentation page.
How to Contact Support for TIBCO Products
You can contact the Support team in the following ways:
-
To access the Support Knowledge Base and getting personalized content about products you are interested in, visit our product Support website.
-
To create a Support case, you must have a valid maintenance or support contract with a Cloud Software Group entity. You also need a username and password to log in to the product Support website. If you do not have a username, you can request one by clicking Register on the website.
-
To submit ideas, suggestions, or feedback for TIBCO products, visit our product Support website.
How to Join TIBCO Community
TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter experts to share and access their collective experience. TIBCO Community offers access to Q&A forums, product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and tools that extend and enable customers to gain full value from TIBCO products. For a free registration, go to TIBCO Community.
Legal and Third-Party Notices
SOME CLOUD SOFTWARE GROUP, INC. (“CLOUD SG”) SOFTWARE AND CLOUD SERVICES EMBED, BUNDLE, OR OTHERWISE INCLUDE OTHER SOFTWARE, INCLUDING OTHER CLOUD SG SOFTWARE (COLLECTIVELY, “INCLUDED SOFTWARE”). USE OF INCLUDED SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED CLOUD SG SOFTWARE AND/OR CLOUD SERVICES. THE INCLUDED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER CLOUD SG SOFTWARE AND/OR CLOUD SERVICES OR FOR ANY OTHER PURPOSE. USE OF CLOUD SG SOFTWARE AND CLOUD SERVICES IS SUBJECT TO THE TERMS AND CONDITIONS OF AN AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER AGREEMENT WHICH IS DISPLAYED WHEN ACCESSING, DOWNLOADING, OR INSTALLING THE SOFTWARE OR CLOUD SERVICES (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH LICENSE AGREEMENT OR CLICKWRAP END USER AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE SAME TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of Cloud Software Group, Inc. TIBCO, the TIBCO logo, the TIBCO O logo, GridServer, FabricServer, GridClient, FabricBroker, LiveCluster, and SpeedLink are either registered trademarks or trademarks of Cloud Software Group, Inc. in the United States and/or other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. You acknowledge that all rights to these third party marks are the exclusive property of their respective owners. Please refer to Cloud SG’s Third Party Trademark Notices (https://www.cloud.com/legal) for more information. This document includes fonts that are licensed under the SIL Open Font License, Version 1.1, which is available at: https://scripts.sil.org/OFL Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro. Cloud SG software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. See the “readme” file for the availability of a specific version of Cloud SG software on a specific operating system platform. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. CLOUD SG MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S), THE PROGRAM(S), AND/OR THE SERVICES DESCRIBED IN THIS DOCUMENT AT ANY TIME WITHOUT NOTICE. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "README" FILES. This and other products of Cloud SG may be covered by registered patents. For details, please refer to the Virtual Patent Marking document located at https://www.cloud.com/legal. Copyright © 2001-2026. Cloud Software Group, Inc. All Rights Reserved.