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.12.0/Hotfix-02. Please check the hotfix readme file for installation steps and other details.

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.12.0_HF-002 (This Release)

New Features

AMBW-55230
Users can now view License Status details through OTEL metrics using
third party applications such as Prometheus or Grafana by using the new meter: 
com_tibco_bw_license_expiration_seconds.

AMBW-54995
Using the following API: 
http://<hostIP>:<appnode_port>/bw/framework.json/license, the user can view
the total number of days remaining before the license expires.

AMBW-54942
Support for Apache Maven version 3.9.11 added in 6.12.0 HF2.

AMBW-54675
Native MCP Server Support for REST and SOAP Services

TIBCO BusinessWorks now supports exposing REST and SOAP services as MCP servers. 
This allows AI agents to dynamically discover and invoke enterprise functions
and data using a standardized protocol. MCP server configuration is available
directly within Business Studio. 

Enable MCP Server (BusinessWorks6): 

- Go to Windows > Preferences > BusinessWorks > MCP Enable MCP Server View.

- Add JVM argument: -Dbw.enable.mcp.server=true to run/debug.

- Added few BusinessWorks design utility commands to enable 
  the MCP configuration: 
   * generate_mcp_config Configures a BusinessWorks module for MCP.
   * generate_mcp_ear Generates an MCP-compatible EAR from an existing EAR.
   * generate_mcp_skeleton Creates an MCP-ready BusinessWorks skeleton from
     a REST API spec.

For more details on enabling and configuring MCP server, see the Bindings and
Palette Reference Guide.

Note: This is a Tech preview feature. This release supports only Tools.

By using this Tech Preview, you acknowledge and agree that:

- It is provided "as is" with no warranties, express or implied.
- It may not be deployed in production environments.
- You are responsible for ensuring that any data processed complies with all 
  applicable laws, regulations, and thirdparty rights.
- Use of this software to analyze content or intellectual property of
  Cloud Software Group is strictly prohibited.
  
AMBW-52697
Dynamic FTL servers are now supported with BusinessWorks Agent for transport.

AMBW-45519
Support has been added to configure a proxy in the OAuth shared resource.
A new Proxy field is available under the Advanced section, allowing users to
associate a proxy resource with OAuth requests.

BWCE-10695
Enhanced the Diff Viewer functionality to support visual comparison of Mapper
activity input configurations. This allows users to identify structural and
mapping changes between different versions of a process.

BWCE-10471
BWCEMON now includes an automated health-check and cleanup mechanism that
periodically validates and removes stale application instances caused by
Kubernetes pod restarts. The following properties have been introduced:

- HEALTH_CHECK_ENABLED: Enables or disables the automated background job that 
  periodically scans for and cleans up stale application instances. 
  The default value is true.

- OVERALL_HEALTH_CHECK_INTERVAL: Specifies the global frequency(default: 5 minutes) 
  at which the system initiates a health scan across all monitored applications.

- HEALTH_CHECK_INTERVAL_MS: Defines the wait time (default: 60000 ms) between 
  retry attempts for an application node after it has been flagged as unhealthy.

- HEALTH_CHECK_MAX_ATTEMPTS: Specifies the maximum number of failed health 
  checks allowed (default: 3) before an instance is permanently removed from
  the database and the UI.

BWCE-10447
Users can now enable Process Monitoring when starting a BWCE application from
the CLI. Property name: APP_ENABLE_MONITORING. 

e.g.: docker run --rm -e BW_APP_MONITORING_CONFIG="{\"url\":\"http://<ip:port>\
",\"appEnableMonitoring\":true}" <app-name>
or
docker run --rm -e BW_APP_MONITORING_CONFIG="{\"url\":\"http://<ip:port>\"}"
-e APP_ENABLE_MONITORING=true <app-name>
 
BWCE-10369
When Smart Mapper is unable to automatically map an element during the Smart
Map operation, the system now logs detailed diagnostic information in the 
Eclipse Error Log. This enables users to understand why certain elements 
failed to map and how to adjust Smart Mapper settings accordingly.

Changes In Functionality 

AMBW-55554
The syntax for createSwaggerOperation BusinessWorks design utility command
is now updated as: 
  - createSwaggerOperation [Create Option] [Operation option] [Process Name] 
    [Module Name] [Swagger File Name] [Resource Path]

The details of the same can be found in Using the BusinessWorks Design Utility
section of Application Development guide.

AMBW-55364
The port number for the OpenTelemetry span exporter endpoint has been updated
to 4317. The corresponding system property is now:
bw.engine.opentelemetry.span.exporter.endpoint=http://localhost:4317

CVEs

AMBW-55550
Upgrades the Plexus libraries bundled with the plexus-utils-4.0.3.jar.

AMBW-55145
This release addresses CVE 2025 68161, a security vulnerability related to the 
bundled Log4j Core dependency.

AMBW-54973
CVE-2025-68161 has been addressed.

AMBW-54487
CVE-2025-8885 due to bc-fips-1.0.2.5.jar and bc-fips-2.0.0.jar has been 
addressed.

AMBW-54486
CVE-2025-8916 due to bcpkix-fips-1.0.7.jar has been addressed.

BWCE-10777
Address High priority CVE-2025-7962 related to com.sun.mail:javax.mail/mail.jar
present in 6.12.0 HF2.

BWCE-10264
Replaced javax.activation references with jakarta.activation because
javax.activation has reached End of Life (EOL).

Known Issues

AMBW-55624
The "Bundle-SymbolicName header is required" error appears when renaming a
shared module and running the install goal. This occurs because the 
Bundle-Version entry in the MANIFEST.MF file is overridden by le-Version. 
It must be manually corrected back to Bundle-Version.

