TIBCO BusinessConnect 6.1.0 hotfix 8 has been released.
Article ID: KB0102785
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Description:
TIBCO BusinessConnect 6.1.0 hotfix 8 has been released.
You can download this Hot Fix from the TIBCO Product Support server using your TIBCO Support Central (TSC) username (email address) and password, at
mft.tibco.com
mft.tibco.com supports FTP, HTTPS, and SFTP.
Once you have successfully logged into the server, you will find the hotfix packages under
Available_Downloads/BusinessConnect/6.1.0/hotfix-08/
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-008 (This Release)
BC-8509
TIBCO Administrator took a long time to show pages for Business Agreements,
Participants, and Users if a large number these items were in TIBCO BusinessConnect.
The java.property.bc.repo.fetch.limit property is added in the
tibcoadmin_<domainName>.tra properties file to customize the maximum entries
per view. You can set a value to this property to control how many rows of data
are displayed from Business Agreements, Participants, or Users database. The
value of this property must be a positive integer and its default value is 500.
Note: If the value of this property is set too large, TIBCO BusinessConnect
might take a long time to show the view.
BC-8505
After restarting TIBCO BusinessConnect Interior Server, which was recovered from
an unexpected crash, the interior server did not start up from the checkpoint
and the IOException exception was thrown.
BC-8502
AS2 MDN response from BusinessConnect did not contain the Content-Length header,
which caused problems for senders who expected this header in a synchronous HTTP
request response.
BC-8501
When TIBCO BusinessConnect was running in a high volume scenario with Oracle
database, the "ORA-00001: unique constraint violated" error message was reported.
BC-8467
If a large number of files in the SSHFTP server directory, TIBCO BusinessConnect
hung and did not get files from certain SSHFTP server to TIBCO BusinessConnect.
BC-8461
When certain errors occurred on the SSHFTP server, TIBCO BusinessConnect did
not close SSHFTP connections properly.
================================================================================
Closed Issues in 6.1.0_HF-007
BC-8462
When multiple messages were staged in "Inbox" with the same transaction ID,
under certain circumstances they cannot be downloaded by SSH FTP client
through TIBCO BusinessConnect Plug-in for SSH Server.
BC-8455
For inbound HTTP/S connections, the SSL security version could fall back to
SSLv3 after the client-server negotiation, which was vulnerable to POODLE
attach.
To restrict the SSL security version from falling back to SSLv3, the
java.property.bc.security.restrictVersion property is added for the
TIBCO BusinessConnnect Gateway gsengine.tra file. You have to manually
add this property in the gsengine.tra file of all Gateway engines,
and two values are available as options:
- java.property.bc.security.restrictVersion=TLSv1
TLS1.0 is allowed as the lowest security version
- java.property.bc.security.restrictVersion=SSLv3
SSLv3 is allowed as the lowest security version
Note: If the value of this property is not set, or this property is not
added into the gsengine.tra file, SSLv3 is allowed as the lowest security
version.
BC-8435
When importing configurations into a new TIBCO BusinessConnect environment,
the contact information of existing participants were duplicated rather
than merged.
BC-8396
If you imported configurations into a new TIBCO BusinessConnect environment
for multiple times, the importing process could be very slow and the "GC
overhead limit exceeded" error message could be displayed due to the
duplication of the participant contact information in the target environment.
================================================================================
Closed Issues in 6.1.0_HF-006
BC-8398
When BusinessConnect generated EDI Acknowledgement such as TA1 which sit in Inbox
waiting to be downloaded by the trading partner through SFTP transport, the
trading partner failed to download it if BusinessEvent integration was enabled so
all the advisories were to be sent to BusinessEvent channels.
BC-8395
When multiple transactions with the same transaction ID were staged in Inbox waiting
to be downloaded by a trading partner, the trading partner was not able to download
these documents via FTPS, SFTP or TIBCO PartnerExpress.
BC-8387
BusinessConnect system property "bc.http.client.expect.header" which, when set to
"false", was used to exclude the "Expect: 100-conginue" HTTP header in outbound
HTTP requests when communicating to a server that only supports HTTP 1.0, didn't
take effect for outgoing AS2 asynchronous MDN receipt; the header still existed
in the MDN receipt which caused the MDN receiver side (the HTTP server)
mal-functioned.
(Set this property in TIBCO Administrator: BusinessConnect > System Settings >
Activated Protocol Plug-ins and Properties > BC.)
BC-8380
When using BusinessConnect as SSHFTP client to connect to an SSHFTP server on some
specific operating systems such as Microsoft Windows 2008 Server, BusinessConnect
failed to connect to the SSHFTP server and the following error occurred:
"SSHFTP An I/O error detected: SshMgr: Ssh Transport creation failed due to I/O
errors: Invalid argument: no further information".
This issue was fixed. Customer need to add this property in BusinessConnect engines'
.tra file to resolve this issue:
java.property.<trading partner name>.sshftp.tcpnodelay=false
BC-8379
BusinessConnect Gateway Server stopped responding to HTTP requests sent from trading
partners after running a long period of time due to memory leak.
BC-8368
When selecting password as the authentication mode to connect to an SSHFTP server
that works in keyboard-interactive mode, an "Authentication methods have been
exhausted: password" error occurred.
An extra option "Keyboard-Interaction" is added to the Authentication Mode
in the configuration of SSHFTP transport; the issue is fixed if you use this mode
rather than the "Password" mode to connect to the SSHFTP server.
================================================================================
Closed Issues in 6.1.0_HF-005
BC-8340
The search function did not work properly under Business Agreements.
BC-8337
If migrating from TIBCO BusinessConnect EDI Protocol powered by Instream
version 6.4.0 to 6.6.0, the Validation Guideline was not migrated successfully
via a .csx file when selecting the Override Operation Settings check box under
Business Agreement.
BC-8335
Inbound transactions were processed successfully via HTTPSCA transport when an
invalid CA certificate was configured.
================================================================================
Closed Issues in 6.1.0_HF-004
BC-8085
When configuring JDBC connections, the user name and password properties
were stored as non-encrypted in TIBCO Administrator database.
BC-8078
When BusinessConnect failed to send a large file using the SSHFTP transport,
other transmissions using the SSHFTP transport were also affected occasionally
and even small files failed to be sent.
BC-8064
If configurations of two participants were exported separately from TIBCO
BusinessConnect, and then imported back into a new TIBCO BusinessConnect
environment, the configuration of the second imported participant overrode part of
the first imported participant, particularly the business agreement.
BC-8061
When uninstalling TIBCO BusinessConnect 6.1.0 Hotfix 3, the uninstallation failed
because a dependency error occurred.
BC-8059
When BusinessConnect was connected to several SSHFTP servers and one of the
connections shut down, connections to other SSHFTP servers also shut down
unexpectedly.
BC-8051
Transmission of large files using the SSHFTP transport failed occasionally.
BC-7941
Only audit logs stored in the default Audit Log database could be viewed
in TIBCO BusinessConnect Log Viewer.
A Connection list was added in Log Viewer for you to select a database from
multiple Audit Log databases.
BC-7880
If multiple mailboxes (POP3 email accounts) were configured to receive emails
from the same POP3 email servers, only the last mailbox worked, and failed
to receive emails from the other mailboxes.
================================================================================
Closed Issues in 6.1.0_HF-003
BC-8034
When importing a .csx configuration file to a new TIBCO BusinessConnect
installation, if the exported .csx configuration file contained a credential that
did not have a counter partner in the old BusinessConnect installation, the
import process failed.
BC-8021
If sending a Responder Request to a private process via a JMS queue failed due
to reasons such as failing to connect to a JMS server, resend was not possible
as the resend data was not logged in Audit Logs.
BC-8015
If the Allow All Operations check box was not selected in Business Agreement
Protocol Binding, messages in Inbox were not able to be downloaded by
TIBCO BusinessConnect PartnerExpress or through the SFTP/FTPS transports even if
the related operations had been added to the Operation Binding.
================================================================================
Closed Issues in 6.1.0_HF-002
BC-7996
When no port number was specified explicitly, outbound requests were not able to
be sent via the HTTPS transport through an HTTP proxy.
This issue has been fixed. Port number 443 was used as the default port number
if no port number was given explicitly.
BC-7994
An "unexpected end of content; expected Body" error occurred when sending
outbound requests from private processes to BusinessConnect engines via JMS
transport.
BC-7980
When the TIBCO BusinessConnect engine sent transactions via the HTTPS
(AS2_HTTPS, HTTPS) transport and the X.509 V3 Certificate contained extension
attributes like "postalCode", the SSL connection was not established.
This issue has been fixed. However, with the limitation that it only works when
ENTRUST is selected as the security provider for outbound HTTPS transport.
To set ENTRUST as the security provider for outbound HTTPS transport, perform
the following steps in TIBCO Administrator:
a. Click BusinessConnect > System Settings > Activated Protocol Plug-ins and
Properties > BC.
b. Set the bc.securityVendor.sockets property to ENTRUST, and then click Save.
================================================================================
Closed Issues in 6.1.0_HF-001
BC-7958
TIBCO BusinessConnect Gateway Server cipher suite algorithms restrictions only
worked when SunJCE was selected as the security provider. When ENTRUST was
selected as the security provider, this function did not work.
BC-7957
This was an enhancement. The Apache Tomcat server embedded in TIBCO
BusinessConnect Gateway Server has been upgraded to version 7.0.54 to mitigate
security risks.
BC-7955
The Socket Timeout (seconds) property of the HTTP, AS2_HTTP, HTTPS, and AS2_HTTPS
transports did not work as expected. Instead of representing the maximum
waiting time before receiving a response from the server, the property set the
maximum waiting time before establishing the connection.
BC-7953
In case some of the SSHFTP servers had restrictions of the number of
simultaneous connections for each FTP user, the SSHFTP channel cache of
BusinessConnect outbound SSHFTP transport resulted in making new connections
rejected by the server.
This issue has been fixed. A property was introduced to resolve this issue.
Add the following property to the BusinessConnect-Interior_Server.tra files of
each BusinessConnect Interior Server:
java.property.<TP_name>.sshftp.cache.disabled=false|true
and set the value to be true (the default value is false). The TP_name represents
the name of the trading partner which hosts the SSHFTP server. This will cause
each SSHFTP channel to close immediately after the FTP activity is completed.
BC-7936
The search in Participants and Business Agreements did not work for searching
strings with wildcards at both the beginning and the end, such as "xyz".
BC-7924
In Advanced Filters definition of Log Viewer, the pre-defined queries did not
work for the following cases:
- The query defined as contains.
- The query defined as is not like.
Environment
All Platforms
Issue/Introduction
TIBCO BusinessConnect 6.1.0 hotfix 8 has been released.
Feedback
Yes
No
Powered by
