+ All Categories
Home > Documents > TIBCO ActiveMatrix BusinessWorks Release Notes · Upgrading from ActiveMatrix BusinessWorks™...

TIBCO ActiveMatrix BusinessWorks Release Notes · Upgrading from ActiveMatrix BusinessWorks™...

Date post: 26-Dec-2019
Category:
Upload: others
View: 18 times
Download: 0 times
Share this document with a friend
105
TIBCO ActiveMatrix BusinessWorks Release Notes Software Release 6.4.0 May 2017 Two-Second Advantage ®
Transcript

TIBCO ActiveMatrix BusinessWorks™ ReleaseNotesSoftware Release 6.4.0May 2017

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Enterprise Message Service,TIBCO Business Studio, TIBCO Enterprise Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent,TIBCO Designer, and Two-Second Advantage are either registered trademarks or trademarks of TIBCOSoftware Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE 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 ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2001-2017 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Contents

Setting Context Sensitive Help Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

3

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Setting Context Sensitive Help Preferences

This procedure explains how to change your help preferences in TIBCO Business Studio™ to accesscontext sensitive help from a local directory or from an internal web server, if you have placed thedocuments under it.

Prerequisites

Before setting context help preferences you must download the documentation for your product fromthe FTP site provided by your TIBCO representative. Copy the documentation zip file to a localdirectory, or to an internal web server and then unzip the file.

Procedure

1. In TIBCO Business Studio, click Window > Preferences. On Mac OS X, click TIBCO BusinessStudio > Preferences.

2. In the Preferences dialog, click BusinessWorks > Help.

3. Select Custom Location and then click Browse to select the html directory where you unzipped thedocumentation, or provide the URL to the html directory on your internal web server.

4. Click Apply and then click OK.

4

TIBCO ActiveMatrix BusinessWorks™ Release Notes

New Features

The following are the new features available in this release of TIBCO ActiveMatrix BusinessWorks™.

Release 6.4.0

Common Features

New option added to resolve XSLT Out of Syncerror.

After migrating a project, the Quick Fix optioncan be used to resolve XSLT out of Sync errors inthe project. Refer to Using the Quick Fix Optionto Resolve XSLT out of Sync Errors in theMigration guide for additional details.

New propertybw.agent.technology.dbems.ems.reconnecti

on.interval added to bwagent.ini file.

Set thebw.agent.technology.dbems.ems.reconnecti

on.interval property to specify in millisecondshow often the bwagent tries to re-connect withthe EMS server if connection is lost. The defaulttime interval is 10 seconds, or 10000milliseconds. Refer to Database with TIBCOEnterprise Message Service Configuration forbwagent in the Administration guide foradditional details.

Ability to select elements from a schema locatedwithin a shared module when configuring theIteration Element field of Iterate group.

Elements from schemas located within a sharedmodule can now be selected when configuringthe Iteration Element field of an Iterate group.

New commands in bwdesign utility enablesshared modules to be exported as a binaryshared modules.

Use the export -binary <shared_module>, orthe export -bin <shared_module>, commandto export a shared module as a binary sharedmodule from the command line .Refer to Exporting a Shared Module as a Binary SharedModule in the Application Development guide foradditional details.

Support to force shut down an AppNode fromAdmin UI and the command line interface.

A new feature has been implemented to supportforce shut down of the AppNode. From thecommand line, a new argument -timeout or -thas been introduced with the Stop command.With this argument you can specify the timeoutin minutes, after which the AppNode shutsdown forcefully, irrespective of the state of theAppNode or the applications.From the AdminUI, click the Stop icon and specify the wait timein minutes. Refer to Force Shutting Down anAppNode in the Administration guide foradditional details.

Java Starter process now accepts moduleproperty for init input parameter.

Support has been added to accept moduleproperties for init input parameter in a JavaStarter process.

5

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

New module property, Process Stack added toTIBCO BW Predefined Module Properties .

A new option, Process Stack, has been added tothe TIBCO BW Predefined Module Propertiessection of the Constants tab in the input mapper.This module property returns the entire processstack,

including the nested subprocesses, and theparent processFor example, main.Process/SubProcess1->sm.SubProcess1/SubProcess2-

>sm1.SubProcess2. Refer to XPath Expresion inthe Application Development guide for additionaldetails.

Engine Command Activity The new Engine Command activity allows youto retrieve statistics and information aboutprocess definitions, process instances, andactivities for the application and the AppNodethat executes the command. Refer to EngineCommand in the Bindings and Palette Referenceguide for additional details.

Support for Call Process activity in local JDBCor JMS transactions.

If a Call Process activity is used within a localtransaction group, the direct subprocesses thatthe Call Process activity calls are also includedin the local transaction.

Referencing multiple XSDs with the samenamespace.

Multiple XSDs with the same target namespacecan be referenced from a Shared Module in anApplication Module, as long as the documentsdo not have conflicting Qnames. and the sameroot element does not exist in both the XSDs.

Also, the referenced XSDs must include an XSDin a schema file from a Shared Module, and theShared Module must use elements in the Iterategroup.

New column Deployed To added to theApplications Archive page on the Admin UI.

A new column Deployed To has been added tothe Applications Archive page, and displays thenumber of AppSpaces in which the archive hasbeen deployed. Click on the number in theDeployed To column and the names of theAppSpaces where the EAR file has beendeployed is displayed.

'XSD includes' is now supported across sharedmodules.

XSD includes is now supported across , andmultiple documents can contain the same targetnamespace in a shared module. However, theQnames should not collide.

6

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

Element ElapsedTimeSinceStarted added tothe command GetProcessInstanceInfo.

A new element ElapsedTimeSinceStarted hasbeen added in the Output schema of theGetProcessInstanceInfo command of theEngine Command activity. TheElapsedTimeSinceStarted element displaysthe elapsed clock time (in milliseconds) since theprocess instance started.

Connecting to AppNodes using the SSH client. Uncomment the properties in the AppNode'sconfig.ini file and provide an available portfor osgi.console.ssh and the host name forosgi.console. Restart the AppNode andconnect to the hostname and port of theAppNode.

Uploading and Downloading logback files fromthe Admin UI

Support has been added to upload or downloadlogbck files from the Admin UI.

To upload or download a logback file, click theUpload or Download link, from the AppNodeLevel 2 page.

Unit Testing You can now take the Test-Driven Design(TDD)approach for developing ActiveMatrixBusinessWorks applications with the new UnitTesting feature. You can define assertions forindividual activities in the BusinessWorksProcess, test the assertions through the debuggerand see the test results in the Debug perpsective.Refer to Unit Testing in the ApplicationDevelopment guide.

Upgrading from ActiveMatrix BusinessWorks™6.3.x to ActiveMatrix BusinessWorks 6.4.x.

Support added to upgrade from ActiveMatrixBusinessWorks™ 6.3.x to ActiveMatrixBusinessWorks 6.4.x in the same TIBCO home.

If the DB drivers and EMS drivers are present inthe previous version of the installation, thedrivers will not need to be re-installed. Refer to Upgrading to ActiveMatrix BusinessWorks™6.4.0 in Installation guide for additional details.

Design Time

Renaming resource packages in TIBCO BusinessStudio.

Packages in the Resources folder can now berenamed. Shared resource references for eachresource under the package can also berenamed.The SOAP and REST bindings thatreference the renamed resource can also berenamed.

7

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design Time

The Request Entity Processing field on theREST Reference Binding can be configured touse Chunked or Buffered.

When configuring the Request EntityProcessing field, you can choose one of thefollowing options:

● BUFFERED: The request entity is buffered inmemory to determine the content length thatis sent as a Content-Length header in therequest.

● CHUNKED: The entity is sent as chunkedencoded. The Content-Length is specified,and the entity is streamed. The Transfer-Encoding header is set to Chunked.

The default value is Chunked.

Refer to REST Reference Binding in the Bindingand Palettes Reference guide for additional details.

Resources and policies can be refactored. This feature allows resources and policies in anapplication to be renamed and moved to adifferent location in the project. References to themodified resources and policies are also updatedwhen these resources are refactored.

Refer to Refactoring a Shared Resource or PolicyPackage in the Application Development guide foradditional details.

Shared module properties are now shareable. Module properties from a Shared Module arenow accessible in an Application Module. Youcan define module properties in a SharedModule and access them in the ApplicationModule resources.

Referencing schema elements from sharedmodules for the Iterate group.

You can now select elements from a schemalocated in a shared module for an Iterate group.

Support added for the API Modelerfunctionality.

The API Explorer view is now enabled in TIBCOBusiness Studio by default to allow customers toaccess the API Modeler functionality in TIBCOCloud Integration to model their APIs andimplement them. The cloud URL, the oauth2URL, the username and password areconfigurable in the Settings dialog of the APIExplorer view.

The Ignore mustUnderstand check box has beenadded to SOAP Reference Binding.

A new check box, Ignore mustUnderstand hasbeen added to SOAP Reference binding todisable all SOAP Headers if the value of themustUnderstand attribute is set to true.

8

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design Time

New check box Enforce BW Service Responseadded to REST Service bindings.

A new check box Enforce BW Service Responsehas been added to the REST Service bindings,and this check box allows users to set strictresponse preferences for BW Service Response.

Migration

Migrating the TIBCO ActiveMatrixBusinessWorks™ 5.x Design Time Library to aTIBCO ActiveMatrix BusinessWorks™ 6.xShared Modules.

ActiveMatrix BusinessWorks 5.x design timelibrary source projects can be migrated asActiveMatrix BusinessWorks 6.x sharedmodules.

Using the ActiveMatrix BusinessWorksframework, you can migrate ActiveMatrixBusinessWorks 5.x projects where the processuses design time libraries to define the resources,subprocesses, and so on. Refer to MigratingDesign Time Libraries (DTL) as Shared Modulesin the Migration guide for additional details.

Command line Migration support to migratedesign time libraries, custom XPath functionsand selective migration.

The ActiveMatrix BusinessWorks6.x migrationconfiguration file, bw6migration.propertiesfile is a template file that contains configurableproperties to migrate design time libraries,custom XPath functions, and migrating selectedprocesses using the command line. Refer to Migrating Projects Using Command Line in theMigration guide for additional details.

Application resources residing outside of defaultpackage folders in shared modules are fullyexported during migration.

When migrating shared modules, applicationresources residing outside of the default packagefolders are fully exported and available to theapplication after migration.

Shared Resource and Processes outside of thedefault folders are also organized under twonew sections after the shared module ismigrated. To view these new sections, expandthe Module Descriptors folder under theapplication package, and select the Providesfolder. The top section, "Special Folder LevelPackages", displays all Shared Resources andprocesses contained in the default Resource andProcess folders in the Shared Module. Thesecond section, "Project Level packages",displays all Shared Resources and processes thatare located outside of the default folders in theShared Module.

9

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.3.5

Common Features

Logging error messages for run time errors inthe JDBC shared resource

When exceptions occur during run time awarning or error message to know the root causeis logged.

HTTP PATCH method is now supported inREST Service and Reference Bindings

PATCH method is now supported in RESTService and Reference Bindings. Refer to RESTService Binding and the REST Reference Bindingin the REST Implementation in TIBCOActiveMatrix BusinessWorks™ guide foradditional details.

The Reset Variables field is now available forgroups with conditions.

The Reset Variables field is now available forgroups with conditions. While configuring theIterate, While, For Each, and Repeat groupactivities, set this field to reset variables duringeach iteration. Refer to following topics in theBindings and Palettes Reference guide foradditional details:

● Iterate

● While

● For Each

● Repeat

A new check box, Single XPATH FunctionGroup Project, is offered in the ProjectMigration Wizard.

A new option is offered in the Project MigrationWizard that enables users to create a single plug-in project for all JAVA XPath sources inside anActiveMatrix Business Works™ 5.x project whenmigrating the project. The Single XPATHFunction Group Project check box is selected bydefault. If this check box has not been selected, aindividual plug-in project is created for eachJAVA XPath source file. Refer to the topic Migrating Projects Using TIBCO Business Studioin the Migration guide for additional details.

10

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

New option provided in the Project MigrationWizard to add third party jars to the XPATHFunction Project.

The migration wizard has been updated with theBrowse field to browse for the third party JARSfolder. All the JAR files in the folder are nowcopied to the lib folder of the Custom XPATHFunction Group Plugin Project after migration,and are added to the plugin class path. Refer tothe topic Migrating Projects Using TIBCOBusiness Studio in the Migration guide foradditional details.

If ActiveMatrix BusinessWorks™ 5.x.custom functions containing thereturn type void are migrated, thefunction is migrated without a returntype statement.

Ability to start and stop components onindividual application instances from the AdminUI.

Users can start and stop components onindividual application instances from the AdminUI. Refer to the Starting a component in anApplication topic and the Stopping a componentin an Application topic in the Administrationguide for additional details.

Design Time

A new check box, Interpret invalid XML chars,has been added to the Advanced tab in theJDBC Call Procedure activity.

A new check box, Interpret invalid XML chars,has been added to the Advanced tab in theJDBC Call Procedure activity.

Call procedure execution will fail if this checkbox is not selected, and invalid characters aresent from the database to TIBCO BusinessStudio™. If invalid characters are sent, and thecheck box Interpret invalid XML chars isselected, the process is executed successfully.

Release 6.3.4

Common Features

REST Reference and Service Bindings nowsupport plain text, as a request or responsemessage format.

REST Reference and Service Bindings nowsupport plain text as a message format forrequests and responses for REST operations(POST, GET, PUT, DELETE). Messages will bereturned as a simple string.

11

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

Elements from different namespaces can now beused in the REST Service Binding.

Elements from different namespaces can now beused in REST Service Binding.

Schemas cannot have cyclicdependencies with other schemas, andcomplex elements cannot have twochild members with the same localname, but from different namespaces.

Query parameters now support multiple values. The REST Binding supports defining queryparameters with repeating cardinality.

Support for anonymous arrays in JSONresponses.

Support for processing and returninganonymous arrays in a JSON response has beenadded to the Parse JSON and Render JSONactivities.

When selecting the method to use when parsingdata, select the Anonymous Array option. Thisoption specifies the input JSON style for theseactivities, and allows the activity to accept aJSON array without the parent element, wherethe root element has exactly one child of the typeArray.

BIGINT is a supported datatype for the inputand output parameters on the JDBC CallProcedure activity.

The JDBC Call Procedure activity can call astored procedure with input and outputparameters of BIGINT type in MSSQL Server2008+, for both native and data direct drivers.

Add query parameters for individual RESToperations.

ActiveMatrix BusinessWorks™ now supportsadding query parameters for individual RESToperations.

The Receive Notification activity and the OnNotification Timeout are offered as processstarter activities in the General Activities palette.

The On Notification Timeout activity specifies aprocess to execute, when a timeout is reached forstoring notification data for a Notify activity.

The Receive Notification activity starts a processwhen another process executes a Notify activitywith a matching key and a shared configurationresource.

Support for Kerberos (SPNEGO) Authenticationfor outbound HTTP requests.

The HTTP Client shared resource now supportsKerberos Authentication for applications usingHTTP and REST.

12

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

Additional elements have been added to theCatch All fault.

Two new elements are available for the Catch Allfault:

● FullClass: Contains the full package that thefault class resides.

● Class: Specifies the class name of theexception.

Design Time

Importing and Exporting Application Profiles This feature allows profile values to be exportedand imported to and from an application inTIBCO Business Studio™. Using this feature youcan import or export preference settings fromone workspace into another.

Binary Shared Modules Binary shared modules can be created to hidethe implementation details of a shared modulefrom the users of the module.

Composite XPath Expressions Added checks for validating composite XPathExpression for newly migrated ActiveMatrixBusinessWorks 6.x using the Migrate Projectsmenu option.

Password type application properties can nowreference password type module properties.

Password type application properties can nowreference password type module properties.

Runtime Administration Framework

FTGroup mode now offered as a persistencemode for the engine.

Support provided for a new fault tolerant modeftgroup that does not require a database. As thenew fault tolerant mode does not use a database,this mode does not support checkpointing. Onlyone AppNode runs the applications, while theother AppNode stands by to take over in theevent of a failure of the active AppNode.

13

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.3.3

Common Features

New activities and shared resource added. TIBCO ActiveMatrix BusinessWorks providesthe Wait for Notification and Notify activitiesand the Notify Configuration shared resource tohandle inter-process communication. Theseactivities are similar to semaphores inprogramming. A process containing a Wait forNotification activity waits for another process toexecute a corresponding Notify activity.

The Notify Configuration Shared Resourcespecifies a schema for passing data betweenexecuting process instances.

Support added for JSON based EMSconfigurations

ActiveMatrix BusinessWorks now supportsJSON based EMS configurations.

Design time libraries (DTL) as a part of TIBCOActiveMatrix BusinessWorks 6.x MigrationUtility

In the Migration Utility, DTLs are now migratedas part of the 5x project. To configure the projectlibraries, click the Browse button in the SelectProjectLibs(DTLs) used by Project field. Thisenables the DTLs to be loaded during migration,keeping all other properties of the project likeresources and references intact.

Concrete WSDLs can now be generated atruntime for SOAP over HTTP bindings.

Users can generate concrete WSDLs at runtimeusing the endpoint URI, followed by a questionmark (?).

For example, to extract a SOAP Over HTTPService wsdl, we can use the SOAP serviceEndpoint URI appended by the requestparameter, wsdl.

In the example for SOAPUnboundHeaders, thatis shipped with the product, and can be accessedin TIBCO Business Studio from binding\soap\http

\tibco.bw.sample.binding.soap.http.SOAPU

nboundHeaders, the SOAP Over HTTP servicebinding, called SOAPServiceBinding, publishedwith the HTTP resource, HTTPConnectorResource, is configured to run on thehost machine localhost, and port number 9909.The binding, SOAPServiceBinding is configuredwith the endpoint URI /SOAPServiceBinding/serverProcess/, and the URL to extract theruntime WSDL definition would be http://localhost:9909/ SOAPServiceBinding/serverProcess/?wsdl, where wsdl is the queryparameter.

14

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Common Features

Support has been added to the WSS Consumerand WSS Provider policies to encrypt and signcertain parts of the message header.

Under the Confidentiality tab of the WSSConsumer and WSS Provider policies, usershave the option to encrypt or sign elements inthe request or response message. If users selectthis option, they can specify elements in therequest or response message to encrypt or sign,and specify the namespace of the element, andthe prefix of the element if it has one.

Design Time

Ability to select inline schemas from WSDLS inthe same application module

From the Output Editor tab of the Start activity,and the Input Editor tab of the End activity, click

, and from the Select Schema ElementDeclaration window, select Include WSLDInline Schemas to display inline schemas fromthe WSDLs in the module.

Group index variable can be made available byselecting the Global check-box for groups

Toggle the Global check-box, located under theGeneral tab of the Repeat, While, For Each,Iterate and Repeat on Error groups, to make thegroup index variable available at the processlevel or revert to local level.

Runtime Administration Framework

SSL support when connecting to EMS servers. AppNodes support connecting to a SSL enabledEMS Server when using the group persistencemode.

LDAP support for user authentication forbwagent REST API.

The bwagent REST API can be configured withthe LDAP login module.

Support for multiple bwagents to be registeredwith TEA.

Multiple bwagent networks can now bemanaged using the same TEA Server.

Release 6.3.2

Common Features

Added support for header parameters describedin the Swagger 2.0 specification.

Added support for header parameters describedin the Swagger 2.0 specification.

Support for Form, specifically application/www-x-form-urlencoded and multipart/form-data as amedia type for REST Service and RESTReference bindings.

Support for Form, specifically application/www-x-form-urlencoded and multipart/form-data as amedia type for REST Service and RESTReference bindings.

Support for anonymous JSON arrays Support for anonymous JSON arrays.

15

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design Time

New type of subprocess You can now use a new non-WSDL-basedsubprocess, called a direct subprocess. A directsubprocess does not require a WSDL to definesubprocess details. Instead, details are set on theStart and End activities in the process interface.During migration processes all subprocesses aremigrated as direct subprocesses.

Support for HTTPS protocol on the RESTReference Binding that are not defined usingSwagger Specification

You can now configure the REST ReferenceBinding to use HTTPS protocol.

Support for posting raw binary data through theSend HTTP Request activity

When configuring the Post Data Type field fromthe General tab, users can now choose to sendpost data as a string or as binary.

REST Reference wizard allows users to invokeweb services from Business Studio

In former versions of TIBCO ActiveMatrixBusinessWorks 6.x, web services could only beinvoked using Swagger files. In this release, thenew REST Reference wizard in Business Studioallows users to invoke web services byproviding the web service URL.

Ability to reuse an HTTP Connector SharedResource from a Shared Module in multipleapplications deployed on the same AppNode

Selecting the Share Across Applications checkbox, under the Advanced Configuration section,enables users to reuse the HTTP ConnectorShared Resource across multiple ApplicationModules.

This check box is only applicable if theHTTP Connector Shared Resource ispresent in the Application module.

Ability to select HTTP methods to disable Users can configure the newly added fieldDisable HTTP Methods, located under theAdvance Configuration section of the HTTPConnector Shared Resource, to disable specificHTTP methods.

To add an HTTP method, click Add icon .To remove an HTTP method, select the method,

and click the Delete icon .

The first time you click the Add icon

, by default the TRACE method isselected and added to the list ofmethods to be disabled.

16

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design Time

Ability to use default confidentiality Users can now select Default Confidentialitycheck-box on the HTTP Client Shared Resourceto connect to HTTP servers using SSL withouthaving to manually specify a SSL ClientResource or Keystores.

