TIBCO BusinessWorks™

Container Edition
Release Notes
Version 2.6.2
May 2021

Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

2 | Contents

Contents
Contents 2

New Features 3

Changes in Platform Support 15

Changes in Functionality 16

Deprecated and Removed Features 19

Closed Issues 20
Binding 20
General 22
Migration 28
Monitoring 29
Palette 29
Policies 35
Runtime 36

Known Issues 40
Binding 40
General 43
Migration 50
Monitoring 53
Palettes 54
Policies 58
Runtime 59

TIBCO Documentation and Support Services 60

Legal and Third-Party Notices 62

TIBCO BusinessWorks™ Container Edition Release Notes

3 | New Features

New Features
The following new features have been introduced in TIBCO BusinessWorks™ Container
Edition and are listed by release.

Release 2.6.2

Common Features

Certifications This release adds certification for:

l OpenShift 4.6.x

l Azure App Service

l Podman

l Kubernetes 1.20.x

l Cloud run for Google Anthos

Note: While deploying an application on cloud run for

Anthos, specify the hostname as 0.0.0.0 under
resource configuration. Ensure sufficient memory is
allocated to each container instance while deploying
an application on cloud run for Anthos.

New environment This release adds additional support for logging format on
variable added to TIBCO BusinessWorks Container Edition using the BW_LOG_
support logging format FORMAT as an environment variable.
on TIBCO
For more information, see "Environment Variables on Docker",
BusinessWorks
"Environment Variables on Cloud Foundry" and "Environment
Container Edition
Variables on TIBCO Business Studio for BusinessWorks in the
TIBCO BusinessWorks Container Edition Application
Development.

Support is added for REST service binding and REST reference binding now support
form parameters form parameters for Open API Specification 3.0.

TIBCO BusinessWorks™ Container Edition Release Notes

4 | New Features

Design Time

Support is added If a swagger file has "default" as one of the responses for REST
for "default" service's operation, then on creating a top-down REST service from
respone the swagger file the same is reflected in the Response Status tab of
in REST Service. REST service binding. To Reply with default fault, it is mandatory to
add "statusCode" element to the default fault schema by following
below steps :

1. Open the REST service process.

2. Click on OnMessage Start -> Properties -> Fault tab.

3. Select defaultResponseSchema

4. Add statusCode as Integer type element.

If the statusCode element is already present in the default response

schema, then the user need not add the element.

Generate Now you can generate the Manifest.json file for cloud projects by using
Manifest.json file the following bwdesign command line utility:
using bwdesign
generate_manifest_json -project <project_name> <location to generate
manifest.json file>

Support added to After using the Smart Mapper, if you do not get the desired mapping
manually update results, you can now drag any other element. The smart mapper
element mappings remembers your selection by increasing the recommended score for
for Smart Mapper that element and then map the same elements next time.
preview feature.
Note that the source and target elements must be within the range of
the level set during smart mapping.

Enhanced The Recommended Mappings option is now available for mapped

Recommended elements as well as Smart Mapper preview feature.
Mappings in Smart
Mapper preview
feature.

TIBCO BusinessWorks™ Container Edition Release Notes

5 | New Features

Release 2.6.1

Common Features

Certifications This release adds certification for:

l Kubernetes 1.19.x
l OpenShift 4.5.x

Support added for multiple This release adds support for multiple buildpacks while
buildpacks in Cloud Foundry deploying in Cloud Foundry in TIBCO BusinessWorks
for TIBCO BusinessWorks Container Edition.
Container Edition
For more information, see "The TIBCO BusinessWorks™
Container Edition Buildpack" in the TIBCO
BusinessWorks Container Edition Application
Development.

Support added for YAML and This release adds support for YAML and properties file for
properties file for using Consul using Consul as Configuration Management Service.
as Configuration Management
For more information, see "Adding the YAML file or
Service.
Properties file for Configuration Management using
Consul" in the TIBCO BusinessWorks Container Edition
Application Development.

Support added for module This release adds support for module properties for the
property for the OAuth following fields of the OAuth Configuration shared
Configuration shared resource:
resource.
l Client ID
l Client Secret
l Access Token URL
l Scope
l Username
l Password
l Confidentiality

TIBCO BusinessWorks™ Container Edition Release Notes

6 | New Features

Common Features

Mapping Score % value is set When you manually map an element through the
to 100% suggestive mapping, the Mapping Score % value in the
Recommended Mappings dialog box is set to 100%.

SOAP Invoke activity now Request with CDATA tags can now be sent with SOAP
sends requests with CDATA Invoke activity.
tags.
For the CDATA tags to remain intact on the wire we need
to set the below java property in VM arguments :
bw.binding.soap.invoke.cdata.serialization=true

Design Time

Support added for Timer A new Use local time check box is added under General
activity to use local time of the tab of Timer activity.
container
If you select the check box, the timer activity is triggered
at the specified Start Time value of the container's time
zone.

Monitoring

Support is added for using A new property DB_ENCRYPT is added to use Azure SQL
Azure SQL Managed Managed Instance (MI) for TIBCO BusinessWorks Container
Instance (MI) for TIBCO Edition Monitoring on Docker and Cloud Foundry.
BusinessWorks Container
For more information, see "Configuring MS SQL Server on
Edition Monitoring.
Cloud Foundry" and "Setting Up TIBCO BusinessWorks™
Container Edition Application Monitoring on Docker" in the
TIBCO BusinessWorks Container Edition Application
Monitoring and Troubleshooting.

Palettes

Support added for reconnecting logs This release adds support for reconnecting logs for

TIBCO BusinessWorks™ Container Edition Release Notes

7 | New Features

Palettes

for JMS Send Message and JMS JMS Send Message and JMS Receive Message
Receive Message activities. activities.

These logs are seen after setting root level as INFO

in the logback.xml file as follows:

<root level="INFO">
<appender-ref ref="STDOUT" />
</root>

The following output is displayed:

Connection re-established successfully. Starting

JMSSender.

Connection re-establised successfully. Starting

JMSReceiver.

Support added for Azure TIBCO BusinessWorks Container Edition adds

Authentication for SQL Server supports for Azure Authentication for SQL Server
database for JDBC Connection database for JDBC Connection Shared Resource.
Shared Resource.
For more information, see "Azure Authentication" in
the TIBCO BusinessWorks Container Edition
Bindings and Palette Reference.

Runtime

Support added to configure both This release adds support for using
Credential and Config Management configuration management service and
together while designing a TIBCO credential management together at once for
BusinessWorks Container Edition TIBCO BusinessWorks Container Edition
application. applications.

For example, you can use Hashicorp as

credential management and Consul as
configuration management service together.

TIBCO BusinessWorks™ Container Edition Release Notes

8 | New Features

Release 2.6.0

Common Features

Certifications This release adds certification for:

l Tanzu Application Services (TAS) 2.10.0
l Kubernetes 1.18.x

Integration for Azure Key This release adds out-of-the-box support for Azure Key Vault
Vault with TIBCO for Credential Management Service for TIBCO
BusinessWorks Container BusinessWorks Container Edition applications.
Edition.
For more information, see "Using Azure Vault for Credential
Management Service" in the TIBCO BusinessWorks
Container Edition Application Development.

Support is added for A new environment variable HASHICORP_VAULT_

Namespace in HashiCorp NAMESPACE is added to use Namespace in HashiCorp Vault
Vault Credential for Credential Management Service for TIBCO
Management. BusinessWorks Container Edition applications.

For more information, see "Using HashiCorp Vault for

Credential Management Service" in the TIBCO
BusinessWorks Container Edition Application Development.

Smart Mapper Smart Mapper provides the ability to intelligently determine

how data is to be mapped in the activity's input tab.

For more information, see "Smart Mapper" in TIBCO

BusinessWorks Container Edition Application Development.

This release adds support l REST Service Binding: Now you can create and
for OpenAPI 3.0 implement a REST Service defined with OpenAPI 3. 0
specification Specification, using both: the Swagger file as well as
TIBCO BusinessWorks Container EditionREST Service
Wizard.
l REST Reference Binding: You can invoke the REST
APIs created using the OpenAPI 3.0 Specification, with
the REST Reference Binding, and Invoke REST API
activity.

TIBCO BusinessWorks™ Container Edition Release Notes

9 | New Features

Common Features

l Updation to Swagger UI: OpenAPI 3.0 support is

added to the Swagger UI, which supports the Swagger
2.0 and 3.0 Specification. On invoking the REST 3.0
service from Swagger UI, the runtime Swagger is
generated as per OpenAPI 3.0 Specification.

Note: Note: The Swagger 3.0 JSON file containing

OpenAPI 3.0-specific features, which are not in parity with
the Swagger 2.0 JSON file, is not supported.

Encryption and decryption TIBCO BusinessWorks Container Edition provides capability

of application profiles. to encrypt complete application profiles which can be
decrypted while debugging and at runtime. It helps to increase
security for application properties containing confidential
information.

For more information about encrypting profiles in TIBCO

Business Studio™ for BusinessWorks™, see "Encrypting an
Application Profile" in TIBCO BusinessWorks Container
Edition Application Development.

Now you can capture the Set the following logger in the logback.xml file :
details of query
parameters sent as a part <logger name="com.tibco.bw.binding.rest">
of the incoming request to <level value="DEBUG"/>
</logger>
a REST service.

