TIBCO ActiveMatrix BusinessWorks Release Notes · 2014. 5. 28. · New Features This topic describes the new features added in the TIBCO ActiveMatrix BusinessWorks product. Release

TIBCO ActiveMatrix BusinessWorks™ ReleaseNotesSoftware Release 6.1.0May 2014

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

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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

This topic describes the new features added in the TIBCO ActiveMatrix BusinessWorks product.

Release 6.1.0

The following are the highlighted features in this release.

Native Eclipse Design-time

● Brand new Business Studio Welcome Page to guide users

— How to create new applications— Access to Documentation and TIBCommunity— One-click loading of key ActiveMatrix BusinessWorks Samples, opening the Main Process, and

ready access to sample documentation● BW Eclipse “Design” Perspective tailored for integration, web and mobile application design● Product Inventory view, which provides a catalogue of ActiveMatrix BusinessWorks out-of-the-box

Palettes and Shared Resources as well those from installed BusinessWorks Plug-in Products● Support for Process level Default Binding, which is especially useful for invoking external services

from sub-processes without configuring them as Component Reference● Group with Iterate in Process design● Support of Long type in Module Property definition● Offers over 65 out-of-the-box project samples to demonstrate usage scenarios

Versatile Runtime Administration Framework

● Product Inventory view in BW Enterprise Administration UI and command line utility● Administration Web UI support for configuration update to AppSpaces, AppNodes● Supports reporting of commands execution history performed from both Web UI and command line

tools for auditing and traceability purposes● Enterprise Administration Framework access through REST/JSON API● Support of TIBCO Hawk for monitoring and management

Release 6.0.1



● Administration Web UI support for:

— Creating and deleting of Domain, AppSpace, and AppNode— Uploading and deploying Enterprise Archives (EARs)

Release 6.0.0


5


Native Eclipse Design time

● Process Designer● Shared modules for modular design of applications● Refactoring tools such as Undo, Redo, and Rename● Design time tooling for migrating BusinessWorks 5.x projects● Offers over 50 out-of-the-box project sample to demonstrate usage scenarios

Graphical Modeler for Zero-code Development

● User-friendly gestures for commonly performed tasks● Multi-operation process definitions● Support for Process Scopes● Support for Event handlers● Support for Exception handlers● Support for Conversations● Visual process debugger● Design time hot deploy debugging paradigm for agile development

Zero-resistance to Coding with Java Development Tooling

● Full-fledged Java coding and debugging with Eclipse Java IDE● Ability to develop Java/OSGi modules● Ability to develop and debug BusinessWorks Process and Java code in a single IDE

First Class Support for REST/JSON

● Wizard to convert resource definitions to testable APIs and services in a few clicks● Option to choose between XML or JSON for resource representation● Integrated Web UI for documentation and testing● Easily consumable from web and mobile applications in Javascript, Python, Ruby, and so on


● Multiple application runtime container● Elastic distributed runtime powered by in-memory data grid● Elastic distributed administration infrastructure powered by in-memory data grid● User-friendly Web UI integrated with TIBCO Enterprise Administrator

— User-friendly UI for navigating large set of complex administration assets— User-friendly UI for deploying ActiveMatrix BusinessWorks and Java Applications

● Powerful command line tools and console with scripting and interactive modes

6


Open Platform

● Activity SDK to Develop Custom Plug-ins and Extensions● OSGi Java development

7


Closed Issues

The closed issues information is organized as per Administration, Binding, General, Migration, andPalette basis. These are the closed issues for the TIBCO ActiveMatrix BusinessWorks 6.1.0 release.

AdministrationThis topic list the closed issues related to Administration.

Closed Issues in 6.1.0

Key Description

AMBW-10204 Under certain circumstances, Process configured with Message Sequencingcapability encountered ClassCastException at Runtime.

AMBW-12019 Clicking on the Machines tab on the left hand navigation pane displays agentsand installations. These lists were not filtered by the selected domain andshowed more entries than the actual entries of the domain.

AMBW-12132 Fixed an issue where clicking on the AppSpace link when looking at anAppInstance of an Application led to an empty page.

AMBW-12910 Change in behavior. Previously (in 6.0.0) the runtime status of an AppSpacewould show as Stopped even when there is at least one AppNode, but lessAppNodes than minNodes. This is now changed to Degraded. This was anomission in the previous version.

