TIB_BW_6.2.2_relnotes

TIBCO ActiveMatrix BusinessWorks™ ReleaseNotesSoftware Release 6.2.2June 2015

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(OR PROVIDE 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, EITHEREXPRESS OR 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-2015 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

3


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


New Features

Here are the new features available in this release (6.2.x) of TIBCO ActiveMatrix BusinessWorks.

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.

5


https://docs.tibco.com/pub/activematrix_businessworks/6.2.1/doc/html/GUID-60DB2FAB-3C7F-4E8E-8FB1-585BD291B43A.html

https://docs.tibco.com/pub/activematrix_businessworks/6.2.1/doc/html/GUID-D7B20A3C-225D-4241-AB41-E2C41F04843F.html

Design-time

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.

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


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.

6


https://docs.tibco.com/pub/activematrix_businessworks/6.2.1/doc/html/GUID-8CE1DA74-12EE-47C8-8D71-66702F4E0099.html


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 inthe Administration guide for details.

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.

7



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.

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.

8



Unified Doc URL configuration Documentation for all applications in anAppSpace using REST services are nowavailable on a single REST Doc URL. SeeAdministration Tasks and Reference ->Managing an Application -> Viewing Endpoints,Components, and Processes -> Configuring aUnified Doc URL in the Administration guide fordetails.

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.

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.

9


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.

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.

10


Design-time

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 nowbe installed from TIBCO Business Studio usingthe Help > Install New Software menu. TheEclipse p2 installation packages for the pluginsmust be downloaded and made available on anupdate site or directory beforehand. SeeInstalling TIBCO ActiveMatrix BusinessWorksPlug-ins in the 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.

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.

11


Changes in Functionality

The following are the notable changes in functionality in this release (6.2.x).

Release 6.2.1


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.

12


Release 6.2.0


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.

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.

13


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 findthe generic 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 theadmin scripts, add the following statement toyour ~/.bashrc file to source the generatedscript:sourceBW_HOME/scripts/bashrc.sh

14


Closed Issues

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

The closed issues are grouped by components:

● Administration● Bindings● General● Migration● Palettes

Administration

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.

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.

15


Key Description

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.

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

16


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

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

17


Key Description

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.

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

18


Key Description

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 inorder to store the design and runtime XSLT of the updated mapping.

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.

19


Key Description

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.

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 inthe current product version, but you can resolve the error by re-mapping theinput manually.

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.

20


Key Description

AMBW-17071 A runtime error was thrown when an XPath expression contained the wildcardcharacter '*' (any element).

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.

21


Key Description

AMBW-16677 When you renamed a partner link or an operation, the framework did not notifythe Confirm activity. This has been fixed.

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

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.

22


Key Description

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

23


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.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 JavaClass Name 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.

24


JAVA Activities Palette

Key Description

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.

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.

25



Key Description

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.

XML Palette

Key Description

AMBW-17792 Render XML XSLT Function did not include namespace definitions in theoutput.

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.

26


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.


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

27


XML Palette

Key Description

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:".

28


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

Administration

Key Description

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.

AMBW-16790 Summary: On Microsoft Windows, closing the bwadmin command windowterminates the AppNodes that were started from this command window.

Workaround: None. On Microsoft Windows, child processes are terminatedwhen their parent terminates.

Bindings

Key Description

AMBW-18408 Summary: Swagger UI is not getting the response for invoking POST/PUTmethod for form parameter on Firefox browser.

Workaround: None.

AMBW-18050 Summary: A 404 Not Found error is encountered if base path name is samein the Path parameter and Query parameter in the Resource Service Pathfield. For example, REST Resource having Resource Service Path as /books/{isbn} or /books?isbn={isbn} in a project which already has resource withpath as /books, will throw an error.

Workaround: Use different base path names for Path and Query parameters.For example, change /books/{isbn} to /books1/{isbn}.

29


Key Description

AMBW-16218 Summary: When using 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 is thrown at runtime.

Workaround: Change the Inline schema targetNamespace and also update theWSDL created by the REST Resource to include a link to that inline schema.

AMBW-17166 Summary: The SOAP binding style RPC encoded is not supported.

Workaround: None.

AMBW-16039 Summary: Incorrect Swagger specification models are generated for RESTservices when using the pass through mechanism (Opaque mode).

Workaround: None.

AMBW-13999 Summary: Deleting a REST Component results in permanent loss of theBindings.

Workaround: If after deletion the artifacts are not saved, quit TIBCO BusinessStudio without saving and this will not delete the bindings. However ifartifacts are saved after deleting a binding or a component, it cannot be re-added.

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 other browsers for the Doc UI.

AMBW-11974 Summary: Resolution of SOAP transport type does not work for SOAP overHTTP, if SOAP over JMS and SOAP over HTTP bindings are in the sameprocess.

Workaround: None.

AMBW-8982 Summary: Changing the Resource name in the REST service Bindings tab,does not update the Resource Service Path.

Workaround: None.

30


General

Key Description

AMBW-18469 Summary: The initial value of a Module Property is not a valid runtime valuefor Boolean, Long, DateTime, and Password types. An initial value is requiredfor these types, but for Password the user must set and unset the value to makeit work at runtime.

Workaround: Set and unset the password Module Property value if an emptystring is desired for the password value.

AMBW-18459 Summary: The ability to reference from an 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.

AMBW-18312 Summary: An application fails to deploy if EAR file name contains non-ASCIIcharacters and a profile is uploaded instead of the default.

Workaround: None.

AMBW-18305 Summary: When JDBC activity output changes, an iteration element does notupdate with the new changes.

Workaround: Make a change to the Iterate Group list XPath and the elementwill be refreshed.

AMBW-18191 Summary: An error, Cannot find XML element, is observed intermittently atruntime if some specific namespaces are not imported in the WSDL. Theintermittent nature of this issue was caused by the changing order in whichWSDL documents were processed.

Workaround: Modify the WSDL files so that their inline schemas do not haveany errors.

AMBW-18138 Summary: An application profile fails to download if application namecontains non-ASCII characters.

Workaround: None.

AMBW-17998 Summary: The EAR file generated using bwdesign utility does not supportnon-ASCII characters.

Workaround: None.

AMBW-17807 Summary: (On Mac) XPath expression is not getting updated for the "SequenceKey" field if OK is pressed in the XPath builder after making changes in theexpression.

Workaround: After writing the expression click anywhere else in the XPathbuilder or press enter before clicking the OK button. The updated value getsrecognized.

31


Key Description

AMBW-17781 Summary: The XSLT processor adds each namespace declaration of thexslt:stylesheet element to the root node of the output document.

Workaround: None.

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-17089 Summary: TIBCO ActiveMatrix BusinessWorks project throws a warningduring validation when it is copied from an old workspace and imported to anew workspace.

Workaround: None.

AMBW-17082 Summary: Changing the reference in a process to use a new port type does notclean up the old references inside the process.

Workaround: Use the Project Explorer right-click menu Refactor/RepairBusinessWorks Projects to repair any process in a project with this issue.

AMBW-17034 Summary: When an application with RVCM is stopped, the AppNode doesnot release the RVCM ledger file handle. As a result, when you try to restartthe application, the RVCM ledger file cannot be opened and the applicationfails to start.

Workaround: For applications with RVCM, restart the AppNode instead ofrestarting the application.

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

Workaround: None.

AMBW-16642 Summary: Product installation fails on Mac OS X with a dialog box requestingto install Java SE 6.

Workaround: Java 6 is required for the installation process to complete.Choose one of the following options to workaround this issue:

1. Prior to running the product installer, download Java 6 from Apple site.For detailed instructions, see http://support.apple.com/kb/DL1572.

2. If you have already run into the installation failure, click Install todownload and install of Java 6. By default, Java 6 is installed under /System/Library/Java/JavaVirtualMachines/1.6.0.jdk. At this pointthe installer is already in a failed state. Exit the installation by clickingCancel. Clean up the TIBCO_HOME directory chosen for installation andrun the installer to install the product.

AMBW-16633 Summary: TIBCO Business Studio fails to launch on Mac Yosemite OS as theJAVA SE 6 runtime is not available by default.

Workaround: Download and install the Java for OS X 2014-001 from http://support.apple.com/kb/DL1572.

32


http://support.apple.com/kb/DL1572



Key Description

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-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-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: Afatal error 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-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-14254 Summary: The following validation error is thrown when you validate theWSDL, ZipInfo_gen.wsdl, from the ZipCodeLook sample: cvc-complex-type.4: Attribute 'location' must appear on element

'wsdl:import'. The validation error is thrown because the generated WSDLdoes not embed the schema.

Solution: To fix this error, embed the schema when generating the WSDL fromthe ZipPort SOAP service binding component.

AMBW-13955 Summary: After deleting a component that contains REST binding, it is notpossible to re-create the component with the REST binding.

Workaround: To re-add the REST binding:

1. In the Process Editor, right click on the Service without a binding.

2. Choose Components > [componentname] > Create REST Binding.

A binding will be created for this service. However, a binding still cannot becreated from the Module Descriptor/Components property section after it hasbeen deleted.

33


Key Description

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 re-open the project.

AMBW-13673 Summary: Schema is not populated in Input Editor/Output Editor if there is notargetNamespace in the schema.

Workaround: Provide targetNamespace in the schema.

AMBW-12785 Summary: When trying to exit TIBCO Business Studio before saving theprocess, throws a java.lang.NullPointerException error.

Workaround: None

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 doesn't solve theissue, try closing and reopening Eclipse. If the errors still persist, do projectclean (that is, go to Project menu and click on "Clean...").

AMBW-12263 Summary: When a user defines a fault context variable at the Port Type level,that context does not work at run time. Operations may define multiple faults,so it is difficult to determine which fault is to be used per operation.

Workaround: Always define a fault context variable per operation, so that theruntime is able to resolve the fault context.

AMBW-11853 Summary: A process that has an XSLT with a substitution, throws a validationexception at run-time, unless the process is explicitly importing the XMLSchema.

Workaround: The user should explicitly import the XML Schema in theprocess, by using the Add Process Import tool that is available in ProcessProperties > Dependencies tab.

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.

34


Key Description

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.

AMBW-10137 Summary: TIBCO ActiveMatrix Platform based products fail to install in thesame TIBCO_HOME as TIBCO ActiveMatrix BusinessWorks 6.0.

Workaround: Installation of TIBCO ActiveMatrix BusinessWorks 6.0 andTIBCO ActiveMatrix Platform based products in the same TIBCO_HOME iscurrently not supported.

Migration

Key Description

AMBW-18293 Summary: For migrated TIBCO ActiveMatrix BusinessWorks 5.x processes, the<bpel:import> element does not contain the namespace attribute for schemaor WSDL references that have no target namespace.

Workaround: Update the namespace manually. For example, update<bpel:import location="/x/y/z.xsd"/> to <bpel:import namespace=""location="/x/y/z.xsd"/>.

AMBW-16406 Summary: When you migrate a project using the command line, the outputschema in the migrated project is missing.

Workaround: To fix this issue:

1. In the Project Explorer view, select all the projects in your workspace.

2. Right-click and select Refactor > Reload Working Copy.

AMBW-15253 Summary: An error was encountered after migration if the schema has animport statement that could not be resolved and one for a namespace, that wasnever used in the process.

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

35


Key Description

AMBW-14213 Summary: After migration, the Render XML activity got an incorrect inputschema because of schema collision.

Workaround: Avoid schema collisions by declaring targetNamespaces in allschema. When that is not possible, include only one of the conflicting schemain each process.

AMBW-13932 Summary: If a global variable name and the iteration group's "iterationelement" field name is the same, then the migration tool generates a uniquename for the iteration element.

Workaround: Fix all the related activity input mappings manually.

AMBW-11449 Summary: Mapping an anyType element to a XML Schema simple type valueresults in an error.

Workaround: Coerce the anyType element with XML Schema simple typeelement and map. The type of the element used for coercion is determined bythe value that is used in the mapping.

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

AMBW-7649 Summary: Error Transitions from an event source and group box are notsupported.

Workaround: Manually fix the associated mappings especially thosecontaining error variables. Also, move the error handing path logic to theenclosing scope's catch block.

Palettes

HTTP Palette

Key Description

AMBW-12732 Summary: Dynamic Headers for HTTP send request activity are partiallymigrated. The user after migration has to re-map these missing dynamicheader fields by using original ActiveMatrix BusinessWorks 5x mappings inreference.

Workaround: Add missing headers manually after migration.

36


JAVA Palette

Key Description

AMBW-18391 Summary: If generic Java class of type <E> was selected for the java class suchas java.util.Collection<E>, then the Input tab for that Java activityshowed no data.

Workaround: None.

AMBW-13526 Summary: In Java To XML activity, the Output tab is not populated correctly,if Java Class contains nested Object references in different classes.

Workaround: None.

AMBW-12687 Summary: Using a 2D Array as an input parameter to Java Method, throws thefollowing exception at design time in Java Invoke activity.

Unable to obtain information for the method from the

class .NoSuchMethodException )