Users can now use module properties whenselecting an HTTP Client Shared Resource forTransport Configuration in SOAP binding.

Users can now use module properties whenselecting an HTTP Client Shared Resource forTransport Configuration in SOAP binding

Support for a custom fault schema for individualoperations and fault codes for REST services.

Users can specify a custom fault schema and theHTTP code and Reason Phrase for individualoperations.

Improved ability to create XML schema from aJSON payload.

Users can now generate an XML SchemaDefinition from a JSON payload which containsanonymous JSON Arrays.

Users can now have null values in the JSON ifthe XML schema has nillable attribute set totrue for the XML Element definition.

TIBCO ActiveMatrix BusinessWorks nowsupports NULL values in JSON. However, thissupport does not extend to supporting NULLvalues in root elements.

Ability to select individual processes andresources during migration.

Selective processes and resources can now bemigrated while migrating projects from TIBCOActiveMatrix BusinessWorks 5.x to TIBCOActiveMatrix BusinessWorks 6.x.

The migration utility migrates all the dependentprocesses and resources while migration.

Logging HTTP request and response time Select the Log Request/Response check box tolog the time required for sending and receivingthe HTTP response in the Send HTTP Requestactivity.

Ability to select individual processes andresources when running the Debugger.

You can now select individual processes andresources to launch, or exclude, when runningthe Debugger in Business Studio.

Runtime Administration Framework

Support for storing historical execution data ofprocess or activity

As a part of monitoring, when users startprocess instance or activity statistics collectionthey can store all the historical execution data ofthe process or activity to an external database.

17

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

Support for using TIBCO FTL® for the bwagenttransport.

The bwagent can be configured to use TIBCOFTL for transport among bwagents. PostgreSQL,MySQL, Microsoft SQL, Oracle, and DB2 are thesupported databases.

Use of TIBCO FTL® with TIBCOActiveMatrix BusinessWorks™ forconfiguring bwagent and forconfiguring group provider for enginedoes not require TIBCO FTL® licenses.

Support for using TIBCO FTL® as the groupprovider technology for the engine.

TIBCO FTL® can be used as the group providertechnology for the engine when the engine isconfigured for group mode.

Use of TIBCO FTL ® with TIBCOActiveMatrix BusinessWorks™ forconfiguring bwagent and forconfiguring group provider for enginedoes not require TIBCO FTL® licenses.

Enabling and disabling specific process startersin an application

Users can now enable, or disable, a particularcomponent in an application from TIBCO®

Enterprise Administrator (TEA).

New Hawk commands Hawk Microagent support for two new methodshas been added:

1. ResumeBWComponent

2. SuspendBWComponent

Publishing APIs to Mashery from the Admin UIusing the Publish to Mashery button.

You can now publish APIs to TIBCO Mashery®from TIBCO® Enterprise Administrator (TEA)using the Publish to Mashery button.

18

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.3.1

Runtime Administration Framework

Unshared State Failover (UFO) support in JMS This feature introduces a new check-box toindicate the usage of Unshared State Failover inJMS. This check-box appears only when theoption Direct is used in the Connection FactoryType field. When using the unshared failoversetup, if a connection loss is detected on Server(A), BusinessWorks will try to connect to Server(B) as defined in the connection factoryconfiguration.

After enabling the check-box, you can pass theprovider URL in the form of UFO. For example,

tcp://serverA:7222+tcp://serverB:7222,

where Server A and Server B are two EMSservers configured for sharing the UnsharedState Failover.

Common Features

Support for Java Runtime Environment (JRE) 8 JRE has been upgraded for Business Studio,Core Runtime and all the tools forAdministration.

Runtime Administration Framework

Unshared State Failover (UFO) support in JMS This feature introduces a new check-box toindicate the usage of Unshared State Failover inJMS. This check-box appears only when theoption Direct is used in the Connection FactoryType field. When using the unshared failoversetup, if a connection loss is detected on Server(A), BusinessWorks will try to connect to Server(B) as defined in the connection factoryconfiguration.

After enabling the check-box, you can pass theprovider URL in the form of UFO. For example,

tcp://serverA:7222+tcp://serverB:7222,

where Server A and Server B are two EMSservers configured for sharing the UnsharedState Failover.

19

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.3.0

Design-time

REST Consumption Improvements With this release, we have introduced supportfor REST reference bindings using Swaggerspecifications. The path and query parametersare fetched from the Swagger document.

Path parameter names and queryparameter names must be unique in aresource service path.

If the Request Format for a RESTBinding is Form, the parameter namemust be different from all elementnames in the referenced schema.

Business Studio upgraded to Eclipse 4.4.1. TIBCO Business Studio now uses Eclipse 4.4.1 asthe underlying platform for design-time. Thisbrings significant improvements in userexperience and performance. In addition, from acompatibility point of view, the upgrade alsoprovides better support for other plug-ins thatare used with Eclipse.

Support for Error Transitions for all activitiesand groups.

Error transitions can now be created betweentwo activities, or a group and an activity.

Support for implementing selective operationsfor a given port type.

Users can now choose to implement only a selectset of operations for given port type as part oftheir process design.

Runtime Administration Framework

Swagger support upgraded from 1.2 to 2.0specification.

BusinessWorks generates Swagger 2.0specification as a standard for documentingRESTful services. The associated Swagger UI hasalso been upgraded to support the 2.0specification.

Users can now create and consume RESTfulservices defined using Swagger 1.2 and 2.0specifications.

Ability to provide the prefix to be appended tothe appNode process (name).

The required prefix can be appended to theappNode process (name) by setting theenvironment variable bw_appnode_pid_prefix tothe desired value.

20

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

Support for Microsoft SQL server and TIBCOEnterprise Messaging Server (EMS) for datapersistence and transport.

bwagent can now be configured to use MicrosoftSQL server and TIBCO Enterprise MessagingServer (EMS) for data persistence and transport.For additional details, refer to the section"Configuring bwagent for Microsoft SQL Serverand TIBCO Enterprise Message Service" in theAdministration guide.

Ability to enable the governance agent on theAppNode to ensure security is enforced onActiveMatrix BusinessWorks 6.x applicationsdeployed with policies.

To enable the governance agent, set the propertybw.governance.enabled to true. You canmodify this property in the AppNode settingsthrough the Admin UI, or in the AppSpacetemplate file, appspace_config.ini_ template,located in <BW_HOME>\config\.

Job data is available in the main process thoughthe execution was suspended by the sub process.

In Business Studio, when a sub-processsuspends a main process, the job data can beviewed in the main process.

Release 6.2.2

Design Time

Ability to enforce security policies on new andexisting ActiveMatrix BusinessWorks 6.xapplications in Business Studio.

In Business Studio, you can create and managepolicies and related resources. In addition, youcan enforce security on ActiveMatrixBusinessWorks 6.x applications by associatingpolicies with activities and bindings inapplication processes.

Runtime Administration Framework

Ability to enable the governance agent on theAppNode to ensure security is enforced onActiveMatrix BusinessWorks 6.x applicationsdeployed with policies.

To enable the governance agent, set the propertybw.governance.enabled to true. You canmodify this property in the AppNode settingsthrough the Admin UI, or in the AppSpacetemplate file, appspace_config.ini_ template,located in <BW_HOME>\config\.

21

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.2.1

Runtime Administration Framework

Ability to enable or disable process statisticscollection from the Admin CLI.

You can enable or disable process statisticscollection for an application from the Admin CLIusing the following commands:

● enablestats

● disablestats

See Process Statistics for details.

Improved Administrator user interface A number of visual cues and aestheticenhancements to the Administrator UI havebeen made including improvements to theProcess Viewer.

GET operation to obtain AppSpace configuration The bwagent REST API now provides a GEToperation to obtain the AppSpace configuration.

Design-time

Improved wizard to create subprocesses The wizard to create subprocesses has beenimproved to create subprocesses with inlineschema and WSDL files. The wizard has alsobeen improved to make it easy to use andconsistent with the approach to create processes.

Swagger UI and Swagger Specification supportfor Basic Authentication

The Swagger UI supports the use of endpointsconfigured with Basic Authentication. TheSwagger UI has two new fields, User Name andPassword, which are always visible.

Basic Authentication support for REST Bindingand Invoke REST API activity

The REST Service Binding and the Invoke RESTAPI activity support Basic Authentication.

The REST Service Binding can be configuredusing a check box in the Binding Configuration.When the check box is selected, the RESTBinding uses the LDAP Shared Resourceconfigured on its HTTP Connector to performBasic Authentication.

The Invoke REST API activity automaticallyadds the authorization header with the usercredentials if an Identity shared resource isconfigured on the HTTP Client shared resource.

See REST Binding for details.

SSL Client and SSL Server resources default thekeystore implementation to JRE's certificate store

The SSL Client and SSL Server resources defaultthe trust keystore configuration to JRE's cacerts.This eliminates the need to create trust storesfrom default.

22

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

HTTP Authentication support for SOAP Binding A new HTTP Authentication check box has beenintroduced. When selected, specifies that theService Request sent by the Service Consumermust be authenticated. Authentication issuccessful, if the user name and passwordspecified in the Service Request exists in theLDAP server configured on HTTP Connector.

Enhancements to JDBC activities● JDBC activities now support ThreadPool

shared resources that you can use to limitthread creation.

● JDBC activities now expose Activity Timeoutwith a default value of 3 minutes. When thetimeout value is reached, the engine cancelsthe activity and throws an ActivityTimedoutexception.

See JDBC Palette for details.

Samples and Scripts

New script, bw6env.sh, to print the environmentvariable configurations

The script, bw6env.sh, prints the required andoptional environment variable configurations onthe screen. This script is available under the<TIBCO_HOME>/bw/6.2/scripts/admin folder.

Release 6.2.0

Runtime Administration Framework

bwagent supports an external datastore forcommunication and TIBCO Enterprise MessageServer (EMS) for persistence

The bwagent now supports an external datastore(PostgreSQL or MySQL) and TIBCO EMS forpersistence and communication in addition toTIBCO ActiveSpaces. See Administrator andAgent -> bwagent -> Configuring bwagent in theAdministration guide for details.

bwagent configuration Two JSON files are provided for bwagentconfiguration: bwagent_as.json andbwagent_db.json. You can use the bwadminconfig command with one of these JSON files toconfigure the bwagent.

See Administrator and Agent -> bwagent ->Configuring bwagent -> ActiveSpacesConfiguration for bwagent and Administratorand Agent -> bwagent -> Configuring bwagent ->Database/EMS Configuration for bwagent in theAdministration guide for details.

23

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

bwadmin commands for viewing agent andengine information

There are new bwadmin commands for viewingagent and engine information:

● The show agentprocessinfo commandshows info about the agent.

● The show bwengine command shows infoabout the engine on an AppNode.

● The bwenginedb command shows info aboutthe engine database.

Remote AppNode debugging from TIBCOBusiness Studio

You can debug a remote AppNode from TIBCOBusiness Studio. To do so, select the AppNode inthe Deploy view and click the enable debug icon

in the Properties view before launching thedebugger.

See Deploying an Application -> Using theDebugger -> Remote Debugging in theApplication Development guide for details.

Remote AppNode debugging enabled using thebwadmin command or from the Admin UI

You can enable remote debugging for anAppNode using the bwadmin command or fromthe Admin UI. This is useful in secureenvironments where only an administrator hasthe access rights to enable or disable ports.

See Administration Tasks and Reference ->Managing AppNodes -> Debugging anAppNode in the Administration guide for details.

Application activity execution statistics andprocess execution statistics collection

You can collect application activity executionstatistics and process execution statistics anddisplay the results as a text file, an HTML file, orwrite to a database. See Logging -> AppNodeLogging -> Statistics Collection in theAdministration guide for details.

Domain backup and deletion in the Admin UI The following operations are available on theDomain Management page in the Admin UI:

● Backing up and restoring an domain. SeeAdministration Tasks and Reference ->Managing Domains -> Backing Up andRestoring a Domain in the Administrationguide for details.

● Deleting a domain. See Administration Tasksand Reference -> Managing Domains ->Deleting Domains in the Administration guidefor details.

24

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

View process diagrams in the Admin UI From the Application page in the Admin UI fora running application, you can view theendpoints, components, and processes for arunning application. Furthermore, you can viewthe process diagrams provided the applicationarchive file was generated using the currentversion of the product.

See Administration Tasks and Reference ->Managing an Application -> Viewing Endpoints,Components, and Processes in the Administrationguide for details.

REST Doc URL in the Admin UI From the Application page in the Admin UI fora running application, you can view the RESTDoc URL for applications using REST services.The links open the REST UI page where you cantest out the operations. See Administration Tasksand Reference -> Managing an Application ->Viewing Running Applications in theAdministration guide for details.

Unified Doc URL configuration Documentation for all applications in anAppSpace using REST services are now availableon a single REST Doc URL. See AdministrationTasks and Reference -> Managing an Application-> Viewing Endpoints, Components, andProcesses -> Configuring a Unified Doc URL inthe Administration guide for details.

Application properties and application instanceproperties editing in the Admin UI

Application properties and application instanceproperties can be edited from the Admin UI. SeeAdministration Tasks and Reference ->Managing an Application -> Editing Applicationand Application Instance Properties in theAdministration guide for details.

25

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

Application profile download from the AdminUI

Application profiles can now be downloadedfrom the Admin UI. This is the same asexporting an application profile on thecommand line using the bwadmin exportcommand. See Administration Tasks andReference -> Managing an Application -> EditingApplication and Application Instance Properties-> Exporting an Application Profile in theAdministration guide for details.

AppSpace or AppNode configuration updatefrom the Admin UI

The AppSpace or AppNode configurations canbe viewed and updated from the Admin UI.Updates to the AppSpace configuration madefrom the Admin UI are applied to all theAppNodes contained in that AppSpace. This isthe same as running the bwadmin configcommand on the command line to update theAppSpace or AppNode configurations.

See Administration Tasks and Reference ->Managing AppSpaces -> Editing an AppSpaceConfiguration and Administration Tasks andReference -> Managing AppNodes -> Editing anAppNode Configuration in the Administrationguide for details.

Ability to iterate through a list of items in Level2 entities in the Admin UI

You can now iterate through a list of items inLevel 2 entities (next and previous) in the AdminUI. See Admin UI tasks in the "AdministrationTasks and Reference" section in theAdministration guide.

Design-time

Compensation Handlers and Compensateactivity

Every scope can define a compensation handler,which contains logic that gets executed to revertthe logic of the scope. A compensation handlercan be executed only if the scope that is belongto has been successfully executed. Acompensation handler can be triggered in thefollowing ways:

● implicitly, by an uncaught fault that isthrown downstream in the process.

● explicitly, by using the Compensate activity.

FTL Palette The FTL palette allows ActiveMatrixBusinessWorks applications to send and receivemessages using TIBCO FTL®. See FTL Palette inthe Bindings and Palettes Reference guide fordetails.

26

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

Inspector Activity The Inspector activity is used to write the outputof any or all activities and module properties toa file and/or standard output. This activity isparticularly useful to debug processes. SeeInspector in the Bindings and Palettes Referenceguide for details.

Deploy an application from TIBCO BusinessStudio

You can deploy an application to an AppSpacefrom TIBCO Business Studio. See Deploying anApplication in the Application Development guidefor details. For restrictions, refer to KnownIssues section in the Release Notes.

Generate ActiveMatrix BusinessWorks processesin SVG format when generating archive file

When creating an archive file for an application,the application packager also generates theActiveMatrix BusinessWorks processes in SVGformat, which can be rendered in the Admin UI.When you deploy this archive file and start theapplication, you can view the process diagramsfor the processes from the Applications page inthe Admin UI.

Support for partial responses in REST Partial responses in REST helps the user torequest only those fields which are required aspart of response. See REST Binding in Bindingsand Palettes Reference guide for details.

Support for refactoring XSD schema and WSDLentities

A new refactoring tool for renaming entities isavailable as part of the Project Explorer menu.When you right-click on a particular entity, ifthat entity supports refactoring, a new Refactormenu containing the refactoring tools that areappropriate and available for that entity isdisplayed. For example, when you right-click onan XML Schema, the Refactor menu item lists aRename XSD Schema Namespace refactoringtool.

Eclipse p2 installation for ActiveMatrixBusinessWorks Plugins

ActiveMatrix BusinessWorks plugins can now beinstalled from TIBCO Business Studio using theHelp > Install New Software menu. The Eclipsep2 installation packages for the plugins must bedownloaded and made available on an updatesite or directory beforehand. See InstallingTIBCO ActiveMatrix BusinessWorks Plug-ins inthe Installation guide for details.

Samples and Scripts

Core admin scripts support database/EMSconfiguration

The core admin scripts now support thebwagent configuration for PostgreSQL databasewith TIBCO Enterprise Message Service.

27

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Samples and Scripts

New admin script to create a fault tolerant groupwith cross-engine persistence.

A new admin script,configureBWEngineGroup.sh, to create a fault-tolerant group with cross-engine persistence isavailable. This script can be used the bwagent isconfigured for TIBCO ActiveSpaces.

28

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Changes in Functionality

The following are the notable changes in functionality in this release.

Release 6.4.0

Design-time

Restrictions on naming the activities in TIBCOBusiness Studio™.

Activities cannot have the same name as that ofoperation in a service, or a reference in a currentprocess.

Changes in the way subprocesses are displayedafter you drag and drop them on a process orsubprocess.

In former versions of the software, dragging adirect or service subprocess from the ProjectExplorer and dropping it on a process, directsubprocess, or service subprocess that was openin the Process Editor caused an activity icon toappear with the default activity name. Forexample, dropping a direct subprocess onto aprocess caused a Call Process activity, namedCallProcess to appear in the process.Alternatively, dropping a service subprocessonto a process caused an Invoke activity, namedInvoke, to appear in the process.

With this enhancement, the Call Process orInvoke activities that appear in the process, orsubprocess, are named after the subprocess theyreference. For example, dropping a directsubprocess, called SubprocessA, onto a processwill result in a Call Process activity namedSubProcessA to appear. The same applies forservice subproccess.

Ability to select multiple process properties todelete.

Multiple process properties can now be selectedand deleted from the Properties tab in TIBCOBusiness Studio. To select multiple processproperties, hold down the Shift key, and eitherselect the individual process properties, or usethe down directional key on your keyboard.

The Rename Refactoring dialog appears only if achange has been detected in the name of themodule property group.

The Rename Refactoring dialog appears only ifa change has been detected in the name of themodule property or module group.

Module Properties support for HTTP transport. The HTTP Client Connector in SOAP ReferenceBinding can now be configured with a literalvalue or a module property.

Remove button disabled in the REST Bindingstab.

If the binding used is a REST binding, theRemove button is disabled in the REST ServiceBindings tab. Users will no longer be able toremove a REST Binding.

29

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

The warning Invalid PartnerLinkType name- Reference PartnerLink name is not

unique changed to an error.

Changed the validation warning, InvalidPartnerLinkType name - Reference

PartnerLink name is not unique to an error.As a result, you cannot add two PartnerLinkreferences with same name in a process.

Release 6.3.5

Migration

Classes folder removed from the CustomXPATH Function Group Plugin project

After migration, the classes folder will no longerbe available inside the Custom XPATH FunctionGroup Plugin Project. ThecustomXPathFunction.jar file for classesreferred by the project are placed in the libfolder. The same JAR file will also be added tothe project class path.

Custom XPATH Function Group Plugin After migration, Custom XPATH FunctionPlugin Project will be included in the applicationproject.

General

Stricter validation for accepted response type REST service has a stricter validation on theaccepted response type, and if anything otherthan the supported response types is used, theunsupported response media type exception isthrown.

Release 6.3.4

Design-time

Flow limit on REST Service Bindings To apply Flow Limit to applications that useHTTP-based transports, specify the number ofmaximum QTP threads on the HTTP Connectorshared resource. The value you set for theminimum number of QTP threads shouldalways be less than, or equal to, the number youset for maximum QTP threads.

If applications are using non-HTTP-basedtransports, for example JMS, set thebw.application.job.flowlimit property. For moreinformation on this, refer to the "Flow Limit(bw.application.job. flow limit)" topic in thePerformance and Tuning guide.

30

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

Replacing a deployed archive file will undeploythe application.

To replace an archive that has been uploaded,but not deployed, use the -replace option withthe upload command to upload the archiveagain. To replace an archive file has beenuploaded and deployed, use the -replaceoption.

Removal of TIBCO Enterprise Message ServiceClient Libraries

Starting with the ActiveMatrix BusinessWorks™6.3.4 release, TIBCO Enterprise Message Service(EMS) client libraries are no longer shipped withthe product. This affects the following areas ofthe product:

● Palettes - JMS (when using EMS as theserver)

● Binding - SOAP (when using JMS transport)

● Configuring bwagent with EMS andDatabase

● Configuring engine Managed Fault Toleranceusing EMS and Database

A new bwinstall utility target has been createdfor users to easily add client libraries from theEMS installation. To install EMS Client librariesrun the following command from<BW_HOME>/bin folder and follow theprompts:

bwinstall ems-driver

Release 6.3.3

There are no changes in functionality in the version 6.3.3 of TIBCO ActiveMatrix BusinessWorks™.

Release 6.3.2

Design-time

Invoke activities with a single Message-Part(Element) as the output, can be selected asthe Output Activity for the group

The Accumulate Output check box is nowsupported for the Invoke activity when theactivity is used inside of a group.