For example, AppSpace a1 has minNodes 2 and 1 AppNode n1.

In 6.0.0: Status of a1 was Stopped. In 6.0.1: Shows correct Status of a1 asDegraded.

AMBW-8763 bwdesign utility did not create the workspace, if the workspace path includeddouble-byte characters.

BindingThis topic lists closed issues related to Binding.


Key Description

AMBW-13036 The HTTP Port was not released when the REST application was undeployed.

AMBW-12155 Component Processes could not be implemented with services or publicreferences that used WSDLs defined in shared modules.

AMBW-9484 REST Binding now works with elements of Anonymous Complex Types.

AMBW-10163 The addition of a new operation to an existing REST Service that is configuredwith parameters (for example, Path Parameters, Query Parameters and so on) didnot work properly.

8


GeneralThis topic lists the closed issues related to General issues.


Key Description

AMBW-11874 Renaming the root element of the schema in the Input Editor and OutputEditor resulted in blank editor.

AMBW-4627 The process property configuration for Start Time for the Timer activity threwan error.

AMBW-6221 Pasting text into the XSLT source text field did not work.

AMBW-10553 Salesforce activities configured with coercions did not work.

AMBW-11711 The following exception was thrown when invoking external MDM WebServices:

com.tibco.pvm.dataexch.xml.util.exceptions.PmxException: PVM-

XML-106024: Cannot find XML data type:{http://www.tibco.com/cim/

services/adminservice/wsdl/2.0}LoginRequest

A similar exception was reported for projects that comtained schemas withmultiple <include> statements, either directly or indirectly, to the sameschema.

AMBW-8815 Specifying an XSD schema in the input of the operation for a service operationdid not show the XSD schema in the Input tab of the Reply activity for thatoperation.

AMBW-11250 The imported projects showed error markers that affected the validationadversely.

AMBW-11936 Referencing service WSDLs defined in a shared module resulted in runtimeerrors.

AMBW-11799 Checkpoint activity contained in a group did not recover correctly at the enginerecovery, especially an iteration group, such as For Each, While, Repeat, Repeaton Error, and so on.

AMBW-11893 Validation messages were visible even when the Select Value option forModule Shared Variable and Job Shared Variable was selected.

AMBW-12039 Conversation initiation did not function at runtime for the signal reply activitiesand worked only for Receive or Signal-In activities. You can now initiateConversation with Reply activities of JMS and HTTP.

AMBW-12087 Fixed a validation error issue for a scenario where TIBCO ActiveMatrixBusinessWorks project contained multiple schemas with same namespace. Anelement from such a schema was used in the "Data Format" shared resource. ATIBCO ActiveMatrix BusinessWorks process containing Parse/Render activityreferred to this "Data Format" shared resource.

9


Key Description

AMBW-12157 When adding a dependency on a shared module, the module was not re-validated automatically. Therefore, the errors that were fixed by introducing thenew dependency, were still reported (in the Problems View).

AMBW-12158 When removing a resource such as an XML Schema, WSDL Resource, and soon, the activities with references to the entities that are part of those resourcesdid not become invalid.

AMBW-11250 The imported projects showed error markers that adversely affected thevalidation.

AMBW-10212 Removing the Sequencing Key from the Process Starter activity, threw aNullPointerException at runtime.

AMBW-10072 Setting the value of a newly created application property did not workproperly. When the resource was saved, the value was lost.

AMBW-10129 After creating a REST Service, a Component <ComponentName> is notconfigured. exception was thrown at design time.

AMBW-10196 Launching BW Debugger with unsaved Processes sometimes triggeredNullPointerException.

PaletteThis topic lists the Closed Issues related to Palettes.


General Activities Palette

Key Description

AMBW-12089 Checkpoint activity migration is now supported.

HTTP Palette

Key Description

AMBW-12067 Write to File check box on HTTP Receiver activity is now supported.

JAVA Palette

Key Description

AMBW-12102 The Java Invoke Method activity showed an input configuration error. Anunexpected output, "Account" was thrown at design time for XML To Javaactivity.

10


Key Description

AMBW-11889 TIBCO Business Studio hung while building a workspace when the class wasselected or the Reload button was clicked in the Java To XML or XML To Javaactivity.

