TIBCO Silver Fabric Enabler for · TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks...

Two-Second Adv

TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™

Release NotesSoftware Release 3.3.0 August 2016

antage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, Two-Second Advantage, TIBCO Silver, TIBCO Silver Fabric, TIBCO ActiveMatrix BusinessWorks, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2011-2016 TIBCO Software Inc. All rights reserved.TIBCO Software Inc. Confidential Information

Contents | iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks Release Notes

iv | Contents


Preface | v

Preface

TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™ is a complementary software component. Using this software component, you can deploy TIBCO ActiveMatrix BusinessWorks projects in cloud environments based on TIBCO Silver Fabric and leverage Silver Fabric capabilities. This accelerates deployments of BusinessWorks projects, enforces its industry best practices, and provides elastic optimization of computing resources.

Topics

• Connecting with TIBCO Resources, page vi


vi | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationAll product documentation is available from https://docs.tibco.com

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks documentation is here:

https://docs.tibco.com/products/tibco-silver-fabric-enabler-for-activematrix-businesswork

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support


https://docs.tibco.com

https://docs.tibco.com/products/tibco-silver-fabric-enabler-for-activematrix-businessworks-3-3-0

https://docs.tibco.com/products/tibco-silver-fabric-enabler-for-activematrix-businessworks-3-3-0

http://www.tibcommunity.com

| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 7

• Deprecated and Removed Features, page 8

• Migration and Compatibility, page 9

• Closed Issues, page 10

• Known Issues, page 19



2 | Release Notes

New Features

The following new features have been added to TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™.

Release 3.3.0The following features are provided in this release.

Support for External Database

Supports more external relational databases for domain data persistence with EMS transport. Microsoft SQL Server, Oracle and DB2 are the new supported databases.

Support for TIBCO FTL ®

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks now support Database and FTL as the domain data persistence and communication transport layer.

Release 3.2.0The following features are provided in this release.

Component Upgrade

Supports upgrade of components created with previous versions. You can create runtime components from different versions.

Support for TIBCO Enterprise Messaging Service™ (EMS) SSL

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks now supports configuration for using TIBCO Enterprise Messaging Service™ securely, when using BusinessWorks 5.x distribution. Note: You may require TIBCO Silver® Fabric Enabler for TIBCO Administrator™ - Enterprise Edition 2.9.0 HF4.


New Features | 3

Support to customize AddMachine properties

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks now supports customizing the properties of AddMachine. You can customize the properties by editing the AddMachine.properties file when using BusinessWorks 5.x distribution.

Release 3.1.0

Support for External Database

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks 6.x supports an external database such as PostgreSql or MySQL for data persistence and TIBCO Enterprise Message Service™ (EMS) as the communication transport layer. It provides high availability to many BusinessWorks instance for more manageable storage as the message transport is fast and the database is independent.

ActiveMatrix BusinessWorks 5.x Component Configurations

• The deployment of ActiveMatrix BusinessWorks application archives using the REST now supports multiple VariableProviders at the same time.

• While creating BusinessWorks 5.x component, the TIBCO BusinessWorks Basic Configuration dialog now provides the following new options:

— Delete Application Configuration at Shutdown.

— Do Not Redeploy Existing EAR File at Startup

— Force Kill of BusinessWorks Process by Engine Daemon on Shutdown

• While creating BusinessWorks 5.x component, the TIBCO Hawk Agent Running Condition dialog provides the following new option:

— Force Kill of TIBCO Hawk Agent Process by Engine Daemon on Shutdown

Backward Compatible for Current Distributions

The Enabler is backward compatible with supported TIBCO ActiveMatrix BusinessWorks Distributions. Refer to the Readme to see all current versions supported.

Upgrade Enabler Components

Components created with release 3.0 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks can be upgraded to utilize features of the 3.1.0 release.


4 | Release Notes

Release 3.0.0

Supports TIBCO ActiveMatrix BusinessWorks 6.2

TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks supports configuration and publishing of TIBCO ActiveMatrix BusinessWorks™ Distribution for TIBCO Silver® Fabric. Run it in Enterprise ready or Local standalone configurations.

TIBCO ActiveMatrix BusinessWorks™ is at the heart of TIBCO's application integration platform. With the TIBCO Silver Fabric Enabler you can publish and replicate scalable, robust, dynamic, applications. You can gather and expose data as real-time events or API services that give you and your applications flexibility to serve and consume data as a service. TIBCO ActiveMatrix BusinessWorks gives you the platform and tools to design, publish, and run applications on TIBCO Silver Fabric to automate processes with timely and appropriate actions.

Backward Compatible for Current Distributions

The Enabler is backward compatible with supported TIBCO ActiveMatrix BusinessWorks Distributions. Refer to the Readme to see all current versions supported.

Supports Enabler for TIBCO Administrator

Installation pre-requisites for TIBCO ActiveMatrix BusinessWorks Distribution release 5.12 are simplified by the creation of an independent TIBCO Silver® Fabric Enabler for TIBCO Administrator™.

Installation Prerequisites Removed and Streamlined

Many installation pre-requisites for TIBCO ActiveMatrix BusinessWorks Distribution release 6.2 are eliminated. Only two BW 6.2 distribution files are required per targeted platform.

For implementations that use TIBCO ActiveMatrix BusinessWorks Distribution release 5.12 the dependency on SilverFabric_tra_common_<os>_rollup is also removed. Users of TIBCO ActiveMatrix BusinessWorks Distribution release 5.12 can get the latest supported distributions of TIBCO Administrator™, TIBCO EMS, TIBCO Rendezvous®, TIBCO Hawk®, and TIBCO Runtime Agent™ without waiting for an update or the TRA Common roll-up zip archive. Open source libraries are now downloaded separately to keep software costs lower.


New Features | 5

Refer to the respective Installation Guide for TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™ Configure, publish, run and scale BusinessWorks 6.2 application archives Run TIBCO ActiveMatrix BusinessWorks 6.2 application archives and scale based on BW Archive statistics. Continuous deployment using the REST interface provides a scriptable way to scale archives that can deploy and run the archive using a single command. Stack based archive scaling enables addition and removal of application archives based on archive statistics set with conditional triggers you define.

Integration with Variable Provider

Supports use of TIBCO Silver® Fabric Continuity on published environments.

Change deployment environments and published configuration values quickly with the variable provider, TIBCO Silver® Fabric Continuity.

Automated bwagent Registration with TIBCO Enterprise Administrator

Run TIBCO ActiveMatrix BusinessWorks Components in stacks with a dependency on TIBCO Enterprise Administrator (TEA) and you can manage your Domain, AppSpace, AppNodes, Applications and more with the TEA server interfaces. Alternatively you can connect to and use an external TEA server to accomplish the same management tasks.

In one Stack this Enabler and the first release of TEA supports one BW Component running in the Server Agent Role and many BW Components running in the Client Agent Role. So you can scale many TIBCO ActiveMatrix BusinessWorks Clients running on the same Domain with as many application archives running as your physical constraints will allow.

Provision Environment, Agent Role, Domain, AppSpace, and AppNode Create, configure, and publish TIBCO ActiveMatrix BusinessWorks™ 6.x Components specifying Environment Type, Agent Role, Domain, AppSpace, and AppNode where your applications will be run.

Running Condition Checks Performed Regularly

When TIBCO ActiveMatrix BusinessWorks is running in Local mode the AppNode is regularly checked to make sure it is responsive. When TIBCO ActiveMatrix BusinessWorks is running in Enterprise mode, bwagent is checked regularly. Configurable thresholds and periodicity of checks allow for appropriate responses when necessary.


6 | Release Notes

Upgrade Enabler Components

Components created with release 2.6 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks can be upgraded to utilize features of the 3.0.0 release.


Changes in Functionality | 7

Changes in Functionality

The following are the changes in functionality in TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

Release 3.3.0There are no changes in functionality in version 3.3.0 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.



