| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | 6.11.0 |
You can download this HotFix from the TIBCO Support Portal (https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to the AvailableDownloads/BusinessWorks/6.11.0/Hotfix-05. Product license activation has been added as part of this hotfix.
Below is the complete list of defects/enhancements addressed in this hotfix(You can also find the same in the attached hotfix readme file).
6.11.0_HF-005 (This Release)
New Feature
BWCE-10387
New properties have been added to control the behavior of the OpenTelemetry
custom tag prefix:
* bw.engine.clear.otel.tag.prefix=true, removes the prefix.
* bw.engine.override.otel.tag.prefix=<custom>, applies a custom prefix.
Note:
The default behavior remains unchanged (the * prefix is used).
If both properties are set, the clear property takes precedence, and the prefix
is removed.
BWCE-10293
Enhanced the Diff Viewer functionality to support visual comparison of Mapper
activity input configurations. Users can now identify structural and mapping
changes between different versions of a process
BWCE-10244
Schedules with past start times now auto‑adjust to the current time unless the
Fire-Past-Due Schedule checkbox is selected, in which case an additional job is
created.
Changes in Functionality
AMBW-54862
The compare editor in the diff view displays differences for the input tab of a
mapper activity and allows to copy those differences when comparing the
local working copy with an older revision.
AMBW-54713
From BusinessWorks 6.11.0 HF05 onward, support for license activation using
environment variables is provided through the TIB_ACTIVATION environment variable.
AMBW-54711
An updated license system property, java.property.TIB_ACTIVATION, will now be
used to activate a license in the bwappnode.tra file starting from
BusinessWorks 6.11.0 HF05 onward.
AMBW-54318
Azure Key Vault now supports non‑password property types as well.
BWCE-10712
To align with standard Maven practices, dependency management for a Mavenized
application must now be handled exclusively through the pom.xml.
When users click the Add, Add External, or Remove dependency buttons, a pop‑up
message will appear, instructing them to manage dependencies directly in the pom.xml.
We understand this change may impact older projects where dependencies are a mix of
Design Time (DT) and Maven configurations.
To help with cleanup, a preference option is provided under:
Window > Preferences > BusinessWorks > Validation > Enable Remove Dependency for
Maven Projects.
Enabling this option allows the Remove button to function for Mavenized projects.
However, it does not enable the Add or Add External buttons.
CVEs
AMBW-54879
High Risk Spring Vulnerability CVE-2025-41249 in BusinessWorks.
AMBW-54727
High priority CVE-2023-6378 due to logback-classic-1.2.3.jar addressed.
AMBW-54726
CVE spring-core-6.1.20.jar addressed.
AMBW-54649
High Risk Spring Vulnerability CVE-2025-41249 in BusinessWorks.
BWCE-10502
Addressed High priority CVE-2025-7962 related to com.sun.mail:javax.mail/mail.jar.
BWCE-10470
okhttp-4.12.0.jar has been upgraded to okhttp-5.3.2.jar.
Known Issues
BWCE-10814
For a multi‑level tree, the tree rendering in JFace shows the top‑level
elements, and these elements are colored. After both sides of the tree are
created, when the user expands a node on the right‑side tree, the default
color of the right‑side tree is applied to the newly expanded elements,
and the same color is also used on the left side of the tree.
The same coloring will be applied in the XSLT view for these expanded nodes.
Closed Issues
AMBW-55006
Swagger UI failed to load when the REST service was configured with an XSD
that contained elements defined with simpleContent types having attributes
only and no child elements.
AMBW-54589
While invoking a REST service defined with required/mandatory request header
parameters, an error was not thrown if the request headers were not passed
in the request. Now, request header validation is taking place,
and a 400 Bad Request error is thrown.
AMBW-54265
The bootclasspath error encountered during EAR generation has been fixed.
To resolve this issue, configure the following setting:
Window → Preferences → Java → Compiler → Compiler compliance level = 1.8
AMBW-54259
The List Files activity was loading the entire file object into memory, which
caused an OOM error during heavy‑load scenarios.
AMBW-53578
To build the tibcrypt.eclipse‑2.19.400.001.jar package, run the following
command from the directory:
<tibco_home>\bw\6.11\maven\tibcrypt
mvn install:install-file
-DgroupId=com.tibco.security
-DartifactId=tibcrypt.eclipse
-Dversion=2.19.400.001
-DgeneratePom=true
-Dpackaging=jar
-Dfile=com.tibco.security.tibcrypt.eclipse-2.19.400.001.jar
AMBW-52779
After the database restart, query flooding has been reduced significantly.
BWCE-10743
Bundles in debug configurations for custom XPath function JARs will be
auto‑selected.
BWCE-10582
Upgraded Microsoft JDBC Driver to version 13.2.1 (JRE 11).
BWCE-10547
All emails are now being delivered successfully with no duplication.
BWCE-10530
The http.status_code OpenTelemetry tag was missing for the SOAP and REST
services implemented in BusinessWorks.
A new http.status_code tag will now appear on the Reply activity in the OTEL
traces for SOAP and REST services, covering both success and fault responses.
BWCE-10433
The issue that caused Studio to hang when right‑clicking the Add Test option
has been fixed.
BWCE-9084
A memory leak was observed in REST services configured with the Basic
Authentication policy when multiple endpoints shared similar nested resource
paths under the same base path.
You can also download the hotfix using the below link:
https://support.tibco.com/s/hotfixes
TIBCO BusinessWorks 6.11.0 Hotfix-05 is available