TIBCO ActiveMatrix BusinessWorks Release Notes

Transcription

1 TIBCO ActiveMatrix BusinessWorks Release Notes Software Release March 2015 Two-Second Advantage

2 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization 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 TIBCO Software Inc. in the United States and/or other countries. Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE 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 OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 3 Contents Setting Context Sensitive Help Preferences...4 New Features...5 Changes in Functionality...12 Closed Issues...15 Known Issues...29

4 4 Setting Context Sensitive Help Preferences This procedure explains how to change your help preferences in TIBCO Business Studio to access context sensitive help from a local directory or from an internal web server, if you have placed the documents under it. Prerequisites Before setting context help preferences you must download the documentation for your product from the FTP site provided by your TIBCO representative. Copy the documentation zip file to a local directory, 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 Business Studio > 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 the documentation, or provide the URL to the html directory on your internal web server. 4. Click Apply and then click OK.

5 5 New Features Here are the new features available in this release (6.2.x) of TIBCO ActiveMatrix BusinessWorks. Release Runtime Administration Framework Ability to enable or disable process statistics collection from the Admin CLI. You can enable or disable process statistics collection for an application from the Admin CLI using the following commands: enablestats disablestats See Process Statistics for details. Improved Administrator user interface GET operation to obtain AppSpace configuration A number of visual cues and aesthetic enhancements to the Administrator UI have been made including improvements to the Process Viewer. The bwagent REST API now provides a GET operation to obtain the AppSpace configuration. Design-time Improved wizard to create subprocesses Swagger UI and Swagger Specification support for Basic Authentication Basic Authentication support for REST Binding and Invoke REST API activity The wizard to create subprocesses has been improved to create subprocesses with inline schema and WSDL files. The wizard has also been improved to make it easy to use and consistent with the approach to create processes. The Swagger UI supports the use of endpoints configured with Basic Authentication. The Swagger UI has two new fields, User Name and Password, which are always visible. The REST Service Binding and the Invoke REST API activity support Basic Authentication. The REST Service Binding can be configured using a check box in the Binding Configuration. When the check box is selected, the REST Binding uses the LDAP Shared Resource configured on its HTTP Connector to perform Basic Authentication. The Invoke REST API activity automatically adds the authorization header with the user credentials if an Identity shared resource is configured on the HTTP Client shared resource. See REST Binding for details.

6 6 Design-time SSL Client and SSL Server resources default the keystore implementation to JRE's certificate store HTTP Authentication support for SOAP Binding Enhancements to JDBC activities The SSL Client and SSL Server resources default the trust keystore configuration to JRE's cacerts. This eliminates the need to create trust stores from default. A new HTTP Authentication check box has been introduced. When selected, specifies that the Service Request sent by the Service Consumer must be authenticated. Authentication is successful, if the user name and password specified in the Service Request exists in the LDAP server configured on HTTP Connector. JDBC activities now support ThreadPool shared resources that you can use to limit thread creation. JDBC activities now expose Activity Timeout with a default value of 3 minutes. When the timeout value is reached, the engine cancels the activity and throws an ActivityTimedout exception. See JDBC Palette for details. Samples and Scripts New script, bw6env.sh, to print the environment variable configurations The script, bw6env.sh, prints the required and optional environment variable configurations on the screen. This script is available under the <TIBCO_HOME>/bw/6.2/scripts/admin folder. Release Runtime Administration Framework bwagent supports an external datastore for communication and TIBCO Enterprise Message Server (EMS) for persistence The bwagent now supports an external datastore (PostgreSQL or MySQL) and TIBCO EMS for persistence and communication in addition to TIBCO ActiveSpaces. See Administrator and Agent -> bwagent -> Configuring bwagent in the Administration guide for details.

