Products | Versions |
---|---|
TIBCO ActiveMatrix Adapter Framework | 1.4.1 |
TIBCO ActiveMatrix(R) Adapter Framework 1.4.1 Hotfix1 is released for all supported platforms. This hotfix is cumulative of prior hot fixes for this version. Listed below is a summary of updates included in Hotfix1. Please refer to the attached Readme for additional details on these and other cumulative fixes included in this Hotfix.
================================================================================
Closed Issues in 1.4.1_HF-001 (This Release)
ADF-3623
Installation using Adapter2Plugin Profile does not work with ADF 1.4.1
This issue is fixed.
ADF-3619
When a TIBCO ActiveMatrix BusinessWorks application is running in multiple
appnodes configured in FT mode, the AdapterSubscriber activity configured using
JMS transport was registered to JMS destination from passive appnodes.
This issue is fixed.
ADF-3615
TIBCO Adapter Framework ignored the RV transport type available in the Advanced
tab of Adapter Palette activities.
This issue is fixed.
Note:
Additional configuration properties have been added for Transport types: "Tibrv
Certified" and "Tibrv Certified Message Queue" in the Advanced tab of Adapter
Palette activities. To override similar configuration properties in the RV shared
resource, these new configuration properties would need to be configured. When RV
shared resource is selected from the Advanced tab, the values / module properties
are copied from RV shared resource to the corresponding fields added in
Advanced tab.
Below configuration properties added to the Advanced tab pertain to double
data type and this type is not supported by TIBCO BusinessWorks as a module
property. Literal values must be used.
- Scheduler Heartbeat
- Scheduler Activation
- Worker Complete time
ADF-3502
Application containing Adapter Palette activities configured with RV transport
would generate "TIBCO-BW-PALETTE-AE-500007: Cannot create reply listener for
subject: {0}" error when being stopped from bwadmin.
This issue is fixed.
================================================================================
Note:
Below tra parameter is supported in this version to allow user 'Client Acknowledge Mode' for Adapter Subscriber Activity:
disable.adsub.autoconfirm
When this parameter sets to true, the Subscriber activity would create consumer in client acknowledge mode. User must use a Confirm Activity to acknowledge the message. Otherwise the message would always stay in the queue.
When this parameter sets to false, the Adapter Subscriber activity would create consumer in auto acknowledge mode. This is the default setting.
This parameter needs to set in the appnode's tra file. And this parameter will affect all the Adapter Subscriber in the same app node.
Please refer to the instruction of Installation/Uninstallation in Readme file for more information.
This hotfix can be downloaded from TIBCO Support Customer Portal Web UI(https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option under:
/AvailableDownloads/Adapters/Adapter-Framework/1.4.1/hotfix-01
Please contact TIBCO Support if you have any problems finding or downloading this Hotfix.