Changes in Functionality

Earlier the TIBCOBusinessStudio.ini file was present inside TIBCOBusinessStudio.app folder.

Now from TIBCO BusinessWorks™ Container Edition 6.7.0, the TIBCOBusinessStudio.ini file is present under eclipse folder.

After a fully-qualified domain names (FQDN) service is provided, when the TIBCO BusinessWorks Container Edition 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 version 4.4.1 is now a part of TIBCO Business Studio for BusinessWorks itself.

To verify the installation, navigate to Help > Installation Details > Plugins (Egit).

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.

Now, The default local of the Docker file for TIBCO BusinessWorks Container Edition is UTF-8.

Now, as per the precedence rule of Spring Cloud Config server, the application specific .properties files is given priority over the common application.properties files.

Adding -force parameter to the export command, you can export the .EAR even if there are validation errors or warnings present in project.

Ability to export properties to Consul with Authentication

For more information, see "Exporting Properties to Consul Server ", in the TIBCO BusinessWorks™ Container Edition Appllcation Development guide.

Now, the -m or --memory docker memory flag is used to limit the memory. The command is:

docker run --memory <other argument>.

This flag sets the maximum amount of memory the container can use. If this option is set, the minimum allowed value is 4 megabytes.

The -m flag also sets the heap parameters dynamically.

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.

Now it shows only those folders that contain unused resources.

Now details in form of incorrect parameters are displayed.

Now, a Catch block without a fault throws a validation error.

Now, the password type module properties values are visible as "***" format on TIBCO BusinessWorks Container EditionMonitoring UI.

Now, the values for the application properties after tokenizing are set to #//<applicationModule_name>//<property_name>#

Now, the password type values are obfuscated.

Now, as per the precedence rule of Spring Cloud Config server, the application specific .properties files is given priority over the common application.properties files.

• There is an addition of a parameter to the setedition command -f.

  The command is:

  bwdesign setedition -name <project name> -t bwcloud -data <directory path of project> -f

  With the -f command, you will not be prompted about setedition confirmation.

• There is an addition of a parameter to the export command -noprofile.

  Adding noprofile to the .EAR export command removes all the profiles from the .EAR file.

  The command is:

  export -ear <project name> -noprofile <filename>

• There is an addition of a parameter to the create command -f.

  Adding -f parameter to create the command checks if an application with the same name already exists. If yes, then bwdesign deletes the existing application and creates a new application with the same name.

  The command is:

  create -f application <application name> <comma separated module names>

• To generate or export the TIBCO BusinessWorks Container Edition properties file using the command-line interface (CLI), use the following command:

  export -pr <profile name> -t -alsomoduleproperty -includesystem <application name>.

Use Apache Components for HTTP communication in SOAP.

Now, to implement custom configuration management, register an OSGi service implementing com.tibco.bw.runtime.customProps.ExternalApplicationProperties interface.

Now, the default value of SSL Protocol for SSL Client or Server Configuration is changed to TLSv1.2

Now, import profile supports Properties to be imported as profile.

Now, a new Clear button is added, and the timestamp in the log is also displayed.

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.

Implicitly, application modules are included during unused resources calculation.

When calculating unused resources for application modules, associated shared modules are also considered.

Now, they return exact expected results.

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.

Now, the name of the property is shown with exception when the value of property is empty when using configuration management services.

The Subprocess span are listed under the callProcess span or the Invoke activity.

The Subprocess span previously were listed directly under the parent activity

Now, the subprocess is listed inside the main process span.

The Export Files after exporting the profile as a properties file now contains keys and value.

The export file after exporting the profile as a properties file previously used to contain only keys

Now, the properties file after exporting contains the key and value.

The default base OS is changed to debian:stretch-slim

The default base OS image from debian:jessie-slim is changed to debian:stretch-slim, because the exisiting debian:jessie-slim image is deprecated.

TIBCO BusinessWorks Container Edition uses non-root users for container execution.

TIBCO BusinessWorks Container Edition used root users during container execution. This has been changed to use non-root users by default.

The MAINTAINER tag is changed to LABEL tag in Dockerfile.

The deprecated MAINTAINER tag is now replaced with the LABEL tag in the Dockerfile.

You can get status messages for Invoke activity for REST Reference Binding.

To get the status message for the exception occured, set either */* , or use "text/html" in the Accept HTTPHeader field on the Input tab of the Invoke REST API activity.

The default Activation mode is set to Multiple AppNodes.

After migration, activation mode for processes and subprocesses was by default Single AppNode.

Now it is changed from Single AppNode to Multiple AppNodes.

Now, if there are issues detected with the database monitoring application it fails to start.

Now, the manifest.yml file generates only for Pivotal Cloud Foundry. The manifest.yml file can be manually generated with the Create manifest yml context menu option for cloud foundry application.