TIBCO BW6: Application runtime configuration

Configuration of FlowLimits on AppNode level:

I have worked till now with TIBCO BW6.3.2 along with TEA_2.2.0 . I have experienced that the TEA GUI do not allow to change the flow limits for the components. This need to be configured at config.ini file for the AppNode. Also, this setting s only applied specific component for which it is configured. In order to do the same, we have to execute the following steps.

1. Find the name of the component as shown in the figure below.

2. Copy the AppNode configuration file at location /data/appdata/tibco/tibco/bw/<<version>>/domains/<<domainName>>/appnodes/<<appSpaceName>>/<<appNodeName>>/config.ini in a temporary location. 

3. Add the property in the following format.

bw.application.job.flowlimit.<UsersBWApplicationName>[.<UsersBWApplicationVersion>][.<UsersBWComponentName>]=8

e.g

 bw.application.job.flowlimit.MSDMS_IS_REST-HTTP.application.1.0.ComponentDocumentbeheerAsync=15

4. At the end of the file add below 2 linein order to improve the performance:

bw.engine.event.publisher.enabled=false

bw.frwk.event.subscriber.metrics.enabled=false

5. Push the configuration to Run time environment, by executing the command (at location /data/appdata/tibco/tibco/bw/<<version>>/bin), 

./bwadmin config -d <<domainName>> -a <<appSpaceName>> -n <<appNodeName>> -cf /tmp/config.ini

6. Finally restart the appNode in order to apply the changes.

TIBCO Businessworks 5.13.0 & TLSv1.2

We always face issues when we have to configure certificates with TIBCO BW. This time we have to migrate from TLS 1.0 to TLS 1.2. I am documenting my experience for future references.

Scenario

 In our scenario we have to interact/call a third party application using SOAP over HTTPS using TLS 1.2. Certificates were provided by the vendor, and following TIBCO release notes, the code migrated to TIBCO BW 5.13.0 (although TLS 1.2 is compatible with TIBCO BW5.12 onwards) from 5.11.x.

While calling the third party application web service using “SOAP Request Reply” activity we were facing Timeout issues. When the traffic over the network was monitored using wireshark, it was noticed that, TIBCO was not using TLS v1.2 where as it was using v1.0.

Resolution

By default TIBCO BW 5.13 use TLS 1.0 for SSL communication, although it is compatible with TLS 1.2. In order to make it work with TLS 1.2, a JAVA property need to add in the bwengine.tra file (located in <<TIBCO_HOME>>\bw\5.13\bin). Viz,

java.property.TIBCO_SECURITY_VENDOR=j2se

This is very strange for us on that occasion as this information was nowhere mentioned in the TIBCO BW document