Workaround: None.

AMBW-6409 Summary: The exception Activity output data conversion error isthrown for the Java to XML if the input has an ArrayList containing a JAVAobject.

Workaround: Use Java Generics and provide the "Type" information. Forexample, use generics List<String> list = new ArrayList<String>();

instead of List list = new ArrayList();

JDBC Palette

Key Description

AMBW-18543 Summary: If an application is run without using the Fetch button on the JDBCQuery activity, the application runs assuming "Record*" as a schema and doesnot throw any error either at design-time or runtime.

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

Workaround: Use "Alias" to work with any in-built function in JDBC Queryactivity.

AMBW-4071 Summary: Save button gets enabled after every click on "JDBC Queryactivity" , even when no changes are made.

Workaround:None.

37


JDBC Palette

Key Description

AMBW-16065 Summary: The Use NIL check box in JDBC Query activity's Advanced tab doesnot work as expected and the output parameters of the JDBC Call Procedureare not nillable.

Workaround: None.

AMBW-14624 Summary: Set Explicit Nil check box for Objects and Collections in JDBC CallProcedure activity is disabled.

Workaround: None.

AMBW-8855 Summary: The localized error messages of JDBC connection were notdisplayed correctly in Studio.

Workaround: None.

AMBW-7535 Summary: While selecting the procedure/function in the JDBC Call Procedureactivity, any "Package functions" should not display until a Package isprovided in the "Catalog or Package field".