Release 3.0.0

Distribution selection changes installation and Component Wizard

TIBCO ActiveMatrix BusinessWorks Distributions are significantly different in many respects. The user must pay special attention to different installation pre-requisites when a TIBCO ActiveMatrix BusinessWorks 5.x distribution will be used versus when TIBCO ActiveMatrix BusinessWorks 6. x distribution is used.

To avoid confusion in both installation pre-requisites and additional dramatic Component Wizard changes, the Enabler documentation is separated depending on Distribution version being used.

When using 5.9 - 5.12 releases of TIBCO ActiveMatrix BusinessWorks Distribution refer to the documentation for TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks 2.6.0.

When using the 6.2 release of of TIBCO ActiveMatrix BusinessWorks Distribution refer to the documentation for TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks 3.0.0.


8 | Release Notes

Deprecated and Removed Features

No features are deprecated or removed in version 3.3.0 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.


Migration and Compatibility | 9

Migration and Compatibility

Upgrade and migration instructions for components created with previous releases of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks are covered in the user’s guide.

The migration of a domain to TIBCO Runtime Agent (TRA) 5.9.0 is not supported. However, you can migrate to TRA version 5.9.1 and above.


10 | Release Notes

Closed Issues

The table lists closed issues for TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks for the respective releases.

Version Key Summary

3.3.0 SFBW-1343 When using EMS SSL as transport, the property ssl_vendor was not changed to j2se in the file hawkagent.cfg

3.3.0 SFBW-1374 Whenever the BusinessWorks component was restarted, appspaces, appnode, archives, domain, and so on were recreated. This was happening even when the data store location was provided in the component configuration wizard.

3.3.0 SFBW-1375 Some bwengine processes were still seen running even after the BusinessWorks stack on which they were running was stopped.

3.3.0 SFBW-1377 The property -machine_name was missing from hawkagent.cfg file, when a new TLM was created.

3.3.0 SFBW-1378 An .ear file, that contained a hyphen in the .par name, cannot be deployed in Load Balance mode with command line.

3.3.0 SFBW-1379 An application status on one component was changed from “Stopped” to “Running” after deploying the same application using REST with NoStart=true to other component..

3.2.0 SFBW-1263 FAST TLM Restart was not executed because of wrong upgrade detection.

3.2.0 SFBW-1264 BWEngine crashed when ActiveSpaces loaded OpenSSL libraries.

3.2.0 SFBW-1276 There was an issue with BusinessWorks enabler for JNDI jar clash.

3.2.0 SFBW-1284 There was a high Engine CPU usage during the archive detection of certain complex EAR Archive which is optimized now.


Closed Issues | 11

3.2.0 SFBW-1319 Deploying archives with multiple applications on two different component types using ant script, threw an exception.

Note: If you want to deploy an ear application which contains process archive and adapter archive using the ant script or the REST client, you need to deploy it at least twice.

Steps for deploying it are as follows:

1. Set "ComponentName = First_Component_Name" in the deployment criteria properties file (deploymentFile for REST client, criteriafile for Ant Task).

2. Deploy the application.

3. Update the deployment criteria properties file by setting "ComponentName = Second_Component_Name".

4. Deploy the application.

5. Repeat steps 3 and 4 if there are more components where the application is to be deployed.

Warning: When deploying an application on multiple components do not add ForceDeploy parameter.

3.2.0 SFBW-1320 Dropdown to choose EMS optional distribution was not populated when the component was created from the Ant scripts. But, the dropdown was correctly populated when the component is created manually from the UI

3.2.0 SFBW-1329 Optimization of the updateActivationInfoProperties

Calls to reduce the number of thread at the broker.The enabler calls updateActivationInfoProperties only if there is a change in the Static Route. Static Route changes include deployment/undeployment or starting/stopping of an archive.

3.1.0 SFBW-1242 While upgrading TIBCO ActiveMatrix BusinessWorks from version 11.0 to 12.0 or higher, if you select the Fast TLM restart option and change the BusinessWorks and TRA Distribution versions, all applications get redeployed.