AMBW-55587
UI components disappeared and the activity became unselectable when
configuring process properties for the Timeout field in the JDBC and Process
Starter activities.

AMBW-55465 
After migrating from BusinessWorks 5.x to the latest BusinessWorks 6.12.0 
environment, all projects show a "No explicit project encoding" warning which 
is harmless and can be fixed/removed/resolved using the quick fix option 
in the warning tab.

AMBW-55363
Adding a CXF dependency through the bwdesign utility results in a harmless
error: [Fatal Error] :1:1: Content is not allowed in prolog.

BWCE-10831
For a multi-level tree, the rendering in JFace displays the top-level elements,
which are colored. After both sides of the tree are created, if the user
expands a node on the right-side tree, the default color of the right-side
tree is applied to the expanded elements, and the same color is also used
on the left side of the tree.

The same coloring is applied in the XSLT view for these expanded nodes.

Closed Issues

AMBW-55534
Changes to dependencies under the Includes tab are not updated in the 
TIBCO.xml file.

AMBW-55482
The endpoint port in the manifest-bwce.json file is not null when the port
refers to a module property from a shared module. Instead, it displays the
actual port value.

AMBW-55260
The issue where a Process property configuration error occurred when a
process property [xxx] was configured with a shared resource from a shared
module in the application has been fixed.

AMBW-55221
Earlier, the long data type was displayed as an integer on the platform.
This issue has now been fixed.

AMBW-55164
Swagger UI failed to load when the REST service was configured with an XSD
that defined elements using simpleContent types containing only attributes
and no child elements.

AMBW-55146
Replaced the old Oracle JAR with the updated version and confirmed that it
is available and functioning correctly in the system hotfix shared location.

AMBW-55128
After the database restart, query flooding has been reduced significantly.

AMBW-55016
A thread pool leak was observed when multithreading was enabled for XSLT
mappers using the threads and contextsize parameters in for-each and
apply-templates.

AMBW-54944
SOAP Invoke activity using a SOAP/JMS binding throws exceptions

AMBW-54943
The latest stable mariadb-java-client 3.5.7 driver has been upgraded with
BusinessWorks 6.12.0 HF2.

AMBW-54941
Domain backup issue with Oracle DB in BusinessWorks 6.12.0 has been fixed.

AMBW-54932
The BusinessWorks agent now proactively detects database service-level
failures (SQLState 08 series) and initiates an internal retry loop until
the database connection is restored.

AMBW-54931
Unable to access BW.PROCESS.NAME and other constants.

AMBW-54890
Able to use predefined module property constants without any errors.

AMBW-54805
Checked Interpret Invalid XML Chars in SQLDirect > Advanced to prevent
issues with trailing spaces in string values.

AMBW-54545
The application fails to start with the error:
TIBCO-BW-SCHEMA-RESOLVER-500204: Failed to resolve WSDL

To resolve this issue, use the following property:
-Dbw.cache.runtime.wsdl.includeasimport=true

AMBW-54220
No warnings related to SnakeYAML deserialization or parsing were observed.

AMBW-54206
When generating the values.yaml file from Studio for an application with 
REST services, the service entries are not duplicated per port number, 
even if the application has more than one REST service.

AMBW-53589
Previously, requests to a REST service configured with query parameters
ignored extra query parameters and did not throw a validation error.

Now, setting the bw.rest.extra.query.parameter.validation system property
to true triggers a 400 Bad Request validation error when an extra query
parameter is included in the request.

AMBW-53566
Fixed the wrapping issue when a bundle is imported into the BusinessWorks
Studio workspace, where the Bundle-RequiredExecutionEnvironment header is 
set to "JavaSE-15" in the MANIFEST.MF file and its content is wrapped.

AMBW-53486
REST services returned a 400 Bad Request error when the configured XSD
imported schemas that referenced types from nested xsd:import.

AMBW-53029
After the database restart, all components started on the correct node,
and their statuses were displayed correctly.

BWCE-10958
Management of License Cache in an OpenShift Container Environment:

BusinessWorks requires a writable directory to store license related
runtime files. In containerized environments (e.g., OpenShift), the
default home directory may not be writable, which leads to runtime issues.
Therefore, a custom writable directory (with read permissions as well)
must be configured.

Note: This can be done in one of the following ways:

 * Set a system property:
   java.property.TIB_ACTIVATION_CACHE=<<location of the directory where
   the files can be written on disk>>

 * Or set an environment variable:
   TIB_ACTIVATION_CACHE

In both cases, ensure that the specified directory exists and has the
appropriate read and write permissions.

BWCE-10954
This release was certified with OpenShift 4.20.x & 4.21.x

BWCE-10889
All emails are now being delivered successfully with no duplication.

BWCE-10881
The Send HTTP Request activity fails with the error ˜The filename,
directory name, or volume label syntax is incorrect when it encounters a 
Content Disposition header containing filename*.

BWCE-10879
Set BW_HAWK_DISABLE to true, and Hawk will not be loaded or used for the 
BusinessWorks application.

BWCE-10863
A memory leak was observed in REST services configured with a Basic
Authentication Policy when multiple endpoints shared similar nested resource
paths under the same base path.

BWCE-10791
Opentelemetry SDK has been upgraded.

BWCE-10780
The http.status_code OpenTelemetry tag was previously missing for SOAP and
REST services implemented in BusinessWorks.

A new http.status_code tag now appears on the Reply activity in the
OpenTelemetry traces for SOAP and REST services, covering both success
and fault responses.

================================================================================

You can also download the hotfix using the below link:

https://support.tibco.com/s/hotfixes

TIBCO BusinessWorks 6.12.0 Hotfix-02 is available