Description:
TIBCO BusinessConnect 5.3.3 hotfix 6 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

           ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

           available_downloads/ActiveExchange/BusinessConnect/5.3.3/hotfix-06/

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 5.3.3 Hotfix 6 (This Release)

CR: BC-7467
Some HTTPS servers cannot negotiate SSL transports in the TLSv1 mode.
In such case, TIBCO BusinessConnect offers to restrict the frame version of
the connection to trading partners to SSLv3.

When using the property "java.property.bc.https.strictSsl3" to the engine's
TRA configuration file, there are three options:

a) When the property exists with no values, it means that any HTTPS outbound
connection, which specifies SSL for its transport property 'Secure
Transport Mode', will always use SSLv3 regardless whether the server would
be able to promote the frame version to TLSv1.

b) When the property exists and has values in the form of "host1, host2,
host3", then the restricted SSLv3 connection will only apply to transports
where the peer hostname (HTTPS server) is in the list.

c) When the property does not exist, then there is no change in behavior;  
whereas an SSL setting in the transport property 'Secure Transport Mode'
means that the negotiation will result in either an SSLv3 or TLSv1 frame
version,  and TLS means that the frame version will be either TLS or the
connection fails if the peer HTTPS server doesn't support TLSv1
communication.

Example:
java.property.bc.https.strictSsl3=www.partnerhttps.com, 10.1.2.3

This setting restricts the SSL frame version to SSLv3 only for transports
whose peers are www.partnerhttps.com or 10.1.2.3, where the 'Secure
Transport Mode' property is set to SSL. All other transports will behave
without any restrictions on the frame version

CR: BC-7468
When TIBCO BusinessConnect engines connect to various FTP or SSH Servers,
some FTP/SSH Servers do not relinquish the connections and would hold on
to it for longer time, thereby not allowing any files to be get from these
servers for different partners. This fix allows a property governed value
to set the maximum life for polling cycle (set to 60 seconds),beyond which
the connections are destroyed and re-established at the next polling cycle.

Users must add this property and set a different value if the default value
is too small or too large for their implementations. This value is

java.property.bc.ftppoller.cycle.maxLife=&ltvalue in seconds>

CR: BC-7462
When receiving very large payloads from Partners via a slow internet
connection, the HTTP (or HTTPS) connection event source timesOut since
the connection timeOut value at the embedded BusinessWorks engine has
the value defaulted to 60 seconds with no way to override. This fix is
to allow the value to be set via the BusinessConnect DMZ engine .tra file
so that the connections stay longer.

tibco.clientVar.gatewayProperties/transports/public/HTTP/connectionTimeout=
&ltvalue in milliseconds>

TIBCO BusinessConnect 5.3.3 hotfix 6 has been released.

Product: TIBCO BusinessConnect Version: 5.3.3 OS: All --------------------