Workaround if you want to upgrade manually from TIBCO Administrator at your convenience and not let the enabler redeploy the applications on upgrade, set the runtime variable UPGRADE_TO_LATEST_VERSION_MANUALLY to true.

Version Key Summary


12 | Release Notes

3.1.0 SFBW-1220 The tibhawkhma process did not shut down even after a BusinessWorks or TIBCO Administrator component was stopped.

3.1.0 SFBW-1208 When using TIBCO Runtime Agent Distribution for TIBCO Silver Fabric 5.9.x, some of the hawk microagents did not start.

3.1.0 SFBW-1204 Even if different values are set for DB_MIN_CONNECTIONS and DB_MAX_CONNECTIONS in 'Silver Fabric Enabler for ActiveMatrix BusinessWorks' than the values set in 'Silver Fabric Enabler for TIBCO Administrator', the values do not make any effect.

3.1.0 SFBW-1199 After changing the Administrator password of the TIBCO Enterprise Message Service component with authorization enabled, TIBCO Administrator was unable to connect to TIBCO Enterprise Message Service, on restarting the TIBCO Administrator Enabler.

Note: The resolution requires Silver® Fabric Enabler for Enterprise Message Service™ 2.1.0 HF003.

3.1.0 SFBW-1193 If the AppNode was created from TIBCO Enterprise Administrator, the bwadmin.log and bwagent.log were displayed in the log URL list, but the appnode.log for that AppNode did not display.

3.1.0 SFBW-1170 Running the AppManage command from the BusinessWorks Enabler, the ps of the process showed the password unexpectedly.

3.1.0 SFBW-1144 The exported runtime variable EMS_ADMIN_PASSWORD displayed the encrypted value in the Silver Fabric Administration UI.

It is now exported as ENCRYPTED_TYPE and show **** in the Silver Fabric administration UI.

Silver Fabric Broker 5.6.0 HF8 must be applied before, to have this defect corrected.

3.1.0 SFBW-1072 TIBCO ActiveMatrix BusinessWorks plug-ins were unselected in the component wizard in Internet Explorer 11.

3.1.0 SFBW-1046 Modifying the hawkagent_<domain>.tra files by editing the associated template file (that is, hawkagenttra.template) on TIBCO Administrator component was not possible using the configure.xml file.

3.1.0 SFBW-870 The REST client deployment failed when an attempt was made to set alertAction.enable or alertAction.message.

Version Key Summary


Closed Issues | 13

3.1.0 SFBW-464 When the Hawk library used JNI to call TIBCO Rendezvous, DSEngines with BusinessWorks archives were restarted unexpectedly, creating orphaned processes. Now an error condition caused while processing messages outside of the dispatch thread is fixed.

3.0.0 SFBW-1091 When using a domain with EMS transport, if the EMS server was down, the virtual router for BW HTTP endpoints was removed. This issue is now corrected.

3.0.0 SFBW-472 Multiple BusinessWorks EAR files deployed on the same engine did not work correctly with a Virtual Router if they use the same URI.

3.0.0 SFBW-1051 Addition of <![CDATA[]]> format to LDAP search Filter with UI option was unavailable.

3.0.0 SFBW-1050 Setting ArchiveSetting was not possible for a defined list of bwprocess (all or one).

The following set of properties are now supported in the REST call:

ArchiveSettings.bwprocess.<ACTION>ArchiveSettings.bwprocess.<ACTION>.<PROCESS_NAME>ArchiveSettings.bwprocess.<ACTION>.<ARCHIVE_NAME>.<PROCESS_NAME>

Where:

<ACTION> has a value of: enabled, maxjob, activation, or flowlimit

<PROCESS_NAME> contains the path of the BusinessWorks process and ends with ".process" or ".serviceagent" as a suffix of the name value.

<ARCHIVE_NAME> Name of the archive ending with .par as a name suffix.Sample of a property:

ArchiveSettings.bwprocess.flowlimit.Read From Sources.par.JMS/Starters/Read Queue.process<ACTION> = flowlimit<ARCHIVE_NAME> = Read From Sources.par<PROCESS_NAME> = JMS/Starters/Read Queue.process

Version Key Summary


14 | Release Notes

3.0.0 SFBW-1048 Empty folders under Application Management in TIBCO administrator GUI were deleted when the BW component was shut down

- If the runtime variable CLEANUP_EMPTY_DIRECTORY_ON_SHUTDOWN is created and set to false, empty directories are not deleted on the BW component shut down.

- If the runtime variable CLEANUP_EMPTY_DIRECTORY_ON_SHUTDOWN is set to true or not present (default), orphan directories are properly deleted.

3.0.0 SFBW-1043 Add Alternative Base DN / User Search Filter and Group Search Filter in LDAP UI configuration

3.0.0 SFBW-1040 Now supports upload of Hawk MicroAgent Plugin configuration in the hma_plugin_dir.

3.0.0 SFBW-1022 An NPE in the AppManageExtension caused an archive scaling management failure for BW archives.

3.0.0 SFBW-1020 Some parameters from BW starter processes were incorrectly being protected from change.

3.0.0 SFBW-1015 Full stops/periods "." in the Application name were replaced with "2E" and prevented proper deployment and archive scaling.

3.0.0 SFBW-1011 Value of the property ‘application.start.dir’ in the application TRA file was changed incorrectly when a BW component was restarted with the FAST TLM restart option.

3.0.0 SFBW-1007 A Virtual Router instance contained static routes to a BWengine that was stopped and then allowed requests to be redirected to that stopped endpoint. The error condition is now corrected.

3.0.0 SFBW-998 Virtual Router static routes to running BWengine instances were sometimes removed incorrectly under specific conditions. This is now corrected.

3.0.0 SFBW-903 BWEngine process is not stopped when a Silver Fabric BusinessWorks Component is stopped through Silver Fabric Admin UI

3.0.0 SFBW-890 TIBCO Administrator enabler is not able to validate if TIBCO Administrator is ready when ssl is used with CA signed certificate.

Version Key Summary


Closed Issues | 15

3.0.0 SFBW-882 The HTTP ports for scaled-up archive instances were not correctly calculated.

3.0.0 SFBW-879 When an application name containing folders was deployed using REST on two different TLM, it generated a wrong application name.

3.0.0 SFBW-878 When a Sales Force .ear was deployed, the static route did not exist. That is now corrected.

3.0.0 SFBW-1067 Statistics were missing for scaling up archives based on memory used.

The following statistics have been added:

— BW Archive Total Allocated Memory

— BW Archive Memory Used Bytes

— BW Memory Used Bytes

— BW Total Allocated Memory

These statistics are not set by default. To add them during the component configuration, click the Add button in the "Add/edit tracked statistics" menu and select them.

2.6.0 SFBW-838 If a BusinessWorks process definition is located under two (or more) subdirectories of the process archive, no HTTP port could be managed by TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

The fix is effective when executing the deployment.

Workaround Before running the component with TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks, manually undeploy the BusinessWorks application with TIBCO Administrator or the command-line utility AppManage.

2.6.0 SFBW-830 If a BusinessWorks process definition is located under two (or more) subdirectories of the process archive, no HTTP port could be managed by TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

2.6.0 SFBW-821 Archive scaling failed due to a temporary file conflict.

Version Key Summary


16 | Release Notes

2.6.0 SFBW-819 Changes made to an HTTP runtime variable of a published BusinessWorks application archive caused associated service bindings to change state to "Deployable" causing them to restart.

The fix for this issue enables uninterrupted archive scaling by setting a global variable, so that new BusinessWorks Application Archive instances receive a calculated HTTP port value.

2.6.0 SFBW-813 When adding external JAR files for classpaths in the bwengine.tra file, Silver Fabric Enabler for TIBCO ActiveMatrix BusinessWorks used the wrong case for the PSP variable. Instead of %PSP%, it used %psp%.

