TIBCO BusinessConnect SOAP Protocol 6.1.0 hotfix 1 has been released.

TIBCO BusinessConnect SOAP Protocol 6.1.0 hotfix 1 has been released.

book

Article ID: KB0102925

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Description:
TIBCO BusinessConnect SOAP Protocol 6.1.0 hotfix 1 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

           /AvailableDownloads/BusinessConnect/SOAP/6.1.0/hotfix-01

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-001 (This Release)

SOAP-1227

Configuration export/import to WSDL didn't support WSS security token.

SOAP-1248

BusinessConnect SOAP Protocol didn't support transferring large payloads by 
using file references between BusinessConnect servers and private process 
engines.

This has been fixed. A new property "bc.soap.pp.fileref.threshold" was 
introduced, with integer as the value type. Payload larger than this value 
will be transferred via file reference; "requestFile" field in RESPONDER.REQUEST 
message and "responseFile" field in INITIATOR.RESPONSE message carry the file 
references, which refer to the files in file system. The "shared file location" 
is used for storing these temporary files.

To configure this property, go to BusinessConnect > System Settings > Active 
Protocol Plug-ins and Properties > SOAP.

SOAP-1249

If inbound messages were larger than Data Streaming Threshold set in the
GatewayServer HTTP inbound transport, the inbound messages were stored
in temporary files but not removed after the inbound messages were processed.

SOAP-1251

TIBCO BusinessConnect SOAP Protocol did not support the SHA256, SHA384
and SHA512 digesting algorithms for signatures of outbound messages.

SOAP-1254

TIBCO BusinessConnect SOAP Protocol did not include Transaction ID for inbound 
duplicate detecting, which is asked by some customers.

This has been enhanced. A new boolean property "soap.dupDetect.txnID.included" 
has been introduced, which enables the Transaction ID to be included in
detecting if an inbound message is duplicated if it's set to "true".

Another boolean property "soap.duplicate.reject" is introduced to determine 
whether a inbound duplicate message is rejected, or still forwarded to 
private process.

Both of the these two properties are configurable in BusinessConnect > System 
Settings > Active Protocol Plug-ins and Properties > SOAP.

SOAP-1262

TIBCO BusinessConnect SOAP Protocol did not support using RSA_OAEP as the 
symmetric key exchange encryption algorithm for outbound transactions.

This has been fixed. A new property "soap.ob.keyExchange.algo" has been 
introduced with three value options: "rsa-1_5", "rsa-oaep" and "rsa-oaep-mgf1p";
choose the right value to enable certain algorithm. The default value is
"rsa-1_5" if this property is not configured.

To configure this property, go to BusinessConnect > System Settings > Active 
Protocol Plug-ins and Properties > SOAP.

Issue/Introduction

TIBCO BusinessConnect SOAP Protocol 6.1.0 hotfix 1 has been released.

Environment

All platforms