tibco silver fabric enabler for · sfbw-1213 the properties exposed for the do main...

Two-Second Adv

TIBCO Silver® Fabric Enabler for ActiveMatrix BusinessWorks™

Release NotesSoftware Release 3.1.0September 2015

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-2015 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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. It allows TIBCO ActiveMatrix BusinessWorks projects to be deployed 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-businessworks-3-1-0

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



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 3

• Deprecated and Removed Features, page 3

• Migration and Compatibility, page 3

• Closed Issues, page 4

• Known Issues, page 12



2 | Release Notes

New Features

The following new features have been added to version 3.1.0 of TIBCO Silver®

Fabric Enabler for ActiveMatrix BusinessWorks™.

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.


Changes in Functionality | 3

Changes in Functionality

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

Deprecated and Removed Features

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

Migration and Compatibility

Upgrade and migration instructions for Components created with previous releases of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorksare covered in the Users 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.


4 | Release Notes

Closed Issues

The table lists closed issues in version 3.1.0 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

Key Summary

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.

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.

SFBW-1217 In the tibcoadmin_DomainName.tra file, it was not possible to comment out or set to False the ‘tibcoadmin.monitor.hawkConsole.enabled’ variable.

SFBW-1213 The properties exposed for the Domain transport's Database connection pool management were missing.

To fine tune the database connection pool management, you can change the following properties by adding the runtime variable of the same name with the required value.

• Time (in milliseconds) for a connection request to wait before a time out occurs and an error is thrown:

tibcoadmin.database.waitTimeoutInterval (default value 30000 ms)

• Time (in milliseconds) after which the database is pinged to determine if it is still connected:

tibcoadmin.database.pingInterval (default value 300000 ms)

• Time (in milliseconds) between which the connection pool status is logged: tibcoadmin.database.logInterval (default value 900000 ms)

• Time (in milliseconds) after which a database connection tries to reconnect when it is found as disconnected:

tibcoadmin.database.reconnectInterval (default value 5000 ms)

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


Closed Issues | 5

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.

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.

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.

SFBW-1187 There were excessive number of inactive connections in database. To reduce the number of inactive connections, add the runtime variable tibcoadmin.database.expiryInterval and set the value (in milliseconds) corresponding of the cycle interval where inactive connections will be removed.

Without adding the runtime variable tibcoadmin.database.expiryInterval, the default value where inactive connections will be removed is 30 minutes (1800000 milliseconds).

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

Key Summary


6 | Release Notes

SFBW-1151 It was not possible to change the CiphersClass value in the HTTPS connector node of TIBCO Administrator before TIBCO Administrator starts.

To change the CiphersClass HTTPS connector, follow these steps:

1. In the TIBCO Administrator Component, add a runtime context variable named, HTTPS_CIPHER_CLASS, using the Administrator Component Wizard.

2. Set HTTPS_CIPHER_CLASS to one of the following accepted values:

— NoExportableCiphers

— AtLeast128Bit (default value when not set)— MoreThan128Bit

— AtLeast256Bit

3. If the value is set to AtLeast256Bit, you must upload the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy, which may be obtained from the Oracle Java website.

a. Create a zip file containing local_policy.jar and US_export_policy.jar.

b. Upload the ZIP file on the TIBCO Administrator Component using the page, Add/override/customize Container and Component-specific content files.

c. Set the relative path to "javapolicy".

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.

SFBW-1120 It was not possible to disable the Hawk Console UI in TIBCO Administrator.

If the runtime variable ENABLE_ADMIN_HAWK_CONSOLE is created and set to false, the Hawk Console UI in TIBCO Administrator get disabled.

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.

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

Key Summary


Closed Issues | 7

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.

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

SFBW-1050 Could not set ArchiveSetting 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

SFBW-1048 Empty folders under Application Management in TIBCO administrator GUI were deleted when BW component was shutdown

- If the runtime variable CLEANUP_EMPTY_DIRECTORY_ON_SHUTDOWN is created and set to false, empty directories will not be deleted on BW component shutdown.

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

Key Summary


8 | Release Notes

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

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

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

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

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

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

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

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

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

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

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

SFBW-887 The tibhawkhma process did not shutdown even after a BusinessWorks or TIBCO Administrator Component was stopped.

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

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

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

Key Summary


Closed Issues | 9

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

SFBW-838 If a BusinessWorks process definition is located under 2 (or more) sub-directories of the process archive no HTTP port be managed by TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

The fix will be effective when executing the deployment. 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.

SFBW-830 If a BusinessWorks process definition is located under 2 (or more) sub-directories of the process archive no HTTP port be managed by TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

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

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.

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%.

SFBW-791 Application TRA file under Fast TLM directory in Silver Fabric is incorrect after TLM restart.

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

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.

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.

Key Summary


10 | Release Notes

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

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

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

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.

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

SFBW-719 In certain situations, when connections with Hawk fail, multiple attempt to reconnect consumes files descriptors that are not released and causing the system to be out of resources.

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

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

SFBW-689 TLM does not always keep the same name when it is restarted.

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

SFBW-621 Scaling up a Component archive instance made the original archive instance restart.

SFBW-540 BW doesn't deploy from SFBW if we specify a configuration for the service instance in the config.xml file

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

Key Summary


Closed Issues | 11

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.

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.

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

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 will restart Hawk Agent.

It will wait CHECK_PRODUCT_REGISTRATION_WAITTIME seconds during the first attempt, then twice times the previous value of wait time on the second attempt incrementing the multiple applied to the wait time up to the allowed number of retries.

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

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.

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

Key Summary


12 | Release Notes

Known Issues

The table lists known issues in version 3.1.0 of TIBCO Silver Fabric Enabler for ActiveMatrix BusinessWorks.

Key Summary/Workaround

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

SFBW-1202 Summary: When the Managed Process for HawkAgent Enabled checkbox 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 creation of domain appspace, appnode, and set remote share folder as datastore. When a client BusinessWorks 6.x component is restarted to another engine instance, the file system of Domain, appspace, appnode is not restored. It is restored at BW_HOME/domains of previous engine instance.

Workaround: None

SFBW-1177 Summary: Even after a BusinessWorks 6.x component is restarted with other 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


Known Issues | 13

SFBW-1104 Summary: When a TIBCO EMS Distribution is not loaded on the TIBCO Silver Fabric Broker the Choose Optional Distributions page will appear 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-1087 Summary: The BusinessWorks VirtualRouter cannot be accessed with TIBCO Rendezvous as transport.

Workaround: Disable the Rewriting Enabled option in VirtualRouter.

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

Workaround: None

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

Workaround: None



14 | Release Notes

SFBW-965 Summary: The stop REST command for TIBCO ActiveMatrix BusinessWorks 6.x version parses <archive-id> 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 needs <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 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/651402

9784038847951/0/archives/tibco.sample.application/sfbwtestissue12

3/stop".

Workaround: None

SFBW-955 Summary: If you create a BusinessWorks component with the Register Enterprise server with TEA server option selected. Then, set the BusinessWorks component dependent on 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.

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 then 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: When using Fast TLM Restart using a network accessible drive or some directory outside of the ENGINE_WORK_DIR may preserve the domain data logging directory in the same location after restart.



Known Issues | 15

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

Workaround: None

SFBW-637 Summary: Runtime changes to engine allocation or threshold deactivation do 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 will resume properly.

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

Workaround: None

SFBW-479 Summary: If there is no application 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.

SFCT-69 Summary: A pre-release 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 which can be used to specify variable providers.



16 | Release Notes


tibco silver fabric enabler for · sfbw-1213 the properties exposed for the do main...

Documents