TIBCO BusinessWorks 6.2.0 Hotfix-02 is available.
Article ID: KB0102997
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
You can download this HotFix from the TIBCO Product Support ftp server, mft.tibco.com. You will need to provide your TSC (TIBCO Support Central) credentials. Your username is your email address to access the server.
Please note you should use an FTP or SFTP client or command-line FTP. TIBCO employees must use a secure protocol.
Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser: https://mft.tibco.com
FTP: port 21
SFTP: port 22
Once you have successfully logged into the server, go to /AvailableDownloads/BusinessWorks/6.2.0/hotfix-02 to download the fix.
================================================================================
Closed Issues in 6.2.0_HF-002 (This Release)
AMBW-17479
For activities that throw Data Validation Exception at runtime, the FaultDetails
generated in the CatchAll block was incorrect.
AMBW-17462
The JDBC activities in a transaction group failed with a NullPointerException.
This has been fixed.
AMBW-17433
The JMS Application Property displayed "Unresolved Element" in the Input tab if
the Application Property was defined in a shared module and the activity used
XML Text as Message Type.
AMBW-17155
The schema payload on the Input tab of a JMS activity failed to load and a
message "Unresolved reference in schema" was received if the Application
Properties Type on the Advanced tab was selected. Previously, we advised
users to close and re-open the project after such configuration for the
activity signature to display properly. This is no longer required with
this fix.
AMBW-17414
Incorrect reporting of cyclic type errors by the XML Schema Parser has been
fixed.
AMBW-17374
When the Java Invoke activity was run in a multi-threaded mode under load test,
an intermittent error was observed. This has been fixed.
AMBW-17390
An error "Failed to set CLIENTID" was thrown if the JMS Connection used by the
deployed application was defined in a shared module. This has been fixed.
AMBW-16912
The custom XPath function failed with an error if the implementation contained
a main method. This has been fixed.
AMBW-17427
The [Copy Of] option could not be used to map the output of the Mapper activity
to invoke a web service. This has been fixed.
AMBW-17074
Changing the default value of a module property of type String from a predefined
string to an empty string resulted in validation errors. This has been fixed.
AMBW-17370
A NullPointerException was thrown by the Inspector activity when the Inspect
field is set to ALL.
AMBW-17156
An error was thrown when the SOAP response received from a SOAP service
contained an incorrect namespace declaration. This has been fixed.
AMBW-17046
ActiveMatrix BusinessWorks 6.x design-time validation / build took a significant
amount of time for complex BW6 applications. For example, applications that
involved multiple modules and deeper inter-module dependencies. Optimization
has been introduced to reduce the validation and build time.
PER-2055
Basic and Username Token Credential Mapping are now supported. This fix
requires the use of ActiveMatrix Policy Director 2.0 with
ActiveMatrix BusinessWorks 6.2. For example, this enables BW6 users to invoke
ActiveMatrix BPM web services.
================================================================================
You can download this HotFix from the TIBCO Product Support ftp server, mft.tibco.com. You will need to provide your TSC (TIBCO Support Central) credentials. Your username is your email address to access the server.
Please note you should use an FTP or SFTP client or command-line FTP. TIBCO employees must use a secure protocol.
Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser: https://mft.tibco.com
FTP: port 21
SFTP: port 22
Once you have successfully logged into the server, go to /AvailableDownloads/BusinessWorks/6.2.0/hotfix-02 to download the fix.
================================================================================
Closed Issues in 6.2.0_HF-002 (This Release)
AMBW-17479
For activities that throw Data Validation Exception at runtime, the FaultDetails
generated in the CatchAll block was incorrect.
AMBW-17462
The JDBC activities in a transaction group failed with a NullPointerException.
This has been fixed.
AMBW-17433
The JMS Application Property displayed "Unresolved Element" in the Input tab if
the Application Property was defined in a shared module and the activity used
XML Text as Message Type.
AMBW-17155
The schema payload on the Input tab of a JMS activity failed to load and a
message "Unresolved reference in schema" was received if the Application
Properties Type on the Advanced tab was selected. Previously, we advised
users to close and re-open the project after such configuration for the
activity signature to display properly. This is no longer required with
this fix.
AMBW-17414
Incorrect reporting of cyclic type errors by the XML Schema Parser has been
fixed.
AMBW-17374
When the Java Invoke activity was run in a multi-threaded mode under load test,
an intermittent error was observed. This has been fixed.
AMBW-17390
An error "Failed to set CLIENTID" was thrown if the JMS Connection used by the
deployed application was defined in a shared module. This has been fixed.
AMBW-16912
The custom XPath function failed with an error if the implementation contained
a main method. This has been fixed.
AMBW-17427
The [Copy Of] option could not be used to map the output of the Mapper activity
to invoke a web service. This has been fixed.
AMBW-17074
Changing the default value of a module property of type String from a predefined
string to an empty string resulted in validation errors. This has been fixed.
AMBW-17370
A NullPointerException was thrown by the Inspector activity when the Inspect
field is set to ALL.
AMBW-17156
An error was thrown when the SOAP response received from a SOAP service
contained an incorrect namespace declaration. This has been fixed.
AMBW-17046
ActiveMatrix BusinessWorks 6.x design-time validation / build took a significant
amount of time for complex BW6 applications. For example, applications that
involved multiple modules and deeper inter-module dependencies. Optimization
has been introduced to reduce the validation and build time.
PER-2055
Basic and Username Token Credential Mapping are now supported. This fix
requires the use of ActiveMatrix Policy Director 2.0 with
ActiveMatrix BusinessWorks 6.2. For example, this enables BW6 users to invoke
ActiveMatrix BPM web services.
================================================================================
Notable Tickets
AMBW-17154 - Cross module schema import fails to resolve reference at
Runtime when schema import contains schemalocation attribute with
relative path reference
* Analysis of this issue shows that import declaration
has schemalocation attribute for schema import across modules, which
is not supported.
Recommended user action is to remove the schemalocation
attribute. BW Engineering is looking into ways to relax the problem
reporting rules in the following ways in future releases:
A. schemalocation attribute for cross module schema references
will be ignored and solely rely on namespace for schema resolution
Note: schemalocation attribute is supported for schema references
within the same module. The primary use case for this is to
support multiple schema having the same namespace in the same
module. This is already supported.
Issue/Introduction
TIBCO BusinessWorks 6.2.0 Hotfix-02 is available.
Environment
TIBCO BusinessWorks 6.2.0 Hotfix-02
Additional Information
TIB_BW_6.2.0_HF-002_readme.txt
Attachments
Feedback
Yes
No
Powered by