A namespace prefix is The response received from SOAP RPC Literal service was
now added for SOAP malformed. Hence the namespace prefix is prepended to the
RPC Literal response. Response element.

New error code to The TIBCO-BW-BINDING-SOAP-550101 error code is

represent SOAP displayed on the Invoke activity on receiving Undeclared
Undeclared Client Fault Client Fault in response from a SOAP service. In case of
server error, the error code TIBCO-BW-BINDING-SOAP-
550100 is displayed.

TIBCO BusinessWorks™ Container Edition Release Notes

10 | New Features

Common Features

For more information, see "SOAP Binding Error Codes" in the

TIBCO BusinessWorks Container Edition Error Codes .

Support is added for This release adds support for OAuth 2.0 configuration on
OAuth 2.0 configuration HTTP Client shared resource for getting OAuth access and
refresh token.

It also adds ability to include access token in outbound REST

reference.

A new OAuth Configuration shared resource is added.

For more information, see "OAuth Configuration Resource" in

TIBCO BusinessWorks Container Edition Bindings and
Palette Reference.

Plug-in manager You can now install and uninstall TIBCO BusinessWorks
Container Edition plug-ins from TIBCO Business Studio for
BusinessWorks in a more simplified way using Plug-in
manager.

For more information, see "Installing Plug-ins using

BusinessWorks Plug-ins Manager" and "Uninstalling Plug-ins
using BusinessWorks Plug-ins Manager" in TIBCO
BusinessWorks Container Edition Installation.

Support is added to You can update the flow limit dynamically and using the REST
update flow limit APIs.
dynamically.
For more information, see "Updating Flow Limit Dynamically"
in TIBCO BusinessWorks Container Edition Application
Monitoring and Troubleshooting.

Design Time

Visual Diff You can compare two revisions of a process and its artifacts side
by side visually in TIBCO Business Studio for BusinessWorks. It
highlights changes in newer revision such as addition or removal of

TIBCO BusinessWorks™ Container Edition Release Notes

11 | New Features

Design Time

activities, changes in an activity configuration.

l You can compare the application properties sections of two
projects and difference between the two profiles of the same
project.
l You can compare the module properties sections of two
projects.
l This feature supports the visual difference for encrypted
profiles.
l You can compare two revisions of a process.
l You can compare shared resources.
l It provides integration with GIT and SVN to compare
revisions stored in a version control system along with local
revisions.

For more information, see "Diff Viewer" in TIBCO BusinessWorks

Container Edition Application Development.

Sorting functionality Now you can move the rows up or down and sort the roles in
is available for roles. ascending or descending order.

Custom Icon is now The Custom Icon field is added on the General tab for the Call
introduced for Call Process and Java Invoke activities.
Process and Java
For more information, see "Call Process" and "Java Invoke" in
Invoke activities.
TIBCO BusinessWorks Container Edition Bindings and Palettes
Reference.

For more information on how to add the custom icons, see "Adding
Custom Icons" in TIBCO BusinessWorks™ Container Edition
Application Development.

Support is provided You can use a module property for the Client ID on a JMS
for module property Connection resource.
for the Client ID on
the JMS
Connection.

TIBCO BusinessWorks™ Container Edition Release Notes

12 | New Features

Design Time

Support is added for Ability to import and export pre-designed application templates
application designed with best practices and pre-configured processes, shared
templates. resources, modules etc.

It helps improve collaborative development experience and

reusability where team members can design their applications
using application templates.

You can perform the following operations:

l Export an existing project as a template.
l Create a project using a template.
l Modify an existing template.

For more information, see "Working with Templates" in TIBCO

BusinessWorks Container Edition Application Development.

Palettes

The ResourcePath element is added on An additional element ResourcePath is added on the

the Input tab of the Invoke REST API Input Tab of the Invoke REST API activity for
activity. overriding the Resource Path value on the
General tab of the activity.

Support is added for PostgreSQL Support is added for PostgreSQL failover URL.
failover URL. For example:

jdbc:postgresql://host1:port1,host2:port2/database

The Loop Subset in Current Process These options are enabled only when the process
check box and the Loop Subset in in subsets is selected.
Calling Process field are added on
For more information, see "JDBC Query" in
the Advanced tab of the JDBC Query
TIBCO BusinessWorks Container Edition Bindings
activity.
and Palettes Reference.

TIBCO BusinessWorks™ Container Edition Release Notes

13 | New Features

Palettes

A new Interpret Invalid XML Chars Select the check box to avoid getting problems
check box is added on the Advanced with illegal chars.
tab of the JDBC Query activity.

Now you can enable Debug level logs Now the input and output for the Parse JSON and
for the Parse JSON and Render Render JSON activities are logged when the
JSON activities. Schema Type is selected as XSD on the General
tab, by enabling Debug level logs.

Add the following logger in the logback.xml file :

<logger name="com.tibco.bw.palette.restjson">
<level value="DEBUG"/>
</logger>

Support is added for the square You can pass a query parameter having the
bracket ([]) in the resource path. square ([]) bracket in the Invoke REST API
activity's Resource Path field on the General tab
or Input tab using percent-encoding for ? as %3F.

Runtime

Integration for This release adds support for ECS Services with AWS Parameter
ECS Services with Store on TIBCO Business Studio for BusinessWorks.
AWS Parameter
For more information see, "Integrating ECS Services with AWS
Store
Parameter Store" in theTIBCO BusinessWorks Container Edition
Application Development .

Support is added This release adds the ability to collect activity instance and process
to collect activity data instance.
instance and
The activity instance and process instance data is collected from the
process data
Appnode and is stored in a database. The data can be queried by
instance.
using REST APIs to find maximum time consuming and maximum
memory consuming activities and processes.

TIBCO BusinessWorks™ Container Edition Release Notes

14 | New Features

Runtime

For more information, see "Collecting Performance Parameters with

respect to Activities and Processes" in the TIBCO BusinessWorks
Container Edition Application Monitoring and Troubleshooting.

For more information on New Features prior to TIBCO BusinessWorks Container Edition
2.6.0 release, see New Features

TIBCO BusinessWorks™ Container Edition Release Notes

15 | Changes in Platform Support

Changes in Platform Support

There are no changes in platform support in TIBCO BusinessWorks™ Container Edition.
For a complete list of all the currently supported platforms, see the readme file.

TIBCO BusinessWorks™ Container Edition Release Notes

16 | Changes in Functionality

Changes in Functionality
The following notable changes in functionality have been made in TIBCO
BusinessWorks Container Edition and are listed by release.

Release 2.6.2

Runtime

By default, the Earlier, the logback.xml file in TIBCO BusinessWorks Container Edition
logback.xml file for runtime had just the hour as trace.
console output
Now, the logback.xml in TIBCO BusinessWorks Container Edition
includes both
runtime for console output includes both date and time as trace.
the date and
time.

Change in the Earlier, the default base OS image was debian:stretch-slim.

default base OS
Now, it is changed to debian:buster-slim to fix some security
image
vulnerabilities.

Sending SSL Earlier, to send a SSL based request with Send HTTP Request activity
based request using Jetty HTTP Client library to a REST service, the Mutual
using Jetty Authentication checkbox on SSL Client shared resource needed to be
HTTP Client enabled
without Mutual
Now, to send a SSL based request with Send HTTP Request activity
authentication
using Jetty HTTP Client library to a REST service, the Mutual
Authentication checkbox on SSL Client shared resource does not need
to be enabled. In Studio console, the "java.lang.IllegalStateException"
warning message is generated but the application executes end-to-end.

Release 2.6.1
There are no changes in functionality in TIBCO BusinessWorks™ Container Edition

TIBCO BusinessWorks™ Container Edition Release Notes

17 | Changes in Functionality

Release 2.6.0

General

The Earlier the TIBCOBusinessStudio.ini file was present inside

TIBCOBusinessStudio.ini TIBCOBusinessStudio.app folder.
file is present at the
Now from TIBCO BusinessWorks™ Container Edition 6.7.0, the
/studio/4.0/eclipse folder
TIBCOBusinessStudio.ini file is present under eclipse folder.
location on Mac
operating system.

Change in the The name of the deployment method is now changed from
deployment method "Appspace" to "BW Appspace".
name

Change in a way to When TIBCO BusinessWorks Container Edition application with

discover application REST reference and with Mesh service client enabled was
server URL. launched from TIBCO Business Studio for BusinessWorks, the
application invoked a Mesh service from the application on an
application server. The application server's URL was determined
by fixed rules.

After a fully-qualified domain names (FQDN) service is provided,

when the TIBCO BusinessWorks Container Edition application is
launched, TIBCO Business Studio for BusinessWorks accesses
the FQDNs and discovers the application server URL from it
using a domain URL.

EGIT plug-in There is no need to install EGIT plugin manually.

installation
EGIT plug-in version 4.4.1 is now a part of TIBCO Business
Studio for BusinessWorks itself.

To verify the installation, navigate to Help > Installation Details

> Plugins (Egit).

Migration

Addition of the module Earlier, after migration, the customxpathfunction jar-name did not
name as a prefix to the have prefix of the module name in it and it migrated as a plain