7 7 Runtime Administration Framework bwagent configuration bwadmin commands for viewing agent and engine information Two JSON files are provided for bwagent configuration: bwagent_as.json and bwagent_db.json. You can use the bwadmin config command with one of these JSON files to configure the bwagent. See Administrator and Agent -> bwagent -> Configuring bwagent -> ActiveSpaces Configuration for bwagent and Administrator and Agent -> bwagent -> Configuring bwagent - > Database/EMS Configuration for bwagent in the Administration guide for details. There are new bwadmin commands for viewing agent and engine information: The show agentprocessinfo command shows info about the agent. The show bwengine command shows info about the engine on an AppNode. The bwenginedb command shows info about the engine database. Remote AppNode debugging from TIBCO Business Studio You can debug a remote AppNode from TIBCO Business Studio. To do so, select the AppNode in the Deploy view and click the enable debug icon in the Properties view before launching the debugger. See Deploying an Application -> Using the Debugger -> Remote Debugging in the Application Development guide for details. Remote AppNode debugging enabled using the bwadmin command or from the Admin UI Application activity execution statistics and process execution statistics collection You can enable remote debugging for an AppNode using the bwadmin command or from the Admin UI. This is useful in secure environments where only an administrator has the access rights to enable or disable ports. See Administration Tasks and Reference -> Managing AppNodes -> Debugging an AppNode in the Administration guide for details. You can collect application activity execution statistics and process execution statistics and display the results as a text file, an HTML file, or write to a database. See Logging -> AppNode Logging -> Statistics Collection in the Administration guide for details.

8 8 Runtime Administration Framework Domain backup and deletion in the Admin UI The following operations are available on the Domain Management page in the Admin UI: Backing up and restoring an domain. See Administration Tasks and Reference -> Managing Domains -> Backing Up and Restoring a Domain in the Administration guide for details. Deleting a domain. See Administration Tasks and Reference -> Managing Domains -> Deleting Domains in the Administration guide for details. View process diagrams in the Admin UI From the Application page in the Admin UI for a running application, you can view the endpoints, components, and processes for a running application. Furthermore, you can view the process diagrams provided the application archive file was generated using the current version of the product. See Administration Tasks and Reference -> Managing an Application -> Viewing Endpoints, Components, and Processes in the Administration guide for details. REST Doc URL in the Admin UI From the Application page in the Admin UI for a running application, you can view the REST Doc URL for applications using REST services. The links open the REST UI page where you can test out the operations. See Administration Tasks and Reference -> Managing an Application -> Viewing Running Applications in the Administration guide for details.

9 9 Runtime Administration Framework Unified Doc URL configuration Application properties and application instance properties editing in the Admin UI Application profile download from the Admin UI AppSpace or AppNode configuration update from the Admin UI Ability to iterate through a list of items in Level 2 entities in the Admin UI Documentation for all applications in an AppSpace using REST services are now available on a single REST Doc URL. See Administration Tasks and Reference -> Managing an Application -> Viewing Endpoints, Components, and Processes -> Configuring a Unified Doc URL in the Administration guide for details. Application properties and application instance properties can be edited from the Admin UI. See Administration Tasks and Reference -> Managing an Application -> Editing Application and Application Instance Properties in the Administration guide for details. Application profiles can now be downloaded from the Admin UI. This is the same as exporting an application profile on the command line using the bwadmin export command. See Administration Tasks and Reference -> Managing an Application -> Editing Application and Application Instance Properties -> Exporting an Application Profile in the Administration guide for details. The AppSpace or AppNode configurations can be viewed and updated from the Admin UI. Updates to the AppSpace configuration made from the Admin UI are applied to all the AppNodes contained in that AppSpace. This is the same as running the bwadmin config command on the command line to update the AppSpace or AppNode configurations. See Administration Tasks and Reference -> Managing AppSpaces -> Editing an AppSpace Configuration and Administration Tasks and Reference -> Managing AppNodes -> Editing an AppNode Configuration in the Administration guide for details. You can now iterate through a list of items in Level 2 entities (next and previous) in the Admin UI. See Admin UI tasks in the "Administration Tasks and Reference" section in the Administration guide.

10 10 Design-time Compensation Handlers and Compensate activity Every scope can define a compensation handler, which contains logic that gets executed to revert the logic of the scope. A compensation handler can be executed only if the scope that is belong to has been successfully executed. A compensation handler can be triggered in the following ways: implicitly, by an uncaught fault that is thrown downstream in the process. explicitly, by using the Compensate activity. FTL Palette Inspector Activity Deploy an application from TIBCO Business Studio Generate ActiveMatrix BusinessWorks processes in SVG format when generating archive file Support for partial responses in REST The FTL palette allows ActiveMatrix BusinessWorks applications to send and receive messages using TIBCO FTL. See FTL Palette in the Bindings and Palettes Reference guide for details. The Inspector activity is used to write the output of any or all activities and module properties to a file and/or standard output. This activity is particularly useful to debug processes. See Inspector in the Bindings and Palettes Reference guide for details. You can deploy an application to an AppSpace from TIBCO Business Studio. See Deploying an Application in the Application Development guide for details. For restrictions, refer to Known Issues section in the Release Notes. When creating an archive file for an application, the application packager also generates the ActiveMatrix BusinessWorks processes in SVG format, which can be rendered in the Admin UI. When you deploy this archive file and start the application, you can view the process diagrams for the processes from the Applications page in the Admin UI. Partial responses in REST helps the user to request only those fields which are required as part of response. See REST Binding in Bindings and Palettes Reference guide for details.

