Changes in Functionality
The following functionality-related changes have been made in this release.
Release 6.7.0
| Administration | |
|---|---|
| Change in the default log level of the Jetty, Jersey, and MSSQL server (if applicable) logs. | Earlier Jetty, Jersey, and MSSQL server (if applicable) logs were available under the BWAgent log when started in Debug mode.
Now by default, only Warn level logs are present. You can change the log level of loggers present in the bwagent_logback.xml. |
| General | |
| The TIBCOBusinessStudio.ini file is present at the /studio/4.0/eclipse folder location on Mac operating system. |
Earlier the TIBCOBusinessStudio.ini file was present inside TIBCOBusinessStudio.app folder. Now from TIBCO ActiveMatrix BusinessWorks™ 6.7.0, the TIBCOBusinessStudio.ini file is present under eclipse folder. |
| Change in the deployment method name | The name of the deployment method is now changed from "Appspace" to "BW Appspace". |
| Change in a way to discover application server URL. | When
TIBCO ActiveMatrix BusinessWorks™ application with REST reference and with Mesh service client enabled was launched from
TIBCO Business Studio™ for BusinessWorks™, the application invoked a Mesh service from the application on an application server. The application server's URL was determined by fixed rules.
After a fully-qualified domain names (FQDN) service is provided, when the ActiveMatrix BusinessWorks™ application is launched, TIBCO Business Studio for BusinessWorks accesses the FQDNs and discovers the application server URL from it using a domain URL. |
| EGIT plug-in installation | There is no need to install EGIT plugin manually.
EGIT plug-in version 4.4.1 is now a part of TIBCO Business Studio for BusinessWorks itself. To verify the installation, navigate to . |
| Migration | |
| Addition of the module name as a prefix to the custom Xpath function | Earlier, after migration, the customxpathfunction jar-name did not have prefix of the module name in it and it migrated as a plain customxpathfunction jar for the custom Xpath functions.
Now, the CustomXpathFunction jar that is generated by the migration tool contains the name of the module as prefix before the customxpathfunction jar name. For example, in SampleApplication_CustomXpathFunction.jar, SampleApplication is the module name. |
Release 6.6.1
| Administration | |
|---|---|
| Option to set the FTL secondary realm server URL in the bwagent.ini file. | The FTL secondary URL is available in
bwagent.ini file after setting the only after setting the
ftlsecondary property to true in the
bwagent_ftl.json file.
For more information about changes, see the "Database with TIBCO FTL for bwagent" section in TIBCO ActiveMatrix BusinessWorks™ Administration. |
| General | |
| The bwdesign utility provides details of incorrect parameters. | Earlier the bwdesign utility did not display any errors details for failure.
Now details in form of incorrect parameters are displayed. |
| The Unused Resources tab shows only those folders with unused resources. | Earlier
Unused Resources tab displayed empty folders if there were no unused resources present in the module.
Now it shows only those folders that contain unused resources. |
| the Catch block which does not have a fault selected throws a validation error. | Earlier if no fault was provided for a
Catch block, no error or warning was displayed.
Now, a Catch block without a fault throws a validation error. |
| A new Exclude Unused Resources check box is added. | A new Exclude Unused Resources check box is added on the Create a new EAR wizard if user has enabled guided user experience. |
| The Cancel button terminates an application execution from the debugger. | When you click the Cancel button on the Launching BWThorRuntime dialog box while debugging an application, the application execution is terminated immediately. |
Release 6.6.0
| Administration | |
|---|---|
| The Process Details pane is set as the default page on the Process tab on the Application Level2 page of Admin UI. |
Earlier, when you select the Process tab on the Application Level 2 page on Admin UI, Process diagram was shown. Now, it is changed to Process Details pane. |
| Binding | |
| Axis2 TPCL upgrade | Axis2 TPCL upgraded to 1.7.9 version.
Use Apache Components for HTTP communication in SOAP. Apache Commons library is now no longer used, because it is deprecated. Older imported projects using Apache Commons, continue to display Apache Commons as the client option, but Apache Components is used as the client for executing the HTTP requests, because this library is obsolete. |
| Support for empty SOAP Header element. | Empty header element <soapenv:Header/> is passed in the SOAP envelope even if you don't configure the SOAP service with Headers. |
| General | |
| Jetty upgrade | The Jetty server version is updated to version 9.4.18.
After upgrade, the Jetty TPCL does not support TLS v1.0, v1.1 and SSL v3. The behavioral change has been implemented internally in the Jetty library, to resolve existing security vulnerabilities. |
| Preventing .EAR file generation, if it has Java-related errors | Earlier, if the project had Java related errors at design time, TIBCO Business Studio for BusinessWorks did not validate those errors while generating .EAR file. Now .EAR file is not generated, if it has Java-related errors. |
| The Include application modules check box from the Unused Resources view is now removed. | The
Include Application Modules check box is now removed from the
Unused Resources view.
Implicitly, application modules are included during unused resources calculation. When calculating unused resources for application modules, associated shared modules are also considered. |
| A few XPath functions are changed as per XML specifications | Earlier, some of the XPath functions such as
matches(),
deep-equal() were not returning results as per XML Specifications.
Now, they return exact expected results. |
| The Jetty access logs are present for the HTTP Connector shared resource | For TIBCO ActiveMatrix BusinessWorks applications that use REST service binding with the HTTP Connector resource, set the system property -Dbw.engine.http.jetty.accesslogs.enable to true in the VM arguments, and set the org.eclipse.jetty logger to DEBUG level in the logback.xml file to enable Jetty access logs. |
| The default value of SSL Protocol is changed to TLSv1.2 | Earlier, The default value of SSL Protocol was TLSv1.
Now, the default value of SSL Protocol for SSL Client or Server Configuration is changed to TLSv1.2 |
| LDAP Authentication Policy | Earlier, while using the LDAP Authentication policy, the
Test Configuration button overrode the result in the existing screen, so there was no way to identify if there was a change in the result behavior.
Now, a new Clear button is added, and the timestamp in the log is also displayed. |
| Palettes | |
| Ability to send message body as a part of request for DELETE REST Service method calls | Request message body was not allowed as the payload for DELETE HTTP requests invoking REST services.
This has been resolved for the Send HTTP Request activity with Jetty HTTP Client. It is compulsory to use the Jetty HTTP client library in the HTTP Client resource with Send HTTP Request activity for achieving this functionality. |
Release 6.5.1
Changes in Functionality due to JRE Upgrade
With the current release TIBCO ActiveMatrix BusinessWorks™ 6.5.1 , the Java Runtime Environment (JRE) is upgraded from JRE Update Release 144 to JRE Update Release 192 . For detailed list of changes made between these two release, see Java Development Kit 8 Update Release Notes at https://www.oracle.com. The following list shows most notable changes that can affect the product.