TIBCO ActiveMatrix® BPM Release Notes · 2014-11-12 · (IWS) Single Sign-On using Kerberos. To...

TIBCO ActiveMatrix® BPM Release NotesSoftware Release 3.1.0November 2014

Two-Second Advantage®

Important Information

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

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

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

TIBCO, Two-Second Advantage, TIBCO Spotfire, TIBCO Enterprise Runtime for R, TIBCO SpotfireServer, TIBCO Spotfire Web Player, TIBCO Spotfire Statistics Services, S-PLUS, TIBCO EnterpriseMessage Service, TIBCO Hawk, and TIBCO Spotfire S+ are either registered trademarks or trademarksof TIBCO Software Inc. in the United States and/or other countries.

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

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

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

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2005-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix® BPM Release Notes

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Configuring the Business Data Services (BDS) Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Upgrade Script Issue with Openspace GlobalHubPolicy Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Upgrading the Oracle JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Openspace Upgrade Script and Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Workspace Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3


Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

TIBCO Hawk ActiveMatrix Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4


TIBCO Documentation and Support Services

All TIBCO documentation is available on the TIBCO Documentation site, which can be found here:

https://docs.tibco.com

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site. To directly access documentation for this product, double-click thefollowing file:

TIBCO_HOME/release_notes/TIB_amx-bpm_version_docinfo.html

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support asfollows:

● 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 canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to:

http://www.tibcommunity.com

5



http://www.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com

New Features

This release introduces new features for the following components:

● Core Components● TIBCO Forms● Clients

Core ComponentsThis section describes the new features for Core Components.

Work Manager

● Integration with TIBCO JasperReports® for ActiveMatrix® BPM

TIBCO JasperReports® for ActiveMatrix® BPM can be used with ActiveMatrix BPM to generatereports from BPM statistical and/or case data. Reports can be combined into dashboards, viewablein either Openspace or web browsers. ActiveMatrix BPM services can be invoked from dashboards,providing the ability to react to and modify the data presented in the dashboard.

The TIBCO JasperReports for ActiveMatrix BPM software included in the bill-of-materialsfor TIBCO ActiveMatrix BPM can only be used in conjunction with TIBCO ActiveMatrixBPM. This means that the licensed use cases are restricted.

Licensed use cases:

— Can be used to analyze usage and performance data that was generated by TIBCO ActiveMatrixBPM whether that data resides within a TIBCO ActiveMatrix BPM database or an externaldatabase.

— Can also be used to analyze business data that is associated with a customer application builtusing TIBCO ActiveMatrix BPM whether that data resides within a TIBCO ActiveMatrix BPMdatabase or an external database.

See Using TIBCO JasperReports® for ActiveMatrix® BPM.

● Developer Server Installation Profile

The ActiveMatrix BPM installer includes a Developer Server installation profile. This is a simpleprofile in which all components are installed on the same computer. It is intended for use in thesituation in which you want to perform rapid development and testing of a BPM application, whichhas been designed in TIBCO Business Studio™. For more information, see the TIBCO ActiveMatrixBPM Installation: Developer Server guide.

● Case States and Case Actions

Case States and Case Actions provide a powerful Case Management tool, allowing a user to choosethe most appropriate actions to perform on a case at a particular point, according to the businesscontext of the case. See TIBCO Business Studio Modeling User's Guide and the TIBCO ActiveMatrixBPM Case Data User's Guide.

6


● Case Folders

Case folders enable you to store documents, or document references, that are associated with a"case" in an external Content Management System (CMS). For more information, see the TIBCOActiveMatrix BPM Case Data User Guide. To support this feature, the following additions have beenmade:

— The TIBCO Configuration Tool includes a new "CMIS Configuration" wizard page to enableyou to configure ActiveMatrix BPM to use a CMS, either during or after ActiveMatrix BPMinstallation. For more information, see the TIBCO ActiveMatrix BPM Installation andConfiguration guide.

— A service task of type Document Operations can be added to a business process or pageflow toperform case folder-related functions.

— A Case Management gadget is provided in TIBCO Openspace to perform case folder-relatedfunctions.

— A new DocumentService API enables you to perform operations with case folders. For moreinformation, see the TIBCO ActiveMatrix BPM Developer's Guide.

— A new getCaseSummary API that allows you to get Summary Information (Case Identifier,Case State etc.) corresponding to a case reference.

● New APIs: cancelAdhocActivity, listAdhocActivities, runAdhocActivity

These Process Engine APIs support using automatic and manual ad-hoc activities. For moreinformation, see the TIBCO ActiveMatrix BPM Developer's Guide.

● New Options in "Edit TIBCO ActiveMatrix BPM Instance" Wizard

The Edit TIBCO ActiveMatrix BPM Instance wizard includes the following additional options:

— Change the settings that ActiveMatrix BPM uses to connect to the runtime database or theBusiness Data Services database, including changing the database location.

— Configure ActiveMatrix BPM Business Data Services to use a content management system forthe new case folder feature.

— Start or stop the ActiveMatrix BPM application.— Move an ActiveMatrix host from one computer to another.

● New APIs: replaceUser, getDeletedResources, purgeDeletedResources

These APIs support deleting users from LDAP and Directory Engine. For more information see theTIBCO ActiveMatrix BPM Developer's Guide.

● Support for Kerberos with Single Sign-on

TIBCO Openspace and TIBCO Workspace have been integrated with Windows Explorer-based(IWS) Single Sign-On using Kerberos. To configure ActiveMatrix BPM, Openspace, and Workspaceto use Kerberos, see the TIBCO ActiveMatrix BPM Single Sign-On guide.

● Support for Oracle 12c R1 and IBM DB2 10.5

For details, see the ActiveMatrix BPM readme.● Support for Microsoft Windows Server 2012 R2

7


Process Manager

● New API Operations for Ad-Hoc Activities

The following new operations have been added to the ProcessManagerService for working with ad-hoc activities:

● cancelAdhocActivity● listAdhocActivities● runAdhocActivity

● Enabled cursors return from QueryProcessInstances to work across multiple nodes.

TIBCO FormsThis section describes the new features in TIBCO Forms.

● BPM Live Development

Developing forms is an iterative and often collaborative effort involving repeated cycles of formmodification followed by form testing. Using the GWT Preview tab in the Form Designer, you canquickly switch between the design mode to make changes and the preview mode to test thosechanges. However, it is sometimes preferable to test a form in its full runtime context as part of adeployed BPM application and running process instance. Earlier, testing of forms involvedrebuilding and redeployment of a new DAA for each and every form change. After redeployment,you need to execute all the process steps leading to the user task for the form in question. Thesesteps can involve multiple work item interactions under multiple credentials.

With BPM Live Development, you can make iterative incremental changes to the form and instantlysee the results in the real-life deployed application context, using live process instance data.

For details, see TIBCO Business Studio Forms User's Guide > Concepts > Live Development of Forms.● Enhanced User Interface

The default styling of forms is now enhanced using the widely accepted Bootstrap styles. Inaddition to the current set of custom CSS classes, the forms are rendered with a specific set of pre-defined classes applied by the run time.

For details, see TIBCO Business Studio Forms User's Guide > Tasks > Enhanced User Interface.

8


ClientsThis section describes the new features in Openspace and Workspace.

Openspace

● New Case Management Gadget

The Data Views gadget has been renamed to the Case Management gadget and includes newfeatures. You can now perform the following from a case ID:

● Perform case actions. You can perform case actions that are specific to your business process oncase data. For example, a claim may have the following states: Reported, Review, Submitted andCompleted. Once a claim is Reported it may need to be reviewed by a Claims Adjuster. Onceyou have selected your case reference in the Case Management gadget, you can select Reviewfrom Case Actions and progress the claim to the next task in your business process.

● Manage work lists. You can view information about a work item such as its name, description,ID, priority and so on. You can also perform some actions on a work item. For example, you canopen a work item and submit it, or allocate a work item to another resource.

● Manage processes. You can display information about the process templates associated with thecase data. You can view information, such as process status, priority, duration and so on. Youcan also perform actions such as start, suspend, or cancel a process instance.

● Audit events. Events are actions that have taken place, for example, logging in, opening a workitem, submitting a work item, suspending a process instance, and so on. You can viewinformation about the events that have taken place for a selected case ID.

● Execute manual ad-hoc activities. A manual ad-hoc activity is a standalone task in a businessprocess. A process can have multiple manual ad-hoc activities. Depending on how the ad-hocactivities have been defined, they can be executed once or multiple times during the lifetime of aprocess instance. Manual ad-hoc activities either create a work-item or call a sub-process.

● Manage case folders. You can access any documents that are stored with the case data. If there isa long list of documents stored with your case data, you can search for the document yourequire. Then, depending on your requirements, you can either view, download, or delete thedocument. Documents are added to your case data when defining your case data model inTIBCO Business Studio.

See TIBCO Openspace User's Guide for more information.● New Enhanced Audit Trail in the Process Views Gadget

The audit trail in the Process Views gadget now displays event sub-processes. Event sub-processesare displayed below the main process, surrounded by a dotted line. There are two types of eventsub-process, interrupting and non-interrupting. In a non-interrupting event sub-process, the startevent is surrounded by a dashed line to distinguish it from an interrupting event sub-process.

See TIBCO Openspace User's Guide for more information.● Configuring a New Location for Openspace Help

You can now configure Openspace to use a different location for the Openspace Help. By default,selecting Help in TIBCO Openspace displays the Openspace Help files that are located on theTIBCO Documentation site. However, if your users do not have internet access, you can configureOpenspace to use a different location for the Openspace Help.

See TIBCO Openspace Customization Guide for more information.

9


● Ability to Manage Deleted Users

If a user is deleted from ActiveMatrix BPM, and the deleted user is the principal of an outstandingprocess instance, that process instance will eventually fail. You can now manage deleted users fromthe Organization Browser. A list of deleted users can be displayed, and if a deleted user hasoutstanding process instances, you can reassign those process instances to yourself.

See TIBCO Organization Browser User's Guide for more information.● Configuring the Openspace Date and Time Format

Date and time stamps are often used in Openspace. For example, the gadget status bar sometimesshows a timestamp. You can now configure a start date and end date for Openspace in the ProcessInstances Measures gadget.

● Openspace Business Service App (BizApp) Configuration

The Business Service App (BizApp) is available as part of Openspace. It enables you to launchbusiness services by providing the appropriate URL. It can render TIBCO Forms and also supportsthe complete functionality of static and dynamic sub-processes.


TIBCO Openspace has been integrated with Windows Explorer-based (IWS) Single Sign-On usingKerberos. This includes a new lockdown.showLogoutButton property in the config.propertiesfile that can be used to specify that the Logout button should not be displayed when using SingleSign-On, as it is not needed because the session is controlled externally to the application.

● Configuring What Happens on TIBCO Openspace Logout

When a user logs out of TIBCO Openspace, usually the current Openspace session is cleared and thecurrent URL is reloaded. However, you can specify a different URL to load, using the Openspaceproperty logout.path. If you are using CA SiteMinder, you can specify the URL of a custom logoutpage that clears the SiteMinder session.

● Support for Google Chrome 37, Internet Explorer 11, and Mozilla Firefox 32

Chrome 37 and Firefox 32 are now the minimum versions of these browsers that Openspacesupports. For details, see the TIBCO ActiveMatrix BPM Installation and Configuration guide.

Workspace

● New Configuration Parameter to Specify Action Taken Upon Logout

A new logoutPath parameter has been added to the Workspace config.xml file. This is used tospecify the action that Workspace takes on logout. You can specify that the application be reloadedwith the original URL, or a custom URL, so custom processing can be performed, including clearingthe session, if desired.


TIBCO Workspace has been integrated with Windows Explorer-based (IWS) Single Sign-On usingKerberos. This includes a new showLogoutButton parameter in the config.xml file that can beused to specify that the Logout button should not be displayed when using Single Sign-On, as it isnot needed because the session is controlled externally to the application.

● New HelpFileLocations Configuration Parameter to Specify the Location of the Workspace andOrganization Browser Help Files

Starting with this release, TIBCO Workspace documentation is not installed with the software. It isavailable from the TIBCO Documentation web site, https://docs.tibco.com.

A new configuration parameter, HelpFileLocations, has also been added to the config.xml filethat allows you to specify the location of the Workspace and Organization Browser help files. Thisparameter can be used to point to the help files if you have downloaded and stored the help fileslocally (because users do not have access to the Internet).

10



● New 'Revoked By' Column on the User Access Privileges Dialog

If the logged-in user does not have access to a function in the application, the Revoked By columnindicates whether access is denied by a system action or a user access control.

● Configuration Parameter for Action Processor Session Timeout Added

The sessionTimeout configuration parameter has been added to the WSProperties file to controlthe amount of time before the Action Processor session times out if the browser is closed withoutbeing reopened. This is useful if the authenticationMode parameter is set to "useSessionByDefault"in the application's config.xml file. In this situation, if the browser is closed, the session remainsactive. If the browser remains closed, once the value in this parameter is reached, the user must re-login. The default is 1800 seconds (30 minutes).