AMBW-12678 Output tab of Java To XML activity did not populate, if the Java class containedArrays or Wrapper Class Objects.

AMBW-12033 Java Collections is now supported for Java Invoke.

JDBC Palette

Key Description

AMBW-12649 JDBC Connection profile could not be created unless the DB activity wasdropped on the Process Editor.

AMBW-10926 A Procedure or Function when selected in JDBC Call Procedure activity,displayed the schema name in the Catalog or Package field, instead of displayingit in the Schema field.

Rendezvous Palette

Key Description

AMBW-11966 Checkpointing feature is now supported for the processes that have RendezvousSubscriber as the Process Starter.

Shared Resource

Key Description

AMBW-13333 Heartbleed vulnerability addressed.

Fix included updates to address the heartbeat extension vulnerability referencedin CVE-2014-0160 and US-CERT VU#720951. This specifically included theOpenSSL 1.0.1g libraries.

11


Known Issues

This topic describes the Known Issues added in version 6.x of the TIBCO ActiveMatrix BusinessWorks.The known issues information is organized as per Administration, Binding, General, Migration, andPalette basis.

AdministrationThis topic lists the Known Issues related to Administration.

Key Description

AMBW-12126 Summary: Applications do not retain the state when AppNode is restarted.

Workaround: None.

AMBW-13910 Summary: Updating AppSpace and Application configuration may result inerrors if the case of Domain, AppSpace, and Application, name is changed.

Workaround: Do not change the case of Domain, AppSpace, and Applicationnames when updating the configuration.

AMBW-8481 Summary: (On Windows) The bwagent listen port is not released when theprocess is killed. When the bwappNodes are launched again by the bwagent,the process continues to run.

Workaround: Always stop the bwagent process gracefully by callingbwagent.exe stop from the TIBCO ActiveMatrix BusinessWorks 6.xinstallation bin folder. Should the bwagent still fail to allocate the ports onrestart, simply wait for 10 minutes before trying again. This allows theOperating System to allocate the ports to a new process.

AMBW-13067 Summary: Deployment of an application with an invalid profile will fail thedeployment, but the UI is showing an application screen with errors. The sameapplies to other scenarios that cause the deployment to fail.

Workaround: Do not use invalid applications.

AMBW-13069 Summary: Starting an AppSpace without any AppNodes shows the runningstatus as Starting instead of Degraded.

Workaround: Refresh the page to get the status updated/reflected properly.

BindingThis topic lists the Known Issues related to Binding.

Key Description

AMBW-12668 Summary: On closing and re-opening the REST BookStore Sample, thefollowing warning message displays.

The file(Books.bwp) has changed on file system" warning message

pops up.

Workaround: None

12


Key Description

AMBW-13955 Summary: REST Binding is lost from the components when the process isremoved from the component containing the REST service and added again.

Workaround: None

AMBW-12108 Summary: REST Service green chevron icon is not displayed on the processcanvas after REST Service is created.

Workaround: Close and reopen the project.

AMBW-13834 Summary: "TIBCO-BW-PALETTE-REST-2000027:Client received a 4xxresponse for invocation at resource path" exception is thrown atruntime for the Resource Service Path with parameters, when a REST Serviceis renamed.

Workaround: None

AMBW-13904 Summary: lrestdoc command always yields the discovery URL usinglocalhost as the hostname.

Workaround: None.

AMBW-14001 Summary: When creating a project with a REST Resource or REST BindingType, the component or REST binding in Module Descriptors > Componentsis not accessible.


AMBW-13775 Summary: JSON to XML conversion fails and results in malformed JSON (orXML), when the JSON document that has a terminal 'array type' node inside acontainer type JSON node results in malformed JSON.

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-13485 Summary: REST Swagger UI does not support browsers like InternetExplorer.

Workaround: Use Chrome or Firefox browsers.

AMBW-13807 Summary: REST Service Binding and Swagger UI do not support OptionalQuery Parameters at runtime even if they are defined as optional at Designtime.

Workaround: None

AMBW-13572 Summary: Swagger UI for some use cases 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.

13


Key Description