An easier way to create an XSD schema from aJSON payload in Business Studio

The new JSON to Schema Wizard provides astreamlined approach to creating an XMLschema from a JSON Payload. It can be easilyaccessed by right-clicking on the Schemas folderfrom the Project Explorer pane, and clickingNew > XML Schema File from JSON Payload.

31

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

Updates to the HTTP access logs The following HTTP Access Log properties,which were introduced in TIBCO ActiveMatrixBusinessWorks™ 6.3.0, were removed:

1. bw.plugin.http.jetty.disableaccesslogs

2. bw.plugin.http.jetty.accesslogs.extended

3. bw.plugin.http.jetty.accesslogs.cookies

4. bw.plugin.http.jetty.accesslogs.servername

5. bw.plugin.http.jetty.accesslogs.dispatchtime

Another update made was to the defaultbehavior of HTTP access logs. Previously, HTTPaccess logs were printed by default. In thisversion of the software, HTTP access logs willnot be printed by default.Users can choose oneof the following options to enable the access log:

● To turn on HTTP access logs for newapplications created using TIBCOActiveMatrix BusinessWorks 6.3.2, select theEnable Access Logs check box in the HTTPConnector Shared Resource.

● To turn on HTTP access logs for applicationsthat were created using TIBCO ActiveMatrixBusinessWorks 6.3.1 , or using previousversions of the software, set thebw.plugin.http.jetty.accesslogs.enable totrue.

Lastly, in previous versions of the software,access logs could only be turned on from anAppNode level. In this release, users have fine-grained control over access logs as they can nowenable access logs on individual SharedResources.

The JDBC palette can be configured to usecustom JDBC drivers

The JDBC Connection Shared Resource can beconfigured to use custom drivers at run time. Foradditional details, refer to the "Using CustomDrivers for Run Time" section in the TIBCOActiveMatrix BusinessWorks Bindings and PalettesReference guide.

32

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Design-time

JMS activities now support dynamic JMSproperties

Users can add JMS properties to the followingJMS activities at runtime:

● Get JMS Queue Message

● JMS Receive Message

● JMS Request Reply

● JMS Send Message

● Reply to JMS Message

● Wait for JMS Request

Migration

Subprocesses in TIBCO ActiveMatrixBusinessWorks 5.x applications are migrated asdirect subprocesses.

During migration subprocesses in TIBCOActiveMatrix BusinessWorks 5.x applications aremigrated as direct subprocesses.

Release 6.3.1

There are no changes in functionality in the version 6.3.1 of TIBCO ActiveMatrix BusinessWorks.

Release 6.3.0

Design-time

An error message is displayed if user attempts toadd a circular dependency.

When a Shared Module or a Service Descriptoris added as a dependency to a separate SharedModule that is already dependent on it, amessage is displayed warning the user that adependency loop will be created.

Module properties and Process Properties cannow be selected for the Schema and Catalog orPackage fields in the JDBC Call Procedureactivity.

Configure the Schema field to use a ProcessProperty or a Module Property if a schema hasbeen defined for the project, and you know theschema name. To search for a schema, configurethe field to use a Literal Value, and click theBrowse button to select a schema from thedatabase that is using the specified JDBCConnection.

Runtime Administration Framework

The existing statistics functionality has beenupdated to pass the optional argumentsprocessname and activityname.

Optionally, to retrieve statistics for a particularprocessname or activityname use the arguments-bp or -ba, respectively.

If not provided, statistics for all processes andactivities will be retrieved

33

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.2.2

Migration

Backwards compatiblity is disabled by defaultfor ActiveMatrix BusinessWorks 6.x applicationsusing TIBCO ActiveMatrix Policy Director 2.0 toenforce security policies.

To reduce overhead when messages areconsumed, backwards compatibility is disabledby default for ActiveMatrix BusinessWorks 6.xapplications using TIBCO ActiveMatrix PolicyDirector 2.0.

To enable backwards compatibility, add thepropertybw.governance.pd.compatibility.mode=true

to the existing AppSpace configuration fileappspace_config.ini (located in the root of theAppSpace folder), or the AppSpaceconfiguration template file,appspace_config.ini_ template, located in<BW_HOME>\config\.

Refer to "Applying Security Policies" in theTIBCO ActiveMatrix BusinessWorks Administrationguide for instructions.

The Authentication check box on service sideactivities and bindings was removed.

If the Authentication check box was selected onactivities or bindings that supportedauthentication in TIBCO ActiveMatrixBusinessWorks 6.2.1 or older, the Authenticationcheck box continues to display andauthentication remains enforced on the activityor the binding.

If you clear the Authentication check box, awarning message is displayed prompting youfor confirmation. Clicking OK causes theAuthentication check box to no longer displayand removes authentication from the activity orthe binding. To reapply authentication, associatethe Basic Authentication policy with the activityor the binding.

Refer to the TIBCO ActiveMatrix BusinessWorksBindings and Palettes guide for additional details.

34

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Release 6.2.1

Runtime Administration Framework

The TEA Shell implementation of the backupcommand has been updated to support thecreation of a zip archive only.

The backup command only supports thecreation of a zip archive. The -z option for thebackup command to create a zip archive isobsolete.

If the argument '-s destination' is an existingfolder, you can choose a name.zip for the ziparchive. If the .zip qualifier is missing, thecommand adds the qualifier to the archivecreated.

The alias for path argument in the TEA Shelldeploy command has been changed from '-p' to'-pa'.

The alias for path argument in the TEA Shelldeploy command has been changed to '-pa' toavoid ambiguity with the '-p' alias for theprofileName argument.

Design-time

JDBC Query activity does not fetch the tablemetadata to construct the Output schemaautomatically.

The JDBC Query activity automatically fetchedthe table metadata to construct the Outputschema based on the SQL query. This behaviorhas been changed. Every time you want toconfigure the JDBC Query activity, you mustfetch the table metadata manually using theFetch button. The new behavior is similar to thebehavior in TIBCO ActiveMatrix BusinessWorks5.x version.

Release 6.2.0

Runtime Administration Framework

Changes in the file system location for thedefault \domains folder

The default folder (domains) used to storeruntime artifacts in the file system used to belocated at TIBCO_HOME/bw/domains. This folderis now located at folder.

You can change the location of the default folderused to store the runtime artifacts by updatingthe defaultdomain.domainHome property in theTIBCO_HOME/bw/6.2/domains/

DomainHomes.properties file. See sectionConfiguring the Location of the DefaultDomains Folder in the Administration guide fordetails.

35

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Runtime Administration Framework

Changes to the OSGi commands The OSGi commands have changed. For the fulllist of commands, see Managing AppNodes ->Enabling the OSGi Console for an AppNode ->OSGi Runtime Statistics Commands in theAdministration guide.

Changes to the TIBCO Hawk MicroAgentmethod names

The TIBCO Hawk MicroAgent method nameshave changed. For the full list of methods, seeMonitoring using TIBCO Hawk -> TIBCO HawkMicroAgent Methods in the Administrationguide.

Archive paths in a backup archive are nowrelative within the archive

When a backup is created as an archive file, thearchive file is generated as<entity>_<name>.zip and contains relativepaths. The destination argument can be anexisting folder, or if the specified ends with aforward-slash ('/') , a folder will be created (if itdoes not exist already).

Persistent application state Previously, applications did not retain their stateafter an AppNode was restarted. This behaviorhas changed and applications now retain theirstate when an AppNode is restarted.

Samples and Scripts

Changes in the file system location The core admin scripts are now available underthe BW_HOME/samples/core/admin folder. SeeCore Admin Scripts in the Administration guidefor details.

36

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Samples and Scripts

Changes to the location of the admin scriptsshipped with the product

Previously, all the admin scripts were installedunder a single directory, BW_HOME/samples/core/admin.

These scripts are now separated into two setsand are installed under the following directories:

● Sample scripts located at BW_HOME/samples/core/admin.

● Generic scripts located at BW_HOME/scripts/admin.

As a consequence of this separation, the samplescripts now rely on the PATH variable to find thegeneric scripts available under BW_HOME/scripts/admin.

The script, BW_HOME/scripts/bashrc.sh,containing the environment variables is auto-generated after installation. To set theenvironment variables required to run the adminscripts, add the following statement to your~/.bashrc file to source the generated script:sourceBW_HOME/scripts/bashrc.sh

37

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Closed Issues

The following are the closed issues for the 6.4.x releases of TIBCO ActiveMatrix BusinessWorks™.

The closed issues are grouped by components:

● Administration

● Bindings

● General

● Migration

● Palettes

● Policies

Administration

Release 6.4.0

Key Description

AMBW-26762 The AppSpace count was displayed incorrectly on the Domain summary page.The issue is now fixed, and only unique AppSpaces in a Domain are nowcounted.

AMBW-26475 Users were unable to upload EAR application files from TIBCO Business Studio,and a Null Pointer Exception was thrown. This has been fixed.

AMBW-26444 An EAR application file entry was missing from the bwagent database, from thetable earfile for a deployed application, operations such as application view,delete, deploy, and so on failed.

AMBW-26415 The error 'TIBCO-BW-ADMIN-500017: BW Agent is running, Stop theremote agent, delete all the files under domains folder,and re-

try' was thrown when the bwagent was registered to TIBCO® EnterpriseAdministrator (TEA). This has now been fixed.

AMBW-26299 The Validate button on the Admin UI has been enhanced, and now displays atooltip indicating that this button validates the HTTP ports within theActiveMatrix BusinessWorks scope only.

Release 6.3.5

Key Description

AMBW-26236 When checking the AppNodes page from the Admin UI, information took along time to display if the bwagent was configured to use an external databaseand TIBCO® Enterprise Messaging Server (EMS) for data persistence andtransport. This has been fixed.

38

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-26206 When checking the Domain Management page from the Admin UI, informationtook a long time to display if the bwagent was configured to use an externaldatabase and TIBCO® Enterprise Messaging Server (EMS) for data persistenceand transport. This has been fixed.

AMBW-26152 When the last registered running bwagent went into the unreachable state inTIBCO® Enterprise Administrator (TEA), and the other bwagent was started,the second bwagent did not join the ActiveMatrix BusinessWorks™ network.

AMBW-25938 EAR files that contained binary shared modules failed to upload in TEA or frombwadmin.

AMBW-25609 An exception was thrown in the Admin UI when the process and activitystatistics gathering feature was turned off.

AMBW-25541 When a user tried to modify a module property in application configurationusing non-existent properties, the incorrect error message was displayed.

AMBW-25487 To specify another host name, set the bw.agent.http.hostproperty in thebwagent.ini file.

AMBW-25150,21388

The REST Doc URL was not displayed when bwagent was started using thebwagent.sh script (execute %TIBCO_HOME%/bw/6.3/scripts/admin/bwagent.sh).

AMBW-25013 When users checked application archives details from the Admin UI, theUploaded By field did not display the correct information. Instead, the fieldincorrectly showed admin as the user who uploaded the archive file when it wasuploaded by a different user.

AMBW-24811 If two EAR files with the same name existed in two different folders, a NullPointer Exception was thrown and users were unable to create new AppNodes.

AMBW-24808 When users enabled or disabled statistics collection from bwadmin CLI, theAdmin UI did not display the new setting that was selected. The ON and OFFmode for statistics collection in the Admin UI was not updated even afterselecting the Refresh button.

AMBW-24714 In a multi-agent network, when users edited configuration properties of theAppSpace of a bwagent that was down, error messages were not thrown. Thescreen froze with no response, and the updated value could be seen only whenthe page was refreshed.

AMBW-24703 The AppSpace config.ini properties were not updated correctly, and anyAppNodes that were newly added were missing from the HAWK display UI.

Release 6.3.4

39

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25410 An exception was thrown in the Admin UI if the process and activity statisticsgathering feature was turned off.

AMBW-24973 TIBCO Enterprise Administrator® (TEA) users who had been assigned theAdministrator and Operator role did not have permission to view AppSpaces,bwagents, and other ActiveMatrix BusinessWorks™ artifacts.

AMBW-24924 A large number of producers and sessions were created through bwagent whenit was configured to use an external database and TIBCO Enterprise MessagingSystem (EMS) for data persistence and transport.

AMBW-24694 If the bwagent was invoked using the REST API, the AppNode status did notreflect the correct state.

AMBW-24667 When configuring AppNode and AppSpace properties from the Admin UI,long property names were not displayed properly in the configuration tables.

AMBW-24631 The value of password was sent as a blank string instead of the actual passwordvalue, when a property of an application configuration in the Admin UI wasedited using the Edit button.

AMBW-24158 Documentation was updated for configuring the location of the Domains folder.

AMBW-23879 EMS user permissions to authenticate non-admin users for bwagent wereupdated in the table "bwagent properties for Multi-Agent, Multi-MachineEnvironments using Database/EMS", in the Administration guide.

AMBW-23696 AppNode run time details were not always retrieved if users changed to theAppNode Graph view in the Admin UI.

AMBW-23516 bwadmin was slow to respond to a domain containing a large number ofAppNodes.

AMBW-21855 The fields Search by Category and Search Text, in the Installed ProductDescription table, were not aligned properly in the Admin UI.

Release 6.3.3

Key Description

AMBW-24629 While working in a Linux environment, the process and activity loggingstatistics were not written to an external database because the table names arecase sensitive in MySQL.

AMBW-24541 If an application property returned a null value, a Null Pointer Exception wasintermittently thrown.

AMBW-24487 Linux scripts for bwadmin was missing the diagramConfig column.

40

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-24468 A typographical error in the mashery.ini file was corrected.bw.mashery.cliendld was changed to bw.mashery.clientld.

AMBW-24431 Linux scripts for bwadmin was missing the ActivityLoggingStats andProcessInstanceLoggingStats tables.

AMBW-24332 Uploading the same EAR file and selecting the replace existing option did notreplace the old profiles.

AMBW-24051 When bwagent was configured to use Oracle 11G and EMS for data transportand persistence, an error was thrown when users tried to create a domain.

AMBW-23733 A Null Pointer Exception was thrown when the bwagent REST API server wasconfigured for one-way SSL.

AMBW-22960 A large number of producers and sessions were created through the bwagentwhen it was configured with an external database and TIBCO EMS.

AMBW-22786 Configuring an application using DB/EMS failed because the size of thecolumns, COMMANDPARAMS and EXECUTIONSTATUS in the tableCOMMANDHISTORY were not appropriate.

AMBW-21835 An overridden EAR file deployed successfully even when the option Replaceany existing version was not selected.

AMBW-20975 Applications with long application profile names failed to successfully upload.

Release 6.3.2

Key Description

AMBW-23601 Improved the performance of the bwadmin command show appspaces.

AMBW-22942 The application status was displayed incorrectly when viewing it from thebwadmin client and the Admin UI.

AMBW-22556 When the bwagent was configured to use EMS/DB for data persistence andtransport, the command SELECT COUNT(commandId) FROM CommandHistorywas executed multiple times.

AMBW-22054 The application status was Impaired if a module property in the EAR file wasupdated and redeployed again.

AMBW-21875 Enabled OSGI ports were visible in the Admin UI after they were removed fromthe Node Update screen. Additionally, the required changes after commentingthe property osgi.console=localhost:1122 on the node's config.ini file onthe disk were not reflected in the Update screen in the Admin UI. The value ofthe OSGI ports were still visible in the Admin UI.

41

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21527 Executing the disableconsole command from the command line did notproperly disable the OSGi console. The same issue occurred if users updatedAppNode settings through the Admin UI and removed the OSGi host and portinformation.

AMBW-20493 Even if one application was running on multiple Appnodes, only one endpointwas listed under the Endpoints tab in the Admin UI.

Release 6.3.1

Key Description

AMBW-21654 Prior to 6.2.2 HF-004, users required AppArchive permission to upload archivefiles and AppSpace permission to deploy an archive file. Now, users onlyrequire AppArchive permissions to upload and deploy archive files.

AMBW-21653 The field diagramConfig was not available in the Oracle, Postgres and MySQLdatabase when the bash scripts under <BW_HOME>\scripts\admin were used.

Release 6.3.0

Key Description

AMBW-20931 bwagent could not connect to the EMS server with authorization enabled withobfuscated passwords.

AMBW-20890 The command mentioned to create an AppNode using bwadmin did not workas documented.

AMBW-20885 If bwagent was configured to use an external database and EMS for transportand persistence, an exception error was thrown while updating the applicationmodule properties.

AMBW-20567 A large number of temporary queues were being created, but were not beingcleaned up when bwagent was configured to use an external database and EMSfor persistence and transport.

AMBW-20539 bwagent could not be configured to use SSL when connecting to an EMS server.

AMBW-20536 bwagent could not be started when the drivername was oracle.jdbc.OracleDriver.

AMBW-20318 After TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix 1 was installed, the errorTIBCO-BW-TEAAGENT-500201: Domain [Domain_Name] is not present wasthrown when users tried to access an existing domain through the Admin UI.

AMBW-20159 The password parameter for EMS could not be updated in thebwagent_db.json file with the key emsuserpassword.

42

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-19956 The bwadmin config command did not correctly update thebw.agent.technology.as.remoteDiscoveryURL field in the bwagentconfiguration file.

AMBW-19389 After upgrading from TIBCO ActiveMatrix BusinessWorks 6.2.1 to the newestversion, AppNodes did not automatically start after restarting the AppSpace.

AMBW-19751 If a large ear file was uploaded, or if multiple large ear files were uploadedsimultaneously through the Admin UI, the upload failed, and the errorjava.lang. OutOfMemoryError: Java heap space was thrown.

AMBW-19749 If the EMS server is restarted in DB/EMS mode, bwagent also needed to berestarted if it was configured to use an external database and EMS forpersistence and transport.

AMBW-18567 When a user deployed an application with a modified profile file, the deploycommand failed and an error was thrown.

AMBW-18448 The latest version of an application was not processed during the applicationstartup, and the status was displayed as Degraded in the Admin UI.

Release 6.2.2

Key Description

AMBW-19397 If an uploaded profile has non-ASCII characters in the EAR file name, a NullPointer Exception error was thrown when a user attempted to download theprofile.

AMBW-14493 System module properties could be edited in the Admin UI.

Release 6.2.1

Key Description

AMBW-18292 The backupDomains.sh and restoreDomains.sh scripts now support the -network parameter.

AMBW-18140 The bwadmin-logback and bwagent-logback files under /bw/6.2/bin nowcontain the code required to append the date in the log files.

43

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-18097 The log file size and rotation for the bwappnode are now configurable. Edit thelogback.xml file to replace the existing appender with the following:<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"><file>../log/bwappnode.log</file><rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"><fileNamePattern>../log/bwappnode%i.log</fileNamePattern><minIndex>1</minIndex><maxIndex>10</maxIndex></rollingPolicy><triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"><maxFileSize>10MB</maxFileSize></triggeringPolicy><encoder><pattern>%d{yyyy-MM-dd HH:mm:ss.SSS}%-5level [%thread] %logger{36}- %msg%n</pattern></encoder></appender>

AMBW-17829 If a node crashed for some reason, the ActiveMatrix BusinessWorks engine wasunable to resume when checkpointing was used. This has been fixed.

AMBW-17828 Checkpointing created many locks at the database. In some cases, it escalatedand created many cascade locks which affected the performance. This has beenfixed.

AMBW-17719 The command bwadmin mode did not work after TIBCO ActiveMatrixBusinessWorks 6.2.0 hotfix02 was installed. This has been fixed.

AMBW-17631 Starting appnode from command line failed with timed out error if the TIBCOHOME contained space.

AMBW-17424 The '-p' alias for path argument in the TEA Shell deploy command has beenchanged to '-pa' to avoid ambiguity with the '-p' alias for profileName argument.

AMBW-17373 The backup script was using the -version argument to back up AppSpaces. Thebackup script for ActiveMatrix BusinessWorks 6.2.1 no longer uses thisargument.

AMBW-17321 The TEA shell implementation of the backup command has been improved.

The backup command only supports the creation of a zip archive. The -z optionto create a zip archive is obsolete. If the argument '-s destination' is an existingfolder, you can choose a name.zip for the zip archive. If the .zip qualifier ismissing, the command adds the qualifier to the archive created.

AMBW-17313 A backup of an AppSpace or domain now contains the TRA files of theAppSpace (organized by agent name) and AppNodes (organized by AppSpace).

AMBW-17275 The status of an AppSpace without any AppNodes now report its status asdegraded, regardless of the start/stop/create operation.

44

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-16950 The create appnode command with -r or -lax options does not work whenrun in a separate session of bwadmin. This has been fixed.

AMBW-16657 The -na or -noarchives options were ignored by the backup command fromTEA shell. As a result, the archives and applications were backed up even whenyou ran the backup command with option-na (or -noarchives) from the TEAshell. This has been fixed.

Release 6.2.0

Key Description

AMBW-16775 On Microsoft Windows, an exception (Failed to write config file) wasthrown when configuring an AppNode if the config.ini file was not writtenusing UTF-8 encoding.

AMBW-14868 After deleting an AppSpace from the AppSpace level 2 page, the first operationto delete (or create) an AppSpace in the AppSpace level 1 page was hanging.

AMBW-12126 Applications did not retain their state when an AppNode was restarted.

AMBW-8481 On Microsoft Windows, the bwagent listen port was not released when a processwas killed. As a result, when the bwappNodes were launched again by thebwagent, the process continued to run.

Bindings

Release 6.4.0

Key Description

AMBW-27133 Catch block was unable to catch the DefaultFaultElement for the Invoke activitySOAP Reference binding. This has been fixed.