11 11 Design-time Support for refactoring XSD schema and WSDL entities Eclipse p2 installation for ActiveMatrix BusinessWorks Plugins A new refactoring tool for renaming entities is available as part of the Project Explorer menu. When you right-click on a particular entity, if that entity supports refactoring, a new Refactor menu containing the refactoring tools that are appropriate and available for that entity is displayed. For example, when you right-click on an XML Schema, the Refactor menu item lists a Rename XSD Schema Namespace refactoring tool. ActiveMatrix BusinessWorks plugins can now be installed from TIBCO Business Studio using the Help > Install New Software menu. The Eclipse p2 installation packages for the plugins must be downloaded and made available on an update site or directory beforehand. See Installing TIBCO ActiveMatrix BusinessWorks Plug-ins in the Installation guide for details. Samples and Scripts Core admin scripts support database/ems configuration New admin script to create a fault tolerant group with cross-engine persistence. The core admin scripts now support the bwagent configuration for PostgreSQL database with TIBCO Enterprise Message Service. A new admin script, configurebwenginegroup.sh, to create a faulttolerant group with cross-engine persistence is available. This script can be used the bwagent is configured for TIBCO ActiveSpaces.

12 12 Changes in Functionality The following are the notable changes in functionality in this release (6.2.x). Release Runtime Administration Framework The TEA Shell implementation of the backup command has been updated to support the creation of a zip archive only. The alias for path argument in the TEA Shell deploy command has been changed from '-p' to '-pa'. The backup command only supports the creation of a zip archive. The -z option for the backup command to create a zip archive is obsolete. If the argument '-s destination' is an existing folder, you can choose a name.zip for the zip archive. If the.zip qualifier is missing, the command adds the qualifier to the archive created. The alias for path argument in the TEA Shell deploy command has been changed to '-pa' to avoid ambiguity with the '-p' alias for the profilename argument. Design-time JDBC Query activity does not fetch the table metadata to construct the Output schema automatically. The JDBC Query activity automatically fetched the table metadata to construct the Output schema based on the SQL query. This behavior has been changed. Every time you want to configure the JDBC Query activity, you must fetch the table metadata manually using the Fetch button. The new behavior is similar to the behavior in TIBCO ActiveMatrix BusinessWorks 5.x version.

13 13 Release Runtime Administration Framework Changes in the file system location for the default \domains folder Changes to the OSGi commands Changes to the TIBCO Hawk MicroAgent method names Archive paths in a backup archive are now relative within the archive Persistent application state The default folder (domains) used to store runtime artifacts in the file system used to be located at TIBCO_HOME/bw/domains. This folder is now located at folder. You can change the location of the default folder used to store the runtime artifacts by updating the defaultdomain.domainhome property in the TIBCO_HOME/bw/6.2/domains/ DomainHomes.properties file. See section Configuring the Location of the Default Domains Folder in the Administration guide for details. The OSGi commands have changed. For the full list of commands, see Managing AppNodes -> Enabling the OSGi Console for an AppNode -> OSGi Runtime Statistics Commands in the Administration guide. The TIBCO Hawk MicroAgent method names have changed. For the full list of methods, see Monitoring using TIBCO Hawk -> TIBCO Hawk MicroAgent Methods in the Administration guide. When a backup is created as an archive file, the archive file is generated as <entity>_<name>.zip and contains relative paths. The destination argument can be an existing folder, or if the specified ends with a forward-slash ('/'), a folder will be created (if it does not exist already). Previously, applications did not retain their state after an AppNode was restarted. This behavior has changed and applications now retain their state when an AppNode is restarted. Samples and Scripts Changes in the file system location The core admin scripts are now available under the BW_HOME/samples/core/admin folder. See Core Admin Scripts in the Administration guide for details.

