Description:
TIBCO BusinessConnect 5.3.0 hotfix 2 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.3.0/hotfix-02/

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

Closed Issues in 5.3.0 Hotfix 2 (This Release)

CR: 1-APMLK6

Intercomponent Communication Rendezvous Settings
Intercomponent Communication Rendezvous settings are used for a myriad of
communication between different components and sub-components within the
TIBCO BusinessConnect Servers.
Intercomponent Communication Rendezvous settings are used for the following
core communications:
• Communication between BusinessConnect DMZ Server and BusinessConnect
Interior Server to relay the message to BusinessConnect Servers.
• Within the BusinessConnect Interior Server for its various sub-components,
such as process starters, poller triggers, and intracomponent communications.
• By the TIBCO Administrator, which sends peer updates made in the UI to the
runtime BusinessConnect Interior Server.
• By the DMZ Servlet Component residing in the supported commercial Application
Servers to BusinessConnect Interior Server.

To accommodate the above communications between different components and
in cases that involve different subnets or local rvd daemons, these
settings could be overridable at each service instance in the appropriate
component .tra file, as described below.

• BusinessConnect DMZ Server Override Setting

BusinessConnect DMZ Server instance can override the Rendezvous transport
parameters such as the daemon host to use local rvd daemon instead of the
configured daemon. This can be done in the deployed .tra file setting.

Following are the properties that can be overridden:

tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/daemon=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/daemon=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/daemon=&ltvalue>


• BusinessConnect Interior Server Override Settings

Following properties must be added if there are differences in the network
part of the network parameter between TIBCO Administrator and TIBCO
BusinessConnect Server machines, along with multicast group to each
BusinessConnect Interior Server engine .tra file. The values entered should
follow the same rules of creating a Rendezvous transport. This is used when
other than default is being set for the network part, and an appropriate
value is set for the network parameter.

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

tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/msh
/daemon=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh
/daemon=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/network=&ltnic|hostname|ip>&ltmulticast group>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/service=&ltvalue>
tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz
/daemon=&ltvalue>

• TIBCO Administrator to BusinessConnect Interior Server Peer Update Settings

TIBCO Administrator is not required to run on the same physical machine as
BusinessConnect Interior Server and, in certain other usage scenarios,
TIBCO Administrator could be running on a separate subnet not related to the
subnets that BusinessConnect Runtime servers are running (which include
BusinessConnect Interior Servers). The Intercomponent settings, therefore,
are required to be overridable at each service instance when they involve
use of the IP multicast over subnets.

Changes involve picking the Rendezvous transport parameters specified in
the TRA for each runtime engine. The Intercomponent settings in the
deployment UI will be used by TIBCO Administrator machine to send peer change
to the TIBCO BusinessConnect Server engines whenever there are changes made
to agent configurations as well. To allow multiple Administrator machines to
work in a cluster environment, as well as use its own local Rendezvous daemon
instead of remote daemon, three new properties are needed to be added to the
Administrator .tra file.

The values set to the appropriate values allow the Administrator component
to communicate the peer updates through its own local rvd daemon using
multicast.
The properties to be added in the Administrator .tra file are:

java.property.bc.gui.intercomponent.peerupdates.daemon=&ltvalue>
java.property.bc.gui.intercomponent.peerupdates.service=&ltvalue>
java.property.bc.gui.intercomponent.peerupdates.network=&ltnic|host
name|ip>&ltmulticast group>

Note: These values must be changed anytime there is a change made in the
Intercomponent settings of the deployment UI and TIBCO Administrator needs
to be restarted after every update. Otherwise, the peer updates from the GUI will
not be reachable to the TIBCO BusinessConnect Server engines.

The values should adhere to the same rules of creating a Rendezvous transport
(see TIBCO Rendezvous documentation for more details).

Other than the above properties, there are other TIBCO Hawk, fault tolerant
or default TIBCO Rendezvous parameters that might need valid values set for
the TIBCO BusinessConnect components to start.

These parameters are:
Bus.User.&ltrv parameters>
Hawk.&ltrv parameters>
Bus.FtDefault.&ltrv parameters>
Bus.Default.&ltrv parameters>

Parameters in the file .tra may also need to change if the service parameter is
the same as the one in the Intercomponent Interior engine settings in the
deployment section.

• DMZ Servlet Component of TIBCO BusinessConnect  

Following are applicable only for users who have installed the DMZ component
of TIBCO BusinessConnect in the Application Servers like WebLogic, WebSphere
or JBoss.

Users must regenerate the bcdmz.war file from bcappmanage tool which exports the
DMZ Component of BusinessConnect as DMZServlet.

Three new properties are added to configure the TIBCO Rendezvous communication
settings to send messages from the DMZ Component to BusinessConnect Interior Servers.
The properties can be edited and placed back in the bcdmz.war file in the file dmz.dat
under the Properties Section Intercomponent.
bc.dmz.rv.service=&ltvalue>
bc.dmz.rv.network=&ltnic|hostname|ip>&ltmulticast group>
bc.dmz.rv.daemon=&ltvalue>

The changed bcdmz.war file should be placed appropriately to the Application Servers
as mentioned in their respective documentation to use the new settings.

This change needs to be done everytime there is a change to the DMZ Settings of
Intercomponent in the Deployment.

CR: 1-ARAIVF
When executing bcappmanage activities that involve connecting to the Administrator
domain like 'exportDmzAsServlet', any changes after the deployment and redeploying
BusinessConnect from the UI would cause the deployment to fail with a
'Server Plugin Failed' at the Application Management-&gtBusinessConnect-&gtConfiguration
tab.

This issue is fixed.

TIBCO BusinessConnect 5.3.0 hotfix 2 has been released.

Product: TIBCO BusinessConnect Version: 5.3.0 OS: All --------------------