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/5.16.1/Hotfix-07.

================================================================================
New Features in 5.16.1_HF-007 (This Release)

BW-22465
BusinessWorks 5 now enriches OpenTelemetry traces with JMS messaging semantic
convention attributes on JMS/EMS activity spans.
The following attributes are now included:

- messaging.system: Identifies the messaging system (e.g., jms).

- messaging.destination.name: The queue or topic name.

- messaging.operation.type: The operation (send, receive, or process).

- messaging.operation.name: The name of the messaging operation.

- Correct span kind: producer for send operations, consumer for push-based
event sources, and client for pull-based receive operations.

The above attributes are present in all JMS activities, as well as activities
that use JMS transport.

The following attributes are present based on the activity type:

- messaging.destination.temporary: Set when the destination is temporary,
such as an anonymous reply-to destination.

- messaging.destination.anonymous: Set when no static reply-to destination
is configured.

- messaging.message.id: The JMS message ID assigned by the broker.

- messaging.destination.subscription.name: The durable subscription name for
topic subscriptions.

When activities in other palettes use JMS transport, the spans they emit also
include these attributes. This provides richer observability for JMS-based
integrations when using distributed tracing tools such as Jaeger.
All existing trace attributes are preserved, ensuring no impact
on backward compatibility.

BW-22428
Added four new OpenTelemetry metrics (com_tibco_bw_starter_status,
com_tibco_bw_starter_running, com_tibco_bw_process_total_running, and
com_tibco_bw_process_total_active) to expose starter and process-level
monitoring data via OTel exports.

BW-22374
A new metric for retrieving license activation details,
"com_tibco_bw_license_expiration_seconds" has been introduced in this hotfix.
It can be consumed by third-party service providers like Prometheus and Grafana
to display license-related information.

BW-22198
Dynamic OTel Service Name

The service name reported to the tracing backend is set with
tibco.env.OTEL_SERVICE_NAME in the application.tra file or in bwengine.tra.
Its value can now contain %property% patterns that the engine resolves at startup,
allowing a single configuration entry to produce a distinct service name for each
deployment. Any property available to the engine can be referenced-including
properties defined in the .tra file, as well as system or environment variables.
For example, given prop1=domainA, setting
tibco.env.OTEL_SERVICE_NAME=service-%prop1% resolves as service-domainA.

BW-22201
Configurable OTel Span Scope

The new property java.property.bw.engine.opentelemetry.span.scope,
configured in application.tra or bwengine.tra, controls how many spans
a process emits: activity or process.

- activity scope: This is the default and preserves earlier behavior,
emitting a span for every activity.

- process scope: Emits only the Process Begin and Process End spans per process,
reducing span volume and backend load in high-volume deployments.
Sub-processes behave the same way under this setting, emitting their own
Process Begin and Process End spans under the calling process.
All intermediate activity spans are suppressed.

In process scope, errors are reported on the Process End span when handled,
and on the Process Begin span when unhandled. Error handling behavior for
activity scope remains unchanged. Trace context propagation remains
unaffected by this setting.

================================================================================
Changes in Functionality in 5.16.1_HF-007 (This Release)

BW-22226
Added support for a request payload in DELETE requests behind a feature flag,
as standard RESTful architecture typically does not support DELETE payloads.

Note: It is a property based fix. Users need to set
java.property.bw.plugin.http.sendBodyOnDelete=true to enable HTTP
Request activity to be able to send request body for HTTP.

================================================================================
Known Issues in 5.16.1_HF-007 (This Release)

BW-23015
For Linux, the inotify API is defaulted to 128 (i.e., max_user_instances=128).
If more than 128 applications are deployed at once on the same machine then
user might run into java.io.IOException: User limit of inotify instances
reached or too many open files error.

To resolve this issue, please set the max_user_instances value at the kernel
level to a higher number.

================================================================================
Closed Issues in 5.16.1_HF-007 (This Release)

BW-23013
Fixed an SSL hostname verification failure for HTTP Send Request and
SOAP-over-HTTP activities when the server certificate's hostname is listed
in the Subject Alternative Name (SAN) extension but not in the Common Name(CN).

BW-22893
Upgraded jackson-core and jackson-databind libraries to version 2.21.5 to
address security vulnerability.

BW-22731
In an MS SQL Server database using JDBC to call a procedure, fields returned
through the result set were unavailable when "Use Schema" was enabled.
This issue has now been fixed.

BW-22702
When a BusinessWorks service invoked another BusinessWorks service over JMS,
the dependency link between the two services was not rendered in the
Elastic APM Service Map. This issue has now been fixed.

BW-22646
The installation of version 5.16.1 HF6 fails with a "java.lang.OutOfMemoryError:
Java heap space" error. This issue has now been fixed.

BW-22465
Added OpenTelemetry messaging semantic convention attributes (messaging.system,
messaging.destination.name, and messaging.operation.type) and applied the correct
span kinds to JMS activity spans for Queue, Topic, and Request-Reply operations.

BW-22435
The Adapter Publisher generates invalid XML due to duplicate namespace
prefix mappings. This issue has now been fixed.

BW-22428
Added four new OpenTelemetry metrics (com_tibco_bw_starter_status,
com_tibco_bw_starter_running, com_tibco_bw_process_total_running, and
com_tibco_bw_process_total_active) to expose starter and process-level
monitoring data via OTel exports.

BW-22400
In BW 5.16.1, the Parse Data activity may fail during the second iteration
of a process when executed repeatedly within the same process flow.
This issue has now been fixed.

BW-22376
Fixed a NullPointerException thrown by the Render XML activity when
OpenTelemetry tracing is enabled and a preceding Parse XML activity fails
via an error transition.

BW-22374
Added the OpenTelemetry metric com_tibco_bw_license_expiration_seconds
to expose license validity status, expiry details, and remaining time,
enabling programmatic license monitoring via Prometheus and Grafana.

BW-22226
Added support for sending a request body with HTTP DELETE requests via the
feature flag bw.plugin.http.sendBodyOnDelete=true in the HTTP Request activity.

Note: It is a property based fix. Users need to set
java.property.bw.plugin.http.sendBodyOnDelete=true to enable HTTP
Request activity to be able to send request body for HTTP.

BW-22201
Added a new configurable property bw.engine.opentelemetry.span.scope
(process / activity) to allow suppression of intermediate activity spans
in OpenTelemetry traces, emitting only process-level start and end spans
to reduce trace volume.

BW-22198
Added support for dynamic OTEL_SERVICE_NAME resolution, allowing BusinessWorks
runtime variables (e.g., %tibco.domain%, %tibco.deployment%) to be used in the
tibco.env.OTEL_SERVICE_NAME property for automatic, unique service naming across
observability platforms.

BW-22017
During the switchover from TAS to IPA licensing mode, an error related to
license caching occurred. This issue has now been fixed.

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

TIBCO ActiveMatrix BusinessWorks 5.16.1 Hotfix-07 is available