A new
Avoid generating empty element for optional-nil element mapping to optional element check box is added.
|
The
Avoid generating empty element for optional-nil element mapping to optional element check box is added in the
Mapper section of the
Preferences dialog box.
Select the check box to forbid empty elements in opt-nil element to optional element mapping.
After selecting or clearing the check box, clean the project for the changes to take effect.
|
The
Ignore Additional JSON Fields field is added in the REST Service Binding and REST Reference Binding.
|
TheIgnore Additional JSON Fields field is added to the
Request tab of the
Operation Details pane of the REST Service Binding and
Response tab of the
Operation Details pane of the REST Reference Binding.
Select the check box to ignore additional fields that are received due to the changes in the external payload when processing the schema.
By default this check box is not selected.
|
OpenTracing
|
Support is added for OpenTracing.
For more information, see "OpenTracing" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Blocking Queue Size field added to REST Service Binding.
|
The
Blocking Queue Size field is added in the
Advanced Configuration section of the REST Service Binding.
This field sets the number of threads to be created for a REST service.
By default, it is set to the value, Integer.MAX_VALUE.
For more information, see "REST Service Binding" in the
TIBCO ActiveMatrix BusinessWorks™ REST Implementation guide.
|
A new
Check unsynchronized runtime binding check box is added.
|
The
Check unsynchronized runtime binding check box is added in the
Mapper option of the
Preferences dialog box.
Select the check box to detect the difference in the stored runtime XSLT and the computed runtime XSLT. After selecting or clearing the check box, clean the project for the changes to take effect.
|
Ability to navigate to an activity in the debug view.
|
When there are complex processes in a project, you can check the debug status of an activity by double clicking the activity in the process diagram. This action highlights the corresponding entry in the
BusinessWorks Jobs tab.
|
The MTOM attachment style now supports SOAP 1.1 and SOAP 1.2 specifications.
|
The Message Transmission Optimization Mechanism (MTOM) attachment style can now be configured with both the SOAP versions, 1.1 and 1.2.
|
A new radio button
XPath Version is added in the
XPath Builder dialog box.
|
The
XPath Version radio button is added in the
XPath Builder dialog box for
Group activity and transition only. The following are the two options provided:
By default, the option, 2.0 is selected.
It validates the specified XPath expression depending upon the selected version.
|
A new
Hide Server Implementation check box is added.
|
The
Hide Server Implementation check box is added to the
HTTP Connector shared resource. When selected, the
Powered By Jetty string does not appear in the error response.
|
Application Logging
|
Support for Application level logging.
For more information about configuring Application logging using the
Log activity, see "Log" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
For more information about configuring Application logging using the
logback.xml file, see "Application Logging" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Two new fields,
SOAP Actor and
Protect Token are added to the
Subject Provider shared resource.
|
The
SOAP Actor field can be used to provide the SOAP actor attribute to address the SOAP header element to a specific endpoint.
When the
Protect Token check box is selected, it enables signing of the Binary Security Token.
For more information, see "Subject Provider" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Multiple AppNodes activation mode of the processes for the FTGroup persistence mode.
|
A new bwengine property
bw.engine.ftgroup.lbmode is added to support
Multiple AppNodes activation mode of the processes for the FTGroup persistence mode.
For more information about this bwengine property, see "Configuring the Engine for FTGroup Persistence Mode" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
The
Expose Security Context check box is added to the SOAP Service Binding.
|
The
Expose Security Context check box is added to the SOAP Service Binding. Select the check box to expose security context in the message header.
After selecting this option, you can map information from the inbound security context to the
SecurityContext element of the Input Context.
|
Support has been added to use MariaDB as a database for the engine.
|
Support is added to use MariaDB as a database for the engine.
For more information, see "Configuring Database for the Engine" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Retrieve the complete version of an application.
|
The Application Full Version module property is added to the list of predefined module properties on the
Constants tab.
This module property returns a three-digit application version in the format <major>.<minor>.<micro>
|
The
Quick Fix option for extra parameter binding.
|
The
Quick Fix option is now available when an extra parameter binding is detected after projects are imported to the workspace.
Use this option to remove all the extra parameter binding related design time errors.
|
Multiple force kill commands can now be triggered for AppNodes from the Admin CLI and Admin UI.
|
You can now trigger multiple force kill commands for AppNodes one after the other and the most recent force shut down command takes precedence over the previous commands.
|
Application portability between
TIBCO ActiveMatrix BusinessWorks™ 6.x, TIBCO BusinessWorks™ Container Edition and TIBCO Cloud™ Integration
|
Now you can deploy TIBCO ActiveMatrix BusinessWorks™ 6.x , TIBCO BusinessWorks™ Container Edition and TIBCO Cloud™ Integration EAR's to any of these three environments.
The bwdesign utility now generates the
manifest.json file from the EAR to push TIBCO ActiveMatrix BusinessWorks™ 6.x or TIBCO BusinessWorks™ Container Edition, EAR files to TIBCO Cloud™ Integration.
For more information, see "Generating the manifest.json File Using the bwdesign Utility" in the
TIBCO ActiveMatrix BusinessWorks™ Application Development guide.
|
Implementation of OSGi commands from Admin CLI
|
OSGi commands can be executed from the Admin CLI.
|
Support has been added to populate custom HTTP headers in the error response of the REST Service Binding.
|
When you select the
Use HTTP Header check box, you can add custom HTTP fault headers defined in the
Response Status tab in the REST Service Binding and REST Reference Binding.
|
Ability to elect the leader AppNode in FTGroup scenarios
|
You can now elect the leader AppNode in FTGroup by configuring two new bwengine properties,
bw.engine.node.weight and
bw.engine.use.weighted.node.
For more information, see "Engine Properties" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Coercion now supports XML Attributes
|
You can coerce input data with Attribute.
For more information, see "Coercing a Specific Data Type" in the
TIBCO ActiveMatrix BusinessWorks™ Application Development guide.
|
The WSDL inline schema from shared module can now be referred.
|
The WSDL inline schema from shared module can now be referred to the application module.
|
Process Monitoring
|
Using the process monitoring feature you can observe and check the status of process instances from the Admin UI.
For more information, see "Enabling process Monitoring" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Password encryption for FTL passwords in
bwagent.ini file
|
FTL passwords can now be provided as obfuscated passwords using bwadmin.
|
Support has been added to deploy and start multiple versions of the same application in the same AppSpace.
|
Same applications with different versions can now be deployed to the same AppSpace.
|
Ability to show heap memory in Admin UI
|
You can now view the heap memory usage in the Admin UI on the AppNode Level 1 page in the graph view.
For more information, see "Viewing AppNode Statuses" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
MariaDB database support added for bwagent with TIBCO EMS and TIBCO FTL
|
The bwagent can be configured to use the MariaDB database with TIBCO Enterprise Message Service (EMS) and TIBCO FTL for persistence and transport.
For more information, see "Configuring bwagent for MariaDB and TIBCO EMS" and "Configuring bwagent for MariaDB and TIBCO FTL" in the
TIBCO ActiveMatrix BusinessWorks™ Administration guide.
|
Pagination support in Admin UI
|
Admin UI now supports pagination for Application Archives, AppSpaces, Applications and AppNodes Level 1 Pages to improve page loading performance.
|
Authorization to BWAgent REST API by roles can now be enabled with LDAP or file based authentication.
|
Authorization to BWAgent REST API by roles can now be enabled with LDAP or file based authentication. BWAgent REST API supports the admin, operator, and user roles for authorization.
To enable authorization, set the property
bw.agent.http.authorization
to true in the
bwagent.ini file.
Users assigned the admin role are given full permissions including create, read, update, delete, and lifecycle. The operator role has the read and lifecycle (start, stop) permissions. The user role has the read only permission.
Note: Authorization does not work for LDAP Custom Group or Role. To use the LDAP custom group or role along with existing groups or roles, use the property
customRoleForLDAP in the
jaas.login.conf file
.
|
REST API to return partial response
|
A new feature has been added to BWAgent REST API that returns only the selected fields instead of the full response based on the query parameters.
Example 1: To check the status of an Application, the REST API GET URL would be -
http://localhost:8079/bw/v1/domains/<DomainName>/appspaces/<AppspaceName>/applications/
<ApplicationName>/<ApplicationVersion>?fields=state
The url will return the following response:
{"state":"Running"}
Note: Use comma separated fields after the question mark (?) with fields=keyword in the request query. Spaces are not permitted.
Example 2: To get AppSpace details
Normal query - http://localhost:8079/bw/v1/domains/<DomainName>/appspaces/<AppSpaceName>
It will give the total payload(all fields).
Select Query - http://localhost:8079/bw/v1/domains/<DomainName>/appspaces/<AppSpaceName>
?select=name,status – It will retrieve only 2 fields.
Sub-field - http://localhost:8079/bw/v1/domains/<DomainName>/appspaces/<AppSpaceName>
?select=appSpaceConfigRefs.href – It will fetch href of appSpaceConfigRefs.
Note: The query will return an empty response if the selected field is a collection.
|
Dynamically passing application specific properties without restarting the AppNode
|
You can now dynamically set job tuning properties like Flow Limit and Page Threshold for an application from the Admin UI without restarting the AppNode.
|
TIBCO Business Studio for BusinessWorks™
|
TIBCO Business Studio for BusinessWorks™ now supports developing and debugging applications for
ActiveMatrix BusinessWorks™ 6.x, TIBCO BusinessWorks™ Container Edition, and TIBCO Cloud™ Integration.
For more information, see "Reconfiguring Deployment Target" in the
TIBCO ActiveMatrix BusinessWorks™ Application Development guide.
|
Generate the
manifest.json file for TIBCO Cloud™ Integration
|
The bwdesign utility now generates the
manifest.json file from the EAR. For more information, see "Generating the manifest.json File Using the bwdesign Utility" in the
TIBCO ActiveMatrix BusinessWorks™ Application Development guide.
|
A new preference option
Automatically open process files during debugger session has been added in the
Run/Debug wizard.
|
A new preference option,
Automatically open process files during debugger session has been added in the
Run/Debug wizard.
This option is enabled by default, and opens all the executed processes while running an application in the debug mode.
You can now disable the
Automatically open process files during debugger session check box by clearing it, and the processes within the application do not open when the application is run in the debug mode.
|
Analyzing Dependencies and References
|
The Dependency Visualizer feature provides graphical representation of all the direct and indirect dependencies and references for an application. You can use this option to view the hierarchy of processes, shared resources, WSDL files, and XSD files.
For more information, see "Analyzing Dependencies and References" in the
TIBCO ActiveMatrix BusinessWorks™ Application Development guide.
|
Refactoring support has been added to reference a Shared Variable in a Shared Module from an application module.
|
Refactoring support has been added to reference a Shared Variable in a Shared Module from an application module.
A new option,
Update Shared Variable from Shared Module Navigate has been added to the
Shared Variable section in the
Module Descriptor editor.
Select the required option and from the
Refactoring wizard, select the shared module where the reference to the shared variable needs to be updated.
|
Support has been added to turn the
Build Automatically option ON or OFF from the
config.ini file.
|
In the
{TIBCO_HOME}/studio/{version}/eclipse/configuration/config.ini file you can now add the
bw.autobuild property.
When the
bw.autobuild property value is
true, auto building of the project builders is turned on during starting of
TIBCO Business Studio™ for BusinessWorks™.
When the
bw.autobuild property value is
true, the
option is selected.
When the
bw.autobuild property value is
false, the
option is clear.
|
Support has been added to use a module property for the
Default Confidentiality field.
|
The
Default Confidentiality field in the
Security pane of the
HTTP Client shared resource now supports a module property and a literal value.
For more information see "Default Confidentiality" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
A new check box
Fill Standard Headers has been added.
|
A new check box,
Fill Standard Headers has been added in the
Advanced tab of the
HTTP Receiver and
Wait for HTTP Request activities.
When selected, additional headers such as
Authorization,
User-agent, and
Host are populated in Dynamic Headers in the output of these activities.
For more information, see "HTTP Receiver" and "Wait for HTTP Request" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
A new check box
Override S/A DataType Schema has been added.
|
A new check box,
Override S/A DataType Schema has been added in the
Advanced tab of
JDBC Call Procedure activity for object and collection use cases. When selected, the check box replaces the schema name used with the object type by a newly provided schema in the
Schema tab of the
JDBC Call Procedure activity at runtime.
For more information, see "JDBC Call Procedure" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support has been added for the OPTIONS method.
|
ActiveMatrix BusinessWorks™ now supports the OPTIONS method in the REST Service Binding and REST Reference Binding.
|
Support for custom JNDI properties.
|
Support has been added for custom JNDI properties in the JNDI Configuration shared resource.
A new JNDI provider option,
TIBCO Custom JMS has been added in the JNDI Configuration shared resource.
For more information, see "JNDI Configuration" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support for PostgreSQL function.
|
Support has been added in the
JDBC Call Procedure activity for PostgreSQL function to return a resultset.
|
A new check box
Write Non Mime Content is added.
|
A new check box,
Write Non Mime Content in
Advanced tab of the
Send HTTP Request activity is displayed on selecting the
Write To File option.
When selected, non-MIME attachments or data downloaded from a server can be saved to the disk.
The filePath element is added in the output schema that contains the path of the file where the attachment is stored.
For more information, see " Send HTTP Request" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support is added for the HTTP PATCH method in the
Send HTTP Request activity and
HTTP Receiver activity for the Apache Components Client.
|
The
PostData field in the
Input tab of the
Send HTTP Request
activity is used to provide the input for the HTTP PATCH method.
|
Support is added for the PATCH method in the
Disable HTTP Methods field in the
HTTP Connector shared resource.
|
The PATCH method is added to the list of HTTP methods in the
Disable HTTP Methods field. The method can be optionally disabled at the
HTTP Connector shared resource. An error
405 Method not Allowed is displayed when a request is sent with a disabled method.
|
A new check box
Provide Client Resource has been added.
|
A new check box,
Provide Client Resource has been added in the
Advanced tab of the
Send HTTP Request activity.
Select this check box to dynamically select a different
HTTP Client resource. When you select this check box,
Host and
Port fields are replaced by the
ClientResource field in the
Input tab.
For more information, see "Send HTTP Request" in
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
A new activity
Transform JSON has been added.
|
A new activity
Transform JSON has been added in the
REST/JSON Palette.
You can convert JSON data in one format to the other JSON format using the Jolt specification.
For more information about the fields of the activity, see "Transform JSON" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide
|
Support is added for Oracle database 12c Release 2.
|
TIBCO ActiveMatrix BusinessWorks™ now supports Oracle database 12c Release 2.
|
A new field
Connection Idle Timeout has been added.
|
A new field
Connection Idle Timeout has been added in the JDBC Driver section of the JDBC Connection shared resource.
For more information, see "JDBC Connection" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support is added for custom JMS driver
|
Support has been added for the TIBCO Custom JMS driver in the
JNDI Connection section of the
JNDI Configuration shared resource.
For more information, see "JNDI Configuration" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
MariaDB is now supported in JDBC Palette
|
MariaDB can now be used for the
JDBC Connection shared resource, and activities from the JDBC palette.
|
Support for module property has been added in the
Confidentiality check box of the
HTTP Client shared resource.
|
You can provide module property along with the standard behavior of
Confidentiality check box in the
HTTP Client shared resource.
For more information, see "HTTP Client" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support is added for the Shared Subscription feature of JMS 2.0 specification.
|
A new check box,
Shared Subscription is added on the
General tab of the
JMS Receive Message activity.
For more information, see "JMS Receive Message" in the
TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.
|
Support has been added to set the constructor arguments for the
Java Global Instance shared resource using module properties.
|
You can set the value of a constructor parameter by using module properties in the
Java Global Instance shared resource.
|