Workaround: Click the Cancel button and select the procedure again.

AMBW-4297 Summary: JDBC activities do not validate unsupported queries.

Workaround: None.

JMS Palette

Key Description

AMBW-18213 Summary: When trying to deserialize a message, an error is encountered.However, this message is not clear.

Workaround: None.

Parse Palette

Key Description

AMBW-12473 Summary: Parse Data activity throws a NullPointerExeption for the XSDnamespace collision scenario.

Workaround: None.

38


Rendezvous Palette

Key Description

AMBW-12473 Summary: RV Subscriber activity does not subscribe the message if outputschema created by XSD schema editor is used. It works fine if the outputschema created Rendezvous activity input/output editor is used.

Workaround: Change the elementFormDefault for the schema element createdusing XSD Schema Editor to "unqualified".

AMBW-12042 Summary: RV subscriber activity does not subscribe the message if outputschema created by XSD schema editor is used. It works fine if the outputschema created Rendezvous activity input/output editor is used.

Workaround: Change the elementFormDefault for the schema element createdusing XSD Schema Editor to "unqualified".


Key Description

AMBW-18224 Summary: Invoke REST API activity bypasses proxy server configured onHTTP Client shared resource.

Workaround: None.

XML Palette

Key Description

AMBW-14292 Summary: Parse XML activity displays blank ErrorCode and ErrorMessage foractivity output data validation error.

Workaround: None.

AMBW-12999 Summary: For Schemas with mixed content, Render XML adds an extra newline to the output after each string.

Workaround: None.

AMBW-6965 Summary: When the "Input and Output Style" is Tree for the Transform XMLactivity, a java.lang.AssertionError: origin cannot be null exceptionis thrown.

Workaround: None.

39


TIB_BW_6.2.2_relnotes

Documents

Transcript of TIB_BW_6.2.2_relnotes