2.6.0 SFBW-783 Components using Fast TLM mode with specific TIBCO Hawk AMI parameters can now be successfully restarted.

2.6.0 SFBW-771 When a BW archive rule for scaling up was set without a scaling down rule, scaling down was less predictable when maximum archive instances were reached.

2.5.0 SFBW-762 Sometime when setting the runtime variable FORCE_COMPOMENT_INSTANCE_VALUE to true the machine name generation generates a null pointer exception.

2.6.0 SFBW-734 Spaces can now be used in the AppName and ArchiveName. Problem no longer exists when using TIBCO Silver Fabric 5.5.0 or higher

2.6.0 SFBW-733 Scaling up an archive instance with HTTP activity used to trigger a TRA API issue that marked all the global variables (even unchanged ones) as updated, requiring a restart.

2.6.0 SFBW-732 For SF Engines with UNIX-based platforms, some BW processes could not be stopped automatically, after the de-allocation of the BW Component on that resource.

2.5.1 SFBW_782 For customers moving from standalone TIBCO ActiveMatrix BusinessWorks to TIBCO ActiveMatrix BusinessWorks instantiated on TIBCO Silver Fabric specific environment variables are now being appended instead of overwritten to retain all values relevant to the deployment.

2.5.1 SFBW-769 When doing an archive scale up and archive scale down, ContextUrl of the virtual router were not cleared.

Version Key Summary


Closed Issues | 17

2.1.0 SFBW-719 In certain situations, when connections with Hawk failed, multiple attempts to reconnect file descriptors were not released and caused the system to be out of resources.

2.1.0 SFBW-702 When the HTTP port global variable was located in a variable group folder, the Virtual Router Static route was not created.

2.1.0 SFBW-695 When there were multiple HTTP share resources used by different HTTP activities in the same BW enterprise archive (.ear), only the first shared resource was considered to be substituted and used in all HTTP activities.

2.1.0 SFBW-791 The Application TRA file under Fast TLM directory in Silver Fabric was incorrect after the TLM restart.

2.1.0 SFBW-689 TLM did not always keep the same name when it was restarted.

2.0.0 SFBW-678 Service instance names with more than 34 characters were not truncated during the redeployment of the application when TLM was restarted.

2.0.0 SFBW-495 On Windows Engines multiple duplicate Hawk agent services can now be created and they are removed when the application component is shut down. This issue was mostly cosmetic and is now fixed.

2.0.0 SFBW-217 In previous releases it was possible for a TIBCO Runtime Agent™ (TRA) to leave a deployed ActiveMatrix BusinessWorks Engine stranded and unusable if the deployed application component was being edited using the TIBCO Administrator at the same time that TRA attempted to undeploy the engine.

1.2.1 SFBW-540 BW did not deploy from SFBW if we specified a configuration for the service instance in the config.xml file.

1.2.1 SFBW-525 The TIBCO Administrator Enabler configuration UI now allows for editing of runtime variables in the container.

Version Key Summary


18 | Release Notes

1.2.0 SFBW-433 This was a customer reported issue: SR_ID:1-D5CXJT

BW Application Component instance went into an infinite loop. The engine log reported: "Software didn't register to machine, hawk agent will restart."

This issue has been fixed by the addition of two new parameters and a new registration validation process:CHECK_PRODUCT_REGISTRATION_NBRETRY (default value 4) CHECK_PRODUCT_REGISTRATION_WAITTIME (default value is 10 sec)

BusinessWorks Enabler now checks for proper product registration after the specified waiting period, and if registration validation fails it restarts Hawk Agent.

On the first attempt, it waits for the time configured in the CHECK_PRODUCT_REGISTRATION_WAITTIME parameter. On the second attempt, it waits for twice the previous wait time value. The multiple applied to the wait time increments up to the allowed number of retries.

Example: If the configured time is 10 sec. During the first attempt, it will wait for 10 sec. On the second attempt, it will wait for 20 sec.