AMBW-13890 Summary: When two or more ActiveMatrix BusinessWorks processes in amodule contain the same processReference name and at least one of theprocesssReference is configured with Binding Reference (Binding configuredat the process level) and rest are configured with external Binding References(Binding configured at the component level), then incorrect Service Provider iscalled.

Workaround: Make the processReference names unique in the module.

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

Workaround: None.

AMBW-11387 Summary: In Swagger documentation, non-ASCII characters in model schemaand parameters are garbled.

Workaround: Remove garbled character before pressing the Try it Out button.

AMBW-11408 Summary: Non-ASCII characters in the generated Swagger JSON file aregarbled.

Workaround: Remove garbled characters before pressing the Try it Outbutton.

AMBW-11542 Summary: REST Swagger UI does not support Internet Explorer browser.

Workaround: Use Google Chrome or Mozilla Firefox.

AMBW-11965 Summary: REST Bindings tab values are not serialized correctly if they areedited from Bindings tab of the REST service on the process.

Workaround: Update values in the Module Descriptors > Components >Bindings.

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-12156 Summary: When you Drag and Drop a Process from a Shared Module into anApplication Module, the Application that contains the Application Module isnot updated to contain the Shared Module.

Workaround: Explicitly add the Shared Module to the Application.

14


GeneralThis topic lists the Known Issues related to General issues.

Key Description

AMBW-13897 Summary: Unable to access the Welcome page, if it is closed after launchingTIBCO Business Studio.

Workaround: To access the Welcome page, either select Help >BusinessWorks Samples or click File > Switch Workspace > Other....

AMBW-13936 Summary: Iterate Group cannot iterate over a local element.

Workaround: Update schema to make element global or do not use localelement in the configuration.

AMBW-13996 Summary: An Illegal Argument Exception is intermittently thrown whenlaunching debugger.

Workaround: Launch the Businessworks Debugger using the DebugConfigurations dialog box.

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

Workaround: None

AMBW-14005 Summary: Testing custom palettes does not work with the run/debugshortcuts (toolbar and process right mouse popup menu).

Workaround: Use the Run/Debug launch configuration dialog and press theRun or Debug button on that dialog to launch a test engine

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-13959 Summary: When running TIBCO Business Studio on a Linux platform, youmay observe the following issues:

● Icons for the samples does not show up on the Welcome page● In the Mapper, help contents for the XPath functions does not show up

Workaround: These issues indicate that the Eclipse SWT browser is notconfigured (or not installed). A supported native browser (WebKitGTK and/orXULRunner) must be installed. To get a list of supported browsers, see http://www.eclipse.org/swt/faq.php#browserlinux

To install WebKitGTK, do the following on Ubuntu Linux:

sudo apt-get install libwebkitgtk-1.0.0

On other supported Linux flavours, run the equivalent of the above commandto install WebKitGTK.

15


HTTP://WWW.ECLIPSE.ORG/SWT/FAQ.PHP#BROWSERLINUX

HTTP://WWW.ECLIPSE.ORG/SWT/FAQ.PHP#BROWSERLINUX

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-13942 Summary: When uninstalling a set of products in a TIBCO_HOME thatinvolves TIBCO ActiveMatrix BusinessWorks, ActiveMatrix BusinessWorksPlug-in for CICS, ActiveMatrix BusinessWorks Plug-in for Data Conversionand ActiveMatrix BusinessWorks Plug-in for WebSphere MQ products all atonce, the un-installation has the possibility of uninstalling ActiveMatrixBusinessWorks first. This fails the uninstallation of the remaining ActiveMatrixBusinessWorks Plugin products.

Workaround: In this case, first uninstall all BusinessWorks Plugins beforeuninstalling BusinessWorks because the uninstallation of BusinessWorksPlugins depends on the uninstallation scripts from BusinessWorks.

AMBW-13122 Summary: Palette samples readme.link files do not display the downloadedsample help page on Windows in TIBCO Business Studio and those help pagescannot be displayed by the Internet Explorer browser on Windows.

Core and Bindings sample readme.link files are not affected.

Workaround: View the downloaded palette sample help files using a differentbrowser on Windows, for example, Firefox, Chrome.

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-13119 Summary: The LDAP SSL connection does not work with the Administrativeuser.

Workaround: None.

AMBW-13090 Summary:com.tibco.bw.core.runtime.ActivityInputValidationException