TIBCO BusinessWorks™ Container Edition Release Notes

18 | Changes in Functionality

Migration

custom Xpath function customxpathfunction jar for the custom Xpath functions.

Now, the CustomXpathFunction jar that is generated by the

migration tool contains the name of the module as prefix before
the customxpathfunction jar name.

For example, in SampleApplication_CustomXpathFunction.jar,

SampleApplication is the module name.

Runtime

The default local of the Docker file for Earlier, the default local of the Docker file for
TIBCO BusinessWorks Container Edition TIBCO BusinessWorks Container Edition was
is UTF-8 POSIX.

Now, The default local of the Docker file for

TIBCO BusinessWorks Container Edition is
UTF-8.

For more information on Changes in Functionality prior to TIBCO BusinessWorks

Container Edition 2.6.0 release, see Changes in Functionality

TIBCO BusinessWorks™ Container Edition Release Notes

19 | Deprecated and Removed Features

Deprecated and Removed Features

This section lists the features that have been deprecated or removed in this release.

Deprecated Features
Release 2.6.2
No features are deprecated in TIBCO BusinessWorks Container Edition
Release 2.6.1
No features are deprecated in TIBCO BusinessWorks Container Edition

Release 2.6.0
The Universal Installer for TIBCO BusinessWorks Container Edition will not ship the out
of the box support for SVN from the next release. TIBCO provides a separate
documentation on how to add the SVN support.

Removed features
Release 2.6.2
No features are removed in TIBCO BusinessWorks Container Edition
Release 2.6.1
No features are removed in TIBCO BusinessWorks Container Edition.
Release 2.6.0

No features are removed in TIBCO BusinessWorks Container Edition.

TIBCO BusinessWorks™ Container Edition Release Notes

20 | Closed Issues

Closed Issues
The following are the closed issues in TIBCO BusinessWorks™ Container Edition.
The closed issues are grouped by components:
l Binding
l General
l Migration
l Monitoring
l Palette
l Policies
l Runtime

For more information on Closed Issue prior to TIBCO BusinessWorks Container Edition
2.6.0 release, see Closed Issues

Binding
This topic lists closed issues related to Binding.

Release 2.6.2

Key Description

BWCE- The BinaryContent field is not visible in HTTP Receiver activity's output
3962 schema with the PATCH and PUT methods of the REST service binding when
you set the Output Style as Binary on the General tab of the HTTP Receiver
activity.

BWCE- Swagger UI request is sent to a wrong port if TIBCO ActiveMatrix

3690 BusinessWorks application exposes multiple REST endpoints by using
separate HTTP Connector shared resource.

BWCE- TIBCO Business Studio for BusinessWorks displays the 500 internal server error

TIBCO BusinessWorks™ Container Edition Release Notes

21 | Closed Issues

Key Description

3323 when you have the following configuration in the REST service binding:

l On the General tab of the REST service binding,

o The Enforce BW Service Response check box is selected
o The Response Client Format is JSON

l On the Response tab:

o Use Empty Values for Null check box is selected.

l The complex type element having "nillable=true" is sent with Set Explicit
Nil selected in the Input tab.

Release 2.6.1

Key Description

AMBW- The operationID field is now displayed in the runtime Swagger file of a REST
42099 service when it is hit from Swagger UI.

AMBW- The Configure Local Swagger option does not work when you import a
35328 project in TIBCO Business Studio™ for BusinessWorks™ first and then
configure the Local Folder path in the API explorer tab.

Release 2.6.0

Key Description

AMBW- After migration, the org.apache.axiom.om.OMException: Unable to determine

41468 SOAP version error occurred when an attachment style was MTOM.

Add the following property:

bw.binding.soap.client.reply.mtom.contenttype.override=true.

AMBW- The unbound header parts were missing in the concrete WSDL generated at

TIBCO BusinessWorks™ Container Edition Release Notes

22 | Closed Issues

Key Description

41299 design time using the Generate Concrete WSDL option from SOAP service,
which imported another WSDL importing request and response header XSDs.

AMBW- The Apache Axis2 threads were not increased with an increase in load.
41129

AMBW- The Unbound Header parts were missing in the runtime concrete WSDL
40680 retrieved from SOAP service with version 1.2.

AMBW- The Unbound Header parts were missing in the runtime concrete WSDL
40679 retrieved from a SOAP service when the abstract WSDL imported another
WSDL, and the WSDL imported request and response header XSDs.

AMBW- The incorrect error code 403 Forbidden was thrown for the Invoke activity in a
39997 SOAP over HTTP application when the HTTP Client shared resource was
configured with the following options:
l Default port = 443
l Implementation Library = Apache HttpComponents(Supported by HTTP
1, SOAP and REST)
l Default Confidentiality check box was selected.

AMBW- The time required for runtime concrete WSDL retrieval for a SOAP service
39819 increased if more applications with a large number of schemas were deployed
on the same AppNode.

AMBW- The runtime concrete WSDL took too much time to generate when an
39038 endpoint was hit in the browser, because the schema cache was not initialized
before WSDL retrieval.

General
This topic lists the closed issues related to General issues.

Release 2.6.2

TIBCO BusinessWorks™ Container Edition Release Notes

23 | Closed Issues

Key Description

BWCE- For the End activity, the testFilePath and activityTestInput fields are not
3982 shown on the Test tab when you select the Activity Assertion Mode and
select the Gold Input From File check box.

BWCE- Now you can generate Manifest.json file for cloud projects by using the
3889 following bwdesign command line utility: generate_manifest_json -project <project_
name> <location to generate manifest.json file>

BWCE- For an existing TIBCO ActiveMatrix BusinessWorks process, a schema

3844 namespace is not refreshed when you define a new exception type as a part
of a new activity added in a process.

BWCE- TIBCO Business Studio for BusinessWorks throws a validation error when the
3777 transition conditions of parallel JDBC palette activities inside the Local
Transaction group are mutually exclusive.

BWCE- The Validate button in the Process launcher XML dialog box validates the
3719 input now.

BWCE- The Transform XML activity cannot process an XSLT that has multiple sort
3697 elements.

BWCE- The Mapper activity cannot sort the values of type DateTime and Date.
3696

BWCE- TIBCO Business Studio for BusinessWorks becomes unresponsive when you
3587 open processes of the external shared modules that are imported from a
Maven repository.

BWCE- On Cent OS, TIBCO Business Studio for BusinessWorks cannot display the
3418 Cloud Container Service Configuration dialog box when you set the
Deployment Target as Container and select the Browse Container
Configuration for an application property in the application properties editor.

BWCE- BWDesign Utility fails to start on SUSE 12.5

3397

TIBCO BusinessWorks™ Container Edition Release Notes

24 | Closed Issues

Key Description

BWCE- If you change a schema on the Start activity, the test input is not updated
2541 automatically and there is no way to update the test input to reflect the new
schema.

BWCE- TIBCO JRE is removed from openjdk:8-jdk-alpine based container image.

2015

AMBW- In some scenarios, migrating a JDBC project displays a validation error for the
42962 Iteration Element in the Iterate group.

AMBW- TIBCO Business Studio for BusinessWorks becomes unresponsive

42859 intermittently when you import a shared module through maven plug-in.

AMBW- An application throws an error when an activity's XPath expression contains

42640 the insert-before() function.

AMBW- The Iterate group in a subprocess generates incorrect output when two
42627 different processes call the same subprocess containing the Iterate group at
the same time.

AMBW- The Mapper activity displays the literal white space character ('') is not datatype-valid
42583 with respect to the datatype definition '{http://www.w3.org/2001/XMLSchema}double' error.

To avoid typecasting error, use the following VM argument:

-Dbw.xml.general-comparison.ignore-numeric-cast=true

AMBW- You cannot add the duplicate When condition along with its expression if you
40371 use the Surround with Choice option for an element, and then try to duplicate
the When condition.

AMBW- An application with Timer and Log activities fails and displays the Invalid
37898 BWApplicationHandle error when an AppSpace is configured in an FT Group
mode and you restart an application on a new AppNode.

Release 2.6.1

TIBCO BusinessWorks™ Container Edition Release Notes

25 | Closed Issues

Key Description

BWCE- All the unbounded elements are not loaded on the Process Launcher tab if an
3732 XML file is provided having unbounded elements in the Validate Schema
dialog box.

BWCE- When the namespace prefix is changed in the Validate Schema window on
3731 the Process Launcher tab, the request message is not updated as per the
validated schema.

BWCE- When the non-string elements are removed from the Validate Schema dialog
3725 box, the corresponding elements are not removed from the Process Launcher
tab.

AMBW- After renaming a process package, the Input tab of the Call Process activity is
42534 not displayed.

AMBW- After Tibtunnel recovers from its termination, TIBCO BusinessWorks

42086 Container Edition cannot connect to the on-premise resources such as
Enterprise Message Service (EMS) for the one round of Timer trigger.

AMBW- The CurrentElement of the Iterate Group is not populated and the element
42068 remains empty.

AMBW- The Last Modified date of an API in the API Explorer tab is incorrect.
41099

Release 2.6.0

Key Description

BWCE- Mashery integration did not show endpoint definition when port mappings
3294 were used.

BWCE- The application property screen went blank intermittently while performing any
3262 tasks on the application properties.

