TIB Bwse 5.10.0 Relnotes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes
Software Release 5.10.0 August 2012
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator, TIBCO Enterprise Message Service, TIBCO Designer Add-in for TIBCO Business Studio, TIBCO ActiveMatrix Service Grid, TIBCO ActiveMatrix Business Studio, and TIBCO Hawk are either registered trademarks or trademarks of 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 their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright 2007-2012 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii viii viii viii
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.9.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.6.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.6.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 5.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 2 2 3 3 4 5 5 5 6 6 7 7
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Release 5.9.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Release 5.9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Release 5.9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Release 5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 TIBCO ActiveMatrix Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Migrating Projects from 5.8.x into 5.9.2, 5.9.3, or 5.10.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
iv
| Contents
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Appendix A Configuring Adapter Projects in ActiveMatrix Design-time . . . . . . . . . . . . . . . . . 88
|v
Preface
TIBCO ActiveMatrix BusinessWorks Service Engine is a gateway for TIBCO ActiveMatrix BusinessWorks to the Service Oriented Architecture (SOA) world. ActiveMatrix BusinessWorks Service Engine provides an ActiveMatrix container to deploy ActiveMatrixTM BusinessWorks projects using the TIBCO ActiveMatrix Administrator.
Topics
Typographical Conventions, page vi Connecting with TIBCO Resources, page viii
vi
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention
TIBCO_HOME ENV_HOME
Use Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco. Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco. TIBCO ActiveMatrix BusinessWorks Service Engine installs into a directory within <TIBCO_HOME>. This directory is referenced in documentation as BWSE_HOME. The default value of BWSE_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\bwse\5.10.
BWSE_HOME
code font
Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process.
bold code font
Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
Preface vii
Table 1 General Typographical Conventions (Contd) Convention

italic font
Use Italic font is used in the following ways: To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts. To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName
Key combinations
Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.
viii
| Connecting with TIBCO Resources

Connecting with TIBCO Resources
How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.
How to Access TIBCO Documentation

You can access TIBCO documentation here: http://docs.tibco.com
How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support as follows: For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: http://www.tibco.com/services/support If you already have a valid maintenance or support contract, visit this site: https://support.tibco.com Entry to this site requires a user name and password. If you do not have a user name, you can request one.
|1
Release Notes
Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.
Topics
New Features, page 2 Changes in Functionality, page 9 Deprecated and Removed Features, page 13 Migration and Compatibility, page 14 Closed Issues, page 18 Known Issues, page 56 Limitations, page 85
Release Notes
New Features
BusinessWorks as a Service Engine has been introduced from the version 5.6.0 of the product. This section lists the features of this product.
Release 5.10
This product version bundles TIBCO ActiveMatrix version 3.2.0. It supports TIBCO DesignerTM Add-in for TIBCO Business StudioTM version 1.4.0. Provides the following new command-line interface tasks:
sds.ear2daa
task for creating DAA for BusinessWorks EAR file task to extract PI.xml and engine
sds.editBWDeploymentConfig
properties file from DAA Provides ability to access message context information such as Correlation ID, Context ID, and Parent Context ID from the BWSE Process flow. TIBCO ActiveMatrix Administrator CLI allows you to edit the BWSE component Engine Properties using the properties file. New engine property Engine.ShutdownOnAllStartupErrors detects the engine startup and activation errors. The component displays the state as Start Failed when there are any startup or activation errors in BW Engine or when the engine stops. Support for delayed Shutdown added to BusinessWorks Service Engine using the following properties as BWSE Component Engine Property:
waitforCheckpoints maxDelay
Release 5.9.3
This product version bundles TIBCO ActiveMatrix version 3.1.5. It supports TIBCO Designer Add-in for TIBCO Business Studio version 1.3.2.
Release 5.9.2
TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.2 now supports ActiveMatrix global transaction. To participate in the AMX Global
New Features 3
Transaction, you need to configure Global Transaction Intent on the BWSE Component and add the engine property bw.plugin.transaction.xa.lock.connection on each BWSE Component before deploying the application DAA from TIBCO ActiveMatrix Administrator. Set the property value to true. The scripted command-line interface (CLI) to create a DAA works only if the BWSE component is in sync with the associated TIBCO BusinessWorks project. A new BusinessWorks CLI extension task for scripted packaging is created that ensures initialization of BusinessWorks projects before SOA projects. To use this task, the syntax is: where %projectName% must be a valid project name.
<sds.initBWProject bwProjectName="%projectName%"/>
Release 5.9.1
No new features are introduced in this release.
Release 5.9.0
Design The design time now allows tighter integration with TIBCO Designer Add-in for TIBCO Business Studio and makes BWSE component more inline with other ActiveMatrix components. It allows you to: Associate a BWSE component to a Service Resource which is the implementation resource. Selectively expose services, references and global variables that are already implemented in BusinessWorks through the BWSE component. Add new services, references, and properties through BWSE component which in turn creates dummy implementations in the BusinessWorks design time project. Navigate from a BusinessWorks Service or Partner exposed in BWSE component to the BusinessWorks process implementing it. Add context parameters and intents to Service resource and then subsequently expose those parameters to BWSE component. Convert EAR files into Distributed Application Archives (DAAs) on command-line using the EAR2DAA utility.
Release Notes
Expose BusinessWorks Global variables into SOA project as ActiveMatrix properties using a BusinessWorks Service resource. When the Service resource is associated with a BWSE component, it exposes these global variables as properties in the component. Test the composite application in Rapid Application Development (RAD) before the actual deployment. Support TIBCO provided TM for distributed transactions in addition to configuring JDBC and JMS libraries. Shells are provided to provision and configure the database drivers and JMS client libraries that are used by ActiveMatrix BusinessWorks Service Engine.
Runtime During run time, for BWSE application DAA to be deployed on a node, only the BWSE implementation types (BWSE IT DAA) need to be deployed on that node from TIBCO ActiveMatrix Administrator. Administration While configuring a BWSE component for deployment, you can now specify substitution variables as values for BWSE Engine properties. You can also add new engine properties at deployment time without modifying the DAA. Deployment of DAA is possible through command-line. CLI extractor tool can be used to generate the deployment configuration templates for BWSE components inside the DAA. You can then use these templates to add BusinessWorks properties to a BWSE component through CLI. In common logging, logging can be enabled at ActiveMatrix application as well as at the node level. Added transaction support for SAML and WS-addressing. TIBCO ActiveMatrix Administrator Infrastructure dashboard has a new look and feel. You can select Dashboards > Infrastructure > Components to see list of all deployed components. When you double-click an ActiveMatrix BusinessWorks Service Engine component, all the component instances of the selected component are displayed in a table. You can then double-click the BWSE component instance to see the details of BusinessWorks Processes running on that instance.
Release 5.8.1
There are no new features added for this release.
New Features 5
Release 5.8
Flow Control and Message Loss A new property for clientACK and Redelivery has been introduced. Redelivery property depends on the clientACK property, hence its value is used only when clientACK property is set to 'true'. clientACK at the Component level depends on the TIBCO ActiveMatrix provider thread pool which is set per component. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details. SOAP Fault Sub-Element Propagation This feature allows the SOAP Fault sub-elements - faultcode, faultstring, and faultactor to be specified on SOAP faults generated by TIBCO ActiveMatrix BusinessWorks. With this mechanism the SOAP faults generated within the TIBCO ActiveMatrix Business Works process can be propagated to the framework in which it is embedded. To configure and propagate the SOAP fault context, the SOAP endpoint configuration user interface for the service and partner link configuration resources are enhanced to include the configuration of fault context. See section SOAP Fault Sub-Element Propagation in TIBCO ActiveMatrix BusinessWorks Process Design Guide for details. Platform Support The following is supported in this release: Software Support This release supports JRE 1.6. Sun Solaris 10 on x86 32 bit AIX 6.1 POWER 64 bit
Release 5.7.2
This release does not introduce any new features.
Release 5.7.1
This release does not introduce any new features.
Release Notes
Release 5.7
ActiveMatrix BusinessWorks Service Engine Design Time Composite Editor This feature allows a tighter integration with the new Eclipse based ActiveMatrix BusinessWorks design time. It provides features like tying a ActiveMatrix BusinessWorks Service Engine component to a ActiveMatrix BusinessWorks project. The changes done in the ActiveMatrix BusinessWorks project are automatically reflected on the BWSE component in your SOA Project. It allows to: Selectively expose services and references that are already implemented in ActiveMatrix BusinessWorks through the ActiveMatrix BusinessWorks Service Engine component. Add new services and references through ActiveMatrix BusinessWorks Service Engine component which in turn create dummy implementations in the ActiveMatrix BusinessWorks design time project. Provide easy cross navigation functionality from a particular port type exposed in ActiveMatrix BusinessWorks Service Engine component to the ActiveMatrix BusinessWorks process by implementing it.
Security Context propagation ActiveMatrix BusinessWorks Service Engine 5.7.0 with Security Context Propagation allows you to: Expose the security context propagated between Matrix components. Propagate the same security context, when the implementing process ends up consuming services from the Matrix bus.
Release 5.6.4
Selective Enabling and Disabling of BW Endpoints ActiveMatrix BusinessWorks Service Engine now allows you to selectively disable or enable the wired BW service endpoints. This feature also allows you to disable all the wired service endpoints. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details.
New Features 7
Reload EAR An EAR file tied to a BWSE component can now be reloaded whenever the EAR file is updated. A new button Reload EAR has been added to the Implementation tab of the BWSE component. You can either use this button or the right-click menu to reload the updated EAR file. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details.
Release 5.6.3
Platform Support AIX 5 for POWER Version 5.3 on 64 bit platform is now supported.
Release 5.6.0
ActiveMatrix BusinessWorks Runs as a Container in ActiveMatrix TIBCO ActiveMatrix BusinessWorks Service Engine provides the BusinessWorks Container in the ActiveMatrix environment. You can create service assemblies for the ActiveMatrix BusinessWorks projects, and then deploy and run these service assemblies in the BusinessWorks Container using TIBCO ActiveMatrix Administrator. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details. Provide ActiveMatrix BusinessWorks Services to Other ActiveMatrix Components ActiveMatrix BusinessWorks Service Engine allows other ActiveMatrix components to discover and invoke ActiveMatrix BusinessWorks services. To provide services to other ActiveMatrix components, the ActiveMatrix BusinessWorks project must contain at least one Service resource. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details. Consume Services Provided by Other ActiveMatrix Components ActiveMatrix BusinessWorks Service Engine allows ActiveMatrix BusinessWorks to consume services provided by other components in the ActiveMatrix platform. In order to consume services provided by ActiveMatrix components, the ActiveMatrix BusinessWorks project must contain partner definitions. The Invoke Partner activity can be used to invoke external services. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details.
Release Notes
Policy Management for ActiveMatrix BusinessWorks Services You can apply policies for ActiveMatrix BusinessWorks services using TIBCO ActiveMatrix Policy Manager. Policy management for any external or ActiveMatrix service that is invoked by the ActiveMatrix BusinessWorks service can be done using ActiveMatrix Policy Manager. See TIBCO ActiveMatrix Policy Manager documentation for details. Monitoring and Managing ActiveMatrix BusinessWorks Services ActiveMatrix BusinessWorks projects running in the BusinessWorks Container can be monitored using ActiveMatrix Administrator. Also, the ActiveMatrix BusinessWorks engine properties and global variables can be specified at deployment time. You can benefit from a single deployment and life cycle management of the BWSE components using the ActiveMatrix Administrator. The ActiveMatrix BusinessWorks engine properties and global variables can be specified at deployment time. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details. Logging Mechanism Common logging using log4j is the default logging mechanism in the ActiveMatrix environment. ActiveMatrix BusinessWorks Service Engine provides an additional mechanism of logging by allowing you to switch to the classic way of logging using SDK logging. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details.
Changes in Functionality 9
Changes in Functionality
This section lists changes in functionality since the last release of this product.
Release 5.10
The BWSE Application Template gets automatically provisioned on a node if you deploy a DAA containing a BWSE component on that node.
Release 5.9.3
TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.3 is a full installer and does not need a prior installation of 5.9.0 or 5.9.2 version.
Release 5.9.2
TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.2 is a full installer and does not need to be installed over 5.9.0 version. When installing TIBCO ActiveMatrix BusinessWorks Service Engine over an active setup of TIBCO ActiveMatrix Service Grid where Administrator and nodes have already been created, there is no need to run TIBCO Configuration tool. However, you need to deploy BWSE IT on an already existing ActiveMatrix nodes through a template. In TIBCO ActiveMatrix Administrator, create a new application with TIBCO ActiveMatrix BusinessWorks Service Engine Implementation Type DAA template and deploy it in Resolve mode on the existing nodes. If you create any subsequent nodes from ActiveMatrix Administrator UI or CLI, you need to provision BWSE IT on these new nodes. See the Provisioning BWSE Implementation Types on New Nodes section in the TIBCO ActiveMatrix BusinessWorks Service Engine Installation for details. In 5.8.x release, the BWSE component was tied to Enterprise Archive file that was associated with all the process definitions, services, and resources in a BusinessWorks project. In 5.9.x release, the BWSE component is tied to a Service resource. To migrate a project from 5.8.x release to 5.9.x, see Migrating Projects from 5.8.x into 5.9.2, 5.9.3, or 5.10.0, page 14.
10
Release Notes
The separator to specify multiple global variables is changed from . (period) to : (colon).
If a BWSE component in 5.9.0 or 5.9.1 project exposes global variables from group, you need to import such project(s) into TIBCO Business Studio in 5.9.2 environment and use the Sync component from implementation quick-fix available on the BWSE component. The plug-ins developed on TIBCO BusinessWorks are not supported with TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.2 release. However, see the respective plug-ins documentation for further updates. TIBCO ActiveMatrix BusinessWorks Service Engine provides new samples for Bottom Up design, Unwired mode, Context, and Intents in the TIBCO_HOME\bwse\<version>\samples folder. The step by step instructions to use these samples are provided in TIBCO ActiveMatrix BusinessWorks Service Engine Getting Started Guide.
Changes in Functionality 11
Release 5.9.0
This section lists changes to existing product functionality in release 5.9.0: In 5.8.0 release, Message Acknowledgment was tied to the Confirm Activity for both In-Only as well as for In-Out scenarios. In 5.9.0 release: For In-Only MEP, the messages are confirmed either when the Confirm activity executes or when the job finishes execution. For In-Out MEP, the message is acknowledged when the response goes back. In 5.8.0 release, the Flow Control was tied to the number of provider threads. Engine's FlowLimit parameter did not determine the Flow Limit. In 5.9.0 release, Flow Control is strictly a function of the FlowLimit set on the engine. BusinessWorks global variables become ActiveMatrix properties in BWSE component. So they can be configured as properties in TIBCO ActiveMatrix Administrator for a BWSE component. To deploy and run BWSE component instance on any other machine in the same ActiveMatrix environment, you no longer need to install the BWSE product on every machine/node. To do this: Using TIBCO Universal Installer, install the BWSE product only on the machine where TIBCO ActiveMatrix Administrator is installed and the system node is running. Using TIBCO ActiveMatrix Administrator > Application screen, provision the BWSE Implementation Type (IT) on that machine. For details, refer to Working in Distributed Mode in Chapter 1 of TIBCO ActiveMatrix BusinessWorks Service Engine Installation guide. TIBCO ActiveMatrix Administrator now uses DAA for creating an application instead of a Service Assembly. The navigation path to monitor the BusinessWorks processes from TIBCO ActiveMatrix has changed. Open the Infrastructure dashboard and select the Components link to view all the components. Double-click the BusinessWorks Service Engine component to view its component instances. To view BusinessWorks processes running on a
Release 5.8.1
There are no changes in functionality in this release.
12
Release Notes
Release 5.8
This section lists changes to existing product functionality in release 5.8. A provision was required for the user to create a process with the partner information in the sub-folder under the main BW Project selected by the user. You can now add a partner on the BW component and select the location for the partner to be created in the TIBCO Designer project along with providing a name for the partner which is being added from the Composite Editor. When attaching a TIBCO Designer project with the BW Component in the Composite Editor, the following options are now provided. Select an already existing archive sitting in the TIBCO Designer project. Allow TIBCO Business Studio to create an archive of the default name which is the TIBCO Designer project name. Change the name of the default archive. Enable All Wired Service Endpoints - This checkbox is available only when the BWSE component is wired and at least one of the service exposed on the BWSE component has a BusinessWorks endpoint configured. Select the checkbox to enable all the wired service endpoints. By default, the checkbox is not selected. The endpoints of port types that are not wired will always be disabled.
Deprecated and Removed Features 13
Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features. This section also lists features that are removed (if any).
Release 5.10
Deprecated Features No features are deprecated in this release. Removed Features No features are removed in this release.
14
Release Notes
Migration and Compatibility