14 14 Samples and Scripts Changes to the location of the admin scripts shipped with the product Previously, all the admin scripts were installed under a single directory, BW_HOME/samples/ core/admin. These scripts are now separated into two sets and 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 sample scripts now rely on the PATH variable to find the generic scripts available under BW_HOME/ scripts/admin. The script, BW_HOME/scripts/bashrc.sh, containing the environment variables is autogenerated after installation. To set the environment variables required to run the admin scripts, add the following statement to your ~/.bashrc file to source the generated script: source BW_HOME/scripts/bashrc.sh

15 15 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 AMBW The backupdomains.sh and restoredomains.sh scripts now support the - network parameter. AMBW AMBW The bwadmin-logback and bwagent-logback files under /bw/6.2/bin now contain the code required to append the date in the log files. The log file size and rotation for the bwappnode are now configurable. Edit the logback.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 AMBW AMBW If a node crashed for some reason, the ActiveMatrix BusinessWorks engine was unable to resume when checkpointing was used. This has been fixed. Checkpointing created many locks at the database. In some cases, it escalated and created many cascade locks which affected the performance. This has been fixed. The command bwadmin mode did not work after TIBCO ActiveMatrix BusinessWorks hotfix02 was installed. This has been fixed.

16 16 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW Starting appnode from command line failed with timed out error if the TIBCO HOME contained space. The '-p' alias for path argument in the TEA Shell deploy command has been changed to '-pa' to avoid ambiguity with the '-p' alias for profilename argument. The backup script was using the -version argument to back up AppSpaces. The backup script for ActiveMatrix BusinessWorks no longer uses this argument. The TEA shell implementation of the backup command has been improved. The backup command only supports the creation of a zip archive. The -z option to create a zip archive is obsolete. If the argument '-s destination' is an existing folder, you can choose a name.zip for the zip archive. If the.zip qualifier is missing, the command adds the qualifier to the archive created. A backup of an AppSpace or domain now contains the TRA files of the AppSpace (organized by agent name) and AppNodes (organized by AppSpace). The status of an AppSpace without any AppNodes now report its status as degraded, regardless of the start/stop/create operation. The create appnode command with -r or -lax options does not work when run in a separate session of bwadmin. This has been fixed. The -na or -noarchives options were ignored by the backup command from TEA shell. As a result, the archives and applications were backed up even when you ran the backup command with option-na (or -noarchives) from the TEA shell. This has been fixed. Release AMBW AMBW AMBW AMBW-8481 On Microsoft Windows, an exception (Failed to write config file) was thrown when configuring an AppNode if the config.ini file was not written using UTF-8 encoding. After deleting an AppSpace from the AppSpace level 2 page, the first operation to delete (or create) an AppSpace in the AppSpace level 1 page was hanging. Applications did not retain their state when an AppNode was restarted. On Microsoft Windows, the bwagent listen port was not released when a process was killed. As a result, when the bwappnodes were launched again by the bwagent, the process continued to run. Bindings Release 6.2.1

17 17 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW [17495] AMBW AMBW Creating schema as part of creating REST Resource led to REST Service binding configuration error. When a service with no input was invoked using TIBCO ActiveMatrix BusinessWorks 6.2, the SOAP request was sent as Document/Literal even though RPC/Literal was used. QName picker did not display "xsd:included" components. Concrete WSDL could not be generated for SOAP Service binding if the associated HTTP Connector shared resource was defined in a shared module, and had fields that referenced module properties. SOAP client using HTTP Client shared resource did not use the specified proxy configuration to access the web service. MTOM did not work where the root node of WSDL message's part was of "type" base64binary. REST Bindings tab values were not serialized correctly if they were edited from Bindings tab of the REST service on the process. The generated concrete WSDL did not contain elements from the schema that was defined in a shared module. As a result, some elements were reported to be missing when this concrete WSDL was imported in a client. The [Copy Of]option could not be used to map the output of the Mapper activity to invoke a web service. An error was thrown when the SOAP response received from a SOAP service contained an incorrect namespace declaration. The exported concrete WSDL did not include the schemas even when the "EMBED SCHEMA" option was selected during export. Refactoring the dependent WSDL namespace caused a TIBCO-BW-BINDING- SOAP : Failed to initialize SoapServiceBinding error. A SOAP client can now directly send a request to an ActiveMatrix BusinessWorks service with a WSS username token header. If the governance agent is enabled, it enforces the policy. REST services bypassed HTTP Basic Authentication even after LDAP Configuration was provided on HTTP Connector shared resource. It did not authenticate against the credentials. When sending a REST request to invoke a REST resource using the Invoke REST API activity, the authorization header was not added to the request. Release 6.2.0

