TIBCO BusinessConnect 7.0.0 hotfix 3 has been released.

You can download this Hot Fix from the TIBCO Product Support website using your TIBCO Support username (email address) and password under “Downloads” and then “Hotfixes”

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

           /AvailableDownloads/BusinessConnect/7.0.0/hotfix-03

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

Closed Issues in 7.0.0_HF-003 (This Release)

BC-10224
TIBCO BusinessConnect now supports NAESB 3.1.

BC-10173
TIBCO BusinessConnect ebXML Protocol implementation failed to encrypt outbound 
message, when 'SMIME encryption' is used as the type of encryption.

================================================================================
Closed Issues in 7.0.0_HF-002

BC-10036
"JMSBoCommunicator: Trying to restore JMS connection" message is logged at regular 
intervals in TIBCO BusinessConnect Interior Server logs, even after a successful 
reconnection.

BC-10012
TIBCO BusinessConnect now supports RSASSA-PSS Signature Algorithm and RSAES-OAEP Key 
Transport Algorithm. 
With this feature the TIBCO BusinessConnect administrator can configure desired 
Signature and Encryption schemes for EMAIL, AS1_EMAIL, AS2_HTTP, AS2_HTTPS transports.

NOTE: This feature will only work in conjunction with TRA 5.10.1 HF-001.

BC-10010
TIBCO BusinessConnect now supports RSA encryption using OAEP padding 
with SHA-256 hash function.

NOTE: This feature will only work in conjunction with TRA 5.10.1 HF-001.

BC-9975
Inbound FTP/FTPS/SSHFTP pollers failed to process received documents.

BC-9953
When the EMS based inter-component communication between TIBCO BusinessConnect 
Interior server and private process is broken, the inbound transactions will fail 
and can only be re-sent manually.

BC-9952 
While processing a duplicate transaction, SqlIntegrityConstraintViolationException
is reported in TIBCO BusinessConnect Interior server engine logs, when working with 
IBM DB2 database.

================================================================================
Closed Issues in 7.0.0_HF-001

BC-9854 Allow a separate DMZ EMS server to be used for GS-IS communication.

Added an optional EMS server to be configured in the DMZ zone that will be
used for all communication between the Gateway and Interior servers. 

To configure the DMZ EMS server in Tibco Administrator, navigate to the 
Application Management > BusinessConnect > Configuration, select Component Settings 
tab under BusinessConnect and populate the JNDI Context URL for the 
Intercomponent DMZ-JMS Settings (Optional).

When the user switches to using the DMZ EMS server (by populating the URL) or
switches back to the default configuration (by removing this URL),

1) The deployment should be undeployed/deleted and redeployed.

2) The gateway tokens should be re-exported.