exception is thrown for a variable of Long dataType, if the Long value isgreater than 6 digits.

Workaround: Ensure that the Long value does not exceed 6 digits.

AMBW-10455 Summary: Schema cache does not parse schemas where the target namespacecontains spaces in it.

Workaround: None.

AMBW-12946 Summary: Substitution for " (any element) *" defined as part of the inlineschema for a WSDL does not resolve newly added elements.

Workaround: None.

16


Key Description

AMBW-12703 Summary: When renaming a process service, the references do not getupdated accordingly to such a process in the same or other processes.

Workaround: Open the processes that contain references to the renamedprocess, and edit them to reflect the new name.

AMBW-12426 Summary: Shared Resource names should be composed of the package name,followed by the file name (without the extension). This is a convention that thetools try to preserve. However, if the name of a shared resource is edited orchanged, it sometimes neither renames the file nor adjusts the package toreflect this convention.

Workaround: Manually move or rename the shared resource file and packageto match the existing name in the editor.

AMBW-11375 Summary: When a user changes the Application Project Name, the applicationname in the Name field of the application's Overview page editor sometimesdoes not change to stay in sync.

Workaround: Open the Overview page of the application and type in thecorrect name.

AMBW-11695 Summary: EAR file generation for a project containing Java source with multi-byte characters fails due to compilation errors.

Workaround: This EAR file generation failure caused by the compilationerrors in the java source code can be addressed by setting the default encodingfor Studio to "UTF-8". The first step is to figure out the current encoding usedby Studio.

1. In TIBCO Business Studio, click Installation Details in the About TIBCOActiveMatrix BusinessWorks dialog box.

2. Click on the Configuration tab.

3. Search for file.encoding. The value set for this property is the defaultencoding for Business Studio.

4. Change this value to UTF-8.

5. Open this file <TIBCO_HOME>/studio/3.6/eclipse/TIBCOBusinessStudio.ini.

6. On Mac, drill down further into the package contents <TIBCO_HOME>/studio/3.6/eclipse/TIBCOBusinessStudio/Contents/MacOS/

TIBCOBusinessStudio.ini.

7. In this ini file, set the property -Dfile.encoding=UTF-8.

8. Restart Business Studio and confirm that the default encoding has changedto UTF-8.

AMBW-11815 Summary: Module Shared Variable cannot initialized with XML file, if theXML file contains double-byte characters.

Workaround: None.

17


Key Description

AMBW-11554 Summary: Unable to use the Set Explicit Nil check box in the mapper.

Workaround: Map (either by dragging from the source tree or using the XPathexpression in the Edit Statement pane) to the target element. You can thenselect the Set Explicit Nil check box. This will remove the mapping, except forthe Explicit Nil.

AMBW-11936 Summary: Referencing service WSDLs defined in a shared module may resultin runtime errors.

Workaround: When creating the Reference use drag-and-drop to add the sub-process invoke to the main process. Dragging the WSDL itself causes thisproblem.

AMBW-12059 Summary: After using bwinstall to install the third party drivers, the driverdoes not get picked up when the BWApplication is launched in TIBCOBusiness Studio.

Workaround: Open the BWApplication. Launch configuration and click on theBundles tab. This will reload the launch configuration, if any new bundles areadded to the configuration from outside eclipse.

AMBW-11874 Summary: Renaming the root element of the schema in the Input Editor andOutput Editor results in blank editor.

Workaround: None.

AMBW-11923 Summary: After importing the project, the schema is lost from the Output tabof the Parse Data activity.

Workaround: Either close and reopen the project or exit and restart TIBCOBusiness Studio.

AMBW-11884 Summary: Multiple REST services cannot be selected in the Components tabof an application module.


AMBW-11595 Summary: Adding an AE activity to a BusinessWorks process encounters aNullPointerException.

Workaround: None.

AMBW-10923 Summary: When creating an application module for the first time allows"hyphen" in the package name. However, when creating application moduleagain, gives not a valid java identifier validation message.

Workaround: None.

AMBW-11250 Summary: Importing an existing Application Module results in missing Inputand Output schema.

Workaround: Use Project > Clean to refresh unresolved schema afterimporting projects.

18


Key Description

