New Features

Last published : Nov 13, 2026
The following features have been added in this release of TIBCO GridServer®:

HashiCorp Vault Support for Database Credentials

TIBCO GridServer® now integrates with HashiCorp Vault to securely store and retrieve database credentials for the reporting database. This allows you to centralize credential management, enhance security, and maintain compliance with enterprise standards. You can use Token-based and AppRole-based Vault authentication methods.
For more information, see "Configuring HashiCorp Vault for Reporting Database Credentials" section in TIBCO GridServer® Installation guide.

Active Directory Authentication for the Microsoft SQL Server Reporting Database

TIBCO GridServer® now supports on-premises Active Directory (AD) authentication for the Microsoft SQL Server reporting database as an alternative to standard SQL Server authentication. This feature is supported on both Windows and Linux operating systems running the Manager. This enhancement allows you to configure Windows Integrated Authentication for your reporting database, meeting stringent security requirements and ensuring seamless integration with your existing AD infrastructure.
For more information, see "Configuring Active Directory (AD) Authentication for the SQL Server Reporting Database (On-Premise)" section in the TIBCO GridServer® Installation guide.

Apply License Using Script

TIBCO GridServer® supports applying a license file through a script. This eliminates the need to log in to the Director UI for license installation. During a silent installation, set the new licenseFile property in install.silent. Provide the full path to your license file. The system applies the license automatically as part of the install. For more information, refer to "Silent Installation" section in the TIBCO GridServer® Installation guide.

Apache Tomcat® 10.1.55 Upgrade

The embedded Apache Tomcat server has been upgraded to version 10.1.55. As Tomcat 10.1 implements Jakarta EE 9 or later, the GridServer Manager web application has migrated from the javax.* namespace to the jakarta.* namespace.
As a result, the REST and SOAP API connectors and authenticators have also been updated to support the new namespace.

Changes in Functionality

The following changes in functionality have been made in this release of TIBCO GridServer®:

GridServer Manager Interface Updated to Bootstrap 5

TIBCO GridServer® web interface now uses Bootstrap 5.3.8, replacing the previously included Bootstrap 3.3.7 version.
With upgrade to this current, supported version of the Bootstrap library addresses vulnerabilities identified in the older version and addresses the security concerns of the Manager interface. For details on changes in functionality since the last major release of this product, see the section "Upgrading GridServer" section in the TIBCO GridServer® Installation guide.

Deprecated and Removed Features

The following features have been deprecated or removed as of this release of TIBCO GridServer®:

Deprecated Features

Affected Component Description Deprecated Release
Engine Support for 32-bit Windows and Linux engines will be discontinued in a future release. To ensure compatibility with future updates. migrate to 64-bit operating systems. 7.1.1

Removed Features

Affected Component Description Deprecated Release
Server / JRE Due to the upgrade to Apache Tomcat 10.1, Java 8 is no longer supported as a compatible Java Virtual Machine (JVM) version. The minimum required JVM version is now Java 11. 7.1.1
Manager RHEL 7 is not supported for the Manager. However, the Engine/Driver should still run on RHEL 7 for applications compiled with GCC 3.4 and GCC 4.9. 7.1.1

Migration and Compatibility

The following information provides migration procedures and a compatibility matrix for this release of TIBCO GridServer®:

Java 11 is the Minimum Required JVM Version

Due to the upgrade to Apache Tomcat 10.1, Java 8 is no longer supported as a compatible Java Virtual Machine (JVM) version. The minimum required JVM version is now Java 11.

Apache Tomcat 10.1 and Jakarta Namespace Migration

Migrate any deployed web components, Broker or Manager hooks, or bundled libraries that reference the javax.* servlet API to the jakarta.* namespace.
It is recommended that before you start the upgrade, back up the server.xml file from the DS_DATA/conf directory to a separate directory to preserve your custom configurations. After the upgrade, replace the server.xml file in DS_DATA/conf with the updated file from the release. Then, reapply any required customizations.

Microsoft SQL Server 2022 Support for the Reporting Database

TIBCO GridServer® now supports Microsoft SQL Server 2022 as a reporting database. You can select this version when configuring the reporting database for the GridServer Manager. GridServer 7.1.1 includes all cumulative fixes from GridServer 7.1.0 HF-01 through HF-08, the additional fixes listed in the Closed Issues section, and the enhancements described in the New Features section.
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 GridServer®:

Documentation

Key Summary
GS-18270 The Developer's Guide included an outdated section regarding C++ compiler configuration. This section referenced invokeGCC, a component that is no longer available in GS 7.x. The documentation now provides updated and correct instructions for configuring the GCC Version property when you run Linux C++ Services.

Manager

Key Summary
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. To fix this issue, you can perform one of the following two options: - 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 input the old server ID during configuration.

Engine, Engine Daemon

Key Summary
GS-17647 On Windows Engines, the logs engine-stderrxxx.log and engine-stdoutxxx.log are not generated as expected.

Known Issues

This section lists known issues in this release of TIBCO GridServer®:

Engine, Engine Daemon

Key Summary/Workaround
GS-17640 Summary When Engines are moved 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-20099 Summary: When connecting to LDAP through a non-SSL enabled grid, results in a FileNotFoundException if the server.keystore file is not present. The system incorrectly attempts to validate or load server.keystore, even when it was not required for the connection. The SSL configuration is updated to prevent this unnecessary check., ensuring successful LDAP connectivity.
GS-17691 Summary: Task collection generates an excessive amount of logs at the FINE level.
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). For the non-SSL server (for converting a Broker to a Director or vice versa). - 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. 3. Go to DS_DATA/cache and delete the old_offline_broker_id.broker file. 4. Start 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 enter the old server ID during configuration.

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 GridServer® is available on the TIBCO GridServer® 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.