Closed Issues in 6.1.0_HF-002 (This Release)

SOAP-959

SOAP messages that contained empty namespace (xmlns="") referring to the 
default namespace could not be processed by BusinessConnect SOAP Protocol.

This has been fixed.

SOAP-1250

SOAP messages that contained XML comments could not be processed by 
BusinessConnect SOAP Protocol and a SOAP Fault with the error code of 920 
would be replied.

This has been fixed.

Notice: After the fix the SOAP messages with XML comments will be 
processed, however the comments will be trimmed from the XML documents.

SOAP-1267

When a SOAP message header contained no domain element, the value of the
name element was treated as the name of the trading partner where the message
was from. Customers requested that the same behavior should be used when the
SOAP message header contained the domain element and this element was empty, 
such as  "<Domain></Domain>".

This has been enhanced. A new boolean property "soap.treatEmptyDomainAsNull"
has been introduced. When a SOAP message header contains an empty domain element, 
if this new property is set to "true", the value of the name element is treated 
as the name of the trading partner.

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

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

SOAP-1227

Configuration export/import to WSDL did not support WSS security token.

SOAP-1248

BusinessConnect SOAP Protocol did not 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" is 
introduced, with integer as the value type. Payload larger than this value 
will be transferred via file reference; the "requestFile" field in the 
RESPONDER.REQUEST message and the "responseFile" field in the 
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 > 
Activated 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 is 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 > Activated 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 > 
Activated Protocol Plug-ins and Properties > SOAP.