● Support for Google Chrome 37, Internet Explorer 11, and Mozilla Firefox 32

Chrome 37 and Firefox 32 are now the minimum versions of these browsers that Workspacesupports. For details, see the TIBCO ActiveMatrix BPM Installation and Configuration guide.

11


Changes in Functionality

There are changes to certain functions of the following components in this release:

Work ManagerChanges in functionality in Work Manager for this release are described in this section.

● The following system action has changed: viewWorkList has been replaced by viewGlobalWorkList.

TIBCO FormsChanges in functionality in TIBCO Forms for this release are described in this section.

● A new URL parameter, tibco_enhanced_ui is introduced in this release. By default, forms from theprojects deployed in the previous releases are rendered as before. You can use this parameter toforce the forms to render using the enhanced user interface.

For details, see TIBCO Business Studio Forms User's Guide > Tasks > Enhanced User Interface.● The common resource bundle now includes keys for Enhanced User Interface.

For details, see TIBCO Business Studio Forms User's Guide > Reference > Common Resource Keys > Keysfor Enhanced User Interface.

A few other keys are also added or updated, such as:

● align_toolbar_button

● forms_compact_mode

For details, see TIBCO Business Studio Forms User's Guide > Reference > Common Resource Keys.

OpenspaceChanges in functionality in Openspace for this release are described in this section.

● The Data Views gadget has been renamed to Case Management.● The Reporting gadget is not present in the default tab layout.

12


Deprecated and Removed Features

This section describes deprecated and deleted features (if any), and lists features, if relevant, that maybe useful alternatives to the deprecated features in TIBCO ActiveMatrix BPM 3.1.0.

Any use of a deprecated feature should be discontinued as it may be removed in a future release.You should avoid becoming dependent on deprecated features and become familiar with the suggestedalternative features.

Deprecated Items

AffectedComponent Description

DeprecatedRelease

Runtime Message IDs in BRM service faults will be changed in a futureversion.

3.0.0

Runtime The following Properties are deprecated and will be removedfrom ECPublicationJMS.properties in a future release.Therefore the legacy method of event publication valid untilTIBCO ActiveMatrix BPM 2.2 will no longer be supported in afuture release of BPM and only the shared resource approachwould be supported:

● InitialContextFactory● InitialURL● TopicConnectionFactory● SecurityPrinciple● SecurityCredentials● SecurityEncryption● Persistent● Priority● TimeToLive● TopicName

3.0.0

Runtime The correlation behavior for all BX audit events will change infuture versions.

3.1.0

Runtime ec_stats table is deprecated and will be removed in a futureversion.

3.1.0

13



DeprecatedRelease

Runtime The following Directory Engine APIs are deprecated and willbe removed in a future version. The information belowspecifies the replacement API (as bullet points) for each of theAPIs deprecated (in italics). In most cases, the replacementAPI provides additional options and information over-and-above that of the original, deprecated API.Attribute Service

listBusinessParameters

● OrgModelService.getOrgModel● OrgModelService.getOrgModelRoots

Both these services return the Resource Attributes for a givenorganization-model version.

getBusinessParameters

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity

The Attributes are returned as part of the details of eachorganization-model entity included in the response of boththese services.

● OrgResourceService.getResource

This method includes the Attributes for a given Resource.

setBusinessParameters

● OrgResourceService.updateResource

Only the Attributes for a Resource can be updated (not thosefor an organization-model entity). This method allows thoseAttributes to be set/updated.

getPushDestinations

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity

These services include the Push Destinations as part of thedetails for each organization-model entity in the response.

● OrgModelService.getPushDestinations● OrgResourceService.getResource

These methods include in the Push Destinations for theidentified entity. The OrgModelService.getPushDestinationscan also be used for Resources.

setPushDestinations

● OrgModelService.updatePushDestinations

3.1.0

14



DeprecatedRelease

Sets, or updates, the Push Destination for a given entity.

Browse Model Service

listCapabilities


Both these services include a list of all Capabilities definitionsfor a given organization-model version.

listPrivileges


Both these services include a list of all Privilege definitions fora given org-model version.

getCapabilities

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity● OrgResourceService.getResource

All these services include the Capability assignments as partof the details for the organization-model entities, andresources, included in the response.

getPrivileges

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity● OrgResourceService.getResource

All these services include the Capability assignments as partof the details for the organization-model entities, andresources, included in the response.

listModelVersions

● OrgModelService.listOrgModelVersions

This service lists all major organization-model versionnumbers. Nested within each major version are the details ofthe organization-models that make up that major version.

openOrgModel

● OrgModelService.getOrgModelRoots

This service returns the details of the root entities of the givenorganization-model version. For Groups and Organizations,the identifiers of any immediate child entities (sub-Groups orOrganizational Units) are included. Those identifiers can then

15



DeprecatedRelease

be fed into the OrgModelService.getOrgModelEntity, in orderto retrieve details of those entities, in a drill-down fashion.

browseModelNode

● OrgModelService.getOrgModelEntity

This service returns the details of an organization-modelentity identified by its organization-model version and GUID.Those entities that have nested, sub-ordinate entities (Groups,Organizations and Organizational Units) will include theidentifiers of those sub-ordinate entities. Those identifiers canthen be fed back into the same service, in order to retrievedetails of those entities, in a drill-down fashion.

listOrgModelOverview

● OrgModelService.getOrgModel

This service returns the details of all the entities within a givenorganization-model version.

listOrganizations

● OrgModelService.getOrgModelRoots

This service returns the details of the root entities of the givenorganization-model version. For Groups and Organizations,the identifiers of any immediate child entities (sub-Groups orOrganizational Units) are included. Those identifiers can thenbe fed into the OrgModelService.getOrgModelEntity, in orderto retrieve details of those entities, in a drill-down fashion.

Container Service

listLDAPContainers

● DirectoryService.listContainers

This service returns the full details of all LDAP Containers;including the mappings of LDAP Attributes to ResourceAttributes.

getLDAPContainerDetail

● DirectoryService.listContainers

saveLDAPContainerDetail

● DirectoryService.saveContainer

Creates, or updates, an LDAP Container.

deleteLDAPContainer

● DirectoryService.deleteContainer

This service will delete the identified LDAP Container, and,optionally, all Resources derived from that Container. IfResources, derived from the identified Container, still exist

16



DeprecatedRelease

(and the option to delete them is not used), the deletion will berefused.

LDAP Service

listLDAPSources

● DirectoryService.listLdapConnectionsThis service will return the details, including the connectionURL, of all available LDAP Connection Shared Resources.

listLDAPEntities

● DirectoryService.listCandidateResources● DirectoryService.getCandidateDetailThe listCandidateResources will return the LDAP details(alias and DN) for the LDAP entries accessible to theidentified LDAP Container. For those entries for which aResource has been created, the GUID and name of thatResource will be included. The service allows the caller to listonly entries associated with existing Resources, only entriesnot associated with existing Resources, or both. The servicealso allows the entries to be retrieved in a paged fashion.

Having retrieved the LDAP DN of the LDAP entries for theLDAP Container, the values of any LDAP attributes mappedto Resource Attributes can then be retrieved usinggetCandidateDetail.

listContainerResources

● DirectoryService.listCandidateResources● OrgResourceService.getResourceThe listCandidateResources will return name and GUID forthose Resources derived from the identified LDAP Container.

Having retrieved the GUID for the Resources derived fromthe LDAP Container, the full details of those Resources canthen be retrieved using getResource.

listLDAPAttributes

● DirectoryService.getLdapEntryThis service returns the values of the named LDAP Attributefor the given LDAP DN. If no LDAP Attributes are named, theresponse will include all attributes for the identified LDAPentry. The values of those attributes that contain binary datawill be base-64 encoded, and the attributes entry will bemarked as binary.

listLDAPAttributeNames

● DirectoryService.listAttributeNamesThis service identifies the names of the LDAP attributes forthe entries identified by evaluating the given LDAP Query

17



DeprecatedRelease

against the LDAP Connection identified by its alias. Thoseattributes that hold binary data will be marked as such.

The response can also include a sample of the values for thoseattributes. The values of those attributes that contain binarydata will be base-64 encoded.

Mapping Service

listMappedEntities

● OrgResourceService.findResources● OrgResourceService.getResource

The findResources service will return name and GUID ofthose Resources associated with an identified org-modelentity (Group, Organization, Organizational Unit, Position,Location, Capability and Privilege). For Location; only thoseResources directly assigned to the identified Location will beincluded.

The getResource service can then be used to retrieve the fulldetails of the Resources, using their GUIDs.

getResourceGuid

● EntityResolverService.lookupUser● OrgResourceService.getResource● DirectoryService.listCandidateResources● OrgResourceService.createResource

Using lookupUser and getResource, the details of an existingResource can be retrieved using the LDAP DN for that user.

Using listCandidateResources and createResource, a newResource can be created from the LDAP properties retrievedfrom the LDAP Container.

deleteResource

● OrgResourceService.deleteResource

This service deletes the records of one or more Resourcesidentified by their GUID.

mapEntities

● OrgResourceService.createResource● OrgResourceService.updateResource

Resources, created by the createResource service, can beassigned to Positions and/or Groups using theupdateResource service.

updateCapabilityAssignments

● OrgResourceService.updateResource

18



DeprecatedRelease

This service allows the update of a Resource's Capabilityholdings; along with other properties of the Resource.

Deleted Items


DeprecatedRelease

RemovedRelease

ProcessManager

We no longer support sharing servicesor migration between modules with thesame name but different applications.This means that modules' uniquenesswill now be identified based on themodule name, module version andapplication name.

3.1.0 3.1.0

19


Migration and Compatibility

This topic describes migration and compatibility issues for TIBCO ActiveMatrix BPM 3.1.0.

Refer to TIBCO ActiveMatrix BPM Installation and Configuration for upgrade instructions.

If migrating from versions prior to this version, see TIBCO ActiveMatrix BPM Installation andConfiguration for information on configuring new features post upgrade:● Configuring CMIS if migrating from TIBCO ActiveMatrix BPM 3.0.● Using the Edit wizard to configure the BDS database to be other than internal BPM database.● Configuring Single sign-on.

20


TIBCO ActiveMatrix BPM Version 1.3

● Using getWorkListItems in a Client Application

Up to and including version 1.2, the entityID element used by getWorkListItems is contained withina choice element.

In some programming environments (such as .NET in its default form), choice elements arerepresented by a parent entity (in this case, Item) which can be cast to any of the types that thechoice allows. For more information, see "Handling Choice Elements in the BPM API Schemas" inthe TIBCO ActiveMatrix BPM Developer Guide.

In version 1.3, the choice element has been removed.

An existing application built using the version 1.2 BPM web service API will continue to run againstTIBCO ActiveMatrix BPM version 1.3.

However, if you rebuild an existing application (that uses getWorkListItems) against the version 1.3BPM web service API, you should change your code to directly use entityID (instead of casting).

TIBCO ActiveMatrix BPM Version 3.0

● Updating Client Applications to Use SOAP Version 1.2

Up to and including version 2.2, TIBCO ActiveMatrix BPM only supported SOAP version 1.1

A TIBCO ActiveMatrix BPM version 3.0 system can be configured to use SOAP version 1.1 (thedefault) or version 1.2 bindings. (See TIBCO ActiveMatrix BPM Installation and Configuration for moreinformation.)

To communicate with a (new or reconfigured) TIBCO ActiveMatrix BPM system that uses SOAPversion 1.2 bindings, an existing client application built using a version 2.2 (or earlier) BPM webservice API must be modified as follows:

API Used Modification Required

BPM web service API Rebuild the application using the SOAP 1.2version of the API.

Java Service Connector Reconfigure the application to use SOAPversion 1.2 - see "Instantiating and Configuringthe Service Connector" in the TIBCOActiveMatrix BPM Developer Guide.

Configuring the Business Data Services (BDS) DatabaseIn particular cases, you may need to configure ActiveMatrix BPM so that names that are used in theBDS database are limited in length to 30 characters. This is to avoid issues that may arise if you latermigrate BDS database tables from Microsoft SQL Server or DB2 to Oracle.

21


Prerequisites

If all the following conditions apply to your situation, we strongly advise you to perform thisprocedure:

● You are upgrading ActiveMatrix BPM (fresh installations are not affected).● ActiveMatrix BPM is using DB2 or Microsoft SQL Server.● You have not yet deployed any BDS Global Data Applications to your running system, or are

upgrading ActiveMatrix BPM from a version before 3.0.

If you have a system to which existing BDS Global Data Applications have been deployed, you shouldnot perform this procedure unless you are happy to first undeploy the Applications.

Procedure

1. Open the bds.properties file in a text editor.

The file is typically stored on the machine where you installed ActiveMatrix BPM, in the followingfolder:

CONFIG_HOME/bpm/BPM_APP_NAME/configuration/

2. Set the following properties to the values shown:# Allows the specification of the maximum length to use for table names.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreTableNameMaxLength=30 # Allows the specification of the maximum length to use for column names.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreColumnNameMaxLength=30 # Allows the specification of the maximum length to use for a database index.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreIndexNameMaxLength=30

