TIBCO BusinessConnect 6.1.0 hotfix 2 has been released.

TIBCO BusinessConnect 6.1.0 hotfix 2 has been released.

book

Article ID: KB0104575

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Description:
TIBCO BusinessConnect 6.1.0 hotfix 2 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/6.1.0/hotfix-02/

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

Closed Issues in 6.1.0_HF-002 (This Release)

BC-7980

When BusinessConnect engine sent out transactions via HTTPS (AS2_HTTPS, HTTPS)
transport and the X.509 V3 Certificate contained extension attributes like
"postalCode", then the SSL connection could not be established.

This issue is fixed with the limitation that it only works when "ENTRUST" is
chosen as the security provider for outbound HTTPS transport. To set "ENTRUST"
as the security provider for outbound HTTPS transport, follow this link in
TIBCO Administrator:

BusinessConnect > System Settings > Activated Protocol Plug-ins and Properties >
BC.

Set the property "bc.securityVendor.sockets" to "ENTRUST", then click "Save"

BC-7994

Outbound requests can now be sent from private processes to BusinessConnect
engines via JMS transport. Previously, exceptions such as "unexpected end of
content; expected Body" occurred on the BusinessConnect engine side when
receiving such JMS messages.

BC-7996

Previously, when no port number was specified explicitly, outbound requests
could not be sent out via HTTPS transport through an HTTP proxy. This issue has
been fixed. Port 443 is now used as the default port number if no port number is
given explicitly.


================================================================================
Closed Issues in 6.1.0_HF-001

BC-7924

In Log Viewer's Advanced Filters definition, the pre-defined queries don't work for the following cases:
    - The query is defined as "contains" type;
    - The query is defined as "is not like" type;
    
This has been fixed in this hotfix release.

BC-7936

The search in Participants and Business Agreements doesn't work for search string
with wildcards at both the beginning and end, such as "*xyz*".

BC-7953

Previously, the outbound SSHFTP channel is cached for a certain period (which is
configurable) so it can be used for consequent FTP activities to the same SSHFTP
server. This was designed for efficiency. However some customers requested that
the SSHFTP connection be closed immediately after an FTP activity is completed,
which is useful in cases there are restrictions on the number of simultaneous
connections for each FTP user put by the SSHFTP sever.

In this hotfix release a property has been introduced to disable the caching of
the SSHFTP connection. Add the following property to each of the  
&ltBusinessConnect-Interior_Server>.tra files:

java.property.&ltTP_name>.sshftp.cache.disabled=false|true

Here the &ltTP_name> is the name of the trading partner the SSHFTP transport connects
to. The default value of this property is false.

Please also be note that this property has to be applied to each of the
BusinessConnect Interior servers to work effectively.

BC-7955
Previously, the "Socket Timeout (seconds)" property of the HTTP, AS2_HTTP, HTTPS,
and AS2_HTTPS transports didn't behave as expected. Instead of setting the
maximum waiting time before receiving a response from the server, the property
set the maximum waiting time for establishing the connection.

This has been fixed in this hotfix release so that the "Socket Timeout (seconds)"
property sets the maximum waiting time before a response is received.

BC-7958

This issue is related to BC-7785 which was partially fixed in BusinessConect
6.1.0 release. In the fix of BC-7785 of BusinessConnect 6.1.0 release, the
BusinessConnect Gateway Server allows user to restrict cipher suite algorithms
set at the HTTPS Service level; however this only worked for SUN JCE security
provider.

This has been fixed in this hotfix release that it also works for ENTRUST
security provider.


BC-7957

The Apache Tomcat server embedded in BusinessConnect Gateway server has been
upgraded to version 7.0.40 to mitigate security risks.

Issue/Introduction

TIBCO BusinessConnect 6.1.0 hotfix 2 has been released.

Environment

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