AMBW-7185 Summary: current-group() function is not available in the Data Source afteradding the ForEach Group xslt statement.

Workaround: None.

AMBW-6221 Summary: Pasting text into the XSLT source text field does not work.

Workaround: Setting the system propertycom.tibco.xml.mapper.xslt.edit is set to true, the XSLT text field iseditable, and a Parse button is provided for re-creating the mapper UI treefrom the modified XSLT.

Property is -Dcom.tibco.xml.mapper.xslt.edit=true

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

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

AMBW-4663 Summary: TIBCO ActiveMatrix BusinessWorks 6.0 Process names followstandard Java naming convention.

Workaround: This is per design.

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.

PaletteThis topic lists the Known Issues related to Palettes.

General Activities Palette

Key Description

AMBW-4627 Summary: The process property configuration for Start Time for the Timeractivity throws an error.

Workaround: Do not configure the Start Time and End Time fields withProcess Property or Module Property.

19


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.

AMBW-13777 Summary: The flag isSSL is not set, if SSL is configured on HTTP resource.Hence, it is not possible to identify whether SSL is used or not from HTTPresource object.

Workaround: None

AMBW-11263 Summary: Parameters on the Send HTTP Request activity automatically getdeleted when Directory name is added on the Advance tab as ModuleProperty.

Workaround: Add the parameters again on the Advance tab.

JAVA Palette

Key Description

AMBW-5702 Summary: For Java To XML activity, if the java object contains variable with'char' datatype, then it gets mapped to 'unsignedShort' in the correspondingXML.

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-6453 Summary: A runtime exception is thrown for Java to Xml activity when tryingto convert java object containing Collections. For example, List, Set, Map, or itsimplementations (ArrayList, and so on).

Workaround: Use Parameterized collections (for example, List<String>) inthe Java code.

20


JDBC Palette

Key Description

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

Workaround: None.

AMBW-11626 Summary: Unable to set JDBC Call procedure parameters, preparedparameters and Object as NIL by using the Set Explicit NIL check box.

Workaround: None.

JMS Palette

Key Description

AMBW-13104 Summary: Body Element structure is not shown in the Input tab of JMSRequest Reply and Send JMS Message activities when the Message Type isXML Text and the activity also references a JMS Application Properties sharedresource.

Workaround:

1. Open the affected process in a text editor (preferably an XML Text editor).

2. Navigate to the <tibex:Types> element.

3. For every <xsd:schema> element under the <tibex:Types> having targetnamespace similar to http://www.tibco.com/namespaces/tnt/plugins/jms,add <xsd:import namespace="xxx"/> (where xxx is the namespace of theJMS Application Properties XSD) under the <xsd:schema> element.

Parse Palette

Key Description

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

Workaround: None.

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

21


HTTP://WWW.TIBCO.COM/NAMESPACES/TNT/PLUGINS/JMS

REST and JSON Palette

Key Description

AMBW-13709 Summary: Specifying a value specified for the Content-Type HTTPHeader as -"application/x-www-form-urlencoded" in the Input tab of the Invoke REST APIactivity, takes application/json or application/xml according to what is selectedin Request or Response Type in the General tab at runtime by default.

Workaround: None.

AMBW-12792 Summary: Invoke REST API activity fails to call, if query parameters includenon-ASCII characters.

Workaround: None

Shared Resources

Key Description

AMBW-11984 Summary: When a Shared Resource field has a Module Property value, andthat field is changed to Literal and then immediately back to Module Property,the Module Property choice must be re-selected. The change to Literal Valueremoves the Module Property value, but the combo box still retains the oldvalue. The old Module Property value is not saved in the Shared Resource.

Workaround: Select the Module Property again to save the value.

XML Palette

Key Description

AMBW-11722 Summary: If in the Input of the Render XML each element is mappedindividually with a corresponding output of Parse XML, "schemas:" getsprepended before every element.

Workaround: None.

AMBW-12860 Summary: After migration problem markers are seen for "Render-PO-XML","Map-Data" , "Assign" and "Publish-CompletePO-Message".


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

22


Documents

TIBCO ActiveMatrix BusinessWorks Release Notes · 2014. 5. 28. · New Features This topic describes the new features added in the TIBCO ActiveMatrix BusinessWorks product. Release