TIBCO ActiveMatrix BusinessWorks 6.5.0 Hotfix-01 is available
Article ID: KB0102046
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | 6.5.0 |
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.0/hotfix-01.
================================================================================
Closed Issues in 6.5.0_HF-001 (This Release)
AMBW-33332
JDBC activities could not connect to a secondary server when a DataDirect driver
was used and the connection URL had hyphen (-) character in the host name.
AMBW-33297
The LDAP basic authentication policy did not work for Microsoft AD Server
at run time when the Admin user credentials check box was selected.
AMBW-33281
TIBCO Business Studio displayed validation errors when generating concrete WSDL
at design time and run time.
AMBW-33275
Main process was delayed as sub-processes could not be spawned.
AMBW-33270
The schema elements in the run time concrete WSDL were duplicated
when the concrete WSDL was fetched from two deployed applications sharing
a common schema from a shared module.
AMBW-33262
SOAP requests failed when mapping optional nil element to optional
empty element.
AMBW-33240
Duplicate messages were not detected when the job completed its execution
due to the timeout for duplicate messages in the Checkpoint activity.
By default, it was 0 minutes and was non-configurable.
Now, you can configure the duplicate key timeout for each application.
You can also configure the periodic interval at which expired dupKeys
must be purged from the database.
Two new properties bw.application.checkpoint.dupKeyTimeout and
bw.engine.checkpoint.expired.dupkey.purge.interval are defined in the
AppSpace config.ini and AppNode config.ini.
bw.application.checkpoint.dupKeyTimeout is an optional property and specifies
the amount of time in minutes to keep duplicate keys stored after
the chekpointed job finished executing.
By default, the timeout is 0 minutes and indicates that
the duplicate key is deleted as soon as the checkpointed job completes execution.
When the property bw.application.checkpoint.retainFaultedJob is set to true for
an application, the job is not automatically removed after a failure.
So the duplicateKey remains as long as the job remains.
Such a job can be restarted or purged later.
The TIBCO ActiveMatrix BusinessWorks application name must be included
as part of this property. However, the application version and
component name are optional. If the component name is not specified, the value
is applied to all components in the TIBCO ActiveMatrix BusinessWorks application.
bw.application.checkpoint.dupKeyTimeout.<UsersBWApplicationName>
[.<UsersBWApplicationVersion>][.<UsersBWComponentName>]=0
bw.engine.checkpoint.expired.dupkey.purge.interval specifies the default interval
for the background thread to poll for expired duplicate keys.
The numerical value can be preceded either by "P" or "D".
For example, a value "P60" indicates the background thread polls after every
60 minutes whereas a value "D2" indicates the background thread polls after
every two days.
The default value is "P30".
AMBW-33216
An error was displayed when validating any WSDL.
AMBW-33208
AppNode logs did not roll over.
For previously created AppNodes, replace the existing AppNode's logback.xml
with {BW.HOME}/config/logback.xml.
Newly created AppNodes use the new logback.xml.
AMBW-33179
The Mapper activity could not evaluate When condition correctly.
You can set the property bw.xml.typedmodel.oldgetvalue to true in
TIBCO Business Studio for BusinessWorks, the config.ini file at AppNode level,
or AppSpace level.
AMBW-33160
After migration, an error was generated at run time when the JMS Send Message
and JMS Receive Message activities had inline schemas.
AMBW-33115
After migration, process migrated as an empty process.
It happened due to a Null Pointer Exception from Throw activity.
AMBW-33110
After migration, when a process had JMS Request Reply (JMS Topic Requester)
whose input and output were configured with inline XML schema, the output
inline schema replaced the input inline schema for that activity.
AMBW-33068
The application failed to start when the application had a asterisk (*)
in the XPATH and the warning message Runtime binding is not synchronized
was fixed with the Quick Fix option.
AMBW-33064
The JMS Receive Message activity generated an exception multiple times and
failed to reconnect to the IBM MQ server when there was a network outage.
AMBW-33056
A JDBC Query activity returned the value as true instead of empty
when mapping the output with nillable as true and Use Nil option was selected.
AMBW-33048
A new check box Start Job on Input Exception is added in the
REST Service Binding.
Select the check box to start the job when there is a wrong or erroneous input.
AMBW-33045
A new option JSON With Root is added in the JSON Definition field on
the Request tab and the Response tab of the REST Service Binding.
Select the option to include the root element in the input JSON string.
AMBW-33041
Excess threads were created when there were maximum number of connections
to the database. The threads created by JDBC activities went into sleep state
for few seconds rather than going into the standing or the waiting state.
AMBW-33027
After migration, the Activity input configuration error was generated on
the Input Tab of an End activity inside a Catch block.
AMBW-33021
After migration, when a process had JMS Request Reply (JMS Queue Requester)
activity whose input and output was configured with inline XML schema,
the output inline schema replaced the input inline schema for that activity.
AMBW-33008
SOAP requests were authenticated intermittently when the password in a request
was empty.
AMBW-32996
The NVARCHAR data type was converted to the VARCHAR data type
when the sendStringParametersAsUnicode property was set to false
in the SQL Server URL.
AMBW-32834
Support is added in the JDBC Call Procedure activity for PostgreSQL
function to return single resultset using ref cursor.
AMBW-32743
The NoHttpResponseException was intermittently displayed when invoking
a REST service.
To ensure correct request processing, set the Request Entity Processing field
value to Buffered on the Advanced tab of the Invoke Rest API activity.
AMBW-32677
The Concrete WSDL file could not be retrieved at runtime for a SOAP service
deployed through a web browser by using the URL.
AMBW-32583
A new process was created after renaming an existing process.
AMBW-32525
TIBCO Business Studio displayed an error for anyElement and anyType element
mapping when using explicit XPath expression.
AMBW-32457
A new check box Use Nil is added on the Advanced tab of
the JDBC Call Procedure activity.
Select the Use Nil check box to display columns with null values or empty
columns from the database tables.
AMBW-32445
The kerberos debug logs are not visible.
To view kerberos debug logs in TIBCO Business Studio, set the property
sun.security.krb5.debug=true.
AMBW-31877
After migration, XPath was missing from a Reply activity.
AMBW-31862
After migration, few exceptions were listed in the MigrationReport.log
that broke some processes.
AMBW-31700
A new check box Use Nil is added on the Advanced tab of
the SQL Direct activity.
Select the check box to display columns with null values or empty columns
from the database tables.
AMBW-29551
A data type of module properties could not be selected from drop-down list
on Redhat Enterprise Linux and CentOS.
AMBW-29546
An activity name could not be completely removed when renaming an activity in
the Properties tab with the backspace key.
AMBW-29504
The module property name could not be edited when clicking it too fast.
AMBW-29289
The JMS Receive Message activity failed to reconnect when a
TIBCO Enterprise Message Server (EMS) failover occurred.
This happened only when EMS was configured with FTgroup or group mode
with governance flag enabled.
AMBW-26463
Now warning is shown instead of validation errors for XPath with wildcard
characters.
AMBW-24090
Support is added for replace() XPath function.
AMBW-23422
The type or value of a promoted application property was not updated
when changing the type or value of the module property related to
the application property.
================================================================================
================================================================================
Closed Issues in 6.5.0_HF-001 (This Release)
AMBW-33332
JDBC activities could not connect to a secondary server when a DataDirect driver
was used and the connection URL had hyphen (-) character in the host name.
AMBW-33297
The LDAP basic authentication policy did not work for Microsoft AD Server
at run time when the Admin user credentials check box was selected.
AMBW-33281
TIBCO Business Studio displayed validation errors when generating concrete WSDL
at design time and run time.
AMBW-33275
Main process was delayed as sub-processes could not be spawned.
AMBW-33270
The schema elements in the run time concrete WSDL were duplicated
when the concrete WSDL was fetched from two deployed applications sharing
a common schema from a shared module.
AMBW-33262
SOAP requests failed when mapping optional nil element to optional
empty element.
AMBW-33240
Duplicate messages were not detected when the job completed its execution
due to the timeout for duplicate messages in the Checkpoint activity.
By default, it was 0 minutes and was non-configurable.
Now, you can configure the duplicate key timeout for each application.
You can also configure the periodic interval at which expired dupKeys
must be purged from the database.
Two new properties bw.application.checkpoint.dupKeyTimeout and
bw.engine.checkpoint.expired.dupkey.purge.interval are defined in the
AppSpace config.ini and AppNode config.ini.
bw.application.checkpoint.dupKeyTimeout is an optional property and specifies
the amount of time in minutes to keep duplicate keys stored after
the chekpointed job finished executing.
By default, the timeout is 0 minutes and indicates that
the duplicate key is deleted as soon as the checkpointed job completes execution.
When the property bw.application.checkpoint.retainFaultedJob is set to true for
an application, the job is not automatically removed after a failure.
So the duplicateKey remains as long as the job remains.
Such a job can be restarted or purged later.
The TIBCO ActiveMatrix BusinessWorks application name must be included
as part of this property. However, the application version and
component name are optional. If the component name is not specified, the value
is applied to all components in the TIBCO ActiveMatrix BusinessWorks application.
bw.application.checkpoint.dupKeyTimeout.<UsersBWApplicationName>
[.<UsersBWApplicationVersion>][.<UsersBWComponentName>]=0
bw.engine.checkpoint.expired.dupkey.purge.interval specifies the default interval
for the background thread to poll for expired duplicate keys.
The numerical value can be preceded either by "P" or "D".
For example, a value "P60" indicates the background thread polls after every
60 minutes whereas a value "D2" indicates the background thread polls after
every two days.
The default value is "P30".
AMBW-33216
An error was displayed when validating any WSDL.
AMBW-33208
AppNode logs did not roll over.
For previously created AppNodes, replace the existing AppNode's logback.xml
with {BW.HOME}/config/logback.xml.
Newly created AppNodes use the new logback.xml.
AMBW-33179
The Mapper activity could not evaluate When condition correctly.
You can set the property bw.xml.typedmodel.oldgetvalue to true in
TIBCO Business Studio for BusinessWorks, the config.ini file at AppNode level,
or AppSpace level.
AMBW-33160
After migration, an error was generated at run time when the JMS Send Message
and JMS Receive Message activities had inline schemas.
AMBW-33115
After migration, process migrated as an empty process.
It happened due to a Null Pointer Exception from Throw activity.
AMBW-33110
After migration, when a process had JMS Request Reply (JMS Topic Requester)
whose input and output were configured with inline XML schema, the output
inline schema replaced the input inline schema for that activity.
AMBW-33068
The application failed to start when the application had a asterisk (*)
in the XPATH and the warning message Runtime binding is not synchronized
was fixed with the Quick Fix option.
AMBW-33064
The JMS Receive Message activity generated an exception multiple times and
failed to reconnect to the IBM MQ server when there was a network outage.
AMBW-33056
A JDBC Query activity returned the value as true instead of empty
when mapping the output with nillable as true and Use Nil option was selected.
AMBW-33048
A new check box Start Job on Input Exception is added in the
REST Service Binding.
Select the check box to start the job when there is a wrong or erroneous input.
AMBW-33045
A new option JSON With Root is added in the JSON Definition field on
the Request tab and the Response tab of the REST Service Binding.
Select the option to include the root element in the input JSON string.
AMBW-33041
Excess threads were created when there were maximum number of connections
to the database. The threads created by JDBC activities went into sleep state
for few seconds rather than going into the standing or the waiting state.
AMBW-33027
After migration, the Activity input configuration error was generated on
the Input Tab of an End activity inside a Catch block.
AMBW-33021
After migration, when a process had JMS Request Reply (JMS Queue Requester)
activity whose input and output was configured with inline XML schema,
the output inline schema replaced the input inline schema for that activity.
AMBW-33008
SOAP requests were authenticated intermittently when the password in a request
was empty.
AMBW-32996
The NVARCHAR data type was converted to the VARCHAR data type
when the sendStringParametersAsUnicode property was set to false
in the SQL Server URL.
AMBW-32834
Support is added in the JDBC Call Procedure activity for PostgreSQL
function to return single resultset using ref cursor.
AMBW-32743
The NoHttpResponseException was intermittently displayed when invoking
a REST service.
To ensure correct request processing, set the Request Entity Processing field
value to Buffered on the Advanced tab of the Invoke Rest API activity.
AMBW-32677
The Concrete WSDL file could not be retrieved at runtime for a SOAP service
deployed through a web browser by using the URL.
AMBW-32583
A new process was created after renaming an existing process.
AMBW-32525
TIBCO Business Studio displayed an error for anyElement and anyType element
mapping when using explicit XPath expression.
AMBW-32457
A new check box Use Nil is added on the Advanced tab of
the JDBC Call Procedure activity.
Select the Use Nil check box to display columns with null values or empty
columns from the database tables.
AMBW-32445
The kerberos debug logs are not visible.
To view kerberos debug logs in TIBCO Business Studio, set the property
sun.security.krb5.debug=true.
AMBW-31877
After migration, XPath was missing from a Reply activity.
AMBW-31862
After migration, few exceptions were listed in the MigrationReport.log
that broke some processes.
AMBW-31700
A new check box Use Nil is added on the Advanced tab of
the SQL Direct activity.
Select the check box to display columns with null values or empty columns
from the database tables.
AMBW-29551
A data type of module properties could not be selected from drop-down list
on Redhat Enterprise Linux and CentOS.
AMBW-29546
An activity name could not be completely removed when renaming an activity in
the Properties tab with the backspace key.
AMBW-29504
The module property name could not be edited when clicking it too fast.
AMBW-29289
The JMS Receive Message activity failed to reconnect when a
TIBCO Enterprise Message Server (EMS) failover occurred.
This happened only when EMS was configured with FTgroup or group mode
with governance flag enabled.
AMBW-26463
Now warning is shown instead of validation errors for XPath with wildcard
characters.
AMBW-24090
Support is added for replace() XPath function.
AMBW-23422
The type or value of a promoted application property was not updated
when changing the type or value of the module property related to
the application property.
================================================================================
Issue/Introduction
TIBCO ActiveMatrix BusinessWorks 6.5.0 Hotfix-01 is available
Resolution
You can also download the hotfix using the below link:
https://support.tibco.com/s/hotfixes?id=a011a00000JKgK8AAL
https://support.tibco.com/s/hotfixes?id=a011a00000JKgK8AAL
Attachments
Feedback
Yes
No
Powered by