If the validation of product registration is unsuccessful after reaching the maximum number of retries specified by CHECK_PRODUCT_REGISTRATION_NBRETRY, then the Application Component instance is shut down and restarted.

1.1.0 SFBW-180 BusinessWorks projects with UTF-8 encoding blocked TIBCO Administrator deployment of TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™ component applications.

Version Key Summary


Known Issues | 19

Known Issues

The table lists known issues for TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks for the respective releases.

Key Summary/Workaround

SFBW-1339 Summary: Application is redeployed if you execute two same, continuous deployments when RV is chosen as a transport.

Workaround: None

SFBW-1340 Summary: If you check the option "Do Not Redeploy Existing EAR File at Startup" in the basic configuration page, the status of application changes from stopped to running. This happens after you redeploy the same application to another machine using continuous deployment with setting NoStart=true.

Workaround: Clear "Do Not Redeploy Existing EAR File at Startup" option in the basic configuration page, and then restart component.

SFBW-1341 Summary: When you deploy application with FT-mode setting from a component or rest call, the value of FT related configurations hbInterval, activationInterval and preparationDelay are ignored.

Workaround: Update hbInterval, activationInterval and preparationDelay in TIBCO Administrator UI directly or deploy the application using the AppManage utility, with the deployConfig xml file specified in the Command line. Do this if hbInterval, activationInterval and preparationDelay are updated in deployConfig xml file.

SFBW-1337 Summary: The second BusinessWorks 6.x client component with an ear application attached, fails to startup when component scaling rule is set.

Workaround: None

SFBW-1241 Summary: When you start or stop a BusinessWorks 6.0 application with REST through REST call and provide a wrong version number (for example, "Version=2.0”), the REST call does not throw any exception and the application does not start or stop.

Workaround: None


20 | Release Notes

SFBW-1202 Summary: When the Managed Process for HawkAgent Enabled check box is selected during the basic configuration, killing the invoke process (engine-instance process) restarts the engine instance but does not kill the hawkagent_<domain_name> process.

Workaround: None

SFBW-1179 Summary: In an Enterprise with one TEA component, two BusinessWorks 6.x component are configured as a server and client, and you enable the creation of domain appspace, appnode, and set remote share folder as datastore. When a client BusinessWorks 6.x component is restarted with another engine instance, the file system of Domain, appspace, and appnode is not restored. It is restored at BW_HOME/domains of the previous engine instance.

Workaround: None

SFBW-1177 Summary: Even after a BusinessWorks 6.x component is restarted with another engine instance, the machine name and TIBCO_HOME path are not updated in TIBCO Enterprise Administrator.

Workaround: None

SFBW-1176 Summary: When the Status of TIBCO Services after TLM Restart option is set to Stopped and the engine instance running the Businessworks 5.x Component is killed, the status does not change to Stopped as expected.

Workaround: None

SFBW-1087 Summary: The BusinessWorks VirtualRouter cannot be accessed with TIBCO Rendezvous as transport.

Workaround: Disable the Rewriting Enabled option in VirtualRouter.

SFBW-990 Summary: The ForceDeploy parameter does not work on a component created in the BusinessWorks 6.x version. The update did not take effect even after updating the EAR application using the REST command.

Workaround: None



Known Issues | 21

SFBW-965 Summary: The stop REST command for TIBCO ActiveMatrix BusinessWorks 6.x version parses <archive-id> is same as <app name>. As the stop command does not output <archive-id>, users cannot use <archive-id> in the REST/CLI call.

For 5.x version, the stop REST command requires <archive-id> to stop the EAR application. For example, curl -u admin:admin -X POST -H "Accept:application/json" -H

"Content-Type:multipart/form-data" -v

"http://Broker_IP:Port/livecluster/rest/v1/sf/engines/{daemon-id}/{

engine-instance}/archives/{archive-name}/{archive-id}/stop"<archive-id> means "foo.par" (some file include in ear application file)

However, for 6.x version, the stop REST command stops the EAR application even if any value is passed for <archive-id>. For example, curl -u admin:admin -X POST -H "Accept:application/json" -H

