TIBCO ActiveMatrix® BPM Release Notes
Software Release 2.2.0 September 2013
Two-Second Advantage® 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, The Power of Now, TIBCO ActiveMatrix, TIBCO Silver and TIBCO Business Studio are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. 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. PLEASE SEE THE README.TXT 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 © 2005-2013 TIBCO Software Inc. ALL RIGHTS RESERVED TIBCO Software Inc. Confidential Information | iii Contents
Preface ...... v Typographical Conventions ...... vi Connecting with TIBCO Resources ...... ix How to Join TIBCOmmunity ...... ix How to Access TIBCO Documentation...... ix How to Contact TIBCO Support ...... ix
Release Notes ...... 1 Upgrading ActiveMatrix BPM to Version 2.2.0 ...... 2 Upgrading if ActiveMatrix Administrator is Replicated ...... 2 Upgrading from ActiveMatrix BPM 1.1.1...... 2 New Features...... 3 BPM Core Components ...... 3 TIBCO Forms ...... 4 Clients...... 6 Platform ...... 9 Changes in Functionality ...... 14 BPM Core Components ...... 14 TIBCO Forms ...... 15 Clients...... 15 Platform ...... 16 Deprecated Features ...... 18 Work Manager ...... 18 Clients...... 20 Platform ...... 21 Migration and Compatibility ...... 22 Work Manager ...... 22 TIBCO Workspace ...... 23 Platform ...... 29 Closed Issues ...... 31 BPM Core Components ...... 31 TIBCO Business Studio Forms...... 38 Clients...... 39 Platform ...... 45 Known Issues...... 58 BPM Core Components ...... 58
TIBCO ActiveMatrix BPM Release Notes iv | Contents
TIBCO Business Studio Forms ...... 65 Clients ...... 68 Platform ...... 72
TIBCO ActiveMatrix BPM Release Notes | v Preface
TIBCO ActiveMatrix BPM is TIBCO’s next-generation business process management platform.
Topics
• Typographical Conventions, page vi • Connecting with TIBCO Resources, page ix
TIBCO ActiveMatrix BPM Release Notes vi | Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions Convention Use ENV_NAME TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation TIBCO_HOME environments. Incompatible products and multiple instances of the same product must be BPM_HOME installed into different installation environments. An installation environment consists of the following properties: • Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu. • Path The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME. TIBCO ActiveMatrix BPM installs into a directory within a TIBCO_HOME. This directory is referenced in documentation as BPM_HOME. The default value of BPM_HOME depends on the operating system. For example on Windows systems, the default value is C:\Program Files (x86)\tibco\amx-bpm\2.2
CONFIG_HOME The directory that stores the TIBCO ActiveMatrix BPM configuration information, such as property and log files. The value of CONFIG_HOME depends on the operating system. For example, on Windows systems, the default value is C:\ProgramData\amx-bpm\tibco\data.
code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code font Bold code font is used in the following ways:
• In procedures, to indicate what a user types. For example: Type admin. • In large code samples, to indicate the parts of the sample that are of particular interest. • In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]
TIBCO ActiveMatrix BPM Release Notes Preface | vii
Table 1 General Typographical Conventions (Cont’d) Convention Use italic font Italic font is used in the following ways: • To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts. • To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. • To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName
Key Key name separated by a plus sign indicate keys pressed simultaneously. For example: combinations Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.
Table 2 Syntax Typographical Conventions
Convention Use
[ ] An optional item in a command or code syntax. For example:
MyCommand [optional_parameter] required_parameter
| A logical OR that separates multiple items of which only one may be chosen. For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
TIBCO ActiveMatrix BPM Release Notes viii | Typographical Conventions
Table 2 Syntax Typographical Conventions Convention Use
{ } A logical group of items in a command. Other syntax notations may appear within each logical group. For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4} In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4} In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
TIBCO ActiveMatrix BPM Release Notes Preface | ix
Connecting with TIBCO Resources
How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.
How to Access TIBCO Documentation You can access TIBCO documentation here: http://docs.tibco.com
How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, contact TIBCO Support as follows: • For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: http://www.tibco.com/services/support • If you already have a valid maintenance or support contract, visit this site: https://support.tibco.com Entry to this site requires a user name and password. If you do not have a user name, you can request one.
TIBCO ActiveMatrix BPM Release Notes x | Connecting with TIBCO Resources
TIBCO ActiveMatrix BPM Release Notes | 1 Release Notes
Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.
Topics
• Upgrading ActiveMatrix BPM to Version 2.2.0, page 2 • New Features, page 3 • Changes in Functionality, page 14 • Deprecated Features, page 18 • Migration and Compatibility, page 22 • Closed Issues, page 31 • Known Issues, page 58
TIBCO ActiveMatrix BPM Release Notes 2 | Release Notes
Upgrading ActiveMatrix BPM to Version 2.2.0
To upgrade your existing ActiveMatrix BPM system to version 2.2.0, follow the information given in TIBCO ActiveMatrix BPM Installation and Configuration. The additional information in this section indicates some specific points you should be aware of. See Migration and Compatibility on page 22 for actions that you may need to take after you have upgraded your system.
Upgrading if ActiveMatrix Administrator is Replicated To perform an upgrade if ActiveMatrix Administrator is replicated, you must upgrade your ActiveMatrix Platform to version 3.1.5-HF-008. It is strongly recommended to upgrade to version 3.1.5-HF-11.
Upgrading from ActiveMatrix BPM 1.1.1 If you are upgrading from TIBCO ActiveMatrix BPM version 1.1.1, or earlier, to version 2.2.0, you must upgrade your ActiveMatrix Platform to version 3.1.2-HF-005, or greater, before upgrading TIBCO ActiveMatrix BPM. More recent versions of TIBCO ActiveMatrix BPM do not require this step.
TIBCO ActiveMatrix BPM Release Notes New Features | 3
New Features
This section lists features added at Release 2.2.0 for the following components: • BPM Core Components • TIBCO Forms • Clients • Platform
BPM Core Components
Work Manager
Platform, Database, and Browser Support TIBCO ActiveMatrix BPM is now supported on Microsoft Windows Server 2012. See TIBCO ActiveMatrix BPM Installation and Configuration for full details of supported operating systems. Microsoft SQL Server 2012 is now a supported database. New browser versions are also supported.
See TIB_amx-bpm_2.2.0_readme.txt for full details of supported database and browser versions.
Service API Change / Application Upgrade A comparison tool now checks the compatibility of a service (and thus the feasibility of an application upgrade). It allows changes to the WSDL where it would not cause process instance upgrade compatibility issues. See "WSDL Change Considerations for Application Upgrade" in TIBCO Business Studio BPM Implementation Guide.
Additional XSD and WSDL Constructs Supported TIBCO ActiveMatrix BPM now supports the following additional XSD and WSDL constructs: • Copying a WSDL or an imported XSD from a remote location into a relative path
• Schemas where the XSD or WSDL is recovered by a URI, such as
TIBCO ActiveMatrix BPM Release Notes 4 | Release Notes
• Mixed constructs, for both XSD and WSDL files
JVM Information Utility The new JVMInfo utility enables you to view the current status of a JVM process, for example memory, threads, or classes. You can use it to get a summary, or to monitor the process continuously. See TIBCO ActiveMatrix BPM - BPM Administrationfor information on JVMInfo.
TIBCO Hawk Rulebases TIBCO Hawk rulebases are generated using the TCT when you are installing a TIBCO ActiveMatrix BPM system or when configuring BPM nodes. These can be used to monitor the host system, the TIBCO ActiveMatrix BPM JVM processes, and the TIBCO ActiveMatrix BPM log files. A command-line utility is provided to generate rulebases when the TCT is not used, such as at upgrade. See TIBCO ActiveMatrix BPM Installation and Configuration and the TIBCO HAWK ActiveMatrix Plug-in User’s Guide.
Getting an Organization Model from the Process Object It is now possible to get the organization model from the process object by using a process script, for example:
var OrgModel orgModel = Process.getOrgModel();
ActiveMatrix BPM Distribution for TIBCO Silver® Fabric TIBCO ActiveMatrix BPM can now use database servers, EMS servers and similar services delivered by TIBCO Silver Fabric engines.
Process Manager
Performance A change to the way that the BPM Process Engine extracts data improves its performance in task scheduling.
TIBCO Forms
Dynamic Validation of Forms TIBCO Forms now supports substitution variables in validation messages; for example, "{0} is not a valid value, must be between {1} and {2}". In addition, messages may be configured as keys referencing display strings in external resource bundles.
TIBCO ActiveMatrix BPM Release Notes New Features | 5
For more information, see the Validating Data in a Form section in the Tasks chapter of TIBCO Business Studio Forms User’s Guide.
Forms Entry and Validation Enhancements TIBCO Forms now supports: • API access to messages in the messages pane. This helps you add and edit your own messages. For more information, see the Reference chapter of TIBCO Business Studio Forms User’s Guide. • Validating input in a grid pane without losing focus on the cell. • Clickable validation messages that set the focus on the control responsible for the validation error. For more information, see the Validating Data in a Form section in the Tasks chapter of TIBCO Business Studio Forms User’s Guide.
Resource Bundles It is now possible to add support for new languages to TIBCO Forms, independent of a TIBCO Forms release, by adding a resource bundle. This: • Enables a new language for the common resource bundle to be deployed. • Enables you to override values of the keys in the built-in common resource bundle, allowing you to override the standard messages provided by TIBCO. You can also add custom key-value pairs to the common resource bundle. For more information, see the Customizing Property Resource Bundles section in the Tasks chapter, and the Common Resource Keys section in the Reference chapter of TIBCO Business Studio Forms User’s Guide.
New Forms APIs In this release, there are new APIs as follows: — New utility methods that can be used in validations — A logging API that can be used in custom clients — An API that provides additional functionality in programmatically setting the focus on controls in grid panes — APIs that can dynamically add custom messages to message panes — A method that returns the base URL to the Presentation Resources folder of the project, in which the custom control is defined.
TIBCO ActiveMatrix BPM Release Notes 6 | Release Notes
For more information, see the Reference chapter of TIBCO Business Studio Forms User’s Guide.
Clients
TIBCO Openspace
Accessible Openspace TIBCO Openspace now provides an accessible persona, reached by specifying its own URL. This persona caters for users who may have impaired vision, or who may have motor control issues that hinder their using a mouse. Therefore, the accessible persona makes it possible to: • Navigate Openspace using only the keyboard, • Use assistive technology such as screen readers or screen magnifiers for the information displayed in Openspace. The accessible persona includes accessible versions of: • The login/logout procedures • Business Services • Process Views • Work Views •Forms To access Openspace, type the Openspace login URL into your browser. The URL is:
protocol://host:port/openspace/lite.html where: • protocol is the communications protocol being used by Openspace, either http or https. This was determined at installation. • host is the DNS name or IP address of the server hosting the BPM runtime. • port is the port being used by Openspace. The default value is 8080.
When elements have focus in accessible openspace, they are displayed with an outline, consisting of a dotted border. If you do not want the elements to be displayed with an outline, remove the *:focus CSS declaration in the accessibility.css stylesheet.
See TIBCO Openspace User’s Guide for more information.
TIBCO ActiveMatrix BPM Release Notes New Features | 7
Work Item Preview There is now a work item data preview option in the Work View gadget. This allows you to see the available form fields and any data that they contain. See TIBCO Openspace User’s Guide for more information.
Work Views Enchancements have been made to the Create New View wizard. • The View of an entity in the org model has been enhanced to include an option for showing ALLOCATED or OFFERED work items. Previously only OFFERED items were shown. •A new View of the global work list option is available. This options shows all work items in the system. The user must have the viewGlobalWorkList system action for this option to be available. See TIBCO Openspace User’s Guide for more information.
Configuring Custom Functionality Openspace now allows you to call your own customized scripts when various events are triggered in Openspace. For example, you may want users to log into a third-party system before automatically logging into Openspace or you may want them to be redirected to a customized URL when logging out of Openspace. See TIBCO Openspace Customization Guide for more information.
Configuring Sort Order Sort order relates to the order of all characters in the unicode character set (for example, numeric, alphabetic, symbol, and so on). Openspace now allows you to customize the sort order that is used, for example, if you have locale-specific conventions. See TIBCO Openspace Customization Guide for more information.
Configuring Layouts You can customize the layouts that are available in Openspace. By default, there are four built-in layouts in Openspace and only these are available for use. There are also some sample layouts defined in the config.properties file. Openspace now allows you to customize the built-in layouts, make the sample layouts available as they or customize them, or create new layouts. See TIBCO Openspace Customization Guide for more information.
TIBCO ActiveMatrix BPM Release Notes 8 | Release Notes
Configuring the Locale Limit
A new locale.limit property in the config.properties file allows you limit the number of language packs that Openspace checks for when it is loading. This is because there are 57 known locales and Openspace checks for each one when it is loading. This can have an impact on the time it takes for Openspace to load. By specifying a limit to the language packs that Openspace checks for, you can considerably shorten the time it takes for Openspace to load. See TIBCO Openspace Customization Guide for more information.
TIBCO Workspace •A new startBusinessServiceWithData Tools Interface method has been added, which allows starting of business services that have formal parameters. The openworkitem sample application was also updated to allow you to start business services that contain formal parameters by including the appropriate data in the URL. The wccApplicationMethods sample application was also updated to include the new startBusinessServiceWithData method. • Two new user access elements (WorkItemFloatOverride and BusinessServiceFloatOverride) have been added to the userAccess.xml file. The WorkItemFloatOverride element controls whether or not the Work Item Forms section is displayed on the Work Items page of the Options dialog. The BusinessServiceFloatOverride element controls whether or not the “Float” portion of the Business Service Forms section is displayed on the Business Services page of the Options dialog. Previously, the WorkItem Forms section, and the “Float” portion of the Business Service Forms section, did not appear on the Options dialog if the user did not have access to the work item or business service lists, respectively. Even though a user may not have access to those lists, they may still use forms that are opened via Tools methods in custom code. The new user access elements provide the ability to control floating forms in these situations. •A new localeKey configuration parameter has been added that is used to specify the default language for the application. • The fields on the Define LDAP Source dialog in the Organization Browser have been rearranged to allow for longer, more complex, queries. • A new Tools Interface method, openNextWorkItemEx, has been added, which allows you to open the next available work item in the Inbox, based on the specified filter and sort criteria. •A new All Work Items option has been added to the New Work View - Supervised Work dialog, which allows you to specify that the new work view include all work
TIBCO ActiveMatrix BPM Release Notes New Features | 9
items irrespective of the resource or organizational entity to which the work items are offered or allocated.
A new AllWorkItems user access control has also been added to the userAccess.xml file to control access to this new functionality. •A new Data Preview tab has been added to the work item list preview pane that shows the data for the currently selected work item. It provides a preview the work item data without having to open the work item.
Two new PreviewData user access controls have also been added to the userAccess.xml file to control access to the new tab, one for supervised work views and one for personal work views. • Custom interfaces have been added to Workspace that allow you to create custom menus and toolbar buttons to be displayed in a WCC application that, when selected, display: — web pages in iFrames, — web pages in TIBCO PageBus Managed Hub iFrames, or — TIBCO General Interface prototypes. For details, see the “Customizations” chapter in the TIBCO Workspace Configuration and Customization guide.
Platform
Management of Older Hosts and Nodes ActiveMatrix Administrator supports full compatibility with hosts and nodes on prior versions of ActiveMatrix (3.1.5 and higher). In other words, ActiveMatrix Administrator server in this version can manage ActiveMatrix runtime hosts and nodes of versions 3.1.5, 3.2.0 and 3.3.0, including the creation of new nodes of a specific older version. This means there are no longer restrictions on partially upgrading of your existing ActiveMatrix enterprise. After upgrading the ActiveMatrix Administrator servers to the latest version, you can now make the choice to upgrade the rest of your enterprise gradually in a phased manner, or to retain your existing nodes and applications without upgrading at all.
The ability to partially upgrade an enterprise aligns itself well with the use-cases for
TIBCO ActiveMatrix BPM Release Notes 10 | Release Notes
multi-tenancy, also described next.
Multi-tenancy Multi-tenancy support enables serving multiple client-organizations (tenants) with a single instance of the TIBCO ActiveMatrix.
Isolation of Hosts A registered TIBCO Host can now be restricted for visibility to specific Environments. ActiveMatrix Administrator now provides a way to associate a Host to specific Environments. When a Host is associated with an Environment it becomes visible to that Environment while creating new nodes. Otherwise it remains hidden, disallowing new nodes from being created on that Host. Multi-tenant systems need good isolation across tenants, and the Host-Environment association can be used to restrict your enterprise assets based on the tenant's Environment.
Resource Template Scoping In a similar way to substitution variable scoping, Resource Templates can now be created at 3 scopes - global (enterprise-wide), environment or an application. Resource templates are configurations meant for sharing. By creating them at an appropriate scope, you can restrict their visibility and provide isolation across Environments, which is a requirement for a multi-tenant system. Here is how scopes for Resource Templates work: • Global resource templates - visible across all Environments for the purpose of creating resource instances, promoting the widest sharing. • Environment scoped resource templates - visible only within an Environment, but sharable across applications in that Environment. • Application-scoped resource templates - have special behavior that resource instances are automatically created when the application is deployed to nodes, and automatically uninstalled when the application is undeployed from nodes. The resource templates are closely tied to the lifecycle of the application itself. These do allow sharing across applications, with some restrictions.
TIBCO ActiveMatrix BPM Release Notes New Features | 11
SOAP
W3C SOAP/JMS TIBCO Business Studio and TIBCO ActiveMatrix Administrator provide the option to choose between TIBCO's SOAP/JMS and W3C SOAP/JMS on SOAP binding type and a target service while adding a binding to a service. The W3C SOAP/JMS Specification is available at: http://www.w3.org/TR/soapjms/
MTOM (Message Transmission Optimization Mechanism) MTOM (Message Transmission Optimization Mechanism) is now supported on the SOAP Binding. This can be used to send or receive binary data as attachments. The MTOM Specification is available at: http://www.w3.org/TR/soap12-mtom/
Multiple Correlation Schemes for SOAP/JMS SOAP Binding Type now supports multiples Correlation Schemes for SOAP/JMS service and reference binding. The supported correlation schemes are: • MessageID-to-CorrelationID (Send a request message and create a message listener with message ID as the selector which is the default behavior) • CorrelationID-to-CorrelationID (Create a correlation ID for the request message and create a message listener with this correlation ID as the selector) • Infer-from-Request (applicable only to the service side)
Overriding SOAP Reference URI An endpoint URI is the URL of an external service that is accessed by a business service. Support is available for changing the endpoint URI for SOAP-HTTP reference from the Administrator UI and using command-line.
TIBCO Hawk ActiveMatrix Plug-in TIBCO Hawk ActiveMatrix Plug-in is now embedded in TIBCO ActiveMatrix. Separate installation is not required. See the TIBCO Hawk ActiveMatrix Plug-in User’s Guide for more information about configuring and using this plug-in.
The plug-in now supports Hawk 5.0 in addition to Hawk 4.9.
HTTP • Support for HTTP Proxy on the Composite Reference is provided.
TIBCO ActiveMatrix BPM Release Notes 12 | Release Notes
• HTTP and SOCKS V4/V5 proxies can now be configured for HTTP Client Resource Templates.
Single Sign-On Single Sign-on functionality is now supported for SiteMinder and IWA (Integrated Windows Authentication) using Kerbreros. This includes SSO support for WebApps, PaaS services, RESTful services, and the Java Connector API.
WebApp Implementation Type • SSO is supported for WebApps hosted on WebApp IT that use SAML, SiteMinder, and Kerberos/SPNEGO tokens. • WebApps can now be configured with web.xml to create OSGi Plug-ins. • Thread context class loading (TCCL) is now supported for OSGi-based Web Apps.
Miscellaneous • Virtualization queues created by user applications are now cleaned up when the applications are deleted. • The creation and execution of scripts to build and deploy DAAs is now supported. • Java 7 is now supported.
Java • Transaction support across multiple Java based components running within the same Java-based node (same JVM) • Access to request context •
TIBCO HAWK ActiveMatrix Plug-in • ActiveMatrix Host Microagent The ActiveMatrix Host Microagent enables the monitoring and management of TIBCO ActiveMatrix host and nodes running on each local machine. It provides methods to retrieve node status and Host status, as well as control methods to start and stop nodes. • Common Logging Event Publisher Microagent This microagent publishes events from TIBCO Hawk using the TIBCO Common Logging in the Base Event Format (BEF)/Common Base Event (CBE).
TIBCO ActiveMatrix BPM Release Notes New Features | 13
• ActiveMatrix Service Microagent The ActiveMatrix Service Microagent allows runtime monitoring of ActiveMatrix components and services on each local node. An associated Monitoring Application must be installed and deployed to each node under management. This is the first release of this microagent.
TIBCO ActiveMatrix BPM Release Notes 14 | Release Notes
Changes in Functionality
BPM Core Components
Work Manager
Event Collector In previous versions, Event Collector used the isPrimary flag to determine whether attributes could be used for sorting and filtering. Attributes can now have new isSortable and isFilterable properties. A new option parameter determines whether API operations should use these new properties or continue to operate as previously. The output from the Event Collector Audit Purge operations has been enhanced so that, as an alternative to a single consolidated message, there is an option to return data items as fields in the purgeStatus object.
Process Manager
System Actions New system actions have been introduced in order to protect the ProcessManagerService API operations that make bulk changes to process instances. The following new system actions are available:
System Action Operation bulkCancelProcessInstances cancelProcessInstances
bulkResumeProcessInstances resumeProcessInstances
bulkSuspendProcessInstances suspendProcessInstances
See the TIBCO ActiveMatrix BPM Developer’s Guide for details.
TIBCO ActiveMatrix BPM Release Notes Changes in Functionality | 15
TIBCO Forms • Relative bindings are now replaced with absolute ancestor pane value bindings. With this change, it is now easier to move form elements within the form. The drag and drop functionality also has been improved to handle such drops intelligently. • A new button is now added to the Business Studio main toolbar that copies the preview URL of the displayed form. Clicking the button copies the URL to the system clipboard, from where it can be later pasted into the address bar of a browser to view the form. • It is now possible to render a read-only view of form data. For more details, see the API for Scripting section in TIBCO Business Studio Forms User’s Guide.
Clients
Openspace
System Actions New sytem actions have been introduced. See the TIBCO ActiveMatrix BPM Web Client API Developer’s Guide for details.
Authentication getAuthenticatedGUID getAuthenticatedUsername isActionAuthorised
Login Services loginAction
Logout Services logoutAction
Process Template Services retryHaltedProcessInstances
Session invalidateSession
TIBCO ActiveMatrix BPM Release Notes 16 | Release Notes
Workitem Service getOrgEntityConfigAttribute setOrgEntityConfigAttribute prioritiseWorkItem
TIBCO Workspace • The Open Next Work Item and Auto-Repeat Open Next Item functions can now be used on all personal (“My Work”) work views; previously, they only worked on the Inbox. Also, the Refine view filter and Sort list contents functions on the work item list are no longer disabled when the Auto-Repeat Open Next Item function is turned on. • Support for TIBCO General Interface forms has been removed. WCC applications (including the default Workspace application) must now use Goggle Web Toolkit (GWT)-rendered forms. • The resource list displayed in the Organization Browser when you select an LDAP container no longer shows attributes and capabilities by default. This provides better performance when the resource list is displayed. Attributes and capabilities can optionally be displayed in the container resource list by selecting the new Show attributes/capabilities in the container list option on the resource list Tools menu.
Platform • On some operating system platforms, you must download Oracle Java 7 Elliptic Curve Cryptography (ECC) LGPL separately. Oracle ships the SunEC (an ECC implementation) library as part of JRE 7. The SunEC library is covered by a different license (LGPL). Install this library to take advantage of ECC. The TIBCO Universal Installer automatically downloads the library for you from download.tibco.com during installation.
If you do not wish to use the Elliptic Curve Cryptography library, you may delete the library named libsunec.so (on Solaris and Linux systems) or sunec.dll (on Windows systems) or libsunec.dylib (on MacOS) from the TIBCOJRE bin directory reserved for native libraries.
Note: IBM's implementation of Java 7 includes ECC, but ECC does not fall under a separate license as it does in Oracle's implementation.
TIBCO ActiveMatrix BPM Release Notes Changes in Functionality | 17
• As of 3.2.0, the internal HTTP load balancer is no longer required when replicating TIBCO ActiveMatrix Administrator servers.
TIBCO ActiveMatrix BPM Release Notes 18 | Release Notes
Deprecated Features
This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it will be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features. This section also lists features that are removed (if any).
Work Manager
SQL Server 2008 Support for SQL Server 2008 is withdrawn at TIBCO ActiveMatrix BPM version 2.2. Customers are recommended to upgrade to SQL Server 2008 R2 or SQL Server 2012. See TIBCO ActiveMatrix BPM Installation and Configuration for full details of supported databases.
Support for GI Presentation Channels Support for TIBCO General Interface (GI) forms, which were deprecated in favor of GWT-based alternatives in Version 1.3.1, has now been discontinued at design time. If you have existing applications that use a GI presentation channel, see "Configuring Deployment with GI Presentation Channels" in TIBCO ActiveMatrix BPM - BPM Administration for information on what you can do.
BPM APIs The following Deadline and Calendar services are deprecated:
Deprecated Use Instead CalendarService WorkCalService
In BusinessDeadlineService, the calcDeadline in the same service CalcBusinessDeadline operation
TIBCO ActiveMatrix BPM Release Notes Deprecated Features | 19
The following Directory services are deprecated:
Deprecated Use Instead AttributeService, Operations in OrgResourceService or BrowseModelService OrgModelService. See the "AttributeService" and "BrowseModelService" chapters in TIBCO ActiveMatrix BPM Developer’s Guide for a full list.
ContainerService DirectoryService
LDAPService DirectoryService
MappingService OrgResourceService
All operations in EntityResolverService OrgResourceService except the lookupUser operation
The executeQuery and executeRegisteredQuery operations in the EventCollectorQue- ryService (which had previously been deprecated) have now been removed and are no longer available. Use the executeGenericQuery and executeRegisteredGenericQuery operations instead.
Event Collector - primaryAttributes List The following attributes are deprecated from the primaryAttributes list. These attributes are unused and will be taken out in future releases.
Common ENTITY_ID ENTITY_TYPE SYS_ACTION_ID RESOURCE_ID
DE LDAP_RESOURCE_ID PUSH_DEST
TIBCO ActiveMatrix BPM Release Notes 20 | Release Notes
PUSH_DEST_TARGET SYS_ACTION_COMP_ID
WPCOMMON CHANNEL_ID
Scripting Methods The following scripting methods, on a BOM field of type date, time, or datetime, are deprecated: — setTime(int hour, int minute, int second, int millisecond) — clear()
Clients
TIBCO Workspace • The following event attributes have been deprecated in this release for filtering and sorting event views:
Attribute Name used in Default U.S. English Description filter/sort shown in Event Viewer ldapResourceId LDAP resource ID
channelID Channel ID
pushDestination Push destination
pushDestinationTarget Push destination target
systemActionComponentId System action component ID
systemActionId System action ID
Event views should no longer be filtered nor sorted on these attributes, as they will be removed in a future release.
TIBCO ActiveMatrix BPM Release Notes Deprecated Features | 21
Platform • Support for the following platforms is deprecated: — Solaris (32-bit) — SPARC (32-bit) • The following are no longer supported: — Oracle Solaris 9 — Windows Server 2003 — Windows Vista — IBM AIX 5.3 — Java 6 • TIBCO Enterprise Message Service ™ 5.1.5 is not supported for use with TIBCO ActiveMatrix version 3.3.0. • In TIBCO ActiveMatrix Administrator, the Infrastructure > Enterprise Graphical view has been deprecated due to limited use cases and its dependency on Microsoft Silverlight. The view will be removed in future releases.
Java • The @Start and @Stop annotations are deprecated. For backward compatibility four life cycle events—Init, Start, Stop, and Destroy—are supported. However, since the SCA specification for Java defines only two life cycle annotations, @Init and @Destroy, only two methods are provided when a Java component implementation is generated. However, when an application or component is started, the runtime will deliver @Init and @Start events to the component. When an application or component is stopped, the runtime will deliver @Stop and @Destroy events.
TIBCO ActiveMatrix BPM Release Notes 22 | Release Notes
Migration and Compatibility
This section describes the migration and compatibility issues for the named releases. Refer to TIBCO ActiveMatrix BPM Installation and Configuration for upgrade instructions.
Work Manager
Version 1.3.n to Version 2.n
Organization Model Versions Up to and including version 1.3, Organization model functions in Work Manager scripts defaulted to using the latest available version of the organization model (if no other version was explicitly specified). From version 2.0.0 this behavior changes, and functions now default to using the organization model major version specified in the work model from which the script originates. When upgrading to version 2.n you can choose which behavior to use by setting a new useWorkModelOrgVersion property in the brm.properties file: • By default this is set to false in an upgraded system; organization model versions are treated as before. • If you set this property manually to true, organization model versions are handled as described above for new version 2.0.0 systems.
Validation of Boolean Fields Up to and including version 1.3, there was no validation of boolean field values in the BPM API. You could enter any value in a boolean field, and when passed from the API as work item data any value other than true would be treated as a value of false. At version 2.0.0 this behavior changes, and in new systems boolean fields accept only the following values: true, false, 1, 0 When upgrading to version 2.n you can choose which behavior to use by setting a new enhancedBooleanValidation property in the brm.properties file: • By default this is set to false in an upgraded system; boolean values are unvalidated as before.
TIBCO ActiveMatrix BPM Release Notes Migration and Compatibility | 23
• If you set this property manually to true, boolean fields are validated as described above for new version 2.0.0 systems.
Version 1.2.0 to Version 1.3.n
BPM API - Using getWorkListItems in a Client Application Up to and including version 1.2, the entityID element used by the getWorkListItems operation is contained within a choice element. In some programming environments (such as .NET in its default form), choice elements are represented by a parent entity (in this case, Item) which can be cast to any of the types which the choice allows. In version 1.3, the choice element was removed. An existing application built using the version 1.2 BPM web service API will continue to run against TIBCO ActiveMatrix BPM version 1.3. However, if you rebuild an existing application (that uses getWorkListItems) against the version 1.3 BPM web service API, you should change your code to directly use entityID (instead of casting). For more information, see the TIBCO ActiveMatrix BPM - BPM Developer’s Guide.
Version 1.1.0 to Any Version
Transaction Recovery after Upgrade on Oracle After upgrading an Oracle system, if you are planning to use Transaction Recovery, you must grant the TIBCO ActiveMatrix BPM user the correct privileges as follows: To grant the privileges, execute the following SQL statements as the "sys" user:
GRANT SELECT ON sys.dba_pending_transactions TO user GRANT EXECUTE ON sys.dbms_xa TO user GRANT SELECT ON sys.dba_2pc_pending TO user
TIBCO Workspace This section describes migration issues if you are upgrading TIBCO Workspace from a previous version.
TIBCO ActiveMatrix BPM Release Notes 24 | Release Notes
The most common migration issues involve handling new configuration parameters (in config.xml) and user access elements (in userAccess.xml). The way in which you make use of new configuration parameters and user access elements after upgrading depends on whether you are using the Workspace application or a custom WCC application. The following sections describe what to do depending on the type of application you are using. Then the sections that follow those list the configuration parameters and user access elements that have been added in each new release of Workspace.
Workspace Application If you are running the Workspace application, any new configuration parameters are automatically available after you upgrade. If you are using the Workspace application, any new user access elements are automatically included in the AccessDefaults user access profile after you upgrade. However, if you have user access profiles other than AccessDefaults, you must manually add the new elements to those profiles to make use of them.
Custom WCC Application If you are running a custom WCC application, and want to make use of new configuration parameters and user access elements, you must manually add them to your application’s config.xml file and userAccess.xml file, respectively, on your development environment file system. You will then need to create a new .war file for your custom application, and redeploy the application using ActiveMatrix Administrator. For information about the process of creating the .war file and deploying an application, see the Deploying an Application After Customizing section in the TIBCO Workspace Configuration and Customization guide. Also note the following: • You must upgrade WCC in your development environment prior to creating the new .war file. After upgrading WCC in your development environment, you must also perform the following tasks: — Copy your custom application-specific directory from the previous release to the new release. For example, if the name of your custom application is "accounts", copy this directory: StudioHome\wcc\oldVersion\JSXAPPS\accounts\ to: StudioHome\wcc\newVersion\JSXAPPS\ — Copy the launch fragment for your custom application from the previous release to the new release. For example, if the name of your custom application is "accounts", copy: StudioHome\wcc\oldVersion\accounts.html
TIBCO ActiveMatrix BPM Release Notes Migration and Compatibility | 25
to: StudioHome\wcc\newVersion\accounts.html
— Copy the .war creation command file for your custom application from the previous release to the new release. For example, if the name of your custom application is "accounts", copy: StudioHome\wcc\oldVersion\accounts.create.war.cmd to: StudioHome\wcc\newVersion\accounts.create.war.cmd
where oldVersion is the version you are upgrading from and newVersion is the new version to which you are upgrading. • If you choose not to utilize the new configuration parameters and user access elements, and you do not redeploy, your custom WCC application will not pick up the new WCC runtime; you must still create the .war file and redeploy for your application to utilize the new runtime, even if you don't want to use the new parameters and elements. • If you add the new configuration parameters and user access elements to the files in your development environment, and then create the .war file and redeploy, they will not be picked up in your WCC application if you had previously accessed the Configuration Administrator and made changes to configuration or user access that would result in the settings being stored in the database. If this is the case, after redeploying, you would need to open Configuration Administrator and either click the Defaults button to pick up the changes you made to the files in the development environment, or duplicate the changes you made to the files in the database using the Configuration Administrator interface. (For more information about using the Configuration Administrator and how it writes information to the database, see the Using the Configuration Administrator section in the TIBCO Workspace Configuration and Customization guide.)
Version 2.x.0 to 2.2.0 The following new configuration parameters has been added in Workspace version 2.2.0: • localeKey • getBinaryLDAPAttributes The following new user access elements have been added in Workspace version 2.2.0: • WorkView > SupervisedWorkItem > PreviewData • WorkView > WorkItem > PreviewData • WorkView > SupervisedWorkItem > AllWorkItems • ConfigureOptions > WorkItemFloatOverride
TIBCO ActiveMatrix BPM Release Notes 26 | Release Notes
• ConfigureOptions > BusinessServiceFloatOverride
For descriptions of these parameters and elements, see the Release Notes.
General Interface (GI) Forms No Longer Supported Support for General Interface (GI) forms has been removed in Workspace version 2.2.0. Therefore, if you are running a custom WCC application that has been configured to use GI forms, you must re-configure it to use GWT forms by performing the following steps (no action is necessary if your custom WCC application is already configured to use GWT forms):
1. Ensure that your application is using the appropriate jsx3.gui.window.html file. When the custom application was created, two of these files where provided, one for use with GI forms and one for use with GWT forms. As your application has been using GI forms, rename the current jsx3.gui.window.html file to jsx3.gui.window_giforms.html, then rename the other one (that is likely named something like jsx3.gui.window_gwtforms.html) to jsx3.gui.window.html.
The jsx3.gui.window.html file is located here: StudioHome\wcc\version\ where: — StudioHome is the directory in which TIBCO Business Studio was installed. — version is the version number of Workspace that was installed with TIBCO Business Studio. 2. Ensure that your application is using the appropriate launch fragment. When the custom application was created, two launch fragments where provided, one for use with GI forms and one for use with GWT forms. As your application has been using GI forms, rename the current WCCProjectName.html file to WCCProjectName_giforms.html, then rename the other one (that is likely named something like WCCProjectName_gwtforms.html) to WCCProjectName.html.
The WCCProjectName.html file is located here: StudioHome\wcc\version\ where: — StudioHome is the directory in which TIBCO Business Studio was installed. — version is the version number of Workspace that was installed with TIBCO Business Studio.
TIBCO ActiveMatrix BPM Release Notes Migration and Compatibility | 27
3. Modify your custom WCC application’s configuration file (config.xml) to use GWT forms instead of GI forms, as follows: a. Open your custom WCC application’s configuration file, which is located as follows: StudioHome\wcc\version\JSXAPPS\WCCProjectName\config.xml where StudioHome is the directory in which TIBCO Business Studio was installed, version is the version number of Workspace that was installed with TIBCO Business Studio, and WCCProjectName is the name you gave your WCC application when you created it in TIBCO General Interface Builder. b. Locate the ChannelIdentifier record and ensure that the “GIGWTPull_DefaultChannel” record is uncommented and that the “GIGIPull_DefaultChannel” record is commented out. c. Locate the addins record and ensure that the “user:gwtforms” record is uncommented and that the “user:forms2” record (which is used with GI forms) is commented out.
d. Save and close the config.xml file.
New Callback Methods Added for Use With Custom Interfaces Two new callback methods have been added in version 2.2 that are used with Simple Managed Hub iFrame type of custom interfaces that publish custom events.
The onHubSubscribeComplete callback method is invoked when the client application subscribes to each custom event. This method can be used to verify the success of the Managed Hub subscription. When a custom event, to which the client has successfully subscribed is published by the custom interface, the new onHubEventData callback method is invoked. This method is used to handle a Managed Hub event that has been published by the custom interface. If your pre-version 2.2 Workspace application, or custom WCC application, makes use of a Simple Managed Hub iFrame type of custom interface that publishes custom events, you can add these new callback methods to the JSXAPPS\wccProjectName\application\js\AppMain.js file (where wccProjectName is the name of your custom WCC application; or "workspace" for the Workspace application). For more information about these methods, see the "Custom Interfaces" chapter in the TIBCO Workspace Configuration and Customization guide.
Version 1.3.x to 2.0.0 The following new configuration parameters have been added in Workspace version 2.0.0: • columnSort (Note that this parameter is initially set to its default value, which causes a "server" sort to be performed when a column is sorted by clicking the header.)
TIBCO ActiveMatrix BPM Release Notes 28 | Release Notes
• customCallout The following new user access elements have been added in Workspace version 2.0.0: • EventView > EventViewer > Find • ProcessView > ProcessInstance > Find • WorkView > SupervisedWorkItem > Find • WorkView > WorkItem > Find • WorkView > ShowInbox1 • ProcessView > ShowAllInstances1 • OrganizationBrowser > EditResources > RenameResource • WorkView > WorkItem > PrioritizeAllocated • WorkView > SupervisedWorkItem > PrioritizeAny • WorkView > WorkItem > PrioritizeAny • EventView > BaseFilter • ProcessView > BaseFilter • WorkView > BaseFilter • EventView > CreateSystemView • ProcessView > CreateSystemView • WorkView > CreateSystemView • EventView > AuthorSystemView • ProcessView > AuthorSystemView • WorkView > AuthorSystemView • ProcessView > ProcessInstance > DefineHaltedView • ProcessView > ProcessInstance > ResumeHalted • ProcessView > ProcessInstance > Retry • ProcessView > ProcessInstance > Ignore • ExportFilterXML
1. If you have users using a profile other than AccessDefaults, and you do not add the ShowInbox and ShowAllInstances elements to their profile after upgrade, those users will not have access to the Inbox and All Instances process view.
TIBCO ActiveMatrix BPM Release Notes Migration and Compatibility | 29
For descriptions of these parameters and elements, see the New Features section in the Release Notes.
Platform You must reboot the server before installing ActiveMatrix version 3.3.0 on an AIX platform if you have launched TIBCO Configuration Tool immediately before installation of release 3.3.0.
TIBCO Business Studio • Projects created using TIBCO Business Studio-ActiveMatrix version 3.x can be opened in TIBCO Business Studio-ActiveMatrix version 3.3.0. You can deploy applications (DAAs) developed in TIBCO Business Studio-ActiveMatrix versions 3.0.x and 3.1.x to nodes in the 3.2.0 environment.
Projects created using TIBCO Business Studio-ActiveMatrix version 2.x.x can be imported into TIBCO Business Studio-ActiveMatrix version 3.3.0 and migrated to 3.3.0 format. For information on how to migrate projects, see Composite Development.
Refer Installation and Configuration for information on upgrading from an earlier version. • ActiveMatrix projects created in versions prior to 3.2.0 that use Java, Spring or WebApp components encounter an Null Pointer Exception (NPE) dialog when imported into any ActiveMatrix version running on JRE 1.7 or later. This is caused by the incompatibility of JRE 1.7 with the JAR format of the DataBinding JARs generated by ActiveMatrix versions prior to 3.3.0. This may happen if you have upgraded to JRE 1.7 or installed an ActiveMatrix version that includes JRE 1.7, such as version 3.3.0.
To avoid this issue: 1. Open the Problems view.
2. Look for instances of the following error message: JAR file incompatible with JRE/JDK 1.7 due to containing entries with empty name. One such message is generated for each offending JAR file.
TIBCO ActiveMatrix BPM Release Notes 30 | Release Notes
3. Right-click on one of these messages and select a quick fix to apply. There are three quick fixes available (all three back up old JARs): Fix JAR for JRE/JDK 1.7 compatibility—This option fixes only the selected JAR (that is, the JAR you clicked to apply the quick fix). Fix all library JARs in project for JRE/JDK 1.7 compatibility—This option fixes all of the offending JARs in the same project as the selected JAR (that is, the JAR you clicked to apply the quick fix). Fix all library JARs in workspace for JRE/JDK 1.7 compatibility—This option fixes all of the offending JARs in the workspace.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 31
Closed Issues
The table in this section lists issues that were closed since release 2.1. To view the defects for a particular feature, click: • BPM Core Components • TIBCO Business Studio Forms • Clients • Platform
BPM Core Components
Work Manager Issues Closed in Version 2.2.0
Key Summary WRM-5729 BPM Environment creation / merge fails if environment already exists and is "secure".
WRM-5704 TIBCO ActiveMatrix BPM Troubleshooting Guide: Deployment and Undeployment Issues : Cleanup Utilities)needs to document parameter "install.version".
WRM-5691 TIBCO ActiveMatrix BPM - BPM Administration guide: Mention that when you (1-F546HT) reconfigure the JDBC resource templates you must restart the node.
WRM-5626 TIBCO ActiveMatrix BPM - BPM Developer’s Guide: - Error in SSL SAML issue (1-ETZ5JT) value. Documentation states that default issuer is "www.tibco.com", but the correct value is: "CN=bpmserver, C=US, ST=CA, L=Palo Alto, OU=BPM, O=TIBCO Inc"
WRM-5619 TIBCO ActiveMatrix BPM - BPM Developer’s Guide: STATE not supported as a sort (1-F3L8TZ) column.
WRM-5505 TIBCO ActiveMatrix BPM Troubleshooting Guide: removed “Geronimo Error (1-F1DTH1) Messages” section.
WRM-5463 TIBCO ActiveMatrix BPM - BPM Developer’s Guide: error in Work Items state (1-EYNXUU) transition diagram.
WRM-5455 Table name wrong in tuning chapter of TIBCO ActiveMatrix BPM - BPM (1-F0EUMI) Administration guide. The correct tables to configure indexes on should be brm_work_items and brm_work_item_resources.
TIBCO ActiveMatrix BPM Release Notes 32 | Release Notes
Key Summary WRM-5444 The WorkItemManagementService.setWortkItemPriority() API does not take into (1-EZOM07) account the OPENEDFROMOFFERED state.
WRM-5436 JMS shared resources cannot be configured for SSL enabled JMS servers. (1-E80L8A)
WRM-5398 Modify/add new purge api/procedures to delete audit entries not linked to process (1-EYIRO9) instances.
WRM-5396 Qualifier and Attribute values for Capabilities and Resource Attributes are not (1-EW021H) validated against their data-type when using the API directly.
WRM-5389 Reschedule process instances stuck in "starting" state after a node crash. (1-E89PLT)
WRM-5378 BRM checks wrong resource set when doing "reallocate to offerset". (1-EWHTW3)
WRM-5331 Invalid assignment of right hand side values for (eventual) comparison with left hand side ENUM variables where those values are entered by the end user may cause failures when those invalid comparisons are evaluated at runtime.
WRM-5316 TIBCO ActiveMatrix BPM Installation Guide: modified documentation to explain that (1-EX29N1) you must use a specific format (including port number) for the JDBC URL.
WRM-5303 On calling REST service, HTTP header attribute "Accept" is not taking (1-EH2KCV) application/json as default when calling the service with json returns
WRM-5224 BPM Cleanup Utility: add steps for identifying and clearing out Work Presentation (1-EU9SAP) (WP) orphaned rows.
WRM-5187 Schemas with Enumeration literal of empty string NamePredictionException. (1-ET7LIK)
WRM-5166 A work item that is reallocated to another resource while in a Pended state is not shown (1-EM780P in the result of a "getAllocatedWorkListItems" operation for the Position. 1-ER7I1T)
WRM-5129 JMS Event Publication does not format DateTime fields (such as attribute6 and (1-EQSFJJ) attribute7) correctly other than creationTime.
WRM-5128 The Custom Client SampleApp bundled in the user documentation is missing the build (1-ERQL4T file. 1-EZDIK1)
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 33
Key Summary WRM-5123 Completion time (end_time) is set when process instances are in started state. (1-EPTWNX)
WRM-5115 Changes needed to Spotfire visualization documentation. (1-ER0EKU)
WRM-4947 "Could not execute JDBC batch update" on CloseWorkItem. (1-EL1TD3 1-ESTECT)
WRM-4934 Should reject the deployment of more than 8 Org Models. The default installation is to (1-EFJRTX) disable the organisation access restriction.
WRM-4911 A work item that is reallocated to another resource while in a Pended state is not shown (1-EM780P in the result of a "getAllocatedWorkListItems" operation for the Position. 1-ER7I1T)
WRM-4904 Disable audit and publish of preciseCreationTime. (1-EKHDUH)
WRM-4899 Unable to create any LDAP Container if one LDAP Source is unavailable. (1-DGMW71 1-ELPVVJ )
WRM-4889 Build file missing in the Custom Client SampleApp. (1-ERQL4T)
WRM-4851 Purge scripts or API do not clear out custom audit entries. (1-EG7HIT)
WRM-4750 TIBCO ActiveMatrix BPM - BPM Administration guide - enhance description of (1-EE39LZ) calendar lookahead properties.
WRM-4734 Open Next throws an error when opening a Dynamic Sub-Process or Pageflow. (1-ECKVSB)
WRM-4724 The new BPM Spotfire Information Library and the current template visualizations are described in TIBCO ActiveMatrix® BPM Spotfire Visualizations.
WRM-4712 On a UNIX or Linux system, if the TIBCO_HOME or CONFIG_HOME paths contain spaces, upgrading TIBCO ActiveMatrix BPM to version 2.1 will fail.
TIBCO ActiveMatrix BPM Release Notes 34 | Release Notes
Key Summary WRM-4601 On a TIBCO ActiveMatrix BPM system working with an Oracle database, when you use the Event Viewer in TIBCO Workspace you could not sort on the Process Instance Details or Resource Entity GUID columns. When using the Event Collector Query APIs (via SOAP), you could not sort on the following attributes: • AUDIT option: entities, processDetails • WORKITEM_STATS option: orgEntGuids, orgEntNames, orgEntTypes, orgEntVers • USER_ACTIVITY option: orgEntGuids, orgEntNames, orgEntTypes, orgEntVers
WRM-4375 Attributes of BigDecimal type logged in a Common Base Event format have their type set to String.
Process Manager
Issues Closed in Version 2.2.0
Key Summary BX-2966 The Variables view does not show variables information when debugging a process. (1-EFKTCB)
BX-2964 Events following an Exclusive Event gateway do not appear properly in Event (1-F6USD9) Collector.
BX-2886 Process Management API : return a more informative error message for (1-EX6M6F) operationFailedFault reply.
BX-2881 BPEL converter doesn't handle the local data fields for the embedded sub-process (1-F081RP) (except for the multi-instance loop)
BX-2852 Got "...Unknown time format` error when trying to use DateTimeUtil. (1-CSYBJH)
BX-2832 "...xsd resource does not exist" error is seen in the logs while generating a DAA. (1-CXCFL3)
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 35
Key Summary BX-2825 Special characters in the description field causing emptyBpel file generated error. (1-DG7B3B)
BX-2820 Enforce mandatory parameters for reusable sub-process task. (1-EUYNJL)
BX-2806 Process does not terminate correctly in the presence of XOR Event Based Gateway (1-ET7LRD) (Pick) that gets skipped.
BX-2800 Database Activity: Users should be able to call stored procedures in a (1-EU3LUX) Package.Procedure format and not just a Schema.Procedure.
BX-2794 The process launcher cannot initialize Data Field inputs. (1-EFKTCB)
BX-2786 If you use the "Reply Immediately With Process Id" feature, the engine may return an (1-ES5QCI) invalid process Id if the transaction commit fails.
BX-2781 Return limits for listProcessInstances() should be documented. (1-ESY4DD)
BX-2766 When process start activities do not have a name, Xpdl2Bpel needs to generate a (1-E856ML) unique name.
BX-2764 Need to defend against Javascript keywords in WSDL. (1-EJGZ1H)
BX-2762 WSDL has a Xpath correlation property query that has an invalid prefix "ns1". (1-EQY09D)
BX-2759 Deployment optimization to handle the transaction timeouts caused by Hibernate. (1-EQRATF 1-EOFBJQ 1-EPND8D)
BX-2750 The Terminate event does not properly cancel immediate start sub-processes. (1-EPTWIX)
BX-2748 Process Manager listProcessInstanceAttributes response time needs improvement. (1-ENJ2AD)
BX-2739 When a schema instance xsi:schemaLocation refers to a xsd is used in a WSDL, that (1-CVGWS5) xsd is not copied in the .processOut folder when the DAA is generated.
TIBCO ActiveMatrix BPM Release Notes 36 | Release Notes
Key Summary BX-2727 Sometimes the debugger cannot get the process template from runtime, leading to an (1-EOOOUB) error.
BX-2720 Process control flow could not be successfully analyzed. (1-ENO785)
BX-2704 CorrelationSet in BPEL is missing the property namespace prefix when multiple (1-EJQKAK) processes share the same correlation property name.
BX-2685 Timer event with a constant period of microseconds fails. (1-EJW925)
BX-2680 A catch event (for example, timer or message) on the boundary of another task (Service (1-EIR6DN) task, Embedded Subprocess, etc) resulting in a concurrency condition which results in multiple paths being followed incorrectly.
BX-2666 Sort order for process management query is incorrect. (1-EB94C7)
BX-2653 For stored procedures, not able to pass the correct value of a parameter whose type is (1-EI38YT) INOUT.
BX-2645 Process migration hangs when trying to migrate a process that has nested sibling tasks. (1-EH1V3F)
BX-2633 For the pageflow engine, BDS/BOM complex objects need to be serialized for (1-EFRDO3 parameters mapped from the parent process to sub-process to avoid issues with 1-EHQ0QN) different versions of BOM classloaderers in different projects.
BX-2625 Unable to route back in progress error process flow could not be successfully analyzed. (1-EFT4UT)
BX-2584 When there are multiple correlation fields of the same complex part, PropertyAlias (1-EAR2PN) were added to the WSDL in inconsistent order, causing "change in interface" error.
BX-2566 Need to register the service agent with the service manager in case of a stop/start (1-E9XYRT) scenario
BX-2548 Enforce mandatory parameters. (1-DLB2EF 1-E2FTVP 1-E6UY2F 1-ED3L2N)
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 37
Key Summary BX-2540 Set exitOnStandardFault="no" for the BPEL processes generated from TIBCO (1-E2F9R9) Business Studio BPM.
BX-2539 BOM data field associated with error event in a sub-process causes deployment error. (1-E93EPB 1-E0EUIF 1-E8Y63B 1-E45JCR)
BX-2526 Email task requires tags around the contents in the body of the email. (1-DZ9BKN)
BX-2421 If process queries are used with the "OR" operator and custom attributes they can (1-EB94C7) return an incorrect or duplicate result set.
BX-2342 In the query using boolean operator, expecting space before closed paranthesis when (1-DES6IR) passing input for queryProcessInstances API.
BX-2211 A temporary variable in an assignment with the same name as the WSDL message and part name causes an error during deployment. (SR 1-D8CL61) (SR 1-DK8PF5)
BX-1877 Need to handle the passing of an array to a stored procedure. (1-CBN7MV 1-ER6YV9)
PVM-475 Request queue items not processed in FIFO fashion in certain conditions. (1-EDSBDR)
PVM-447 Pageflow throws "java.lang.IllegalStateException: Since ids are not pre-resolved, (1-EVY043) parent >indicator should point to one of my ancestors, but doesn't."
PVM-429 A suspended process that has any pending work items would continuously reschedule, (1-EMWCOH) increasing the size of the request queue table.
PVM-416 AQL pagination fails with ClassCastException "java.lang.String cannot be cast to (1-EB94C7) java.lang.Number" for certain queries.
PVM-412 Request Queue item cleanup is outpaced by queue buildup causing database space (1-EGWMCP) issues on Oracle.
PVM-395 Setting a BOM attribute with a non-alphabetic character in the second position in the (1-EFQG23) name causes a problem with BPM Javascript tasks
TIBCO ActiveMatrix BPM Release Notes 38 | Release Notes
Key Summary PVM-383 Order by query on PVM_INST_TASK causes high database usage. (1-DWZI1C)
TIBCO Business Studio Forms
Runtime Issues Closed in Version 2.5.0 This section lists issues that were closed for TIBCO Business Studio Forms in this release.
Defect # Summary/Workaround FORM-5924 On selecting an option, a multi-select option list used to scroll down in forms viewed on Internet Explorer.
FORM-5915 After a form is cancelled either through the built-in Cancel operation or through the "Cancel on error" functionality, actions that were previously queued up continue to be processed.
FORM-5815 The getOptionLabels() API did not return the labels actually displayed on the User Interface if the number of labels is less than the number of values.
FORM-5813 The logger API in the formsclient was not exposed and documented.
FORM-5802 context.record could not resolve the value correctly on invoking the form open event, and when the collection pane value was null.
FORM-5747 Forms runtime always passed the grid-edit render mode to the initialize() method of custom controls that support both normal and view-edit render modes.
FORM-5731 The Add and Delete buttons of a grid pane did not function correctly if the grid pane was marked as static with deferred rendering, and the parent of that grid pane was also marked with deferred rendering.
FORM-5715 Forms using custom controls in a grid pane and record pane sometimes displayed an error in the client-side Google Web Toolkit (GWT) log on the cancel, close and submit actions. This prevented the forms runtime from calling the destroy() method on other custom controls in the form.
FORM-5601 The bindings between data field and grid selection were not handled properly.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 39
Defect # Summary/Workaround FORM-5585 While loading and reloading complex forms, memory leaks were observed on Internet Explorer.
FORM-5410 In grid panes, it was not possible to validate the input using the Enter key while main- taining the focus on the cell.
FORM-4914 StackOverflowException was thrown while editing classes defined in BOMs within two proj- ects which had a cyclical dependency.
FORM-4850 The focus was not set on a control after a validation failure. Now the setFocus() API is available for controls, which sets the focus on the specified control.
FORM-4743 Validation messages did not support substitution, and they were not dynamic.
FORM-4035 In Internet Explorer 7, the content of a horizontal pane wrapped if the window was made too small to show the entire pane. This happened in Internet Explorer 8 as well when viewing forms in ActiveMatrix BPM Workspace, as the browser was forced into Internet Explorer 7 viewing mode in that case. This was not a problem with Internet Explorer 8 in TIBCO ActiveMatrix Openspace.
Clients
TIBCO Openspace
Issues Closed in Version 2.2.0
Key Summary OS-1405 The Calendar gadget does not automatically default back to English if a requested translation is missing.
OS-1498 If you create a base calendar and perform many actions without regularly saving your changes (for example, adding working hours and exclusions and switching between tabs), a Save operation failed - 500 The call failed on the server, see server log for details message displays when you click Save updates.
OS-1740 Ensure that Hub Manager is loaded before Openspace tries to use it.
OS-1639 Selecting a time zone "GMT+xx" from the dropdown list can be translated to (1-ESA135) "GMT-xx".
TIBCO ActiveMatrix BPM Release Notes 40 | Release Notes
Key Summary OS-1622 Disable drag and drop operations for Openspace gadgets that are in Maximized state. (1-ESA18F )
OS-1611 Shindig does not allow an Openspace Gadget spec to be hosted on HTTP when 1-EQ15CX Openspace is running on HTTPS.
OS-1610 Fix Apache Shindig 1.1 to allow Gadgets to be hosted on HTTP when Openspace is (1-EQ15CX) running on HTTPS.
OS-1553 The Openspace Calendar gadget fails to communicate with the server when it is (1-EN1YCR) invoked through a load balancer.
OS-1540 In the graphical audit trail, a multiple boundary event icon is displayed for a catch 1-EFJHW9 boundary event. It should be modified to a message boundary event.
TIBCO Workspace
Key Closed Issue WS-1355 When the application language is changed, the tooltip text does not change for all toolbar buttons on lists. After refreshing the list, the text changes to the new language for some, but not all of the tools.
WS-1352 When the Options dialog is opened, and options (other than language) are modified, a subsequent change to the application's language is not persisted after logging out and logging back in. This only occurs when options are modified first, and then the language is changed on the main application title bar. It does not occur if the language is changed before modifying options or if the language is changed from within the Options dialog.
WS-1329 LDAP attributes containing binary data are not displayed in the list of LDAP attributes on the Organization Browser LDAP Container Editor.
A new getBinaryLDAPAttributes parameter has been added to the config.xml file to resolve this issue. For information about this parameter, see the TIBCO Workspace Configuration and Customization guide.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 41
Key Closed Issue WS-1321 Fonts used in menu items, and in the hierarchical matrix for work views, business services, event views, and Organization Browser, cannot be controlled using the currently available configuration files.
A new workspaceStyles.css file has been added to control these items.
WS-1320 If the value of Attribute 5 for a work item is 0.0, it is shown as "0E-10" in the Event Viewer.
WS-1316 When using Microsoft Internet Explorer version 10, the Organization Browser is experiencing some broken mouse click events, as well as some inoperative context menu selections.
WS-1310 When the owner or an author of a system view edits the view, the header at the top of the edit dialog indicates the view owner with "System View - Owner: username". When a recipient edits the view, the header just says "System View". The header should also display the owner for the system view recipients.
WS-1309 In the process instance list sort dialog, if you move a sort attribute to the right pane (Sort Attributes), click OK, then reopen the sort dialog and click on the same attribute in the right pane, the sort attribute appears in both the left pane (Available Attributes) and right pane (Sort Attributes).
WS-1300 When items are selected in the work item, process instance, or event lists, switching between views or refreshing the list causes the items to become unselected.
WS-1297 If there is a very large number of resources, the Create Resource(s) dialog, as well as the Select All option on the Resource List, can be very slow to list the resources.
WS-1285 The Organization Browser takes an excessive amount of time to display a very large container list.
WS-1276 When user access settings prevent a user from changing a user option (on the Options dialog), the denied user option should fall back to the system default for that option. Currently, if a user had previously changed the option value to something other than the system default, if that user loses access to the option, it maintains the value persisted in the database, rather than changing to the system default.
WS-1274 Workspace incorrectly requires the BRM.workItemAllocation system action to perform the Allocate Work Item(s) to Self operation in the user's own work item list
WS-1272 In the Organization Browser, switching between "display names" and "unique names" for organizational entities (Tools > Show unique names for organizational entities) does not cause the column headers in the resource list to be updated with the display/unique names.
TIBCO ActiveMatrix BPM Release Notes 42 | Release Notes
Key Closed Issue WS-1271 The text boxes for entering the base search and query in the Organization Browser LDAP container editor are very narrow, making it difficult to view and edit longer complex queries. The text boxes have been re-arranged to allow longer entries.
WS-1270 If a user who has the DE.resourceAdmin system action removes himself from the group or position that granted him that system action, the Resource Editor remains open and the OK and Cancel buttons stop functioning, making it impossible to close the Resource Editor. After this fix, the Cancel button functions properly, allowing the user to exit. Note, however, that the Organization Browser and Resource Editor may exhibit unusable behavior under these circumstances until the user logs out and logs back in.
WS-1267 Data in the PageBus event payload is missing standard and custom attribute data associated with items in the process instances list.
WS-1266 If Workspace is unable to find a given organizational entity because, for example, a script references an invalid organization model version, the error message incorrectly states that the work item ID no longer exists. After this fix, the error message correctly states that a scripting error prevented the work item from opening.
WS-1264 If a work item is left open when the application is closed, the user should be able to re-open the work item without cancelling it first. Currently, it must be cancelled before it can be reopened. The user is now presented with a message asking if the work item should be re-opened.
WS-1262 When the Open Event Viewer menu selection on work item and process instance lists is disabled, subordinate items on that menu are still enabled.
WS-1257 The Organization Browser resource list does not show if a resource possesses a qualified capability with no value, or an unqualified capability. Check marks are now shown in the resource list for assigned capabilities that are qualified with no value, as well as capabilities that are unqualified.
WS-1240 The Event Viewer shows an entry for "Workspace login" even if only Openspace is accessed.
WS-1238 Applications that have been undeployed still appear in the Start Process Instance list.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 43
Key Closed Issue WS-1228 The Open Next Work Item and Auto-Repeat Open Next Item functions are enabled only when viewing the Inbox. They should be available from all personal ("My Work") views. Also, the Refine view filter and Sort list contents functions are currently disabled when the Auto-Repeat Open Next Item function is turned on; those functions should be available when the Auto-Repeat Open Next Item function is turned on.
WS-1221 Cannot sort on the entities attribute in Event Collector queries. The fix for this resulted in two new attributes being returned by the eventCollectorGetAttributes and eventCollectorGetAllAttributes methods: IsFilterable and IsSortable. These new attributes indicate if the Event Collector attribute is filterable and sortable, respectively. Also, the IsPrimary attribute should no longer be used to determine if the Event Collector attribute is filterable and sortable.
WS-1219 Upon log in, the application hangs with an "appendChild" exception if user has been assigned a Supervised Work System View, but does not have user access granted for Supervised Work Views.
WS-1217 On the Process Instance Data dialog (Process Instance Summary > View Details), a blank custom field may in some cases display BOM data from another field in the process instance. In the XML presentation of the information everything is correct, but in the tree presentation it shows the repeated data.
WS-1216 If the user is not authorized to cancel, resume, and suspend a process instance, the Tools menu is removed from the list (as well as the right-mouse context menu). If the user is authorized to view outstanding items or the event viewer, the Tools menu should not be removed and those items should remain available in the menu.
WS-1212 System action enforcement in the Organization Browser needs to be modified. The DE.createResourceAdmin system action is no longer needed to create memberships in groups and positions, or to edit capabilities. However, the DE.resourceAdmin system action is now required to create memberships in groups and positions, and to edit capabilities Also, the Organization Browser now lists the memberships of groups and positions for users with either the DE.resolveResource or DE.resourceAdmin system actions (previously, those lists were only available to users with DE.resourceAdmin).
WS-1210 The text for the Only change enabled state for existing push destination check box on the Organization Browser Edit Push Destination dialog is truncated when translated to some languages. Note that this check box is displayed only when multiple resources are being edited in the Resource Editor.
TIBCO ActiveMatrix BPM Release Notes 44 | Release Notes
Key Closed Issue WS-1207 Mapping resources whose LDAP OU contains the ’&’ character results in an XML parsing error from the Action Processor.
WS-1206 Workspace incorrectly requires the BRM.cancelWorkItem system action to cancel work items in the user's own work list.
WS-1192 The string "(Master)", which is appended to the name of a system view to identify it as the master system view, is not localized and always displays in English.
The string has been added to the locale.xml file.
WS-1166 The Handle work item data conflict dialog that is displayed if a user attempts to close or submit a work item that was altered by another application or activity while the user had the work item open, needs to be reworded.
WS-984 Workspace is failing to escape special characters ( \, *, ’, and ?) in the event filters that result from the user requesting related events from the work item list, process instance list, or lists in the Organization Browser.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 45
Platform
Installer
Key Summary
TOOL-1626 The clean-up target was not invoked while creating or replicating ActiveMatrix Administrator.
TOOL-1403 The Edit TIBCO ActiveMatrix Administrator Server Configuration screen of TIBCO Configuration Tool used the default JMX port number as 6051, instead of the actual configured port.
TOOL-1341 TIBCO configuration using the console mode now works correctly.
TOOL-1331 The test connection to the SSL enabled SQLServer2008 no longer fails when using a trust keystore file generated using the Create a Trust Store option in TIBCO Configuration Tool.
TOOL-920 There was no option in TIBCO Configuration Tool to specify Enterprise Message Service Connection Factory used for the Monitoring and Logging service.
TOOL-1337 When you run TIBCO Configuration Tool after installing the product in the same TIBCO_HOME of an earlier product installation, the Select products to deploy option no longer lists duplicate entries for the available product components (such as, Mediation IT). These entries do not include the version numbers.
AMRP-2775 Virtualization queues are created by Messaging Bus when components are deployed on node. These queue are shared between nodes when same component is distributed across them. During undeployment of the component, queues created are now removed.
Documentation
Key Summary BJMS-1492 The JMS Binding Reference section now includes the following note applicable for both Request and Reply messages: If Request or Reply message destination type is set to Queue or Topic and JMS Provider does not support dynamic queue or topic creation or the user of provider does not have create permissions, create a queue or topic before deploying the application.
TIBCO ActiveMatrix BPM Release Notes 46 | Release Notes
Key Summary BJMS-1491 In the documentation > JMS Binding Reference > table "Configuration for Reply JMS message, applicable for In-Out MEP" > Destination Type > the description of the property now reads: The Type of JMS destination, Queue, Topic or JNDI. For direct destinations use Queue or Topic. For JNDI resource template, use JMS Destination Resource template. By default, destination type is 'Same as Request Message'. Note: 'Same as Request Message' option indicates that Reply Message Destination Type is same as Request Message Destination Type. In CLI script, there is no such option. You must select Queue, Topic, or JNDI. Required MEP: • In-Out (Service, Reference)
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 47
Runtime
Key Summary AMRP-4713 The Thread-Pool and JMS AtLeastOnce policies no longer prevent error messages from being delivered into an error queue when they’re configured in a one-way MEP in a Mediation component service.
AMRP-4669 The -Nodeutil7:listEndpoints command listed nothing even when the application had a binding defined.
AMRP-4625 The describeHost command (used with the tibcohost executable) no longer returns the incorrect hotfix version, which only occurred in some cases.
AMRP-4605 Undeploying and deleting TIBCO ActiveMatrix BPM user applications no longer occasionally fails due to a low-level provisioning error.
AMRP-4527 JDBC resource instance connection pool now gives a warning message when usage exceeds 80% of capacity.
AMRP-4521 In ActiveMatrix 3.2.0 Hotfix 2, new nodes created had over 100 empty bundles under org.eclipse.osgi/bundles.
AMRP-4452 At times, the Business Process Management nodes could not be stopped, and the nodes had to be manually killed after 15 minutes.
AMRP-4406 Some projects that ran correctly on a node failed in the rapid application environment and threw a NullPointerException.
AMRP-4399 A StackOverFlowError exception was thrown while deploying a particular DAA of an SOA project. Now, the error is handled gracefully.
AMRP-4397 Stale or failed connections in connection pools no longer cause transactions to roll back.
AMRP-4390 Messages are now removed from the queue once consumed by the component.
AMRP-4385 In ActiveMatrix 3.2.0, the load balancer did not work when a composite was invoked using virtualization binding.
AMRP-4378 Node startups are no longer affected when initialization depends on some file system time stamps.
TIBCO ActiveMatrix BPM Release Notes 48 | Release Notes
Key Summary AMRP-4361 There is now an OSGi command available to regenerate the Policy database on demand. Please see the following steps for enabling the OSGi console, regenerating the Policy database, and disabling the OSGi console (after the hotfix has been installed and applied). Before starting, the TIBCO Host and all of its nodes must be running. 1. Open a command window and change to
CONFIG_HOME/tibco/data/tibcohost/InstanceName/host/bin 2. Enable the OSGi console on the BPM Node:
./tibcohost sncp -nodeName NodeName -properties osgi.console=portNumber
where:
NodeName is the name of your BPM Node. portNumber is any free TCP port; a typical portNumber value is 1112 3. Stop the BPM Node:
./tibcohost stopNodes -nodeName NodeName -wait -1 4. Remove the existing Policy database folder from file system. Find the PolicyAgentRuntimeDB folder under the CONFIG_HOME/tibcohost/nodes/NodeName/work/cf/ directory and delete it:
rm -rf CONFIG_HOME/tibcohost/nodes/NodeName/work/cf/UUID/work/PolicyAgentRuntimeDB 5. Start the BPM Node:
./tibcohost startNodes -nodeName NodeName -wait -1 6. Open an OSGi console on the BPM Node:
telnet localhost portNumber
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 49
Key Summary AMRP-4361 7. Run the OSGi command to rebuild the Policy database by entering the following at (continued) the osgi prompt:
rebuildPolicyDB 8. Disconnect from the OSGi console:
disconnect 9. Disable the OSGi console on the BPM Node: a. Set the property to disable the OSGi console on the next restart:
./tibcohost sncp -nodeName NodeName -properties osgi.console= b. Stop the BPM Node:
./tibcohost stopNodes -nodeName NodeName -wait -1 c. Restart the BPM Node:
./tibcohost startNodes -nodeName NodeName -wait -1 The OSGi console should be always be disabled after use to avoid creating a security "hole."
AMRP-4339 Known valid script tasks in TIBCO ActiveMatrix BPM user applications no longer occasionally fail after application upgrades.
AMRP-4336 In Rapid Application Development, you could not invoke a nested composite when a promoted service and the nested composite's promoted service used the same binding name. In this case, the SOAP UI request was unresponsive.
AMRP-4330 The SystemNode no longer hangs and gets stuck in Starting state during an upgrade. This occurred because the node was prematurely processing the RDA command before the RDA command file was written to disk. The node no longer prematurely reads the RDA command file to prevent this issue.
AMRP-4303 Upgrading applications with dependent components no longer fails when the dependent components are in a Preparing for Undeploy state.
AMRP-4283 The SOAP/JMS Binding Type now receives the timeout signal when the threading policy is configured on the component reference and the component and composite reference are deployed on different nodes.
TIBCO ActiveMatrix BPM Release Notes 50 | Release Notes
Key Summary AMRP-4266 InvalidTransactionException no longer occurs during the processing of the reply message when a component that requires a global transaction has a reference that is AMRP-4649 virtualized; the transaction is now properly suspended on the request thread and resumed on the reply thread.
AMRP-4265 In the 3.3.0 version of the release, the following entries were removed from the SystemNode.tra file: • java.property.javax.net.ssl.trustStore=E:/programs/bwse592/tibcohost/3.1/templates/admin.default.ssl.trust.store.ts • java.property.javax.net.ssl.trustStoreType=JCEKS • java.property.javax.net.ssl.trustStorePassword=#!llDFtm1IZoO9hFkLI83SMqigDHIE/V/ To make the UDDI server SSL-enabled, add these properties manually.
AMRP-4260 When parameterOrder is specified in the portType, client requests to the SOAP endpoint no longer fail. WSBT-539
AMRP-4246 The SOAP/JMS Binding on the reference-side now supports time-out. Users can configure the timeout through the "Threading Policy" on the component reference.
AMRP-4245 The SOAP/JMS Binding on the reference-side now supports time-out. Users can configure the timeout through the Threading Policy on the component reference. WSBT-536
AMRP-4142 A FileNotFoundException no longer occurs when ActiveMatrix service is invoked from BPM using virtualized binding.
AMRP-4095 Idle connections are now eliminated from the JDBC connection pool after a reasonable period, preventing the buildup of unused connections in the pool. The default value for the JDBC resource property POOL_IDLE_TIMEOUT is now set according to the correct unit (minutes). Previously, the default value was erroneously set to an incorrect unit (ms).
AMX-13875 Installing the hotfix on top of TIBCO BusinessWorks Service Engine installed with SOA Development profile (Design-time), no longer results in the warning: ANT Task: Installing TIBCO Business Studio using p2 provisioning has failed.
AMX-12817 You can now configure a service or reference binding transport for SOAP over JMS.
AMX-12491 Creating an application from TIBCO Business Studio or ActiveMatrix Administrator no longer fails when WSDL and XSD files have namespaces that contain the following character: #.
AMX-12254 Using console mode to install an ActiveMatrix 3.2.0 hotfix is now supported.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 51
Key Summary AMX-12132 Removing a node from an existing TIBCO ActiveMatrix BPM application distribution no longer loses the Organizational Model mappings and prevents the users from logging in.
AMX-12067 Upgrading the BPM product and/or BPM user applications with interdependencies no longer causes BPM user applications to get stuck in the Waiting for Dependencies state.
This can manifest itself as work items that cannot be opened with a Cannot find classloader map error or processes that cannot be started or continued.
AMX-12025 Upgrade target upgrade-enterprise is now supported in combination with setting the artifact.download.port Ant property, regardless of how many nodes are involved. This property can be used to specify the port number used to communicate with the system being upgraded. You can set this property with -D on the ant command line when running the upgrade scripts.
AMX-12026 When installing this hotfix after installing ActiveMatrix 3.1.5-based products on an existing system but BEFORE running the upgrade scripts, you can now choose a particular network Interface to use when upgrading a remote node.
The new property artifact.download.host.name can be used to specify the IP address or hostname associated with the network interface used to communicate with the system being upgraded. You can set this property with -D on the ant command line when running the upgrade scripts.
AMX-12027 The ActiveMatrix Administrator server's backup task no longer backs up all old backup folders that might cause processing delays and growth in file size.
AMX-8723 Topic destinations are no longer supported for SOAP/JMS bindings. TIBCO Business Studio now raise a validation error if a user attempts to map JNDI destinations to WSBT-485 topics.
PER-1913 SOAP requests that have a signed SAML token with bearer confirmation method are now validated correctly. PER-1889
TIBCO ActiveMatrix BPM Release Notes 52 | Release Notes
Key Summary PER-1908 The Nonce and Created elements can now be optionally added when a Basic Credential Mapping or WSS Credential Mapping policy is used to insert a UsernameToken in the PER-1920 SOAP security header. The Nonce and Created elements must be explicitly disabled when a Basic Credential Mapping or WSS Credential Mapping policy is used to insert a UsernameToken in the SOAP security header. You can configure a Basic Credential Mapping or WS-Security Consumer Credential Mapping policy to have the UsernameToken without the Nonce and Created elements by copying the template below and modifying the parameters appropriately. See the Policy Sets, Policy Templates Reference section in the Composite Development guide for more information about configuring policy sets.
PER-1803 Policy components stored in agent databases are now automatically restored when the agent database is regenerated. Users can regenerate the agent database by searching for the GovernanceAgentRuntimeDB folder in the node’s work area, backing it up, and then deleting it. The agent database will be recreated the next time the node is started.
PER-1793 When a Basic Credential Mapping or WSS Credential Mapping policy is used to insert a UsernameToken in a SOAP security header, the Nonce and Created element now PER-1792 appears in the UsernameToken element.
PER-1786 The Authorization policy template now allows comma separated values in the role attribute.
PER-1699 Credential Mapping no longer fails with a NullPointerException in random instances.
PER-1698 While authenticating SAML tokens, ActiveMatrix 3.1.5 rejected an unsigned SAML1.1 token when the policy applied was Unsigned SAML 1.1 Authentication.
DSS-814 Propagation of Kerberos-authenticated security context in virtualized environments is now fixed.
DSS-802 Messages that have valid signatures for both Sender-Vouches and Holder-of-Key methods are now processed so that the correct method is used for the authenticated DSS-803 principal.
DSS-756 Any signed messages containing xsi:type can now be verified.
DSS-754 Service invocations will no longer fail due to policy failures with specially-formatted, signed SAML assertions.
DSS-750 When using a replicated ActiveMatrix Administrator, resource instances no longer fail to install if the primary Administrator is down.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 53
Key Summary DSS-744 Keystores accessible through https URLs can be accessed in IBM JREs as well.
DSS-713 Direct references to SAML tokens are supported and conform to Basic Security Profile 1.1.
DSS-704 A wrong valueType is no longer used to sign and verify SAML 2.0 tokens. The valueType now conforms to WSS SAML Token Profile 1.1.
DSS-663 Keystore Provider refresh did not work as expected. Changes to the keystore file on the disk did not get picked up.
DSS-662 If the audit service is invoked when running around 1000 process instances, a ConcurrentModificationException was thrown.
MCR-1999 While creating the Administrator, the SystemNode.log threw multiple trivial errors, that did not have an impact on the creation.
MCR-1998 Deploying a Business Process Management application on a node failed when a Business Process Management server was created that used an existing Administrator server.
MCR-1947 When an already deployed application is redeployed to an additional node, policy enforcement for policies distributed through TIBCO ActiveMatrix Policy Director now works for newly created bindings on the additional node.
MCR-1939 Redeployment of an application no longer results in policy enforcement failures for MCR-1945 policies distributed through TIBCO ActiveMatrix Policy Director.
TRUP-367 Publishing to a UDDI registry where bindings are distributed across multiple nodes no longer results in an exception. TRUP-364
TRUP-354 ActiveMatrix services are now published correctly in the registry of TIBCO ActiveMatrix Lifecycle Governance Registry Foundation.
WSBT-849 When you upgraded and deployed an application, the binding failed to start during deployment and threw a NullPointerException.
WSBT-828 The Endpoint URI field defined in the SOAP Binding with HTTP Transport now may contain a single token or no token at all, for example, /sample or /.
WSBT-638 SOAP 1.1. endpoints now correctly respond with a version mismatch error when receiving a SOAP 1.2 message.
TIBCO ActiveMatrix BPM Release Notes 54 | Release Notes
Key Summary WSBT-611 While adding or editing a binding in Administrator (Add > Binding, Edit > Binding), DUPS_OK_ACKNOWLEDGE and CLIENT_ACKNOWLEDGE were listed as possible Acknowledgement Mode options.
WSBT-598 For in-only MEP, when you add a binding on the reference side, only one JMS Destination resource (that is, the JMS Outbound Destination) should be created. However, two JMS Destination resources were being created (that is, JMS Outbound Destination and JMS Inbound Destination).
WSBT-584 With SOA Developer Studio (SDS) in TIBCO ActiveMatrix 3.0, you could select a non-supported WSDL, RPC/Encoded.
WSBT-547 When you add a new binding with a new URI to an existing binding in Administrator, Administrator did not validate the URI to check whether it ended with a / and a "404" error was displayed. All URIs must have a context root, which is the segment immediately following the port. For example, http://localhost:80/abc/. Here /abc is the context root and / is the path for the service internally. For other URIs which have a context root, you need not terminate with a /. For example, http://localhost:80/abc/xyz. Here, the context root is /abc and /xyz is the path used for the service internally.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 55
JMS
Key Summary BJMS-1500 POOL_IDLE_TIMEOUT and POOL_BLOCKING_TIMEOUT properties for the connection factory resource instance can now be added in SystemNode.tra file. BJMS-1509 POOL_IDLE_TIMEOUT is the time after which the idle connections are closed, in minutes. The default is 5 minutes. The property for POOL_IDLE_TIMEOUT is java.property.com.tibco.amf.sharedresource.jms.connection.pool.idletimeout. POOL_BLOCKING_TIMEOUT is the maximum amount of time a requestor will wait for a connection when the pool is at maximum, in milliseconds. The default is 60000 ms (i.e., 1 minute). The property for POOL_BLOCKING_TIMEOUT is java.property.com.tibco.amf.sharedresource.jms.connection.pool.blockingtimeout.
BJMS-1478 If the temporary reply destination on service side is invalid, the JMS binding reply delivery no longer goes into infinite loop.
BJMS-1474 If the temporary reply destination on the service side is invalid, the JMS binding reply delivery no longer goes into an infinite loop.
BJMS-1340 A particular XML over JMS project which worked in release 3.0.2 does not work in 3.1.x. As the payload does not match the schema, the project does not work in 3.1.x. No fix is done for this defect.
BJMS-848 In the mutablecontext.setParameter() Plain Old Java Object (POJO), when you add a context parameter name with a trailing space, the JMS binding reference does not read the value at runtime. The trailing space needs to be trimmed in the Java code.
BJMS-763 For a JMS Transacted OneWay policy, when Enterprise Message Service is restarted after a crash and the transaction commit fails, the reason in the error message is now provided.
BJMS-753 A WebSphere MQ 7 JMS driver installed via TIBCO Configuration Tool now works with WebSphere MQ 6.0 server. Topic on Inbound side deploys, and message exchange happens.
BJMS-734 The timeout setting in JMS Binding Reference is redundant. However, this setting will not be changed in order to maintain backward compatibility.
BJMS-645 If a node crashes while a transaction is running on node start up, the redelivery count is no longer set back to 'zero'.
TIBCO ActiveMatrix BPM Release Notes 56 | Release Notes
Key Summary BJMS-641 Deploying a new application containing a JMS reference binding after restarting Enterprise Message Service referred from JMS Connection Factory resource instance no longer fails with 'IllegalStateException: Connection is being closed' in the node log.
BJMS-640 and Applications are now undeployed successfully after EMS crashes. BJMS-764
BJMS-610 When migrating JNDI application properties and JMS resource templates that are configured for SSL to 3.x, the SSL configuration is now migrated.
BJMS-547 JMS Destination and Destination Configuration resource instances now check the connection to JMS server at the time of resource instance installation.
BJMS-546 JMS Connection Factory Configuration and JNDI Connection resource instances now check the connection to JMS server at the time of resource instance installation.
BJMS-417 After unwiring a JMS service from JMS reference, reference properties are now deleted.
BJMS-332 When a resource instance is created from a resource template with bad configuration, an error is reported on resource instance installation.
BJMS-238 JMS bindings now allow you to select header or property name for Bag and Message context parameter types in the Context Variable Mapping screen.
BJMS-203 When the JNDI name of the resource instances supporting a SOAP/JMS binding are not provisioned in the TIBCO Enterprise Message Service, the behavior is no longer different for SSL and non-SSL connections.
BJMS-1492 The following note, applicable for both Request and Reply messages, is now present in TIBCO ActiveMatrix Composite Development and TIBCO ActiveMatrix Administration, in the Advanced Settings for JMS Binding table: If Request or Reply message destination type is set to Queue or Topic or Topic and JMS Provider does not support dynamic queue or topic creation or the user of provider does not have create permissions, create a queue or topic before deploying the application.
BJMS-1485 While creating JNDI Resource Template in TIBCO ActiveMatrix Administrator UI, you can now configure JNDI Name of Identity Provider that supplies credentials as authentication credentials.
BJMS-1484 While editing a Service Binding with a single operation WSDL, if you click on the Advanced Tab, the Binding can now be saved.
TIBCO ActiveMatrix BPM Release Notes Closed Issues | 57
Key Summary BJMS-1482 In TIBCO ActiveMatrix Administrator, values for some of the fields on JMS Service and JMS Reference Binding are now displayed correctly. • Service Binding: Default non-over ridden value of Durable Subscription on Operation level is displayed as "inherited". • Reference Binding: Request Message fields (Message Type, Delivery Mode and Message Priority) when over-ridden are intermittently displayed as "inherited" while Message Expiration is displayed as -1.
BJMS-1479 For projects created in TIBCO ActiveMatrix(R) Service Grid 3.2.0, JMS Binding uses RequestDestination and ReplyDestination terminology. When the JNDI name for the RequestDestination/ReplyDestination does not exist, JMS Binding no longer logs old property names (Inbound Destination/Outbound Destination).
BJMS-1469 For projects created in TIBCO ActiveMatrix Service Grid 3.1.2, JMS Binding no longer logs ConnectionFactory properties names as RequestConnectionFactory and ReplyConnectionFactory instead of 3.1.2 terminology - ConnectionFactory and ConnectionFactoryConfiguration.
BJMS-1348 For a JMS Binding application configured with JMS At Least Once Policy, if node crashes and starts up, message redelivery count is no longer set back to zero.
BJMS-1257 JMS Binding can now be edited from Administrator UI.
BJMS-1175 For JNDI Connection Application Properties, the Save button is now enabled if the value of a property is edited.
TIBCO ActiveMatrix BPM Release Notes 58 | Release Notes
Known Issues
The tables in this section list the known issues in this release. To view defects for a particular feature, click: • BPM Core Components • TIBCO Business Studio Forms • Clients • Platform
BPM Core Components
Work Manager
Key Summary/Workaround WRM-5741 Summary When attempting to use the 32 Bit Windows version of AMX-BPM on a 64 Bit Windows operating system you cannot use either the default "Production" or "Development" JVM settings. Workaround You should instead select the "Development" JVM profile and change the "Max Heap" value from 1536 to 1200. Not doing so will result in the BPMNode failing to start. TIBCO strongly recommends that you do not use the 32 Bit version as it severely limits the amount of memory available.
WRM-5720 Summary The PDF version of the TIBCO ActiveMatrix BPM Installation and Configuration differs from the HTML documentation with respect to the recommendations about enabling logging and monitoring. The PDF version contains the correct recommendation. Workaround TIBCO does not recommend deploying the ActiveMatrix Monitoring or Logging service on BPM production systems without first verifying the performance on a test system configured for the desired system usage and load.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 59
Key Summary/Workaround WRM-5686 Summary BPM Cleanup utility fails to generate scripts on AIX. Workaround 1. Download XmlTask source from http://www.oopsconsultancy.com/software/xmltask/. 2. Extract downloaded tar file and edit the com/oopsconsultancy/xmltask/jdk15/XPathAnalyser15.java file, replacing: import com.sun.org.apache.xpath.internal.objects.*; import com.sun.org.apache.xpath.internal.*; with import org.apache.xpath.objects.*; import org.apache.xpath.*; 3. Download the junit.jar (required by the build), place it into the XmlTask source folder and then update the CLASSPATH to refer to it: export CLASSPATH=./junit.jar
4. Run ‘ant’ to compile the source, and ‘ant package’ to create the xmltask.jar file.
5. Copy the generated xmltask.jar file into the /opt/apache-ant-1.7.1/lib folder.
TIBCO ActiveMatrix BPM Release Notes 60 | Release Notes
Key Summary/Workaround
WRM-5583 Summary In the BPM public API, the brmdto.xsd file contains the following documentation errors. 1. HiddenPeriod:
The description of the HiddenPeriod complexType contains the following errors: • If a HiddenPeriod expires or is cancelled, the work item transitions back to the state that was in before it was hidden (not to the ended state, as documented in the brmdto.xsd file). • In the examples, with a HiddenPeriod of 0 or -5, the work item transitions back to the Allocated state (not to the Pended state, as documented in the brmdto.xsd file). 2. apiVersion:
The description of the apiVersion attribute in brmdto.xsd is: "Specify the version of the return data. If omitted or set to 1 this API will return work views without specifying either the getAllocated boolean or the viewType for compatibilty with existing views. If > 1 additional Work View data will be returned." This is incorrect. The correct description is: "Version of the work list view definition to be returned. Either: — 2, to return a work list view that includes the getAllocatedItems attribute and resourcesRequired parameter, or — 1, to return a work list view that omits the getAllocatedItems attribute and resourcesRequired parameter. (You should use this value to maintain compatibility with work list views created in pre-2.2 versions of BPM.) This is the default behaviour if apiVersion is not specified." Workaround Use the correct descriptions given above. (These elements are also documented correctly in the main body of the TIBCO ActiveMatrix BPM Developer’s Guide.)
WRM-5574 Summary During installation, when you create details for the database name and user to be created and click Generate scripts, when you proceed to create a BPM node it will not work if you used a database name containing special characters (for example "-"). Workaround The generated script to create a database should use quotes for the database name if it contains special characters like "-".
TIBCO ActiveMatrix BPM Release Notes Known Issues | 61
Key Summary/Workaround WRM-5480 Summary On an HP-UX (64-bit)/Itanium platform, TIBCO Configuration Tool fails to launch in GUI mode if certain external libraries are not installed. Workaround Make sure that the following libraries are installed on the machine on which you are trying to run TIBCO Configuration Tool:
gtk+2-2.24.10-ia64-11.23.depot gcc-ia64-4.7.0.depot libgcc-4.2.3-ia64-11.23.depot glib2-2.32.3-ia64-11.23.depot cairo-1.12.2-ia64-11.23.depot atk-2.4.0-ia64-11.23.depot pixman-0.26.0-ia64-11.23.depot gdk_pixbuf-2.26.1-ia64-11.23.depot libpng-1.5.12-ia64-11.23.depot libXft-2.2.0-ia64-11.23.depot libXrender-0.9.7-ia64-11.23.depot bzip2-1.0.6-ia64-11.23.depot fontconfig-2.9.0-ia64-11.23.depot freetype-2.4.10-ia64-11.23.depot zlib-1.2.7-ia64-11.23.depot expat-2.1.0-ia64-11.23.depot libffi-3.0.11-ia64-11.23.depot intltool-0.50.2-ia64-11.23.depot gettext-0.18.1.1-ia64-11.23.depot libiconv-1.14-ia64-11.23.depot
WRM-4745 Summary Error opening TIBCO ActiveMatrix BPM Installation Guide on Solaris X86 32-bit/64-bit using Gnome PDF Viewer. Workaround Use an alternative PDF viewer.
WRM-5275 Summary You get the following Oracle error trying ORA-12899: value too large for column "TAMXACBP"."BRM_WORK_ITEMS"."ENTITY_QUER. Workaround Increase entity_query column on brm_work_items table and brm_work_model_entity on Oracle, Postgres and DB2 to be larger.
WRM-4732 Summary In TIBCO ActiveMatrix® BPM Spotfire Visualizations, in the section entitled "Using TIBCO Spotfire Automated Services to Change Your BPM Database Schema Name", step 6 states "From the Type drop-down list, select Schema." This is incorrect, it should say, "From the Type drop-down list, select Catalog." If you select Schema, when you try to open the template visualizations in the BPM Spotfire Information Library, an error displays because the information library cannot find the tables in the BPM database. Workaround From the Type drop-down list, select Catalog.
TIBCO ActiveMatrix BPM Release Notes 62 | Release Notes
Key Summary/Workaround WRM-4716 Summary When working with the CMIS Form Sample within TIBCO Business Studio, if you preview the Parent form first, the BPM user credentials are not passed into the form, and as a result the form throws the error "There is no Security Context in the HTTP Session". Workaround Preview the embedded form first, and then the Parent form.
WRM-4186 Summary If an enumeration in a BOM is a restriction of another enumeration, it is drawn in TIBCO Business Studio as if one is a generalization of the other. However in fact they are two separate enumerations, with no inheritance from each other in the underlying code. Therefore an interface that expects the base type cannot be passed the restricted type, and there will be a failure at run time. Workaround If this XSD construct is used in a web service that ActiveMatrix BPM needs to interact with, use a Mediation between BPM and the external web service.
WRM-3002 Summary Using the Google Chrome browser, you cannot open the TIBCO ActiveMatrix BPM HTML documentation that is installed on the file system when TIBCO ActiveMatrix BPM is installed. (This is because of the way that Chrome handles file URLs.) Workaround Do one of the following: • Use a different browser. • Use the TIBCO ActiveMatrix BPM PDF documentation that is installed on the file system when TIBCO ActiveMatrix BPM is installed. • Use the TIBCO ActiveMatrix BPM documentation available on the TIBCO Product Documentation web site.
WRM-2604 Summary Service Connector uses third party Axis2 and Rampart libraries. This may increase the Java classpath length. Workaround To avoid classpath length issues, use the new feature provided in Java 1.6 to include all binaries by using the wild card character(*). 1. Unzip the service connector to a folder, for example service-connector (in this example the folder is in c:) 2. Set the classpath to the service-connector folder using the wild card character: for example, SET CLASSPATH=%CLASSPATH%;c:\service-connector\*
WRM-2388 Summary The stored procedures used to delete audit entries and statistical data for COMPLETED, CANCELLED, and FAILED process instances do not remove work group events (BRM_WORKGROUP* messages) from the database tables. Workaround None.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 63
Key Summary/Workaround WRM-1671 Summary In TIBCO Workspace Event Views, the Push related columns for the PUSH events do not display any information. Workaround None.
WRM-1539 Summary If a measure is requested for a particular process, the returned data is a cumulative roll-up of the data for the process. However the statistics collector does not return any roll-up data for hours in which there is no activity on the process. Workaround If data for any hour is missing, assume it to be the same as the previous hour.
WRM-1429 Summary Business Services: Privilege references are not supported. Workaround None.
WRM-521 Summary If a pageflow has no user tasks then this will cause an exception when called from a client application, for example from either Openspace or Workspace. Workaround Add page activities to pageflow process.
WRM-440 Summary Uninstall of TIBCO ActiveMatrix BPM fails to stop BPMNode, AdministratorNode and TibcoHost before removing files. Workaround Stop them yourself or reboot the system.
WRM-79 Summary Work items can be assigned to an organizational entity (such as a position) using an RQL statement. However, the work items assigned this way do not appear in the Supervised Work List for the organizational entity (because the work items are offered to individual resources, not to the group being listed in the Supervised Work List). Workaround None - this is the intended behavior.
WRM-69 Summary The Email presentation channel does not support SMTP authentication. Workaround None.
TIBCO ActiveMatrix BPM Release Notes 64 | Release Notes
Process Manager
Key Summary/Workaround BX-2978 Summary Debugger: If a project has been deployed and breakpoints are set on the pageflow/business service, and then the application is upgraded through TIBCO Business Studio, the breakpoints previously set are removed. Workaround Terminate the debugger and restart it after the process is re-deployed so that the breakpoints are in sync again.
BX-2967 Summary When you have two versions of an application - V1 and V2 with V2 having event handlers and added mandatory parameters, process instances that migrate from V1 to V2 might go into 'Halted' state with an error - 'No value set for mandatory IN/INOUT parameter'. Workaround • The parameters added in V2 should be non-mandatory • The parameters added in V2 can be mandatory but at the interface of the tasks where the process instance migrates, the parameters should be made INOUT - non-mandatory.
BX-2956 Summary Mapping between incompatible types like BPM attribute to POJO list could result in ExpressionEvaluationError. Workaround Add a script task before the java service task to build the source data as an array of Java objects out of the BDS list, before mapping it to the POJO method parameter.
BX-2507 Summary Data in the database and server's response can not display correct characters outside the character set supported by the default system encoding. This could cause the extended message to be displayed incorrectly. Workaround None.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 65
TIBCO Business Studio Forms
Known Issues at Runtime in Version 2.5.0 The table in this section lists known issues related to TIBCO Business Studio Forms observed at runtime.
Defect # Summary/Workaround FORM-6110 Summary: When editing a list control in Openspace or Workspace, if you scroll the window using the scroll-wheel, the edit box in the list control remains on the page, and does not scroll with the window. Workaround: Pressing the Escape or Enter key closes the edit box.
FORM-6079 Summary: When a Date-Time control is bound to a value of type Date Time (not Date Time and Time Zone), and it is the first editable control in the form, its value gets converted to the users’ local timezone even if they do not edit the value.
Workaround: If timezone information is important, then model the value using Date Time and Time Zone instead of Date Time.
FORM-6050 Summary: On Red Hat Enterprise Linux V6, an exception is thrown in the GWT preview pane when invoking the Reload button in the preview. Workaround: Refresh the GWT preview pane by selecting the Design tab, and select the GWT Preview tab again to reload the form.
FORM-5717 Summary: At runtime, presumably only one version of a Component Library can be loaded within the same browser session. Workaround: If later versions of a process need to use an updated version of a library, then that library should be renamed to avoid a conflict with the earlier version of the library.
TIBCO ActiveMatrix BPM Release Notes 66 | Release Notes
Defect # Summary/Workaround FORM-4911 Summary: In Safari 5, when the browser window is resized, some of the CSS prop- erties applied at the form level (such as background-color) will not work properly, causing the form to render incorrectly. Workaround: Add the following style for the TIBCO ActiveMatrix Workspace application within the BPM runtime instance: #JSX .jsx-tibco-forms { width: 100% !important; height:inherit !important; overflow:visible; }
This is added to the CSS file located within the Program Data directory of the BPM runtime instance. The location is as follows:
FORM-4910 Summary: You cannot specify a relative path for linked HTML files in a Hyperlink control. If a relative path is specified in a Hyperlink control, that URL will be resolved relative to the application in which the form is loaded (e.g. openspace.html, work- space.html) rather than being relative to the location of the form itself, as happens when resolving image URLs for the Image control. Workaround: The URL will need to be specified as an absolute URL.
FORM-4809 Summary: Tabbing within list controls does not work properly in Firefox 3.5. This is not a problem in Firefox 3.6 and later. Workaround:None.
FORM-4441 Summary: In Workspace, using Google Web Toolkit (GWT) forms, the Application Monitor log may show an error "Uncaught Exception: Unspecified Error." when starting a Busi- ness Service by double-clicking on it. Workaround: None. The error message can be ignored. There is no other side-effect.
FORM-4164 Summary: A mobile form that contains a Duration list control is not properly destroyed when the form is submitted. Workaround: None. The only workaround is to avoid using Duration list controls for forms targeting the mobile presentation channel type.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 67
Defect # Summary/Workaround FORM-4145 Summary: In mobile forms, the deletion of values from multi-valued list controls is not working. Workaround: None.
FORM-3544 Summary: Sometimes the loading of a mobile form will be slow or can appear to freeze. This will only happen during the initial load of the particular form and will load quickly with subsequent loads of instances of the same form. Workaround: None.
FORM-2592 Summary: The setOptions() method on RadioGroups and OptionLists in Google Web Toolkit (GWT) fails if an array of numbers is passed in as the value array. Workaround: Use an array of strings to set the values for an OptionList or Radio- Group control.
FORM-2376 Summary: Specific to TIBCO Google Web Toolkit (GWT) forms. For image con- trols, the settings of width and height do not have any effect on the rendered image. Workaround: The size of images can be set using CSS. Follow these steps: 1. Create a CSS file in the Presentation Resources folder that contains a CSS rule for setting the size of an image control, for example:
.TibcoForms .imageSize img {width: 100px; height: 100px;} 2. Add the CSS file as a reference in the Form Resource property sheet. 3. Add imageSize as the Style Class Name for the image control. (You can use whatever CSS class name you want as long as it matches what is used in the CSS file.)
TIBCO ActiveMatrix BPM Release Notes 68 | Release Notes
Clients
TIBCO Openspace
Change Request ID Summary/Workaround OS-1820 Summary An error is returned if you filter work items on strings that contain a literal single quote character. Workaround None.
OS-1795 Summary Openspace draws multi-instance loops as one icon showing that there are multiple iterations. Sometimes, due to event types not matching, Openspace will draw the loops as separate instances. The result shows the correct audit but the loop iterations are not consolidated. Workaround None.
OS-1790 Summary When using Internet Explorer, make sure Internet Explorer is set to use Standards Mode. There are two reasons for this: • If you click Compatibility Mode rather than Refresh, then Openpace requires the use of Google Chrome frame. This is not advisable because Google Chrome frame has been deprecated by Google. • It affects how Openspace displays. To check this, from the Menu bar, select Tools > Compatibility View Settings. Make sure that Openspace is not listed in the Websites you’ve added to Compatibility View box. You may also want to deselect the checkboxes below, depending on your requirements. Workaround When using Internet Explorer, ensure Standards Mode is set.
OS-1402 Summary Because of an issue with TIBCO ActiveMatrix BPM, if you are using Internet Explorer 9 and opening a form with a large amount of data, you may experience a delay opening the form. Workaround Adding the parameter &noRefresh=true in your Openspace url will reduce, though not remove, the delay.
OS-1393 Summary When using the Chrome browser with a zoom setting of 100% and the Hub Policy Administrator is open, the buttons at the bottom of the dialog may not be visible and the scroll bars cannot be selected to move the screen position. Workaround Reduce the browser zoom to allow the entire dialog to be visible.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 69
Change Summary/Workaround Request ID OS-1265 Summary You cannot create an exclusion in the Calendar gadget that spans 2 days. Workaround If your exclusion spans more than one day, you should specify the date the exclusion starts and finishes and set the exclusion as recurring. See TIBCO Openspace User Guide for more information.
OS-1259 Summary When you go to the Layouts area of the Preferences Area, the layout box displayed should show your currently selected layout. However, sometimes, when you move between tabs with the Preferences Area open, the layout boxes are incorrect. For example, the layout box displays a 1 column layout when it should display a 2 column layout. Workaround When moving between tabs, close the Preferences Area for the tab you are on, move to a new tab and then reopen the Preferences Area.
OS-1081 Summary When accessing the help in TIBCO Openspace using Internet Explorer 9 as your browser, the Maximize button does not work. Workaround Use Compatibility View to view the TIBCO Openspace help in an earlier version of Internet Explorer.
OS-1062 Summary On the Audit tab in the Process Template gadget, if you toggle between Audit Detail, Audit, and Graphic Audit, then this can cause the gadget to display incorrectly. Workaround Refresh the gadget.
OS-1040 Summary When a process template is selected in the Templates tab, a list of instances for the process displays in the bottom pane. By default, 8 process instances are displayed per page. If you then select a process instance and click the Audit tab, Openspace only allows the 8 process instances on the current page to be viewed. This means that clicking the Previous or Next buttons does not display more process instances, even though there may be more process instances in total. Workaround Increase the page size on the process instance pane. The maximum is 99 process instances on one page. This allows Openspace to display more process instances in the current page. See TIBCO Openspace User’s Guide for more information.
OS-1036 Summary Usernames and passwords in Openspace must not contain multibyte characters. Only single-byte characters are supported. Workaround None.
TIBCO ActiveMatrix BPM Release Notes 70 | Release Notes
Change Summary/Workaround Request ID OS-1024 Summary If you change your layout in Openspace so that it is using a layout that displays gadgets in different widths (for example, the layouts that divide the tab into 3 boxes), and then drag and drop a gadget to a new box, the gadget’s width does not resize to fit the box correctly. This applies whether the gadget should increase or decrease in size. Workaround If you resize your browser window, either by maximizing or minimizing or using the arrows, the gadget resizes correctly.
OS-607 Summary The audit trail on the Process Templates gadget lists only currently deployed versions of the templates. Audit information for older versions which have been undeployed is not listed. If multiple versions of process templates are deployed in the system, the audit information for all the deployed versions is shown. Workaround None.
OS-558 Summary The following restrictions apply when localizing Openspace: • The third-party OpenSocial gadgets cannot be translated. • Audit messages cannot be translated. • Sorting is not supported when Openspace is configured to use new languages. Only text sorting is supported. Workaround None.
OS-331 Summary Memory leak associated with the SecurityManager (caused by issues in the apache.shindig library) not being terminated leads to permgen exhaustion. Workaround None
OS-324 Summary Memory leaks in the BPMNode (caused by issues in the apache.shindig and google.guice libraries). Workaround None.
OS-140 Summary A user logged in with the same user name cannot have independent sessions of Workspace and Openspace when using multiple browsers or multiple tabs in a single browser. Workaround None.
OS-120 Summary When you attempt to delete a tab, you can only delete the last tab (the furthest one on the right). Workaround None.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 71
TIBCO Workspace
Change Request ID Summary/Workaround WS-1348 Summary An error is returned if you filter work items on strings that contain a literal single quote character. Workaround None
WS-842 Summary Login fails if the username contains multibyte characters (for example, Chinese or Japanese characters). Workaround None
WS-672 Summary Pageflow definitions can include branching that would require the simultaneous handling of multiple user tasks, each requiring the display of a form (this same scenario could also occur in embedded sub-processes set up for chained execution). Workspace cannot currently display multiple forms resulting from these parallel pageflows. If one is encountered in a WCC application (including the default Workspace application), the following warning message is displayed: "The business service or work item has encountered a parallel pageflow which cannot be displayed in Workspace". Workaround Rework the process/pageflow to eliminate the parallel display of multiple forms, or create a custom BPM application using the available APIs that can handle pageflow branching (for information, see the TIBCO ActiveMatrix BPM Developer’s Guide).
TIBCO ActiveMatrix BPM Release Notes 72 | Release Notes
Platform
Installer
Key Summary/Workaround INST-164 Summary The TIBCO Universal Installer does not display the products to be installed correctly. Workaround Note the discrepancies. There is no action required.
MCR-1943 Summary If you have upgraded to ActiveMatrix release 3.3.0 from a prior version and attempt to replicate the upgraded configuration, deploying the replicated configuration may fail. Workaround Replicate your configuration before upgrading to ActiveMatrix release 3.3.0.
SDS-5917 Summary The installer downloads Hibernate and Eclipse LPGL assemblies required by TIBCO Business Studio and TIBCO Configuration Tool. In a suite installation scenario, if you unzip all product archives into the same directory, you might overwrite the 3.1.5 installer with a 3.1.2 installer. The 3.1.2 installer won't download the required assemblies, which will lead to failure of TIBCO Business Studio and TIBCO Configuration Tool. Workaround When you unzip all products in the same directory while preparing for a suite install, make sure you preserve the installer binary from the most recent product installation. When you run the installation, the version of the 3.1.5 installer in the About dialog is 2.9.4.
Runtime
Key Summary/Workaround AMRP-4754 Summary If a service provider and a service consumer exist in the same BPM application, undeploying the application may undeploy the service provider even though the service consumer still requires the service provider. Workaround Separate the service consumer and the service provider so that they’re both in two separate user applications.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 73
Key Summary/Workaround AMRP-4744 Summary If you upgrade ActiveMatrix BPM to release 2.2.0 and ActiveMatrix to release 3.3.0, and upgrade a pre-existing user application so that it’s a web service implementation with REST enabled, you may see exceptions similar to the following in the logs during the reply message event although the response is successfully received: [INFO ] stdout - java.io.IOException: Exception in opening zip file: C:\ProgramData\amx-bpm-2.1.0v12\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM Server\data_3.2.x\nodes\BPMNode\work\cf\cdfa6b9e-d49d-4764-8623-fa331f8820c3\bundle 28 Aug 2013 16:52:32,824 [Framework Event Dispatcher] [INFO ] stdout - at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:291) 28 Aug 2013 16:52:32,824 [Framework Event Dispatcher] [INFO ] stdout - at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:87) Workaround Restart the node in which the application is deployed.
AMRP-4736 Summary You may not be able to start amxbpm as a Windows Service after upgrading to ActiveMatrix release 3.3.0 from release 3.1.5 (or previous releases) or ActiveMatrix BPM release 2.2.0 from release 2.1.0 (or previous releases). Workaround If you encounter this issue:
1. Launch a command prompt where tibcohost.exe is located.
2. Uninstall existing ActiveMatrix BPM windows service by executing tibcohost.exe --uninstall
3. Install the windows service again by executing tibcohost.exe --install
AMRP-4707 Summary If you use TIBCO Configuration Tool to configure an ActiveMatrix Administrator Server, entering the full IPv6 address of the local host in the Network Adapter field may result in exceptions similar to the following example: java.lang.IllegalArgumentException: No closing ']' for https://[2001:cafe::103/amxadministrator.httpbasic/ Workaround In the Network Adapter field, enter [::] instead of the machine’s full IPv6 address.
AMRP-4639 Summary The default JSSE provider for Oracle's Java 7 has introduced a bug with the Diffie Hellman Ephemeral (DHE) key exchange. (See the description in Oracle’s bug DSS-811 database for more information: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8013059) Establishing ciphers like TLS_DHE_RSA_WITH_AES_128_CBC_SHA sometimes fails and gives the error message Received fatal alert: bad_record_mac. By default, SSL connections with TIBCO EMS Server prefer the stream cipher RC4. You can overwrite this behavior by explicitly choosing the ciphers either in SSLClient RT or in the EMS Server. Workaround By default, no workaround is needed. If you do choose explicit ciphers, avoid the DHE ciphers so that you do not run into this occasional Java 7 bug. Unaffected ciphers include TLS_RSA_WITH_AES_128_CBC_SHA, amongst others.
TIBCO ActiveMatrix BPM Release Notes 74 | Release Notes
Key Summary/Workaround AMRP-4445 Summary If you create and install an HTTPConnector resource instance for a runtime node and assign it a port that is also used as an external or internal HTTP port of SystemNode, users will encounter a 404 error when attempting to log in to TIBCO ActiveMatrix Administrator after the TIBCO Host instance has been restarted. Workaround To avoid this issue: 1. Stop the TIBCO Host instance.
2. Go to CONFIG_FOLDER\tibcohost\tibco_host_instance_name\data_3.2.x\host\plugins 3. Delete, move (or backup with a different name) the plugin whose name takes the following form:
ri_HTTPConnector_Resource_InstanceName_NodeName_******.jar 4. Start the TIBCO Host instance.
Users should be able to log in to TIBCO ActiveMatrix Administrator. You may also need to modify the HTTPConnector resource template to use a port that is not being used by an existing instance such as SystemNode or a runtime node.
AMRP-4013 Summary Acceptor threads for HTTP connectors may consume excessive amounts of CPU. The processing performance of any node that uses an HTTP connector experiencing this issue may be affected when asynchronous IO is involved. Workaround Edit the HTTP Connector Resource Template to use blocking IO. See the chapter Resource Templates in Administration for more information.
AMRP-3828 Summary If you enter incorrect configuration data for a JDBC resource, it is not verified by any tools during resource creation or installation and the runtime reports a failure when an application tries to access the resource. Workaround Ensure that the configuration supplied to the JDBC resource template is correct.
AMRP-3788 Summary The LDAP resource template pool properties are not used when initializing the connection pool. Workaround Configuring the connection pool using system properties specified for the target node applies them to all instances deployed to that node. Refer to the Oracle documentation for more information: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html
TIBCO ActiveMatrix BPM Release Notes Known Issues | 75
Key Summary/Workaround AMRP-3721 Summary The LDAP shared resource does not reconnect automatically to its associated LDAP server. Workaround Reinstall the LDAP shared resource instance and then restart all dependent applications. Or, restart the node.
AMX-14346 Summary Suite installation of ActiveMatrix Service Grid 3.3.0 and ActiveMatrix BPM 2.2.0 fails with the following error: More than one active 'Finish' task has been defined. Workaround Do not install ActiveMatrix BPM and ActiveMatrix Service Grid at the same time using the Suite Installer.
AMX-14345 Summary Upgrading the second system node in a replicated Administrator setup can fail with exception(s) similar to the following example:
java.lang.IllegalStateException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'urn:amx:SystemEnvironment/amx.platform-app/GovernanceAgent/pepHttp/HttpFilterComponent_1.3.0': TIBCO-AMX-IT-JAVA-SPRING-801001: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: javax/xml/transform/TransformerFactoryConfigurationError Start component 'wtplogservice' on node 'SystemNodeReplica' failed : java.lang.IllegalArgumentException: Exception during web application initialization. Deployment of web application failed Workaround Upgrade the second system node again.
AMX-14344 Summary When upgrading an installation that has TIBCO Enterprise Message Service (EMS) configured to use SSL, upgrading the Administrator (done as part of the SystemNode upgrade) may fail due a fatal EMS connection error described in Known Issue DSS-811. This is caused because of a Java 7 bug, related to Ephemeral Diffie Hellman based ciphers, documented in Oracle's bug database. Workaround The failure is only seen during the upgrade process, and not during normal runtime operation, hence a workaround is required only in the former scenario. If upgrading process fails, apply this workaround and then re-run the upgrade script for the SystemNode. Update the EMS server configuration to exclude ciphers using Ephemeral Diffie Hellman. You can exclude ciphers by using: ssl_server_ciphers = !DHE-RSA-AES128-SHA:!DHE-DSA-AES128-SHA:!DHE-RSA-AES256-SHA:!DHE-DSA-AES256-SHA:ALL For more information, see the TIBCO Enterprise Message Service User's Guide, chapter "Using the SSL Protocol," section "Specifying Cipher Suites." The workaround can be removed after a successful upgrade.
TIBCO ActiveMatrix BPM Release Notes 76 | Release Notes
Key Summary/Workaround AMX-14310 Summary ActiveMatrix release 3.3.0 packages IBM JRE 1.7.0 SR2. If you are running ActiveMatrix on an AIX platform and install Unlimited Jurisdiction Policy (UJP) files, DSS-817 you may encounter errors. Workaround If you encounter errors, you must install the appropriate version of the UJP files for that build of the JRE. Errors similar to the following example indicate that the version of the UJP files is not the appropriate version for the installed JRE: Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers! at javax.crypto.b.a(Unknown Source) at javax.crypto.b.a(Unknown Source) at javax.crypto.b.access$600(Unknown Source) at javax.crypto.b$0.run(Unknown Source) at java.security.AccessController.doPrivileged(AccessController.java:254) ... 28 more If you see such errors, you must install the appropriate version of the UJP files.
AMX-13851 Summary If you use Microsoft SQL Server 2012 as an external database server and use its Mirror Mode to establish a connection to a secondary failover database server, TIBCO ActiveMatrix Administrator fails to connect to either database server. Workaround In addition to providing the JDBC URL of the mirrored servers in SQL Server 2012, you must set the IP and hostname of both the primary and secondary database servers in the hosts file. The location of the hosts file depends on the operating system:
• Windows: ROOT_DIR\system32\drivers\etc\hosts
• UNIX/Linux: /etc/hosts
For example, you have two database servers. The primary server's IP is 192.167.71.42 and its hostname is amx-db42; the secondary server's IP is 192.167.71.60 and its hostname is amx-db60. You would provide the following JDBC URL for these two mirrored primary and secondary servers: jdbc:sqlserver://192.167.71.42:1433;databaseName=db1;failoverPartner=192.167.71.60. To ensure that TIBCO ActiveMatrix Administrator successfully connects to both servers and allows for seamless switching between them using SQL statements, you must add the following entries to the hosts file: 192.167.71.42 amx-db42 192.167.71.60 amx-db60
TIBCO ActiveMatrix BPM Release Notes Known Issues | 77
Key Summary/Workaround AMX-11984 Summary You are not able to replicate the Administrator server after upgrading from an earlier 3.1.x version. TAP-12831 Workaround Follow these before attempting the replication procedure:
1. Import basic_cli.xml in sharedWorkFolder_build.xml. Modify the line
2. Edit sharedWorkFolder_data.xml
a. Remove the ApplicationFolder element.
b. Change the artifact server app name from com.tibco.amx.platform.artifactserver to amx.artifactserver.app. c. Change the name of the internal HTTP connector name in the substitution variable element from TIBCO ActiveMatrix Internal HTTP Connector Resource to tibco.admin.http.connector.internal.
AMX-11980 Summary (Windows only) When executing the upgrade-tibcohost script, you have to use the same case (either uppercase or lowercase) to define -Dtibco.config.mgmt.home that you had used earlier. The original path can be discovered by examining the value of property hpa.client.securityConfigFile in CONFIG_HOME/tibcohost/instanceName/host/th/hpaclientcli.properties. Workaround None.
AMX-11970 Summary In a replicated Administrator server setup if you deploy to the system node applications with policies applied on them, those policies are not enforced after upgrade. Workaround First undeploy and then redeploy these applications after upgrading all system nodes.
DSS-813 Summary While upgrading to ActiveMatrix release 3.3.0, you may see benign errors similar to the following example: [ERROR]com.tibco.trinity.runtime.base.provider.identity.CipherSupport Such errors are harmless and do not mean that the upgrade failed. No action is required. Workaround None.
TIBCO ActiveMatrix BPM Release Notes 78 | Release Notes
Key Summary/Workaround MCR-2002 Summary If you have configured Microsoft SQL Server 2012 as a database for Administrator, invoking a custom DAA may result in harmless exceptions similar to the following examples: Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of UNIQUE KEY constraint 'UQ__Mcr2Stat__1C012A471DC5DDE4'. Cannot insert duplicate key in object 'dbo.Mcr2StatisticsMetric'. The duplicate key value is (93, 21, 22, 3, -1). at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStateme nt.java:404) ... 44 more Workaround None.
MCR-1995 Summary If you have configured IBM DB2 as an external database, you may see harmless exceptions similar to the following examples in SystemNode.log: Retrying database transaction after error: Proceccing of metric requestsIn for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceRequestIn failed for measure Total and time window Since Started Time Window Retrying database transaction after error: Proceccing of metric faults for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceExecutionTime failed for measure Total and time window Since Started Time Window Such exceptions are benign and don’t require any action. Workaround None.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 79
JMS
Key Summary/Workaround BJMS-1490 Summary JNDI Resource Template using Custom Property for LDAP Provider URL will not get installed. Workaround Provide URL in the Provider URL field on the Resource Template.
BJMS-1382 Summary If JMS Binding configured with JMS AL Least Once Policy is undeployed before the redelivery count is exhausted, and deployed again, the message is not redelivered. Workaround None.
BJMS-1374 Summary If JMS Binding is configured with JMS At Least Once Policy and the EMS Provider URL used for connection is fault tolerant, the message is not redelivered in case EMS crashes. Workaround None.
BJMS-755 Summary Enterprise Message Service XA Resources from orphaned transactions do not disappear after transaction timeout from Enterprise Message Service server. They are seen on the Enterprise Message Service server as a part of show transactions command. Workaround Re-start the Enterprise Message Service server. As there is no locking in messaging associated with an XA resource, this issue is not serious.
BJMS-736 Summary When a 2.x project containing a JMS binding is migrated to 3.x the JNDI resource template required for looking up the destination are not created and the generated warning does not clearly state that JNDI resource templates need to be created. Workaround Manually create JNDI resource templates required for defining inbound and outbound destination configurations.
BJMS-726 Summary On re-starting Enterprise Message Service, for in-flight messages, transaction does not get committed. Re-delivery happens and message is forwarded to error queue. Workaround Recover the requests from the error queue.
BJMS-718 Summary For JMS Binding, the SDS UI allows you to set Context Parameters of type Message. This is not supported for JMS Binding. Workaround Do not use type Message for Context Provisioning related to JMS Binding.
TIBCO ActiveMatrix BPM Release Notes 80 | Release Notes
Key Summary/Workaround
BJMS-636 Summary The show connection command in the TIBCO Enterprise Message Service administration tool ems-admin doesn't contain "ClientID" value for connections created by JMS resource instances for outbound connections. Workaround None.
BJMS-603 Summary Administrator does not validate that an application with JMS Transacted One-Way policy set should be deployed on a single node. Workaround Ensure that the JMS binding that has a JMS Transacted One-Way Policy is deployed on the same node as that of component(s), it is wired to.
BJMS-355 Summary When a JMS service is deployed in LB setup over routed queues, the "'javax.jms.IllegalStateException: Not allowed to use transacted session on routed queues" message is displayed and the service does not start. Workaround Enterprise Message Service does not support transactions on routed queue consumers. Enterprise Message Service 6.0 added an explicit check to prevent this. You can restore the old behavior by setting the following main configuration parameter: allow_unsupported_tx_routed_q_consumers = true
BJMS-139 Summary If you rename an operation in a WSDL file, JMS bindings on composite services and references are not updated correctly. Workaround Create new JMS binding after renaming the WSDL operation or re-assign the WSDL file to existing JMS binding.
Java
Key Summary/Workaround SDS-5003 Summary If you regenerate a Java component, the data binding choice you selected when you generated the implementation is lost. Workaround Use generate instead of regenerate, and select the correct data binding.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 81
Key Summary/Workaround SDS-5002 Summary Deployment of an application may fail if the application name has the characters \, /, :, *, ?, ", <, >,|, whitespace, %, #, &, (, ), and comma. Workaround Rename the application to avoid use of those characters.
SDS-4948 Summary TIBCO Business Studio incorrectly allows you to configure a header part for fault messages and if you do so when you generate Java code it fails. Workaround Ensure that multi-part fault messages are not being used. Fault messages can only be single part, and are serialized as single part, part->element, document literal.
SDS-4733 Summary Migration of WS-Transfer, WS-Eventing and WS-Enumeration projects from ActiveMatrix Service Grid 2.x to ActiveMatrix Service Grid 3 is not supported and will result in errors in the MANIFEST of migrated Java projects. Workaround None.
TIBCO ActiveMatrix BPM Release Notes 82 | Release Notes
Key Summary/Workaround SDS-4564 Summary Java components migrate correctly, but further modification of migrated Java components is not fully supported. Workaround Here are some manual steps you can follow if you must do this (for example, if you need to add a service to a migrated Java component): 1. Do your modification in composite editor (for example, add a service and configure with its port type). 2. Save the composite. 3. Right-click the component (now showing out of sync error), select Quick Fixes->Update Implementation Class. Select yes on the dialog that comes up and wait for the background code generation to complete.
4. Open the Java implementation for the component, remove the implements clause that is making it implement the XMLBeans class and replace it by an extends of the Abstract class that got generated (usually called AbstractYourClass and located next to YourClass) For example,
public class AreaComponent implements AreaService { ---> public class AreaComponent extends AbstractAreaComponent { 5. Save the Java file to get the error marker of unimplemented methods, left-click on the error marker and select "Add Unimplented methods". 6. Save the file again. 7. Go back to the composite, right-click the Java component and select Quick Fixes->Update Implementation Class, and wait for it to complete. 8. Go to the custom feature file associated with the component and ensure the version of the plug-ins listed matches the versions of the corresponding java plugins (including the "qualifier" part). Whether you change it in the custom feature or on the Java plug-in does not matter, they just need to match. You should not have any remaining related errors on your Java component and can freely use your component as a 3.0 component and do any modifications on it as if it had been created in 3.0 in the first place.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 83
Key Summary/Workaround SDS-4322 Summary When you generate Java component implementations with the JAXB option, by default wrapper classes are not generated for user defined schema types. Workaround If the XSD schema has a user defined type, add the following JAXB annotation in each XSD schema.
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" jaxb:version="2.0"
SDS-3925 Summary DAA creation fails on Linux when TIBCO_HOME has a space and the DAA contains Java plug-ins. This affects RAD as well. Workaround Use a TIBCO_HOME without spaces.
AMRP-3205 Summary JAXB data binding cannot be used with a Java component wired to a BWSE component. This apply to wires from a Java component reference to a service on a BWSE component service and a BWSE component reference to a Java component service. Workaround Use XMLBeans data binding for scenarios involving Java components wired to BWSE components.
TIBCO ActiveMatrix BPM Release Notes 84 | Release Notes
Key Summary/Workaround SDS-3359 Summary WSDL files that declare simple parts as types are not supported. For example:
TIBCO HAWK ActiveMatrix Plug-in
Key Summary/Workaround HKAM-12 Summary TIBCO Hawk ActiveMatrix Plug-in 1.1.0 release does not support the -noEMS option on tibcohost configurations. Workaround None.
TIBCO ActiveMatrix BPM Release Notes Known Issues | 85
Key Summary/Workaround HKAM-129 Summary When the Monitoring Application feature is installed into a TIBCO_HOME without ActiveMatrix 3.1 platform present, then an error is thrown "ANT Task: Post installation - Update - Update install.properties has failed." with an incomplete installation. Workaround Install the Monitoring Application feature into a TIBCO_HOME that has ActiveMatrix 3.1 installed.
HKAM-139 Summary Samples rules don't start tibcohost on Windows Server 2008 R2 and throws ERROR : java.io.IOException: Timed out waiting for output from process powershell.exe.
Workaround Sign the script HAWK_CONFIG_HOME/staging/scripts/get-th-processcount.ps1, or change the Powershell settings on the machine: Set-ExecutionPolicy Unrestricted.
TIBCO ActiveMatrix BPM Release Notes 86 | Release Notes
TIBCO ActiveMatrix BPM Release Notes