AMBW-27102 Strict validation for Accept headers in REST Request is now turned off. A RESTservice can now be invoked externally without passing the Accept headers.

AMBW-26215 Importing projects created in ActiveMatrix BusinessWorks release 6.2.2 andadding custom faults did not update the external WSDL.

AMBW-26122 The Invoke activity failed with an error when an element in the input of theInvoke activity was coerced to another element from the WSDL.

AMBW-26118 If an element of the decimal type was used in a REST service, the element wasconverted to the exponential form, which resulted in a failed validation and aGenXDM exception was thrown.

AMBW-25293 If a WSDL imported other schemas, retrieving a concrete WSDL from theendpoint resulted in an error.

45

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25211 SOAP services with the In Only operation threw an error when invoked multipletimes from SOAP Reference Binding using the Invoke activity.

Release 6.3.5

Key Description

AMBW-25463 If the format is not explicitly specified in the Swagger file, Swagger to schemaconversion changed the type integer to decimal in the schema. This has beenfixed.

AMBW-25277 The REST Reference binding did not work if it referenced an HTTP ClientShared Resource that was configured to use a Proxy Configuration sharedresource.

Release 6.3.4

Key Description

AMBW-25225 When importing a project, a validation error was thrown on the REST Referencebinding if the project contained an HTTP Client Shared Resource in a sharedmodule.

AMBW-25151 The Parse JSON activity no longer throws a validation error when configuredwith elements which reference elements from other schemas using the importattribute.

AMBW-25126 A typo was fixed in the title of the REST Reference Wizard.

AMBW-25095 SOAP faults 1.2 generated by the ActiveMatrix BusinessWorks™ SOAP serverdid not display the xml:lang attribute.

AMBW-25004 Attribute values were not passed in an unbound SOAP header.

AMBW-24967 The SOAP Reference Binding exception "javax.jms.IllegalStateException: Illegaluse of receive() from multiple threads" was thrown intermittently.

AMBW-24953 The REST Service binding became corrupted if users modified the ResourceService Path.

AMBW-24908 If a REST service was implemented in the Opaque mode, and XML was set as theresponse format, the response obtained was incorrect.

AMBW-24784 The JSON to XSD conversion mechanism assumed the object elements of anarray as uniform.

AMBW-24577 After multiple successful calls, an exception was thrown on the REST Referencebinding if authentication was enabled on the HTTP Client shared resource.

AMBW-24526 On importing projects created in earlier versions containing query parameters,users can now view and edit query parameters from the query parameters table.

46

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-24441 REST Resources were not invoked correctly during run time if resource pathsused a common prefix.

AMBW-23877 If a SOAP service used JMS for transport, and the SOAP action attribute for anoperation contained, or began with, a leading slash character, the SOAP Servicebinding did not consume the JMS message.

AMBW-22177 The Swagger UI did not show the application/xml option if the service wasconfigured with XML.

AMBW-21091 If REST resources were implemented as Opaque, the generated Swaggerspecification was incorrect.

AMBW-19163 The Swagger UI did not show the error code for bad requests such as clientfaults, invalid inputs, and so on.

AMBW-11795 Parameter templating was not supported for the Invoke REST API activitywhen it used a module property for the Resource Path. Module properties arenow supported.

Release 6.3.3

Key Description

AMBW-24395 REST References could not be created if a process was created within a SharedModule.

AMBW-23984 An Invoke activity, configured to send a SOAP over JMS message to a webserviceusing an asynchronous operation, did not throw an exception when the connectionto the EMS server broke.

AMBW-23966 The body of the request message did not contain the namespace defined in theWSDL when the SOAP Binding style was of type RPC/Literal.

AMBW-22848 Users can now view the associated Swagger file as a link in the REST ServiceBinding.

AMBW-22747 When the Swagger file has a property of type object an equivalent XSD was notgenerated and an error was thrown.

AMBW-16039 Incorrect Swagger specification models were generated for REST services whenusing the pass through mechanism (Opaque mode).

Release 6.3.2

Key Description

AMBW-23581 If a SOAP service binding was configured to use JMS as the transport type, and theAcknowledge Mode field was set to Client or TIBCO Explicit, unconfirmedmessages were not redelivered.

47

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-23309 The 404 Not Found error was thrown for a REST Resource when multiplehierarchical REST Resources were deployed in the same application.

AMBW-22634 Swagger UI incorrectly used HTTP, instead of HTTPS, even if the HTTP ConnectorResource used by the REST Service Binding was configured with HTTPS.

AMBW-22496 TIBCO ActiveMatrix BusinessWorks always published SOAP/JMS servicesresponse messages in the PERSISTENT mode, even if the request message has beenpublished by the consumer in the NON_PERSISTENT mode.

AMBW-22495 Added an option to not confirm a message if an error is thrown in a processcontaining Service over JMS with TIBCO EMS Explicit Client ACK, or client ACKmode.

AMBW-22038 Swagger UI did not display the REST services if the operation response wasconfigured to use Simple Element or Simple Type.

AMBW-21864 Renaming an implemented REST service binding operation from Business Studiodid not work, and caused an exception to be thrown.

AMBW-21351 Query parameter types can now be edited in the REST binding. Query parametersare now defined for every REST operation instead of every service binding.

AMBW-21338 Swagger UI did not support fields for Basic Authentication.

AMBW-20990 The Connection Header field was not populated in a SOAP service request.

AMBW-20406 Users were unable to use an Invoke activity that had a reference inside an Eventhandler. The Invoke activity could reference to either a subprocess or an externalservice.

AMBW-19616 Changes were not saved when parameters in the Resource Service Path of a RESTService Binding were altered without pressing the Enter key.

AMBW-19194 The error REST Service Binding configuration error was thrown if unrelatedREST bindings were deleted.

Release 6.3.1

Key Description

AMBW-21786 The HTTP transport property header Set-Cookie was not available in SOAPReference binding.

AMBW-21723 When the element used to configure the REST service was a long, float, or doubletype Number, incorrect datatypes were represented in the generated Swagger APIdocument.

AMBW-21647 If an Invoke activity timed out in an application configured to use SOAP/JMSbinding, JMS Resources were not released and a memory leak was observed.

48

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21422 If SOAP services contained complex unbound headers and multiple bindings,SOAP headers were duplicated in the request message, which caused run timefault generation.

AMBW-20757 The Render JSON activity incorrectly converted empty string values to Nullvalues. Empty string values are now properly converted to empty string("").

Release 6.3.0

Key Description

AMBW-20231 Adding a new REST Service removed the custom HTTP header from the RESTschema.

AMBW-19998 If an external SOAP reference binding was configured to use a concrete WSDL froma shared module, an error was thrown when trying to start the process.

AMBW-19915 When a SOAP/JMS request reply application was running, temporary queues werenot deleted after a response was successfully returned.

AMBW-19750 Due to an incomplete refactoring of the process service, binding validation errorswere not displayed in Business Studio. After the service was run, an exception wasthrown.

AMBW-19717 WSDLs from shared modules could not be used to configure an "Unbound Header"for a service in the application module.

AMBW-19695 When a HTTP Client resource was configured with the Apache Commonsimplementation library, the Basic Credential Mapping policy did not work forSOAP Reference Binding and HTTP Activities.

AMBW-19612 If the Concrete WSDL referred to a schema that contained a complex type and anelement that were using the same name, only one of these was included in theConcrete WSDL.

AMBW-19139 Service Reply did not propagate the CorrelationId present in the Service Request.

AMBW-19099 The Reply Fault activity faulted with the exception Reply activity was unableto send reply using partner link.

AMBW-19089 SOAP Service binding now exposes the remote address header value in the requestcontext.

