book
Article ID: KB0101841
calendar_today
Updated On:
Description
You can download this HotFix from TIBCO Support Portal (https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can the download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to the AvailableDownloads/BusinessWorks/6.5.1/hotfix-01.
================================================================================
Closed Issues in 6.5.1_HF-001 (This Release)
AMBW-35749
At run time, when a condition was matched, TIBCO ActiveMatrix BusinessWorks
wrongly evaluated the success with no matching condition as Success.
AMBW-35738
The REST APIs of BWAgent failed to configure SSL.
AMBW-35582
OpenTracing now displays name of the process for starter activities using the
ProcessName tag.
AMBW-35580
OpenTracing now supports SOAP reference bindings. Pre-defined tags for SOAP
reference binding are visible in the Invoke activity whereas SOAP service
binding related tags are visible in the Receive activity. Additional headers
to propagate SpanContext are added to the SOAP message when OpenTracing is
enabled.
AMBW-35577
Pre-defined tags for REST reference binding are now visible in the Invoke
activity whereas REST service binding related tags are visible in the Receive
activity.
AMBW-35563
Ability to create complex value by combining two module properties
You can combine two module properties in the following ways:
1. Two properties in the same module-
prop1 = C:\
prop2 = applications
prop3 = %%prop1%%%%prop2%%
The prop3 evaluates to C:\applications at run time.
2. One property in the shared module and one in the application module -
prop1 = C:\
prop2 = applications (defined in shared module)
prop3 = %%prop1%%%%//<name of the shared module>//prop2%%
The prop3 evaluates to C:\applications at run time.
You can use the complex values created by using partial value substitution
in shared resources as well.
AMBW-35399
Ability to export application profile properties.
You can export application properties in a .properties file for Tibco Cloud
Deployment Target.
Double click application properties.
In the Properties view, select the profile, and click Export Profile button.
The Export Profile wizard opens. If the project has only one Deployment Target
selected as Tibco Cloud, then by default TIBCO Business Studio for BusinessWorks
does not allow tokenization of properties.
Select properties to be exported. Select the check box Export as properties file
and browse the location to export the properties file.
Properties are available in the .properties file in key-value pair form.
This functionality supports properties of type boolean, string, integer, long,
and password. In case of password type properties, if no password is given,
then the output .properties file contains value as PASSWORD.
Otherwise, it adds value as an encrypted password.
If you have already selected Deployment Target as Container, and you add
or configure Deployment Target as Tibco Cloud, property values are exported as
default values.
In case of integers and long, default value is 0. For boolean it is false,
for string, it is same as key. For passwords, it is a string PASSWORD.
AMBW-35396
A new button Tokenize the property is added in the Properties view for
application properties.
After tokenization, the property value is set in the format of #<property_name>#.
Once the user tokenizes a property, the original default value for the property
is lost.
The Tokenize the property button is available only for applications with
the Deployment Target set as Container or Tibco Cloud.
When you open Export Profile wizard, tokenized values are already selected.
AMBW-35372
TIBCO ActiveMatrix BusinessWorks generated a null pointer exception when an
AppNode was shut down.
AMBW-35369
Ability to make XSLT validation optional.
A new check box Disable implicit-if existence checking is added in the
Preferences > Mapper dialog box.
Select the check box and clean the project to remove
<xsl:if test="$Mapper/Element1"> elements from Optional to Optional mapping.
AMBW-35284
Application startup time has been improved while deserializing process.
AMBW-35275
The copy-of on root element failed with incorrect namespace.
AMBW-35244
The Repeat on Error group executed even when a success condition occurred.
AMBW-35207
After EMS fail over, before restarting the failed EMS server,the bwagent could
not start and displayed Duplicate member error.
AMBW-35191
TIBCO ActiveMatrix BusinessWorks generated a null pointer exception when an
AppNode was shut down.
AMBW-35173
When an application had nested Repeat on Error groups, the inner group executed
continuously in a loop and never exited, even though there was no error.
AMBW-35169
OpenTracing displayed incorrect trace structure when activity generated exceptions.
AMBW-35167
A warning was displayed in a debug mode when unbounded string element had
multiple values set.
AMBW-35127
The bwdesign utility displayed Null Pointer error intermittently when exporting
an EAR file.
AMBW-35126
The definition of the Namespace prefix was lost when using the render-xml()
XPath function.
AMBW-35123
Namespace declaration was missing when type substitution on input of JMS
Send Message activity was used.
AMBW-35101
The JMS message deserialization failed when both the JMS sender and the JMS
receiver used the same schema, and when you set the field value for int, decimal,
double and float to NULL.
A new Default Map Type Value check box is added for Get JMS Queue Message, JMS
Receive Message, JMS Request Reply, and Wait For JMS Request activities on
the General tab. Select the check box to set the default value of the data type.
AMBW-35064
When the EMS server was restarted, the machine status and the bwagent status was
changed to unreachable in Admin UI.
AMBW-35039
Promoting a module property to an application property took an incorrect value
at run time when a module property had new line character (\n) in the value.
AMBW-34962
A Stack Overflow error was encountered during migration for activities when
the input schema elements were referenced recursively and were used for mapping.
AMBW-34647
You can add custom tags for OpenTracing.
A new tab Tags is added for all activities.
Additionally, each activity has a few more pre-defined tags except for
Rendezvous palette activities supported for OpenTracing.
The tags help you understand more details about the job.
AMBW-34626
On Unused Resources view, now you can:
- See the total number of unused resources. This includes:
Processes
Job Shared Variables
Module Shared Variables
Policy
Shared Resource.
The Include Application Modules check box is now removed from the
Unused Resources view. Implicitly, application modules are included during
unused resources calculation.
- Delete unused resources
To delete unused resources by type, select the resource > right click > Delete
To delete all unused resources in one go:
select all resources > right click > Delete
However, you need to repeat this process more than once to remove all unused
resources.
If you add, remove, or re-factor unused resources in the application,
you need to find unused resources again.
Use refresh button in the Unused Resources view to get the updated unused
resources.
If you remove or close any project from the Project Explorer view,
the Unused Resources view is cleared.
- Exclude unused resources when generating .EAR.
In TIBCO Business Studio for BusinessWorks, Preview of Unused Resources is
displayed during .EAR generation in the Create Application Archive wizard.
In bwdesign utility, use the parameter -removeunused in the export command.
If you select BusinessWorks > Deployment > Exclude unused resources from
packaging check box in the Preferences dialog box, then the preview of Unused
Resources is not visible in the Create Application Archive wizard.
Also Unused Resources are exported during .EAR generation.
AMBW-34515
TIBCO Business Studio for BusinessWorks became unresponsive during startup for
applications with cyclic dependencies between the schemas used in WSDL's, and
generated out of memory error.
AMBW-30723
When the same coercion was applied on two or more sibling elements, all the
elements were incorrectly renamed to the name of the last sibling.
================================================================================
Issue/Introduction
TIBCO ActiveMatrix BusinessWorks 6.5.1 Hotfix-01 is available
Resolution
You can also download the hotfix using the below link:
https://support.tibco.com/s/hotfixes?id=a012L00000L4nzwQAB