Products | Versions |
---|---|
TIBCO BusinessWorks Collaborator | - |
Not Applicable | - |
Description:
TIBCO BusinessWorks(TM) Collaborator (BWC) 5.5.1 HF04 supports TIBCO Runtime Agent(TM) 5.7.1 and TIBCO BusinessWorks(TM) 5.9
Limitation and Restrictions:
===================
1) TIBCO BusinessWorks Collaborator continue to run as a 32 bit application and can be installed on any 32-bit or 64-bit platform. It requires all other software like TRA,BW,Admin,JRE etc needs to be 32-bit as well.
2) For the compatibily of FormBuilder with BWC 5.5.1 HF04/TRA 5.7.1 Please refer to LBN1-CJBXG7 and apply the solutions given in that LBN.
Known Issues:
===========
Known Issues for TIBCO BusinessWorks Collaborator 5.5.1 hotfix04
Defect BWC-405
Summary: TIBCO BusinessWorks Collaborator fails with the error
java.lang.LinkageError: loader constraint violation: when resolving
interface method. This is due to TRA Defect TRA-2372.
Workaround: Remove the TIBCOAdapter_RT_5.4.0.jar file from the TRA 5.7.1 lib
and rebuild the shared archive through Domain Utility. Make sure to
delete the earlier deployment if any and clean up the EAR Download
folder from the deploymentfolder under
<TRA DOMAIN HOME>\<domain name>\EARDownload\<application name>.
Defect BWC-407
Summary: The DataDirect database drivers are no longer bundled in TIBCO
Runtime Agent 5.7.1.
Workaround: Point the database driver explicitly in the classpath of the
tomcat startup script or copy the JDBC folder under old TRA version
to the TRA 5.7.1 and then recreate the shared archive file from
Domain Utility to deploy the application.
Defect BWC-419
Summary: Domain Utility hangs while registering the tomcat engine to the TIBCO
Administrator Domain.
Workaround: Two different versions of TPCL libraries are shown while registering
the Tomcat instance in Domain Utility.
With TRA 5.7.0 - TPCL 5.7.0.1 and TPCL 5.7.0.31
With TRA 5.7.1 - TPCL 5.7.0.1 and TPCL 5.5.0.2
For successful registration, select TPCL 5.7.0.1
However, with other versions Domain Utility hung.
Defect BWC-416
Summary: Tomcat console shows LOG4J warnings during the startup.
Workaround: Manually point to the log4j.properties in the classpath of Tomcat
Startup Script. The location of tomcat startup script is under
<TRA DOMAIN HOME>\<domain name>\Tomcat\bin\startup.bat.
This hot fix can be downloaded from the TIBCO Product Support ftp server, ftp://support-ftp.tibco.com/, using your username and password for the TIBCO Support Web. Once logged on you can find the hot fix under:
ftp://support-ftp.tibco.com/ActiveEnterprise/BusinessWorks-WorkFlow/5.5.1/hotfix-04/
Please contact TIBCO Support if you have any problems finding or downloading this hot fix..