These settings limit the length of the names used in the BDS generated database.

3. Save and close the file.When you have set these properties and deployed a BDS Global Data Application, you should notchange the property values again.

Upgrade Script Issue with Openspace GlobalHubPolicy DataThe upgrade script does not upgrade the Openspace GlobalHubPolicy data automatically. This meansthat the Calendar is not displayed. A manual post-upgrade action is required.

Procedure

1. Log into Openspace and open the preferences panel on any tab except Calendar, then click MoreGadgets.

2. Select Manage Gadgets > Communication. The Hub Policy Administrator opens.

3. Click Delete Selected Domain. A warning appears - click OK.

4. Click Save.

5. Select Manage Gadgets > Communication to reopen the Hub Policy Administrator.

6. Click Add Hub Policy.

22


7. Warnings appear - click OK.

8. More warnings appear - click OK.

9. Expand the OpenspaceApp / Publish Topics to confirm that TranslationEvent2 is listed.

10. Click Save.

11. Close the Hub Policy Administrator and log out of Openspace.

12. Log into Openspace again and the Calendar is available.

Upgrading the Oracle JDBC DriverTo use the new case data features of 3.0 on Oracle, you must ensure your JDBC driver meets theminimum version requirement of 11.2.0.4.0.

If you have upgraded TIBCO ActiveMatrix BPM, ensure that you have the correct JDBC driver. You canfind out the current version of the Oracle JDBC driver by looking for the following entry in the log fileon system startup:

16 Apr 2014 11:03:27,276 [Job_Executor4] [INFO ] org.hibernate.cfg.SettingsFactory -

JDBC driver: Oracle JDBC driver, version: 11.2.0.4.0

Alternatively, locate the following folder: TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001, open the ojdbc6 JAR file, and examine the fileMETA-INF/MANIFEST.MF for the following entry:

Implementation-Version: 11.2.0.4.0

If your Oracle JDBC driver does not meet the minimum requirement, use the following procedure toupgrade it.

Procedure

1. Shut down the entire system (Administrator and all BPM nodes on all machines).

2. On all machines, replace the file ojdbc6.jar in the folder TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001 with the JDBC driver thatmeets the minimum requirement (11.2.0.4.0).

3. On all machines, replace the file ojdbc6.jar in the folder TIBCO_CONFIG_HOME/tibcohost/Admin-AMX BPM-AMX BPM Server/data_3.2.x/host/plugins/

com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001 with the JDBC driver that meets the minimumrequirement (11.2.0.4.0)

4. Start up the entire system (Administrator and all BPM nodes on all machines).

Openspace Upgrade Script and Data ViewsWhen upgrading to TIBCO ActiveMatrix BPM 3.0.0 from an earlier version, the upgrade script will notadd the new Data Views, Data Admin and Organization Browser components to existing user layouts.A post upgrade step is required to push the new gadgets and layout to existing users.

There are two scenarios.

If no standard persona exists

The default persona is modified during the upgrade to include the new default TIBCO layout thatincludes the new Data Admin, Data Views and Organization Browser gadgets. After upgrade, theOpenspace Administrator must do the following:

● Login into Openspace.● Click Manage Settings.

23


● From the drop-down list, select Default Persona.● Select Apply persona to all users.● All users must select Reset Settings and then logout and login to Openspace.

— This causes all users settings to default to the new TIBCO layout. Next time they log in, amessage displays informing them that their settings have been updated and the new layout willbe applied.

— Any user customizations such as sort / filter settings are reset to default and need to berecreated.

If a standard persona does exist

If you have previously created a Standard (customized) persona which is applied to new users andexisting users (in other words Apply persona to all users) was selected when the persona was created.The Standard persona is not modified by the upgrade. After upgrade, all existing and new users willcontinue to see the Standard persona layout. To see the new TIBCO layout, the OpenspaceAdministrator must do the following, after upgrade:

● Delete the standard persona and perform the steps described above to modify the default persona.● Modify the standard persona to include the new gadgets and desired layout and then apply it to all

users. See TIBCO Openspace User's Guide for more information.

Workspace MigrationThis section describes migration issues if you are upgrading TIBCO Workspace to version 3.1.0 from aprevious version.

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 configurationparameters and user access elements after upgrading depends on whether you are using theWorkspace application or a custom WCC application.

The following two subsections describe what to do depending on the type of application you are using.Then the last subsection lists the configuration parameters and user access elements that have beenadded in Workspace 3.1.0.

For information about migrating from earlier versions, see earlier release notes.

Workspace Application

If you are running the Workspace application, after you upgrade, any new configuration parametersare automatically available and any new user access elements are automatically included in theAccessDefaults user access profile. However, if you have user access profiles other than AccessDefaults,you must manually add the new elements to those profiles to make use of the elements.

Custom WCC Application

If you are running a custom WCC application, and want to make use of new configuration parametersand user access elements, you must manually add them to your application’s config.xml file anduserAccess.xml file, respectively, on your development environment file system. You must thencreate a new .war file for your custom application, and redeploy the application using ActiveMatrixAdministrator. For information about the process of creating the .war file and deploying anapplication, see "Deploying an Application After Customizing" in the TIBCO Workspace Configurationand Customization guide.

24


Also note the following:

● If you choose not to use the new configuration parameters and user access elements, and you do notredeploy, your custom WCC application will not pick up the new WCC runtime; you must stillcreate the .war file and redeploy for your application to use the new runtime, even if you don'twant to use the new parameters and elements.

● If you add the new configuration parameters and user access elements to the files in yourdevelopment environment, and then create the .war file and redeploy, they will not be picked up inyour WCC application if you had previously accessed the Configuration Administrator and madechanges to configuration or user access that would result in the settings being stored in thedatabase. If this is the case, after redeploying, you must open the Configuration Administrator andeither click Defaults 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 ConfigurationAdministrator interface. (For more information about using the Configuration Administrator andhow it writes information to the database, see "Using the Configuration Administrator" in theTIBCO Workspace Configuration and Customization guide.)

● 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 followingtasks:

— 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 newrelease. For example, if the name of your custom application is "accounts", copy:

StudioHome\wcc\oldVersion\accounts.html

To:

StudioHome\wcc\newVersion\accounts.html

— Copy the .war creation command file for your custom application from the previous release tothe 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 towhich you are upgrading.

New Configuration Parameters and User Access Elements

This section provides information about configuration parameters in config.xml and user accesselements in userAccess.xml that are new in version 3.1.0.

New Configuration Parameters

25


The following configuration parameters have been added in Workspace version 3.1.0:

● logoutPath - This new parameter is used to specify the action that Workspace takes on logout. Youcan specify that the application be reloaded with the original URL, or a custom URL, so customprocessing can be performed, including clearing the session, if desired.

● showLogoutButton - This new parameter used to specify that the Logout button not be displayedwhen using Single Sign-On, as it is not needed because the session is controlled externally to theapplication.

● HelpFileLocations - This new parameter is used to specify the location of the Workspace andOrganization Browser help files. This parameter can be used to point to the help files if you havedownloaded and stored the help files locally (because users do not have access to the Internet).

New User Access Elements

There are no new user access elements in Workspace version 3.1.0.

26


Closed Issues

The closed issues in TIBCO ActiveMatrix BPM 3.1.0 are listed per component:

● Core Components● TIBCO Forms● Clients

Core ComponentsThe section lists closed issues for Core Components in TIBCO ActiveMatrix BPM 3.1.0.

Work Manager

Key Information

WRM-7539 Unable to access the worklist from Case Management UI - fails with "UnauthorizedAPI".

WRM-7533 An ordering issue while processing statistics events can cause Event Collector (EC)event triggers to be processed in the incorrect order. This can then lead to incorrectStatistics Collector (SC) status information, and in addition it can also lead to SCfailing to process triggers causing SC to to retry the trigger processing. This thencauses a backlog in the ec_event_triggers table that further slows down the SCprocessing.

WRM-7532 Fix precise time ordering issue across nodes (the implementation of precise timerelies on the CPU clock which is not accurate). This can cause Event Collector (EC)event triggers to be processed in the incorrect order on a multi-node installation.This can then lead to incorrect Statistics Collector (SC) status information, and inaddition it can also lead to SC failing to process triggers causing SC to to retry thetrigger processing. This then causes a backlog in the ec_event_triggers table thatfurther slows down the SC processing.

WRM-7501 If a workitem is opened and then closed immediately then an error occurs. Partiallypopulated BDS objects were being validated on a close, meaning any missingmandatory fields in the complex objects caused the close to fail. Validation shouldonly be performed on a submit.

WRM-7380 Statistics Collector (SC) throws "ORA-24816: Expanded non LONG bind datasupplied after actual LONG or LOB column" during a loadtest with 1500 users. Thiscauses SC to fail to process an event trigger, SC then has to retry processing theevent trigger. This then causes a backlog in the ec_event_triggers table that cancause SC processing to slow down.

WRM-7216 Model entities (including model template entities) have two 'name' values; "name"and "label". When a model entity is generated from a model template entity, it takesall its properties from that model template entity. Prior to this fix, the label propertyof the model template entity was not copied to the generated model entity.

27


Key Information

WRM-7170 TCT does not load some configuration values for certain panels of the main BPMwizard:

● The sizing panel doesn't have a "Custom" option, so always defaults to Prod orDev on load (depending on what you selected) and sets all the values to thedefaults for either of those. It should choose "Custom" when you changeanything and keep your choices.

● The ActiveMatrix Administration Database username is always blank after aload.

WRM-7113 When purging Event Collector data via the API record sets over 1000 will beprocessed in batches rather than as an atomic operation for performance reasons.

WRM-7084 If you have two environments, each of which has an instance of the ActiveMatrixBPM application that is called amx.bpm.app, upgrade can fail to reprovision thenodes.

WRM-7065 In the TIBCO Configuration Tool (TCT), the default values are always used in theActiveMatrix BPM installation even if if you specify different values for thefollowing fields:

● bpm.userapp.jms.enablessl● bpm.userapp.jms.ssl.keystoretype● bpm.userapp.jms.ssl.keystorelocation● bpm.userapp.jms.ssl.keystorepassword

WRM-7060 When an email that contains a link to a work item is pushed, the link correspondsonly to a particular version of the work item. This version may not be the latest, ifthe work item has been opened after the email was created.

To address this issue, you can set a new propertyUSE_LATEST_VERSION_ON_PUSH to true to ensure that the link always openswhichever is the latest version of the work item when the link is clicked. For moreinformation, see the TIBCO ActiveMatrix BPM Administration guide.

WRM-7046 The performance of the deadline calculation has been significantly improved.Although all durations have been improved, this is more noticable for deadlinedurations exceeding 10 years.

WRM-7045 When organization restrictions have been put in place (by associatingOrganizations with LDAP Containers), a user (user-A) may access another user(user-B) if any of the following are true:

● If both users come from the same LDAP Container.● If user-B's LDAP Container has no associated organizations.● If user-A's LDAP Container shares any organization association as user-B's

LDAP Container.● If the user-A is granted the System Action organizationAdmin.

28


Key Information

WRM-7036 An internal error caused a failure in the execution of the REST implementation ofthe Directory Service Execute LDAP Query API (executeLargeLdapQuery).

WRM-7030 If you add a Close button on a pageflow step, a null pointer is generated.

WRM-6999 Improvements have been made to the purging of case audit data.

To help address these issues, the Event Collector purge scripts have been modified:

● Oracle

— Case audit data is no longer purged.— References to ROWID in the scripts have been removed because they could

cause an issue if row movement is enabled.— cursor_refresh is enabled and now represents a period of time (in seconds)

before the cursor is refreshed again.● Microsoft SQL Server

— Case audit data is no longer purged.— cursor_refresh is enabled and now represents a period of time (in seconds)

before the cursor is refreshed again.

WRM-6962 When performing an unlinkCase on case data that is linked, the case reference is notupdated on the case data that is being unlinked. This means that further operationson the case reference fail and an error similar to the one below is displayed:

There is a newer version(2) in the case datastore than currently

requested version(1) for type(com.example.ordermodel.Order)

id(12053)

WRM-6960 If you reference a class that is not in the same project you may get an error.

WRM-6948 Propagate Model Template Candidate Query changes to instances.

WRM-6935 Adding a new composition to a Case Data Object Model and deploying a newversion causes a problem wherein case objects cannot be deleted from the database.Deletion fails with a foreign key violation error.

WRM-6909 Instances of pageflows are cached. If you have a pageflow that is completedwithout ever being updated, the pageflow instance is never removed from thecache.

WRM-6897 There are issues with the purging of case audit data.

To help address thes issues, the Event Collector purge scripts for the EventCollector purge APIs and DB2 have been modified so that case audit data is nolonger purged.

WRM-6888 If a work item tries to read a global data object that no longer exists (for example,because it has been deleted), ActiveMatrix BPM handles the failure scenarioincorrectly.

29


Key Information

WRM-6869 LDAP Referrals allow one LDAP Server to reference entries on another LDAPServer. The referral provides the information to connect to the other LDAP Serverand retrieve the referenced entry. An error would occur when attempting toreference an LDAP referral on an SLL-enabled LDAP.

