Description:
This hotfix doesn't need any TRA hotfix. The patch can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveEnterprise/BusinessWorks/BW/5.4.2/hotfix-05/  to download the appropriate hotfix for your OS/platform.

Closed Issues in 5.4.2_hotfix5 (This Release)





  1-8V4OF3

  For a JDBC XA Connection to Oracle RAC using the TIBCO driver, the

  Database URL did not accept the attributes, ServiceName, and

  AlternateServers. This has been fixed. These attributes can be

  specified in the Database URL using the following syntax -

  jdbc:tibcosoftwareinc:oracle://&lthost1>:&ltport1>ServiceName=

  &ltdb_instancename>AlternateServers=(&lthost2>:&ltport2>,&lthost3>:&ltport3>,

  ...,&lthostN>:&ltportN>)



  1-8WXELX

  As a result of the fix for 1-8EGZZ0 in TIBCO BusinessWorks 5.4.2,

  the "dataEncipherment" KeyUsage flag was not required and user

  certificates had to have only "digitalSignature" and

  "keyEncipherment" KeyUsage attributes. This caused the third party

  applications to fail with a "PKA Decrypt failure" error when

  confidentiality policy was used. This has been fixed.

  TIBCO BusinessWorks now requires the user certificate to have

  "dataEncipherment" KeyUsage flag in addition to "digitalSignature"

  and "keyEncipherment" KeyUsage attributes.



  1-8WXN2D

  The Parse Data Activity can only parse a maximum of two optional

  fields at the end of each line that has a "Fixed" Format. This has

  been fixed.



  1-8VT2JO

  On Linux, when a process having a series of JDBC Query activities to

  Sybase is run with multiple parallel jobs, some jobs get completed

  only when all the other jobs are completed. This has been fixed.



  To fix this, set the bw.plugin.jdbc.checkClosed property to false.

  This property is set to true by default.



  1-8YN00B

  The SOAPRequestReply activity did not support type substitution in

  the detail element of the SOAP Fault message. This has been fixed.