AMBW-18784 The SOAP response from SOAP server (MFT) failed with the Cannot find XMLdata type: {http://schemas.xmlsoap.org/soap/encoding/}string error.

AMBW-18232 Response context did not display the response code.

AMBW-18170 If a SOAP request is not well formed, the validation exception can now be caught atthe process level.

Release 6.2.2

49

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-19523 WSDL generation for SOAP and JMS binding failed when module properties wereused in JMS Connection shared resources in the shared module.

AMBW-19320 A ClassCast exception was thrown when processing a SOAP request. This has beenfixed.

AMBW-19152 The HTTP bindings were unable to handle flow control requests. This has beenfixed.

AMBW-19139 The SOAP/JMS service response did not propagate the JMS CorrelationId that waspresent in the service request. This has been fixed.

AMBW-18657 When using Policy Director, the security context set after authentication in HTTPcan now be propagated to SOAP binding and a credential mapping policy can useit for outbound requests.

AMBW-18543 Design time errors and run time errors were not thrown after you clicked Fetch.

AMBW-18517 The Invoke activity always timed out after 30 second irrespective of the valuespecified in the Invocation Timeout field of the Invoke activity. This has been fixed.

AMBW-13999 Deleting a REST Component resulted in a permanent loss of the Bindings.

AMBW-4297 JDBC Activities did not throw exceptions when unsupported queries were entered.

Release 6.2.1

Key Description

AMBW-18076 Creating schema as part of creating REST Resource led to REST Service bindingconfiguration error.

AMBW-18059 When a service with no input was invoked using TIBCO ActiveMatrixBusinessWorks 6.2, the SOAP request was sent as Document/Literal even thoughRPC/Literal was used.

AMBW-18050 A 404 Not Found error was encountered if base path name is same in the Pathparameter and Query parameter in the Resource Service Path field. For example,REST Resource having Resource Service Path as /books/{isbn} or /books?isbn={isbn} in a project which already has resource with path as /books, threwan error.

AMBW-17932 QName picker did not display "xsd:included" components.

AMBW-17804 Concrete WSDL could not be generated for SOAP Service binding if the associatedHTTP Connector shared resource was defined in a shared module, and had fieldsthat referenced module properties.

AMBW-17581 SOAP client using HTTP Client shared resource did not use the specified proxyconfiguration to access the web service.

50

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17025 MTOM did not work where the root node of WSDL message's part was of "type"base64binary.

AMBW-11965 REST Bindings tab values were not serialized correctly if they were edited fromBindings tab of the REST service on the process.

AMBW-17696 The generated concrete WSDL did not contain elements from the schema that wasdefined in a shared module. As a result, some elements were reported to bemissing when this concrete WSDL was imported in a client.

AMBW-17427 The [Copy Of]option could not be used to map the output of the Mapper activityto invoke a web service.

AMBW-17156 An error was thrown when the SOAP response received from a SOAP servicecontained an incorrect namespace declaration.

AMBW-17090 The exported concrete WSDL did not include the schemas even when the "EMBEDSCHEMA" option was selected during export.

AMBW-16625 Refactoring the dependent WSDL namespace caused a TIBCO-BW-BINDING-SOAP-500020: Failed to initialize SoapServiceBinding error.

AMBW-16552[17495]

A SOAP client can now directly send a request to an ActiveMatrix BusinessWorksservice with a WSS username token header. If the governance agent is enabled, itenforces the policy.

AMBW-16317 REST services bypassed HTTP Basic Authentication even after LDAPConfiguration was provided on HTTP Connector shared resource. It did notauthenticate against the credentials.

AMBW-15931 When sending a REST request to invoke a REST resource using the Invoke RESTAPI activity, the authorization header was not added to the request.

Release 6.2.0

Key Description

AMBW-16218 When using an inline WSDL schema for REST service, a TIBCO-BW-BINDING-REST-500008: Error Occurred while creating User Part. Responding to

client with error message. exception was thrown at run time.

AMBW-14834 An error was thrown by the SOAP service if the SOAP address location containeda question mark character ("?").

AMBW-14694 Model/Model Schema in Swagger UI did not show anonymous complex typeelements which refer to another anonymous complex type.

AMBW-13807 REST Service Binding and Swagger UI did not support Optional QueryParameters at runtime even if they were defined as optional at design time.

51

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-11344 When you moved a process from a shared module into an application moduleusing Drag and Drop mechanism, the application that contained the applicationmodule was not updated to contain the shared module.

AMBW-14678 Service names, reference names, and binding names now support the use of Latinextended and CJK characters.

General

Release 6.4.0

Key Description

AMBW-27226 The module property, BW.ACTIVITY.NAME was unavailable in a spawnedsubprocess.

AMBW-27013 The $_error was missing in some activites.

AMBW-26949 TIBCO Business Studio™ became unresponsive when trying to reinclude ashared module. This has been fixed.

AMBW-26924 Conversations added to an event handler for a process could not be deleted,and the java.lang.NullPointerException error was thrown. This has beenfixed.

AMBW-26884 The debug log threw exceptions if the debug message text was formatted.

AMBW-26842 Coercion threw an error in TIBCO Business Studio if the coerced output of theParse XML was mapped to the Log activity.

AMBW-26730 TIBCO Business Studio became unresponsive during refactoring, when a set ofprojects or shared modules were deleted from a workspace. This has now beenfixed.

AMBW-26693 Test connection now works fine with module properties specified in theIdentity Provider Shared Resource for the LDAP Authentication SharedResource.

AMBW-26642 TIBCO Business Studio hung while creating a new process in projects withconflicting namespace schemas.This has been fixed.

AMBW-26626 When upgrading from ActiveMatrix BusinessWorks release 6.3.x, if thedatastore or group mode was used, the error PVM-MODEL-100306: PVM-MODEL-100306 (No message; locale=default) was thrown on startup.

AMBW-26594 The feature to reset variables in an iteration that was added in the ActiveMatrixBusinessWorks™ release 6.3.5, did not work for the message output of theInvoke activity.

52

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-26408 Starting an application while the AppNode it was deployed to was starting,caused a deadlock. This has been fixed, and the application can start after theAppNode has been started.

AMBW-26323 The error, Unable to obtain WSDL Interface details from the GenXDMWSDL Module was thrown when the application was started, when the WSDLincluded documentation elements.

AMBW-26321 Serialization of import locations across modules is now supported.

AMBW-26311 Modified the unique name generation scheme in schema cache to avoidcollisions in complex and simple type names.

AMBW-26301 Shutting down an AppNode with running applications shuts down the OSGIlayer, without stopping the AppNode. This prevented connecting to the OSGIconsole and debugging it.

AMBW-26294 The group and datastore persistence mode caused HTTP and JMS issuesinside an application when the activities, Wait For HTTP Request or Wait forJMS Request were used inside a subprocess.

AMBW-26285 Variables were not available for the input binding, for activities inside a Catchor CatchAll block.

The variables are now available inside the Catch or the Catch All block, andvalidation errors from migrated projects are now resolved.

AMBW-26264 Now Rethrow is not allowed in the process outside a Catch or CatchAll block.Restrictions have also been placed on the creation of the Start, End andCompensate activities in a process.

AMBW-26179 The SSL client in the JMS Connection Shared Resource failed if a moduleproperty was used in the Key Alias Name and Key Alias Password field, butran successfully only when a literal value was used. In this release, the SSLclient accepts module properties and literal values.

AMBW-26024 The boolean() function threw an error when a required element was missing inan activity, but the function runs successfully during run time. Now, the errorhas been switched to warning, as the boolean value works in run time.

AMBW-26114 TIBCO Business Studio hung when working with projects associated with theSVN repository. This has now been fixed.

AMBW-26003 Removing or renaming the Activator process now updates the activatorconfiguration section of the application module.

AMBW-26001 The fix improves the loading time for the debug launch configuration.

AMBW-25997 A new preference option has been added to persist the Build Automaticallyoption.

53

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25880 Debugger Job Data displayed wrong results for an XML schema inputcomposed of any type element and string element.

AMBW-25777 When adding a new XSD element in the schema editor, when a user entered aname that was different from the default name, Eclipse initiated an XSDelement rename refactoring. This has now been fixed.

AMBW-25543 The Generate Schema from JSON Payload utility failed when the payloadincluded NULL values. Now the wizard displays a list of the attributes thatwere changed from the NULL value to string, when parsing the payload.

AMBW-25499 References to shared resources were not entirely removed when they weredeleted using the Process Editor. This has been fixed, and unused processes nolonger linger in the project after they are deleted.

AMBW-24944 Empty sequences with attributes were populated with an error node. This hasnow been fixed, and now populating the child of a node when the node is anempty sequence, is prevented.

AMBW-24888 On Microsoft Windows 7, when creating a new subprocess, the Custom optionwhich is found under the Interface Mechanism field on the wizard, was notdisplayed when the display scaling was set to 125%.

AMBW-23945 When users add a description to a module property, the same description wasincorrectly applied to the other module properties in the project. This has beenfixed, and module properties now maintain individual descriptions.

AMBW-23931 After renaming an operation, new operation names appear in all other activitiesand references referring to the service or the operation.

AMBW-22882 When a user created a process from a WSDL that included a Shared Module,the process was created in the first Application Module that contained a processfolder. This has now been fixed, and when the process folder is missing, a newdialog appears with the list of projects using which you can select a processfolder from a different project or cancel the operation.

AMBW-22673 When a custom XPath function was created and the concerned class wasrenamed using the standard refactoring mechanism, that is, the custom XPathfunction, was not found under the list of functions.

AMBW-21518 In the process of creating new applications, when a new service was invoked,the WSDL prefix and WSDL operation name was saved, by default. This hasnow been fixed, and the service details will be saved only when the check boxRemember service details is selected.

AMBW-21075 When adding a new XSD element in the Eclipse XSD Schema Editor, if userentered a name different from the default name, Eclipse initiated a XSD elementrename refactoring, which caused an unrelated activity and updated the inputbinding incorrectly. This has now been fixed.

AMBW-19473 From the Component editor, multiple processes can be selected at the same timeand added as components for the Application Module.

54

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17151/AMBW-26259

After making minor changes and saving a process that contained the EMFgenerated prefix XML, some errors were thrown. The errors were thrownbecause the XML prefix violateed XML specifications. This has now been fixed.

AMBW-15756 The error, such error marker is not valid, was reported in the ProblemsView when removing a module dependency from an Application Module. Thishas been fixed.

AMBW-11853 A process that contained an XSLT with a substitution, threw a validationexception at run time, unless the process was explicitly importing the XMLSchema.

Release 6.3.5

Key Description

AMBW-26150 TIBCO Business Studio hung when the Salesforce object type was selected forcoercion on substitution.

AMBW-26148 A Null Pointer Exception was thrown when a sub process was called by anapplication that was running on an AppNode configured to use ftgroup mode.

AMBW-26119 Starting an application, while the AppNode it was deployed to was starting,caused a deadlock. This has been fixed, and the application can start after theAppNode has been started.

AMBW-26034 The sequence key did not work in the group mode when the key was set to avalue. The error Caused by: java.lang.NullPointerException: nullerror was thrown.

AMBW-25935 When multiple applications used the same application module or sharedmodule, and the application module or shared module contained a SharedResource that was referenced by these applications, the application failed tostart if the status of the Shared Resource was Degraded.

AMBW-25918 TIBCO Business Studio™ would hang when users removed shared modulesfrom the Application Includes page, which can be accessed from the ProjectExplorer view by fully expanding the application and double-clicking Includesunder Package Unit.

AMBW-25786 The bwinstall TIBCO EMS driver failed when the installation contained only therun time environment.

AMBW-25785,

AMBW-25754

An exception was thrown at run time, if binary shared modules containedencrypted process files. This has been fixed, and the encrypted process files cannow be parsed successfully at runtime.

AMBW-25771 When Shared Module with JNDI Configuration Shared Resource is used inmultiple applications that are deployed to the same AppSpace, configurationupdate for the JNDI Configuration Shared Resource in one application causesissues in the other application. This has been fixed.

55

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25718 Fixed an implementation bug in the handling of grouping in XSLT.

AMBW-25679 Mappings are maintained when copying and pasting a Call Process activityfrom one process to another.

AMBW-25660 When attempting to reference the attribute in schemas containing attributedefinitions, the TIBCO Business Studio™ mapping tool created a copy of theattribute and generated the following error:

Activity configuration error. The activity [Mapper] has input

configuration error. Rename to about.

AMBW-25659 Added a new section to the Installation guide that contains instructions on howto install and link TIBCO Enterprise Message Service™ client libraries from theTIBCO Enterprise Message Service™ installation. Refer to the section"Integrating with TIBCO Enterprise Message Service™" in the Installation guidefor more details.

AMBW-25643 Applications that had a JMS Queue Receiver activity did not work correctly ifthe engine was configured to use the ftgroup mode.

AMBW-25622 When an application with a Sleep activity was terminated in the debuggingmode, the application was not terminated. This has been fixed.

AMBW-25579 If the engine is configured for fault tolerance, and the AppNode failed to startafter failover, the application running on the AppNode was impaired.

AMBW-25571 The stackoverflow issue caused by circular dependency between sharedmodules has been fixed.

AMBW-25525 The $_error field for error transitions was not populated in the parent processwhen an error was found in the called process.

AMBW-25486 When copying and pasting a process in the same package, TIBCO BusinessStudio™ incorrectly allowed users to rename the new process to use the name ofan already existing process. Now, TIBCO Business Studio™ notifies users if aprocess with the same name already exists in the package.

AMBW-25424 Module properties are now supported in the Key field on the ReceiveNotification activity.

AMBW-25397 Schema variables were not getting resolved if WSDL and XSD files used thesame target namespace. To avoid this issue, ensure WSDL and XSD files usedifferent target namespaces

AMBW-25376 The process property in the Notify Configuration Shared Resource can now beconfigured to use module properties.

AMBW-24247 The variable list in an Iterate group was incorrectly reset when the JDBCactivity inside the group was refreshed.

56

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25351 A Null Pointer Exception was intermittently thrown in a migrated project whena service was added to a component in the Module Descriptor.

AMBW-23571 Updated the documentation for the "Load Balancing an Application Using anAppSpace" sample in the Samples guide to inform the users that to use the loadbalancing setup without fault tolerance you do not require the database. For theJMS Receive Message activity, load balancing is done by setting the flow limit.For the HTTP Receiver activity, load balancing is done at the external loadbalancer level.

AMBW-23940 Changing the com.tibco.pvm package logging level to DEBUG changed thefault response if an invalid SOAP request was sent.

AMBW-22281 When the input was a complex schema a service sub process could not bestarted from the TIBCO Business Studio™ process launcher.

AMBW-21735 Editing the sorting option in Statement tab will now give the correct commandon the XSLT level.

AMBW-20732 Elements in Iterate groups did not display attributes for the assigned schema.Only the simple and complex elements were displayed.

AMBW-16594 Empty module properties, that have String set as the data type, are allowed,irregardless of whether they are used by an activity configuration. Emptyprocess properties are not allowed. A validation error is thrown for emptyprocess properties, irregardless of whether they are used by an activityconfiguration.

Release 6.3.4

Key Description

AMBW-25515 Fixed memory leaks that occurred when subprocesses completed with a fault.

AMBW-25482 When users deleted shared modules, and re-imported the project, the CallProcess activity did not maintain the name of the subprocess it formerlyreferenced.

AMBW-25481 The Recover Activity IDs check box was re-enabled in the RepairBusinessWorks Projects wizard. Selecting this check box allows the Repair toolto recover the xpdl ID of the activity, or recreate the xpdl ID if it is missing. Toaccess this check box, launch the Repair BusinessWorks Projects wizard byright-clicking on the project and selecting Refactor > Repair BusinessWorksProjects....From the wizard, select the Recover Activity IDs check box. Followinstructions in the wizard and click Finish to repair the project.

AMBW-25188 The ProcessStack field in FaultDetails or ErrorReport has been fixed to showthe full stack trace for direct subprocesses.

AMBW-25089 Improvements made to indexing and XSD parsing reduced the amount of timeit took to import and validate large migrated projects.

57

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25027 A typo was fixed in the JDBC driver connector JAR files name.

AMBW-25003 The description for the timeout field was updated to "Specifies the waitingperiod for a message in milliseconds" in the "Get JMS Queue Message" topicfrom the Bindings and Palettes guide.

AMBW-24934 Coercion did not work when coercing multiple elements to the same type.

AMBW-24826 Changes made to module properties from the Module Property editor and fromthe Navigator View in the TIBCO Business Studio™ were not always saved.

AMBW-24814 If the engine was configured for the fault tolerance mode, and was using theMySQL 5.6 database, the CREATION and EXPIRATION time entries were notcorrect for pending messages pushed by the Notify activity.

AMBW-24704 When generating the EAR file from TIBCO Business Studio™, a Null PointerException error was thrown if ActiveMatrix BusinessWorks™ Plug-in forActiveSpaces® and ActiveMatrix BusinessWorks™ Plug-in for EDI wereinstalled.

AMBW-24645 Oracle database permissions were updated in the "Configuring bwagent forOracle and TIBCO FTL" and "Configuring bwagent for Oracle and TIBCOEnterprise Message Service" Administration guide topics.

AMBW-24606 Duplicates of subprocesses and the Start activity were incorrectly shown in theprocess launcher view.

AMBW-24244 The bwdesign command, ignored the -name parameter in the non-interactivemode. The EAR file was created with the same name as the project that wasbeing exported.

AMBW-24163 After migration, the command variable element was not present in the DataSource tab, for mapping.

AMBW-24113 Adding coercion to multiple Activity Data sources did not work. Coercionadded to the first element was successful, but was lost when it was added tosecond element.

AMBW-24101 After migration, TIBCO Business Studio™ was unresponsive indefinitely whena folder was moved to the process directory.

AMBW-23859 A database lock exception was intermittently observed in the managed faulttolerance mode, in the AppSpace when MySQL and SQL servers were used.

AMBW-23747 When the bwadmin bwenginedb command was used, an error was thrown, andusers were not able to view database related information if the engine wasconfigured with database.

AMBW-23443 The example provided in the tooltip for the Resource Service Path field in theREST Service Window was improved.

58

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-22855 When editing properties from the Properties Editor in TIBCO Business Studio,the values of properties that were changed to strings were not preserved.

AMBW-22511 The ActiveMatrix BusinessWorks™ product version was updated to the mostrecent version when viewing product details in TIBCO Business Studio™.

AMBW-22197 The Null Pointer Exception was thrown, and the bwdesign export commandfailed to generate the EAR file if the project name and the application namewere not the same.

AMBW-22062 In some cases, the timeout value for the Invoke activity was not saved properlyif it was changed multiple times.

AMBW-21822 Installing ActiveMatrix BusinessWorks™ would prompt the user to install Java 6on Mac OS X.

AMBW-21804 Process properties that were defined on an activity were deleted if the activitywas removed from the process.

AMBW-21522 If a Surround with ForEach group was applied to an element that was currentlypart of a For Each group, the current-group() Xpath function did not displayunder the Data Source tab.

AMBW-21500 A process cannot be created in a shared module by selecting Overview > CreateBusinessWorks Process.

AMBW-21200 Iterate groups did not accept values from schemas without a target namespace.

AMBW-21134 When a process file was moved from one folder to another folder, two threadswere concurrently triggered, which caused deadlock.

AMBW-20392 Updated documentation for " Configuring Database for the Engine" in theAdministration guide to inform users that a different database instance shouldbe used for each AppSpace, and to do this with a single database, a tablespaceor schema would need to be created for each AppSpace.

AMBW-15804 When using the bwdesign utility an error was thrown while exporting a largeEAR file because the export process did not wait for the EAR file to finishgenerating. This corrupted the EAR file, and the file could not be decompressedafter it was exported.

Release 6.3.3

Key Description

AMBW-24604 If no component process was selected, the Debugger did not validate processselection.

59

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-24463 ActiveMatrix BusinessWorks incorrectly tried to look up namespaces on thenetwork when loading a schema from a shared module that contained a targetnamespace corresponding to a network host, for example, ns.tibco.com.

AMBW-24408 When debugging a direct sub process, the process launcher loaded the incorrectschema element as the input element of the request message.

AMBW-24393 Calling the parent process failed after executing the Activator Process forOnStartup containing a Call Process activity.

AMBW-24310 While working in the Process Launcher view, users could not enter input fordirect sub processes.

AMBW-24059 Imported projects took a long time to open in Business Studio becauseexternally located documents were not getting resolved.

AMBW-23857 If a message failed on the SOAP Reference binding, the Java ClassCastExceptionerror message was thrown instead of the ActiveMatrix BusinessWorks errorcode and message.

AMBW-23699 When a Call Process activity called a direct subprocess, that was defined in theShared Module, and the Shared Module was restarted, a Null Pointer Exceptionwas thrown.

AMBW-23582 Recovery of check-pointed jobs failed when using Managed Fault Tolerancewith Oracle database.

AMBW-23540 The issue of column names appearing twice on the tabs in the ModuleProperties editor has been fixed.

AMBW-22852 Module properties, that were part of a property group, can now be selectedwhen configuring an activity.

AMBW-22273 The Invoke activity timeout attribute can be set to module property of typeString or Integer, by selecting the required type in the drop down option addedin the Activity Timeout field.

AMBW-22268 TIBCO ActiveMatrix BusinessWorks now supports RAC on Oracle 12C forbwengine.

AMBW-21885 The Migrate BW Projects... menu option in Business Studio was incorrectlyshown under the Import wizard menu.

AMBW-21451 Joining a conversation failed when the persistence mode was set to group.

AMBW-20502 Removing an unused schema from a project did not remove the dependency ofschema from the process.

AMBW-18366 The No Schema with target namespace found in the module errors werethrown when users migrated BusinessWorks 5.x projects to BusinessWorks 6.x.

60

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17807 When working in Mac OS X, the xpath expression was properly updated for theSequence Key field after users selected OK in the xpath builder editor.

Release 6.3.2

Key Description

AMBW-23806 The cache did not properly resolve schemas when the bwdesign exportcommand was used for complex projects.

AMBW-23207 If an array type was used in the JSON Request Body for the REST ServiceBinding, an incorrect Swagger was generated under the Service Descriptorsfolder.

AMBW-23127 For some nested schema imports Business Studio did not manage the sharedcomponents properly.

AMBW-22681 The resource tree locked exception was thrown while refreshing an internalrepository file when running the bwdesign tool.

AMBW-22676 Infinite recursion, that occurs if nested coercion contains cyclic schema types, isnow prevented.

AMBW-22660 Database locks were not detected when the engine was started.

AMBW-22658 A NullPointerException was reported when a Group contained the Replyactivity.

AMBW-22497 When importing dependent schemas, schema references were not alwaysproperly resolved when the application was started.

AMBW-22494 The AppNode status hung if an application used JDK 1.7, or later versions ofthe software, and allowed unsynchronized access from multiple threads.

AMBW-22055 The enablestats command for processinstance failed in TIBCOActivematrix BusinessWorks 6.3.0.

AMBW-22053 A Shared Module was not added as dependency after a Module Property,which was pointing to a Shared Resource from a Shared Module, wasreferenced in the Application Module.

AMBW-22037 Users could not create new projects in Business Studio if the region andlanguage format in their operating system was set to Thailand.

AMBW-21898 Custom plugins could not be installed in Business Studio.

AMBW-21803 When configuring Authentication and Confidentiality for the HTTP ClientShared Resource, an incorrect label displayed when users hovered over the ...icon.

61

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21713 The dbconnectionurl property value was corrected in the Administration guidetopic "Database with TIBCO Enterprise Message Service Configuration forbwagent".

AMBW-21677 The XML model miscalculated prefixes when ancestor nodes contained twodifferent prefix mappings for the same namespace and the current Appnoderemapped one of those prefixes.

AMBW-21402 When the engine persistence mode was configured for datastore mode, theduplicate key detection feature did not work with the PostgreSQL database.

AMBW-21167 Business Studio was unable to send the first EMS message to the EMS serverafter restarting. However, the subsequent messages were successfully sent tothe EMS server.

AMBW-21115 When users right-clicked on a module property in Business Studio, the menuincorrectly displayed duplicate options, and some options did not work.

AMBW-21083 Business Studio failed to add the necessary xslt parameter when a parameterreference followed an asterisk (*) in an xpath.

AMBW-20977 When the Create New Process Property button was used, while creating a newprocess property for a process starter, the error, llegalStateException:Cannot activate read/write transaction in read-only transaction

context was thrown.

AMBW-20900 The error java.lang.reflect.InvocationTargetException wasintermittently thrown in Business Studio if users had configured an applicationmodule to use a shared module contained within another shared module.

AMBW-20725 After creating a new process and launching it in the Debugger, an exceptionwas thrown.

AMBW-20720 When elements of data type any were coerced, their sibling elements were alsocoerced.

AMBW-20530 Business Studio did not support text content in XSLT files. In the Mapperactivity, after mapping a text variable for the first time if you move to anothertab, the text node disappeared from the UI.

AMBW-20368 Activities that the user had set to be hidden in Business Studio were incorrectlydisplayed in the Palettes pane if the user created a new process.

AMBW-20297 When the bwdesign import utility was executed from the command line, andthe job failed, an errorlevel of 0 was incorrectly returned.

AMBW-19982 Migrating large projects took a long time to complete.

62

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-19768 If an activity did not include a transition to the next activity, and the activitywas renamed, the name change was not reflected in the XPATH expression ofthe next activity.

AMBW-19718 From Business Studio, processes were not successfully copied and pasted to theComponents folder.

AMBW-19530 Nested inner loop accumulation did not reset on entry of each inner loop. Onsubsequent iterations of the inner loop, the accumulation variable of the innerloop contained accumulation values from the previous inner loop iterations.

AMBW-18516 While mapping a repeating element in the design time, the correspondingruntime XSLT was not generated properly. It missed one of the xsl:paramelement in the runtime XSLT.

AMBW-18219 An exception was thrown, and users were unable to connect to bwagentconfigured for SSL from the Business Studio Deployment Servers View.

AMBW-18079 Inline schemas that lacked a targetNamespace attribute, threw the Null PointerException, when used in a project.

AMBW-17968 The value of the module property was not displayed in the combo box whenthey were selected on the Shared Resource.

AMBW-17550 When data was mapped from one mapper to another mapper, the schema thatwas produced incorrectly contained unused namespaces.

AMBW-15154 Large TIBCO ActiveMatrix BusinessWorks 5.x projects took a long time tomigrate to TIBCO ActiveMatrix BusinessWorks 6.x. After fixing errors in themigrated project and saving the project in the workspace took a long time tobuild.

Release 6.3.1

Key Description

AMBW-21937 When an application was deployed from Business Studio using the Deploymentservers option, deployment failed with an exception.

AMBW-21871 Applications did not start properly when Managed Fault Tolerance wasconfigured at the AppSpace level to use an external database and TIBCOEnterprise Messaging Service for data persistence and transport. This has beenfixed. To recreate the database, use the updated database scripts at<TIBCO_HOME>\bw\6.3\config\dbscripts\engine. For example, if you areusing an Oracle database, execute the updated database scripts at<TIBCO_HOME>\bw\6.3\config\dbscripts\engine\oracle.

AMBW-21870 Corrected a race condition that under certain circumstances could cause a falsevalidation failure in the Parse XML activity.

63

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21868 When sending email with attachment failed, the Send Mail activity did notrelease the lock on the file that was specified as the attachment.

AMBW-21847 Duplicate references forced the cache to require schema locations where theywere not needed. So, duplicate references to documents in the document cacheare no longer created.

AMBW-21806 Duplicate references forced the cache to require schema location attributeswhere they were not needed. So, duplicate references to documents in thedocument cache are no longer created.

AMBW-21649 Managed fault tolerance did not work if a schema used in an applicationprocess did not have a targetnamespace. This has been fixed. To recreate thedatabase, use the updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts\engine. For example, if you are using an Oracle database, executethe updated database scripts at <TIBCO_HOME>\bw\6.3\config\dbscripts\engine\oracle.

AMBW-21646 Failed to update the bundle when modifying a running application in BusinessStudio.

AMBW-21587 Nested Coercions did not work in the Mapper. This has been fixed.

AMBW-21583 Documents which depend upon an imported document's included document'scomponents are now properly resolving those references. WSDL documentswith annotation and documentation elements are now also properly parsed.

AMBW-21577 When BusinessWorks applications used schemas with no target namespace, thefollowing error was thrown:no xsd for this imported location

AMBW-21189 The Invoke activity can now be used with the Accumulate Output feature forgroups. Users can now select Invoke as output activity if it has just oneMessage->PartName->XSDElement as its output.

AMBW-20698 BusinessWorks applications failed to start properly after a process was modifiedand saved while the Debugger was running.

AMBW-20434 The bwagent resgistration URL provided in documentation was incorrect. It hasbeen updated to http://<TEA_HOST>:8777/tea/.

AMBW-7649 Error Transitions from an event source and group box are now supported

Release 6.3.0

Key Description

AMBW-21352 When large project containing modifications was saved, the entire project wasrebuilt.

64

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21347 For large projects, Business Studio hangs at "Building Workspace" whencreating error markers.

AMBW-21256 Exceptions thrown by conditions on transitions were not handled by theCatchAll activity and threw the ClassCastException.

AMBW-20851 The process launcher did not show the input request for all sub processes andshowed the incorrect input while adding a new sub process.

AMBW-20758 If an importing schema contained a targetNamespace that did not exist in aformerly imported schema, the application failed and threw the following error:

No xsd for this imported location

AMBW-20699 A memory leak was observed when the XSLT processor processed schemaswith import statements.

AMBW-20590 If a WSDL contained nested schemas, an exception was thrown and theapplication failed to start.

AMBW-20500 An exception was thrown when the XSD and WSDL schemas were not resolvedduring design-time validation.

AMBW-20459 When BusinessWorks applications used schemas with no target namespace, thefollowing error was thrown:no xsd for this imported location

AMBW-20453 The Issue of using XSD Include with chameleon schema has been resolved.

AMBW-20410 When the engine used the HTTP protocol to look up a namespace, there was asignificant delay when applications were started.

AMBW-20374 For certain complex hierarchies of schema types, for example, circular typereferences within a chain of schema types' content models, type references werenot resolved properly.

AMBW-20298 Running BusinessWorks Studio on Windows 8.1 threw the following error onstartup: com.tibco.bw.tpcl.org.hyperic.sigar, Missing native codematch sigar-x86-winnt.dll.

AMBW-20296 The custom fault data from nested sub-process invocation was not directlypropagated to the main process.

AMBW-20266 BusinessWorks Studio did not display complex items with an asterisk (*) iconwhen the maxOccurs attribute was set to a finite number.

AMBW-20201 The element of a WSDL was being referred by incorrectly using the <include>tag in the BusinessWorks process file.

AMBW-20148 A NULL pointer exception was reported repeatedly at design time. The errorwas thrown when the existing schema from the input editor of an activity wasreplaced, and the new schema mapping was configured.

65

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-20009 When Business Studio used the HTTP protocol to look up a namespace, therewas a significant delay when applications were started.

AMBW-19992 A memory leak was observed when the engine mode set to Memory mode andthe application was redeployed multiple times.

AMBW-19982 Migrating large projects from BusinessWorks 5.x to BusinessWorks 6.x took along time to complete.

AMBW-19968 When a nested iterative group's variable list mapped with complex elements theerror Adding definition failed for process was thrown.

AMBW-19932 Given a scenario a shared resource referenced another shared resource in ashared module, and that shared module was included in multiple applicationsrunning on the same AppNode, lifecycling any of the applications changed thestate of other applications to be Impaired.

AMBW-19870 The application intermittently failed to start and its status changed to Impairedafter the AppSpace was stopped and the application was undeployed and re-deployed.

AMBW-19863 Iterate group did not include the referred schema and threw the followingerror:

java.lang.Exception: Unresolved reference

AMBW-19859 Business Studio hung when a large project was migrated in Business Studio,and when the project was built in the workspace.

AMBW-19858 Business Studio is now able to build a project with complex sets of schemas anddoes not show the StackOverflow error.

AMBW-19844 Exceptions were observed in the log when a new WSS Provider policy wascreated in Business Studio.

AMBW-19834 Process files that were created in TIBCO ActiveMatrix BusinessWorks 6.2.1 andcontained errors could not be opened in ActiveMatrix BusinessWorks 6.2.2.

AMBW-19810 The TIBCO ActiveMatrix BusinessWorks 6 schema resolver failed to properlyresolve referenced components when using the Swift plug-in.

AMBW-19685 When a user created a new Service in an existing process using an existing XSD,the XSD was incorrectly modified.

AMBW-19677 The attribute fields modifiedOn and modifiedBy were updated after a changewas made to a process file. This behavior caused conflicts during filesynchronization when working with a revision control system.

AMBW-19664 When the option Refactor > Rename XSD Schema namespace was used tomodify the namespace of the XSD file, an exception was thrown.

66

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-19654 If an Invoke activity had an ActivityContext element, but the PartnerLink of theInvoke activity did not have a context parameter, the serialization of the Invokeactivity threw an exception, and the process could not be saved.

AMBW-19634 The bwdesign utility was unresponsive after generating EAR files for theprojects.

AMBW-19607 On Microsoft Windows 7, the AppNode would not start and the errorjava.util.zip.ZipException: Exception in opening zip file: wasthrown if the TIBCO_HOME directory name contained a space.

AMBW-19590 Shared module dependencies were not automatically added to theDependencies section if a shared resource was being used in the sharedapplication module.

AMBW-19557 Group accumulate failed when the same target namespace was found inmultiple schemas.

AMBW-19503 The CatchAll block did not handle exceptions or errors thrown by incorrectexpressions on transitions.

AMBW-19478 An option to add multiple coercions for an abstract element was not available inBusinessWorks 6.x.

AMBW-19412 Using the user defined prefix to access the WSDL elements instead of thedefault tns element caused errors during runtime.

AMBW-19407 The SOAP Reference binding was not properly updated if the HTTP Clientshared resource was renamed, deleted, or removed.

AMBW-19379 If the location of module properties for a deployed application was updated,and the AppNode that the application was running on was restarted andredeployed, the application failed.

AMBW-19325 Starting a simple process containing a very complicated schema threw the error,Failed to resolve Schema java.lang.AssertionError: provider

cannot be null.

AMBW-19199 When using a group, job data could not be viewed in the debug mode.

AMBW-19106 With the current implementation it was not possible to retrieve the statistics forindividual activities or processes.

AMBW-19041 The Stale Transition Warning message continued to be displayed even aftercleaning and re-factoring the project.

AMBW-18954 When a new process property was created from the General tab, an errormessage incorrectly displayed.

67

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-18982 In Business Studio, module property names and their values were truncated inthe Module Property Selection drop-down menu if they contained more than64 characters. The number of characters that display in the Module PropertySelection drop-down menu was increased to 128.

AMBW-18901 Error transitions are now available for all activities and groups in BusinessStudio.

AMBW-18900 In Linux, the parameter type could not be selected from the drop-down menuwhen it was being configured in the properties view of a REST Service Binding.

AMBW-18898 Studio no longer throws error Selected schema element's targetnamespace cant be empty! if the namespace in the target XSD was notdeclared.

AMBW-18706 Migrated projects did not have the System Module properties.

AMBW-18586 Job data was missing from the Job Data view in the main process when thecalling subprocess reached to breakpoint in the debug mode.

AMBW-18566 After a project was migrated from TIBCO ActiveMatrix BusinessWorks 5 toTIBCO ActiveMatrix BusinessWorks 6, the XML attribute in the process wasmissing if the attribute in the Call Process activity used a constant value.

AMBW-18565 The migration tool threw an error if all the WSDL services in the project werenot implemented.

AMBW-18464 After migrating a project from BW 5.x to BW 6.x, a literal string with a value of"true" was translated to a boolean function true().

AMBW-18448 If an application is redeployed, and the latest version of an application is notprocessed during the application start up, the status displays as Degraded inthe Admin UI.

AMBW-18305 When JDBC activity output changed, an iteration element did not update withthe new changes.

AMBW-18271 Activity timeout in the Invoke activity did not support Module Properties.

AMBW-18092 When the Copy-Contents-Of option was selected during mapping, the errorPVM-XML-106018: Expression Creation Error: '<?xml version="1.0"

encoding="UTF-8"?> was thrown at runtime.

AMBW-18005 The Activity output configuration error was thrown when the Invoke activitywas renamed or a dummy change was done to the name.

AMBW-17870 The following error was shown in Business Studio when the EXISTS() XPathfunction was used with the activity output to check if the activity was executed:

Effective boolean value of a required component is always true

68

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17082 Changing the reference in a process to use a new port type did not clean up theold references inside the process.

AMBW-17033 JAXWSInterop sample (binding > soap > http > JAXWSInterop) threw 'Activity[JavaInvoke] fault' when deployed in Admin.

AMBW-15253 The schema parser, when checking for cycles in model groups, did not properlyexclude the contents of element particles.

AMBW-13932 If a global variable name and the iteration group's Iteration Element field namewas the same, the migration tool generated a unique name for the iterationelement.

AMBW-12263 When a user defined a fault context variable at the Port Type level, that contextdid not work at run time. Operations might define multiple faults, so it wasdifficult to determine the fault that should be used for each operation.

Release 6.2.2

Key Description

AMBW-19319 The execution statistics such as Total Elapsed Time, Minimum Elapsed Time,and Maximum Elapsed Time were incorrect for completed jobs. For failed jobs,default values were incorrect. This has been fixed.

AMBW-19150 Due to an error in the lookup of certain OSGi bundle entries, applications failedto start and the following error was thrown: TIBCO-BW-SCHEMA-RESOLVER-500204: Failed to resolve WSDL. This has been fixed.

AMBW-19121 The XML model miscalculated prefixes when ancestor nodes contained twodifferent prefix mappings for the same namespace and the current noderemapped one of those prefixes. This has been fixed.

AMBW-19006 The circular reference inside the schema was invalid in TIBCO ActiveMatrixBusinessWorks 6.x.

AMBW-18891 The runtime behavior of a process was inconsistent if the process contained aschema (schema A) with an element declaration whose substitutionGroupmembers were in other schema (schema B and C) which included schema A.This has been fixed.

AMBW-18966 The values computed for TotalElapsedTime and TotalExecutionTime wereincorrect. This has been fixed.

AMBW-18864 When Iterate group is configured with a local xsd element that contained the@nill attribute, the @nill attribute had to be recognized and handled inside theProcess file.

AMBW-18863 A false design-time validation was reported when a process referred to aschema embedded within a WSDL, and the target namespace of the schema andthe WSDL was different. This has been fixed.

69

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-18795 Fixed the latency on the debugger GUI, which was observed to be greater thanusual.

AMBW-18698 An XSD with a null element was not resolved correctly when used in the outputeditor. This has been fixed.

AMBW-18675 When an XSD with no namespace was imported, the following message wasobserved on the Problems tab: "Unable to load model for the Process[Process.bwp] due to error". Closing and reopening this project caused thefollowing error: "Could not open the editor:org.eclipse.core.runtime.CoreException: The file is invalid on Business Studio."This has been fixed.

AMBW-18659 The bwdesign utility failed to validate the sample BookStore project. This hasbeen fixed.

AMBW-18656 The XPATH expression within the variable list was being shortened aftermigrating a project from BW5 to BW6. If the expression was modified to be thecorrect value, it was shortened again and an error occured at run time whenusers tried to run the project.

AMBW-18623 When using the Maven plugin, validation failed if an application contained ashared module with activities or shared resources from the FTP Palette. This hasbeen fixed.

AMBW-18622 When using the Maven plugin, the generated POM (pom.xml) for a sharedmodule contained an incorrect TIBCO_HOME if a non-default TIBCO_HOMEwas specified in the Maven Configuration Details dialog. This has been fixed.

AMBW-18191 An error, Cannot find XML element, was observed intermittently at runtime ifsome specific namespaces are not imported in the WSDL. The intermittentnature of this issue was caused by the changing order in which WSDLdocuments were processed. This has been fixed.

AMBW-18094 An error was thrown when the user tried to start an application deployed to theTEA server.

AMBW-17082 If you removed an WSDL that was formerly referenced in a project, butcurrently had no references in the project then you received an ImportConfiguration Error.

AMBW-17033 JAXWSInterop sample (binding > soap > http > JAXWSInterop) threw 'Activity[JavaInvoke] fault' when deployed in Admin.

AMBW-16038 A NullPointerException was thrown at runtime for projects that hadsubprocesses referring to an external schema.

AMBW-13955 After a component containing REST binding was deleted, it was not possible tore-create the component with the REST binding.

70

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

PER-2106 After decrypting an incoming SOAP message at the reference endpoint, thedecrypted message was not passed back in the message context. This has beenfixed.

PER-2095 A memory leak was observed when SAML authentication policies wereenforced. This has been fixed.

PER-2083 SAML 1.1 Token 1.1 option for SAML credentials mapping policy was unable togenerate SAML 1.1 assertion. This has been fixed.

Release 6.2.1

Key Description

AMBW-18289 When a Test Connection failed, the error message displayed on the dialogappeared truncated and the error message could not be copied using the clickand select option with the mouse. This has been fixed.

AMBW-18214 When assigning a value to a simple variable, the Assign activity failed with anexception if either format-Date, format-Time, or format-DateTime functionswere used. This has been fixed.

AMBW-18198 The Mapper did not fully populate the choice groups with availablesubstitutions. This has been fixed.

AMBW-18185 TIBCO Business Studio hung when an XSD schema was imported in theActiveMatrix BusinessWorks project before the dependent XSD schema.

AMBW-18163 Adding conversation to a Reply activity threw a NullPointerException.

AMBW-18114 When an iteration was included into a transaction activity, the input propertiesof the elements included in the iteration were not visible and could not bechanged.

AMBW-18057 NullPointerExceptions were thrown when the init method was called severaltimes with same conversation key and then followed by a join. This has beenfixed.

AMBW-18005 The configuration of the Call Process activity reported errors when theReference PortType was lost. This has been fixed. However, the fix requires youto reconfigure the Call Process and Reference activities with the appropriatesettings in order to save the updated configuration.

AMBW-17990 Validation error was thrown when "schemalocation" tag was removed from thexsd.

AMBW-17979 Mapping from a Receive activity to a SetSharedVariable activity was lost andvalidation errors were thrown when the focus was moved to some other activityand then returned to the mapping. This has been fixed. However, the fixrequires you to remap the given SetSharedVariable activity's input once in orderto store the design and runtime XSLT of the updated mapping.

71

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17960 When Iterate group was created, the "Variable list" element used in otheractivity displayed an Activity configuration Error.

AMBW-17824 References to schema elements were not resolved when projects were imported.

AMBW-17818 TIBCO Business Studio did not validate the restriction of a nested element atdesign-time. This has been fixed.

AMBW-17792 The Render XML XSLT function now includes namespace definitions in itsoutput.

AMBW-17772 When upgrading from version 6.2.0 to version 6.2.1 of the software, the installerreplaced the existing configuration and .tra files. As a result, any customconfigurations in the configuration or .tra files were lost. This has been fixedand the installer now creates a backup folder, <TIBCO_HOME>\bw\6.2\backupto store the configuration and .tra files before upgrading.

AMBW-17743 CatchAll block using XPath expressions in transitions threw XSLT compilationerror at application init time.

AMBW-17716 When a Shared Resource was configured with a non-existing module property,the runtime did not report an error.

AMBW-17728 The following issues caused by renaming a service or reference have been fixed:

● Renaming a service or reference caused the context mechanism to fail atruntime. This has been fixed and the appropriate context configuration isnow updated correctly.

● Renaming context parameters resulted in a BPEL Variable that had noelement.

● SetContext and GetContext activities lost their reference to a service orreference when it is renamed. Now they are updated with the new name.

Any projects (prior to HF3) broken due to renaming a service or reference, canbe fixed by renaming the service or reference in HF3.

AMBW-17695 When copying a scope with accumulation the old element appeared to becopied, but was no longer used. Since the variable was now invalid, it caused aruntime error.

AMBW-17608 When renaming an activity, there was a distinct pause between each keystroke.

AMBW-17607 Validation reported a false error when building an archive file if the applicationcontained a Java module.

AMBW-17606 When using coercions and substitutions in the Mapper, an element wasunresolved if it was not used elsewhere in the process. Now when a coercion orsubstitution is done, an import for the element's namespace is added to theprocess, which allows the element to be correctly resolved.

AMBW-17579 Mapping currentElement from Iterate group threw a validation error.

72

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17560 Summary: When debugging using step-into, the focus was lost when steppinginto a group within a group. This issue was observed when using the Debugview.

Workaround: Use the BusinessWorks Jobs view to debug using step-into.

AMBW-17510 REST, SOAP, and HTTP now support Basic Authentication.

AMBW-17500 Import location with HTTP URL in WSDL was not supported.

AMBW-17479 The FaultDetails generated in the CatchAll block was incorrect for activities thatthrow Data Validation Exception at run time.

AMBW-17462 The JDBC activities in a transaction group failed with a NullPointerException.This has been fixed.

AMBW-17451 The source $Variable node could not be mapped to the target tree. This has beenfixed. You can now drag $Variables of type element to map to the target tree.

AMBW-17414 Incorrect reporting of cyclic type errors by the XML Schema Parser has beenfixed.

AMBW-17397 An error was reported when loading projects that contain huge embeddedschema if a process was loaded before all of its schemas were available.

AMBW-17390 A "Failed to set CLIENTID" error was thrown, if the JMS Connection used bythe deployed application was defined in a shared module.

AMBW-17330 When a Confirm activity was used inside an exception scope (like CatchAll), itdid not show the ConfirmEvent.

AMBW-17133 The addBooks operation in the REST Bookstore sample added only up to threebooks at a time. This has been fixed.

AMBW-17131 A design time validation error appeared on Set Shared Variable activities if theyused a web service element mapping directly. This mapping error persists in thecurrent product version, but you can resolve the error by re-mapping the inputmanually.

Each activity with this problem will have an error marker whichneeds to be resolved manually.

AMBW-17083 When configuring JMS or JNDI shared resources, the UI selection toggled to"None" if you specified the username and password fields using moduleproperties. This has been fixed.

AMBW-17074 Changing the default value of a module property of type String from apredefined string to an empty string resulted in validation errors.

AMBW-17071 A runtime error was thrown when an XPath expression contained the wildcardcharacter '*' (any element).

73

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17070 The application validator did not complain when there were moduledependencies that were not included as part of the application.

AMBW-17046 ActiveMatrix BusinessWorks 6.x design-time validation / build took asignificant amount of time for complex BW6 applications. For example,applications that involved multiple modules and deeper inter-moduledependencies. Optimization has been introduced to reduce the validation andbuild time.

AMBW-17041 Mapper showed validation error when mapped to an iteration group.

AMBW-17011 The bwadmin "show apps" command showed incorrect status in the local mode.

AMBW-16997 When running an ActiveMatrix BusinessWorks application on MicrosoftWindows 2012, an error message, com.tibco.bw.tpcl.org.hyperic.sigar,was thrown during startup. This has been fixed. The error message no longerappears and the OSGi command appnodeprocessinfo works properly.

AMBW-16912 The custom XPath function failed with an error if the implementation containeda main method.

AMBW-16981 When running activities that have their input generated by an XPath expression(and not by an XSLT), a validation error "Content is not allowed in prolog" wasthrown.

AMBW-16939 When schema A imports B which includes non-chameleon C, the schema parsersometimes reported unresolved type errors. If it did report an error, then,during process execution, validation errors for elements pointing to thatunresolved type were thrown. This has been fixed. Note: This behavior wasobserved when the schemas were parsed in a certain order and may not be seenwith every import of a schema with a non-chameleon include.

AMBW-16923 A StackOverflow exception was thrown by unnecessary loading and reloadingof schema or WSDL components. This has been fixed.

AMBW-16846 Refactoring the HTTP Shared Resource name or package did not update theHTTP connector field in REST binding. This has been fixed.

AMBW-16831 Projects cannot be created with their names ending with .xsd or .wsdl. Thewizard prevents the creation of a project with such a name and prompts with an"Unsupported characters" message.

AMBW-16791 The default TIBCO Rendezvous port to enable Hawk microagents has beenupdated from 7500 to 7474.

AMBW-16759 The silent installation mode now supports the installation of the runtimecomponent alone over an existing installation of TIBCO ActiveMatrixBusinessWorks 6.2.0.

AMBW-16677 When you renamed a partner link or an operation, the framework did not notifythe Confirm activity. This has been fixed.

74

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-16625 Refactoring the dependent WSDL namespace caused an error "TIBCO-BW-BINDING-SOAP-500020: Failed to initialize SoapServiceBinding".

AMBW-16536 Using empty values in Module/Process property caused error in the project.

AMBW-16325 An exception, The org.eclipse.osgi plug-in is missing from thisconfiguration, was thrown when running an application if ActiveMatrixBusinessWorks release 6.1.1, ActiveMatrix BusinessWorks release 6.1.1 hot fix1,and TIBCO Enterprise Message Server 8.1 were installed in the sameTIBCO_HOME. This has been fixed.

AMBW-16213 In the Debug Launcher, only one application could be deselected. If you tried todeselect a second application, the first application would be selectedautomatically. This has been fixed and you can now deselect two or moreapplications in the Debug Launcher.

AMBW-16209 Complex elements were not visible on the Input editor. This has been fixed.

AMBW-16191 An application status was Impaired if the application module, the application,and the EAR file were at the same location with the same name. This has beenfixed.

AMBW-15396 During reload, the schema and wsdl caches failed to remove the stale versionsof their schema and wsdl resource files. Multiple cleans (or other operationswhich result in cache reloads) of projects with sufficient numbers of schema andwsdl resources resulted in a very, very large cache which took a very, very longtime to reload. That problem is fixed.

PER-2055 Basic and Username Token Credential Mapping are now supported. This fixrequires the use of ActiveMatrix Policy Director 2.0 with ActiveMatrixBusinessWorks 6.2. For example, this enables BW6 users to invoke ActiveMatrixBPM web services.

Release 6.2.0

Key Description

AMBW-16642 Product installation failed on Mac OS X with a dialog box requesting to installJava SE 6.

AMBW-16038 Summary: A NullPointerException is thrown at runtime for projects whichhave subprocess referring to external schema.

Workaround: None. The NullPointerException can be ignored if the RESTapplication can be accessed from web browser, and the application can bestarted and stopped as usual.

AMBW-15334 When a process contained two or more Error transitions, the input mappingsfor all but one of the activities using the error transitions were broken andcaused incorrect problem markers.

75

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-14958 Summary: During installation, if you choose not to download and install theOracle Elliptic Curve Cryptography Library, then projects containing a sharedresource configured with SSL fail at run time with the following error: A fatalerror has been detected by the Java Runtime Environment.

Workaround: If you have a different JRE installed in the system path and thatone has the library installed, remove the JRE from the system path and thenrelaunch TIBCO Business Studio.

AMBW-14789 While debugging, the F6 key could not be used continuously to step throughthe code as the focus was lost.

AMBW-14770 Creating a conversation for a process that included both a service or a referenceand a signal-in activity resulted in a corrupted process.

AMBW-14712 The size of the drop-down field for the Reply Activity's General Service wasminimal and did not show any content by default. To resize the window, youhad to select the drop-down field and enter the return key. This has been fixed.

AMBW-14577 Clicking on a process file in the Project Explorer and choosing "LaunchBusinessWorks Debugger" option did not start the ActiveMatrix BusinessWorksprocess. This has been fixed.

AMBW-14442 You can now copy and paste activities from one group to another within aprocess.

AMBW-13942 When uninstalling ActiveMatrix BusinessWorks and one or more of thefollowing plugins from a TIBCO_HOME all at once, if ActiveMatrixBusinessWorks was uninstalled first, then the uninstallation of the remainingplugin products failed. The affected plugins were:

● ActiveMatrix BusinessWorks Plug-in for CICS

● ActiveMatrix BusinessWorks Plug-in for Data Conversion

● ActiveMatrix BusinessWorks Plug-in for WebSphere MQ

AMBW-13090 An exception,com.tibco.bw.core.runtime.ActivityInputValidationException, wasthrown for a variable of long data type if the long value was greater than 6digits.

AMBW-11595 A NullPointerException was thrown when an AE activity was added to anActiveMatrix BusinessWorks process.

AMBW-7677 Module shared variable did not build its initial value correctly from XSDschema for the double-byte characters.

Migration

Release 6.4.0

76

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-27206 When the WSDL reference was configured in the Input editor the Mapperactivity migrated as an empty activity.

AMBW-26432 Mappings in the Call Process activity which were invoked from Service Processbroke if the Call Process activity had a WSDL schema reference.

Release 6.3.4

Key Description

AMBW-20896 XPath comments are now converted to the ActiveMatrix BusinessWorks™ 6.x.format when migrated from ActiveMatrix BusinessWorks™ 5.x.

AMBW-18591 The migration tool migrated all the global properties as process properties forevery process, regardless of whether they were used by the process or not.

AMBW-16406 When you migrated a project using the command line, the output schema in themigrated project was missing.

Release 6.3.3

Key Description

AMBW-24274 Schemas with different encoding are now supported in migration.

AMBW-24220 Selecting and migrating dependent processes is now supported. Click the SelectLinked Processes button, to migrate all the dependent processes under themain process.

AMBW-23580 There was an issue with refreshing the Data Format Shared Resource, on theParse activity. The Shared Resource refreshed only on un-mapping and re-mapping the data format.

AMBW-21089 When an ActiveMatrix BusinessWorks 5.x™ project containing an HTTP SharedResource with a space in its name was migrated to ActiveMatrixBusinessWorks™ 6.x, the HTTP Shared Resource is not correctly mapped in theTransport configuration of Soap Binding.

AMBW-18569 Input and output data that was set on TIBCO Rendezvous® activities was notmigrated properly.

AMBW-18511 Xpath functions with prefixes were not migrated correctly to ActiveMatrixBusinessWorks™ 6.x.

Release 6.3.2

77

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-22531 Processes that were created in TIBCO ActiveMatrix BusinessWorks 5.x , andcontained an Iterate group, did not successfully migrate to TIBCO ActiveMatrixBusinessWorks 6.x.

AMBW-21900 When an attribute was mapped from another attribute, the attribute value wasmissing after the projects were migrated from TIBCO ActiveMatrix BusinessWorks5.x to TIBCO ActiveMatrix BusinessWorks 6.x.

AMBW-20164 If an application, that contains a process using the Call Process activity, is notproperly migrated from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCOActiveMatrix BusinessWorks 6.x. if output details have not been set on the CallProcess activity.

AMBW-18512 Shared variables that were defined using a schema reference were not correctlymigrated from TIBCO ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrixBusinessWorks 6.x.

AMBW-18473 Mapping of the process $start/root to a process variable migrated incorrectly.

AMBW-18095 If an iteration element from an Iterate group was used as an input, the mappingbroke after the project was migrated.

AMBW-17825 Mapping for a repeating element was not properly migrating from TIBCOActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks 6.x.

AMBW-20038 TIBCO ActiveMatrix BusinessWorks 5.x projects did not migrate properly if theyused XSD files that did not use UTF-8 for encoding.

Release 6.3.1

Key Description

AMBW-20791 While projects were migrated, schemas were not loaded properly and facedencoding issues.

Release 6.3.0

Key Description

AMBW-20762 When migrating a BusinessWorks 5.x project with Java Palette activities toBusinessWorks 6.x, the migration wizard reported that the project being migratedis a java project.

AMBW-20726 Migration was not successful in 6.3.0 when the project contained a global variableof the password type.

AMBW-20034 SSL enabled JMS Connection references were lost after migration.

AMBW-19933 JMS Queue Requestor activities from BusinessWorks 5.x with message type set toXML text were not migrated correctly in BusinessWorks 6.x.

78

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-19861 An internal error occurred, and migration was aborted when large projects weretrying to be migrated from BusinessWorks 5.x to BusinessWorks 6.x.

AMBW-19559 After migration, projects in BusinessWorks 6.x failed at runtime as an additionalimport namespace with an invalid schemaLocation was added in the inline schemafile.

AMBW-19180 While migrating JMS Queue Sender activities from BusinessWorks 5.x toBusinessWorks 6.x, projects with message type Map and Stream were not migratedcorrectly, and became empty activities in BusinessWorks 6.x.

AMBW-18706 System module properties were missing from migrated projects.

AMBW-18594 After migration, coerced activity inputs are migrated correctly.

AMBW-18565 The migration tool did not implement all the WSDL services in a project.

AMBW-18472 Duplicate output transitions were created after using the migration script forBusinessWorks 5.x projects.

AMBW-18293 For migrated BusinessWorks 5.x processes, the <bpel:import> element did notcontain the namespace attribute for schema or WSDL references that did not havetarget namespace.

AMBW-15253 An error was encountered after migration if the schema has an import statementthat cannot be resolved and one for a namespace, that was never used in theprocess.

Release 6.2.2

Key Description

AMBW-18212 TIBCO ActiveMatrix BusinessWorks 6.x did not support sorting at the mapperstatement level. This has been fixed.

Release 6.2.1

Key Description

AMBW-18233 An Invalid SQL Exception was thrown after migration if the SQL query began witha space. This has been fixed.

AMBW-17476 Migrating TIBCO ActiveMatrix BusinessWorks 5.x projects using command linefailed if TIBCO_HOME name contained space.

AMBW-16744 An exception was thrown when you migrated a project that contained a folder witha space in the folder name. This has been fixed.

79

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-14688 When importing TIBCO ActiveMatrix BusinessWorks projects containing Java,HTTP or SMTP activities in TIBCO Business Studio, some processes might havebeen marked to be dirty (indicated by the * infront of the process name in ProjectExplorer). If these processes were opened, the Save button was enabled althoughthe user had not made any changes to the process. When this project was run inDebugger, the exception com.tibco.bx.debug.MismatchedModelException:Node Definitions don't match BPEL Activities was thrown.

Release 6.2.0

Key Description

AMBW-13832 After migration, the HTTP, JMS and Mail projects showed a duplicate header onthe Input tab.

AMBW-13566 XPath could not convert an integer to string automatically when the upstreamactivity had multiple level schema. This has been fixed.

AMBW-11189 The Java Custom Function activity did not migrate successfully.

AMBW-10891 Timer activity was not migrated and displayed as an empty activity after migrationon a non-English platform.

AMBW-10289 After migration, the Data Format shared resource reference was not generatedcorrectly for Parse or Render data activities.

Palettes

Release 6.4.0

HTTP Palette

Key Description

AMBW-26423 Requests were sent to the wrong port when the HTTP Send Request activity wasunder high load.

JDBC Palette

Key Description

AMBW-26752 When a timestamp value was inserted in an Oracle database, millisecond valueswere truncated to 000.

AMBW-26530 When the Process in Subsets option was selected in the JDBC Query activity,JDBC connections did not close.

AMBW-26390 Data direct oracle driver of the JDBC Connection Shared Resource now supportsthe LoadBalancing Connection property.

80

TIBCO ActiveMatrix BusinessWorks™ Release Notes

REST and JSON Palette

Key Description

AMBW-26410 When schemas were created from the Parse JSON activity, the XSD did notcontain the attribute elementFormDefault="qualified". The activity failedwith the error JSONParserException. This has now been fixed. Now when aschema is created from the Parse JSON activity, it works successsfully atruntime.

AMBW-26409 The ParseJSON activity threw an error when parsing a schema which used atype that was imported from a different XSD. This has been fixed now.

AMBW-26392 Decimal values are now not converted to the exponential form and conversionsgo through. An exception to this would be when 0 is present before the decimalpoint and 6 or more zeroes are present after the decimal point before a non-zeronumber. In this scenarion, the result is in the exponential form, for example,0.000000*XX where X is a number other than 0.

AMBW-20729 When configuring the Invoke REST API activity, path or query parameters werenot parsed correctly when a module property was used for the Resource Path.

JMS Palette

Key Description

AMBW-27101 The Connection Factory SSL password did not work when a module propertywas used. A run time error was thrown.

AMBW-27037 Even if the polling interval on the JMS Receive Message activity is set toseconds, internally TIBCO ActiveMatrix BusinessWorks™ treated the timeoutvalue in miliseconds. This has been fixed.

FTL Palette

Key Description

AMBW-25642 When the applications started, a duplicate FTP connection opened for each FTPDIR activity. This has now been fixed.

Mail Palette

Key Description

AMBW-25542 Relative path keystore certificate can be configured to SSL enabled SMTPresource.This has been fixed now.

Release 6.3.5

81

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JDBC Palette

Key Description

AMBW-26164 The JDBC Query activity threw a Closed Connection error if the Query Subsetoption inside a Local Transaction activity was used.

AMBW-25778 Upsert mode did not work if users had configured the JDBC Update activity forthe TIBCO Oracle Data Driver, and the activity was set to use a preparedstatement.

AMBW-25713 The Login Timeout field in JDBC Connection shared resource displayed msecsvalue instead of secs. This has been fixed to display secs.

AMBW-25678 Schema output was not refreshed in the stored procedure if the ResultSet UseSchema check box was selected. This has been fixed.

AMBW-25097 Toggling between JDBC Query activities that were in the same process causedissues when users selected the SQL button from the Statement tab to build aSQL statement.

AMBW-23265 DB2 is now supported with DataDirect drivers.

AMBW-22145 The SQL Direct, JDBC Call Procedure and the JDBC Query activities timed outat the default value of three minutes when the results from the database were notreceived within that period of time, not honoring the timeout value set by theuser. This has been fixed.

AMBW-24348 JDBC activities did not parse the datetime columns when the GMT was set toServerTimeZone.

AMBW-22098 The JDBC Call Procedure activity ignored the value set in the Timeout field.

REST and JSON Palette

Key Description

AMBW-25987 Special symbols like Euro (€) did not parse correctly in Json text, in the Genericmode. This is now fixed.

FTL Palette

Key Description

AMBW-24673 The FTL Subscriber activity allows the user to specify its durable name to allowit to dynamically create a durable listener.

Release 6.3.4

82

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JAVA Palette

Key Description

AMBW-21453 Module properties were not supported in the key field for the ReceiveNotification activity.

JDBC Palette

Key Description

AMBW-25466 Instructions for setting up custom drivers for run time were updated to let usersknow that the plugins folder is automatically generated after you export the JARfile.

AMBW-25415 If existing connections become stale, ActiveMatrix BusinessWorks™ failed to re-create the connection.

AMBW-24966 The data types BLOB and DATE did not work when they were embedded as aOracle table type. DATE was interpreted as xsd:date and BLOB threw a formatconversion error.

AMBW-23384 TIBCO ActiveMatrix BusinessWorks™ was unable to use functions that returnthe data type BIGINT if DataDirect drivers were used.

AMBW-23383 TIBCO ActiveMatrix BusinessWorks™ was unable to retrieve smallint valuesfrom the Postgres database if DataDirect drivers were used.

AMBW-22526 The JDBC Update activity failed to execute when the option, Insert if recorddoes not exist was used with SQL Server 2012 or 2014.

XML Palette

Key Description

AMBW-24900 The Render XML activity failed to validate XML messages if one of the elementshad a value supplied using a module property.

Release 6.3.3

HTTP Palette

Key Description

AMBW-24623 When a header was repeated in a HTTP fault response, the Send HTTP Requestactivity failed with the error, java.lang.ClassCastException:[Ljava.lang.String; cannot be cast to java.lang.String.

AMBW-23318 An exception was thrown, and the application failed to start, if the Send HTTPRequest activity in an application process tried connecting to a remote, andsecured, REST service configured to use a proxy server.

83

TIBCO ActiveMatrix BusinessWorks™ Release Notes

HTTP Palette

Key Description

AMBW-12732 Dynamic Headers for HTTP Send Request activity were partially migrated.After migration, the user had to re-map these missing dynamic header fields byusing original ActiveMatrix BusinessWorks 5.x mappings in reference.

JDBC Palette

Key Description

AMBW-24791 If a JDBC connection was marked as invalid after creation, the active connectioncount was not decremented, which prevented new connections from beingcreated if the max connections value was reached.

AMBW-24446 The internal lock was not released when a database connection was notsuccessful. This caused the thread to freeze and the thread did not continue theexpected execution.

AMBW-24138 Activities from the JDBC Palette threw a JDBC Timeout Exception if the queryloads too large for the connection pool could handle.

Java Palette

Key Description

AMBW-24008 Improvements have been made to the performance of the Java to XML activity.

JMS Palette

Key Description

AMBW-24033 The JMS Application Properties editor did not set the cardinality of the element.

AMBW-24032 When configuring the security settings of the JMS Connection Shared Resource,a NullPointer Exception occurred if the user name and password in the JNDIResource were not set.

AMBW-23955 An error was thrown if the the JMS Receiver activity received a message thatwas configured to use application properties, but did not contain any applicationproperties.

AMBW-22662 If the JMS Connection Shared Resource was configured with a Keystore SharedResource, the JMS Connection Shared Resource failed to initialize when amodule property was used for the Keystore URL field.

AMBW-22488 The JMS Receiver and Get JMS Queue Message activities threw a validationerror if the JMS client sent a message with JMSXGroupID and JMSXGroupSeqheader properties.

84

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JMS Palette

Key Description

AMBW-21866 Attempts to reconnect to the JMS Request Reply activity failed after the EMSserver was restarted.

AMBW-20889 JMS test connection failed when a module property was used to configureKeystore URL field.

AMBW-16250 The JMS Request Reply activity threw a warning if the Reply To Destinationfield was specified on the Input tab instead of the Advanced tab of the activity.

AMBW-10770 An exception was not thrown if messages sent to the WebSphere MQ queue weremore than value specified by the MaxQDepth property.

Mail Palette

Key Description

AMBW-24217 The text body content is now sent in byte array.

Parse Palette

Key Description

AMBW-12473 The Parse Data activity threw a NullPointerExeption for the XSD namespacecollision scenario.

REST and JSON Palette

Key Description

AMBW-24282 The parse exception was thrown when a JSON string, with decimal valuerestricted to 6 fractional digits was parsed to an XML activity. The Parse JSONactivity converted large numbers into scientific form which was not validatedagainst the decimal type. This also caused rounding off numbers whenroundtripped, for example, when json is translated to xml, which is thentranslated back to json.

AMBW-18651 Descriptive error messages are now thrown when Parse JSON and RenderJSON activities fail.

XML Palette

Key Description

AMBW-24089 When a complex element was selected in the Select Schema Element declarationwindow for CDATA section, CDATA was not applied to the child elements of thecomplex element.

85

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Basic Activities Palette

Key Description

AMBW-24171 The error IndexOutOfBoundsException was thrown when Critical Sectiongroups were used.

Release 6.3.2

HTTP Palette

Key Description

AMBW-22518 The TIBCO ActiveMatix BusinessWorks 6.3.1 HTTP client did not support forTLSv1.2 GCM ciphers offered in Java 8.

AMBW-20924 The Authentication check-box for the HTTP Client Shared Resource was resetafter the check-box was cleared.

AMBW-19092 The Send HTTP Request activity was unable to handle Chinese characters in thefilename attribute of the content disposition header in the mimepart.

AMBW-19048 Logging the time stamp for sending a HTTP request and receiving the HTTPresponse in the Send HTTP Request activity was not supported in BusinessStudio.

AMBW-19075 The HTTP server did not recognize requests containing multiple Accept orContent-Type elements in the header.

JDBC Palette

Key Description

AMBW-22120 JDBC activities did not free temporary tablespace when working with OracleLOB data.

AMBW-21860 An error was thrown if the output data type parameter in the JDBC CallProcedure activity was set to Null, or left empty.

JMS Palette

Key Description

AMBW-23031 The JMS Send Message activity with JNDI connection failed to send messages inthe EMS Fault Tolerance with SSL mode.

AMBW-22588 The JMS Receiver activity incorrectly continued to create jobs even after theEMS Server was terminated.

AMBW-22500 Runtime XML serialization mishandled redeclaration of the default namespacemapping to the null namespace.

86

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JMS Palette

Key Description

AMBW-22499 A session leak has been fixed on the JMS Connection Shared Resource.

AMBW-22498 The JMS Receiver activity threw an out of memory exception when the one ofthe applications using the shared resource was stopped.

AMBW-22481 When the JMS Receiver activity received messages of type XML Text, and themessages did not conform to the schema, the session was blocked and noadditional messages were received.

AMBW-21167 The JMS Send activity was unable to send the first message to the EMS serverafter restarting. Subsequent messages however, were successfully sent to theserver.

AMBW-21140 Applications deployed in one AppNode stopped consuming JMS inboundmessages under load.

AMBW-21124 The JMS Connection Shared Resource test connection failed to connect to theEMS server if mutual authentication was enabled in TIBCO ActiveMatrixBusinessWorks 6.x.

AMBW-19105 Business Studio now supports JBOSS as a JMS provider.

AMBW-18646 Business Studio now supports IBM Websphere MQ as a JMS provider.

AMBW-18213 An unclear error message was displayed when a message was not successfullydeserialized.

Mail Palette

Key Description

AMBW-20804 The SendMail activity sent an empty PDF file when the selected attachmentformat type was BinaryContent.

Release 6.3.1

FTL Palette

Key Description

AMBW-18945 Users were unable to connect to or access FTL applications through the FTLRealm Server Connection Shared Resource in Business Studio. TIBCOActiveMatrix BusinessWorks 6.3.1 now comes bundled with FTL 4.3.0 clientlibraries.

87

TIBCO ActiveMatrix BusinessWorks™ Release Notes

General Activities Palette

Key Description

AMBW-21374 Web services that accepted a multi-part request were not successfully invoked ifone of the request part was set to null ("").

JDBC Palette

Key Description

AMBW-21878 When an Oracle stored procedure used an Oracle Struct with a DATE type fieldinside, the JDBC Call Procedure activity failed with an output validation error.

Parse Palette

Key Description

AMBW-21873 The Parse Data activity performance slowed down if placed in a repeat loop. Toavoid this, use filename as input for parsing with the Parse Data activity.

Shared Resources Palette

Key Description

AMBW-21648 If an Invoke activity timed out in an application configured to use SOAP/HTTPbinding, HTTP Resources were not released and a memory leak was observed.

Release 6.3.0

FTP Palette

Key Description

AMBW-19462 A plain TCP connection was created despite the FTP connection beingconfigured with SSL. Now, when an FTP Connection is configured with SSL, asecure connection is created, and the process executes successfully.

AMBW-12997 Process Property of type Password mapped to the Input schema parameterreturned an encrypted password value at runtime and caused activity connectionfailure. This has been fixed and it returns a decrypted password and executes theprocess successfully.

General Activities Palette

Key Description

AMBW-19760 The Timer activity did not adjust the time interval for Daylights Savings Time.This has been fixed.

88

TIBCO ActiveMatrix BusinessWorks™ Release Notes

General Activities Palette

Key Description

AMBW-19011 The Activator Process for OnStartup did not work as expected, and other starterprocesses began in parallel.

HTTP Palette

Key Description

AMBW-19650 The Update SSL sample project SecuredRequestResponse exposed the privatekeys at both the client end and server end.

AMBW-19440 The documentation for the HTTP Palette incorrectly stated that the dynamicheader is an additional header parameter to add runtime headers to the outgoingHTTP messages.

AMBW-18705 Logging all attempts of HTTP access and requests is now supported.

JDBC Palette

Key Description

AMBW-20251 The JDBCUpdate activity was wrongly committing changes to the databasewhen the batch update option was used, the activity was inside a transactiongroup, and the transaction failed.

AMBW-19820 The JDBC Update activity truncated the millisecond part when using aparameter of TIMESTAMP data type.

AMBW-19639 The JDBC Call Procedure activity failed to fetch results when an outputparameter was used at the same time there was a cursor as return type.

AMBW-19247 A JDBCConnectionNotFound fault was incorrectly thrown when a login timeexception occurred.

AMBW-19082 The JDBC Update activity incorrectly listed all stored procedures for selectionafter catalog was specified as a filter.

AMBW-18183 The Schema field and Catalog or Package field could not be configured to use aProcess Property or a Module Property.

JMS Palette

Key Description

AMBW-20696 When an application contained multiple JMS Receiver activities, and theconnection to the EMS server was reset, some JMS Receiver activities did notreconnect and start receiving messages.

89

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JMS Palette

Key Description

AMBW-20566 When a JMS request reply activity was executing, the exception "Invalidtemporary destination" was intermittently thrown.

AMBW-20494 In TIBCO ActiveMatrix BusinessWorks 6.x, a stack overflow error was thrown atruntime if the JMS Receiver activity was using XSD elements from TIBCOCollaborative Information Manager™.

AMBW-20365 While using durable subscribers, each time a JMS connection is made to the JMSServer, a new durable subscriber is created, and using a manually specified clientID resolved the issue.

AMBW-20312 Cyclic includes in XSD files caused a stack overflow.

AMBW-20289 The JMS Send Message activity in a transaction group failed to send a messageto TIBCO Enterprise Messaging Service (EMS) but did not throw any exception.

AMBW-19975 After the TIBCO Enterprise Messaging Service (EMS) server was restarted, theGet JMS activity threw the error javax.jms.IllegalStateException:Trying to Reconnect to JMS Server, and messages were not beingprocessed until ActiveMatrix BusinessWorks 6.x was restarted.

AMBW-19752 TIBCO Business Studio now supports XSD's with cylical dependencies. WhenXSD's containing cycles are imported, a StackOverflow error does not occur.

AMBW-19630 An ambiguous error message was thrown at runtime if the activities, JMSConnection and JMS were not configured in sync.

AMBW-19334 The values for JMSProperties element were not being populated in the output ofJMS Receiver and GetJMSQueueMessage activities.

AMBW-17324 JMS test connection failed when the URL field in KeystoreProviderResource wasset using module property.

JAVA Palette

Key Description

AMBW-18391 If generic Java class of type <E> was selected for the Java class such asjava.util.Collection<E>, then the Input tab for that Java activity showed nodata.

AMBW-12687 Using a two-dimensional Array as an input parameter to Java Method, throwsthe following exception at design time in the Java Invoke activity:

Unable to obtain information for the method [analyze2DArray] from

the class [test2DArray].NoSuchMethodException

occurred.primitives.test2DArray.analyze2DArray([Z)

90

TIBCO ActiveMatrix BusinessWorks™ Release Notes

REST and JSON Palette

Key Description

AMBW-20231 Adding a new REST Service removed the custom HTTP header from the RESTschema.

AMBW-20151 Design time validations were not available for REST/JSON activities, forunsupported schema type.

Rendezvous Palette

Key Description

AMBW-21245 Summary: RV activities in sub-processes with xmlCompliantFieldNames orxmlFormat enabled fail after migration.

Workaround: New projects will work after migration. For old projects the RVactivities with these properties enabled should be deleted and re-created.

AMBW-20030 When a WaitforRVMessage activity joined a conversation using a schema for thekey where elementFormDefault = qualified , the process failed at runtime.

AMBW-19997 RV activities in sub-processes with xmlCompliantFieldNames or xmlFormatenabled failed while parsing the process file.

AMBW-19848 RV messages were not properly constructed in ActiveMatrix BusinessWorks 6.xif the type of element was simple type.

AMBW-17918 For XML format RV messages, the RV Subscriber activity adds a namespacewhen messages are received without a namespace to support interoperabilitybetween ActiveMatrix BusinessWorks 5 and ActiveMatrix BusinessWorks 6.

AMBW-12042 RV subscriber activity did not subscribe the message if output schema created byXSD schema editor was used. It worked fine if the output schema createdRendezvous activity input or output editor was used.

XML Palette

Key Description

AMBW-12999 For Schemas with mixed content, Render XML adds an extra new line to theoutput after each string.

Release 6.2.2

91

TIBCO ActiveMatrix BusinessWorks™ Release Notes

HTTP Palette

Key Description

AMBW-18868 The Socket Timeout and Connection Timeout fields on an HTTP Client sharedresource were not working when "Apache HttpComponents" was selected as theImplementation Library. The HTTP Client Resource automatically used the"chunked" form as Transfer-Encoding HTTP header value regardless of whethercontent-length was set in the Input tab for Apache HTTP components or not.

AMBW-18824 The JDBC Call Procedure activity failed to fetch Resultset schema when"ResultSets Use Schema" was enabled and DB2 database was used. This has beenfixed.

JDBC Palette

Key Description

AMBW-19803 When a login time exception occured, a JDBCConnectionNotFound fault isincorrectly thrown.

AMBW-18811 The JDBC Call Procedure activity returned incorrect results when calling astored procedure that returns multiple resultsets in DB2. This has been fixed.

AMBW-18794 The schema used by UnResolvedResultsets output element in the JDBC CallProcedure activity in version 5.x and version 6.x of the product were different.This has been fixed.

AMBW-18543 If an application was run without using the Fetch button on the JDBC Queryactivity, the application runs assuming "Record*" as a schema and did not throwany error at design-time or runtime.

AMBW-18514 A NullPointerException was thrown when calling a stored procedure in DB2mainframe. This has been fixed.

AMBW-16065 The Use NIL check box in JDBC Query activity's Advanced tab did not work asexpected and the output parameters of the JDBC Call Procedure were notnillable.

AMBW-7535 While selecting the procedure or function in the JDBC Call Procedure activity,Package functions displayed until a Package is provided in the Catalog orPackage field. This has been fixed.

AMBW-4297 JDBC activities did not validate unsupported queries.

AMBW-4071 Save button gets enabled after every click on "JDBC Query activity" , even whenno changes are made. This has been fixed.

92

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JMS Palette

Key Description

AMBW-18345 The JMS Receiver did not honor the cardinality of the XML Schema elementspassed as an application property and generated a fault if those properties werenot populated in the message received. This has been fixed.

REST and JSON Palette

Key Description

AMBW-18224 Invoke REST API activity bypassed the proxy server configured on HTTPClient shared resource. This has been fixed.

AMBW-18050 A "404 Not Found" error was encountered if base path name was same in thePath and Query parameters in the Resource Service Path field. This has beenfixed.

Release 6.2.1

General Activities Palette

Key Description

AMBW-17370 A NullPointerException was thrown by the Inspector activity when theInspect field was set to ALL.

JAVA Activities Palette

Key Description

AMBW-18240 When a Java activity was modified, it did not refresh its signature correctly andcaused errors. This has been fixed.

To trigger the refresh of a Java activity's signature, select or reselect the Java ClassName in the activity's General tab after the Java activity is modified.

AMBW-17374 When running the Java Invoke activity in a multi-threaded mode under load test,an intermittent error was observed.

AMBW-6453 A runtime exception was thrown for Java to XML activity when trying to convertjava object containing Collections. For example, List, Set, Map, or itsimplementations (ArrayList, and so on).

JDBC Palette

Key Description

AMBW-18254 The SQLDirect activity has been fixed to participate in transactions.

93

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JDBC Palette

Key Description

AMBW-17745 Referring out parameter to CURSOR in store procedure, showed an error inTIBCO Activematrix BusinessWorks 6.2.0 hotfix2 instead of showing“UnresolvedResultSet”.

AMBW-17731 The JDBC Query activity did not refresh the Output schema automatically whenchanges were made to the table in the database. To fix this, use the Fetch buttonto refresh the output schema manually.

The Refresh button has been renamed to Fetch.

AMBW-17511 Calling an SQLServer stored procedure failed with an exception when the JDBCCall Procedure activity was configured with a Catalog name.

AMBW-17008 Module property support added for Maximum Connections field in JDBCConnection resource .

JMS Palette

Key Description

AMBW-17433 The JMS Application Property displayed "Unresolved Element" in the Input tabif the Application Property was defined in a shared module and the activity usedXML Text as Message Type.

AMBW-17155 The schema payload on the Input tab of a JMS activity failed to load and amessage "Unresolved reference in schema" was received if the ApplicationProperties Type on the Advanced tab was selected. Previously, we advised usersto close and re-open the project after such configuration for the activity signatureto display properly. This is no longer required with this fix.

REST and JSON Palette

Key Description

AMBW-17005 "TIBCO-BW-PALETTE-REST-100014: An error occurred in render

activity: [no message for java.lang.NullPointerException]"

exception was thrown at run time for Complex Type element withsimpleContent.

AMBW-17599 The 'XML to JSON' activity has been fixed to allow it to be added, removed, andmodified without causing a configuration error.

AMBW-15931 When sending a REST request to invoke a REST resource and authentication isenabled, the authorization header is not added to the request. As a result, therequest failed even though the authorization information was provided. Thisissue was observed only with the Invoke REST API activity.

94

TIBCO ActiveMatrix BusinessWorks™ Release Notes

XML Palette

Key Description

AMBW-17792 Render XML XSLT Function did not include namespace definitions in the output.

AMBW-16925 An exception was thrown at runtime if the Stylesheet field in the Transform XMLactivity was specified using a module property and the module propertycontained an absolute path to the stylesheet.

Release 6.2.0

HTTP Palette

Key Description

AMBW-14508 The HTTP Client Resource automatically used the "chunked" form as Transfer-Encoding HTTP header value regardless of whether content-length was set in theInput tab for Apache HTTP components or not.

AMBW-11263 Parameters on the Send HTTP Request activity were automatically deleted whenDirectory name was added on the Advance tab as Module Property.

AMBW-9210 The HTTP Request activity always applied UTF-8 encoding to generate a URIencoded string for the GET method, regardless of the content-type setting in theHTTP Header.

AMBW-7757 The HTTP Receiver activity always applied UTF-8 encoding to get the parameterdata from URI encoded strings. The parsed parameter data in the HTTP Receiveractivity was garbled if native encoding was applied to URI encoded string.

JMS Palette

Key Description

AMBW-15982 When configured with JMSApplicationProperties and XML Text payload, theBody element clashed and mapping could not be done in the input field. This hasbeen fixed.

However, the UI is not refreshed automatically. You must close the project andthen re-open it to refresh the UI.

AMBW-14631 The package name of an existing JNDI configuration was deleted if a second JMSShared Resource of type JNDI was added with the following conditions:

● the New button shortcut is used to create the JNDI Configuration.

● a JNDI Configuration with the same name already exists.

This led to a validation error 'No JNDI Configuration specified' on all theJMS Connection shared Resources that used the affected JNDI Configuration.

AMBW-7449 RequestTimeout input item is now available in the JMS Request Reply activity.

95

TIBCO ActiveMatrix BusinessWorks™ Release Notes

REST and JSON Palette

Key Description

AMBW-14866 When using the BW JSON UTILS > Create Schema from JSON payload wizard,the XSD schema was always created with the root element name even though adifferent file name was specified.

For example, if the root element name was "Books" and the file name was"Books1.xsd", then the schema was created as "Books.xsd" .

AMBW-13573 The REST Invoke activity now throws a design time validation error ifconfigured with an HTTP Client Resource which has an unsupportedImplementation Library.

Shared Resources

Key Description

AMBW-11984 When a Shared Resource field had a Module Property value, and that field waschanged to Literal and then immediately back to Module Property, the ModuleProperty choice had to be re-selected. The change to Literal Value removed theModule Property value, but the combo box still retained the old value. The oldModule Property value was not saved in the Shared Resource.

XML Palette

Key Description

AMBW-14283 An Activity output data validation error exception was thrown atruntime for schemas that contained "any" element and processContents="strict".

AMBW-12860 After migration, problem markers were seen for "Render-PO-XML","Map-Data" ,"Assign" and "Publish-CompletePO-Message". This has been fixed.

AMBW-11722 In the Input of the Render XML, if each element was mapped individually with acorresponding output of Parse XML, every element was prepended with"schemas:".

Policies

Release 6.3.5

Key Description

AMBW-22045 The security header in the response has been removed after the signature hasbeen verified, and the error message Must Understand check failed forheader is no longer thrown if the response header is signed.

AMBW-19792 If an WSS Consumer policy was configured to verify decryption, but notconfigured for authentication, an error message was incorrectly logged insteadof a debug message.

Release 6.3.2

96

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-22810 A memory leak was observed if the governance agent property on theAppSpace was enabled.

AMBW-22768 Users were not able to encrypt a SOAP message using AES-GCM (AES/GCM/NoPadding).

Release 6.3.0

Key Description

AMBW-22810 A memory leak was observed in the HTTP Connector shared resource as theoption to set the HTTP session timeout was unavailable.

AMBW-22768 TIBCO Business Studio did not support encrypting messages using AES-GCM -AES,GCM,NoPadding. Messages are encrypted based on the algorithm of thealgorithm suite specified which does not include the algorithm http://www.w3.org/2009/ xmlenc11#aes128-gcm.

AMBW-19814 If the name of an Identity Provider resource contained non-ASCII characters,an exception was thrown when the project was ran in the Debugger. This hasbeen fixed.

AMBW-19666 If module properties used by a policy were updated, the changes did not takeeffect when the application was stopped and then restarted or redeployed.

AMBW-19378 The Basic Credential Mapping policy was not supported on SOAP ReferenceBinding.

97

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Known Issues

The following are the known issues in this release of TIBCO ActiveMatrix BusinessWorks™.

The known issues are grouped by components:

● Administration

● Bindings

● General

● Migration

● Palettes

● Policies

Administration

Key Description

AMBW-27441 Summary: When a custom logback xml file is provided in thelogback.configurationFile property, the uploaded file will not change theAppNode logging , and the default logback.xml is downloaded instead of thecustom logback file specified in the logback.configurationFile property.

Workaround: Specify the default path for the AppNode logback.xml file.

AMBW-27440 Summary: In the DBEMS mode when we upgrade from 6.3.1 to 6.4.0 andrestore Domain,the error, ERROR: null value in column "commandid"violates not-null constraint, is thrown.

Workaround: After upgrade drop the old commandhistory table and run thenew 6.4.0 bundled script to create the commandhistory table and then restorethe domain.

AMBW-27319 Summary: While enabling LDAP Authentication for bwagent REST API, theAppNode failed to communicate with the bwagent REST API and failed toreport its status. The status of AppNode is shown displayed as stopped.

Workaround: In the bwagent.ini file, use the LDAP user and password(obfuscated) for the following properties - bw.agent.appnode.user andbw.agent.appnode.password respectively. The password must be able to bede-obfuscated.

AMBW-27257 Summary: Failed to validate the OSGi Ports against the OSGi interface and theHTTP interface from Admin UI.

Workaround: None.

AMBW-27163 Summary: The Unregister command to unregister an agent from a givendomain does not work.

Workaround: None.

AMBW-26286 Summary: Unable to upload large sized ear files (~10 MB) when the DB2database is used for the DBEMS or DBFTL mode.

Workaround: None.

98

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-26276 Summary: When an EAR application file is uploaded, and the machine isrunning out of disk space, the bwadmin console prints an error messageindicating that the transaction log for database XXX is full. As the error thrownis an SQL error, the agent failed to understand that the root cause was out ofdisk space.

Workaround: None.

AMBW-25889 Summary: From the command line, users can enable the OSGi and create anew AppNode on the same OSGi port.

Workaround: Use the Admin UI to enable the OSGi port.

AMBW-24467 Summary: The property bw.mashery.config.file= ../config/mashery.ini did not work as documented in Publishing APIs to TIBCOMashery in the Administration guide.

Workaround : Delete the extra space before ../config/mashery.ini.

AMBW-22520 Summary: The bwadmin start and bwadmin -deploy -startondeploycommands report the STARTED state though the AppNode and AppSpace arestopped.

Workaround: Use bwadmin show applications command to retrieve theapplication status.

AMBW-17562 Summary: The OSGi configuration properties have been aligned between thedebug environment launched from within TIBCO Business Studio™ and theAppNode that is launched in an installation. However, a difference in behaviorof the osgi.compatibility.bootdelegation property in both theenvironments has been observed.

Workaround: None.

Bindings

Key Description

AMBW-27435 Summary: When module properties used from a shared module project wererenamed, the changes made were not reflected at the SOAP binding level.

Workaround: Select the updated module property from the drop down in theSOAP binding.

AMBW-27051 Summary: Request and Response is displayed as a string in REST ReferenceBinding when it was configured with a wrapper whose name does not endwith the array suffix and where JSON Definition Style is set to theAnonymous Array option.

Workaround: None.

AMBW-26806 Summary: When a REST service with a schema that uses a type which wasimported from another XSD is invoked in a REST Reference Binding, it failswith the ServiceRuntimeException.

Workaround: None

99

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-21363 Summary: REST Call failed on run-time under non-UTF8 locale environment.

Workaround: Set the default encoding of the AppNode to UTF-8 by adding "-Dfile.encoding=UTF-8" to java.extended.properties of "bw/6.3/config/bwappnode-an. tra_template".

AMBW-21278 Summary: Currently, the SOAP Service palette allows users to develop Serviceor Reference bindings with no restrictions on the level of imports for schemasor definition targetnamespace. But when a SOAP wsdl is generated for Servicebindings, the concrete wsdl does not include the schemas which are referred atnested level 3 or more.

Workaround: Include concrete wsdls with referenced schema definition asinline schema while providing service consumer for concrete wsdl. For HTTPSOAP Service bindings, check the run time wsdl generation as an alternativesolution.

AMBW-13607 Summary: REST Doc UI is not supported on Firefox browser.

Workaround: Use other browsers for the Doc UI.

AMBW-13572 Summary: For some use cases, REST Doc UI does not show the correct errorcode in case of Internal Server errors on the Server side.

Workaround: Check the raw message that contains the correct error code.

AMBW-13485 Summary: REST Doc UI does not support browsers like Internet Explorer.

Workaround: Use Chrome browsers for the Doc UI.

AMBW-8982 Summary: Changing the Resource name in the REST service Bindings tab,does not update the Resource Service Path.

Workaround: None.

General

Key Description

AMBW- 27253 Summary: The Identity Provider field in the WSSConsumer Policy resourcedoes not supported module properties.

Workaround: None

AMBW-25318 Summary: A pre-defined element reference could not be added to a schemafrom the schema editor in TIBCO Business Studio.

Workaround: Set the element reference for the schema from the Propertiesview.

AMBW-25313 Summary: When a namespace is manually edited from the Source view, thecorrect namespace value is not displayed in the Design view.

Workaround: Use the Edit Namespaces functionality available in the SchemaEditor properties section.

100

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-25265 Summary: Managed Fault Tolerance does not work properly if servers are indifferent time zones.

Workaround: None

AMBW-25073 Summary: The option to test connections, for example JMS or sFTP, in a sharedresource that has a profile is not supported in TIBCO Business Studio™.

Workaround: Specify the server configuration details as literal value or moduleproperties.

AMBW-24789 Summary: The application fails to restart and remains in the AppError stateafter starting and stopping an appspace multiple times, if ActiveMatrixBusinessWorks™ 6.3.3 is using Red Hat Enterprise Linux 6.8, or later versions,and Oracle 12c.

Workaround:None.

AMBW-24309 Summary: Upgrading to TIBCO ActiveMatrix BusinessWorks™ 6.3.1 or ahigher fails if sFTP 6.1.0, or a lower version of the plugin, is installed in thesameTIBCO_HOME.

Workaround:Uninstall sFTP 6.1.0, or a lower version, plugin before you installthe newer version of TIBCO ActiveMatrix BusinessWorks 6.x in the sameTIBCO_HOME.

AMBW-24052 Summary: When an external client executed a SOAP request using the defaultnamespace in the payload, an empty payload was received on SOAP over JMSBinding.

Workaround : Change the namespace in the Invoke activity's XSLT source.

AMBW-23376 Summary: Failed to get runtime information of an AppNode on the AIXplatform using REST API.

Workaround: The workaround is to create a symbolic link using the followingtwo commands cd <BW_HOME>/system/shared/com.tibco.bw.tpcl.org.hyperic.sigar_<version> and ln -s libsigar-ppc64-aix-5.so libsigar-ppc64-aix-7.so

AMBW-19789 Summary: Embedded policies are not enforced on the AIX platform, and theexception NoClassDefFoundError is logged in the AppNode log when youstart the AppNode.

Workaround: None.

AMBW-19540 Summary: When a project contain abstract and concrete WSDL using sametarget namespace, a validation error is thrown.

Workaround: None.

AMBW-18459 Summary: The ability to reference from a standalone (external) schema to aninline schema is not supported. If your project contains such a reference, avalidation error is thrown.

Workaround: Externalize the WSDL-inline schema and change the importstatements to reference the newly created (external) schema.

101

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-17998 Summary: The EAR file generated using bwdesign utility does not supportnon-ASCII characters.

Workaround: None.

AMBW-17562 Summary: The OSGi configuration properties have been aligned betweendebug environment launched from within TIBCO Business Studio™ and theAppNode that is launched in an installation. However, a difference in behaviorof the "osgi.compatibility.bootdelegation" property in both the environmentshas been observed.

Workaround: None.

AMBW-16256 Summary: The first attempt to change the data type of an Operator's input oroutput schema element fails and the change is not committed. Subsequentattempts complete without any failure.

Workaround: To commit the change, you must press the return key after everychange.

AMBW-14861 Summary: Unable to enter an XPath expression on a transition using the XPathBuilder. This issue is observed on Mac OS only.

Workaround: Enter the XPath expression directly in the Properties tab >Expression field for the transition without using the XPath Builder.

AMBW-14533 Summary: Mapper does not throw typecasting error, if the Integer data type ismapped with String data type.

Workaround: None

AMBW-13823 Summary: Directory browser dialog in BW Context Sensitive Help preferencesetting page does not consistently popup on Mac OS X 10.9.2

Workaround: Copy and paste the directory path into the configuration fieldinstead of using directory browser to pick it.

AMBW-13683 Summary: Shared resource module property references in the migrated TIBCOActiveMatrix BusinessWorks 5.x projects do not show up correctly on non-Windows platforms.

Workaround: Close and reopen the project.

AMBW-13673 Summary: Schema is not populated in Input Editor and Output Editor whenthere is no targetNamespace in the schema.

Workaround: Provide targetNamespace in the schema.

AMBW-12490 Summary: Under certain circumstances, substitution types do not resolveproperly in the mapper. The mapper shows errors for them.

Workaround: Try closing and reopening the project. If that does not solve theissue, try closing and reopening Eclipse. If the errors still persist, perform aproject clean (that is, go to the Project menu and click Clean...).

102

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-11815 Summary: A module shared variable cannot initialized with an XML file thatcontains double-byte characters.

Workaround: None.

AMBW-11624 Summary: TIBCO Business Studio™ hangs when opening SQL Builder if thedatabase details on the JDBC shared resource are changed from PostgreSQL toMySQL after a query has been created using SQL builder.

Workaround: None.

AMBW-11534 Summary: TIBCO Business Studio™ crashes occasionally on Windows 2012 R2platform when switching workspace from File > Switch Workspace.

Workaround: Retry by switching the workspace.

Migration

Key Description

AMBW-27379 Summary: Mappings are broken when a Shared Module and ApplicationModule existing in different workspaces are referenced.

Workaround: Check the option Copy projects to workspace while importingmigrated projects into the workspace.

AMBW-27312 Summary: Mappings are incorrectly migrated when projects referencing DTLsin different workspace other than same DTL location are migrated using thecommand line.

Workaround: None

AMBW-20170 Summary: Validation errors occur after migration when an XML element froman XSD schema, that does not have a target namespace, cannot be resolved.

Workaround: None

AMBW-14547 Summary: When you migrate an ActiveMatrix BusinessWorks 5.x projectcontaining in-built functions in the JDBC Query activity, an Invalid Columnname error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the ActiveMatrixBusinessWorks 5.x project.

AMBW-14295 Summary: After migration, the output of project with Rest and JSON activitiesdoes not match with the input of the other activities in the migrated project.

Workaround: None.

103

TIBCO ActiveMatrix BusinessWorks™ Release Notes

Key Description

AMBW-9969 Summary: TIBCO ActiveMatrix BusinessWorks 5.x projects with SOAPheaders configuration in SOAP activities are not properly migrated to TIBCOActiveMatrix BusinessWorks 6.x.

Workaround: SOAP functionality in ActiveMatrix BusinessWorks 6.x isachieved through SOAP Binding where its detail configuration is outside ofBusinessWorks Process. The SOAP headers definition are defined at theBinding configuration and configured as generic context parameters for theProcess. In the Process, you can use the Get Context activity (from BasicPalette) to retrieve and process the headers as context data. You can do thismanually to complete the migrated project.

Palettes

JAVA Palette

Key Description

AMBW-13526 Summary: In Java To XML activity, the Output tab is not populated correctly, ifJava Class contains nested Object references in different classes.

Workaround: None.

JDBC Palette

Key Description

AMBW-27422 Summary: When the JDBC Connection Shared Resource was used on amodule property and the module property was then used on an activity, theshared resource was not recognized by the activity.

Workaround: Select the field type as literal and select the shared resource fromthe shared module project.

AMBW-23464 Summary: The Oracle DataDirect driver does not support cursor datatype.

Workaround: Use native drivers instead of DataDirect drivers.

AMBW-23193 Summary: When using DataDirect drivers with a JDBC Shared Resource, thatis linked to a JDBC process, the SQL Builder Wizard does not work correctly.

Workaround: Use native drivers.

AMBW-20130 Summary: The login timeout value is not effective when connecting to aWindows OS database. The JDBC Query activity fails withJDBCConnectionNotFoundException at runtime without honouring the LoginTimeout value specified in the JDBC Connection Shared Resource.

Workaround: None

104

TIBCO ActiveMatrix BusinessWorks™ Release Notes

JDBC Palette

Key Description

AMBW-14547 Summary: When you migrate an ActiveMatrix BusinessWorks™ 5.x projectcontaining in-built functions in the JDBC Query activity, an invalid columnname error is thrown in the JDBC Query activity.

Workaround: Use an Alias instead of the in-built functions in the ActiveMatrixBusinessWorks™ 5.x project.

AMBW-11624 Summary: TIBCO Business Studio™ hangs when opening SQL Builder if thedatabase details on the JDBC shared resource are changed from PostgreSQL toMySQL after a query has been created using SQL builder.

Workaround: None.

AMBW-11667 Summary: Using any in-built function in JDBC Query activity without "Alias"fails to execute the application and throws an Invalid Column name error atrun time.

Workaround: Use "Alias" to work with any in-built function in JDBC Queryactivity.

AMBW-14624 Summary: The Set Explicit Nil check box for Objects and Collections in JDBCCall Procedure activity is disabled.

Workaround: None.

AMBW-8855 Summary: The localized error messages of JDBC connection are not displayedcorrectly in TIBCO Business Studio™.

Workaround: None.

XML Palette

Key Description

AMBW-14292 Summary: Parse XML activity displays blank ErrorCode and ErrorMessage foractivity output data validation error.

Workaround: None.

Policy

Key Description

AMBW-19513 Summary: If a SOAP binding is not configured with Transport, the Add NewPolicy icon should be disabled, the Policy field should not be displayed in thetree view, and a NULL pointer exception is thrown if you try to add a policy onthe binding.

Workaround: None.

105

TIBCO ActiveMatrix BusinessWorks™ Release Notes


Recommended