WRM-6833 EC scripts generated with the DB cleanup do not drop indices at the end of thescript

WRM-6821 While running a process that includes a Reusable Sub-Process task that runs in amultiple instance loop, some Oracle deadlocks occur in the statistics collectorthread.

WRM-6800 EC Purge scripts do not accept NULL values for batchsize on oracle.

WRM-6780 The ec-probes-rules has the message IdBDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT_AUDIT which should actually beBDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT.

WRM-6778 We support single sign-on using Siteminder authentication. Multiple applicationscan partake in single sign-on using Siteminder. If the user is logged into a partakingapplication, the user can log in to all the other partaking applications withoutproviding credentials again for each application. However, once the user is signedon using single sign-on, the logout links on Openspace and Workspace do not signoff the user from applications.

WRM-6757 If a process declares a mandatory IN parameter, and you try to start the businessservice without specifying the parameter, the business service call returns a SOAPfault with a Null Pointer Exception. The call should return a SOAP fault thatcontains a message describing the issue.

WRM-6608 Case Data : Data View : View Creation without category is possible from SOAP UI.If this view is created, it cannot be shown in Openspace or Workspace.

WRM-5878 If closing or submitting a work item fails because the update on the case referencehas failed as the case reference is stale (for example, the global data has beenupdated concurrently by another user), the error Cannot resume validtransaction is displayed, and the work item is stuck in an Opened state.

Process Manager

Key Information

BX-3421 Imported XSD schema with inline WSDL schema seems to be ignored duringschema registration resulting in "Cannot find XML data type" exceptions inruntime.

BX-3418 Set parent's process priority on inline sub processes.

BX-3394 Task stuck in starting state. The XPDLtoBPEL converter is not marking a task as anuncontrolled merge when it should.

30


Key Information

BX-3327 If a user application that calls the BPM public API is deployed to the runtime, it canprovide packages that are duplicates of those provided by the public API. This cancause the following error:

java.lang.LinkageError: loader constraint violation: loader

(instance of org/eclipse/osgi/internal/baseadaptor/

DefaultClassLoader) previously initiated loading for a different

type with name "com/tibco/n2/common/api/exception/ErrorLine"

if you perform any of the following:

● Start tibcohost in -clearCache mode.● Start tibcohost in resolve mode.● Apply any hot fixes.

BX-3315 If you perform the following steps:

1. Create two WSDLs with the same port type names but different namespaces.

2. Create an operation in each port type with the same name.

3. Create a process with a receive task for each of the above operations.

4. Deploy the application and send a message to both operations.

both messages are delivered to the same process definition.

BX-3312 Fix "Reply Immediate Option" for process design that includes the use of a pick.

BX-3277 In TIBCO Workspace, on the Process views tab, if you click the Next and Previousbuttons, action processor errors are thrown.

BX-3235 Service task for "Global Data Service" does not support retry options in theResource tab.

BX-2770 TIBCO Business Studio process editor/validation hangs in Process Manager flowanalyzer on certain processes (sometimes eventually resulting in Out Of memoryexception).

BX-2756 Process Manager: Enable cursors return from QueryProcessInstances to workacross multiple nodes.

PVM-636 Issues with passing text array parameter from subprocess to parent process.

PVM-635 XML serialization issue in Pageflow invoking web-service in mediation.

PVM-615 If you deploy and run a BPM user application, and then upgrade ActiveMatrixBPM to version 3.0, undeploying the application causesorg.hibernate.PropertyAccessException if the application has any pendingmessages.

PVM-614 Expose Request Queue configuration parameters to allow them to be modified.

31


Key Information

PVM-586 The PVM engine reschedules any process events whose module is not ready(application not running) with a lower priority of 100. Although this works OKnormally, in busy BPM environments this can cause high priority processes to berescheduled with priority 100 and suffering starvation.

To address this issue, the priority of process events whose module is not ready islowered incrementally instead.

TIBCO FormsThe table lists closed issues for TIBCO Forms in TIBCO ActiveMatrix BPM 3.1.0.

Runtime

Key Information

FORM-6641 The container class is deprecated. Instead, you can use tf-container.

For details, see TIBCO Business Studio Forms User's Guide > Reference > CSS Classes >Built-in Static CSS Classes.

FORM-6511 The documentation on keyboard shortcuts is now updated.

For details, see TIBCO Business Studio Forms User's Guide > Reference > KeyboardShortcuts.

FORM-6414 Two new methods, getParameterNames() and getParameterValue() are added inthe Form class. You can access parameter and data field values from custom clientsusing these methods.

For more information, see TIBCO Business Studio Forms User's Guide > Reference >API for Scripting > Methods for Form Class.

FORM-6274 The default timeout for JSONP requests is increased from 2.5 seconds to 1 minute.The timeout can also be configured using the two URL parameterstibco_jsonp_tinterval and tibco_jsonp_tmrc.

The parameter tibco_jsonp_tinterval refers to the number of seconds the timerneeds to wait before checking the status of the request whereas tibco_jsonp_tmrcrefers to the number of times it needs to execute the check. Thus, iftibco_jsonp_tinterval is set to 500 (default) and tibco_jsonp_tmrc is set to 120(default), the JSONP request times out in 120 * 500 = 60,000 ms, that is 1 minute.

ClientsThe section lists closed issues for Openspace and Workspace clients in TIBCO ActiveMatrix BPM 3.0.0.

Openspace

Key Information

OS-2606 If you are using ActiveMatrix BPM with Siteminder, you cannot log in to theOpenspace accessible client.

32


Key Information

OS-2593 The Business Service App (BizApp) fails to participate in Single Sign-On with RESTservices if REST services are the first to be called.

OS-2591 The Business Service App (BizApp) fails to participate in an existing session.

The default authentication mode for BizApp has been changed so that by defaultBizApp participates in any existing session.

OS-2590 In the Organization Browser, the first letter of the title new LDAP Containershould be capitalized.

OS-2579 When Openspace is running in Korean or Chinese (Simplified), the Calendar tabuses the wrong date format.

OS-2560 In the Data Views gadget, you cannot select the columns on the Details tab, and thepreference for certain columns does not persist.

To address this issue, a column selector has been added. For more information, seethe TIBCO Openspace Customization Guide.

OS-2557 When a work view is edited in the Work Views gadget, the sort is no longerapplied and is missing from the Summary page.

OS-2550 The Mexican flag in the main banner does not match the Mexican flag used in thelanguage selector drop-down list.

OS-2549 On the welcome page, the link "Build your own gadget or add and app from theOpenspace App store" is broken and contains a typo.

OS-2544 When Openspace is running in Mexican, Portuguese, or Spanish, in the Reportinggadget, the Calendar label is truncated on the Averages tab.

OS-2538 The Openspace login URL is missing the TIBCO favicon (favorite icon).

OS-2537 In the calendar time zones list, some old place names are used.

OS-2531 In the Reporting gadget, when you click Start Date or End Date, the date pickerdialog is truncated.

OS-2515 Some non-English menu item text continues onto a second line, causing the imageof the next menu item to be cropped.

OS-2513 The Data Views gadget contains an empty tab.

OS-2509 The Data Views gadget allows you to set a page size greater than seven, but it onlydisplays seven results.

OS-2443 The CSS for Openspace - Mobile causes rendering issues in TIBCO Forms.

OS-2382 In the Work Views gadget, the Filter drop-down list, the Work Item AttributeColumns, and the Work Item Attributes should display work item attributes 1-40instead of work item attributes 1-14.

33


Key Information

OS-2029 Load an existing view does not work for the work view View is of all work items,even though the work view has the View Global Worklist action.

Workspace

Key Information

WS-1576 The Workspace user access DataView > DataViewList > DataViewResults >WorkItems has been modified to depend on the BRM.viewGlobalWorkList systemaction. It previously depended on the BRM.viewWorkList system action. This isdue to a change made in ActiveMatrix BPM in WRM-7539.

WS-1568 When the Action Processor constructs the query to get the counts for a haltedprocess view, it does not put the user part of the filter in parentheses.Consequently, the wrong logical filter is evaluated and the count on the list maynot match the contents of the list.

WS-1552 The audit message for the DE_ENTITY_AUDIT_REMOVE_FROM_ENTITY eventis incorrect.

WS-1530 If authenticationMode=useSessionByDefault and an invalid username orpassword is entered in the login dialog, subsequent attempts to log in with thecorrect username and password fail until the application is reloaded.

WS-1525 When Workspace is using an Oracle or Microsoft SQL Server database, if youcreate a process view using the Include selected processes option, then youindividually select hundreds of process templates, and then you try to edit theprocess view, the process template selection page of the process view wizarddisplays an unresponsive script message.

If you select the process view list, Workspace takes a long time to load the list.

WS-1523 When a data view is defined externally to Workspace, an unhandled exception isthrown when the view is edited and saved in Workspace if both of the followingconditions apply:

● The filter contains a clause that contains multiple arrays in the attribute path.● The last attribute in the path is an array that is denoted by empty brackets "[]"

or no brackets.

WS-1519 Workspace allows you to create a Data View category that has a blank name. Thisis a problem because the category is not visible in TIBCO Openspace.

WS-1518 The Process Views wizard does not display all the process templates that areavailable. It displays only the first 500.

WS-1513 When Workspace is running in Russian, the Show Details dialog is overlapped byany error windows displayed in the Event Viewer.

WS-1508 There are problems with the validation of Data View category names.

34


Key Information

WS-1507 In Event Viewer, the default event view for errors may display many errors, manyof which may be irrelevant if they're old.

The default event view now displays all errors that have been generated on thecurrent day.

WS-1506 When you create or edit a data view, if your filter attribute allows multiple values,when you try to specify a logical operator for the filter attribute, Workspace alwayschanges the logical operator to "[ANY]". For example, a filter expression of"nameddrivers[12].accidentHistory[ALL] SIZE_EQ '2'" is automatically changed to"nameddrivers[].accidentHistory[] SIZE_EQ '2'".

WS-1505 The following Process Engine message codes do not have descriptions when theyappear in Event Viewer: BX_TEMPLATE_INITIALIZED,BX_TEMPLATE_DESTROYED, BX_TEMPLATE_UNDEPLOYED.

35


Known Issues

The known issues in TIBCO ActiveMatrix BPM 3.1.0 are listed per component:

● Core Components● TIBCO Forms● Clients● Platform

Core ComponentsThis topic lists the known issues of Core Components in TIBCO ActiveMatrix BPM 3.1.0.

Work Manager

Key Information

WRM-7603 Summary: The following information was omitted from the ActiveMatrix BPMdocumentation. If TIBCO ActiveMatrix BPM is configured to use MicrosoftSharepoint 2013 to provide its content management system (CMS), the followinglimitations apply to the use of the DocumentService in the TIBCO ActiveMatrix BPMpublic API:

● The linkDocument and unlinkDocument operations cannot be used. This isbecause Sharepoint 2013 does not support multi-filing capability.

● You cannot use the LIKE operator when using the findDocument operation tosearch for documents in a case folder. This is because Sharepoint 2013 does notallow the use of the LIKE operator in CMIS Query language.

● You cannot use the CONTAINS() function (used for full-text searches) whenusing the findDocument operation to search for documents in a case folder. Thisis because Sharepoint 2013 mandates 'bothSeparate' query capabilities, butfindDocument performs a scoped search of documents (via the CMIS IN_TREE()clause) inside a case folder.

Workaround: Avoid usage of the above capabilities when Sharepoint 2013 is used asa CMS.

WRM-7593 Summary: Mapped attributes 15, 38, 39 and 40 are assigned to iteration, iteration ID,Host task name, Host task type respectively.

Workaround: Avoid using attributes 15, 38, 39 and 40 when mapping data fields.

WRM-7585 Summary: If you have deployed a BDS project but have not created any cases for acase data case, the getCaseSummary API should return a fault for a non-existingcase.

Workaround: None.

WRM-7577 Summary: When you install TIBCO ActiveMatrix BPM, it will not work if you havespaces in TIBCO_CONFIG_HOME.

Workaround: Avoid having any spaces in TIBCO_CONFIG_HOME.

36


Key Information

WRM-7574 Summary: Sometimes a misleading exception is thrown (Null Pointer Exception)when a pageflow execution fails (for example, when a wrong set of parameters arepassed).

Workaround: None.

WRM-7553 Summary: The listCaseAction API is used by case management gadget (it could beused by custom clients as well) to display list of case actions that corresponds to agiven case reference. If a case reference passed to this API becomes stale (forexample, if case objects gets deleted in-between reading it and supplying tolistCaseActions API), then the listCaseAction API will return all case actions ratherthan returning a fault.

Workaround: None.

WRM-7549 Summary: Error while performing SiteMinder SSO authentication in Openspace/Workspace when the IP address is populated in resource template.

Workaround: Remove the client IP address from the runtime.

WRM-7512 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: (For all claims)Clicking on a claim whose instance is completed, in the claim exposure value "-" isshown.

Workaround: None.

