Description:
TIBCO BusinessConnect 5.2.1 hotfix 3 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/5.2.1/hotfix-03/

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

Closed Issues in 5.2.1 Hotfix 3 (This Release)

CR: 1-8T1UL4
The resend poller can raise a NullPointerException with business protocols
where the interaction type is not defined for some private process messages.
This problem has been fixed.

CR: 1-9B1IT3
Fix an issue where "no peer changes from the configuration UI occurs
when Admin and BusinessConnect engine are on different machines with
different network interface names" problem.

The Intercomponent network setting in the deployment UI would be used by
Administrator machine to send peer change to BusinessConnect engine.
BusinessConnect engine network settings must be overridden at each instance
of the BusinessConnect Engine in the .tra file after deployment to receive
the updates from the Administrator machine. This setting can be found
in the Application Management-&gtBusinessConnect-&gtConfiguration-&gtComponent
Settings-&gtIntercomponent Communication-&gtInterior Settings section.

Following properties must be added if there are network interface name
differences between Administrator and BusinessConnect machines along
with multicast group to each BusinessConnect engine .tra file. The value
entered as part of the network interface name in the BusinessConnect
engine .tra file is the NIC name pertaining to the machine and the
"multicast group" must be the IP address specified in the Intercomponent
network settings for Interior engines under deployment.

Following properties must be added and configured appropriately for
BusinessConnect Engine .tra files.

tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/network=&ltnic>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh/network=&ltnic>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz/network=&ltnic>&ltmulticast group>

Note:
-----

If there are more than two different network settings, but same "Service" ports
in any of the deployment configuration, then the second rendezvous transport
would not initialize due to RV and IP Protocol limitation. (Please refer RV
documentation for a clear explanation).

If the Private Process uses TIBCO Rendezvous for communication, then if the
"Service" value is the same as the one set in the InterComponent Communication->
Interior Settings, then either the "Service" value must be changed to something
different or the same Network value (&ltnic>&ltmulticast group>) must be specified
in the Deployment section for Rendezvous transport to start. The BusinessConnect
engine .tra file should also be modified for the following property:

tibco.clientVar.gatewayProperties/transports/backoffice/RVCMQ/network=&ltnic>&ltmulticast group>

Bus.User.&ltrv parameters> and Bus.Default.&ltrv parameters> parameters in
the .tra may also be needed to change if the service parameter is the
same as the one in the Intercomponent Interior engine settings in the
deployment section.

CR: 1-9CVW59
EZComm protocol is not sending payload as file reference on Responder.Request Message
for FTP Get protocol.

A new property, "ezcomm.interior.pp.threshold" is now added to EZComm protocol.
If the payload size (in bytes) is above the value specified in this property, payload
is sent as a file reference to private process. This behavior is only applicable to
FTP-Get transport protocol. If this property is not specified, it defaults to
'Skip Content Threshold' specified in Application Management-&gtBusiness
Connect-&gtConfiguration-&gtIntercomponent Advanced tab in the Deployment.

Users can add the above mentioned property in the Configuration UI at
BusinessConnect-&gtSystem Settings-&gtInstalled Protocols-&gtEZComm. They need to
add an integer property name "ezcomm.interior.pp.threshold" and enter a threshold
value.