18 18 AMBW AMBW AMBW AMBW AMBW An error was thrown by the SOAP service if the SOAP address location contained a question mark character ("?"). Model/Model Schema in Swagger UI did not show anonymous complex type elements which refer to another anonymous complex type. REST Service Binding and Swagger UI did not support Optional Query Parameters at runtime even if they were defined as optional at design time. When you moved a process from a shared module into an application module using Drag and Drop mechanism, the application that contained the application module was not updated to contain the shared module. Service names, reference names, and binding names now support the use of Latin extended and CJK characters. General Release AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW When a Test Connection failed, the error message displayed on the dialog appeared truncated and the error message could not be copied using the click and select option with the mouse. This has been fixed. When assigning a value to a simple variable, the Assign activity failed with an exception if either format-date, format-time, or format-datetime functions were used. This has been fixed. The Mapper did not fully populate the choice groups with available substitutions. This has been fixed. TIBCO Business Studio hung when an XSD schema was imported in the ActiveMatrix BusinessWorks project before the dependent XSD schema. Adding conversation to a Reply activity threw a NullPointerException. When an iteration was included into a transaction activity, the input properties of the elements included in the iteration were not visible and could not be changed. NullPointerExceptions were thrown when the init method was called several times with same conversation key and then followed by a join. This has been fixed. The configuration of the Call Process activity reported errors when the Reference PortType was lost. This has been fixed. However, the fix requires you to reconfigure the Call Process and Reference activities with the appropriate settings in order to save the updated configuration.

19 19 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW Validation error was thrown when "schemalocation" tag was removed from the xsd. Mapping from a Receive activity to a SetSharedVariable activity was lost and validation errors were thrown when the focus was moved to some other activity and then returned to the mapping. This has been fixed. However, the fix requires you to remap the given SetSharedVariable activity's input once in order to store the design and runtime XSLT of the updated mapping. When Iterate group was created, the "Variable list" element used in other activity displayed an Activity configuration Error. References to schema elements were not resolved when projects were imported. TIBCO Business Studio did not validate the restriction of a nested element at design-time. This has been fixed. The Render XML XSLT function now includes namespace definitions in its output. When upgrading from version to version of the software, the installer replaced the existing configuration and.tra files. As a result, any custom configurations in the configuration or.tra files were lost. This has been fixed and the installer now creates a backup folder, <TIBCO_HOME>\bw\6.2\backup to store the configuration and.tra files before upgrading. CatchAll block using XPath expressions in transitions threw XSLT compilation error at application init time. When a Shared Resource was configured with a non-existing module property, the runtime did not report an error. The following issues caused by renaming a service or reference have been fixed: Renaming a service or reference caused the context mechanism to fail at runtime. This has been fixed and the appropriate context configuration is now updated correctly. Renaming context parameters resulted in a BPEL Variable that had no element. SetContext and GetContext activities lost their reference to a service or reference 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, can be fixed by renaming the service or reference in HF3. AMBW AMBW When copying a scope with accumulation the old element appeared to be copied, but was no longer used. Since the variable was now invalid, it caused a runtime error. When renaming an activity, there was a distinct pause between each keystroke.

20 20 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW Validation reported a false error when building an archive file if the application contained a Java module. When using coercions and substitutions in the Mapper, an element was unresolved if it was not used elsewhere in the process. Now when a coercion or substitution is done, an import for the element's namespace is added to the process, which allows the element to be correctly resolved. Mapping currentelement from Iterate group threw a validation error. REST, SOAP, and HTTP now support Basic Authentication. Import location with HTTP URL in WSDL was not supported. The FaultDetails generated in the CatchAll block was incorrect for activities that throw Data Validation Exception at run time. The JDBC activities in a transaction group failed with a NullPointerException. This has been fixed. The source $Variable node could not be mapped to the target tree. This has been fixed. You can now drag $Variables of type element to map to the target tree. Incorrect reporting of cyclic type errors by the XML Schema Parser has been fixed. An error was reported when loading projects that contain huge embedded schema if a process was loaded before all of its schemas were available. A "Failed to set CLIENTID" error was thrown, if the JMS Connection used by the deployed application was defined in a shared module. When a Confirm activity was used inside an exception scope (like CatchAll), it did not show the ConfirmEvent. The addbooks operation in the REST Bookstore sample added only up to three books at a time. This has been fixed. A design time validation error appeared on Set Shared Variable activities if they used a web service element mapping directly. This mapping error persists in the current product version, but you can resolve the error by re-mapping the input manually. Each activity with this problem will have an error marker which needs to be resolved manually. AMBW AMBW When configuring JMS or JNDI shared resources, the UI selection toggled to "None" if you specified the username and password fields using module properties. This has been fixed. Changing the default value of a module property of type String from a predefined string to an empty string resulted in validation errors.