WRM-7509 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Internet Explorerspecific (Internet Explorer 9, 10 and 11) : Intermittent error where sometimes allreport contents are not loaded on the first attempt.

Workaround: None.

WRM-7508 Summary: TIBCO JasperReports Server for ActiveMatrix BPM : When you suspendprocess instances and resume, work items of such processes are not displayed in theOffered Work report.

Workaround: None.

WRM-7507 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Work items ofcancelled and suspended process instances should not be displayed in theOutstanding tasks report.

Workaround: None.

WRM-7502 Summary: Errors caused by the following 3 error conditions will not be visible whenaudit events are viewed from case management gadget:

● User does not have correct System Action● Request is not schema compliant● Document Service is not enabled in bds.properties

Workaround: None.

37


Key Information

WRM-7496 Summary: If you enter a valid JSON string in a text field on a form, either an errormessage is displayed or the string is not stored in the ActiveMatrix BPM databaseexactly as you entered it. For example, if you enter:

{"name":"joe"}

ActiveMatrix BPM interprets the string as a JSON string, and tries to process itaccordingly. This is because ActiveMatrix BPM uses JSON internally to handle formdata.

Workaround: To store in the database a JSON string that you have entered in a textfield, escape the double quotation marks using the backslash character. For example,to store the above string, enter:

{\"name\":\"joe\"}

Consequently, when the string is retrieved from the database, the escape charactersmust be removed, using http://org.apache.commons.lang3.StringEscapeUtils, forexample.

WRM-7484 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Not able to formatand apply filters on Top 5 claims reports.

Workaround: None.

WRM-7481 Summary: If a BOM contains a type hierarchy, for example a class 'Drink' and sub-classes 'Coffee' and 'Tea', then problems can arise when manipulating instances ofsuch Business Objects via a User Task meaning that you may lose some sub-classdata. If a class 'Person' has an attribute/composition of type 'Drink' then, although aForm may appear to allow Coffee and Teas to be assigned, the resulting BusinessObject will always record these as the base type, Drink.

Workaround: None.

WRM-7464 Summary: Logging related to the Document Service's findDocuments API cansometimes be missing from the BPM.log. For example, if the system is configured toinclude INFO level logging, then messages such as "CMIS where clause is(cmis:name LIKE 'abc.txt')" should appear in the BPM.log when a find operation isperformed.

Workaround: If such messages are expected but do not appear, then this can berectified by making an edit to the cm.properties configuration file. It is notnecessary to change any of the configuration settings; a simple comments changewill suffice. For example, one option is to add a character to the end of the first line("# Configuration file for Content Management functionality" could be edited to read"# Configuration file for Content Management functionalityX"). This willpermanently fix the problem.

WRM-7446 Summary: The entry for Shared Secret for SiteMinder should be shown as apassword character as the corresponding runtime uses the same pattern.

Workaround: None.

38


http://org.apache.commons.lang3.StringEscapeUtils

Key Information

WRM-7437 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: On loading ClaimBreakdown dashboard for first time if you click on the clear filter, 'All' claims aredisplayed though selected option is 'open' claim.

Workaround: Click on Open and then Closed again.

WRM-7415 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Cannot sort Top 5claims by claim value.

Workaround: None.

WRM-7393 Summary: TCT Edit Wizard should get and populate the current setting for editingLDAP authentication.

Workaround: Enter LDAP authentication information manually.

WRM-7333 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Column filtersshould not reset on refresh gadget or user login/logout.

Workaround: None.

WRM-7281 Summary: Case Data: When you delete a Case and the referring form has the sameCase marked as Mandatory, you receive an error.

Workaround: None.

WRM-7268 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Jaspersoftdashboards do not work on Internet Explorer 8.

Workaround: Use an alternative browser.

WRM-7195 Summary: Calling the setMigrationRules REST method with a json body results inan error.

Workaround: Use XML payload as request/response.

WRM-7188 Summary: Issue with extra null elements in the json data being returned from thequeryApplications REST call.

Workaround: You will need to include these extra elements when constructingJSONPath expressions. For example, if writing an expression to retrieve theprocessName from the returned JSON, you will need to write the expression asfollows:

$.xml-fragment.applications.. application.processTemplates.

processQName..processName

WRM-7183 Summary: SQL Server only: when using nested sub-process levels you may getdiscrepancy in Openspace and Workspace views because of a deadlock.

Workaround: Retry. It might take a few minutes for the data to be updatedcorrectly.

39


Key Information

WRM-6964 Summary: If you attempt to store a JSON string in a Text Field (note, this is notrecommended behavior) you will get an error submitting the form.

Workaround: You will need to escape the quote (for example /" ) .

WRM-6833 Summary: Event Collector scripts generated with the database cleanup do not dropindexes at the end of the script .

Workaround: You can drop these indexes using either the relevant database DROPcommand or a GUI tool.

WRM-6802 Summary: Event Collector Purge: Cursor_refresh (the number of process instancesthat should be deleted before the cursor is refreshed) is still considered as amandatory parameter even though it is deprecated.

Because the parameter is in the middle of the list of parameters and not at the end,providing no value for it causes a problem.

For example : EXEC amxbpm.ec_delete_audit_stats_data NULL, '08-OCT-1013:35:37', NULL, 'TRUE' would return an error as it tries to assign 'TRUE' tocursor_refresh which is a BIGINT.

Workaround: Provide a value for the Cursor_refresh parameter. For example,change the above command to EXEC amxbpm.ec_delete_audit_stats_dataNULL, '08-OCT-10 13:35:37', NULL, '10', 'TRUE'

WRM-6801 Summary: Warnings occur while creating indexes for Event Collector purge onMicrosoft SQL server.

Workaround: These indexes should be dropped immediately after finishing thepurge to avoid any future issues.

WRM-6791 Summary: TIBCO ActiveMatrix BPM Business Data Services Developer Guide:screenshots of TIBCO Business Studio's Properties tab are out of date.

Workaround: None.

WRM-6780 Summary: Updates to Global Data database scripts made via the Openspace DataAdmin gadget or web service API will not be audited.

Workaround: Edit the ec-probe-rules.xml configuration file, replacing'BDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT_AUDIT' with'BDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT'. Make this change if you want to seethis message propogated to the ec_event table

40


Key Information

WRM-6756 Summary: Search conditions based on certain attributes, whether specified in a DataView or DQL expression, can result in SQL errors at run-time.

Specifically, this can occur when (1) The attribute is multiplicity-many and on aglobal class, not the case class. and (2) The global object containing the attribute is inan attribute path that contains an [ALL] or [<index>] suffix in an earlier fragment ofthe path.

For example, consider searching for Clubs in the following BOM:

DQL expression: members[ALL].favouriteColours = 'Red'

Meaning: Find Clubs where all members have Red as one of their favorite colors.

DQL expression: members[0].favouriteColours = 'Blue'

Meaning: Find Clubs where the first member has Blue as one of their favorite colors.

Both of the expressions above can exhibit the problem.

To be clear, the problem occurs only when [ALL] or [<index>] are used, asdescribed above. The following DQL expression does not suffer from the problem:

DQL expression: members.favouriteColours = 'Red'

Meaning: Find Clubs where any member has Red of one of their favorite colors.

Workaround: Altering the BOM to eliminate the multiplicity-many attribute avoidsthe problem. In the following modified BOM, a Person contains many Colours, eachof which has a text attribute containing the name of the colour:

The original DQL queries would then be rewritten as follows:

DQL expression: members[ALL].favouriteColours.colour = 'Red'

Meaning: Find Clubs where all members have Red as one of their favorite colors.

DQL expression: members[0].favouriteColours.colour = 'Blue'

Meaning: Find Clubs where the first member has Blue as one of their favouritecolours.

In terms of the generated database tables, this is of equivalent complexity to theoriginal BOM, and may even be considered better practice.

41


Key Information

WRM-5878 Summary: If the Close/Submit fails because the update on the case reference hasfailed because the case reference is stale, errors are recorded in the BPM log, and thework item is stuck in Opened state.

Workaround: Cancel the work item, then re-open it (this causes it to re-read the casereference, thus getting the up-to-date version). Then the Close/Submit should work.

If the update fails because the case reference no longer exists, there is noworkaround.

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 the 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 in the XmlTask sourcefolder and then update 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 xmltask.jar file to the /opt/apache-ant-1.7.1/lib folder.

WRM-4698 Summary: It is not possible to connect to a CMIS repository accessed via SSL byusing the CMIS sample.

Workaround: None.

WRM-4186 Summary: If an enumeration in a BOM is a restriction of another enumeration, it isshown in TIBCO Business Studio as if one is a generalization of the other. However,they are two separate enumerations, with no inheritance from each other in theunderlying code. Therefore, an interface that expects the base type to be passed to itcannot be passed the restricted type, and there will be a run-time failure.

Workaround: If this XSD construct is used in a web service that ActiveMatrix BPMneeds to interact with, use a Mediation between BPM and the external web service.

42


Key Information

WRM-2604 Summary: Service Connector uses third-party Axis2 and Rampart libraries. Thismay increase the Java CLASSPATH length.

Workaround: To avoid CLASSPATH length issues, use the new feature provided inJava 1.6 to include all binaries by using the wildcard character(*).

1. Unzip the service connector to a folder, for example c:\service-connector.

2. Set the CLASSPATH to the c:\service-connector folder using the wildcardcharacter, for example:

SET CLASSPATH=%CLASSPATH%;c:\service-connector\*

WRM-1671 Summary: In TIBCO Workspace Event Views, the Push-related columns for thePUSH events do not display any information.

Workaround: None.

WRM-1539 Summary: If a measure is requested for a particular process, the returned data is acumulative roll-up of the data for the process. However, the statistics collector doesnot return any roll-up data for hours in which there is no activity in the process.

Workaround: If data for any hour is missing, assume that it is the same as that forthe previous hour.

WRM-521 Summary: If a pageflow process has no user tasks, this causes an exception when itis called from a client application, for example from either Openspace or Workspace.

Workaround: Add page activities to the pageflow process.

WRM-440 Summary: Uninstallation of TIBCO ActiveMatrix BPM fails to stop the processesBPMNode, AdministratorNode and TibcoHost before removing files.

Workaround: Stop the processes manually or restart the system.

WRM-69 Summary:The Email presentation channel does not support SMTP authentication.

Workaround: None.

Process Manager

Key Information

BX-3474 Summary: Sub-process with Start Immediately option inherits parent processpriority rather than starting the sub-process with priority Normal [200].

Workaround: None.

43


Key Information

BX-3456 Summary: Debugger inconsistently throws exceptions in the following situations:

● After debugging pageflow/business service.● After debugging a process on closing the project.● Closing the project and opening it again, then adding new breakpoints.

Workaround: None.

BX-3452 Summary: Initializers are not retroactive following a process migration. An ad-hocactivity added during a migration is not initialized by an activity that has alreadybeen executed prior to the migration, but will be initialized by an activity thatexecutes after the migration.

Workaround: If you want the ad-hoc activity to execute after the migration, makethe migration point activity an initializer.

BX-3425 Summary: TIBCO Business Studio workspace sometimes throws an error "Aninternal error occurred during: "Compute launch button tooltip"".

Workaround: None.

BX-3346 Summary: No support for mapping BDS data from a sub-process error event.

Workaround: Use a script task to break down the error data into multiple primitivefields.

BX-3214 Summary: amx.bpm.app redeployment after removing a node from theamx.bpm.app distribution halts process instance creation/execution.

Workaround: Restart all Nodes in the setup.

BX-2967 Summary: When you have two versions of an application - V1 and V2 with V2having event handlers and added mandatory parameters, process instances thatmigrate from V1 to V2 might go into 'Halted' state with an error - 'No value set formandatory 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 taskswhere the process instance migrates, the parameters should be made INOUT - non-mandatory.

BX-2956 Summary: Mapping between incompatible types like BPM attribute to POJO listcould result in ExpressionEvaluationError.

Workaround: Add a script task before the java service task to build the source dataas an array of Java objects out of the BDS list, before mapping it to the POJOmethod parameter.

44


Key Information

BX-2507 Summary: Data in the database and server's response can not display correctcharacters outside the character set supported by the default system encoding. Thiscould cause the extended message to be displayed incorrectly.

Workaround: None.

PVM-550 Summary: Maximum key length warnings appear when runningProcessManagerCreate.sql for SQL Server 2012.

Workaround: None.

TIBCO FormsThis topic lists the TIBCO Forms known issues in TIBCO ActiveMatrix BPM 3.1.0.

Runtime

Key Information

FORM-6725 Summary: Labels are rendered with borders, which may give a false impressionthat they are editable text fields.

Workaround: None.

FORM-6724 Summary: Specifying the key forms_compact_mode in the common resourcebundle does not affect the rendering of modal dialog panes.

Workaround: None.

FORM-6721 Summary: In Openspace, the hints provided for controls in grid panes are notaligned properly.

Workaround: None.

FORM-6717 Summary: On Internet Explorer 9, when focusing on a grid pane button or columnname, the height of the root pane or the grid pane increases.

Workaround: Set the CSS as .TibcoForms.tf-uir-enabled.ua-ie9 .pane-grid{ height:100%; } and .TibcoForms.tf-uir-enabled.ua-ie9 .pane_<parentpane name> .pane-content { height:50%; }.

FORM-6714 Summary: On Windows 8, forms do not load properly on the GWT Preview tab ofTIBCO Business Studio.

Workaround: Use an external browser to preview forms.

FORM-6705 Summary: After working on a form in Workspace, if you open the same form inInternet Explorer as a work item and see the data preview, going back to theSummary tab throws an exception in GWT Log.

Workaround: None. You can safely ignore the exception.

45


Key Information

FORM-6704 Summary: When a form is loaded on a BPM client, such as Workspace orOpenspace, an exception is thrown in GWT Log if the form has both BOM andglobal data references.

Workaround: None.

FORM-6700 Summary: On Internet Explorer 8, glyphicons used in a form are not alwaysvisible.

Workaround: Use alternative browser.

FORM-6466 Summary: Custom controls of complex type are not validated.

Workaround: None.

FORM-6460 Summary: A select event is triggered on value update in a grid pane even whenthere is no selection.

Workaround: In the action scripts, add null checks when the grid pane selectionAPI is used.

FORM-6446 Summary: The API setFocus(Integer index, Integer item) does not work on controlsin a record pane.

Workaround: None

FORM-6110 Summary: When editing a list control in Openspace or Workspace, if you scroll thewindow using the scroll-wheel, the edit box in the list control remains on the page,and does not scroll with the window. It is also applicable to editing controls in agrid pane when not in Always Render mode.

Workaround: Pressing the Escape or Enter key closes the edit box.

FORM-5717 Summary: At runtime, presumably only one version of a Component Library canbe loaded within the same browser session.

Workaround: If later versions of a process need to use an updated version of alibrary, then that library should be renamed to avoid a conflict with the earlierversion of the library.

46


http://glyphicons.com

Key Information

FORM-4911 Summary: In Safari 5, when the browser window is resized, some of the CSSproperties applied at the form level (such as background-color) will not workproperly, causing the form to render incorrectly.

Workaround: Add the following style for the TIBCO ActiveMatrix Workspaceapplication 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 BPMruntime instance. The location is as follows:<ProgramData>\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM Server

\data_3.2.x\host\plugins\com.tibco.n2.rtc.ws_1.8.0.011\resources

\addins\gwtforms

There is no need to restart the BPM node. It will be necessary to refresh the TIBCOActiveMatrix Workspace client application in your browser.

FORM-4809 Summary: Tabbing within list controls does not work properly in Firefox 3.5. Thisis not a problem in Firefox 3.6 and later.

Workaround: Use alternative browser.

FORM-4164 Summary: A mobile form that contains a Duration list control is not properlydestroyed when the form is submitted.

Workaround: None. The only workaround is to avoid using Duration list controlsfor forms targeting the mobile presentation channel type.

FORM-4145 Summary: In mobile forms, the deletion of values from multi-valued list controls isnot working.

Workaround: None.

FORM-3544 Summary: Sometimes the loading of a mobile form is slow or can appear to freeze.This only happens during the initial load of the particular form and for subsequentinstances of the same form load.

Workaround: None.

FORM-2592 Summary: The setOptions() method on RadioGroups and OptionLists in GoogleWeb Toolkit (GWT) fails if an array of numbers is passed as the option valuesarray.

Workaround: Use an array of strings to set the option values for an OptionList orRadioGroup control.

47


Key Information

FORM-2376 Summary: Specific to TIBCO Google Web Toolkit (GWT) forms. For imagecontrols, the settings of width and height do not have any effect on the renderedimage.

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 rulefor setting the size of an image control, for example: .TibcoForms .imageSizeimg {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 usewhatever CSS class name you want as long as it matches what is used in theCSS file.)

ClientsThis topic lists the known issues for Openspace and Workspace clients in TIBCO ActiveMatrix BPM3.1.0.

Openspace

Key Information

OS-2977 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: StatisticsDashboard is making an external call which will result in failures if you have noexternal web access.

Workaround: None.

OS-2973 Summary: Two new properties in the Openspace config.properties file havenot been documented. The two properties are:

● application.name. This is for internal use and should not be changed.

● max.page.size. This limits the page size when listing Case IDs in the CaseManagement gadget. The default value is 100.

Workaround: Please see the TIBCO Openspace Customization Guide for moreinformation about how to use the Openspace config.properties file.

OS-2962 Summary: If you are creating a work view in the accessible variant of Openspaceand you select a work item attribute as part of your sort criteria, the name of theattribute does not display. The work item attributes display as attribute1, attribute2and so on.

Workaround: None.

OS-2953 Summary: (only applies to Mozilla Firefox) In the Data Admin gadget, if you hoverover the Case model, the Details dialog displays. However, you are not able toscroll through it.

Workaround: Use another browser, for example, Chrome.

48


Key Information

OS-2951 Summary: Inactive Gadgets on the Preference Panel start as minimized whenactivated.

Workaround: Click the maximise icon to set the height larger than the minimizedstate.

OS-2946 Summary: (only applies to Mozilla Firefox and Chrome) If you have a multi-columnedform in Openspace and the first column consists of check boxes, the check boxesare not aligned correctly.

Workaround: Use another browser.

OS-2909 Summary: When you are in one of the Case Navigation pages in the CaseManagement gadget, the page navigation box does not display correctly. If thereare no further pages, the Next Page should be disabled and it is not.

Workaround: None.

OS-2908 Summary: The graphical audit trail in the Process Views gadget should show whena process instance is interrupted and resumed, for example, when using ad-hocactivities or event sub-processes.

Workaround: None.

OS-2940 Summary: (applies to Chrome only). After you have logged into Openspace, if youswitch to another tab, the options in top right-hand corner disappear, for example,Refresh, Maximize, Menu and so on.

Workaround: You can either use a different browser or, hover your mouse in thearea where those options are and the tool tips display allowing you to select theoption you need.

OS-2910 Summary: If you are in the Process Views tab in the Case Management gadget, and

● there are currently no process instances for the case ID currently selected and● a process instance that is going to be associated with the case ID is started

externally or by another user from the Process Views gadget

then you should be able to select Refresh and see the new process instance.However, an error displays and the process instance is not displayed.

Workaround: Select Refresh again and the process instance is now displayed onthe Process Views tab in the Case Management gadget.

OS-2894 Summary: In the Case Management gadget, if you try to view the contents of awork item associated with a case ID and you do not have the correct privileges, noerror displays to warn you and the Preview tab is empty. This may cause confusionif you have previously viewed work item data successfully in the Preview tabbecause you viewed a work item that you did have the correct privileges to.

Workaround: None.

49


Key Information

OS-2885 Summary: When using the Chinese language pack, some time zones are nottranslated correctly in the Calendar gadget.

Workaround: Upgrade to the latest language pack.

OS-2844 Summary: In the Audit tab on the Process Views gadget, a message start event in anon-interrupting event sub-process should be displayed with a dashed line insteadof a solid line.

Workaround: None.

OS-2777 Summary: If you configure any groups for the work items in your work item list,they are lost when you open a work item belonging to the group.

Workaround: None.

OS-2518 Summary: When using Internet Explorer Version 9 with Openspace, delays areexperienced when opening work items with forms.

Workaround: Use a later (supported) Internet Explorer version - check the TIBCOActiveMatrix BPM Installation Guide for supported versions OR use anothersupported browser version as listed in the installation guide.

OS-2438 Summary: In the Organization Browser, if you select some resources and thenchange the organization model version, the resources are deselected and you haveto select them again.

Workaround: None.

OS-2326 Summary: You cannot delete extension points using Openspace.

Workaround: You must delete extension points using the TIBCO ActiveMatrixBPM API.

OS-2140 Summary: You cannot contribute the sample Work View gadget supplied TIBCOActiveMatrix if your environment is enabled for SSL.

Workaround: The sample gadgets URL has to be on HTTP and not on HTTPS.

OS-1914 Summary: When you first open the Calendar gadget and click Edit next toSYSTEM, the Working Days and Exclusion tabs do not display.

Workaround: Click Back then click Edit again and the tabs display.

50


Workspace

Key Information

WS-1572 Summary: When the language is set to Korean or Chinese, the time is shown in a12-hour format in event views, whereas it is customary to show the time in a 24-hour format.

Workaround: You can specify that time values are shown in the 12- or 24-hourformat using the General Interface system locale files.

1. Locate and open the appropriate locale file for Korean or Chinese in the JSX\locale directory.

2. Locate the "time.24hour" record.

3. Set the value of the jsxtext attribute as appropriate:

● "true" - The time is shown in 24-hour format.● "false" - The time is shown in 12-hour format.

4. Save and close the locale file.

WS-1524 Summary: When Workspace is using a Microsoft SQL Server database, if youcreate a process view using the Include selected processes option and thenindividually select hundreds of process templates, a SQLServerException may bethrown that states Some part of your SQL statement is nested too deeply.

Workaround: None

WS-1348 Summary: An error is returned if you filter work items on strings that contain aliteral 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 thesimultaneous 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 chainedexecution).

Workspace cannot currently display multiple forms resulting from these parallelpageflows. If one is encountered in a WCC application (including the defaultWorkspace application), the following warning message is displayed: "Thebusiness service or work item has encountered a parallel pageflow which cannot bedisplayed in Workspace".

Workaround: Rework the process/pageflow to eliminate the parallel display ofmultiple forms, or create a custom BPM application using the available APIs thatcan handle pageflow branching (for information, see the TIBCO ActiveMatrix BPMDeveloper’s Guide).

51


PlatformThis topic lists the known issues for the TIBCO ActiveMatrix Platform in TIBCO ActiveMatrix BPM3.1.0.

Administrator

Key Summary/Workaround

TAP-13883 SummaryDuring undeployment, feature is disabled even if the component is inPreparing For Undeploy, and enable feature task fails.

Workaround Do not undeploy BDS user-apps and Process User-apps (that makes use ofBDS user-apps) together (that is, via multi-selecting both apps inAdministrator or via selecting the check-box that requests Administrator toundeploy them together).

TAP-9568 Summary Errors are seen in the Administrator UI when deploying a BPM userapplication when one of the nodes is not available.

Workaround The error dialog can be dismissed. The application will deploy and start fineon the running nodes.

TAP-9402 Summary When using TIBCO Business Studio to deploy a DAA that is dependant onanother DAA which is not in the deployed state results in errors such as:Follower application component urn:amx:BPMEnvironment/com.example.appa/APPAProcessFlow requires capability com.tibco.amf.sca.model.componenttype.impl.RequiredCapabilityImpl@7ee0f191 (id: com.tibco.bx.capability.implementation.bx, version: 1.0.0, type: factory) but the target application does not provide it.

Workaround Make sure the dependant DAA is deployed.

TAP-9380 Summary When a new node is added, the synchronization flag for the BPMapplication, amx.bpm.app, shows Out of Sync.

Workaround The application being out of sync won’t prevent or cause problems forapplication deployed to the new nodes.

To sync the BPM application, amx.bpm.app, select the application and clickDeploy.

52



TAP-9353 Summary If you deploy a BPM user application, start the instance and then deploy theapplication, the application will be in a partially running state. If you nowadd a new node to the BPM application, amx.bpm.app and click deploy, theBPM user application and the amx.bpm.app application are now in theConfigured_Failed state.

Workaround None.

TAP-9351 Summary When you change the nodes to which the BPM application, amx.bpm.app, isdistributed and if you remove a node and then redeploy, the application failsto start.

Workaround None.

TAP-9344 Summary ActiveMatrix BPM applications use the Product Distribution mode whereyou distribute to a target application amx.bpm.app and not to specific nodesin an environment. If you visit the Distribution tab for your application, youwill see the node based distribution for your application components. TheDistribution tab appears to allow editing of the node distribution for yourapplication components. However, you cannot change the componentdistribution this way while using Product Distribution mode. Modifying thenode distribution for components and then clicking Save does not actuallychange the distribution. It will simply revert to the original distribution. Thedistribution for components should've ideally been made as read-only.

Workaround None.

TAP-12891 Summary If you have replicated Administrators (say, Admin A and Admin B) and tryto download the logs from a node local to Admin B from Admin A (and viceversa), the download will fail with the following error:TIBCO-AMX-INFRA-002126:

error renaming <path>\retrievelog-root-1379033703875.zip.tmp to

<path>\retrievelog-root-1379033703875.zip

This does not occur if the node is on a remote host from either Administrator.

Workaround Download the logs from the Administrator that’s on the same host as thenode.

53



TAP-12881 Summary If you attempt to deploy a Mediation-based application to a node runningActiveMatrix version 3.2.0 (from an Administrator running ActiveMatrixversion 3.3.0), the Mediation implementation type will not be auto-provisioned. This occurs because of a failure to provision gXML.

Workaround If you encounter this issue, do the following in the Administrator UI:

1. Go to Infrastructure > Nodes > Configuration > Features and select therelevant node to see it’s details.

2. Select all the features that have a status of Marked for Install (there shouldbe four). Remove them, then click Save. You do not need to click Apply atthis point.

3. Add the following features (they should be available from the drop-downlist; if Mediation IT version 3.5 is installed, they will not be available):

● TIBCO TIBCOxml version 5.51.6.V00

● TIBCO gXML version 1.0.4.V00

● TIBCO ActiveMatrix Mediation IT version 3.4.0.V00

Click Save, then click Apply with Resolve. The result Changefeatures Successful should display.

4. Deploy the application that triggered the auto-provisioning of MediationIT initially. The deployment should be successful.

Alternatively, you can perform steps 2-4 preventively.

TAP-12878 Summary If you import a resource template into an upgraded user application that didnot previously contain a resource template (that is, if no resource templateshad previously been imported into the application), the scope of the importedresource template will automatically be set to Global, rather than Application.This occurs even if you specify Application scope in the CLI.

Workaround After the resource template is imported (to Global scope), you change itsscope as required (to Application scope, for example) in the ActiveMatrixAdministrator UI. To do this:

1. Go to Shared Objects > Resource Templates .

2. Select the imported resource template.

3. Click Change Scope, and change the scope to the Application orEnvironment level as desired.

54



TAP-12860 Summary If you have a main process and a subprocess application and one or moredependent main process applications deployed in ActiveMatrix version 3.1.5(and any ActiveMatrix BPM version between 1.3.0 and 2.1.0), then upgradethe BPM platform version to BPM 2.2.0 (ActiveMatrix 3.3.0), andsubsequently attempt to upgrade the subprocess, you will see a warningsimilar to the following example:TIBCO-AMX-ADMIN-012430: Provided capability 'com.example.my.subprocess.pe.capability' provided by component 'MySubAppProcessFlow' cannot be removed. It is being used by the following components:Component 'MyMainAppProcessFlow' from application 'com.example.my.mainapp.process

This warning is issued erroneously and can be safely ignored. The subprocesswill be upgraded successfully and the main processes will run fine, providedthe subprocess maintains the same major version number as before.

Workaround None.

TAP-12858 Summary The logging configuration of a node, host, or application (which is stored inthe node, host, or application’s log4j.xml; for example, node-log4j.xml)may enter into an inconsistent state if the node, host, or application uses aJMS appender that is configured with an SSL-enabled EMS server. In thiscase, the logging configuration uses an HTTP URL to refer to a keystore that’shosted on the Administrator. This HTTP URL is the internal HTTP connectorURL of the Administrator.

Changing the configuration of the internal HTTP connector (for example, toenable SSL or change the port number) causes the URL configured in thelogging configuration (log4j.xml) to become invalid or out of synch. Thelogging configuration of each affected node, host, or application needs to beupdated or it will fail to connect to EMS.

Currently this is not done automatically.

Workaround You must manually save and apply the logging configuration for each node,host, or application that uses a JMS appender. To do this:

1. In the Administrator UI, go to the logging configuration for the node, host,or application that’s in the situation described above.

2. Change a value in the logging configuration that makes the node, host, orapplication go out of synch.

3. Click Save.

4. Click Apply. This pushes the new logging configuration, with a newHTTP URL, to the node, host, or application.

55



TAP-12810 Summary If ActiveMatrix administrator is replicated (or running in a replicated setup),the ActiveMatrix Service Performance Manager probe should be enabled onall replicated Administrator instances while you enable the SPM probe.

Workaround None.

TAP-12738 Summary If you delete a binding in the ActiveMatrix Administrator UI, that bindingwill still be visible in the SPM Dashboard with a Down status. This occursbecause the Delete notification for the ActiveMatrix binding component is notbeing emitted.

Workaround None.

TAP-12714 Summary ActiveMatrix Administrator does not properly undeploy applications withmissing feature dependencies.

Workaround To avoid this issue, go to Node > Configuration > Features and remove thefeature with Marked for Install and a blank value for Type. You should beable to undeploy the application with no issues.

TAP-12702 Summary If you use TIBCO Configuration Tool to edit Administrator databasesettings, the following harmless error may appear in SystemNode.log: Couldnot open Hibernate Session for transaction.

Workaround None.

56



TAP-12426 Summary When upgrading an SSL-enabled TIBCO Host (and no nodes or applications)to this release version, shared resource instances may enter into a Failed state.

If this occurs, the ActiveMatrix Administrator UI displays an error messagesimilar to the following example:Waiting for following resource instance dependencies to be installed: Failed to create ConnectionFactory javax.sql.DataSource. Reason TIBCO-AMX-SR-JDBC-013102: Unable to get user credentials from java:DataSource_subjectJndiName due to exception:: java.lang.RuntimeException: TIBCO-AMX-SR-JDBC-013102: Unable to get user credentials from java:DataSource_subjectJndiName due to exception: com.tibco.trinity.runtime.core.provider.identity.trust.TrustRuntimeException: javax.security.auth.login.FailedLoginException:

Workaround If you encounter this issue, upgrade the nodes residing on the affectedTIBCO Host. Upgrading the nodes will restart the nodes. The nodes willrevert to a normal state after being restarted.

TAP-12319 Summary When deploying an application, ActiveMatrix Administrator automaticallyinstalls resource instances if there are resource templates with scope to theapplication. If the resource template installation fails, then applicationdeployment will also fail. For example, if the HTTP connector has a portconflict, it fails to start.

Workaround For HTTP Connector port conflicts use substitution variables to assigndifferent port numbers for each node to avoid port conflicts. Then uninstallthe application and redeploy it.

TAP-12087 Summary Making changes to the configuration of a JDBC service resource templatethat is a dependency for a running application may cause that application toenter a Stopped state.

Workaround Manually restart the stopped application.

57



TAP-11318 Summary If you use Mozilla Firefox as a web browser, TIBCO ActiveMatrixAdministrator may display a blank page when opened.

Workaround To avoid this issue:

1. In the Firefox address bar, enter about:config

2. Click "I'll be careful, I promise!"

3. In the search field, enter javascript.options.ion.content

4. Set the Value for javascript.options.ion.content to false

5. Restart Firefox in Safe Mode. See the following URL for more informationabout starting Firefox in Safe Mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode#w_how-to-start-firefox-in-safe-mode

TAP-10854 Summary In an upgraded environment product applications are not auto-provisionedby default.

Workaround Either manually deploy the product applications or enable auto-provisioning for the environment and create a System folder for theenvironment.

If the product application is present in the environment but missing from thenode, move the product application to the System folder.

TAP-10830 Summary When wiring a reference to a service in the same application that has a SOAPbinding using an HTTP Connector that does not exist results in the followingexceptionError generating the WSDL for binding SOAPService_Binding1, Caused by: Could not find resource instance with name httpConnector when generating WSDL for binding SOAPService_Binding1 on service NewService

Workaround Create the HTTP Connector before creating the application.

58



TAP-10800 Summary When creating an Administrator server with an Oracle database thefollowing error messages are seen in the SystemNode log files:SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AdmnCnfig_sttsNtifictinTrnsprt on "ADMINCONFIG" ("NTFCTNTRNSPRT_STTSNTFCTNTRNS_D") SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AMXdminsrPrfrncs_prvisnvslctin on "AMXADMINUSERPREFERENCES" ("PRVISNVSLCTIN_PRVISNVSLCTIN_ID") SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object......SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index ApplicationFolder_childFolders on "APPLICATIONFOLDER" ("APPLICATIONFOLDER_PARENT_E_ID") SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-01408: such column list already indexed

Workaround These errors can be safely ignored as the indexes are created.

TAP-10767 Summary HTTP Connector resource instances that are referenced by properties whosenames are not specific, such as HttpInboundConnectionConfig orhttpConnector, are not recognized by Administrator as HTTP Connectorswhile displaying information. As a result these HTTP Connectors are notdisplayed in the Administrator UI as dependencies where expected.

Also, you can delete any such HTTP Connector even when it has dependentapplications.

Workaround Use property names such as HttpInboundConnectionConfig orhttpConnect to refer to HTTP Connectors resource instances. Additionallywhen deleting a HTTP Connector resource instances manually check whetherother applications are dependent on it.

59



TAP-10751 Summary Executing the scripts generated by the DDL Script Generator for MicrosoftSQL Server displays errors reporting a failure to create foreign keyconstraints.

Also, even if the generated scripts are not used, error messages are seen in theSystemNode log file logged in SystemNode.log regarding failure to createforeign key constraints.

Workaround None. These errors can be ignored as a failure to create foreign keyconstraints does not impact product functionality.

TAP-10663

DSS-527Summary Heterogeneous environments with mixed JREs are not supported. Sun JRE isnot compatible with IBM JRE when it comes to storing secret keys in a Javakeystore. This causes a problem when the Administrator server running onSun JRE stores a username and password in its global identity keystore and ahost and node running on IBM JRE attempts to access that username andpassword. The reverse, Administrator on IBM JRE and host and node on SunJRE would have the same problem.

Workaround Ensure that Administrator, TIBCO Host instances, and nodes are all usingJREs provided by the same vendor.

TAP-7784 Summary After creating and starting a node, if you try to stop and uninstall the nodewhen its runtime state is Running and the Action History state is In Progress,the node will fail to get uninstalled.

Workaround Wait for the Action History state to change from the In Progress state to onethat matches the chosen action before selecting another action for the node.

TAP-7644 Summary You may see the following error message when undeploying an application[ERROR] com.tibco.amf.admin.server.axis2.RPCMessageReceiver - Error occured in Administrator... about to throw AxisFault for this exception

Workaround Refresh the browser. This error message can be safely ignored.

60



TAP-7571 Summary Users who have permissions only to view an application and anenvironment but do not have permissions to view a node are not able to seethe list of selected nodes when distributing an application.

Workaround Permissions to view the node have to be explicitly granted by a superuser.

TAP-7423 Summary You may see an Errors in dashboard dialog box when using the Dashboard.

Workaround Click OK to proceed using the Dashboard. This error message can be safelyignored.

TAP-6584 Summary When the extended monitoring is enabled the two new periodic windows(24 hours and 7 days) do not show on some Dashboard tabs.

Workaround Refresh the browser.

TAP-5653 Summary Updating the value of a substitution variable for the Timeout property in aJMS or SOAP/JMS binding in a deployed application does not take effect afterthe application is redeployed.

Workaround .Undeploy and deploy the application.

TAP-4890 Summary In the dashboards, a text filter is ignored when you maximize or minimize agadget.

Workaround Re-enter the text filter.

TAP-4645 Summary In the Dashboards > Infrastructure screens, resource instances cannot befiltered by promoted reference or promoted service.

Workaround In the Application Screen, check properties of the reference or servicebindings.

61



TAP-3698 Summary On Windows, the folder containing a TIBCO Host instance cannot be moved,copied, or deleted when the RuntimeWorkArea file name length is longerthan 255. This occurs if you select the default value for CONFIG_FOLDER whenrunning TIBCO Configuration Tool.

Workaround Delete the folder using rmdir /s /q.

TAP-1669 Summary Deploying an application fails when the application name contains thefollowing characters: \, /, :, *, ?, ", <, >,|, %, #, &, (, ), the comma or whitespace.

Workaround Clear the cache of your browser.

PER-583 Summary For bundled policies added in this release, if the resource instance(s) used inthe policy is reinstalled then policy enforcement will fail.

Workaround Redeploy the application after reinstalling the resource instance(s).

PER-49 Summary When configuring an LDAP Authentication resource template inAdministrator, the option to generate SAML 1.1 assertion is not supported byplatform policies.

Workaround When configuring an LDAP Authentication resource template, accept thedefault setting to generate SAML 2.0 tokens.

MCR-1823

TAP-10602Summary The value for the uptime displayed in the infrastructure dashboard screensare accounted from the time a request is made to the application by invokingthe endpoint or through an internal call from another application.

If an application is deployed and not used, the value for uptime will be 0.

Summary None.

62



MCR-1422 Summary If nodes are restarted when the SystemNode is down, the Uptime and SinceStarted statistics are not reset.

Workaround Either make sure that the system node is running using admin replication orrestart the applications for which incorrect statistics are seen.

MCR-1350 Summary The number of components reported for a given node in the EnterpriseGraphical View includes components that belong to the ActiveMatrixPlatform Application. The Dashboard component count does not includethese components.

Workaround None

MCR-1226 Summary The Endpoint, Service, and References tabs display an incorrect value forAvg Comp Process Time when extended monitoring is enabled. The valuedisplayed is Req Comp Time.

Workaround The correct average component processing time is available in theComponents and Applications tabs.

MCR-1205 Summary If the TIBCO Host is shutdown while the Dashboard is running, thefollowing error message is seen in the SystemNode log files:[ERROR] org.apache.axis2.engine.AxisEngine - bean:name=govObjFilterServiceMBean

Workaround None. This error can be safely ignored.

MCR-1204 Summary Stopping the TIBCO Host instance occasionally causes exceptions to bethrown in the log file. During a graceful stop of TibcoHost instance there maybe some exceptions in the log file with the root cause "Caused by:java.lang.RuntimeException: Statistics aggregator is closing down, rollingback transaction".

Workaround Ignore the error.

63



MCR-1162 Summary Statistics for Web Application components do not display in the dashboard.

Workaround None.

MCR-876 Summary Status value is "Unknown" and uptime is empty when the same applicationis deployed on two nodes across environments.

Workaround Change the application name during deployment. It must be unique for anenterprise for dashboard to show correct status and uptime.

MCR-800 Summary When a component reference is promoted, component reference metricsshow zero values. All metrics are shown on the promoted reference andreference endpoint.

Workaround View metrics on the promoted reference.

MCR-753 Summary In the Dashboards > Infrastructure screens the application request countincludes requests counts from all services promoted to application level. Inaddition, it incorrectly includes reference invocations count from allreferences promoted to application level.

Workaround None.

MCR-521 Summary If a node is stopped or started several times while SystemNode is down, thelast stop or start time of SystemNode is used to calculate the node’s uptimepercentage. Other stops and starts are missed and not used in uptimecalculation.

Workaround Configure the Administrator server in fault tolerant mode.

AMX-10828 Summary If your BPM application refers to a OM project and if changes are made tothe OM project that break backward compatibility, errors are generated whenredeploying the BPM application.

Workaround Downgrade the OM project to the previous version.

64



WSBT-888 Summary Substitution variables for services with SOAP binding are not supported forany fields. Substitution variables for references with SOAP binding are onlysupported for the Endpoint URI field. See Services and References inAdministration for more information about substitution variables.

Workaround None.

WSBT-881 Summary Policies and policy sets cannot be added, edited, or deleted via theActiveMatrix Administrator UI. Policy set properties can be viewed but notadded, edited, or deleted.

Workaround Edit policy sets and properties in Business Studio.

SVCP-86

SVCP-84Summary The TIBCOActiveMatrix Service Performance probe on the Administratornode does not receive self-shutdown notifications sent from TIBCO Host. Thisoccurs because the Service Performance Manager probe component on theAdministrator node responsible for such communication shuts down before itcan send the notification.

Workaround None.

SVCP-74 Summary ActiveMatrix lifecycle events of Composite reference endpoints are notpublished correctly if two or more endpoints shares same WSDL portType.

Workaround None.

SVCP-55 Summary The ActiveMatrix Service Performance Manager probe does not emitmetrics-related data to SPM for applications that use pure JMS binding.

Workaround None.

SVCP-54 Summary The ActiveMatrix Service Performance Manager probe does not emitmetrics-related data to SPM for applications that use virtualization binding.

Workaround None.

65


Installer


INST-164 Summary The TIBCO Universal Installer does not display the products to be installedcorrectly.

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 andattempt to replicate the upgraded configuration, deploying the replicatedconfiguration 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 byTIBCO Business Studio and TIBCO Configuration Tool. In a suite installationscenario, if you unzip all product archives into the same directory, you mightoverwrite the 3.1.5 installer with a 3.1.2 installer. The 3.1.2 installer won'tdownload the required assemblies, which will lead to failure of TIBCOBusiness Studio and TIBCO Configuration Tool.

Workaround When you unzip all products in the same directory while preparing for asuite install, make sure you preserve the installer binary from the most recentproduct installation. When you run the installation, the version of the 3.1.5installer in the About dialog is 2.9.4.

Runtime


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 thoughthe service consumer still requires the service provider.

Workaround Separate the service consumer and the service provider so that they’re both intwo separate user applications.

66



AMRP-4744 Summary If you upgrade ActiveMatrix BPM to release 2.2.0 and ActiveMatrix to release3.3.0, and upgrade a pre-existing user application so that it’s a web serviceimplementation with REST enabled, you may see exceptions similar to thefollowing in the logs during the reply message event although the response issuccessfully 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\bundle28 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 toActiveMatrix release 3.3.0 from release 3.1.5 (or previous releases) orActiveMatrix 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 executingtibcohost.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 ActiveMatrixAdministrator Server, entering the full IPv6 address of the local host in theNetwork Adapter field may result in exceptions similar to the followingexample: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 IPv6address.

67



AMRP-4639

DSS-811Summary The default JSSE provider for Oracle's Java 7 has introduced a bug with theDiffie Hellman Ephemeral (DHE) key exchange. (See the description in Oracle’sbug database for more information: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8013059) Establishing ciphers likeTLS_DHE_RSA_WITH_AES_128_CBC_SHA sometimes fails and gives the errormessage Received fatal alert: bad_record_mac. By default, SSLconnections with TIBCO EMS Server prefer the stream cipher RC4. You canoverwrite this behavior by explicitly choosing the ciphers either in SSLClient RTor in the EMS Server.

Workaround By default, no workaround is needed. If you do choose explicit ciphers, avoidthe DHE ciphers so that you do not run into this occasional Java 7 bug.Unaffected ciphers include TLS_RSA_WITH_AES_128_CBC_SHA, amongstothers.

AMRP-4445 Summary If you create and install an HTTPConnector resource instance for a runtimenode and assign it a port that is also used as an external or internal HTTP port ofSystemNode, users will encounter a 404 error when attempting to log in toTIBCO ActiveMatrix Administrator after the TIBCO Host instance has beenrestarted.

Workaround To avoid this issue:

1. Stop the TIBCO Host instance.

2. Go to \tibcohost\tibco_host_instance_name\data_3.2.x\host\plugins

3. Delete, move (or backup with a different name) the plugin whose name takesthe 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 aport that is not being used by an existing instance such as SystemNode or aruntime node.

AMRP-4013 Summary Acceptor threads for HTTP connectors may consume excessive amounts ofCPU. The processing performance of any node that uses an HTTP connectorexperiencing this issue may be affected when asynchronous IO is involved.

Workaround Edit the HTTP Connector Resource Template to use blocking IO. See thechapter Resource Templates in Administration for more information.

68



AMRP-3842 Summary Can't log into Workspace if trying to access it from a node that is running on amachine different than the one on which the Enterprise Message Service serveris running and the Enterprise Message Service server restarts.

Workaround Restart the node.

AMRP-3828 Summary If you enter incorrect configuration data for a JDBC resource, it is not verifiedby any tools during resource creation or installation and the runtime reports afailure when an application tries to access the resource.

Workaround Ensure that the configuration supplied to the JDBC resource template is correct.

AMRP-3823 Summary Status is not updated in Administrator for when an application running onBPMNode experiences a database connection failure.

Workaround If a component is failing, try restarting the component.

AMRP-3788 Summary The LDAP resource template pool properties are not used when initializing theconnection pool.

Workaround Configuring the connection pool using system properties specified for thetarget 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

AMRP-3721 Summary The LDAP shared resource does not reconnect automatically to its associatedLDAP server.

Workaround Reinstall the LDAP shared resource instance and then restart all dependentapplications. Or, restart the node.

69



AMX-14346 Summary Suite installation of ActiveMatrix Service Grid 3.3.0 and ActiveMatrix BPM 2.2.0fails with the following error: More than one active 'Finish' task hasbeen defined.

Workaround Do not install ActiveMatrix BPM and ActiveMatrix Service Grid at the sametime using the Suite Installer.

AMX-14345 Summary Upgrading the second system node in a replicated Administrator setup can failwith 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 theSystemNode upgrade) may fail due a fatal EMS connection error described inKnown Issue DSS-811. This is caused because of a Java 7 bug, related toEphemeral Diffie Hellman based ciphers, documented in Oracle's bug database.