This section explains how to migrate from a previous release to this release.
TIBCO ActiveMatrix Administrator

Upgrading 3.1.x administration and runtime objects (Administrator servers, hosts, and nodes) to 3.2.0 is supported. For information on how to upgrade runtime objects, see the TIBCO ActiveMatrix BusinessWorks Service Engine Installation guide.
Migrating Projects from 5.8.x into 5.9.2, 5.9.3, or 5.10.0

The steps to migrate the projects created in TIBCO ActiveMatrix BusinessWorks Service Engine version 5.8.x to version 5.9.2, 5.9.3, or 5.10.0 are as follows. 1. Import the legacy SOA project into TIBCO Business Studio. You should import projects that are dependent on one another (for example, a TIBCO SOA project and the Businessworks project on which it depends) at the same time. For information on how to import projects, see Help > Help Contents > Workbench User Guide > Tasks > Importing. The Problems view displays several errors. 2. Invoke the migration wizard: In the Project Explorer, right-click the SOA project to be migrated or its contained composite file and select Migrate to ActiveMatrix 3.x format. In the Problems view, right-click the problem and select Quick Fix. In the Quick Fix dialog, click Finish. The Project Migration wizard displays all the legacy projects to be migrated. 3. Optionally, click Add to specify additional projects. 4. Optionally, check the Save a copy of these projects before migrating checkbox and click Browse to browse to the location in which to save the projects. An archive file containing the projects is saved before the project migration. 5. Click Next. A tree containing the selected projects and the proposed migration actions is displayed.
Migration and Compatibility 15
6. Uncheck checkboxes next to the migration actions you do not want to be performed. 7. Click Finish. The selected migration actions are performed and Migration results are displayed. 8. Click OK to dismiss the Migration results dialog. 9. Save all the projects. Migration Result A Migration results summary page contains Information, Warnings, Error messages, and any manual steps required. A summary of the migration is stored in the file <SOA Project>/Migration/migration.txt, which is opened in a text editor. The summary lists the actions that were performed, the objects that were not migrated, and the manual actions that you must perform to run the migrated project. For example, after migrating a BWSE component, the Information area displays:
Updated BW Project bwProject for component BWSE_Component1 in composite bwcomposite
where bwProject is BusinessWorks project that was tied to BWSE_Component1 Updates in the Associated BusinessWorks Project after Migration In case of BWSE component, note that: After migration, the associated BusinessWorks project is updated as follows, A new AMX Enabled Service resource is created and all the exposed services and references on the 5.8.x component are added on the new Service resource. For example, if 5.8.x component has two Services configured on it, the newly created Service resource contains both the service port types. If there are exposed references on BWSE component, a new Partner Link Configuration is created, where partner links with AMX endpoint are added. For example, if 5.8.x component has two References configured on it, the newly created Partner Link Configuration displays two partner links configured for Service endpoints. These partner links are associated with the new Service resource in the Reference tab.
16
Release Notes
These resources are created per BWSE component as in 5.9.x version, each component is tied to a Service resource. Both the above resources are created under <BusinessWorks-Project>/Migration folder. In 5.8.x, BWSE component was tied to Enterprise Archive file that was associated with all the process definitions, services, and resources in the BusinessWorks project. To preserve the associated data in Enterprise Archive file, a reference to that Enterprise Archive file is added in the newly created Service resource ->Properties tab ->Enterprise Archive path. The exposed service and reference will have only AMX endpoint. The native endpoints configured in 5.8.x are preserved in the Enterprise Archive file tied to the BWSE Component. Post Migration Steps Check the migrated composite files and the associated resources. 1. To view the BusinessWorks project associated with BWSE component, double-click the BWSE component. It opens the associated BusinessWorks project and display new Service resource under Migration folder. 2. Save the project. After migration, you must save the BusinessWorks project. If you do not save the project, the newly created resources may be lost and you may get validation errors. 3. If you want to expose global variables used in 5.8.x projects as BWSE component properties in 5.10.x, follow these steps: a. Select the new Service resource -> Properties tab. By default, it displays the global variables used in 5.8.x BusinessWorks project. While importing multiple TIBCO BusinessWorks and SOA projects into TIBCO Business Studio, if the global variables do not appear in the Global Variables view, click the DABS Synchronize button for each project for which the global variables are missing.
Migration and Compatibility 17
b. Select the global variables to be exposed. c. Click Apply and save the project. The BWSE component appears to be out of sync. d. Update Component from Implementation on BWSE component to expose these global variables as BWSE component properties. 4. Save the project. Limitations The enable/disable endpoints configuration on 5.8.x component does not get ported after migration as the exposed service/reference on BWSE 5.10.x component has only AMX endpoints. After migration, BW native endpoints are enabled by default and cannot be configured through BWSE Component. If you want to disable them, remove them from the old service resource. If you want to enable them on BWSE component, reconfigure them in new service resource. If the older project contains a BPEL service exposed on component, BPEL implementation does not get migrated.
18
Release Notes
Closed Issues
The table in this section list issues that were closed in the named releases. To view defects for a particular feature, see the sections: Closed in Release Installation/Migration on page 18 Documentation on page 19 Design-time on page 20 Tools on page 33 Runtime on page 34 Administrator on page 43 ActiveMatrix BusinessWorks Plug-ins on page 47 TIBCO ActiveMatrix Administrator on page 48 TIBCO BusinessStudio on page 54 Summary
Change Request ID
Installation/Migration 5.10 5.10 5.10 5.9.3 BWSE-3468 BWSE-3373 BWSE-3328 BWSE-3072 When Oracle coherence classes were loaded in ActiveMatrix, there was a conflict. Migrating an ActiveMatrix BusinessWorks Service Engine project missed some imports and threw an error. When the BWSE 5.9.3 HF001 was applied, JDBC errors were noticed on SQL activities. When the design-time of ActiveMatrix Service Grid 3.1.5 32-bit and ActiveMatrix BusinessWorks Service Engine 5.9.2 32-bit were installed in the same home, using the "Debug as Composite Applicaion" option failed with error. ActiveMatrix BusinessWorks Service Engine 5.9.2 IT could not be deployed on a setup having ActiveMatrix 3.1.5 and ActiveMatrix BusinessWorks Service Engine 5.9.2. The performance of HTTP Server in unwired ActiveMatrix BusinessWorks Service Engine was lower than in the standalone BusinessWorks.
5.9.3
BWSE-3068
5.9.2
BWSE-2006
Closed Issues 19
Closed in Release 5.9.2 5.9.2 5.9.2
Change Request ID BWSE-1988 BWSE-1899 BWSE-838 1-9ARWE9
Summary BWSE component did not work with JMS server for IBM Web Sphere 7.0.0. ActiveMatrix BusinessWorks Service Engine 5.9.2 version supports Oracle 11g. When installing TIBCO ActiveMatrix BusinessWorks Service Engine on top of any TIBCO ActiveMatrix product, clicking the Finish button at the end of the installation took a long time to stop the installer. Uninstallation of ActiveMatrix BusinessWorks Service Engine did not delete the Extractor.exe, the executables for the ActiveMatrix Administrator instances and nodes. The dependency on the TIBCO Designer Add-in for TIBCO Business Studio has been removed from the TIBCO ActiveMatrix BusinessWorks Service Engine product. Now, the installer does not check for TIBCO Designer Add-in for TIBCO Business Studio dependency, if the Design-time feature is not selected during the product installation. It was a prerequisite to have TIBCO Runtime Agent and ActiveMatrix BusinessWorks already installed before installing ActiveMatrix BusinessWorks Service Engine. When ActiveMatrix BusinessWorks Service Engine version 5.6.3 was installed after an ActiveMatrix Administrator was created on an earlier version (5.6.0), an internal server error was thrown while mapping ActiveMatrix BusinessWorks Service Unit to the node, deploying/undeploying service assembly, or starting a service assembly in ActiveMatrix Administrator. While installing TIBCO ActiveMatrix BusinessWorks Service Engine service pack, the Universal Installer did not run a dependency check to verify whether the base version of the product was available in the environment.
5.9.2
BWSE-690 1-97JAET
5.7.2
1-9Z8OPF
5.7.1
1-991TAY
5.6.4
1-920LEZ
5.6.3
1-8W4T8J
Documentation 5.6.4 1-8N9Y57 TIBCO ActiveMatrix BusinessWorks Service Engine Users guide incorrectly stated the location of the tutorial as
TIBCO_HOME\bw\container\version_number\examples\bwse-tutori
al.zip.
20
Release Notes
Closed in Release 5.6.4
Change Request ID 1-8N9YDB
Summary The TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide incorrectly stated the tab under BusinessWorks Service Unit as BW Service Engine Settings. The correct tab name is BW Settings.
Design-time 5.10 5.10 5.10 BWSE-3372 BWSE-3229 BWSE-3184 Quick fix errors were observed while working with the sample projects provided for Top-down design approach. The Save button remained in the "Enabled" state even after saving the composite with the BWSE Component. If the context property of MESSAGE type in a WSDL message was configured in the imported WSDL, running it in RAD threw NullPointerException when the request was sent to a service. To make sure that application status is in sync with the Engine state, added the property Engine.ShutdownOnAllStartupErrors. To catch all the exceptions or errors related to BusinessWorks engine startup and activation, enable the property Engine.ShutdownOnAllStartupErrors = true to ensure that BusinessWorks engine throws ShutDownException and stops the BusinessWorks engine. Uploading a new DAA or updating the existing DAA did not update the BusinessWorks template. Common logging for Java Code activity did not work if applied at the component level. When the SOA project from WSDL option was selected and service/reference was configured with WSDL from BusinessWorks project, the BWSE component did not show corresponding chevrons. The user-defined loggers used in Write To Log activity did not take effect when configured at the application component level. If BWSE components in a composite were linked to two different service agents from the same BusinessWorks project and these Service agents contained operations/processes that share some global variables, promoting them from BWSE components resulted in duplication of composite properties.
5.10
BWSE-2835
5.10 5.10 5.10
BWSE-2677 BWSE-2635 BWSE-2567
5.10 5.10
BWSE-2270 BWSE-2259
Closed Issues 21
Closed in Release 5.10
Change Request ID BWSE-2047
Summary The value of a global variable was same as its name and it was exposed on a BWSE Component and promoted. In this case, even though the promoted component property was not sourced to the substitution variable, DAA packaged that global variable as a substitution variable. When Adapter Binding Type (BT) was installed with ActiveMatrix BusinessWorks Service Engine, the Generate Adapter WSDL resource did not generate adapter WSDL. While specifying the context parameters for AMX endpoint, if the type "Message" was selected for the "Fault" direction, the component gave validation error. In the Bottom Up approach, Quick fixes did not appear on the BWSE component when you deleted Partner details from the Process Partner tab, clicked Apply, and then saved the BusinessWorks project. When a BusinessWorks Service or Partner was exposed to a BWSE component and their port type was changed on the component, sync from component did not take any effect and component threw an error. After exposing a partner on a component, renaming the exposed partner on a component was not supported. If you rename such reference and choose to sync to component, new Partner with process and partner configuration resource was generated in BusinessWorks project with default names. When an exposed service on a BWSE component was renamed, instead of renaming the service, it implemented new service in BusinessWorks when synced from component. When a Service resource was referenced to a Partner Link of AMX type with Output Context configured, it threw error messages.
5.10
BWSE-1927
5.10
BWSE-1880
5.10
BWSE-1828
5.10
BWSE-1719
5.10
BWSE-1650
5.10
BWSE-1647
5.9.3
BWSE-3103
22
Release Notes
Summary The BW plug-ins on top of ActiveMatrix Service Engine are now supported only using the Classpath (Append/Prepend) approach. As the ActiveMatrix platform does not provision the Plug-ins on the node, you must add the BW Plug-in JARs to the (Append/Prepend) classpaths for each DAA in the engine properties. This means that the design time will not add any requirements while generating the DAA files and ActiveMatrix Administrator will not validate the plug-in while deploying them at the Runtime.
5.9.3
BWSE-3046
When the context on BW Service Agent was configured to use the message present in the imported WSDL (and not in the Abstract WSDL), the BWSE component threw error. Two instances of the Send Mail activity could not run simultaneously with different authentication configuration within the same node (JVM). If a BWSE component is using the Invoke Partner activity with a Partner Link Configured on SOAP/JMS binding (without a promoted service), the JNDI Password property for the Partner Link COnfiguration reference was not supported as substitution variable. ClassCastException was observed while packaging a DAA if EAR resource contained Java global instance shared resource and had a BW plug-in installed. The SAML assertion sequence was not consistent after sending multiple requests in case of SAML SSO credential mapping (Signed) and SAML authentication. The security context propagation did not work in ActiveMatrix BusinessWorks Service Engine for a scenario where Client -> [Service -> BWSE component -> Reference] -> Partner Service. The SAML credential mapping policy applied on Reference failed as the context was not available. TIBCO Designer did not respond and failed to display global variables when the Properties tab on the Service Agent was clicked.
5.9.3
BWSE-3040
5.9.3
BWSE-3038
5.9.3
BWSE-3016
5.9.3
BWSE-2974
5.9.3
BWSE-2959
5.9.3
BWSE-2902
Closed Issues 23
Summary A concrete WSDL contained two operations with its schema and two partner link configurations. If there were two separate processes that used the partner link configurations to call the Invoke Partner activity, the second operation always failed. In fault tolerance mode, the Null Pointer Exception was thrown by secondary engine when creating jobs. In the Top Down approach, adding a new reference to a BWSE Component reported validation errors on the service agent and partner link configurations in TIBCO Designer Add-in for TIBCO Business Studio. If the "qualifier" argument was added to EAR2DAA without specifying any value, an "Invalid argument" error was thrown on the console. If WSDL-A is imported in WSDL-B and a Service resource is configured on WSDL-B, the message in the imported WSDL-A could not be selected in the Service resource. When both branches after the Catch activity take error transition, instead of sending SOAP fault, error loop was observed. Generating a DAA file with composite version X.Y.Z.<<qualifier>> (where qualifier can be a DateTime or random #) was not possible with EAR2DAA tool. This has been fixed by introducing a new argument "qualifier" in the EAR2DAA tool. It can have default value DateTime or user-specified custom value. Sample usage is as: EAR2DAA -earPath "" compositeVersion "" -qualifier ""
5.9.3 5.9.3
BWSE-2885 BWSE-2868
5.9.3
BWSE-2813
5.9.3
BWSE-2776
5.9.3 5.9.3
BWSE-2721 BWSE-2717
5.9.3
BWSE-2716
Invoke Partner activity could not locate proper schema to validate response message from third party service if it was configured with the WSDL that included schema files instead of importing them. FileNotFoundException exception can be encountered in the node or RAD logs. This exception is harmless and can be ignored.
5.9.3
BWSE-2679
SOAP request sent by the Invoke Partner activity had wrong namespace for a substitution type.
24
Release Notes
Closed in Release 5.9.3 5.9.3 5.9.2 5.9.2
Change Request ID BWSE-2659 BWSE-2613 BWSE-2238 BWSE-2074 1-9DSVOO
Summary The Transform XML activity in a Process Definition failed with exception. Debugging a composite application containing a BWSE a Mediation components in RAD failed with an error. It was not possible to run RAD with SOA Development (designtime) profile. When associating an ActiveMatrix BusinessWorks project containing a service resource with a BWSE Component, closing of the ActiveMatrix BusinessWorks project threw a NullPointerException in the workspace log. When a simple timer based process was run in an unwired mode in TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.0 with TIBCO ActiveMatrix Service Grid 3.1.0, the service was deployed but did not run. However, the status appeared In Progress in TIBCO ActiveMatrix Administrator. Invoke Partners from non-service starters do not work. If the name of a BWSE component was the same as any BusinessWorks project or SOA project in the workspace, an invalid DAA was generated. BW Service Implementation Details and BW Partner configuration Details disappeared when the PortType on Services and References section of the BWSE Component was selected. If a reference was added to the component implemented with default process and partner link resource, the Data may be lost dialog box appeared. Selecting YES did not add the partner to the Service Resource and the component showed out of sync error. When a Partner was exposed to a component, deletion of related process and Partner Link resource from BusinessWorks project threw NPE if the same partner was selected on the component. Unable to get response from ActiveMatrix BusinessWorks for the second request on SOAP -> BWSE scenario with WSRM (Exactly Once) policy added on the soap binding.
5.9.2
BWSE-2056
5.9.2 5.9.2
BWSE-2051 BWSE-1989
5.9.2
BWSE-1962
5.9.2
BWSE-1951
5.9.2
BWSE-1949
5.9.2
BWSE-1921 AMX-7950
Closed Issues 25
Summary
If none of interfaces configured on AMX enabled Service resource
were exposed to BWSE component, the native endpoints defined were not accessible. 5.9.2 BWSE-1888 When Endpoint of a BusinessWorks Service resource was SOAP/HTTP, the project ran successfully in RAD mode and ActiveMatrix Administrator runtime, but the http port could not be established. In the Top Down approach, after exposing BusinessWorks service or reference to a component, if you made any addition, deletion, or modification in the Context and Intent on the component UI, the changes did not reflect in the implementation resource. When a DAA is created on a command line for a composite with BWSE component, multiple com.tibco.ae.designerapi.NameConflictException were observed on the console. Selecting a partner link of transport type AMX in the Process was not possible. In the Top down approach, the WSDL file present in the TIBCO Designer project cannot be accessed for the BWSE component in the SOA project. Node's "PS Perm Gen" pool/number of loaded classes increased with each restart of a BWSE service assembly, eventually resulting in node crashing. When a WSDL file generated for an adapter in TIBCO Business Studio was mapped to a Partner Link Configuration in the TIBCO Designer project and the TIBCO Designer project was validated, the following error was thrown:
[Partner Link Configuration = Partner Link Configuration; Partner Link = name_1]. Partner Link has invalid configuration
5.9.2
BWSE-1886
5.9.2
BWSE-1876
5.9.2 5.9.2
BWSE-1556 BWSE-1539
5.9.2
BWSE-1150
5.9.2
BWSE-605 1-92OSJR
5.9.0
BWSE-1249 1-AL4MOP
In the TIBCO Designer project, when adding a Service to a BW component and manually configuring the Service Endpoint, the Implementation tab in the Modelling view showed the 'Enable All Wired Service Endpoints' checkbox selected by default.
26
Release Notes
Summary It was possible to create Service Resources with partners with the same name. However, the validator did not report the partners with the same name. When a Service agent had no endpoint configurations defined on it, renaming WSDL operation caused the 'Available Services to Expose' window to show the previous WSDL name and as a result the service could not be exposed. TIBCO ActiveMatrix BusinessWorks Service Engine Feature Plug-in detail displayed in TIBCO Business Studio Help -> About screen was improper. "com.tibco.matrix.bwse.help.doc" Plug-in was displayed with no proper Plug-in name. In the Implementation tab of the BWSE component, Enable All Wired Service Endpoints checkbox is available only when the BWSE component is wired and at least one of the service exposed on the BWSE component has a TIBCO ActiveMatrix BusinessWorks endpoint configured. When renaming an ActiveMatrix BusinessWorks Service Engine Component in a Composite, one more service Unit was created even though the old component continued to exist in the Service Assembly Editor. The Service Assembly archive was created with a dummy component and a Service Unit also appeared in the ActiveMatrix Admin for deployment on Node.
5.8.0
1-9SZCMP
5.8.0
1-9ORLWK
5.8.0
1-A2CUV2
5.8.0
1-9FMMU3
Closed Issues 27
Change Request ID 1-9NRJHB
Summary Scripted packaging is possible now. Use the following commands for scripted packaging:
<BWSE-Home>\tibcojre\1.6.0\bin\java -Xms256m -Xmx512m -XX:MaxPermSize=512m -jar startup.jar -refresh -application com.tibco.matrix.ant.task.service.jbi.assembly.AMXCre ateDeployableArchive -data "<workspace>" -saf "<saf file path>" -archive "<assembly archive path>"
<BWSE-Home>\tibcojre\1.6.0\bin\java -Xms256m -Xmx512m -XX:MaxPermSize=512m -Dosgi.bundles=org.eclipse.equinox.common@2:start,org .eclipse.equinox.registry@2:start,org.eclipse.update. configurator@3:start,org.eclipse.core.runtime@start -jar startup.jar -refresh -application com.tibco.matrix.ant.task.service.jbi.assembly.AMXCre ateDeployableArchive -data "<workspace>" -saf "<saf file path>" -archive "<assembly archive path>"
5.8.0
1-A7Z9PG
In the Composite editor the implementation property had an absolute path of the EAR file location. Hence, the user had to change the archive location every time the project was checked out. A validation check was required so that when the Enterprise Archive file is empty and user is creating a Service Assembly, an error is thrown. Occasionally renaming of the Processes and/or Resources in the BW project threw a FileNotFoundException in the TIBCO Designer Console. A dialog box was required in order to enable the user to create a new archive or use an existing archive, when selecting a BW Project in a BW Component. User now has the option to select an already existing archive sitting in the Designer project or TIBCO Business Studio is able to create an archive of the default name which is the TIBCO Designer project name or change the name of the default archive.
5.8.0
1-9T74P0
5.8.0
1-9H24EH
5.8.0
1-9H3WLZ
5.8.0
1-9GTMMN
User could not provide a name of their choice when adding a partner on the BWSE component in the Composite Editor; whereas other components like Java and DotNet allowed the same.
28
Release Notes
Change Request ID 1-9F39SJ
Summary A provision was required for the user to create a process with the partner information in the sub-folder under the TIBCO Designer Project selected by the user. The user can now select any location under the TIBCO Designer Project to add the partner. When creating a Service Assembly where the ActiveMatrix BWSE component was wired to Services and/or References, the Workspace logs showed a SWTException. When there were no archives in the workspace, the project archive picker was not empty. After renaming either a WSDL, a Service Interface or a Partner in the TIBCO Designer project; the respective Service and/or Reference on the BWSE component gets deleted. However, the related information continued to remain in the archive which was tied to the BWSE component. Occasionally, while running an ActiveMatrix SOA project containing a BWSE component in the ActiveMatrix Debugger, TIBCO Business Studio did not respond and showed either Namespace Cache, Saving Project, or Packaging Service Assembly pop-ups. On the Implementation tab, when a partner was exposed or added and a partner was selected, the table on the right side showed wrong column names. If a project associated with the component was closed, the delete component continued to show the popup message asking the user to open the ActiveMatrix BusinessWorks project. The Service Resources did not show the correct process name when a web service was re-generated from a WSDL without modifying the portType. On the Implementation tab, the complete path to the archive was not displayed. When a Process had multiple partners configured on it and a Service had multiple portTypes exposed or added on the BWSE component, deleting one Service/Reference resulted in the deletion of the related process entry from the archive in the Designer project.
5.8.0
1-9GI39S
5.8.0 5.8.0
1-9HA4BZ 1-9HMZQL
5.7.2
1-9HNCXW
5.7.2
1-9T3B8I
5.7.2
1-9GWRXL
5.7.1
1-9F39US
5.7.1 5.7.1
1-9F3YP5 1-9GI333
Closed Issues 29
Change Request ID 1-9GPSEF
Summary If a PortType exposed on two components was removed from the Service Resource, it removed the chevron from both components but did not remove the Service Resource entry from the archive of the second component. Clicking on the Archive Name link in the Implementation tab after associating a BWSE component with a TIBCO Designer Project threw a SWTException if the associated TIBCO Designer Project had not been saved. When renaming a WSDL that was tied to a service agent in the TIBCO Designer project, the 'Available services for Expose' list on BWSE component did not get refreshed with the updated WSDL information and resulted in the service agent not getting exposed on the ActiveMatrix BWSE component. If a BWSE component existed in the composite then components like Java/.Net/Mediation showed incorrect (BW component) information. When an EAR file was deleted from an ActiveMatrix SOA project, an exception was thrown if a BWSE component or a service assembly archive was created using the EAR file. When creating a BWSE component, all the schemas from the ActiveMatrix BusinessWorks EAR file were not imported. This was caused by multiple import statements in a single XSD or a WSDL file and the order in which the WSDL files or XSD were imported was important. When the contents of an ActiveMatrix BusinessWorks EAR file tied to a BWSE component changed, the user had to delete the component and create a new BWSE component with the changed EAR file. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for the steps to use an updated ActiveMatrix BusinessWorks EAR file.
5.7.1
1-9HIZW6
5.7.1
1-9HNDUM
5.7.0 5.6.4
1-999QWL 1-8KT513
5.6.4
1-919J0S
5.6.4
1-929Z48
30
Release Notes
Change Request ID 1-94V0VC
Summary The BWSE component now allows you to selectively enable and disable the service endpoints of all wired port types. By default, the endpoints of wired port types are enabled. To disable all the wired service endpoints: a. Navigate to Properties -> Implementation tab for the selected BWSE component. b. Select the checkbox Disable All Wired Service Endpoints to disable all the endpoints of wired port types. When the checkbox is cleared, you can choose to enable or disable the individual endpoints for the wired port types. To enable or disable the individual endpoints for wired port types: a. Navigate to the Properties -> Implementation tab for the selected BWSE component and select the node Service Resources in the tree structure. b. Select a port type under the service resource. The port type information is displayed on the right hand side. A new column, Enabled, has been introduced in the table Endpoints Defined in BW and a checkbox is provided for every wired endpoint listed in the table. These check boxes are selected by default. c. To disable an endpoint, clear the checkbox against the endpoint in the Endpoints Defined in BW table. To enable an endpoint, select the checkbox against the endpoint in the Endpoints Defined in BW table. The endpoints of port types that are not wired will always be enabled. TIBCO ActiveMatrix BusinessWorks 5.6.3 must be installed to allow selective enabling and disabling of service endpoints. NOTE: Disabling all wired endpoints at the component level will override the selection at the individual endpoint levels.
Closed Issues 31
Closed in Release
Change Request ID
Summary In the ActiveMatrix environment, the context mapping of the most recently created service resource is picked up. However, when the checkbox Disable All Wired Service Endpoints for a BWSE component is selected, the context mapping for the endpoints will no longer be available. Hence the Get Context and Set Context activities will not retrieve and set the value of a Context resource respectively. For a service resource with multiple endpoints, the context mapping is available if: the checkbox Disable All Wired Service Endpoints is not selected at least one of its endpoints is enabled and wired context mapping has been defined for the enabled endpoint.
5.6.4
1-90IMQX
The Get Context and Set Context activities did not retrieve and set the value of a Context resource respectively when processing a message from ActiveMatrix BusinessWorks Service Engine. This has been fixed. However, note the following limitations: The context mapping configured for the most recently created endpoint in the Service resource is applied to the request. While invoking services through the ActiveMatrix environment, any context mappings with SOAP input headers, other than the ones mapped from the input message's message parts, fail at runtime. This is due to the restriction in ActiveMatrix to configure soap headers. While invoking services through the ActiveMatrix environment, any context mappings which use security context fail at runtime. In the ActiveMatrix environment, the context mapping of the most recently created service resource is picked up. When the checkbox Disable All Wired Service Endpoints for a BWSE component is selected, the context mapping for the endpoints will no longer be available. Hence the Get Context and Set Context activities will be unable to retrieve and set the value of a Context resource respectively.
This fix is available only if TIBCO ActiveMatrix BusinessWorks 5.6.3 is installed in your environment.
32
Release Notes
Change Request ID 1-9AJOZJ
Summary While adding two BusinessWorks service units to a service assembly archive, the Add Definition dialog for the second service unit did not list the BusinessWorks container and the BWSE component if both the service units contained a BWSE component each. This has been fixed. When a service unit name was edited using the Service Assembly editor and saved, the changes were not retained. The service unit name was reverted to the original name. This has been fixed. When components such as Java, .NET, or Mediation were added to a composite containing a BWSE component, the Composite Editor incorrectly displayed the BWSE component related information for the other components too. This has been fixed. The manifest information of a service assembly differed when the service assembly was created using the composite and by right clicking the .EAR file. This has been fixed. ActiveMatrix BusinessWorks Service Engine was unable to resolve external jar files that were part of an ActiveMatrix BusinessWorks project EAR file and were specified as AliasLibrary references. This has been fixed. The Content Tree for a BWSE component, available under the components Properties -> Implementation tab, was empty on the Linux platform. This has been fixed. While creating a new BWSE component a NullPointerException was thrown if the ActiveMatrix BusinessWorks project EAR file selected contained a SOAP over JMS event source, and the JNDI Context URL in the JMS Connection shared resource Configuration tab was empty. This was observed even if the Use JNDI for Connection Factory checkbox was not checked. This has been fixed. Although not a part of the ActiveMatrix BusinessWorks project, a dummy WSDL file test.wsdl was packaged in the service assembly when a service assembly archive was created by right-clicking the project .EAR file. This has been fixed.
5.6.3
1-9AJP0M
5.6.3
1-8OA5UL
5.6.3
1-8U3T6Y
5.6.3
1-8U6A6B
5.6.3
1-8V1VXR
5.6.3
1-8XQA3V
5.6.3
1-8U3T5V
Closed Issues 33
Change Request ID 1-8MYYHZ
Summary If the schema in the WSDL was referred to by its relative path, the .xsd files associated with an EAR file were not imported correctly while creating a BWSE component. Although the schema name was seen under the appropriate location, the contents were not imported in the Business Studio project. An exception was thrown in such a case. This has been fixed. While creating a BWSE component, the nested schema associated with an EAR file was not imported correctly.
5.6.1 Tools 5.10 5.8.0
1-8MMKGX
BWSE-2204 1-AD49Y9
Added an option compositeNamespace to the EAR2DAA tool to change namespace. There was absence of heap size settings in the tra files of Migrator and Extractor. Hence, the default size setting which were very small, caused the utilities to run out of memory. Increasing the default maximum heap size for Ear2SA, Migrator, and Extractor tools was required. With this fix these tools are provided with the following two variables.
java.heap.size.initial java.heap.size.max
5.8.0
1-AD49WX
The value of these variables can be tweaked as per your requirements. 5.8.0 1-9WP7JD A provision was required to update the version number of Service Assembly and ActiveMatrix BusinessWorks Service Unit using the Ear2SA tool. Ear2SA, Migrator and Extractor tools did not use Client VM instead of Server VM. The service names for all the unwired ActiveMatrix BusinessWorks service assemblies were shown as Component_Ear2SA in Monitor & Manage perspective of ActiveMatrix Administrator and TIBCO ActiveMatrix Service Performance Manager Services dashboard, making it difficult to distinguish them. Now the EAR name is appended to the Component Name for all the components created through the EAR2SA tools.
5.8.0 5.7.2
1-AD49ZT 1-9MNCK8
34
Release Notes
Closed in Release 5.7.1 5.7.1 5.7.1 5.7.0 5.6.4 5.6.4
Change Request ID 1-9F2282 1-9F22ZC 1-9RK2S0 1-8MTETJ 1-8YQ7MR 1-8MQU9X
Summary Logs were not created at the specified location when migration failed with the "!Error Occured!" message. On Linux, the Migrator tool displayed an error and failed to migrate a workspace after the Migrator.tra file was modified. The EAR2SA tool did not work on Linux. The EAR2SA tool did not give specific error messages when an incorrect input was provided. The EAR2SA tool did not exit after creating a service assembly. The message on the console after a Service Assembly is created using the EAR2SA tool has been modified to "SA Archive created and located at SA_Location". When the EAR2SA tool was run with any EAR file, the tool either failed or did not respond. When the program did not respond, the key Ctrl+C had to be used to stop the program and generate the service assembly. The error messages provided by the EAR2SA tool referred the user to the log files. However, the location of the log files was not provided.
5.6.4
1-92KZU5
5.6.4 Runtime 5.10 5.10
1-8YQ7LZ
BWSE-3363 BWSE-3329
"InvalidTransactionException" was observed when records were inserted in a loop in the transaction group. When the custom SOAP Fault message was returned, the Invoke Partner activity generated wrong output and TIBCO BusinessWorks threw validation error. Performance improvement in the project validation time. Message was not consumed from the Virtualization Queue when an invalid payload was received. Message was not consumed from the Virtualize Queue for a BWSE component. Memory leak problems were observed in BWSE Runtime during multiple deployment and undeployment.
5.10 5.10 5.10 5.10
BWSE-3309 BWSE-3303 BWSE-3281 BWSE-3241
Closed Issues 35
Closed in Release 5.10 5.10
Change Request ID BWSE-3214 BWSE-3210
Summary Add or update of substitution variable using CLI failed if type was not specified. If the End activity got an error as input from the Error transition, a Null Pointer Exception was thrown. ActiveMatrix BusinessWorks Service Engine went into a loop and consumed 95% of CPU. Also, if the WSDL file contained the multi-part message for the operation, the content of the SOAP body and head were exchanged while generating the output.
5.10 5.10
BWSE-3175 BWSE-3067
The Global Managed Transactions did not work with JDBC updates in a Group. When the external Service sent back the custom SOAP Fault response to the Invoke Partner activity, incorrect output was generated and ActiveMatrix threw validation errors. If you set MaxJobs and FlowLimit on a BWSE Application and the Application contained a service that received data from the JMS endpoint, stopping the application or the node did not release the JMS connection and threw error. Throughput of the InvokePartner activity degraded by approximately 50% when the service was placed on a different node from that of InvokePartner. When a DAA containing an Engine Command Shutdown activity was deployed and run using TIBCO ActiveMatrix Administrator, it went into an unknown state. The DAA could not be deployed or deleted in a normal way. Memory leak issue was observed in the JMS receiver. Deploying a custom JAR gave loading issues in TIBCO Business Studio. Exception is thrown at runtime if the Call Process activity is used in a Transaction group. Queue receiver did not read messages from queue if JNDI-based JMS connection was used.
5.10
BWSE-3035
5.10
BWSE-951 1-9GT9CB
5.10
BWSE-373 1-8MBGL8
5.9.3 5.9.3 5.9.3 5.9.2
BWSE-2922 BWSE-2657 BWSE-2558, BWSE-2499 BWSE-2445
36
Release Notes
Summary The Instrumentation property added significant performance overhead. This property is disabled by default in TIBCO ActiveMatrix BusinessWorks Service Engine version 5.9.2. Some of the TIBCO Hawk instrumentation methods require runtime actions that impose performance and memory overhead. These actions can be enabled or disabled on a per-process definition basis at any time by setting this property. Setting the engine property Instrumentation.* to true enables those actions for all process definitions. Setting the property Instrumentation.<processName> to true enables those actions for a specified process definition. Setting this property to false disables the actions. The instrumentation properties can be set at runtime by calling the TIBCO Hawk setInstrumentProperties method. The property value specified in a call to setInsrumentProperties takes effect immediately. To monitor the Process Definition statistics in ActiveMatrix Administrator dashboards, add this property through ActiveMatrix Administrator in Engine Properties as follows:
Instrumentation.* = true
5.9.2
BWSE-2202
During Deploy, Undeploy, Start, or Stop of an application, memory leak might happen. To avoid such memory leaks, disable Hawk from BW Engine by adding the property Hawk.Enabled=false in BW Engine Properties in TIBCO ActiveMatrix Administrator > Application > Application Configuration. When Authentication with Signature and Authorization for authenticated user policies were applied on each endpoints of a Service Assembly such as SOAP, ActiveMatrix BusinessWorks Service Engine and JAVA for security context propagation; an error was thrown on the node console while sending a request through ActiveMatrix BusinessWorks client. The request, however, was passed. When the severity of the logging configuration in ActiveMatrix Administrator was set to DEBUG, the exceptions were seen in the log files. When a SOAP service with multipart output message was invoked, the service gave an error if it was running in the wired mode in the ActiveMatrix environment.
5.9.2
BWSE-937 1-9GGVPJ
5.9.2
BWSE-645 1-960KID BWSE-428 1-8N42CM
5.9.2
Closed Issues 37
Change Request ID 1-AUK1TV
Summary The value of faultcode element in SOAP fault response sent by TIBCO ActiveMatrix BusinessWorks Service Engine 5.8.0 had an extra namespace. Resources in Alias libraries and classpath did not load. With this fix now, all types of files in TIBCO ActiveMatrix BusinessWorks Service Engine can be accessed, if added in the Alias library component with the "Classpath" and "Deploy" option checked. When starting TIBCO ActiveMatrix BusinessWorks Service Engine process on AIX platform, ActiveMatrix BusinessWorks engine failed to initialize and threw a Nullpointer exception. A way to control the flow of jobs by setting parameters like AcceptCount, MaxJobs, FlowLimit, ActivationLimit, StepCount, etc, to done at the Node level was required, since the TIBCO ActiveMatrix BusinessWorks runs inside the node. For details, refer to TIBCO ActiveMatrix BusinessWorks Service Engine User's Guide.
5.8.0
1-ACR35H
5.8.0
1-AA9SVI
5.8.0
1-92MAXC
5.8.0
1-9TCPI3
On Windows 2008, executables such as managementdaemon, amx-db, and so on did not run and an "access is denied" error was displayed as user privileges were not sufficient. Node heap size did not reduce even after shutting down and undeploying the TIBCO ActiveMatrix BusinessWorks Service Engine. When Service Assembly with BW component containing HTTP Request Activity in its TIBCO BusinessWorks project was re-started, it encountered the following error: "java.lang.LinkageError:
class". loader constraints violated when linking org/apache/commons/httpclient/HostConfiguration
5.8.0 5.8.0
1-9N92PX 1-AJ89NH
5.8.0 5.8.0
1-AFQ5P0 1-A45KIJ
On Unix platform when deploying a BW service having JMS transport, the service did not get initialized. PortType with the same name and namespace defined in two different WSDL files caused the Operations to be not listed in the Invoke Partner Activity, when the PortType partner was selected.
38
Release Notes
Closed in Release 5.8.0 5.7.2 5.7.2
Change Request ID 1-8QV7HS 1-9C987B 1-9QWWYQ
Summary For the Multipart input message containing string datatype, an "Output data invalid" error was encountered for the Wired Service. The <detail> element was missing from the SOAP fault returned by the TIBCO ActiveMatrix BusinessWorks BPEL process. If a service assembly was stopped from the ActiveMatrix Administrator while the Invoke Partner activity was still executing, an InterruptedException was thrown and captured in the logs. This issue was seen in ActiveMatrix BusinessWorks Service Engine 5.7.1. A node shutdown when activating the ActiveMatrix BusinessWorks Service Engine container from ActiveMatrix Administrator on an existing node, if the node was created before ActiveMatrix BusinessWorks Service Engine 5.7.0 was installed. The built-in resource provider did not work with ActiveMatrix BusinessWorks Service Engine standalone as well as wired scenarios. When Integration Scenario for Adapter was run through Adapter Binding Type with ActiveMatrix BusinessWorks Service Engine, it did not work for the Out-only scenarios where Adapter was the publisher and ActiveMatrix BusinessWorks Service Engine was the subscriber. In the ActiveMatrix BusinessWorks Service Engine environment, the Local Endpoints did not work as expected. When a BWSE component containing the Invoke Partner activity was wired to a SOAP reference and the corresponding service assembly was deployed and run, a NullPointerException was sometimes thrown when multiple jobs were running simultaneously. Exceptions were thrown when a composite containing the BWSE component was run using the ActiveMatrix debugger. The global variables in an ActiveMatrix BusinessWorks project could not be specified using the ActiveMatrix Administrators Command Line Interface (CLI). As a result, ActiveMatrix BusinessWorks Service Engine did not support the use of ActiveMatrix Administrator CLI for deployment. See Chapter 5, Working with ActiveMatrix Administrator Command-Line Interface in TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide for details.
5.7.1
1-9DZ1KY
5.7.1 5.7.0
1-9HEZJ7 1-8NKK3U
5.7.0 5.7.0
1-8Y39GV 1-8VE6H5
5.6.4 5.6.4
1-90ZVJ7 1-8VR6X2
Closed Issues 39
Change Request ID 1-9364S1
Summary The ActiveMatrix Administrator Command-line Interface (CLI) tool could not deploy a service assembly containing more than one BusinessWorks Service Units. This has been fixed. When a BWSE component was created from a WSDL file name containing a blank space, a deployment error was thrown by the node. This has been fixed. An MBean Server Registration Exception was thrown if two or more BusinessWorks service units were packaged in a single service assembly archive. This has been fixed. When ActiveMatrix BusinessWorks Service Engine 5.6.3 was installed on top of ActiveMatrix Service Grid 2.0.x, the ActiveMatrix Debugger failed to start. This has been fixed. Wiring a BWSE component service or reference chevrons did not override the BusinessWorks concrete bindings. If the component service was not overridden, then the reference was also not getting overridden. This has been fixed. This fix is available only if TIBCO ActiveMatrix BusinessWorks 5.6.3 is installed in your environment.
5.6.4
1-94XXN9
5.6.4
1-95D9DA
5.6.4
1-95D9JA
5.6.4
1-8STYTD
5.6.4
1-90OJDL
A SOAP over JMS service resource configured to run with a direct JMS Connection did not give any errors during validation. However, the service gave a connection error at runtime. This has been fixed. This fix is available only if TIBCO ActiveMatrix BusinessWorks 5.6.3 is installed in your environment.
5.6.4
1-95G55U
The BWSE component did not work when wired to the JAVA component if the message parts were of either simple or complex type. This has been fixed. Some of the allocated resources were not released when a BWSE component was stopped. This was because the BWSE components shared the same class loader and hence the same resources. This has been fixed.
5.6.4
1-929WTW
40
Release Notes
Change Request ID 1-8T44UO
Summary Performance degradation was observed for services that were invoked and consumed by ActiveMatrix BusinessWorks Service Engine through the ActiveMatrix framework. This degradation was governed by: Scalability of the ActiveMatrix framework Marshalling and unmarshalling of data for messages exchanged between the BusinessWorks container and the ActiveMatrix framework.
This has been fixed. 5.6.4 1-97LWBV Exceptions were thrown when a service resource with Local endpoints or no endpoints configured was run in the wired mode in the ActiveMatrix environment. This has been fixed. This fix is available only if TIBCO ActiveMatrix BusinessWorks 5.6.3 is installed in your environment.
Closed Issues 41
Change Request ID 1-951D2D
Summary Following is the list of messages that are logged when the logging configuration for the BusinessWorks container and the BusinessWorks service unit is set to DEBUG.
INFO : TIBCO-IT-BW-910251: BusinessWorks Implementation Type initialized successfully. INFO : TIBCO-IT-BW-910252: BusinessWorks Implementation Type started successfully. INFO : TIBCO-IT-BW-910255: BusinessWorks Implementation Component "env1-node1-httpwww.example.comdefault-BusinessWorks" created successfully. INFO : TIBCO-IT-BW-910273: BusinessWorks Implementation Component "env1-node1-httpwww.example.comdefault-BusinessWorks" stopped successfully. INFO : TIBCO-IT-BW-910274: BusinessWorks Implementation Component "env1-node1-httpwww.example.comdefault-BusinessWorks" undeployed successfully. INFO : TIBCO-IT-BW-910272: BusinessWorks Implementation Component "env1-node1-httpwww.example.comdefault-BusinessWorks" started successfully. DEBUG: TIBCO-IT-BW-910291: InboundRequest.BusinessWork Implementation: Component=env1-node1-httpwww.example.comdefault-Business Works, Operation=http://xmlns.example.com/BokerWSDL, Message=<?xml version="1.0" encoding="UTF-8"?><ns5:InMessage xmlns:ns5="http://xmlns.example.com/BokerWSDL"><PANNumbe r>123</PANNumber> DEBUG: TIBCO-IT-BW-910292: InboundResponse.BusinessWork Implementation: Component=env1-node1-httpwww.example.comdefault-Business Works, Operation=http://xmlns.example.com/BokerWSDL, Message=<?xml version="1.0" encoding="UTF-8"?><ns:OutMessage xmlns:ns="http://xmlns.example.com/BokerWSDL"><ApprovalS tatus>Loan approved for :123</ApprovalStatus></ns:OutMessage> DEBUG: TIBCO-IT-BW-910293: OutboundRequest.BusinessWork Implementation: Component=env1-node1-httpwww.example.comdefault-Business Works, Operation=http://xmlns.example.com/CreditCheckService, Message=<?xml version="1.0" encoding="UTF-8"?><ns:InMessage
42
Release Notes
Closed in Release
Change Request ID
Summary
xmlns:ns="http://xmlns.example.com/CreditCheckService">< PANNumber>123</PANNumber></ns:InMessage> DEBUG: Outbound.BusinessWork Implementation: Message Context Info : Component=env1-node1-httpwww.example.comdefault-Business Works, ExchangeID=0e67a7d9-7c3b-4aa0-8a6d-a31449fb7246, InterfaceType=interface javax.wsdl.PortType, portType={http://xmlns.example.com/CreditCheckService}Cr editCheckInterface, Operation=http://xmlns.example.com/CreditCheckService, Security Subject=null DEBUG: TIBCO-IT-BW-910294: OutboundReponse.BusinessWork Implementation: Component=env1-node1-httpwww.example.comdefault-Business Works, Operation=http://xmlns.example.com/CreditCheckService, Message=<?xml version="1.0" encoding="UTF-8"?><ns5:OutMessage xmlns:ns5="http://xmlns.example.com/CreditCheckService"> <CreditScore>6</CreditScore></ns5:OutMessage>
5.6.3
1-8U0C29
When an ActiveMatrix BusinessWorks project was run with the ActiveMatrix BusinessWorks Service Engine, the size of the global variable name and its value were limited by the database used in the ActiveMatrix environment. This limitation was observed while working with non-default databases, that is, any database other than HSQLDB. This has been fixed. Performance of a TCP Receiver activity when run in ActiveMatrix BusinessWorks Service Engine was slower than running the activity with standalone ActiveMatrix BusinessWorks. This has been fixed. If a service assembly was stopped from the ActiveMatrix Administrator while the Invoke Partner activity was still executing, an InterruptedException was thrown and captured in the logs. This has been fixed. A NullPointerException was thrown when the Invoke Partner activity received a Fault reply without a faultName element. This has been fixed.
5.6.3
1-8NWNWD
5.6.3
1-8VGYP9
5.6.3
1-8VR6VN
Closed Issues 43
Change Request ID 1-8L7CP3
Summary If you had two separate TIBCO_HOME directories, for example TIBCO_HOME and ACTIVEMATRIX_HOME, and the BusinessWorks container was installed, the node console threw the following exception: java.io.FileNotFoundException: ACTIVEMATRIX_HOME\bw\5.6\bin\bwengine.tra. This problem was observed on the Windows 2003 Server platform. This has been fixed. If an abstract WSDL with inline schema was created in ActiveMatrix BusinessWorks, the <wsdl:types> field was found to be missing. Hence, the <wsdl:types> field in a service created using this abstract WSDL would also be blank. If such a service was exposed in ActiveMatrix environment, an internal error was thrown when this service was invoked. This has been fixed. When more than one service assembly was run on a given node, an error occurred if the service assemblies contained ActiveMatrix BusinessWorks JDBC activities in their projects and the JDBC Connections connected to Oracle using the OCI driver (oracle.jdbc.driver.OracleDriver). To fix the issue, edit the property java.property.java.ext.dirs in the
AMX_TIBCO_HOME\amx\data\Environment_Name\Node_Name\bin\nod
e.tra
5.6.1
1-8MWR6R
5.6.1
1-8M9VWX
file to include the Oracle native driver jars in the path.
Administrator 5.10 BWSE-3313 When the BWSE application was deployed into an ActiveMatrix node, it did not read jndi.properties file like standalone TIBCO ActiveMatrix BusinessWorks. The basic authentication did not work against ActiveMatrix Administrator server. Installing 'TIBCO ActiveMatrix Binding Type for Adapters' along with ' ActiveMatrix BusinessWorks Service Engine' threw exceptions in ActiveMatrix Administrator while displaying BW Engine Properties. The BWSE
Admin war
5.9.3 5.9.3
BWSE-2917 BWSE-2729
5.9.2
BWSE-2165
was not getting deployed.
44
Release Notes
Summary In TIBCO ActiveMatrix Administrator > BusinessWorks Service Engine component Instance > Active Processes View, the exceptions thrown for the active processes provided the same exception details for all the processes. It displayed the JOB ID of the first process in the list and showed the same for all the ones below it. In TIBCO ActiveMatrix Administrator > BusinessWorks Service Engine screens, an error was thrown when a request failed. Instead of providing details, the error provided only the status code of the error. The data shown in the General tab > Statistic table did not match with the actual engine data (for completed, swapped, suspended, queued, aborted, totalExecution, averageExecution). Because of this, the created jobs did not match with the completed jobs. When deploying an application, if the application name was specified with spaces, the Monitor and Manage functionality did not work. Node errors were not printed in the node.log when there was an error in the engine start up.
logger com.tibco.amx.it.bwse.logger
5.9.2
BWSE-2000
5.9.2
BWSE-2021
5.9.2 5.9.2
BWSE-2020 BWSE-2231
You can log all the lifecycle and message events by configuring the at the node level.
5.9.2
BWSE-1998
In TIBCO ActiveMatrix Administrator > BusinessWorks Service Engine screens, when multiple records were selected in Locks and Active Processes screen only single record or none of the records could be seen. When a service assembly containing external jar files specified as AliasLibrary references was deployed and run, the following error message was thrown multiple times and could be seen in the node logs: "Error:
no alias for xxxx"
5.9.2
BWSE-562 1-9133AG
where xxxx is either name of the jar file or the folder containing the jars which is specified in the Alias Library. 5.9.0 BWSE-969 1-9HF4LP When a Service Assembly with an ActiveMatrix BusinessWorks Service unit was uploaded in ActiveMatrix Administrator, the global variables were also visible under the Substitution tab.
Closed Issues 45
Change Request ID BWSE-855 1-9CAN6L
Summary When trying to configure any global variables of a Service Assembly or ActiveMatrix BusinessWorks settings, clicking 'Save' did not show the new values entered by the user. ActiveMatrix BusinessWorks Service Engine did not support substitution variables. Consequently, a common variable at the composite level could not be shared across the BWSE component and any ActiveMatrix component(s). In the Monitor and Manage perspective for BusinessWorks processes, you can enable or disable process starters in the service assembly. When a process starter was selected and you clicked Enable or Disable, a pop-up window with an Alert message appeared. However, the process starters were enabled or disabled successfully. After editing the Password type global variable once if the values of other variables were edited, the Password type got corrupted. The Global Variable changes were not getting updated when a Service Assembly file was regenerated and uploaded. To get the updated Global Variable changes, ensure that you update the version number of TIBCO ActiveMatrix BusinessWorks service units and then generate the Service Assembly. This can be done by using either Ear2SA tool or TIBCO Business Studio.
5.9.0
BWSE-727 1-993QRH
5.9.0
BWSE-356 1-8M3715 BWSE-388 1-8MIDAF
5.8.1 5.8.0
1-AO1IFX 1-A76C2V
5.8.0 5.7.2
1-A2VX3H 1-9SYLYF
The "Exceptions" column under the "Active Processes" link was missing. On Solaris, if the Admin server was created by multiple users, the Global Variable and BW Settings tabs were not displayed in the TIBCO ActiveMatrix Administrator user interface for the BusinessWorks Service unit. However, the Service Assembly could be deployed. The Engine.Log.Type property could not be set at deployment time. This has been fixed. You can now set this property in the bwengine.xml file located in <TIBCO_HOME>/bw/5.x/lib/com/tibco/deployment. The default value specified in this file is used for all EARs and SAs created on the setup.
5.7.1
1-9N5BUK
46
Release Notes
Change Request ID 1-8OP513
Summary The default path where the JAAS web service is deployed to in ActiveMatrix Administrator was different from the path in TIBCO Administrator. As a result, the configuration file, JAAS.config, could not be used to configure JAAS authentication in ActiveMatrix. This has been fixed. See TIBCO ActiveMatrix BusinessWorks Service Engine Users Guide, Chapter 4 - Advanced ActiveMatrix BusinessWorks Features for the steps to configure JAAS authentication in the ActiveMatrix environment.
5.7.0
1-9AEWQU
When a service assembly was stopped from the ActiveMatrix Administrator while the Invoke Partner activity was still executing, an ?InterruptedException? was thrown and captured in the logs. This has been fixed. In the Active Processes perspective for BusinessWorks processes of the ActiveMatrix Administrator GUI, the search on ANY criteria did not work and gave a "duration blk" error message. This has been fixed. When global variables of type Integer and Boolean were edited in the ActiveMatrix Administrator GUI, the updated values were not picked up at runtime. This has been fixed and is available only if the service assembly is created in ActiveMatrix BusinessWorks Service Engine version 5.6.4. The service assemblies created with earlier versions have to be recreated in ActiveMatrix BusinessWorks Service Engine version 5.6.4 for this fix to be available. Accessing any link in the ActiveMatrix Administrator Monitor and Manage perspective's Process tab threw a StringOutOfBoundException exception if the composites target namespace differed from the default target namespace. This has been fixed.
5.7.0
1-8NCZ7K 1-8U9JC3 1-8U85LJ
5.6.4
1-97OZ95 1-9AEX3J
5.6.4
1-92OW63
Closed Issues 47
Change Request ID 1-8UC5P1
Summary The version numbers for ActiveMatrix BusinessWorks Service Engine Plug-in and BusinessWorks Container were not updated after the service pack for ActiveMatrix BusinessWorks Service Engine was installed, that is, version 5.6.1 or 5.6.2. The version numbers were incorrectly displayed in the ActiveMatrix Administrator GUI as 1.0.0. This has been fixed and the container version number is updated to 1.0.3 when ActiveMatrix BusinessWorks Service Engine 5.6.3 is installed.
Note: For release versions 5.6.1 and 5.6.2, the container version
number is not updated and is shown incorrectly as 1.0.0. To use the ActiveMatrix BusinessWorks Service Engine version 5.6.1 or 5.6.2, select 1.0.0.023. ActiveMatrix BusinessWorks Plug-ins 5.9.2 BWSE-1986 BusinessWorks XA transaction when used along with ActiveMatrix BusinessWorks Service Engine global transaction failed when the user used 'Generate Error' activity inside the XA transaction group. BusinessWorks Salesforce.com Plug-in could not run successfully in the ActiveMatrix environment as a standalone process using ActiveMatrix BusinessWorks Service Engine 5.6.1 and threw the following error:
java.lang.LinkageError.
5.7.2
1-9686YX
5.7.0
1-8LXWCR
When a service assembly containing any ActiveMatrix BusinessWorks SOAP activities was deployed and started in the ActiveMatrix environment, the following message was logged in the node logs:
lookup for BwHttp/HostName failed, default to "localhost": javax.naming.NameNotFoundException: [java:comp/env/BwHttp/HostName] not bound in naming service.
This has been fixed. 5.6.1 1-8MRN0B When an ActiveMatrix BusinessWorks project was run with ActiveMatrix BusinessWorks Service Engine, exceptions were thrown if the project contained activities from the SWIFT plug-in. The exceptions occurred because the libraries for TIBCO Adapter for SWIFT were not available in the classpath for the node. This has been fixed.
48
Release Notes
Change Request ID 1-8M2KPZ 1-8METVT 1-8MFHKT 1-99839D
Summary The following BusinessWorks plug-ins did not run with ActiveMatrix BusinessWorks in the ActiveMatrix environment: BusinessWorks COBOL Copybook Plug-in. BusinessWorks Salesforce.com Plug-in. BusinessWorks XA Transaction Manager Plug-in.
This has been fixed. TIBCO ActiveMatrix Administrator Closed in Release 3.2.0 Key TXML-115 Summary When an application containing a BWSE component is repeatedly deployed and undeployed, nodes no longer crash due to an out of memory condition. If you navigated to Infrastructure > Servers, after your login session expired an empty page no longer displays. A SOAP reference endpoint is no longer removed before the component has finished undeploying. Adding a group to an enterprise permission is working correctly. Setting a property of type Thread Pool no longer throws a ClassCastException. Granting permissions for an LDAP group using the CLI has been optimized. Thread pool resource instances installed on nodes in different environments are now resolved correctly. The stop command for a component in the Unconfigured state is now processed. A TIBCO Host instance can now be shut down when it has a node running an application in the partially deployed state.
3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
TRUP-212 TAP-9889 TAP-9857 TAP-9828 TAP-9740 TAP-9721 TAP-9688 TAP-9658
Closed Issues 49
Key TAP-9624
Summary If authorization is enabled for the EMS Server, for non-super users the password field is no longer blank in in the Environment > Environment Name > Configuration > Messaging Bus tab. Uninstalling resource instances and then immediately deleting them without waiting for the uninstall process to complete no longer leaves the resource instances installed and in the runtime state but deleted from Administrator. For HTTP connector resource instances, the ports are now relinquished.
3.2.0
TAP-9622
3.2.0
TAP-9529 TAP-9667
Concurrently deploying applications or undeploying applications and deleting resource templates from TIBCO BusinessStudio or Administrator CLI scripts no longer results in StaleObjectStateException errors. The upgrade application action in CLI now does not wait for previous version of the application to finish undeployment. In case of ActiveMatrix BPM, previous version of applications may not be undeployed for a long time (eg. until all existing work items are completed). In case users are upgrading an application from Business Studio they will not encounter a hang while the upgrade process is being completed. You are now able to select a batch of 10 or more nodes to install or start without running into a Protocol Violation error coming from the Oracle JDBC driver and a failure to complete the operation. When importing resource templates from a DAA or creating resource templates with inline credentials, the credentials are now added to the keystore. The Administrator UI now times out after using the Dashboard. Only superusers can now see the Permissions button in the Admin Configuration > Admin Server > Transport Configuration screen. The following error is not seen when installing a JMS resource instance for the second time using the Application > Deploy >Resource Instances dependency wizard:
[ERROR] org.apache.axis2.engine.AxisEngine - Please provide valid number of resource ids.
3.2.0
TAP-9524
3.2.0
TAP-9515
3.2.0
TAP-7778
3.2.0 3.2.0 3.2.0
TAP-7748 TAP-7704 TAP-7687
50
Release Notes
Key TAP-7577
Summary When you reinstall a resource instance, other resource instances or applications that depend on this resource instance now use the new version of the resource instance. When you navigate to a resource instance using the path Infrastructure > Hosts > hostname > Resource Instances > All Instances> template name, the Install and Uninstall drop-down lists are now correctly populated. Discrepancies are no longer seen in the Runtime and Action History states of the log service and payload service applications when the platform application is restarted. A thread pool resource instance (or any resource instance referenced from a policyset property) is not reported as being used by an application even though the application is either undeployed or was never deployed. Uninstalling a node immediately after installing it without starting the node no longer causes the install action to fail. If installing a resource instance on multiple node fails, the Administrator UI no longer hangs with the Saving Data message. When you wire a reference to a service the service binding is now listed oly once on the Target Service page of Manual Binding. After wiring a JMS service to JMS reference, clicking on Manual Binding displays the correct dialog. If a binding is contained in a logical node, promoting the reference using the binding to the environment is now allowed. An error is no longer displayed when Administrator is invoked from within TIBCO Business Studio and the default browser Internet Explorer 8. An HTTP connector resource template now accepts a substitution variable for the port number. Deploying or redeploying a DAA that contains policy sets works as expected.
3.2.0
TAP-7544
3.2.0
TAP-7447
3.2.0
TAP-7431
3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
TAP-6816 TAP-6647 TAP-5672 TAP-5669 TAP-4813 TAP-1628
3.2.0 3.2.0
TAP-1618 PER-586
Closed Issues 51
Key PER-1689
Summary VerifyAuthentication action now correctly validates the principal for authenticated user if the authentication is done against SSL-enabled LDAP. If Administrator and the Monitoring service used different databases and if the monitoring database was down when an application is deployed, newly deployed application did not show up on the dashboard. Application status is reported correctly in Dashboard when the application is deployed on two nodes across environments. The following error is no longer seen in the SystemNode log files:
Sync failed due to invalid Governed Object.
3.2.0
MCR-939
3.2.0 3.2.0
MCR-1742 MCR-1696
3.2.0
MCR-1655
The Dashboards > Infrastructure > Endpoint, Dashboards > Infrastructure > Service and Dashboards > Infrastructure > References tabs now show the accurate value for Avg Comp Process Time when extended monitoring is enabled. When applications containing multiple components are mapped to multiple nodes without restarting the application, the application status is accurately reported in the Dashboard. When using a CLI script to overwrite the node mapping for an application, "Partially Running" status is no longer seen in the dashboard. SAML assertions with the xmlns prefix outside the assertion no longer fail. SAML assertions no longer declare the default namespace prefix to no namespace so verification of the tokens through STRTransform no longer fail. User Search Expression can now be set for LDAP Authentication via CLI even when the Login as Administrator option is not checked in the LDAP Resource Template configuration dialogs in ActiveMatrix Administrator UI. The payload data URL correctly resolves the hostname in all configurations.
3.2.0
MCR-1241
3.2.0
MCR-1206
3.2.0 3.2.0
DSS-683 DSS-677
3.2.0
DSS-619
3.2.0
CL-2390
52
Release Notes
Closed in Release 3.2.0 3.2.0
Key CL-2307 CL-2035
Summary Memory growth is not observed on the node running log service (typically SystemNode) after it processes a large number of log events. When using DB2 the following exception is no longer seen in the SystemNode log when you click Export in Log Viewer
stdout - org.hibernate.exception.SQLGrammarException .
3.2.0
CL-1814
Undeploying and re-deploying the default log service results does not result in a Resource instance 'amxAdminDefaultHttpConnector' could not be found warning message. When you run the TIBCO Configuration Tool the following error message is no longer seen in the systemNode log file:
TIBCO-AMX-HPA-014212: Failed to lookup shared resource java:cl_logservice_jmsDestination javax.naming.NameNotFoundException: Name not found: 'cl_log service_queue
3.2.0
CL-1651
3.2.0
CL-1303
If you uses HSQLDB as the log service database, and you set the logging level of an logging configuration to Debug, the database will no longer crashes. If you use Oracle 11g and MSQL 2008 server for the log service database with a Debug log level, performance degradation is not observed. The following node properties to disable HTTP OPTIONS and PUT methods for HTTP connections are now supported:
amf.node.disableHTTPOptions=false amf.node.disableHTTPOptions.<connectorName>=false amf.node.disableHTTPPut=false amf.node.disableHTTPPut.<connectorName>=false
3.2.0
AMX-11095
You set these properties in the node's Configuration Configuration tab. 3.2.0 AMX-11094
> JVM
The cipher strength for Administrator's external HTTP connector is now configured to be "AtLeast128Bit". If the Administrator server is already configured with an SSL external HTTP connector then applying the hotfix will not update the existing connector to have the cipher strength to "AtLeast128Bit". You must recreate Administrator server after applying the hotfix.
Closed Issues 53
Key AMX-11092
Summary The Administrator server now supports form-based authentication for the Administrator CLI. To enable form-based authentication in the CLI, add httpAuthType=form in the Administrator properties file, for example remote.properties. Administrator now shows the correct node status when running with fault tolerant TIBCO Enterprise Message Service servers. Deploying an application containing an HTTP connector and other resources after undeploying with the Administrator CLI no longer returns the "Servlet already bound" error. Components now respond to the stop command even if they are in an unconfigured state. When an application resulted in a node running out of memory, Administrator no longer queues tasks (performed from the CLI and Administrator UI) for stopping and starting nodes and for deploying applications to other nodes. If Authorization is not enabled for the EMS server, updating the password for the EMS server in the Admin Configuration > Admin Server tab of the Administrator UI works as expected.
3.2.0 3.2.0
AMX-10929 AMRP-3932
3.2.0 3.2.0
AMRP-3885 AMRP-3726
3.2.0
AMRP-3704
54
Release Notes
TIBCO BusinessStudio Closed in Release 3.2.0 Key SDS-6002 Summary You can now disable WSDL validation as follows: 1. Select "Window > Preferences > TIBCO SOA Platform -> WSDL Validation". 2. Check one of the following checkboxes to choose the type of validation: Disable Live WSDL Validation - Disable WSDL validation for all operations Disable WSDL Validation - Disable WSDL validation for all operations except DAA creation You can also specify -Dsoa.disableWSDLValidation=true when starting TIBCO Business Studio to disable WSDL validation for all project operations. To validate a composite, right-click and select "Validate WSDL/XSD". 3.2.0 SDS-5991
related
The build time for DAAs containing SOAP/JMS bindings is reduced because TIBCO Business Studio no longer attempts to look up URLs that start with www.tibco.com. On a promoted service with SOAP binding, when the Style was Document, and Encoding was Literal, TIBCO Business Studio now enforces that only one WSDL message part can be bound to the SOAP body. WSDL and XSD schema files with multibyte characters on elements and names are now supported. TIBCO Business Studio now prevents you from specifying an application name that contains special characters (\, /, :, *, ?, ", <, >,|, whitespace, %, #, &, (, ), and comma) not supported by runtime. The Refresh Server action in the Deployment Wizard now completely refresh the local cache of the server contents. Validation for port type with In-Out operation can be done for JMS Transacted OneWay and Virtualization Transacted OneWay policies when you add a policy as well as when you add an intent.
3.2.0
SDS-5939
3.2.0 3.2.0
SDS-5017 SDS-5002
3.2.0 3.2.0
SDS-4994 SDS-4976
Closed Issues 55
Key SDS-4950
Summary Distribution policies cannot be changed once the application is created. When generating an Administrator CLI script and an application is being upgraded, the wizard now does not display a distribution option different from what was originally specified. Administrator CLI script execution does not fail if you select a resource instance that is in the Uninstalled or Failed state. Virtualization Transacted OneWay Policy configuration (maximum redelivery count, redelivery delay interval, error queue, and list of exceptions to stop redelivery) is not ignored on the reference side. If you used a Doc-Lit WSDL file with multipart messages, TIBCO Business Studio no longer shows a warning that "Generation of concrete wsdl with Doc-Lit style is not supported, because of multi parts". When there were multiple resource template files with the same name in the workspace, removing one of them no longer clears all references to that name.
3.2.0 3.2.0
SDS-4870 SDS-4174
3.2.0
SDS-3877
3.2.0
SDS-3692
56
Release Notes
Known Issues
The table in this section lists known issues in this release. To view defects for a particular feature, see the sections: Change Request ID Installation/Migration on page 56 Tools on page 59 Design-time on page 60 Runtime on page 64 Administrator on page 67 ActiveMatrix BusinessWorks Plug-ins on page 67 TIBCO ActiveMatrix Administrator on page 68 TIBCO Business Studio on page 81
Summary/Workaround
Installation/Migration BWSE-3650
Summary When you upgrade the BPM node from version 3.1.5 to 3.2.0 and deploy a DAA with SOAP, Mediation, and BWSE using "Force Deploy" on that BPM node, the deployment fails. Workaround Use the Resolve mode to deploy the Mediation and BWSE product applications on the BPM node. Alternately, deploy these product applications on a non-BPM node.
BWSE-3570
Summary Installing ActiveMatrix BusinessWorks Service Engine 5.10 on a setup of TIBCO ActiveMatrix BusinessWorks removes the _uninstall directory. Workaround To uninstall TIBCO ActiveMatrix BusinessWorks, run the uninstaller as follows:
Go to TIBCO_HOME/tools/universal_installer/ and run TIBCOUniversalInstaller. In the TIBCO Installation Manager, select Uninstall Products from Selected TIBCO Home Location and select the appropriate options.
Known Issues 57
Summary/Workaround
Summary (AIX - 64 bit) After installing TIBCO Runtime Agent, object files are cached in memory on AIX which may result into TIBCO Configuration tool failure. Workaround Login as a root user and run /usr/sbin/slibclean before installing TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.2.
BWSE-2560
Summary Sun MQ, JBoss MQ, and Weblogic MQ are not supported in TIBCO ActiveMatrix BusinessWorks Service Engine version 5.9.2. Third party shells are not available in the TIBCO Configuration Tool (TCT) for these JMS Providers. Workaround Configure the Custom Append (CUSTOM_EXT_APPEND_CP) or
Custom Prepend (CUSTOM_EXT_PREPEND_CP) property in ActiveMatrix Administrator. BWSE-2437

Summary Upgrading BWSE-IT fails if the application DAA containing BWSE
component is in the Running state.

Workaround While upgrading BWSE-IT, make sure all the application DAAs containing BWSE component are stopped.
BWSE-2529
Summary Entrust security provider is not supported. Workaround None
BWSE-2338
Summary Installing TIBCO ActiveMatrix BusinessWorks Service Engine over an active setup of ActiveMatrix (where ActiveMatrix Administrator, tibohost, and nodes are running) throws the fatal error: Unable to find the start class during TIBCO Runtime Agent installation. Workaround Before installing TIBCO Runtime Agent (as part of TIBCO ActiveMatrix BusinessWorks Service Engine installation), first stop tibcohost. However, if you have already tried installing TIBCO Runtime Agent once, stop tibcohost by killing the tibcohost process from Windows Task Manager. Then, reinstall TIBCO Runtime Agent by selecting Yes for the Do you wish to reinstall features? warnings.
BWSE-2078
Summary Running tibcohost on AIX fails with an error messsage: Failed

to exec process : Arg list too long : ./tibcohost.
Workaround Login as a root and set the property:

#chdev -l sys0 -a ncargs=16
58
Release Notes
Summary/Workaround
Summary Starting BWSE application on a new setup throws
java.lang.UnsatisfiedLinkError
in the node logs.
Workaround When installing ActiveMatrix BusinessWorks Service Engine on top of ActiveMatrix Service Grid, you must stop the node. If you do not stop the node, you need to restart the Tibco host.
BWSE-1865
Summary Uninstalling the product without stopping one or more services, does not unistall the services or files in use. Workaround None
BWSE-1167 1-AEZOTJ
Summary With standalone TIBCO Designer Add-in for TIBCO Business Studio already installed, during the Custom installation of TIBCO ActiveMatrix BusinessWorks Service Engine 5.8.0, the preinstall and post install summary screens shows TIBCO Designer Add-in for TIBCO Business Studio as a component being installed in spite of not being selected. Workaround None
BWSE-1000
Summary (RedHat Linux) Even after turning on the Hawk.Enabled property in bwengine.xml, the Hawk AMI interface cannot be viewed with ActiveMatrix BusinessWorks Service Engine. Workaround For enabling TIBCO Hawk in ActiveMatrix BusinessWorks Service Engine, add RV_HOME/bin and RV_HOME/lib to the node.tra file.
BWSE-970
Summary An ActiveMatrix BusinessWorks project tied to a BWSE component on Linux cannot be edited as ActiveMatrix BusinessWorks Service Engine design time on Linux is not supported. Workaround Create a Service Assembly on Windows and use a Linux machine for deployment.
BWSE-879 1-9DKDSC
Summary When migrating SOA projects using the Migrator Tool, the services
shows an unresolved proxy in its Configuration error along with a NullPointerException in the workspace log.
Workaround Use the menu Project > Clean after migrating the SOA projects.
Known Issues 59
Change Request ID BWSE-944 1-9GNTDV
Summary/Workaround
Summary While deploying a service assembly in an ActiveMatrix Administrator which uses Sybase database, an exception is thrown if the name of any deployment artifact is a numeric value. For example, if the name of an environment 123 or node is 555, the following exception is thrown:
com.sybase.jdbc3.jdbc.SybSQLException: Implicit conversion from datatype 'VARCHAR' to 'INT' is not allowed.
Workaround Ensure that the service assembly, environment, and node names are alpha-numeric.
Tools BWSE-3419
Summary If the composite or component name starts with numeric or special characters, the EAR2DAA tool throws an error. Workaround The name can have spaces and alphanumeric characters but cannot be empty or start with numeric characters. If the EAR name starts with numeric characters,you must specify valid compositeName and componentName arguments while running the tool.
BWSE-2077
Summary Even after a DAA is created successfully, running the EAR2DAA tool throws exception "The name: (self) already has a binding:" and
"[Fatal Error] :15994:45: XML document structures must start and end within the same entity".
Workaround This is harmless exception and can be ignored.
BWSE-1212 1-AIZ64D
Summary The EAR2DAA tool fails to create a service assembly when run from
the command line in case of an Adapter Archive present in your Enterprise Archive and throws a "Java.lang.IllegalStateException".
Workaround Use TIBCO Business Studio to create the Service Assembly.
BWSE-657 1-965D1X
Summary The EAR2DAA tool can no longer be run with the following options:
Verbose Tracing. Troubleshooting by Modifying the Thread_Stack_Size and Heap_Size properties.

Workaround None
BWSE-671 1-96WWYG
Summary While running, the EAR2DAA tool throws unnecessary log4j messages on the console. These messages are harmless and can be ignored. Workaround Make sure that components have unique names.
60
Release Notes
Change Request ID Design-time BWSE-3669
Summary/Workaround
Summary Creating a DAA fails if a user removes an archive reference from a
Service Agent resource.

Workaround Open the <service_name>.service file linked to the BWSE
Component. Remove the tag <enterPriseArchive/> from the file and perform the DABS Sync on the TIBCO Designer Project. BWSE-3663
Summary After renaming a component and implementation multiple times,
TIBCO ActiveMatrix BusinessWorks Service Engine hangs intermediately.

Workaround After renaming a component and implementation, you must save both TIBCO Designer and SOA projects.
BWSE-3615
Summary Running the sample for the Engine Properties project in RAD throws a ClassNotFound exception. The sample is available at TIBCO_HOME\bwse\<version>\samples\RAD_Example. Workaround
1. Click Run->Run Configuration-> Select Composite Application. 2. Go to Advanced tab. 3. Expand Node and add the following parameter to JVM Options:
-DTIBCO_SECURITY_VENDOR=j2se
BWSE-3469
Summary When you generate a web service from a WSDL in the TIBCO Designer project and save the project, the Enable for AMX checkbox does not work. Workaround After generating the web service from WSDL in the TIBCO Designer project, save the project and click on the Project Tree in the Explorer.
BWSE-3162
Summary When two BWSE components in an SOA project reference to two different service resources in two different BusinessWorks projects that have the same Service name, DAA includes only one Service. Workaround Keep the Component names unique across all the composites.
BWSE-2814
Summary The Invoke Partner activity throws "java.io.FileNotFoundException" exception while validating response message from the third party service. Workaround The 'FileNotFoundException' exception in the node or RAD logs
is harmless and can be ignored.
Known Issues 61
Summary/Workaround
Summary Even if the Global Transaction Intent is applied on a single BWSE component in a composite, the global transaction get propagated to all the components in the given composite and the components participate in the transaction. Workaround None
BWSE-2564
Summary Transaction Manager does not release the lock on the database if the engine property 'bw.plugin.transaction.xa.lock.connection' is not set to true on the BWSE Component participating in the Global Transaction. Workaround None
BWSE-2562
Summary ActiveMatrix Global Transactions do not work if a BWSE Component is configured with Call Process activity. Workaround None
BWSE-2434
Summary While debugging applications in RAD, even after you change the values of engine properties in the engine properties file added in the Enterprise Archive Resource, the new values do not take effect. Workaround Create a new Debug Configuration and run RAD.
BWSE-2415
Summary When multiple BusinessWorks and SOA projects are imported into a new workspace, some BWSE components show Quick Fix errors. Workaround
1. Import all the BusinessWorks projects before importing the SOA projects. 2. On each component, select Quick Fix > Sync Component from Implementation. BWSE-2261
Summary Third party drivers do not get loaded in the RAD Debugger. Workaround Configure Append or Prepend Engine property with the absolute path to the third party drivers in the Debug Launch Configuration dialog.
62
Release Notes
Summary/Workaround
Summary The timeout parameter configured on ActiveMatrix Threading policy does not affect the timeout parameter configured on the BW Partner Link Configuration on reference side. Both these timeout parameters operate independently. This implies that, when timeouts are different:
If timeout of BWSE is shorter, BWSE will timeout a request before ActiveMatrix times it out and return an error to ActiveMatrix. If timeout of ActiveMatrix is shorter, ActiveMatrix will timeout a request before BWSE times it out and return an error to BWSE component. The BWSE component will then propagate this error back to the caller.
Note that this is applicable only to the ActiveMatrix transport.

Workaround Ensure that the timeout is configured only at one place.
BWSE-1992
Summary While running EAR2DAA tool on Linux, the

java.awt.HeadlessException
error is displayed on the console.
Workaround This is harmless exception and can be ignored.
BWSE-1972
Summary Context mapping is not getting saved properly. Workaround Open the XPATH formula builder and save the mapping.
BWSE-1945
Summary Security Context is picked by only the first principal. It is not handled if there are multiple principals. Workaround None
BWSE-1750
Summary After deleting AMX endpoint of exposed service, sync from component does not add the AMX endpoint to the same service again. It shows an error that Service already exist in implementation. Workaround Configure AMX endpoint for BW Service in Service Resource.
BWSE-1736
Summary After exposing BusinessWorks partner, if you delete related AMX
Endpoint from Partner Link resource, and do sync from component, it incorrectly re-implements given reference in BusinessWorks with default process and partner link resource name.
Workaround None
BWSE-1696
Summary After enabling Service resource for ActiveMatrix, if SOAP endpoint is changed to AMX endpoint, that service will not be exposed onto BWSE component. Workaround Delete SOAP endpoint and add new AMX endpoint.
Known Issues 63
Summary/Workaround
Summary When you double-click a BWSE component to open the implementation resource in the Designer perspective, a null pointer exception is seen. Workaround This is harmless exception and can be ignored as it does not break
any functionality. BWSE-1536

Summary When a global variable is exposed as Component Property, it does
not retain its default value set as global variable.

Workaround Promote the component property at composite level to see its default value.
BWSE-1442
Summary Updated SOAP default style in the Service resource (AMX enabled) does not reflect in the SOAP Service Bindings of Promoted service. Workaround None
BWSE-1247 1-AK7932 1-AK7905
Summary For an Imported Workspace, whenever an existing partner is deleted,
the WSDLs in the TIBCO ActiveMatrix BusinessWorks project do not get listed when trying to add a new partner.
Workaround After importing the projects into the new workspace:
1. Open the Composite containing the BW component(s) in the text editor. 2. Locate earFile="<Workspace each BW component. 3. Replace <Workspace component.
Path> Path>/<BW Project name>"
attribute for
with the new workspace path for each BW
4. Close and re-open the Composite. DABS-447 1-9ZADG4

Summary When the Invoke Partner process is called from a Call Process dynamically, the calling process (which is a process starter) is not added to the archive. Workaround Manually add the calling process to the EAR file.
DABS-586 1-AHKQJM
Summary On using Import > Existing projects into workspace with Copy
into workspace option enabled, occasionally Global Variables are not displayed.
Workaround Use DABS Synchronize button to ensure these are available in
the Global Variables View.
64
Release Notes
Change Request ID BWSE-999 1-9MJN5E
Summary/Workaround
Summary Schemas from libraries built using the LibraryBuilder feature of TIBCO BusinessWorks are not resolved in TIBCO Business Studio. The exposed service from WSDL can not resolve the schemas and a deployable archive can not be created. Workaround Change the extension of ".projlib" to ".zip" on the disk. Remove that library from Design-time Library tab in the project. Extract the zip file on the disk and import the required resources in the TIBCO ActiveMatrix BusinessWorks project. Now delete the imported resources from the extracted folder and zip it. Change .zip to .projlib. Re-add this library again to the TIBCO ActiveMatrix BusinessWorks project.
BWSE-1032 1-9P3VGH
Summary In a Designer project, add/delete/modify actions on operation in a
PortType for the WSDL show no effect on the BWSE component side in the Composite Editor.
Workaround Validate the project and observe the errors shown on the Service agent. Manually update the changes made on the service agent for this scenario to work.
BWSE-899 1-9E6O0S
Summary When opening the Composite Editor, the following warning is
displayed multiple times in the workspace log: "Detected

recursive attempt by part com.tibco.corona.models.servicemodel.diagram.part.
Workaround None
BWSE-890 1-9DUUYT
Summary An unexpected exception is thrown in the BusinessStudio logs while
creating a Service Assembly containing a BWSE component, which is associated with a ActiveMatrix BusinessWorks Project sharing the HTTP connections configured in it.
Workaround None
Runtime BWSE-2443
Summary If you deploy a DAA containing the RV Activity Listener on a node, it may break the Monitor and Manage functionality. Workaround Before deploying a DAA containing the RV Listener activities, access the Monitor and Manage functionality on that node at least once before starting the BWSE Component.
Known Issues 65
Summary/Workaround
Summary When native Oracle 10g/11g is installed on a node, the change features fail. Workaround When you add a feature on a node, click Save and then Apply with Resolve. The system restarts the node and the feature gets provisioned on the node successfully.
BWSE-505 1-8UO6CB
Summary When a service assembly containing the EJB Connection activity is deployed in the BusinessWorks container and run for the first time, a NullPointerException is thrown if the EJB Connection is configured to use the JNDI datasource. This is because the EJBHome object for the JNDI name is not resolved. Workaround Follow these steps to run the service assembly:
1. Stop the service assembly. 2. Restart the node. 3. Start the service assembly. Note that you need to restart the node restart even if a service assembly is redeployed. BWSE-519 1-8VUD63
Summary A BWSE component containing the Invoke Partner activity is wired to a SOAP reference. If the process starter for the ActiveMatrix BusinessWorks process is a timer activity configured to run once, the corresponding service assembly runs without any errors when the timer is triggered for the first time. For all subsequent runs, the following fault message is received and the Invoke Partner activity fails:
com.tibco.matrix.amxframework.spi.MessagingException: AMX_MESSAGING_BUS-9024: Service provider is not available for endpoint [{http://www.example.com/default}Reference1].&#13
Workaround None
BWSE-443 1-8NKB09
Summary TIBCO BusinessEvents cannot be used with ActiveMatrix BusinessWorks Service Engine. A NullPointerException is thrown during the service assembly deployment if ActiveMatrix BusinessWorks interacts with TIBCO BusinessEvents to send or receive events. Workaround None
66
Release Notes
Change Request ID BWSE-374 1-8MDEDT
Summary/Workaround
Summary TIBCO ActiveMatrix BusinessWorks projects fail to run out of the
box in the ActiveMatrix BusinessWorks Container if the RV-SSL transport is configured in the project. This is because tibrvjsd.jar is not available in the classpath for the node.
Workaround Following steps explain how to update the node.tra to include
tibrvjsd.jar
in the classpath.
1. Open the node.tra for the node at the following location

TIBCO_HOME\amx\data\Environment_name\NodeName\bin\
You can update the template file for the node.tra, server.tra, at TIBCO_HOME\amx\<AMX_version>\server\bin\server.tra. 2. Append the following value to java.class.path:
TIBCO_HOME\\components\\eclipse\\plugins\\com.tibrv.rv.clien
t.fullmsg.secure.X.Y.Z.XXX\\tibrvjsd.jar (where X.Y.Z.XXX
is
the latest version of com.tibco.rv.client.fullmsg.secure 3. Restart the node. BWSE-372 1-8MBGKJ
plugin)
Summary An ActiveMatrix BusinessWorks project containing an External
Command activity that is configured to invoke an application such as MS Paint, Calc, or Notepad, when run in ActiveMatrix BusinessWorks, the external application opens and the project completes execution only when the external application is closed. However, when the same project is run with ActiveMatrix BusinessWorks Service Engine, the external application process starts, but the GUI never shows up. Also, the external application process keeps running even after the service assembly is stopped, deployed, or deleted from ActiveMatrix Administrator. You have to manually kill the external application process to remove it.
Workaround None
BWSE-679 1-972KCV
Summary When a BusinessWorks Service Unit bound to node1 is mapped to node2 after undeploying the service assembly and the service assembly then redeployed and restarted, a JVM_BIND 9093 Error is thrown on node2. Workaround Restart both the nodes before starting the service assembly on
node2.
Known Issues 67
Change Request ID BWSE-834 1-9AJM8N
Summary/Workaround
Summary Message on a queue is not picked up by the ActiveMatrix
BusinessWorks Service Engine if the node on which the BusinessWorks container is deployed is stopped while ActiveMatrix BusinessWorks Service Engine is waiting for a response and the response is placed on the queue before the engine is restarted. In such a case, if a second request is initiated and the response received, the process completes successfully. However, the first response remains in the queue.
Workaround None
Administrator BWSE-608 1-92P2CS

Summary Global variables are "flattened" when they appear in the
Administrator UI, thereby loosing the hierarchy. For example, a/b/c becomes
a_b_c.
Workaround None
BWSE-736 1-996HVC
Summary When a Service Assembly with a SOAP or JMS component is
undeployed and again redeployed, it throws the following NullPointerException:

Caught exception (java.lang.NullPointerException) executing org.apache.tomcat.util.net.LeaderFollowerWorkerThread@60376037, terminating thread
Workaround None
ActiveMatrix BusinessWorks Plug-ins BWSE-403 1-8MP3DS

Summary The BusinessWorks Integration Manager Plug-in is not supported
and cannot run with ActiveMatrix BusinessWorks in the ActiveMatrix environment.

Workaround None
BWSE-449 1-8O3HLZ
Summary Two or more service assemblies containing the TIBCO
BusinessWorks HL7 Plug-in components cannot be deployed using ActiveMatrix Administrator. Redeploying a single service assembly of the TIBCO BusinessWorks HL7 Plug-in on the same node also fails.
Workaround Restart the node before redeploying a service assembly of TIBCO BusinessWorks HL7 Plug-in on the same node.
Note that only one service assembly of the TIBCO BusinessWorks HL7 Plug-in can be deployed in a node.
68
Release Notes
Change Request ID BWSE-375 1-8MDEJP
Summary/Workaround
Summary When the ActiveMatrix project contains adapter activities, additional steps are required to configure the BWSE component in a composite. Workaround Appendix A, Configuring Adapter Projects in ActiveMatrix Design-time describes how to configure a BWSE component when the EAR file contains adapter activities.
BWSE-417 1-8MVVPM
Summary By default, adapter activities in an ActiveMatrix BusinessWorks project publish or subscribe on the following subject: %%domain%%.%%Deployment%%.adapterProjectName. While deploying the project in TIBCO Administrator, these global variables are replaced with the actual domain name and application name. Any communication with these adapter services must happen on the concrete subject, where the variables have been replaced with their actual values.
domain.BWSE_ADB.adb.ActiveDatabaseAdapterConfiguration.ADBSubscr
is an example of a concrete subject. However, when you run an ActiveMatrix BusinessWorks project in the ActiveMatrix environment, the services running in ActiveMatrix are unable to communicate with the adapter services deployed in TIBCO Administrator. This is because the global variables domain and Deployment are not replaced by the actual values.
iber
Workaround In the Deploy to an Environment perspective, replace the values of the global variables domain and Deployment with their actual values in the BW
Global Variables tab for the BusinessWorks service unit. TIBCO ActiveMatrix Administrator Key TRUP-211 Summary/Workaround
Summary If the following tModels are deleted through a UDDI server's UI,
uddi:tibco.com:admin:host uddi:tibco.com:admin:node uddi:tibco.com:admin:enterprise uddi:tibco.com:admin:environment uddi:tibco.com:admin:appfolder uddi:tibco.com:admin:application
publication will fail.

Workaround None.Those tModels, along with UDDI bootstrap tModels such
as all the tModels with key prefix "uddi:uddi.org:" should never be deleted.
Known Issues 69
Key TAP-9313
Summary/Workaround
Summary In the application wizard, if there is no suitable target application to pick for Product Distribution and you cancel the wizard, the current application still gets created. However, this application cannot be deployed and should be deleted. Workaround Delete the application after exiting the application wizard.
TAP-8060
Summary There are many WARN logs "SQL Warning: 4474, SQLState: 01000" in SystemNode log when you configure a DB2 database on an HP platform. Workaround Set the ERROR level for the logger org.hibernate.util on SystemNode, to suppress the warnings.
1. Select Infrastructure > Nodes. 2. In the Environment drop-down list, select SystemEnvironment. 3. In the Nodes list, select SystemNode. 4. Click the Configuration tab, and click Logging Configurations section. 5. Create a logging configuration with the name org.hibernate.util. 6. Add file appender and select SystemNode_ROOT in the drop-down. 7. Set the level to ERROR. 8. Click Save. 9. Click Apply. The new logging configuration will take effect and the warnings will be suppressed. TAP-7784
Summary After creating and starting a node, if you try to stop and uninstall the node when 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 one that 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 brower. This error message can be safely ignored.
70
Release Notes
Key TAP-7571
Summary/Workaround
Summary Users who have permissions only to view an application and an environment but do not have permissions to view a node are not able to see the list of selected nodes when distributing an application. Workaround Permissions to view the node have to be explicitly granted by a
superuser. TAP-7459
Summary You are unable to bind the TibcoHost instance when the Administrator server is configured with different Enterprise Message Service servers for system environment and the Notification Server. Workaround Use the same Enterprise Message Service configuration for the
system environment and the Notification Server. 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 safely ignored. 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 a JMS or SOAP/JMS binding in a deployed application does not take effect after the 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 a gadget.
Workaround Re-enter the text filter.
TAP-4645
Summary In the Dashboards > Infrastructure screens, resource instances cannot be filtered by promoted reference or promoted service. Workaround In the Application Screen, check properties of the reference or service bindings.
Known Issues 71
Key TAP-4233
Summary/Workaround
Summary (ActiveMatrix BPM only) If you have a BPM application, say appA, and you have another application, say appB, that is dependent on appA. If appB is in the Preparing for Undeploy state, upgrading appA changes the state of appB to Interrupted Preparing for Undeploy. Workaround Application appB can be reverted to the previous state by starting
the appB. 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 longer than 255. This occurs if you select the default value for CONFIG_FOLDER when running TIBCO Configuration Tool. Workaround Delete the folder using rmdir /s /q.
TAP-1669
Summary Deploying an application fails when the application name contains the following characters: \, /, :, *, ?, ", <, >,|, %, #, &, (, ), the comma or whitespace. Workaround Clear the cache of your browser.
TAP-10874
Summary Form-based Authentication should not be enabled when Administrator uses SSL. Workaround None.
TAP-10855
Summary After upgrading a replicated Administrator server, you see duplicate entries of all tabs and menu items in the Administrator UI. Workaround Restart the primary instance and make sure you are able to log into the Administrator UI before you log into or refresh the Administrator UI of the secondary instance.
TAP-10854
Summary In an upgraded environment product applications are not auto-provisioned by default. Workaround Either manually deploy the product applications or enable auto-provisioning for the environment and create a System folder for the environment.
If the product application is present in the environment but missing from the node, move the product application to the System folder.
72
Release Notes
Key TAP-10830
Summary/Workaround
Summary When wiring a reference to a service in the same application that has a SOAP binding using an HTTP Connector that does not exist results in the following exception
Error 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.
TAP-10800
Summary When creating an Administrator server with an Oracle database the following 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-10798
Summary Auto-provisioning of product applications in an upgraded
environment results in the following error message:

ApplicationFolder System (-1) was not found.
Workaround Manually create the missing System folder in each environment.
Known Issues 73
Key TAP-10781
Summary/Workaround
Summary Users with permission to an environment are not allowed to edit the messaging bus configuration. Workaround Assign superuser privileges to the users trying to edit the messaging bus configuration.
TAP-10776
Summary You are not able to save the configuration of a resource template if
the password field is left blank.

Workaround Provide a password for the resource template.
TAP-10767
Summary HTTP Connector resource instances that are referenced by properties whose names are not specific, such as HttpInboundConnectionConfig or httpConnector, are not recognized by Administrator as HTTP Connectors while displaying information. As a result these HTTP Connectors are not displayed in the Administrator UI as dependencies where expected.
Also, you can delete any such HTTP Connector even when it has dependent applications.
Workaround Use property names such as HttpInboundConnectionConfig or
httpConnect
to refer to HTTP Connectors resource instances. Additionally when deleting a HTTP Connector resource instances manually check whether other applications are dependent on it.
TAP-10751
Summary Executing the scripts generated by the DDL Script Generator for Microsoft SQL Server displays errors reporting a failure to create foreign key constraints.
Also, even if the generated scripts are not used, error messages are seen in the SystemNode log file logged in SystemNode.log regarding failure to create foreign key constraints.
Workaround None. These errors can be ignored as a failure to create foreign key constraints does not impact product functionality.
74
Release Notes
Key TAP-10384
Summary/Workaround
Summary When using SQL server, the SystemNode log file contains messages
such as:
28 Mar 2011 18:23:48,069 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: alter table [AMXDMINSRPRFRENCES_PRPERTYGRPS] add constraint AMXDMINSRPRFRENCES_PRPERTYGRPS foreign key ([USERPREFPROPERTYGROUP_E_ID]) references [USERPREFPROPERTYGROUP] 28 Mar 2011 18:23:48,069 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - There is already an object named 'AMXDMINSRPRFRENCES_PRPERTYGRPS' in the database.
Workaround These messages can be safely ignored.
PER-586
Summary DAA deployment does not update policies correctly. Case 1 DAA deployment does not fail, even though the policies associated
with it did not deploy successfully.

Workaround 1 Test for policy enforcement. If policies are not enforced for an application, then stop and undeploy the application, fix the policies, recreate the DAA, deploy the new DAA, start the application and verify policy enforcement. Case 2 Redeploying a DAA after modifying properties associated with policies (for example, Threading or Reliable Messaging) does not update previously deployed policies. Workaround 2 Undeploy the DAA, then deploy the updated DAA.
PER-583
Summary For bundled policies added in this release, if the resource instance(s) used in the 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 in Administrator, the option to generate SAML 1.1 assertion is not supported by platform policies. Workaround When configuring an LDAP Authentication resource template, accept the default setting to generate SAML 2.0 tokens.
PER-1385
Summary You are able to successfully uninstall a resource instance even if it is used by a PolicySet component. Workaround None.
Known Issues 75
Key MCR-945
Summary/Workaround
Summary In the Infrastructure Dashboard, incorrect results are displayed in the Resource Instances table when an Application is selected in the filter panel. Instead of displaying the resource instances associated to the application, the table displays all of resource instances created on the nodes to which the application was deployed. Workaround None.
MCR-876
Summary Status value is "Unknown" and uptime is empty when the same application is deployed on two nodes across environments. Workaround Change the application name during deployment. It must be unique for an enterprise for dashboard to show correct status and uptime.
MCR-800
Summary When a component reference is promoted, component reference metrics show zero values. All metrics are shown on the promoted reference and reference endpoint. Workaround View metrics on the promoted reference.
MCR-753
Summary In the Dashboards > Infrastructure screens the application request count includes requests counts from all services promoted to application level. In addition, it incorrectly includes reference invocations count from all references promoted to application level. Workaround None.
MCR-521
Summary If a node is stopped or started several times while SystemNode is down, the last stop or start time of SystemNode is used to calculate the nodes uptime percentage. Other stops and starts are missed and not used in uptime calculation. Workaround Configure the Administrator server in fault tolerant mode.
MCR-1823 TAP-10602
Summary The value for the uptime displayed in the infrastructure dashboard screens are accounted from the time a request is made to the application by invoking the 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.
MCR-1422
Summary If nodes are restarted when the SystemNode is down, the Uptime and Since Started statistics are not reset. Workaround Either make sure that the system node is running using admin replication or restart the applications for which incorrect statistics are seen.
76
Release Notes
Key MCR-1350
Summary/Workaround
Summary The number of components reported for a given node in the Enterprise Graphical View includes components that belong to the ActiveMatrix Platform Application. The Dashboard component count does not include these components. Workaround None
MCR-1226
Summary The Endpoint, Service, and References tabs display an incorrect
value for Avg Comp Process Time when extended monitoring is enabled. The value displayed is Req Comp Time.
Workaround The correct average component processing time is available in the Components and Applications tabs.
MCR-1205
Summary If the TIBCO Host is shutdown while the Dashboard is running, the following 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 be thrown in the log file. During a graceful stop of TibcoHost instance there may be some exceptions in the log file with the root cause "Caused by: java.lang.RuntimeException: Statistics aggregator is closing down, rolling back transaction". Workaround Ignore the error.
MCR-1162
Summary Statistics for Web Application components do not display in the dashboard. Workaround None.
CL-2598
Summary The Logging Policy fails to log payload data for applications where the governed object URI exceeds 255 characters.. Workaround Alter the ECOMPID table and update the size of the urn column
from 255 to 500.
Known Issues 77
Key CL-2580
Summary/Workaround
Summary (Oracle 11g only) The resource instances required by the logservice and payload service applications are not installed after running the provided scripts to create and deploy the log service and payload service to non-SystemNodes. Workaround
1. Navigate to the TIBCO_HOME/administrator/version/scripts/logging folder. 2. Edit the cl_logservice_build.xml and cl_payloadservice_build.xml files and add the following attribute to the AMXAdminTask for the install.ri target name:
options="auto-resolve"
3. Execute the scripts available in TIBCO_HOME/administrator/version/scripts/logging.
78
Release Notes
Key CL-2575
Summary/Workaround
Summary Common logging runtime, Logging Policy and Metrics Collection runtime do not work when configured to use a JMS appender for an EMS server enabled with SSL.
A non-functioning Common logging runtime, or a non-functioning Logging Policy means that the logging infrastructure on runtime nodes cannot push log records to the EMS queue and therefore no log or payload records are stored for later viewing or searching in the Log Viewer in Administrator. A non-functioning Metrics Collection runtime causes blank statistics displayed in Administrator Dashboard.
Workaround If SSL is not a mandatory requirement, enable the EMS server to listen on two ports - one secured with SSL and another not using SSL. You can then configure Common logging runtime, Logging Policy and Metrics Collection runtime to use the non-SSL port, while the rest of your communications (such as Notification transport, JMS bindings) use the EMS port with SSL.
This configuration for the Common logging runtime, Logging policy and Metrics Collection runtime to use non-SSL EMS port will actually need to be done on TIBCO EMS side, following the example below: 1. In AMX Administrator, go to Shared Objects > Resource Templates. 2. Select the resource template of type "JMS Connection Factory". The relevant resource template are typically named: TIBCO ActiveMatrix PayloadService JMSConnectionFactory Resource TIBCO ActiveMatrix LogService JMSConnectionFactory Resource TIBCO ActiveMatrix Governance JMS ConnectionFactory Resource 3. Look for the value in the field "Connection Factory JNDI Name". Typical values are "QueueConnectionFactory" and "GenericConnectionFactory".
Known Issues 79
Key CL-2575 (contd)
Summary/Workaround 4. Edit factories.conf in the TIBCO EMS configuration folder. Replace all instance of ssl:// entries with
[GenericConnectionFactory] type = generic url = tcp://7222 [TopicConnectionFactory] type = topic url = tcp://7222 [QueueConnectionFactory] type = queue url = tcp://7222 tcp://
entries as follows:
This will bind the JNDI names to non-SSL port connections, allowing Common logging runtime, Policy logging and Metrics Collection runtime to connect to the EMS server. File-based logging is not affected and you should see the log files produced as expected. CL-1924
Summary After upgrading a 3.0.x node, values for the field Expiration Time
in DB
are not shown in the log table and for a JMS log appender.
Workaround None. The Expiration Time in DB field was added in the 3.1.x release. As a result logging data coming from 3.0.x nodes does not contain this information.
80
Release Notes
Key AMX-11984
Summary/Workaround
Summary You are not able to replicate the Administrator server after upgrading from an earlier 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 from
com.tibco.amx.platform.artifactserver amx.artifactserver.app.
to
c. Change the name of the internal HTTP connector name in the substitution variable element from TIBCO ActiveMatrix Internal HTTP Connector Resource to tibco.admin.http.connector.internal. AMX-11970
Summary In a replicated Administrator server setup if you deploy to the system node applications with policies applied on them, those policies are not enforced after upgrade. Workaround First undeploy and then redeploy these applications after
upgrading all system nodes. AMX-11772

Summary If you enable the debug port on a Windows 7 (64-bit) machine using some 1.6.0 JVM versions, you could run into a JVM crash. The Windows error log shows an application level event ID 1000 in dt_socket.dll. Workaround None. This should not be an issue in production, where a debug port should not be used.
AMRP-3788
Summary The LDAP resource template pool properties are not used when initializing the connection pool. Workaround Configuring the connection pool using system properties specified for the target node applies them to all instances deployed to that node.
Refer to the Oracle documentation for more information: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html
Known Issues 81
TIBCO Business Studio Key XPD-1858 Summary/Workaround

Summary When opening a native file browse dialog on RedHat Linux for the first time, TIBCO Business Studio can crash. Workaround Type the path to the file in the text control.
XPD-1600
Summary If you drag and drop a WSDL file to another folder and move it
back, or move it to Mediation Flows folder, you cannot use the WSDL file to set the port types of services and references.
Workaround Right-click the WSDL file and select Move.
SDS-6554
Summary When displaying SOAP End-Point URLs in the Administrator Explorer the first URL is displayed for all end points. Workaround When invoking the endpoint from a Web Services Explorer (or any other tool) replace the last part of the URL with the actual endpoint url fragment.
SDS-6530
Summary If projects fails to deploy when they are deployed using TIBCO Business Studio without specifying the default port of 443. Workaround Specify the port number when connecting to the Administrator
server. SDS-6479
Summary Generating code for projects created using ActiveMatrix 3.1.5 results in NullPointer exceptions. Workaround None.
SDS-6458
Summary If you install TIBCO Business Studio 3.2 in the same location (TIBCO_HOME) as an older version of TIBCO Business Studio, you can no longer use the older version of TIBCO Business Studio. Workaround To continue using the older version of TIBCO Business Studio, install TIBCO Business Studio 3.2 in a different location, TIBCO_HOME.
SDS-5896
Summary If you create a DAA from a project that references resources in a closed project, the DAA will be incomplete and it will not be possible to create an application from the DAA. Workaround Do not close related projects before building a DAA and make sure that all related projects are available in the workspace.
82
Release Notes
Key SDS-5866
Summary/Workaround
Summary When one of the nodes participating in a high availability configuration is stopped and an application is deployed via TIBCO Business Studio, the deployment never completes. Workaround If you deploy from Administrator the application state will be partially running state instead of running - which is the expected behavior.
SDS-5848
Summary Clicking the hyperlink for a resource template name in the SOAP reference property sheet opens up incorrect reseource template with the same name. Workaround Open the resource template by going to Resource Templates
folder and double-clicking the resource template name. SDS-5780

Summary Deployment server displays connected when it is not connected.
1. Create a deployment server and validate with Test Connection, but do not check the Save Password checkbox 2. Right-click on the deployment server and select Connect. 3. You will be prompted for a password. Enter an invalid password. 4. Click OK on the authentication error message that appears. 5. In the Properties tab, the server state will display connected. 6. Right-click the deployment server. The dynamic menu option of Disconnect is displayed. However it should be Connect since you are not connected to the server.
Workaround The property sheet is not being refreshed. Switch away from the property sheet and return.
SDS-5564
Summary Exporting bundles from the workspace results in out of memory exceptions. Workaround Add -XX:+UseParNewGC to the TIBCOBusinessStudio.ini file. Additionally refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=346730.
SDS-5015
Summary When generating an Administrator CLI script if you alternate between creating two HTTP Connector resource instance names when overriding the HTTP Connector property setting, TIBCO Business Studio generates a data file that contains two ResourceInstance elements but only one matching ResourceTemplate element. When you execute the script, it fails with a resource instance does not exist error. Workaround Delete the ResourceInstance element that you dont want from under the Node entry in the data file.
Known Issues 83
Key SDS-3890
Summary/Workaround
Summary Sometimes there is an "Unhandled EventLoop Exception" in the
error log.
Workaround None. Ignore the error.
SDS-3511
Summary TIBCO Business Studio does not support substitution variables of the format %%keystoreURL%%/JKS/server-CAs.jks. Workaround Set the value in Administrator.
PER-714
Summary Multiple SOAP references deployed in a single node sending different credentials to a single SOAP service protected with Basic Authentication Policy could result in erroneous authentication failures for some of the references even if they are sending valid credentials. Workaround There are two workarounds:
Deploy these references in different nodes. or Configure these references with different HTTP Client resource instance configurations. PER-632
Summary For proper policy enforcement, every composite containing a web application component must have a different context root. Workaround None.
PER-609 PER-623
Summary Incompatible policies: UsernameTokenAuthentication and

WSSProvider.
These two policies have redundant functionality, but they cannot co-exist on the same SOAP service.
UsernameTokenAuthentication
authenticates using only the username
token in the WS-Security header.

WSSProvider
authenticates using any available information in the WS-Security header.
Both policies remove the WS-Security header from the message after successful authentication. If both policies are in effect at the same service, when the first one (WSSProvider) succeeds, the second (UsernameTokenAuthentication) must fail, because the WS-Security header is no longer available. This failure causes request messages with proper credentials to fail erroneously.
Workaround Do not apply the policies WSSProvider and
UsernameTokenAuthentication
together at the same SOAP service.
84
Release Notes
Key PER-557
Summary/Workaround
Summary The policy AuthorizationByRole does not support nested groups.
Suppose user A is a member of group B, which is a subgroup of group C. If group C has access permission to request an operation, and user A attempts to request that operation, then the request fails. That is members of group B do not inherit access permission from group C.
Workaround Configure access permissions directly in each subgroup (in this example, in group B).
AMX-8723
Summary Topic destinations are not supported for SOAP/JMS bindings but
TIBCO Business Studio does not raise a validation error.

Workaround None.
AMX-8720
Summary A composite containing a reference with a SOAP/JMS binding
cannot be run in RAD.

Workaround None.
AMX-6683
Summary Some SOAP client test tools do not generate the right WSDL
message when WSDL constructs are of Doc/Literal with the message part referring to type causing unpredictable behavior.
Workaround Use a SOAP client test tool as close as possible to the real SOAP clients for testing, rather than changing the WSDL construct to allow the test tool scenarios to work.
Limitations 85
Limitations
This section lists the limitations in the current release. Security TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.0 version does not support entrust security vendor. You can use j2se security vendor. WSDL Support Though ActiveMatrix framework allows creation of SOA Project from WSDL (that is, implement port types with Implementation Type in new SOA project), you cannot implement WSDL existing outside the BusinessWorks project in TIBCO ActiveMatrix BusinessWorks Service Engine. So expect the following behavior for the following use cases: When a WSDL is imported from SOA project or BusinessWorks project and you create new Businessworks project and Service resource, a dialog with the 'WSDL doesn't belong to BusinessWorks project' message appears and a blank component is generated. When a WSDL is imported from SOA project and you create new Service Resource in existing BusinessWorks project, a dialog with the 'WSDL doesn't belong to BusinessWorks project' message appears and a blank component is generated. When a WSDL is imported from BusinessWorks project and you create new Service Resource in different BusinessWorks project, a dialog with the 'WSDL doesn't belong to BusinessWorks project' message appears and a blank component is generated. When a WSDL is imported from BusinessWorks project and you create new Service Resource in the same BusinessWorks project, a component is created successfully. You cannot pick process and PLC For reference as component is yet to be created. So those are created with default values. Component is created with configured Service(s) and reference(s).
Basic Authentication The basic authentication feature for ActiveMatrix BusinessWorks projects can be used in the ActiveMatrix environment by setting up the TIBCO Administrator Realm in ActiveMatrix Administrator. See TIBCO ActiveMatrix Administration for details.
86
Release Notes
Policy Palette in ActiveMatrix BusinessWorks versus TIBCO ActiveMatrix Policy Manager The inbound and outbound WSS policies configured in ActiveMatrix BusinessWorks are applicable to the ActiveMatrix BusinessWorks endpoints alone. For a given service, you must ensure that policies are applied either in ActiveMatrix BusinessWorks using the Policy Palette, or in the ActiveMatrix environment using TIBCO ActiveMatrix Policy Manager. BusinessWorks Service Container The BusinessWorks Service Container in standalone ActiveMatrix BusinessWorks is not the same as the BusinessWorks container provided by ActiveMatrix BusinessWorks Service Engine. The BusinessWorks Service Container cannot be used in the ActiveMatrix environment. Support for Rules Set in ActiveMatrix Environment Rulesets for BusinessWorks processes are not supported in the ActiveMatrix environment. SOAP Service support The SOAP details configured for a SOAP service in ActiveMatrix BusinessWorks will not be applicable for messages that arrive over the ActiveMatrix bus. Publishing to UDDI Registry ActiveMatrix Administrator allows publishing to the UDDI Registry. While working with ActiveMatrix BusinessWorks projects, service endpoints can be published to the UDDI Registry only when the BWSE component is wired in the composite. Web Services Context The Web Services context activities, such as Get Context and Set Context, configured in ActiveMatrix BusinessWorks will not be available in the ActiveMatrix environment.
Limitations 87
Target Namespace for Services In TIBCO Designer, the Service resource generates a random target namespace for the concrete WSDL. When the interface is inlined, the inlined PortTypes assume the randomly generated target namespace. However, in the ActiveMatrix design-time, a BusinessWorks partner defined using an abstract WSDL cannot be wired to a Reference defined using the concrete WSDL generated in Designer. This is because the target namespaces of the PortTypes do not match. To overcome this limitation, specify the target namespace of the generated concrete WSDL source to be the same as the target namespace of the abstract WSDL Ensure that the concrete WSDL generated and the corresponding abstract WSDL, with the same target namespace, do not exist in the same ActiveMatrix BusinessWorks project. Doing so causes namespace conflicts which can result in indeterminate behavior.
88
| Appendix A
Configuring Adapter Projects in ActiveMatrix Design-time
Appendix A
Adapters expose their services in the ActiveMatrix environment via WSDLs. just as any other ActiveMatrix component. When your ActiveMatrix BusinessWorks project contains one or more adapter activities, additional tasks need to carried out to configure the BWSE component in ActiveMatrix design-time. The following steps describe how to configure a BWSE component when the EAR file contains adapter activities. 1. In TIBCO Designer, create and save an ActiveMatrix BusinessWorks project containing Adapter activities, for example Base_Project. 2. In TIBCO Business Studio, create a General project using the File -> New Project -> General -> Project menu. For example, ActiveMatrix_General_Project. 3. Import the project created in TIBCO Designer, Base_Project, into the ActiveMatrix General project created in Step 2, ActiveMatrix_General_Project. 4. Create an ActiveMatrix SOA project in Business Studio. For example, ActiveMatrix_SOA_Project. 5. In ActiveMatrix_General_Project , select the adapter configuration file. Right-click and select Generate Adapter WSDL. Select ActiveMatrix_SOA_Project in the Target Project window. The following folders are created in the ActiveMatrix SOA project directory: adapter_configuration_resources - contains the adapter WSDL file, adapter .dat file and the adapter endpoint information file.
schema
- contains the adapter XSD schema.
6. In TIBCO Designer, create another ActiveMatrix BusinessWorks project, for example New_AMBW_Project. Import the folders schema and adapter_configuration_resources created in step 5 using the File ->Import menu. The schema and adapter_configuration_resources folders are located in the Eclipse workspace on the disk. The WSDL and schema cannot be imported into the ActiveMatrix BusinessWorks project created in Designer (step 1) as the endpoints would conflict with the existing schema in the project.
Configuring Adapter Projects in ActiveMatrix Design-time 89
7. Configure the New_AMBW_Project, in the following way: a. Add a Partner Link configuration resource and configure it with the Adapter WSDL imported in step 6. The WSDL file is available under the adapter_configuration_resources folder. b. Create a process definition. In the Partners tab, add a partner to the process. c. Replace the start activity in the process with a process starter, such as a Timer or a Rendezvous Subscriber activity. d. Add an invoke partner activity to the process. e. Provide inputs to the ActiveMatrix BusinessWorks process in the Input tab. f. Save the project.
8. Create an enterprise archive (EAR) of the project New_AMBW_Project, for example New_AMBW_ProjectArchive.ear. 9. Configure the ActiveMatrix_SOA_Project in the following way: a. Import the EAR created in step 8, New_AMBW_ProjectArchive.ear, into the Service Descriptors directory. b. Open the Composite Editor, create and add a BWSE component from the imported EAR file, New_AMBW_ProjectArchive.ear. c. Add an Adapter reference in the reference section. In the General tab, browse and select the Adapter endpoint from the Adapter WSDL. d. Bind the Adapter reference with the BWSE component in the Binding tab. 10. Save and build the service assembly archive. Refer to the documentation for the steps to deploy and run the service assembly using ActiveMatrix Administrator.
90
| Appendix A

TIB Bwse 5.10.0 Relnotes

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

TIB Bwse 5.10.0 Relnotes

Enviado por

Direitos autorais:

Formatos disponíveis

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Software Release 5.10.0 August 2012

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Appendix A Configuring Adapter Projects in ActiveMatrix Design-time . . . . . . . . . . . . . . . . . 88

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

bold code font

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Table 1 General Typographical Conventions (Contd) Convention

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

| Connecting with TIBCO Resources

How to Join TIBCOmmunity

How to Access TIBCO Documentation

How to Contact TIBCO Support

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Deprecated and Removed Features 13

Deprecated and Removed Features

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Migration and Compatibility

TIBCO ActiveMatrix Administrator

Migrating Projects from 5.8.x into 5.9.2, 5.9.3, or 5.10.0

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Migration and Compatibility 15

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Migration and Compatibility 17

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.2 5.9.2 5.9.2

Change Request ID BWSE-1988 BWSE-1899 BWSE-838 1-9ARWE9

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.6.4

Change Request ID 1-8N9YDB

5.10 5.10 5.10

BWSE-2677 BWSE-2635 BWSE-2567

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.10

Change Request ID BWSE-2047

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.3

Change Request ID BWSE-3101

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.3

Change Request ID BWSE-2898

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.3 5.9.3 5.9.2 5.9.2

Change Request ID BWSE-2659 BWSE-2613 BWSE-2238 BWSE-2074 1-9DSVOO

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.2

Change Request ID BWSE-1890

TIBCO ActiveMatrix BusinessWorks Service Engine Release Notes

Closed in Release 5.9.0