21 21 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW A runtime error was thrown when an XPath expression contained the wildcard character '*' (any element). The application validator did not complain when there were module dependencies that were not included as part of the application. ActiveMatrix BusinessWorks 6.x design-time validation / build took a significant amount of time for complex BW6 applications. For example, applications that involved multiple modules and deeper inter-module dependencies. Optimization has been introduced to reduce the validation and build time. Mapper showed validation error when mapped to an iteration group. The bwadmin "show apps" command showed incorrect status in the local mode. When running an ActiveMatrix BusinessWorks application on Microsoft Windows 2012, an error message, com.tibco.bw.tpcl.org.hyperic.sigar, was thrown during startup. This has been fixed. The error message no longer appears and the OSGi command appnodeprocessinfo works properly. The custom XPath function failed with an error if the implementation contained a main method. 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" was thrown. When schema A imports B which includes non-chameleon C, the schema parser sometimes reported unresolved type errors. If it did report an error, then, during process execution, validation errors for elements pointing to that unresolved type were thrown. This has been fixed. Note: This behavior was observed when the schemas were parsed in a certain order and may not be seen with every import of a schema with a non-chameleon include. A StackOverflow exception was thrown by unnecessary loading and reloading of schema or WSDL components. This has been fixed. Refactoring the HTTP Shared Resource name or package did not update the HTTP connector field in REST binding. This has been fixed. Projects cannot be created with their names ending with.xsd or.wsdl. The wizard prevents the creation of a project with such a name and prompts with an "Unsupported characters" message. The default TIBCO Rendezvous port to enable Hawk microagents has been updated from 7500 to The silent installation mode now supports the installation of the runtime component alone over an existing installation of TIBCO ActiveMatrix BusinessWorks

22 22 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW PER-2055 When you renamed a partner link or an operation, the framework did not notify the Confirm activity. This has been fixed. Refactoring the dependent WSDL namespace caused an error "TIBCO-BW- BINDING-SOAP : Failed to initialize SoapServiceBinding". Using empty values in Module/Process property caused error in the project. An exception, The org.eclipse.osgi plug-in is missing from this configuration, was thrown when running an application if ActiveMatrix BusinessWorks release 6.1.1, ActiveMatrix BusinessWorks release hot fix1, and TIBCO Enterprise Message Server 8.1 were installed in the same TIBCO_HOME. This has been fixed. In the Debug Launcher, only one application could be deselected. If you tried to deselect a second application, the first application would be selected automatically. This has been fixed and you can now deselect two or more applications in the Debug Launcher. Complex elements were not visible on the Input editor. This has been fixed. 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 been fixed. During reload, the schema and wsdl caches failed to remove the stale versions of their schema and wsdl resource files. Multiple cleans (or other operations which result in cache reloads) of projects with sufficient numbers of schema and wsdl resources resulted in a very, very large cache which took a very, very long time to reload. That problem is fixed. Basic and Username Token Credential Mapping are now supported. This fix requires the use of ActiveMatrix Policy Director 2.0 with ActiveMatrix BusinessWorks 6.2. For example, this enables BW6 users to invoke ActiveMatrix BPM web services. Release AMBW AMBW AMBW When a process contained two or more Error transitions, the input mappings for all but one of the activities using the error transitions were broken and caused incorrect problem markers. While debugging, the F6 key could not be used continuously to step through the code as the focus was lost. Creating a conversation for a process that included both a service or a reference and a signal-in activity resulted in a corrupted process.