BWCE- When profile properties file was exported using bwdesign utility for TIBCO

TIBCO BusinessWorks™ Container Edition Release Notes

26 | Closed Issues

Key Description

3207 BusinessWorks Container Edition applications, the property values exported

were different than the ones provided in TIBCO Business Studio for
BusinessWorks.

AMBW- The activity input data validation error occurred when converting a double
41613 value to a decimal value and the -Dbw.application.activity.validateOutput=false
property was set in the config.ini file.

A new -Dbw.xml.decimal.allowDoubleExponent property is added.

Set the -Dbw.xml.decimal.allowDoubleExponent property to true along with the -

Dbw.application.activity.validateOutput=false in the config.ini file.

AMBW- The Iterate group for a schema element did not work when the element
41298 belonged to a no-namespace schema.

AMBW- The trim() mapper function in the Group by clause failed and generated the
41223 XSLT transformation error at run time.

AMBW- The input tab mappings were not visible for activities when the if condition in
41221 the XPath function was empty.

AMBW- The coercion failed to fetch the correct elements for mapping and displayed a
40860 validation error at design time when there were two elements of the same
name and namespaces, but from the different schemas.

AMBW- Support for migration of the tib:evaluate function is provided in TIBCO

40453 BusinessWorks™ Container Edition 2.6.0.

AMBW- TIBCO Business Studio for BusinessWorks displayed null pointer exception
40436 when constructing the CatchAllFaultDetails document because of the incorrect
transition link from the Scope.

Now, the following error message is displayed whenever there is a link in the
process that has the source activity set as the group end activity.

Outgoing link from Group End activity of <group_name> group is incorrectly

configured. Please delete and recreate it to repair or apply the quick fix.

TIBCO BusinessWorks™ Container Edition Release Notes

27 | Closed Issues

Key Description

Applying the quick fix deletes the erroneous link and recreate the link with the
correct serialization.

AMBW- TIBCO Business Studio for BusinessWorks did not select subprocesses
40295 correctly in the Run Configuration and Debug Configuration windows.

AMBW- The XSD resolver could not process the id attribute in the xs:group element.
39898

AMBW- TIBCO Business Studio for BusinessWorks did not display appropriate error
39820 for a transition from the Group End activity to any activity inside the Group.

AMBW- The current-dateTime() function returned different representation of output in

39494 TIBCO Cloud Integration, ActiveMatrix BusinessWorks, and TIBCO
BusinessWorks Container Edition.

AMBW- After migration, coercion disappeared and had to be remapped frequently.

38971

AMBW- TIBCO Business Studio for BusinessWorks failed to generate .EAR from
38966 studio and bwdesign utility due to null pointer exception.

AMBW- TIBCO Business Studio for BusinessWorks displayed an error in the

38787 Problems tab when a module property inside a shared module referred a
process property of type JDBC Connection.

AMBW- Leading or trailing white spaces from alias name of SSL server shared
38748 resource did not trim when the value type was literal value.

AMBW- Null pointer exception occurred while generating .EAR for specified customer
38292 project.

AMBW- While moving the JMS shared resources from an application module to a
37808 shared module, TIBCO Business Studio for BusinessWorks didn't refactor the
module property path correctly.

AMBW- The Job Data view in the debugger became unresponsive while displaying

TIBCO BusinessWorks™ Container Edition Release Notes

28 | Closed Issues

Key Description

37597 large data.

AMBW- The validation message was not displayed on using the parallel JDBC activity
37112 inside the Local Transaction group.

AMBW- An application was not visible in the Debug Configuration window when the
36034 project's name was different than the value of the ID field of the Overview
section of the project.

AMBW- The Iterate group configuration error because of schema used does not have
34133 namespace. error reported if the Iterate group used schema without
namespace.

Migration
This topic lists the closed issues related to Migration.

Release 2.6.0

Key Description

BWCE- Post migration and mavenising a project, during a build or deployment of the
3586 project a NullPointerException occurred due to the sequencing of the
MANIFEST.MF file in the CustomXPathfunction jar.

BWCE- The MANIFEST.MF file in the CustomXPathfunction jar is now the first entry
3568 whenever the jar contents are extracted.

AMBW- After migration, the $error_<activityname> was not migrated and failed to fetch
41319 error details from the Local Transaction group.

AMBW- After migration, the subprocess containing the padfront() function failed at
41022 runtime.

AMBW- After migration, multiple errors occurred for DTD to XSD conversion.
40178

TIBCO BusinessWorks™ Container Edition Release Notes

29 | Closed Issues

Key Description

AMBW- After migration, the SOAP Request Reply activity could not migrate
40068 successfully.

AMBW- After migration, transitions to Invoke activities were not present in a process.
40067

AMBW- After migration, the faultDetails mapping was incorrect.

38737

AMBW- After migration from the SAP adapter configurations to TIBCO ActiveMatrix
37700 BusinessWorks™ Plug-in for SAP, the mappings were not migrated.