Workaround The failure is only seen during the upgrade process, and not during normalruntime operation, hence a workaround is required only in the former scenario.

If upgrading process fails, apply this workaround and then re-run the upgradescript for the SystemNode.

Update the EMS server configuration to exclude ciphers using Ephemeral DiffieHellman. 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.

70



AMX-14310

DSS-817Summary ActiveMatrix release 3.3.0 packages IBM JRE 1.7.0 SR2. If you are runningActiveMatrix on an AIX platform and install Unlimited Jurisdiction Policy (UJP)files, you may encounter errors.

Workaround If you encounter errors, you must install the appropriate version of the UJPfiles for that build of the JRE.

Errors similar to the following example indicate that the version of the UJP filesis 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 itsMirror 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 Server2012, you must set the IP and hostname of both the primary and secondarydatabase servers in the hosts file. The location of the hosts file depends on theoperating system:

● Windows: ROOT_DIR\system32\drivers\etc\hosts

● UNIX/Linux: /etc/hosts

For example, you have two database servers. The primary server's IP is192.167.71.42 and its hostname is amx-db42; the secondary server's IP is192.167.71.60 and its hostname is amx-db60. You would provide thefollowing 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 toboth servers and allows for seamless switching between them using SQLstatements, you must add the following entries to the hosts file:192.167.71.42 amx-db42192.167.71.60 amx-db60