23 23 AMBW AMBW AMBW AMBW The size of the drop-down field for the Reply Activity's General Service was minimal and did not show any content by default. To resize the window, you had to select the drop-down field and enter the return key. This has been fixed. Clicking on a process file in the Project Explorer and choosing "Launch BusinessWorks Debugger" option did not start the ActiveMatrix BusinessWorks process. This has been fixed. You can now copy and paste activities from one group to another within a process. When uninstalling ActiveMatrix BusinessWorks and one or more of the following plugins from a TIBCO_HOME all at once, if ActiveMatrix BusinessWorks was uninstalled first, then the uninstallation of the remaining plugin 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 AMBW AMBW-7677 An exception, com.tibco.bw.core.runtime.activityinputvalidationexception, was thrown for a variable of long data type if the long value was greater than 6 digits. A NullPointerException was thrown when an AE activity was added to an ActiveMatrix BusinessWorks process. Module shared variable did not build its initial value correctly from XSD schema for the double-byte characters. Migration Release AMBW AMBW AMBW An Invalid SQL Exception was thrown after migration if the SQL query began with a space. This has been fixed. Migrating TIBCO ActiveMatrix BusinessWorks 5.x projects using command line failed if TIBCO_HOME name contained space. An exception was thrown when you migrated a project that contained a folder with a space in the folder name. This has been fixed.

24 24 AMBW When importing TIBCO ActiveMatrix BusinessWorks projects containing Java, HTTP or SMTP activities in TIBCO Business Studio, some processes might have been marked to be dirty (indicated by the * infront of the process name in Project Explorer). If these processes were opened, the Save button was enabled although the user had not made any changes to the process. When this project was run in Debugger, the exception com.tibco.bx.debug.mismatchedmodelexception: Node Definitions don't match BPEL Activities was thrown. Release AMBW AMBW AMBW AMBW AMBW After migration, the HTTP, JMS and Mail projects showed a duplicate header on the Input tab. XPath could not convert an integer to string automatically when the upstream activity had multiple level schema. This has been fixed. The Java Custom Function activity did not migrate successfully. Timer activity was not migrated and displayed as an empty activity after migration on a non-english platform. After migration, the Data Format shared resource reference was not generated correctly for Parse or Render data activities. Palettes Release General Activities Palette AMBW A NullPointerException was thrown by the Inspector activity when the Inspect field was set to ALL. JAVA Activities Palette AMBW AMBW When a Java activity was modified, it did not refresh its signature correctly and caused errors. This has been fixed. To trigger the refresh of a Java activity's signature, select or reselect the Java Class Name in the activity's General tab after the Java activity is modified. When running the Java Invoke activity in a multi-threaded mode under load test, an intermittent error was observed.

25 25 JAVA Activities Palette AMBW-6453 A runtime exception was thrown for Java to XML activity when trying to convert java object containing Collections. For example, List, Set, Map, or its implementations (ArrayList, and so on). JDBC Palette AMBW AMBW AMBW The SQLDirect activity has been fixed to participate in transactions. Referring out parameter to CURSOR in store procedure, showed an error in TIBCO Activematrix BusinessWorks hotfix2 instead of showing UnresolvedResultSet. The JDBC Query activity did not refresh the Output schema automatically when changes were made to the table in the database. To fix this, use the Fetch button to refresh the output schema manually. The Refresh button has been renamed to Fetch. AMBW AMBW Calling an SQLServer stored procedure failed with an exception when the JDBC Call Procedure activity was configured with a Catalog name. Module property support added for Maximum Connections field in JDBC Connection resource. JMS Palette AMBW AMBW The JMS Application Property displayed "Unresolved Element" in the Input tab if the Application Property was defined in a shared module and the activity used XML Text as Message Type. The schema payload on the Input tab of a JMS activity failed to load and a message "Unresolved reference in schema" was received if the Application Properties Type on the Advanced tab was selected. Previously, we advised users to close and re-open the project after such configuration for the activity signature to display properly. This is no longer required with this fix. REST and JSON Palette AMBW "TIBCO-BW-PALETTE-REST : An error occurred in render activity: [no message for java.lang.nullpointerexception]" exception was thrown at run time for Complex Type element with simplecontent.