AMBW- After migration, the pipe character ('|") was converted to the "or" condition
37114 which resulted in incorrect activity output.

AMBW- The transition condition now has the migration support of adding the XPath 1.0
31022 tag.

Monitoring
This topic lists the Closed Issues related to Monitoring.

Release 2.6.0

Key Description

BWCE- The Database table was getting locked when any operation occurring on an
3443 application, that had a large number of application instances.

BWCE- The TransitionLoggingStats was getting logged in to the database only when
2749 instrumentation and process monitor was enabled. By default it is disabled.

Palette
This topic lists the Closed Issues related to Palettes.

TIBCO BusinessWorks™ Container Edition Release Notes

30 | Closed Issues

Release 2.6.2

JDBC Palette

Key Description

AMBW- With the SQL Direct activity in an application, a heap memory leak is
43088 observed on an AppNode.

AMBW- TIBCO Business Studio for BusinessWorks displays timeout error with SQL
42888 stored procedures when you use Data Direct Driver and XML type parameters
as IN or OUT.

JMS Palette

Key Description

BWCE- The JMS Receieve Message activity throws an error when the Message
3887 Type is set as Text on the General tab of the JMS Receive Message activity
but the message contains the byte content.

To align the functionality with TIBCO ActiveMatrix BusinessWorks 5.x, the new
property is added.

Set the bw.jms.receiver.deserialize.message.as.bw5=true property in the AppNode's

config.ini file to receive appropriate content.

REST and JSON Palette

Key Description

BWCE- The output of the Render JSON activity shows the decimal number in double
3689 quotes ("") if both of the following conditions are met:

l On the General tab, the Badgerfish check box is selected.

l Schema element is of complexType with extension base and contains

decimal type value.

TIBCO BusinessWorks™ Container Edition Release Notes

31 | Closed Issues

REST and JSON Palette

Key Description

AMBW- The design time and runtime Swagger files now include the definitions of the
43096 extended elements from different XSD.

XML Palette

Key Description

AMBW- The Value-of max(xsd:int*) expression returned as a scientific notation value when
42474 the Transform XML activity has bigger numbers in input.

Release 2.6.1

File Palette

Key Description

AMBW- The Write File activity cannot generate a file when the TextContent field has
42344 the space character (" ") value.

HTTP Palette

Key Description

BWCE- The routing URL is unavailable when user defined module property value
3639 localhost is configured in the HTTP Connector shared resource.

For docker or cloud foudry, you can set the property by passing it in BW_
JAVA_OPTS environment variable as
Dbw.user.module.property.value.localhost.resolved=true to access the route URL.

TIBCO BusinessWorks™ Container Edition Release Notes

32 | Closed Issues

Mail Palette

Key Description

AMBW- An application becomes unresponsive on the Send Mail activity and does not
42212 timeout when the existing engine threads are occupied.

JDBC Palette

Key Description

BWCE- When the Nil option is selected in SQL Direct and the table is left empty or
3687 only one of the columns contains data then at runtime the Activity output data
validation error is displayed.

Release 2.6.0

FTP Palette

Key Description

AMBW- The FTP Rename File activity failed intermittently to rename files from a
38106 particular directory when the FTP Rename File activity was a part of a
subprocess, which was called from a Call Process activity with the Spawn
check box selected.

HTTP Palette

Key Description

AMBW- The Send HTTP Request activity threw the HttpClientException when the
41408 application deployed on TEA was restarted, and the HTTP Client shared
resource had the Apache HttpComponents(Supported by HTTP 1, SOAP
and REST) implementation library, and the Provide Client Resource check
box was selected on the Advanced tab of the Send HTTP Request activity.

TIBCO BusinessWorks™ Container Edition Release Notes

33 | Closed Issues

HTTP Palette

Key Description

AMBW- The SSL was configured even when the SSL Client shared resource picker
41006 was not empty and the module property against the Confidentiality field at
HTTP Client shared resource was set to false.

Set the bw.plugin.http.client.relyOnConfidentialityField property to true.

AMBW- The Send HTTP Request activity could not send the request with Content-
40484 type as multipart/form-data to ServiceNow with Apache HttpComponents
library.

Send the POST request using the Jetty HTTP Client library in the HTTP Client
shared resource.

JDBC Palette

Key Description

AMBW- The JDBC connection created against the database increased beyond the
41608 configured value when any of the following cases occurred:
l There was a network issue.
l Database was stopped or started
l The bw.engine.activity.async.waitTime property was present in the config.ini file.

AMBW- The Null Pointer Exception was thrown when re-connecting the database with
41215 an application.

AMBW- The input and output parameters for a stored procedure were not accessible
41146 when the stored procedure was inside a package.

AMBW- The JDBC Call Procedure activity failed and generated the Unknown
41145 exception occurred.

AMBW- TIBCO BusinessWorks™ Container Edition generated the

40335 java.sql.SQLException at runtime when the Database URL had forward
slashes in the sslTrustStoreLocation path.

TIBCO BusinessWorks™ Container Edition Release Notes

34 | Closed Issues

JMS Palette

Key Description

BWCE- The Get JMS Queue Message activity was not able to reconnect to EMS
3292 when there was an EMS connection failure.

AMBW- For the ActiveMQ JMS provider, the JMS Receive Message activity failed to
41548 reconnect for network issues.

AMBW- The JMS Send Message activity displayed the Null pointer exception
40637 intermittently when messages were sent in concurrent batches.

AMBW- The JMS Request Reply activity can now filter requests and response
35597 messages correctly on the basis of JMS CorrelationID or MessageID.

AMBW- Messages were stuck in an EMS queue when the EMS connection dropped
34959 and reconnected.

This issue occurred intermittently when the AppSpace was configured with
FTgroup persistence with the EMS FT URL.

Also, the secondary EMS server was not available intermittently after the
failure of the first server.

AMBW- In TIBCO Business Studio™ for BusinessWorks™, the default value for the
33187 Directory preference option on the BusinessWorks > Palettes > JMS
preference page was invalid.

Mail Palette

Key Description

AMBW- The Receive Mail activity used to start the handshake with TLSv1 irrespective
39777 of the TLS SSL Protocol selected in the SSL Client Configuration for the
SMTP shared resource.

AMBW- The Send Mail activity used to start the handshake with TLSv1 irrespective of
39776 the TLS SSL Protocol selected in the SSL Client Configuration for the SMTP
shared resource.

TIBCO BusinessWorks™ Container Edition Release Notes

35 | Closed Issues

REST and JSON Palette

Key Description

AMBW- For some scenarios, the Parse JSON activity generated the
41167 XMLStreamException in the console, in logs and the Output tab in Job Data
view became empty when an application was executed in the debug
configuration.

Set the bw.engine.debug.core.disableNamespaceFixup property to true.

Do not use this property while mocking the output for unit testing.

AMBW- The Parse JSON activity could not parse a JSON key having a value of array
40875 type with length more than 512 characters.

AMBW- Logs for the Invoke REST API activity now also display the response body
40618 information. Set the following logger in the logback.xml file:

<logger name="com.tibco.bw.palette.restjson.runtime.RestInvoke">
<level value="DEBUG"/>
</logger>

XML Palette

Key Description

AMBW- The Parse XML activity threw Content is not allowed in prolog error when the
41240 input file encoding was UTF-8-BOM and the Validate Output check box was
selected.

Set the -Dbw.application.activity.validateOutput.treeValidation=true property as a VM

argument when validating an output XML.

AMBW- An error occurred when the YearMonth datatype was typecasted with the
33245 xsd:string().

Policies
This topic lists the Closed Issues related to Policies.

TIBCO BusinessWorks™ Container Edition Release Notes

36 | Closed Issues

Release 2.6.1

Key Description

BWCE- If a policy is applied at root "/" level, then it gets applicable to every path under
3544 it, unexpected calls are received at governance layer which leads to memory
leak.

Runtime
This topic lists the Closed Issues related to Runtime.

Release 2.6.2

Key Description

AMBW- The Wait and Notify activities in the group persistence mode do not work with
43223 default values for the bw.engine.threadCount and bw.engine.db.maxConnection
properties.

The following new properties are introduced in the AppSpace's config.ini file:
l com.tibco.bx.lockWaitNotify=true

l com.tibco.bw.throttle.notify.activity=true

l com.tibco.bw.throttle.wait.activity=true

Use the throttle properties when default configuration is used.

The bw.engine.db.maxConnection value must be greater than the

bw.engine.threadcount value.

AMBW- Some of the TIBCO BusinessWorks Container Edition jobs are not processed
43222 intermittently when an application has the Wait and Notify activities.

To avoid the deadlock scenario, TIBCO recommends to set the

com.tibco.bx.lockWaitNotify=true property and the value of bw.engine.db.maxConnection
property = twice the value of bw.engine.threadCount.

AMBW- The performance is degraded in the Iterate group.

TIBCO BusinessWorks™ Container Edition Release Notes

37 | Closed Issues

Key Description

42815

AMBW- The Iterate group maps incorrect data to the iteration element when the
42771 Iterate group is executed by multiple jobs at the same time.

AMBW- Two applications incorrectly refer to the same hashmap in some cases when
41331 an AppNode starts the applications at the same time, and an activator process
is used along with custom XPath functions.

Release 2.6.1

Key Description

BWCE- An exception occurs in debug mode for console, when the ASCII Characters
3712 are not be serialized or parsed in XML.

AMBW- The BW.MODULE.NAME and BW.MODULE.VERSION module properties

42418 return empty values.

AMBW- On stopping an application, the application cannot call the delete method of
42416 the shared resource when the shared resource uses a module property in one
of the fields.

AMBW- TIBCO Business Studio for BusinessWorks displays an error message for the
42125 OAuth Configuration shared resource when the confidentiality is not defined
for the HTTPS.

AMBW- Modifications done inside a running application in TIBCO Business Studio for
40159 BusinessWorks displays the Process not found error.

Release 2.6.0

Key Description

BWCE- The JDBC Call Procedure activity failed by timeout when the store procedure
3396 used had a complex nested array type of objects.

TIBCO BusinessWorks™ Container Edition Release Notes

38 | Closed Issues

Key Description

BWCE- The performance of xsl:apply-templates was poor, when the optional Select
1665 attribute contained a XPath expression which was not an empty string. The
optimizer now recognizes such XPath expressions that can be sped up, and
improves performance in supported cases significantly.

AMBW- The <?xml-multiple?> tag disappeared from the output of the Parse XML activity
41486 when the Validate Output check box was selected.

Set the -Dbw.application.activity.validateOutput.treeValidation=true property as VM

argument to add the tag when validating an output XML.

AMBW- The <msgCode> tag under FaultDetails could not capture the actual msgCode
41289 value.

AMBW- An application was unable to resolve a process variable on startup for the
41222 Assign activity, even though the Call Process activity in the same process
could resolve the same process variable.

AMBW- The Engine Command activity did not stop an application when an application
41218 was restarted.

AMBW- Memory leak issue was observed due to an instance of to

41207 org.eclipse.xsd.XSDSchemaDirective[] on an AppNode.

AMBW- After upgrading, the Transform XML activity took more memory and
41045 generated the Out of Memory Exception.

AMBW- An application could not be started when its status was STARTFAILED.
40793

AMBW- An application using WSDL from a shared module failed to restart and
40362 displayed the java.lang.IllegalStateException: BundleContext is no longer
valid error.

AMBW- The conversation handler failed when multiple AppNodes were set up in a
40232 group persistence mode.

AMBW- Ability to evaluate transition expression as XPath 1.0 expression

TIBCO BusinessWorks™ Container Edition Release Notes

39 | Closed Issues

Key Description

40145 Set the bw.engine.use.transition.xpath.expression.lang.1.0 property to true in the

AppNode's config.ini file.

By default, the value is false.

AMBW- The performance was degraded in the Iterate Group activity.

38813

AMBW- When an application had a persistent shared module in the group mode, the
36149 following error occurred intermittently: PVM-MODEL-102700.

AMBW- After migration, the Repeat group used in a calling process displayed
33830 java.sql.SQLException when the JDBC Query activity was configured with a
process in subsets used inside a subprocess.

TIBCO BusinessWorks™ Container Edition Release Notes

40 | Known Issues

Known Issues
The following known issues have been introduced in TIBCO BusinessWorks™ Container
Edition .

The known issues are grouped by components:

l Binding
l General
l Migration
l Mocking Support
l Monitoring
l Palettes
l Policies
l Runtime

Binding
This topic lists the Known Issues related to Binding.

Key Description

BWCE- Summary: The Swagger UI does not load the resource path details for
3983 applications having multiple REST services with separate HTTP Connector for
each endpoint on Cloud Foundry.

Workaround: None.

AMBW- Summary:The Swagger UI is blank when the swagger URL is hit from Internal
43156 Web Browser in TIBCO Business Studio for BusinessWorks 6.7.0

Workaround:Hit the swagger URL from external browser.

AMBW- Summary:For form parameter of password type, the Swagger JSON under
43023 service descriptors has missing "format": "password" key-value inside the

TIBCO BusinessWorks™ Container Edition Release Notes

41 | Known Issues

Key Description

Schema object.

Workaround: Manually add the "format" : "password" tag to the form

parameter in the swagger file.

AMBW- Summary: A multipart message where one part points to type and the other
36113 part points to element and a message using mixed security mode is not
supported.

Workaround: Change mixed security mode in a given WSDL.

AMBW- Summary: A SOAP service responding with mustUnderstand attribute as true

32951 is ignored irrespective of selecting or deselecting the Ignore mustUnderstand
check box on the SOAP Reference binding. This behavior does not affect the
client and server communication.

Workaround: None

AMBW- Summary: On creating SOAP Reference Binding with the concrete WSDL
32760 generated at run time with multilevel schema imports, the
java.lang.NullPointerException is displayed when clicking the reference
binding.

Workaround: None

AMBW- Summary: When creating a concrete WSDL by right-clicking on the Service

29098 Descriptor folder, the following error is generated at design time: WSDL
import error.

Workaround: None

AMBW- Summary: On importing WSDL with RPC Encoded style, a validation error is
27870 generated at design time since the underlying schema with namespace
http://schemas.xmlsoap.org/soap/encoding/ is not generated.

Workaround: To remove the validation error and create the SOAP Reference
Binding, download the encoding schema with the said namespace and ensure
that schema is a part of the application module or the shared module.

AMBW- Summary: When module properties used from a shared module project were

TIBCO BusinessWorks™ Container Edition Release Notes

42 | Known Issues

Key Description

27435 renamed, the changes made were not reflected at the SOAP binding level.

Workaround: Select the updated module property from the drop down in the
SOAP binding.

AMBW- Summary: When a REST service with a schema that uses a type which was
26806 imported from another XSD is invoked in a REST Reference Binding, it fails
with the ServiceRuntimeException.

Workaround: None

AMBW- Summary: When the WSDL uses multiple parts in the Request body of an
23104 operation, a design time validation error occurs on the generated SOAP
reference binding. The application works fine at run time.

Workaround: None

AMBW- Summary: When the REST Service which is implemented with GET Operation
22981 with Response as String, then the content-type of the response is changed
from application/json to text/plain.

Workaround: Use XSD Element in Response instead of String.

AMBW- Summary: REST Doc UI is not supported on Firefox browser.

13607
Workaround: Use other browsers for the Doc UI.

AMBW- Summary: For some use cases, REST Doc UI does not show the correct error
13572 code in case of Internal Server errors on the Server side.

Workaround: Check the raw message that contains the correct error code.

AMBW- Summary: REST Doc UI does not support browsers like Internet Explorer.
13485
Workaround: Use Chrome browsers for the Doc UI.

AMBW- Summary: Changing the Resource name in the REST service Bindings tab,
8982 does not update the Resource Service Path.

Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

43 | Known Issues

General
This topic lists the Known Issues related to Binding.

Key Description

BWCE- Summary: Context-sensitive help for any activity or sample in TIBCO

4016 Business Studio™ for BusinessWorks™ is not currently available.

Workaround: Use the enhanced search functionality in TIBCO

BusinessWorks™ Container Edition 2.6.2 online help to find necessary
information.

BWCE- Summary: When an application containing Netsuite plug-in activities is

2556 deployed in TIBCO BusinessWorks Container Edition Container, a
SSLHandShakeException is thrown.

Workaround: Copy the libsunec.so library found in jre-8u<no>-linux-x64.rpm/tar.gz

which is available in Oracle resource library to /resources/addons/lib folder before
you create the base image or buildpack.

BWCE- Summary: Marketo application generates run time SSLHandshakeException

2073 for TIBCO BusinessWorks Container Edition.

Workaround: Copy the libsunec.so library found in jre-8u<no>-linux-x64.rpm/tar.gz

which is available in Oracle resource library to /resources/addons/lib folder before
you create the base image or buildpack.

BWCE- Summary: FTL application does not work in windows container because of
2008 absense of FTL client libraries for windows.

Workaround: None.

BWCE- Summary: In the FTL application logs, an Invalid message type received from
1433 peer 'NULL' error message occurs.

Workaround: None. These errors can be ignored.

BWCE- Summary: An error, related to libcrypto.so, is displayed in the logs when the
1239 application is pushed to the Cloud Foundry or Docker.

Workaround: None. These errors can be ignored.

TIBCO BusinessWorks™ Container Edition Release Notes

44 | Known Issues

Key Description

BWCE- Summary: When specifying Application Properties, if invalid login credentials

103 are specified in the Configure Container Connection Dialog, the dialog
asking for valid login credentials repeatedly pops up even after valid login
credentials are specified.

Workaround: Press the Cancel button on the dialog.

AMBW- Summary: In bwdesign, if we export substvar files with the same name twice in
41950 the same location, it does not overwrite the substvar file.

Workaround: Delete the previous substvar file and export substvar again.

AMBW- Summary: Many to one mapping is not supported for Smart Mapper.
41948
Workaround: None

AMBW- Summary: Any operation on the module or application properties that leads to
41846 a change in their order results in a faulty difference generation. So, such
operations are not supported in TIBCO BusinessWorks Container Edition
6.7.0.

Workaround: None.

AMBW- Summary: The lock icon on the encrypted profile in the difference viewer
41832 perspective is shown based on whether the workspace copy of the profile is
encrypted or not. Currently, if the workspace copy of the profile is encrypted,
then in the difference viewer perspective, the lock icon is shown even on the
un-encrypted revisions of that profile.

Workaround: None.

AMBW- Summary: The properties and profile are not showing in the application
41827 property editor on opening the editor for the first time in a new workspace.

Workaround: Close and reopen the editor, it shows all the details.

AMBW- Summary: If a keystore file location or name is changed then on refresh blank
41779 property value is shown and on running the application, the File Not Found
Exception is thrown.

TIBCO BusinessWorks™ Container Edition Release Notes

45 | Known Issues

Key Description

Workaround: Restore file with a valid name at a specified location on disk and
do project clean.

AMBW- Summary: Any changes in the module or application properties inside groups
41716 are not supported in TIBCO BusinessWorks Container Edition 6.7.0 and the
corresponding difference generation is faulty in such cases.

Workaround: None.

AMBW- Summary: The difference viewer calculates the difference and highlights the
41715 properties, but does not highlight any corresponding fields of the properties.

Workaround: Switch to the text difference mode and see the difference in the
non-UI fields.

AMBW- Summary: In the substitution variables file, only five types of module
41499 properties are saved: String, Integer, Long, Boolean, and Password.

When a module property is assigned a type other than the above-mentioned

types then that type is saved as a String in the substvar file in the Diff Viewer
window.

Workaround: None.

AMBW- Summary: If there are any changes in the Description field of a module or
41474 application property, it is not highlighted in the difference viewer.

Workaround: None.

AMBW- Summary: Application property editor does not display value in case of
41307 removing encryption setting using the Clear All button and exporting profile.

Workaround: Close the application properties editor and open it again.

AMBW- Summary: When you try to install a missing plugin using the Quick Fix option
41277 and you select or unselect a plugin version from the list of provided versions;
the following message is displayed: Cannot complete the install because of a
conflicting dependency.

However, you can still install the plugin successfully.

TIBCO BusinessWorks™ Container Edition Release Notes

46 | Known Issues

Key Description

Workaround: None.

AMBW- Summary: The New Name field in the Rename Projects section on the Create
41252 Project From Template window is not enabled on a single click.

Workaround: First click on the old name of the module or the application after
which the field is enabled. .

AMBW- Summary: The Password field is shown as changed while doing a Shared
41155 Resource diff, even if the password are the same.

Workaround: None.

AMBW- Summary: Confirmation message is displayed with any operation on

41238 encrypted profiles.

Workaround: Click Yes.

AMBW- Summary: The Authentication field is shown while doing a diff when the
41035 Confidentiality field is set for Http Connector shared resource.

Workaround: None.

AMBW- Summary: Default icon shown instead of Custom icon for the Call Process
40811 and Java Invoke activities within external shared module.

Workaround: Manually browse the Custom icon field value and add
respective icon to activity on importing external shared module.

AMBW- Summary: The null pointer exception reported on clicking Binding Section in
39899 Components after the Refactoring operation.

Workaround: Post refactoring, close the Module Descriptor section and

reopen it. No popup is displayed.

AMBW- Summary: The collectappnodedata command is not working on the AIX

39837 platform.

Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

47 | Known Issues

Key Description

AMBW- Summary: Breakpoints are not working when execution flow goes from one
37594 process to another.

Workaround: Select an activity where debugging with the breakpoint is halted.

It enables the Resume button. Click the button to resume debugging.

AMBW- Summary: When you delete a module shared variables or job shared
36990 variables from the Unused Resources view, then the editor for module shared
variables or job shared variables does not get refreshed automatically

Workaround: Close the module shared variables or job shared variables and
open it again.

AMBW- Summary: Failed to connect to AppNode using SSH client

34416
Workaround: Use HTTP client. Preffered way is using curl.

AMBW- Summary: Incorrect trace is generated for the invoke process with default
34404 jaeger properties.

Workaround: Set JAEGER_SAMPLER_TYPE=const, and JAEGER_SAMPLER_

PARAM=1 properties in the AppNode or AppSpace config.ini file.

AMBW- Summary: An application fails to start in TIBCO Business Studio for

34343 BusinessWorks when you install the latest EMS driver.

Workaround: Restart TIBCO Business Studio for BusinessWorks.

AMBW- Summary: The user will not be able to create the references for the custom
32761 operations like Merge, Update, Trace etc. using the drag and drop swagger
file approach.

Workaround: Users can create the references for the custom operations using
the REST Reference wizard.

AMBW- Summary: Ungrouping nested groups created inside a catch block of a group
28941 may not ungroup as expected.

Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

48 | Known Issues

Key Description

AMBW- Summary: The tibco.bw.sample.policy.samlcredentialmapping.SoapHttpBinding sample

28663 fails intermittently with the error:
com.tibco.governance.agent.action.ActionException.

Workaround: None

AMBW- Summary: When a Process Property is renamed , the change is not reflected
28378 in the activity and an error is displayed.

Workaround: None

AMBW- Summary: WSDL interface fails to resolve correctly if multiple WSDLs share
28319 the same target namespace and the SOAP invoke is created with an external
binding reference.

Workaround: Instead of an external reference binding, use binding reference.

AMBW- Summary: When groups with the On Catch, Catch All and the OnEvent faults
28264 are created inside a constructor or a proxy operation, the activities inside them
are lost after ungrouping.

Workaround: None

AMBW- Summary: The Identity Provider field in the WSSConsumer Policy resource
27253 does not support module properties.

Workaround: None

AMBW- Summary: The option to test connections, for example JMS or sFTP, in a
25073 shared resource that has a profile is not supported in TIBCO Business Studio
for BusinessWorks.

Workaround: Specify the server configuration details as literal value or

module properties.

AMBW- Summary: TIBCO-THOR-FRWK-CMN-500001:Error while renaming bundle

24508 file to final location: - error could be due to low disk space.

Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

49 | Known Issues

Key Description

AMBW- Summary: When you initialize the module shared variable of XSD type with
19746 the select value option to point the XML instance, application fails to start at
run time.

Workaround: Enforce the default encoding of AppNode JVM to UTF-8 by

adding -Dfile.encoding=UTF-8 in the bwappnode.tra file.

AMBW- Summary: When a project contain abstract and concrete WSDL using same
19540 target namespace, a validation error is generated.

Workaround: None

AMBW- Summary: The ability to reference from a standalone (external) schema to an

18459 inline schema is not supported. If your project contains such a reference, a
validation error is generated.

Workaround: Externalize the WSDL-inline schema and change the import

statements to reference the newly created (external) schema.

AMBW- Summary: The first attempt to change the data type of an Operator's input or
16256 output schema element fails and the change is not committed. Subsequent
attempts complete without any failure.

Workaround: To commit the change, you must press the return key after
every change.

AMBW- Summary: Unable to enter an XPath expression on a transition using the

14861 XPath Builder. This issue is observed on Mac OS only.

Workaround: Enter the XPath expression directly in the Properties tab >
Expression field for the transition without using the XPath Builder.

AMBW- Summary: Under certain circumstances, substitution types do not resolve

12490 properly in the mapper. The mapper shows errors for them.

Workaround: Try closing and reopening the project. If that does not solve the
issue, try closing and reopening Eclipse. If the errors still persist, perform a
project clean (that is, go to the Project menu and click Clean...).

AMBW- Summary: TIBCO Business Studio for BusinessWorks hangs when opening

TIBCO BusinessWorks™ Container Edition Release Notes

50 | Known Issues

Key Description

11624 SQL Builder if the database details on the JDBC shared resource are
changed from PostgreSQL to MySQL after a query has been created using
SQL builder.

Workaround: None

AMBW- Summary: TIBCO Business Studio for BusinessWorks crashes occasionally

11534 on Windows 2012 R2 platform when switching workspace from File > Switch
Workspace.

Workaround: Retry by switching the workspace.

Migration
This topic lists the Known Issues related to Migration.

Key Description

BWCE- Summary: After migration, an element of simple type is not supported.

3763
Workaround: In the existing schema create an element reference for all
WSDL messages which are referring type references.

First create an element reference in inline or externalized schema and then

update WSDL message to refer the element (newly created one for complex
or simple type definition) and remove the reference of type definition.

AMBW- Summary: After migration, a path is not executed that leads to the difference
40387 in output.

Workaround: In TIBCO BusinessWorks Container Edition 5.x the transition

condition $Map-Data/ConditionType[last()] is treated as boolean but not in TIBCO
BusinessWorks Container Edition 6.x as TIBCO BusinessWorks Container
Edition 6.x has strict validations.

In order to resolve this, please update the condition as follows:

count($Map-Data/ConditionType[last()])>0

TIBCO BusinessWorks™ Container Edition Release Notes

51 | Known Issues

Key Description

AMBW- Summary: Migration of custom icon for the Call Process activity is not
40187 supported

Workaround: After migration, manually browse the custom icon field value for
the Call Process activity.

AMBW- Summary: While migrating a project using XPATH language for transitions
39231 option, which is set to XPATH 1.0 by default, on the Migration Wizard, the
Process inline namespace schema collision issue occurs intermittently after
migration is complete.

Workaround: Navigate to the faulted process and add the missing schema
location field next to the namespace.

AMBW- Summary: While migrating a project using the XPATH language for transitions
39230 option, which is set to XPATH 1.0 by default, the service agent process
migrates as an empty process thereby throwing the Argument Cannot Be Null
exception upon trying to view that process post Migration.

Workaround: Migrate that project in a different workspace, because the issue

is intermittent.

AMBW- Summary: Post migration, a schema cannot refer the .WSDL file in it and if you
36094 try to run the project, the Schema not found error is displayed at the run time.

Workaround: Copy the inline schema that gets created post migration of the
project and paste it into the .WSDL file.

Remove the inline schema dependency from the dependencies section and in
the input editor of the inline schema activity, re-map the point to the inline
element. After this remove the inline schema that is empty and execute the
project.

AMBW- Summary: After migration, if the migrated project contains any SOAP service
36077 or client binding that uses SOAP RPC Encoded arrays, the following WSDL
validation error occurs:

WSDL In-line schema SOAP encoded array type error. In-line schema in
WSDL file contains SOAP encoded array type which requires a fix pattern.

TIBCO BusinessWorks™ Container Edition Release Notes

52 | Known Issues

Key Description

Workaround: Download the SOAP Encoding schema from

'http://schemas.xmlsoap.org/soap/encoding/', and put it into the TIBCO
BusinessWorks Container Edition project.

AMBW- Summary: The migration tool does not support external schema for multi-part
35926 message in the bindings.

Workaround: Create wrapper schemas for all multi-part messages of WSDL.

AMBW- Summary: Currently, only copy-of mapping is supported for context mapping
35899 of headers.

Workaround: You can either create One-to-one mapping manually or use a

copy-of option for context mappings.

AMBW- Summary: After migration, additional round brackets in the names of the
33749 folder for externalized schema creates issues at run time.

Workaround: Remove the special characters after migration in the folder

names.

AMBW- Summary: A schema cannot contain two global components with the same
30656 name.

Workaround: Modify one of the schema namespaces or element names, so

that the names are unique.

AMBW- Summary: After migration, the input mapping for the End activity which refers
30476 to a multi-part WSDL message displays validation errors.

Workaround: A WSDL message is not supported by a mapper. Create a new

.xsd schema element with the structure similar to associated WSDL message,
and then map the schema element in place of WSDL message.

AMBW- Summary: The TransformXML activity from TIBCO BusinessWorks Container

26746 Edition 5.x did not migrate correctly if the Input/Output style of the activity was
set to TREE in the TIBCO BusinessWorks Container Edition 5.x project.

Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

53 | Known Issues

Key Description

AMBW- Summary: When you migrate an TIBCO ActiveMatrix BusinessWorks 5.x

14547 project containing in-built functions in the JDBC Query activity, an Invalid
Column name error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the TIBCO

BusinessWorks Container Edition 5.x project.

AMBW- Summary: After migration, the output of project with Rest and JSON activities
14295 does not match with the input of the other activities in the migrated project.

Workaround: None

AMBW- Summary: Shared resource module property references in the migrated

13683 TIBCO ActiveMatrix BusinessWorks 5.x projects do not show up correctly on
non-Windows platforms.

Workaround: Close and reopen the project.

AMBW- Summary: ActiveMatrix BusinessWorks 5.x projects with SOAP headers

9969 configuration in SOAP activities are not properly migrated to TIBCO
BusinessWorks Container Edition .

Workaround: SOAP functionality in TIBCO BusinessWorks Container Edition

is achieved through SOAP Binding where its detail configuration is outside of
TIBCO BusinessWorks Container Edition Process. The SOAP headers
definition are defined at the Binding configuration and configured as generic
context parameters for the Process. In the Process, you can use the Get
Context activity (from Basic Palette) to retrieve and process the headers as
context data. You can do this manually to complete the migrated project.

Monitoring
This topic lists the Known Issues related to Monitoring. .

Key Summary

BWCE- Summary: When a monitoring application is started with any database other

TIBCO BusinessWorks™ Container Edition Release Notes

54 | Known Issues

(Continued)
Key Summary

2548 than Oracle, the Oracle libraries are getting downloaded.

Workaround: None.

BWCE- Summary: TIBCO BusinessWorks Container Edition Monitoring does not work
2393 with Oracle Database on Docker.

Workaround: In the Dockerfile, add RUN npm rebuild on line number 29.

BWCE- Summary: In some cases, catch block, reference binding, service binding is
1832 misaligned in the process diagram in Monitoring UI.

Workaround: None.

BWCE- Summary: When Process Monitoring is enabled for an application, in PCF, all
1810 historical records also appear when observing process monitoring data when
an application is deleted and same application is pushed again.

Workaround: None.

BWCE- Summary: Once you enable Process Monitoring, if your application completes
1795 all its jobs, before process monitoring is enabled, then you wont see any
process instances in the Monitoring UI.

Workaround: Add sleep in your process or hit REST/SOAP/HTTP endpoints if

any to see newly created process instances.

BWCE- Summary: You have to edit the logback.xml every time you restart the
1396 application.

Workaround: None.

Palettes
This topic lists the Known Issues related to Palettes.

TIBCO BusinessWorks™ Container Edition Release Notes

55 | Known Issues

HTTP Palette

Key Description

AMBW- Summary: Error occurred on the Send HTTP Request activity with client SR
36777 using HTTP1 Apache HttpComponents and connector SR using HTTP2.0 with
Follow HTTP1 Compliance checked.

Workaround: Use the Jetty client as the client library for implementation under
HTTP client shared resource.

JAVA Palette

Key Description

BWCE- Summary: TIBCO BusinessWorks Container Edition Application throws

1740 java.net.UnknownHostException when deployed in Docker Swarm

Workaround: None.

AMBW- Summary: In Java To XML activity, the Output tab is not populated correctly,
13526 if Java class contains nested object references in different classes.

Workaround: None.

JDBC Palette

Key Description

BWCE-79 Summary: Exceptions are seen when you import a project that contains a
JDBC shared resource.

Workaround: Restart TIBCO Business Studio for BusinessWorks and open

the project in a new workspace. If the issue persists, recreate and reconfigure
the JDBC shared resource.

AMBW- Summary: Unnecessary error logs are displayed in the log file.
36229
Workaround: None

TIBCO BusinessWorks™ Container Edition Release Notes

56 | Known Issues

JDBC Palette

Key Description

AMBW- Summary: The Oracle DataDirect driver does not support cursor datatype.
23464
Workaround: Use native drivers instead of DataDirect drivers.

AMBW- Summary: MySQL Community Edition is not supported for Data Direct drivers
23260
Workaround: Use native drivers instead of DataDirect drivers.

AMBW- Summary: When using DataDirect drivers with a JDBC Shared Resource, that
23193 is linked to a JDBC process, the SQL Builder Wizard does not work correctly.

Workaround: Use native drivers.

AMBW- Summary: The login timeout value is not effective when connecting to a
20130 Windows OS database. The JDBC Query activity fails with the
error,JDBCConnectionNotFoundException at runtime without honoring the
Login Timeout value specified in the JDBC Connection Shared Resource.

Workaround: None

AMBW- Summary: The Set Explicit Nil check box for Objects and Collections in JDBC
14624 Call Procedure activity is disabled.

Workaround: None

AMBW- Summary: When you migrate an TIBCO ActiveMatrix Business works™ 5.x
14547 project containing in-built functions in the JDBC Query activity, an invalid
column name error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix

Business works 5.x project.

AMBW- Summary: Using any in-built function in JDBC Query activity without "Alias"
11667 fails to execute the application and throws an Invalid Column name error at
run time.

Workaround: Use "Alias" to work with any in-built function in JDBC Query
activity.

TIBCO BusinessWorks™ Container Edition Release Notes

57 | Known Issues

JDBC Palette

Key Description

AMBW- Summary: TIBCO Business Studio for BusinessWorks hangs when opening
11624 SQL Builder if the database details on the JDBC shared resource are changed
from PostgreSQL to MySQL after a query has been created using SQL
builder.

Workaround: None

AMBW- Summary: The localized error messages of JDBC connection are not
8855 displayed correctly in TIBCO Business Studio for BusinessWorks.

Workaround: None

JMS Palette

Key Description

AMBW- Summary:The reply to the JMS Request Reply activity is sent through the
42602 JMS Send Message activity, because of which the reply is not received. In
the JMS Request Reply activity, if the correlation ID is not specified, the JMS
Message ID is passed as a selector. The Reply To JMS Message activity
replies for that corresponding ID only.

Workaround: If you use the JMS Send Message activity instead of the Reply
To JMS Message activity for sending the reply to the JMS Request Reply
activity, then you must explicitly map the JMS Correlation ID in the JMS Send
Message activity with the Message ID in the JMS Request Reply activity to
maintain the correct order of the request and reply.

REST and JSON Palette

Key Description

AMBW- Summary: The Parse JSON activity fails to pick up the prefixes defined in the
28795 namespace registry and provides the output with the default namespace
prefixes.

TIBCO BusinessWorks™ Container Edition Release Notes

58 | Known Issues

REST and JSON Palette

Key Description

Workaround: None

XML Palette

Key Description

AMBW- Summary: Use of pipe(union) ('|') character in XSLT throws the following error
31813 at runtime:

com.tibco.bw.palette.xml.runtime.fault.XMLTransformException: Exception
[org.genxdm.xpath.v20.err.ConcreteErrException] occurred during XSLT
transformation. Exception detail
[org.genxdm.xpath.v20.err.ConcreteErrException: [XPTY0004] Either the
expression has a static type that is not appropriate for the context in which it
occurs, or the dynamic type of the value does not match the required type.]

Workaround: Open the XSLT file and manually convert the pipe (union) ('|')
operator to "or" operator and run the project

AMBW- Summary: The Parse XML activity displays blank ErrorCode and
14292 ErrorMessage for activity output data validation error.

Workaround: None.

Policies
This topic lists the Known Issues related to Policies.

Key Description

AMBW- Summary: Marketo plugin container edition breaks with the recent JRE
34607 upgrade.

Workaround: Please refer Marketo plug-in documentation for more

information.

TIBCO BusinessWorks™ Container Edition Release Notes

59 | Known Issues

Key Description

AMBW- Summary: If a SOAP binding is not configured with Transport, the Add New
19513 Policy icon should be disabled, the Policy field should not be displayed in the
tree view, and a NULL pointer exception is generated if you try to add a policy
on the binding.

Workaround: None

Runtime
This topic lists the Known Issues related to Runtime. .

Key Summary

BWCE- Summary: Service Discovery fails with SSL applications on Pivotal Platform.
2571
Workaround: None.

BWCE- Summary: When a module property has inputs with combinations of special
2072 characters like $,% &, the complete input provided is not reflected in the
output. Some part of the input is omitted.

Workaround: None.

TIBCO BusinessWorks™ Container Edition Release Notes

60 | TIBCO Documentation and Support Services

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 TIBCO Product Documentation
website, mainly in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current
than any other documentation included with the product. To access the latest
documentation, visit https://docs.tibco.com.

Product-Specific Documentation
Documentation for TIBCO BusinessWorks™ Container Edition is available on the TIBCO
BusinessWorks™ Container Edition Product Documentation page.
To directly access documentation for this product, double-click the following file:
TIBCO_HOME/release_notes/TIB_bwce_2.6.2_docinfo.html where TIBCO_HOME is the top-level
directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME
is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.
The following documents for this product can be found in the TIBCO Documentation site:
l TIBCO BusinessWorks™ Container Edition Release Notes
l TIBCO BusinessWorks™ Container Edition Application Development
l TIBCO BusinessWorks™ Container Edition Application Monitoring and
Troubleshooting
l TIBCO BusinessWorks™ Container Edition Bindings and Palettes Reference
l TIBCO BusinessWorks™ Container Edition Concepts
l TIBCO BusinessWorks™ Container Edition Error Codes
l TIBCO BusinessWorks™ Container Edition Getting Started
l TIBCO BusinessWorks™ Container Edition Migration
l TIBCO BusinessWorks™ Container Edition Performance Benchmarking and

TIBCO BusinessWorks™ Container Edition Release Notes

61 | TIBCO Documentation and Support Services

Tuning
l TIBCO BusinessWorks™ Container Edition REST Implementation
l TIBCO BusinessWorks™ Container Edition Refactoring Best Practices
l TIBCO BusinessWorks™ Container Edition Samples

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. In addition, users can submit and vote
on feature requests from within the TIBCO Ideas Portal. For a free registration, go to
https://community.tibco.com.

TIBCO BusinessWorks™ Container Edition Release Notes

62 | Legal and Third-Party Notices

Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF
SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE
FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED
TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE
USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE
LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR
CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE
“LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE
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 TIBCO Software Inc.

TIBCO, the TIBCO logo, the TIBCO O logo, TIBCO ActiveMatrix BusinessWorks, TIBCO
ActiveSpaces, TIBCO Business Studio for BusinessWorks, TIBCO Designer, TIBCO Enterprise
Message Service, TIBCO Hawk, TIBCO Rendezvous, and TIBCO Runtime Agent are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other
countries.

Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle
Corporation and/or its affiliates.

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.

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.

This 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 this software version on a specific operating system platform.

TIBCO BusinessWorks™ Container Edition Release Notes

63 | Legal and Third-Party Notices

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. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

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 "READ ME" FILES.

This and other products of TIBCO Software Inc. may be covered by registered patents. Please
refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.

Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

TIBCO BusinessWorks™ Container Edition Release Notes