"Content-Type:multipart/form-data" -F "Version=2.0" -v

"http://192.168.75.244:8080/livecluster/rest/v1/sf/engines/65140297

84038847951/0/archives/tibco.sample.application/sfbwtestissue123/st

op".

Workaround: None

SFBW-955 Summary: If you create a BusinessWorks component with the Register Enterprise server with TEA server option selected, set the BusinessWorks component dependent on the TEA component and publish it on a stack. Running the BusinessWorks component displays only one BusinessWorks agent, even if the BusinessWorks maximum instance number is set to 3.

Workaround: This issue is specific to TIBCO ActiveSpaces, so you can use Database/EMS as the Domain data persistence and communication transport layer in the enterprise mode.

SFCT-69 Summary: A prerelease version of TIBCO Silver Fabric Continuity, the newest Variable Provider, currently fails to accept certain ActiveMatrix BusinessWorks release 6.2 archives for upload.

Workaround: Components accept REST and CLI commands that can be used to specify variable providers.

SFBW-637 Summary: Runtime changes to engine allocation or threshold deactivation does not remove engines when the number of runtime instances were at a previously allowed minimum or maximum.

Workaround: Use TIBCO Administrator to remove engines. Compliance with the new allocation or threshold deactivation rule set resumes properly.



22 | Release Notes

SFBW-1033 Summary: While creating the Threshold Activation rule, if you choose the component statistics as the condition type, the statistics that are not supported by the current distribution appear incorrectly in the drop-down.

Workaround: None

SFBW-1104 Summary: When a TIBCO EMS Distribution is not loaded on the TIBCO Silver Fabric Broker, the Choose Optional Distributions page appears without the ability to select any Distribution because a supported TIBCO EMS Distribution has not been loaded. By design the Choose Optional Distributions drop-down menu only displays versions of TIBCO Enterprise Messaging Service distributions.

Workaround: Install a supported TIBCO EMS Distribution on the TIBCO Silver Fabric Broker.

SFBW-874 Summary: When the TIBCO Administrator component is running in FT mode it can resist changes to LDAP settings. Attempted changes to the TIBCO Administrator component LDAP settings by XML file can fail.

Workaround: If LDAP values are set in the TIBCO Silver Fabric Administrator Component UI, it can be updated successfully.

SFBW-767 Summary: When using Fast TLM Restart, the domain data changes its location, but the logFilePattern does not. Log file location for the domain data directory are not retained in the same directory when using Fast TLM Restart.

Workaround: Use a network accessible drive or some directory outside ENGINE_WORK_DIR, when you use Fast TLM restart, to preserve the domain data logging directory in the same location after restart.

SFBW-670 Summary: When a TLM is restarted with a BusinessWorks Application Service, that was uploaded from the Admin GUI, the BW service starts running even if the setting for state after TLM restart is set to "Stopped".

Workaround: None

SFBW-626 Summary: Sometimes, in the case of a large number of scaled archives, TIBCO Administrator may display an NPE in the Service instance screen and some BW processes may be orphaned.

Workaround: None



Known Issues | 23

SFBW-479 Summary: If no application is deployed on the TLM, undeploying the TLM BW component does not remove the machine from TIBCO Administrator. Machines are never deleted from the domain.

Workaround: To remove the machine from the TIBCO Administrator, use the remove machine feature which is available from TIBCO Administrator Manager machine management.

SFBW-639 Summary: In some cases scaling an archive instance will forces preexisting instances to be updated and restarted.

Workaround: None

SFBW-621 Summary: Scaling up a Component archive instance restarts the original archive instance.

Workaround:

1. Deploy archives using the AppManage utlity with FT mode disabled. Avoid using TIBCO Administrator for initial archive deployment,

or

2. Create two service instances of the archive in non-FT mode. Save it. Remove the second service instance created. Save and deploy the application.



24 | Release Notes


Date post:	24-Sep-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

TIBCO Silver Fabric Enabler for · TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks...

Documents