26 26 REST and JSON Palette AMBW AMBW The 'XML to JSON' activity has been fixed to allow it to be added, removed, and modified without causing a configuration error. When sending a REST request to invoke a REST resource and authentication is enabled, the authorization header is not added to the request. As a result, the request failed even though the authorization information was provided. This issue was observed only with the Invoke REST API activity. XML Palette AMBW AMBW Render XML XSLT Function did not include namespace definitions in the output. An exception was thrown at runtime if the Stylesheet field in the Transform XML activity was specified using a module property and the module property contained an absolute path to the stylesheet. Release HTTP Palette AMBW AMBW AMBW-9210 AMBW-7757 The HTTP Client Resource automatically used the "chunked" form as Transfer- Encoding HTTP header value regardless of whether content-length was set in the Input tab for Apache HTTP components or not. Parameters on the Send HTTP Request activity were automatically deleted when Directory name was added on the Advance tab as Module Property. The HTTP Request activity always applied UTF-8 encoding to generate a URI encoded string for the GET method, regardless of the content-type setting in the HTTP Header. The HTTP Receiver activity always applied UTF-8 encoding to get the parameter data from URI encoded strings. The parsed parameter data in the HTTP Receiver activity was garbled if native encoding was applied to URI encoded string.

27 27 JMS Palette AMBW AMBW When configured with JMSApplicationProperties and XML Text payload, the Body element clashed and mapping could not be done in the input field. This has been fixed. However, the UI is not refreshed automatically. You must close the project and then re-open it to refresh the UI. The package name of an existing JNDI configuration was deleted if a second JMS Shared 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 the JMS Connection shared Resources that used the affected JNDI Configuration. AMBW-7449 RequestTimeout input item is now available in the JMS Request Reply activity. REST and JSON Palette AMBW AMBW 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 a different 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". The REST Invoke activity now throws a design time validation error if configured with an HTTP Client Resource which has an unsupported Implementation Library. Shared Resources AMBW When a Shared Resource field had a Module Property value, and that field was changed to Literal and then immediately back to Module Property, the Module Property choice had to be re-selected. The change to Literal Value removed the Module Property value, but the combo box still retained the old value. The old Module Property value was not saved in the Shared Resource. XML Palette AMBW An Activity output data validation error exception was thrown at runtime for schemas that contained "any" element and processcontents="strict".

28 28 XML Palette AMBW After migration, problem markers were seen for "Render-PO-XML","Map-Data", "Assign" and "Publish-CompletePO-Message". This has been fixed. AMBW In the Input of the Render XML, if each element was mapped individually with a corresponding output of Parse XML, every element was prepended with "schemas:".

29 29 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 AMBW AMBW Summary: The OSGi configuration properties have been aligned between the debug environment launched from within TIBCO Business Studio and the AppNode that is launched in an installation. However, a difference in behavior of the osgi.compatibility.bootdelegation property in both the environments has been observed. Summary: On Microsoft Windows, closing the bwadmin command window terminates the AppNodes that were started from this command window. On Microsoft Windows, child processes are terminated when their parent terminates. Bindings AMBW AMBW Summary: Swagger UI is not getting the response for invoking POST/PUT method for form parameter on Firefox browser. Summary: A 404 Not Found error is encountered if base path name is same in the Path parameter 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, will throw an error. Workaround: Use different base path names for Path and Query parameters. For example, change /books/{isbn} to /books1/{isbn}.

30 30 AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW AMBW-8982 Summary: When using inline WSDL schema for REST service, a TIBCO-BW- BINDING-REST : Error Occurred while creating User Part. Responding to client with error message. exception is thrown at run time. Workaround: Change the Inline schema targetnamespace and also update the WSDL created by the REST Resource to include a link to that inline schema. Summary: The SOAP binding style RPC encoded is not supported. Summary: Incorrect Swagger specification models are generated for REST services when using the pass through mechanism (Opaque mode). Summary: Deleting a REST Component results in permanent loss of the Bindings. Workaround: If after deletion the artifacts are not saved, quit TIBCO Business Studio without saving and this will not delete the bindings. However if artifacts are saved after deleting a binding or a component, it cannot be readded. Summary: REST Doc UI is not supported on Firefox browser. Workaround: Use other browsers for the Doc UI. Summary: For some use cases, REST Doc UI does not show the correct error code in case of Internal Server errors on the Server side. Workaround: Check the raw message that contains the correct error code. Summary: REST Doc UI does not support browsers like Internet Explorer. Workaround: Use other browsers for the Doc UI. Summary: Resolution of SOAP transport type does not work for SOAP over HTTP, if SOAP over JMS and SOAP over HTTP bindings are in the same process. Summary: Changing the Resource name in the REST service Bindings tab, does not update the Resource Service Path.