71



AMX-11984

TAP-12831Summary You are not able to replicate the Administrator server after upgrading from anearlier 3.1.x version.

Workaround Follow these before attempting the replication procedure:

1. Import basic_cli.xml in sharedWorkFolder_build.xml.

Modify the line<import file="${admin.samples.directory}/admin-scripts-base.xml"/> to <import file=”basic_cli.xml”/>

2. Edit sharedWorkFolder_data.xml

a. Remove the ApplicationFolder element.

b. Change the artifact server app name fromcom.tibco.amx.platform.artifactserver toamx.artifactserver.app.

c. Change the name of the internal HTTP connector name in thesubstitution variable element from TIBCO ActiveMatrix InternalHTTP Connector Resource totibco.admin.http.connector.internal.

AMX-11980 Summary (Windows only) When executing the upgrade-tibcohost script, you have to usethe same case (either uppercase or lowercase) to define -Dtibco.config.mgmt.home that you had used earlier. The original path can bediscovered by examining the value of propertyhpa.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 nodeapplications with policies applied on them, those policies are not enforced afterupgrade.

Workaround First undeploy and then redeploy these applications after upgrading all systemnodes.

72



AMX-10757 Summary After shutting down and restarting a database accessed by a JDBC resourceinstance, Workspace throws an error.

Workaround Log into Workspace again.

DSS-813 Summary While upgrading to ActiveMatrix release 3.3.0, you may see benign errorssimilar 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 isrequired.

Workaround None.

MCR-2002 Summary If you have configured Microsoft SQL Server 2012 as a database forAdministrator, invoking a custom DAA may result in harmless exceptionssimilar 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(SQLServerPreparedStatement.java:404) ... 44 more

Workaround None.

73



MCR-1995 Summary If you have configured IBM DB2 as an external database, you may see harmlessexceptions 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 WindowRetrying 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 Hawk ActiveMatrix Plug-in


HKAM-266 Summary If the ActiveMatrix Administrator server or TIBCO Host instance isconfigured to use SSL-enabled Enterprise Message Service on AIX platform,and Hawk 5.0 is installed, then starting Hawk Agent fails giving an error.

Workaround Use Hawk 4.9 instead of Hawk 5.0.

HKAM-264 Summary Users cannot change the timeout of method invocation for Custommicroagent.

Workaround None.

HKAM-256 Summary TIBCO Hawk cannot use TIBCO Data Grid for communicating betweenHawk Agent and ActiveMatrix HMA.

Workaround Use other transport modes, such as TIBCO Rendezvous (RV) or TIBCOEnterprise Message Service.

74



HKAM-253 Summary Hawk Display shows multiple entries for node Service microagent whenrulabases for TIBCO Host or nodes are invoked after the TIBCO Host or nodecrash.

Workaround Click Done, and again open the microagent. Alternatively, restart HawkDisplay.

HKAM-251 Summary Continuous error messages are seen in the hawk.log file after startingtibhawkagent.exe on HAWK 5.0. Hawk 5.0 is unable to runpowershell.exe used in TIBCO Host rulebase.

Workaround Prefix powershell.exe in the rulebase of the TIBCO Host with the absolutepath of powershell.exe.

HKAM-250 Summary When using Hawk 5.0, logs are not generated in the CONFIG_HOME/hkam/<host_instance_name>/logs folder. The Hawk Agent shows errors relatedto slf4j in the Hawk logs.

Workaround Remove the slf4j jars and jars with different versions of slf4j from theagent classpath.

HKAM-249 Summary The Stop Reason and Reason Code arguments are not updated for theonNodeEvent method after calling stopNode.

Workaround None.

HKAM-242 Summary Hawk 5.0 cannot find Windows PowerShell.

Workaround Prefix powershell.exe in the rulebase of the TIBCO Host with the absolutepath of powershell.exe.

75



HKAM-237 Summary On creating a node in the ActiveMatrix Administrator web interface, itsrulabase is created in the CONFIG_HOME/hkam/<host_instance_name>/rulebases folder. If the node is deleted, the HAWK.log file continuouslyproduces errors.

Workaround Manualy delete the rulebase to avoid error entries in the HAWK.log file.

HKAM-193 Summary Hawk ActiveMatrix Plug-in displays some ActiveMatrix applications orcomponents in runtime state as uninstalled, but ActiveMatrix Administratoror nodeutil do not show these applications.

Workaround Restart Hawk Agent to clear the cache.

76


Date post:	06-Aug-2020
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times