TIB Amsb3x 3.1.2 Relnotes

TIBCO ActiveMatrix Service Bus Release Notes
Software Release 3.1.2 April 2011
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, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. 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 2005-2011 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information
| iii
Preface
Topics
Typographical Conventions, page iv Connecting with TIBCO Resources, page vii
iv
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention
TIBCO_HOME ENV_NAME CONFIG_HOME
Use Many TIBCO products are installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The 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. Products installed into different installation environments do not share components. Incompatible products and multiple instances of the same product must be installed into different installation environments. An installation environment consists of the following properties:
Name Identifies the installation environment. The name is appended to the
name of Windows services created by the installer and is a component of the path to the product in the Windows Start > All Programs menu. This directory is referenced in documentation as ENV_NAME.
Directory The directory into which the product is installed. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME
depends on the operating system. For example, on Windows systems the default value is C:\Program Files\tibco\amx-3. A TIBCO configuration home stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on. This folder is referenced in documentation as CONFIG_HOME. The default location of the folder is USER_HOME/ENV_NAME/data. For example, on Windows, the default location is C:\Documents and Settings\UserName\Application Data\ENV_NAME\data.
code font
Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process.
Preface v
Table 1 General Typographical Conventions (Contd) Convention

bold code font
Use 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]
italic font
Italic font is used in the following ways: To indicate a document title. For example: See 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.
Table 2 Syntax Typographical Conventions Convention

[ ]
Use An optional item in a command or code syntax. For example:

MyCommand [optional_parameter] required_parameter
vi
| Typographical Conventions
Table 2 Syntax Typographical Conventions (Contd) Convention
|
Use A logical OR that separates multiple items of which only one may be chosen. For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
{ }
A logical group of items in a command. Other syntax notations may appear within each logical group. For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
Preface vii
Connecting with TIBCO Resources
How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, 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 All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here: http://docs.tibco.com/TibcoDoc
How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please 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.
viii
| Connecting with TIBCO Resources
| ix
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii vii vii vii
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 2 3
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 7 7
Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Release 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Release 3.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
| Contents
|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 6 Deprecated Features, page 7 Migration, page 8 Closed Issues, page 11 Known Issues, page 29
Release Notes
New Features
This section lists features added since the last release of this product.
Release 3.1.2
Upgrading 3.0.x administration and runtime objects (Administrator servers, hosts, and nodes) to 3.1.2 is supported. Support for TIBCO Hawk rulebases for TIBCO ActiveMatrix Support for Microsoft JDBC Driver 3.0
JMS Support for IBM WebSphere MQ 6.0 The following properties can now be set with a substitution variable: JMS binding configuration: Operation Property, Fault Property, Durable, Durable Subscription and Message Selector JMS binding reference: Timeout
Release 3.1.0
Resource templates support obfuscated passwords.
Administrator Secure communication channels (SSL everywhere) Node management Startup modes Debugger configuration Tuning configuration Payload service Extended and basic monitoring support
New Features 3
Business Studio Administrator CLI integration Administrator Explorer view Remote debugging Support for migrating 2.x projects and shared resources to 3.x format. One-way transaction support added for JMS bindings.
Mediation Support for migrating mediation flows created in the 2.x environment to the 3.x environment.
Release 3.0.0
Out-of-the-Box policy enforcement Thread pool control and management at the individual service level Removed direct dependency on database connection New shared resources: (Hibernate, SMTP, and so on) OSGi-based container architecture Context propagation Support for intents
Administrator Component level life cycle management and control Late binding of endpoints Promotion of bindings to enterprise level Hot upgrade of components and bindings Centralized distribution of software and remote provisioning
Release Notes
All administration commands and actions are available through Ant tasks Wire services across environments Graphical view and navigation for administration objects Dashboard view for basic monitoring and management
Business Studio Composite implementation type reuse components in ActiveMatrix composites Composite debugger Declarative policy intents QOS intents At least once At most once Transacted one way Logical distribution editor Fully scriptable composite creation including create and import projects, create and distribute DAAs
Java Transaction support across multiple Java based components running within the same Java-based node (same JVM) Access to request context
Mediation Support for Intents AutoMediate Tool Support added for ANT tasks. Custom XPath functions Support for creating custom XPath functions. Improved wizards for creating custom mediations tasks.
New Features 5
Mediation Fault Path Includes a timeout fault that catches any timeouts encountered while executing the target operation. gXML: a Java API for the XQuery Data Model (XDM) and eXtensible Markup Language (XML) Processing. gXML provides a cohesive suite of XML processors including XPath, XSLT, and XQuery. Support for multiple message exchange patterns. Manage Context Access security and context information directly within mediation flows.
Release Notes
Changes in Functionality
This section lists changes in functionality since the last major (x.0.0) release of this product.
Release 3.1.2
The following are changes in functionality in this release. JMS For Context Provisioning, the following headers were gettable and settable from JMS Binding in the previous release of ActiveMatrix. JMS Headers which can be accessed by JMS service and JMS Reference: JMSCorrelationID, JMSDeliveryMode, JMSExpiration, JMSMessageID, JMSPriority, JMSTimestamp, JMSType, JMSRedelivered JMS Headers which can be set by JMS service and JMS Reference: JMSExpiration, JMSPriority, JMSDeliveryMode, JMSCorrelationID, JMSType
From this release onwards, the following JMS headers can be used to set context parameters in addition to the existing headers: JMS Headers which can be accessed by JMS service and JMS Reference: JMSDestination, JMSReplyTo
Administrator Logging configurations for the component level cannot be edited using the Administrator UI. Use the command-line tool to update the component level logging configurations.
Release 3.1.0
There are no changes in functionality.
Deprecated Features 7
Deprecated Features
This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. 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 equivalent feature.
Release 3.1.2
Support for Red Hat Enterprise Linux 4.x
Release 3.1.0
There are no deprecated features.
Release 3.0.0
Java The @Start and @Stop annotations are deprecated. For backward compatibility four life cycle eventsInit, Start, Stop, and Destroyare supported. However, since the SCA specification for Java defines only two life cycle annotations, @Init and @Destroy, only two methods are provided when a Java component implementation is generated. However, when an application or component is started, the runtime will deliver @Init and @Start events to the component. When an application or component is stopped, the runtime will deliver @Stop and @Destroy events.
Release Notes
Migration
This section explains how to migrate from a previous release to this release.
Release 3.1.2
TIBCO Business Studio Projects created using TIBCO Business Studio 3.0.x can be opened in TIBCO Business Studio 3.1.2. You can deploy applications (DAAs) developed in TIBCO Business Studio 3.0.x to nodes in the 3.1.2 environment. Projects created using TIBCO Business Studio 2.x.x can be imported into TIBCO Business Studio 3.1.2 and migrated to 3.1.2 format. For information on how to migrate projects, see Composite Development. TIBCO ActiveMatrix Administrator Upgrading 3.0.x administration and runtime objects (Administrator servers, hosts, and nodes) to 3.1.2 is supported. For information on how to upgrade runtime objects, see the installation manual for your product.
Release 3.1.0
TIBCO Business Studio Projects created using TIBCO Business Studio 3.0.x can be opened in TIBCO Business Studio 3.1.0. You can deploy applications (DAAs) developed in TIBCO Business Studio 3.0.x to nodes in the 3.1.0 environment. Projects created using TIBCO Business Studio 2.x.x can be imported into TIBCO Business Studio 3.1.0 and migrated to 3.1.0 format. For information on how to migrate projects, see Composite Development. TIBCO ActiveMatrix Administrator Upgrading 3.0.x administration and runtime objects (enterprises, hosts, and nodes) 3.1.0 is not supported. Enterprises and associated runtime objects created using 3.0.x must be recreated using 3.1.0.
Migration 9
Logging The database schema is updated automatically when the log service application is deployed. To migrate the classifier data in the same tablespace 1.
insert into "statsclassifiers"("classifierid","dtype",E_VERSION,"name","val ue") select E_ID,'StatsClassifiers',0,"name","value") from "classifier"
2.
insert into "classifiergroups"("dtype",E_VERSION,"classifiergroupid","class ifierid") * select 'ClassifierGroups',0,"baseeventformat_e_id","classifier_e_id" from "baseeventformat_classifiers"
3.
insert into "classifierbefmap"("dtype",E_VERSION,"befid","classifiergroup") * select 'ClassifierBefMap',0,"baseeventformat_e_id","baseeventformat_e_ id"from "baseeventformat_classifiers" + group by "baseeventformat_e_id"
To update and migrate data into a different table space 1. Export data from the original database and import it into the migrated database. 2. Follow steps outlined in To migrate the classifier data in the same tablespace to transfer classifier data. Downgrade from 3.1 to 3.0 To downgrade the database schema from 3.1 to 3.0:
ALTER TABLE "baseeventformat" DROP COLUMN "expirationtimeindb" DROP TABLE "classifierbefmap" DROP TABLE "classifiergroups" DROP TABLE "statsclassifiers"
10
Release Notes
Release 3.0.1
TIBCO Business Studio Projects created using TIBCO Business Studio 3.0.0 can be opened in TIBCO Business Studio 3.0.1. You can deploy applications (DAAs) developed in TIBCO Business Studio 3.0.0 to nodes in the 3.0.1 environment. TIBCO ActiveMatrix Administrator Upgrading 3.0.0 administration and runtime objects (enterprises, hosts, and nodes) to 3.0.1 is not supported. Enterprises and associated runtime objects created using 3.0.0 must be recreated using 3.0.1.
Closed Issues 11
Closed Issues
Installer Closed in Release 3.1.0 3.1.0 Key AMX-6712 INST-215 Summary When running TIBCO Configuration Tool on Solaris 10 SPARC, some crypto errors were displayed. If TIBCO Enterprise Message Service 5.1.5 and a 3.0.x TIBCO ActiveMatrix product were installed in the same TIBCO_HOME folder, running the universal_uninstall batch file in the _uninstall directory generated an error. When configuring the monitoring database, the default setting of the Max Connection field caused an exception. When you execute Administrator Server Configuration: Notification and Messaging Bus Server screens in TIBCO Configuration Tool an error is no longer thrown if you dont have administrator permission.
3.1.0 3.1.0
TOOL-364 TOOL-470
Documentation Closed in Release 3.1.2 Key AMX-8446 Summary Installation and Configuration now documents the TIBCO Enterprise Message Service configuration changes required if you do not specify the TIBCO Enterprise Message Service admin user and password when running TIBCO Configuration Tool wizards. Composite Development now states that you cannot use Web Services Explorer to invoke a SOAP request when the transport is JMS.
3.1.2
SDS-4558
12
Release Notes
Closed in Release 3.0.1
Key PER-652
Summary There were typographic errors in the policy set samples. 1. In the folder WSSProvider, the file
DecryptAuthenticateUsernameTokenAndSignatureTimestamp .policysets
contained extra nested comment markers.
2. In the folder BasicCredentialMapping, the file

BasicCredentialMappingRoleBased.policysets should contained wssp as the namespace prefix for HttpsToken instead of wsp.
These errors have been fixed. 3.0.1 AMX-6002 Administration now includes information on how to deploy an application that depends on a product application that is not contained in the ActiveMatrix platform application. Composite Development and Administration in the JMS Bindings > Use Cases sections no longer states that Out-Only and Out-In MEP are supported. These MEPs are not supported in 3.0. In the discussion of binding a host to an Administrator server, Administration now includes the prerequisite that a host must use the same notification server and must reference the same enterprise name as the Administrator server.
3.0.1
BJMS-289
3.0.1
TAP-5047
Runtime Closed in Release 3.1.2
Key AMX-7921
Summary A context parameter with header source TCP and header name remotePort or localPort is now supported when an application is distributed across more than one node. When generate a WSDL file for SOAP/HTTPS binding the file correctly references the HTTPS protocol. When an Oracle database server is restarted, reconnections are handled correctly. When an HSQLDB server is restarted, reconnections are handled correctly.
3.1.0 3.1.0 3.1.0
AMRP-2528 AMRP-2682 AMRP-2683
Closed Issues 13
Closed in Release 3.1.0 3.1.0
Key AMX-6956 AMX-7143
Summary When a node is stopped forcefully, on start up it now cleans up the OSGi cache and restarts properly. The aspectj and beans postprocessor [The version 1.5.2a has a defect in org.aspectj.lang.LangUtil] correctly identifies the version of JRE and method signature parsing for classes with generics no longer fails. An exception thrown by a service provider is now propagated back to caller in one node one-way MEP.
3.0.1
AMRP-2642
JMS Closed in Release 3.1.2 3.1.2 Key BJMS-223 BJMS-333 Summary Even when a JMS SSL connection failed, the Admin status showed application as "Running" (Deploy with Start Successful). Even when the Queue receiver and Topic subscriber were unable to start and there was an error in the node log, the Admin status showed application as Deployed successfully. If a Service binding wired to a Reference was deleted, the Save and Revert buttons on the Wires page were disabled. The Admin UI did not validate which fields were mandatory and which were not. The TimeOut value set at Endpoint level was not read at Operation level. If a JMS Resource Template was imported from TIBCO Business Studio and had substitution variables, and resource instances were created based on this template, a Null Pointer Exception was thrown at the time of installation. Substitution variables used in JMS Resource Templates did not get imported in Admin. When a JMS binding was configured with WebSphere MQ or Sonic as the JMS provider, local debugging in RAD was not supported.
3.1.2 3.1.2 3.1.2 3.1.2
BJMS-361 BJMS-391 BJMS-400 BJMS-402
3.1.2 3.1.2
BJMS-403 BJMS-549
14
Release Notes
Key BJMS-579
Summary Admin UI->Wire to binding->Wire JMS service to JMS reference: If there were two references in one composite (one created in TIBCO Business Studio and the other through Admin UI or a Reference without a binding), JMS Reference created from TIBCO Business Studio did not show up in the list of References. When the bindings were configured to use third-party JMS providers, TIBCO Business Studio allowed you to assign the JMS Transacted OneWay policy to JMS bindings. A JMS binding no longer requires an outbound connection factory even if the MEP is in-only. If a JMS reference was set up for a static reply destination, the JMSReplyTo destination is now set in outgoing messages. In the Administrator UI if you changed the state of the Enable SSL checkbox of JMS Connection Factory, JMS Connection Factory Configuration, and JNDI Connection resource templates the value now gets saved. A message is now added to the JMS error queue if the TIBCO Enterprise Message Service server crashed while processing the JMS-Java with service virtualization scenario. If a JNDI Destination name was direct.queue name/topic name a NullPointerException was seen at deployment. Inline credentials on JMS resource templates and JNDI Connection Configuration are no longer lost after being imported by the New Application wizard. If there are pending requests on JMS reference binding yet to time out, undeployment of the application or stopping of the node no longer hangs. The SonicMQ initial context factory and its default provider URL now appears in the drop-down in the JNDI Connection Configuration. When you try to create a JMS reference binding from a service binding in the Administrator CLI, you no longer see a NullPointerException.
3.1.2
BJMS-602
3.1.0 3.1.0 3.1.0
BJMS-192 BJMS-207 BJMS-268
3.1.0
BJMS-276
3.1.0 3.0.1
BJMS-282 BJMS-204
3.0.1
BJMS-208
3.0.1 3.0.1
BJMS-229 BJMS-234
Closed Issues 15
Closed in Release 3.0.1 3.0.1 3.0.1
Key BJMS-240 BJMS-244 BJMS-247
Summary It is now possible to type in the timeout value for an operation for a JMS or SOAP/JMS binding. When creating JMS or JNDI resource templates from the CLI, inline credentials are now honored. For JNDI Connection Configuration resource templates, you can now switch back and forth between username/password and identity provider credentials. It is now possible to type in the message expiry value for a JMS or SOAP/JMS binding. When you try to create a JMS reference binding from a service binding in the Administrator UI, you see no longer see a NullPointerException. When authorization is turned on for the TIBCO Enterprise Message Service server serving as the notification server, password validation no longer fails during Administrator server startup. JMS resource templates expect JNDI names for Destination, ConnectionFactory properties, and so on. The fields do not indicate that substitution variables are supported for JNDI names. However if you add substitution bindings element like <substitutionBindings template="%%SVar%%" propName="jndiName"/> to the jndi:configuration element using the AutoMediate tool or manually, deployment no longer fails and substitution works. JMS binding now propagates a message out of the composite.
3.0.1 3.0.1
BJMS-263 BJMS-264
3.0.1
BJMS-279
3.0.1
BJMS-286
3.0.1
BJMS-571
16
Release Notes
Administrator Closed in Release 3.1.2 Key AMRP-2540 Summary When the JVM arguments for a node were updated using the Administrator UI, the node stopped issuing notification messages after a restart. When a DAA that contained a Teneo resource was undeployed and then immediately redeployed, the application that used the Teneo resource resulted in errors when accessing the resource. When you invoked Infrastructure > Software Management > Apply and Resolve for database drivers to SystemNode, sometimes SystemNodes would crash with an out of memory error. This issue was caused by perm-gen space on Administrator being exceeded The Log Viewer is now able to find the updated Teneo resource instance if it is changed or renamed. You can now have more than one logservice instance in a given environment. You can now have more than one payload service instance in a given environment. The resource instance name for the httpConnector when deploying a non-default logservice has to be amxAdminDefaultHttpConnector. The resource instance name for the httpConnector when deploying a non-default payload service no longer has to be amxAdminDefaultHttpConnector. The Export button in the Log Viewer now works as expected when exporting more than 100K records. The SystemNode no longer runs out of memory if message processing slows down resulting in a large number of messages being queued.
3.1.2
AMRP-2779
3.1.2
AMRP-2842
3.1.2 3.1.2 3.1.2 3.1.2 3.1.2
CL-1773 CL-1816 CL-1818 CL-1820 CL-1822
3.1.2 3.1.2
CL-1824 MCR-1017
Closed Issues 17
Key MCR-1190
Summary In the Dashboard Components page, Ref Invoc, Ref Invoc Time, and Ref Invoc Rate metrics for a component reference were empty when a component reference was wired to another component service, and component reference name was not identical to component service name. Reference invocation and reference invocation rate metrics were not available in the Dashboard's Components gadget. Dashboard - > Infrastructure -> Components -> Component Instances : The "Availability" metric in the component instances gadget always showed 0%. The TIBCOHost instance would hang during the shutdown process. If a machine was put in stand by/hibernate mode and then restarted the performance statistics aggregator did not process the messages from the TIBCO Enterprise Message Service server queue. When a component threw undeclared faults, the following components metrics were invalid: - Requests Queued: shows the request as queued until next node restart - Faults, %Success, Requests Dispatched, Responses, Response Time (Avg), Fault Rate, Success, Request Rate, Comp. processed Rate: do not include statistics from requests resulting in undeclared faults.
3.1.2 3.1.2
MCR-1196 MCR-1231
3.1.2 3.1.2
MCR-1243 MCR-659
3.1.2
MCR-717
3.1.2
MCR-816
The performance statistics aggregator application did not reconnect to the TIBCO Enterprise Message Service server if the TIBCO Enterprise Message Service server was not configured for fault tolerance and the server shut down. Applications that got into an unrecoverable intermediate state could not be deleted from the Administrator GUI. An SMTP resource template did not accept a substitution variable for the port number with a dot(.) in it. For example, %%smtp.port%% did not work. An HTTP client resource template did not accept a substitution variable for the port number with a dot(.) in it. For example, %%http.port%% did not work.
3.1.2 3.1.2
TAP-1605 TAP-1616
3.1.2
TAP-1619
18
Release Notes
Key TAP-4771 TAP-4797
Summary Undeploying an application that has property that referenced a Teneo resource instance failed. After changing columns displayed in a dashboard gadget or gadget refresh time, sometimes an error dialog would be displayed. In addition there would be an entry in the node log for SystemNode with a stack trace having an ultimate cause of: Caused by: org.hibernate.NonUniqueResultException: query did not return a unique result: 2.
3.1.2
TAP-4813
When a binding was contained in a logical node, promoting the reference using the binding to the environment was not allowed because the binding was deleted. "Error in dashboard "tibco.dash.Error.Requesttimeout" window poped up when you accessed Dashboards > Infrastructure. This happened the first time you went to the dashboard regardless of whether or not the aggregator was available, if the aggregator applicationwasnt running, your session timed out, or the SystemNode stops or became unavailable. Permissions were not honored in the Dashboard if multiple users accessed Administrator from the same browser. You could not deploy Monitoring applications in the replica server. When replicating Administrator server a CLI action had to be changed from set to add so that the deployed applications were distributed both in the system node and the replicated system node. On unwiring a JMS or SOAP service from a JMS or SOAP reference, name of the reference binding remained that of the service. A StaleObjectStateException was thrown while installing mulitple nodes if the Administrator server was replicated and used the internal HTTP connector that was configured to use a load balancer URL. When deploying applications if some nodes are offline, warning messages are now issued in the Administrator UI and the command line scripts. The Action Status dialog now includes a time stamp for the pending tasks and actions.
3.1.2
TAP-4873
3.1.2 3.1.2 3.1.2
TAP-4939 TAP-5665 TAP-5667
3.1.2 3.1.2
TAP-5688 TAP-5751
3.1.2
TAP-5858
3.1.2
TAP-6052
Closed Issues 19
Closed in Release 3.1.2 3.1.2 3.1.2 3.1.2 3.1.2 3.1.2
Key TAP-6057 TAP-6085 TAP-6095 TAP-6253 TAP-6573 TAP-660
Summary Any errors encountered when undeploying components are now reported. An incorrect URL to the published WSDL was registered in UDDI Registry. If you tried to upgrade an application with a new component resulted in Composite Merger errors. When binding to a host using the Administrator UI sometimes resulted in exceptions which resulted in the host screen to go blank. If you undeployed a plug-in that was already undeployed and deployed, the Administrator server did not restart automatically. The following issue was observed in Administrator when reconnecting to a Tibco Host process after the host instance was restarted, but its node processes were running. There were two cases: 1. SystemHost. Reconnect did not work. 2. The automatic reconnection for other hosts happened only after the first user action failed. This issue is now fixed.
3.1.2 3.1.2
TAP-6809 TAP-6687
When creating a node, sometimes an Instance with session error was seen.
not associated
If you added a JMS or SOAP/JMS binding to a service or reference, the JMS Connection Factory and JMS Destination resource instances that were already installed on a node did not display in the picker when you configure the binding. If the TIBCO Enterprise Message Service server using for the message bus is unavailable, the application runtime state no longer shows Lost Contact or Unknown. Applications now reconnect to the Enterprise Message Service server after initially loosing connection. The installation of an application resulted in errors if the description of the application exceeded 255 characters.
3.1.2
TAP-683
3.1.2 3.1.2
TAP-6862 TAP-6869
20
Release Notes
Closed in Release 3.1.2 3.1.2 3.1.2 3.1.2 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
Key TAP-6884 TAP-7503 TAP-7733 TAP-6740 CL-1380 MCR-572 MCR-732 MCR-802 TAP-3735 TAP-4181
Summary A SOA project that used a Keystore Credential Provider resource template failed to launch successfully in RAD. Adding permissions for an existing LDAP group no longer fails. Searching for LDAP users was slow and caused time outs when indexes were not set. For a service, clicking Binding > Generate WSDL resulted in errors. The Log Viewer is now able to query logs from the database after configuring a JMS appender for SystemNode. In the Dashboard > Infrastructure screens, Request Queued metric now always resets to zero after the requests have been processed. The since started time period now restarts when the application or node is restarted. Dashboards > Infrastructure. The Average Comp Process Time on Application tab is no longer always 0. For Firefox 3.6 versions greater than 3.6.5 the interaction with the Enterprise Canvas is now workable. If resource instances were mapped to nodes through New Application wizard, the instances had to be manually installed on nodes before deploying. Administrator can now deploy DAAs created from projects or composites that have spaces in their names. When session timed out or servers become unavailable instead of showing timeout the Dashboard > Infrastructure screen did not display any data. When you clicked an icon in an environment under Infrastructure > enterprise graphical view, an exception is no longer thrown. While resolving dependency warnings for resource instances, after selecting the resource template names for the resource instances and saving them, the wizard again gave dependency warning.
3.1.0 3.1.0
TAP-4465 TAP-4602
3.1.0 3.1.0
TAP-4798 TAP-4910
Closed Issues 21
Key TAP-4959 TRUP-253
Summary In some cases the gadgets in a Dashboard screen would show up as empty. A service "xxx" is a promoted service and is included in the application, the service is also published in multiple registries, not just the primary registry (primary registry is the one that has auto-publish checkbox enabled when you adding a UDDI registry). In the application upgrade case, if the promoted service was removed from a new DAA, and the new DAA was uploaded in the original application, in the UDDI tab of the application, the service "xxx" was marked as deleted, but the Apply Change button in the UDDI tab was disabled. For primary registry, if you deployed the application again, the service was automatically unpublished from the primary registry. However, if the service was also published in a non-primary registry, there was no way to unpublish it because the Apply Change button was disabled. The Apply Change button is now visible.
3.0.1
AMRP-1681
If a WSDL files schema has schema import, and the referenced schemas schema components are not used within the WSDL files schema section directly (but are used at the WSDL level, for example at the WSDL part level), the schema components from the imported XSDs are now resolved completely at the top level WSDL. When a SOAP service or reference and a component are deployed on two different nodes, and the faultcode, faultrole are used through faultcontext mapping, theres no longer a serialization issue for across node communication in this specific case. On Windows (NTFS) the maximum file name length is 226 characters and on Linux (ext4fs) the maximum file name length is 226 bytes. ActiveMatrix uses application name, component name, nested composite name, service name and reference name as part of created folder and file names. If the maximum file length limit is exceeded, a java.io.FileNotFoundException is no longer thrown when applications are deployed. If the endpoint URI of a SOAP/HTTP binding is configured as /abc/ then all URIs beginning with /abc/, for example, /abc/def , /abc/def/xyz are no longer processed.
3.0.1
AMRP-2090
3.0.1
AMRP-2112
3.0.1
AMRP-2147
22
Release Notes
Key CL-1308
Summary A SystemNode logging configuration can now be configured to use a JMS appender. The log service runs inside SystemNode. If SystemNode's logging configuration is changed to use JMS appender, then an infinite loop will form. Model extensions logs to a JMS appender no longer fail. When an Administrator server is configured to use the Oracle database, a ClassNotFoundException is no longer thrown in the node log during node shutdown or startup. You can now have multiple log services on multiple nodes running in the same Administrator server. After a several hours of persistently hitting services, the aggregator application no longer throws an OutOfMemoryException due to excessive garbage collection time. Administrator now warns if component properties are mapped to resource instances that are not existing on runtime node. Substitution variables used in the Connection Properties section of the JDBC XA resource template configuration are now being substituted by Administrator. WS-Addressing can now be enabled while adding or editing SOAP/HTTP binding in the Administrator UI. The header columns in case of Component details page in the Dashboard now show correctly. A host bound by a user who isn't superuser can now be seen by that user.
In a Keystore Provider resource template, once you select a Provider
3.0.1 3.0.1
CL-1313 CL-1315
3.0.1 3.0.1
CL-1319 MCR-792
3.0.1 3.0.1
TAP-1603 TAP-3900
3.0.1 3.0.1 3.0.1 3.0.1 3.0.1
TAP-4098 TAP-4637 TAP-4707 TAP-4740 TAP-4761
Name, it can now be undone. Administrator no longer displays a success message if you select Infrastructure > Hosts > hostname > Security > Enable Secure Management Communication if the Administrator is not running TIBCO Credential Server.
Closed Issues 23
Key TAP-4777
Summary When the components are distributed manually through the Administrator UI from the Distribution tab, and Save button is clicked the "Saving Data" message now resolves to green to say "Changes are Saved ..". While starting a node, you no longer observe java.io.FileNotFoundException: http://hostname:port/amxadministrator/svn/trunk/artifacts/keystore /admin_default_keystore.jceks in the node log. After upgrading an application, the application deployment no longer goes into the waiting for dependencies state. Dashboards > Infrastructure. Picking items in the filter list that are of the same type as the list being displayed is no longer ignored. Deployment no longer fails if a malformed feature is provisioned to a node. When running with Microsoft SQLServer the Administrator server no longer becomes slower in responding after some time. An exception is no longer thrown if you change multiple properties on JMS binding at the same time. Sometimes node no longer goes into unrecoverable state if install/uninstall is performed several times and the node cannot be force deleted. The Administrator UI now allows wiring a reference to service if the reference has intents. The CLI samples copied
CONFIG_FOLDER/admin/enterprisename/samples folder now work as
3.0.1
TAP-4809
3.0.1 3.0.1 3.0.1 3.0.1 3.0.1 3.0.1
TAP-4834 TAP-4835 TAP-4893 TAP-4899 TAP-4902 TAP-4919
3.0.1 3.0.1
TAP-4922 TAP-4929
is. 3.0.1 3.0.1 TAP-4949 TAP-4963 Life cycle actions from the Dashboard screens now work. In the New Application wizard, when you upload a DAA that is a different version of existing DAA, the wizard no longer displays a duplicate application error. When the Administrator Infrastructure dashboard link was clicked, a error was thrown repeatedly.
3.0.1
TAP-5003
RequestTimedOut
24
Release Notes
Key TAP-5018 TAP-5040
Summary Inline credentials are no longer lost after importing them from TIBCO Business Studio. Composite level references with policy intents and policy set attributes can now be mapped to virtualization bindings in the Administrator UI.
Business Studio
Closed in Release 3.1.2 3.1.2 3.1.2
Key SDS-3666 SDS-4560 SDS-4496
Summary Code generation no longer fails when the schema location in the WSDL file contains spaces. Wiring from a topic that has been converted to an abstract component to Java components is no longer lost during migration. If you click Test Connection when creating a deployment server and the Administrator is enabled for SSL, the certificates are downloaded and then an error no longer displays saying that the certificates are not trusted and the connection fails. A composite no longer fails to migrate when there is composite service wired directly to composite reference and both are configured with in-only WSDL file. When generating an Administrator CLI script the Generate button is no longer disabled when you select only the Start Application action (unchecking the Upload and Configure actions). Services with a WSDL port type with parts defined by a complex type can now be used in local or remote debugger. If used the debugger in the node will become unusable. After you migrate a composite, the editor containing the message you must migrate a 2.x composite no longer remains open.
3.1.2
SDS-4561
3.1.2
SDS-4547
3.1.2
SDS-4530
3.1.2
SDS-4543
Closed Issues 25
Key SDS-4419
Summary You no longer encounter a provisioning failure when running an Administrator CLI script generated by Studio if you specify Resolve Mode when you generate the script. When generating an Administrator CLI script, if a DAA contains a resource template that matches an existing template already on the server, any option no longer overwrites the existing template with the one from the DAA. When adding a new database driver definition in Windows Preferences > Data Management > Connectivity > Driver Definitions > Oracle Thin Driver, it will be created with the same driver class name than that of a JDBC Resource Template. When working disconnected from the Internet builds no longer take very long time due to validation of the composite. A mediation component no longer receives a null message for the scenario where a SOAP header is declared for WSDL operation output, but no context parameter mapping is done for output SOAP header. If a WSDL message part was of simple type then the debugger would throw a NullPointerException. If you had a composite which was referred to by a distribution file and you renamed the composite file, then a transaction exception would occur and was shown in an empty editor. Generating a WSDL file when the transport is HTTPS is now supported. After changing value of the JMS Inbound Destination of a SOAP/JMS binding, the field is no longer mandatory even if the value has been changed back to an empty string. When there were multibyte characters in a generated concrete WSDL, you could not use the WSDL file because of encoding issues. After changing the name of the composite, a launch configuration that references the composite no longer shows composite unresolved and an error that composite was not found in the workspace.
3.1.2
SDS-4304
3.1.2
SDS-3770
3.1.2 3.1.2
SDS-4500 SDS-4439
3.1.0 3.1.0
AMRP-2156 SDS-2953
3.1.0 3.1.0
SDS-3055 SDS-3654
3.1.0 3.0.1
TXML-87 SDS-1415
26
Release Notes
Key SDS-3513 SDS-3630
Summary SOAP bindings now retain context mapping settings. In the Create deployment archive wizard unrelated features will be packaged in the same DAA even if added explicitly through the wizard. WSDL files with a JMS bindings now show graphically on the WSDL editor. TIBCO Business Studio is configured to compile plug-in projects against the TIBCO Host runtime environment instead of the target platform against which Business Studio is running. However this configuration is not a suitable development environment if you want to do Eclipse plug-in development. If attempt to launch an Eclipse application for debug from Business Studio then the exception below will no longer be seen. java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
3.0.1 3.0.1
SDS-3632 SDS-3665
3.0.1
SDS-3711
When you run the TIBCO Business Studio CLI it no longer prints many unrelated log entries on the console.
Mediation Closed in Release 3.1.2 Key MED-2412 Summary The option Migration from AMX 3.0 format appeared on the popup menu for the mediation resource in the Project Explorer even for 3.x mediations.
Closed Issues 27
Key MED-2420 MED-2425
Summary Mediation flows that contained context parameters did not retain the correct input mapping upon migration. After migration, the mediation components did not retain the correct references to the mediation implementation after you closed the project or re-started Business Studio. A MOZILLA_FIVE_HOME not set or MOZILLA_FIVE_HOME libraries not found error was seen during design time when there was a mismatch of Mozilla libraries on a 32-bit or 64-bit RedHat Linux machines. The Endpoint Reference option, which is not support, is no longer available in the drop-down list of the Set Dynamic Reference task. The unsupported Java primitive type byte is no longer available in the Custom XPath Wizard. The mapper tree in the Catch All path of Catch Target fault did not contain the Timeout fault message when you unchecked the checkbox for the Timeout fault path. Error markers appeared on all input and output flow paths when there was a data mismatch on at least one of the paths. The AutoMediate command line tool used incorrect values for the and -httpConnectorName configuration parameters.
3.1.2
MED-1698
3.1.0 3.1.0 3.0.1
MED-1844 MED-1702 MED-1538
3.0.1
MED-1738
3.0.1
MED-1852
-servicePort
3.0.1
MED-1875
When a ActiveMatrix BPM component was wired to a Mediation component and if the WSDL message contained a part referring to a simpleType, data loss was observed in message data of the Mediation exchange. Processing unbound SOAP headers resulted in a Null Pointer Exception. ActiveMatrix BPM process failed to invoke BW projects via the Mediation flow.
3.0.1
MED-1878
3.0.1
MED-2026
28
Release Notes
Key MED-2017
Summary While building a request with Declared unbounded request the Mediation component incorrectly added a Message Part name and Element name as part of the SOAP Header. Invoking the fault path of a target service circularly through Invoke tasks on the Mediation fault path resulted in com.tibco.amsb.core.task.rt.MediationTaskFault exceptions.
3.0.1
MED-1186
Known Issues 29
Known Issues
The tables in this section list known issues in this release. Installer Key AMX-8669 Summary/Workaround
Summary After uninstalling 3.1.2 after installing on top of 3.1.1, a TIBCO Host instance will no longer start. Workaround Avoid doing an uninstall of 3.1.2 after installing on top of 3.1.1. If you have already done the uninstall, you can restore your environment by re-installing 3.1.1 again (in the same TIBCO_HOME).
INST-164
Summary The TIBCO Universal Installer does not display the products to be installed correctly. Workaround Note the discrepancies. There is no action required.
SDS-4837
Summary After installing 3.1.2 and before upgrading runtime objects, you cannot launch 3.0.1 or 3.1.2 TIBCO Business Studio. Workaround Install the SOA Development profile in a new TIBCO_HOME and in a different TIBCO_HOME from where you install the Runtime Host and Administration profiles.
SDS-4967
Summary While installing on Solaris 10 x86 a warning displays that "BusinessStudio installation has failed" and there is a "FileNotFound" error in the Ant log file. Workaround Ignore the error.
TOOL-889
Summary TIBCO Configuration Tool should be more flexible when validating third-party JDBC URLs. It only accepts a / before the Oracle SID, but should accept a : . Workaround Specify a / before the Oracle SID.
30
Release Notes
Documentation Key AMX-8655 Summary/Workaround

Summary Administration and Composite Development should report that
application names should not have the characters \, /, :, *, ?, ", <, >,|, whitespace, %, #, &, (, ), and comma.
Workaround None.
AMX-8646
Summary In Installation and Configuration the mediation.app property should be for the target upgrade-node instead of the target upgrade-admin. Workaround None.
AMX-8648
Summary In Composite Development should document the Upgrade Existing
Application checkbox for the Generate Administrator CLI wizard as follows: For an online server, the checkbox is enabled and checked when the application already exists and disabled if the application does not exist. For an offline server it is always enabled. When the checkbox is checked, the wizard generates an upgrade.app target that invokes the Administrator CLI upgrade action. When the checkbox is unchecked, the wizard generates a create.app target that invokes the Administrator CLI add action.
Workaround None.
BJMS-800
Summary Composite Development and Administration incorrectly includes the
Timeout field at operation configuration level.

Workaround Starting from this release, the Timeout field exists only for
reference. For a service, add a thread policy on a JMS service binding and set a timeout in the policy configuration. BJMS-805
Summary Installation and Configuration, Composite Development, and
Administration do not mention that JMS resource templates can be enabled for SSL only when using TIBCO Enterprise Message Service.
Workaround None.
SDS-5008
Summary Administration and Installation and Configuration should refer to instanceName rather than hostName in the path to a host executable or log. instanceName is the name specified when a host is created in TIBCO Configuration Tool. hostName is the name specified when the host is bound to
the Administrator server.

Workaround None.
Known Issues 31
Key SDS-4601
Summary/Workaround
Summary Composite Development should say that to resolve the error that Java component's Java resource is out of sync with the file system which occurs when you open an SOA project in a new version of TIBCO Business Studio you should reset the target platform as follows:
1. Select Windows > Preferences >Plug-in Development > Target Platform. 2. Click Browse... and go to the TIBCO_HOME/components/shared/1.0.0 folder. 3. Click Apply, then click OK.
Workaround None.
TAP-6711
Summary Administration should say that you should contact TIBCO Support to reset a lost superuser password. Workaround None.
TAP-7768
Summary Administration should document the following runtime states for a
node:
Stopped The node was explicitly stopped. This is a normal and expected
condition. Stopping a node is expected to be a quick activity. If the node is stuck at Stopping for more than a few minutes, checking the logs may indicate the problem.
Start Failed The host was not able to start the node process. Possible causes are that the node_classpath.tra file contains errors, the JRE libraries are not found, or the OS is not able spawn additional processes. After this state the node is disabled and must be manually enabled.
Workaround None.
TOOL-910
Summary Installation and Configuration should provide AIX configuration
steps: 4. Login as root and run:

#chdev -l sys0 -a ncargs=16
Otherwise, a tibcohost executable fails to start on AIX reporting the error: Failed to exec process : Arg list too long : ./tibcohost.
Workaround None.
32
Release Notes
Key TOOL-733
Summary/Workaround
Summary Installation and Configuration should state that the keyStoreLocation attribute value in KeyStoreResource target in integration_create_admin_data.xml should be edited before creating an Administrator server with SSL using TIBCO Configuration Tool script. Workaround None.
Runtime Key AMRP-2775 Summary/Workaround

Summary Virtualization queues are created by Messaging Bus when components are deployed on node. These queue are shared between nodes when same component is distributed across them. During undeployment of the component, queues created are not removed. Workaround Manually clean up and remove the queues.
AMRP-2807
Summary JAXB data binding does not correctly handle WSDL message parts that
use the primitive binary types: hexBinary and base64Binary.

Workaround None.
AMRP-3142
Summary WSDL port types with an operation named with a Java keyword are not supported. The following exception will be thrown at runtime:
java.lang.IllegalArgumentException: TIBCO-AMX-CF-009000: Cannot create a Java identifier for the Java keyword, "new".
Workaround Rename the operation in the WSDL port type.
Known Issues 33
Key AMRP-3215
Summary/Workaround
Summary Changing the JMX security settings on a TIBCO Host instance and its nodes may run into a erroneous situation on the host. The host process appears to be stalled and the nodes are in STARTING state. Stopping the host via command line may also fail. Workaround
1. Manually stop the host process and all node processes. 2. Go to the CONFIG_HOME/tibcohost/instanceName/ nodes/nodeName/configuration folder and open the jmxenvironment.properties file. 3. Change the property .secure=true to .secure = false. 4. Restart the host. It will restart all the nodes in insecure mode. You can then attempt to change the JMX configuration again. AMRP-3218
Summary If you try to secure the JMX communication between TIBCO Host instance and its node while one or more of the nodes are offline, the host will not be able to communicate with the offline nodes once they are brought back online. Workaround Start all nodes before applying the JMX changes.
DSS-527
Summary Heterogeneous environments with mixed JREs are not supported. Sun
JRE is not compatible with IBM JRE when it comes to storing secret keys in a Java keystore. This causes a problem when the Administrator server running on Sun JRE stores a username and password in its global identity keystore and a host and node running on IBM JRE attempts to access that username and password. The reverse, Administrator on IBM JRE and host and node on Sun JRE would have the same problem.
Workaround Ensure that Administrator, TIBCO Host instances, and nodes are all using JREs provided by the same vendor.
JMS Key BJMS-139 Summary/Workaround

Summary If you rename an operation in a WSDL file, JMS bindings on composite services and references are not updated correctly. Workaround Create new JMS binding after renaming the WSDL operation or re-assign the WSDL file to existing JMS binding.
34
Release Notes
Key BJMS-203
Summary/Workaround
Summary When the JNDI name of the resource instances supporting a SOAP/JMS binding are not provisioned in the TIBCO Enterprise Message Service, the behavior is different for SSL and non-SSL connections. When the connection is non-SSL, lookups fail but the application deploys.When the connection is SSL, the lookup fails and the application deployment fails too. Workaround Check the node logs to see if the resource instance installation was
successful. BJMS-209
Summary A mismatch of data types for IN and OUT messages between a client and a JMS service or reference results in a misleading exception: The message will be rolled back. Workaround Ignore the exception message.
BJMS-238
Summary JMS bindings do not allow you to select header or property name for Bag and Message context parameter types in the Context Variable Mapping screen. Workaround None. JMS bindings do not support those property types.
BJMS-246
Summary JMS reference that uses a SonicMQ JMS provider hangs after one processing one message. Workaround None.
BJMS-332
Summary When a resource instance is created from a resource template with
bad configuration, no error is reported on resource instance installation. It does so only when used from an application.
Workaround Deploy an application using the resource instance to detect if the configuration is incorrect via Admin Status.
BJMS-355
Summary When a JMS service is deployed in LB setup over routed queues, the "'javax.jms.IllegalStateException: Not allowed to use transacted session on routed queues" message is displayed and the service does not start. Workaround Enterprise Message Service does not support transactions on routed queue consumers. Enterprise Message Service 6.0 added an explicit check to prevent this. You can restore the old behavior by setting the following main configuration parameter:
allow_unsupported_tx_routed_q_consumers = true
Known Issues 35
Key BJMS-417
Summary/Workaround
Summary After unwiring a JMS service from JMS reference, reference properties do not get deleted. Workaround None. Summary JMS Connection Factory Configuration and JNDI Connection resource instances do not check the connection to JMS server at the time of resource instance installation. Workaround Ensure that JNDI names are bound to appropriate connection factories, topics, or queues on the source/target JMS server.
BJMS-546
BJMS-547
Summary JMS Destination and Destination Configuration resource instances
do not check the connection to JMS server at the time of resource instance installation. Ensure that JNDI names are bound to appropriate connection factories, topics, or queues on the source/target JMS server.
Workaround None.
BJMS-603
Summary Administrator does not validate that an application with JMS Transacted One-Way policy set should be deployed on a single node. Workaround Ensure that the JMS binding that has a JMS Transacted One-Way Policy is deployed on the same node as that of component(s), it is wired to.
BJMS-610
Summary When migrating JNDI application properties and JMS resource templates that are configured for SSL to 3.x, the SSL configuration does not get migrated. Workaround Manually recreate the configuration.
BJMS-636
Summary The show connection command in the TIBCO Enterprise Message
Service administration tool ems-admin doesn't contain "ClientID" value for connections created by JMS resource instances for outbound connections.
Workaround None.
BJMS-640 and BJMS-764
Summary Application does not get undeployed successfully after EMS crashes. Workaround Undeploy the application forcefully, uninstall the connection factory shared resource, install it, and deploy the application.
36
Release Notes
Key BJMS-641
Summary/Workaround
Summary Deploying a new application containing a JMS reference binding
after restarting Enterprise Message Service referred from JMS Connection Factory resource instance fails with 'IllegalStateException: Connection is being closed' in the node log.
Workaround Uninstall and install the JMS Connection Factory resource
instance. BJMS-645
Summary If a node crashes while a transaction is running on node start up, the redelivery count is set back to 'zero'. Workaround None. The application may deliver JMS messages more times
than that configured in the policy. BJMS-652

Summary When migrating a 2.x project having JMS resource templates to 3.x, the following substitution variables are not migrated:
Connection Factory JNDI Name in Connection Factory Configuration and Connection Factory resource templates Service/Reference target and reply destinations which get migrated to JMS Destination resource templates, do not have SVar set for 'Destination' field.
Workaround Re-create the substitution variables manually.
BJMS-654
Summary Redelivery does not work for applications with topics. Message is redelivered infinitely without observing the configured redelivery delay interval. Workaround None. Use JMS queues whenever possible, if redelivery is
required. BJMS-718
Summary For JMS Binding, the SDS UI allows you to set Context Parameters of type Message. This is not supported for JMS Binding. Workaround Do not use type Message for Context Provisioning related to JMS
Binding. BJMS-726
Summary On re-starting Enterprise Message Service, for in-flight messages, transaction does not get committed. Re-delivery happens and message is forwarded to error queue. Workaround Recover the requests from the error queue.
Known Issues 37
Key BJMS-734
Summary/Workaround
Summary Timeout setting in JMS Binding Reference is redundant. Ideally,
Thread Policy must be set on the component reference and the framework should trigger timeout from the component reference.
Workaround Either, do not use the Thread Policy on component reference in case of JMS Binding Reference, or set timeout on JMS Binding Reference lower than that of Thread Policy on component reference.
BJMS-736
Summary When a 2.x project containing a JMS binding is migrated to 3.x the JNDI resource template required for looking up the destination are not created and the generated warning does not clearly state that JNDI resource templates need to be created. Workaround Manually create JNDI resource templates required for defining inbound and outbound destination configurations.
BJMS-753
Summary A Websphere MQ 7 JMS driver installed via TIBCO Configuration Tool does not work with Websphere MQ 6.0 server. Topic on Inbound side does not deploy and a NullPointerException is thrown in the MQ client library. Message exchange does not happen. Workaround Use the latest Websphere MQ 7 client libraries from the 7.0.1.3
installer. BJMS-755
Summary Enterprise Message Service XA Resources from orphaned transactions do not disappear after transaction timeout from Enterprise Message Service server. They are seen on the Enterprise Message Service server as a part of show transactions command. Workaround Re-start the Enterprise Message Service server. As there is no locking in messaging associated with an XA resource, this issue is not serious.
BJMS-762
Summary For JMS Resource Templates with credentials (JMS ConnectionFactory Configuration, JMSConnectionFactory, JNDI Connection Configuration), the Restore Defaults button does not work after credentials type is changed from inline to referenced. Workaround Cancel creation of the resource template and create a new one.
BJMS-763
Summary For a JMS Transacted OneWay policy, when Enterprise Message Service is restarted after a crash and the transaction commit fails, the reason in the error message is missing. Workaround None.
38
Release Notes
Key BJMS-781
Summary/Workaround
Summary For cases where you do not want to authenticate against a JMS server, a RAD node does not accept a null Identity Provider in JMS resource instances. Workaround Use inline credentials with a blank username/password instead.
BJMS-786
Summary For JMS Transacted OneWay policy, configuration (Maximum Redelivery Count, Redelivery delay interval, error queue, and list of exceptions to stop redelivery) is ignored on the reference side. Workaround None.
BJMS-806
Summary An application that has a JMS reference wired to a JMS service of another application does not get deployed completely. Workaround None.
Administrator Key AMRP-2357 Summary/Workaround

Summary Administrator server creation with Oracle 10g database server fails
when an Oracle 10g JDBC driver is used.

Workaround Configure the Oracle 10g database server with the Oracle 11g
JDBC driver. AMRP-2805

Summary On Microsoft Windows, the HTTP connector does not flag port conflicts resulting in several connectors being started with the same port number at runtime. No errors are reported and all connectors are in the running state. Workaround None. You cannot have more than one HTTP connector with the
same port. AMX-5860

Summary Every Administrator server requires a different TIBCO Enterprise Message Service server. Workaround None.
Known Issues 39
Key CL-1303
Summary/Workaround
Summary If you use HSQLDB as the log service database, and you set the logging level of an logging configuration to Debug, the database will crash. If you use Oracle 11g and MSQL 2008 server for the log service database with a Debug log level, performance will degrade. Workaround Specify the cache parameter for the DB URL which is valid for only HSQL-DB jdbc:hsqldb:hsql://localhost:1234/amx1;hsqldb.default_table_type=cached.
CL-1651
Summary When you run the TIBCO Configuration Tool you see the following error message in the systemNode log file:
TIBCO-AMX-HPA-014212: Failed to lookup shared resource java:cl_logservice_jmsDestionation javax.naming.NameNotFoundException: Name not found: 'cl_logservice_queue
Workaround None. This error can be safely ignored.
CL-1771
Summary The logservice, by default, uses the same default database as the Administrator on the system node created by TCT. This default database is an in-process database which is unaccessible by applications out of the system node. As a result, the logservice deployed on a node other than the system node is unable access the default HSQL database used by the Administrator. Workaround Do not use the default database for logservices on nodes other than the system node.
CL-1802
Summary The payload service, by default, uses the same default database as the Administrator on the system node created by TCT. This default database is an in-process database which is unaccessible by applications out of the system node. As a result, the payload service deployed on a node other than the system node is unable access the default HSQL database used by the Administrator. Workaround Do not use the default database for payload services on nodes other than the system node.
CL-1814
Summary Undeploying and re-deploying the default logservice results in a

Resource instance 'amxAdminDefaultHttpConnector' could not be found
warning message.
Workaround In TIBCO Administrator select the logservice application and click Deploy> More deploy options, uncheck the check box for Resolve mode, and deploy the application.
40
Release Notes
Key CL-1824
Summary/Workaround
Summary The Export button in the Log Viewer does not work as expected when exporting more than 100K records. Workaround Use a query that results in a smaller number of log records before using the Export button in the Log Viewer.
CL-1920
Summary If you enable authorization for the Enterprise Message Service Server, you have to manually update the related resource templates. Workaround The following manual steps are required:
1. Update the resource templates used by the logservice and payload service to use the updated username and password. The following resource template have to be updated: cl_logservice_jndiConnectionConfig cl_logservice_jndiConnectionConnectionFactory cl_payloadservice_jndiConnectionConfig cl_payloadservice_jndiConnectionConnectionFactory 2. Uninstall and re-install each resource instance that uses the resource templates listed in step 1. 3. Restart the logservice and the payload service. CL-1981
Summary When using the LogViewer, you are not able to run queries after exporting logs entries. Workaround Restart the node where the logservice application is deployed, or stop and undeploy the logservice application, uninstall and re-install the JDBC and Teneo resource instances used by the application, and lastly deploy and start the logservice application.
Known Issues 41
Key CL-1992
Summary/Workaround
Summary If there are more than 100K log entries in the logservice database, restarting the node where the logservice application runs results in out-of-memory errors with the default heap size setting. Workaround The following steps are required:
1. Stop the node which logservice application is running. 2. Back up the logservice database. 3. Drop the logservice tables in this sequence:
drop table baseeventformat_classifiers; drop table classifier; drop table baseeventformat_payloadids; drop table activestarttimes; drop table baseeventformat; drop table ecompid; drop table othersituation_any; drop table situationtype; drop table reportingcomponentid;
4. Start the node. The logservice application will recreate empty tables. While this takes care of the out-of-memory error it also results in deleting the existing log entries from the logservice database. MCR-1162
Summary Statistics for Web Application components do not display in the dashboard. Workaround None.
MCR-1184
Summary Rate metrics are reset to 0 when an application is stopped while the rest of the metrics are reset to 0 on application start in the Since Started time period. Workaround None.
MCR-1202
Summary The instances available metric in the services and references list of a component shows a blank value. Workaround Look for the instances available metric in a component. It
shows the correct value.
42
Release Notes
Key MCR-1204
Summary/Workaround
Summary Stopping the TibcoHost 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-1206
Summary If you use a CLI script to overwrite the node mapping for an application it shows "Partially Running" status in the dashboard. Workaround Modify the CLI script to remove the mapping from the first node and the second node instead of using the "set" action. Alternatively, use the Administrator GUI to remove existing mapping and add new mappings.
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-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-1241
Summary When applications containing multiple components are mapped to multiple nodes without restarting the application, the application status is reported as Partially Running in the Dashboard. Workaround None. The correct application status can be viewed in the deployment screens of the Administrator UI.
MCR-1350
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-1410
Summary After upgrading from an earlier 3.0.x version, values for the Requests metric are not updated in the monitoring dashboard. Workaround Upgrade the nodes where the application are deployed.
Known Issues 43
Key MCR-1422
Summary/Workaround
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.
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-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-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-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-939
Summary If Administrator and the Monitoring service are using different databases and monitoring database is down when an application is deployed, newly deployed application does not show up on the dashboard. Workaround When both databases are available, manually synchronize Administrator and monitoring databases using the following command:
1. cd TIBCO_HOME/administrator/3.1/scripts/governance 2. Run ant

-f governace_integration_build.xml sync
44
Release Notes
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.
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-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-586
Summary Incorrect behavior when deploying or redeploying a DAA that contains policy sets
Deploy, redeploy and undeploy commands in Administrator cause actions related to the DAA at the node. Within a node, the component framework (CF) arranges the application, and also requests that the governance agent (GAgt) arrange policies as specified in the DLL. However, this release has a defect in the communication between CF and GAgt, which affects the following three cases.
Known Issues 45
Key PER-586 Case 1
Summary/Workaround
Situation Deploy a DAA. The application deploys correctly and runs correctly, but the policies fail to deploy. Expected Result The entire DAA would fail. CF would automatically remove the application from the node. Actual Result Warning. The application runs, but the policies do not. The governance agent (GAgt) does not notify Administrator that policies failed to deploy. This case can be dangerous; for example, security policies cannot ensure encryption, nor prevent unauthorized use of the application. Workaround After a DAA successfully deploys, review node logs for policy deployment errors, and empirically test whether critical policies are operating as expected. Node logs are on the computer where the node is running, in this location: CONFIG_HOME/tibcohost/InstanceName/nodes/NodeName/logs/NodeName.lo
g
If you find that policy deployment failed, stop and undeploy the application, fix the policies, recreate the DAA, deploy the new DAA, and verify policy deployment. PER-586 Case 2
Situation Deploy a DAA. The application fails to deploy, but the policies deploy correctly. Expected Result The entire DAA would fail. The governance agent (GAgt) would automatically remove the policies from the node. Actual Result Policies remain in the node. GAgt does not notify Administrator that policies are deployed. Workaround Do not modify policies after an application fails to deploy; wait until after you fix the application in the DAA. After you fix the DAA and the application deploys correctly, GAgt reconnects the remaining policies to the application, and they operate correctly. Subsequently undeploying the DAA correctly removes the reconnected policies.
PER-586 Case 3
Situation Redeploy a DAA after modifying properties. Expected Result The node would update all property values. Actual Result The node updates properties associated with the application, but
not values associated with policies.

Workaround Undeploy the DAA, then deploy the updated DAA.
46
Release Notes
Key TAP-1593
Summary/Workaround
Summary If you undeploy a Policy Agent application it fails the first time with a provisioner error. Workaround Undeploy again using the Administrator CLI.
TAP-1618
Summary .An HTTP connector resource template does not accept a
substitution variable for the port number.

Workaround Use an integer value instead.
TAP-1628
Summary .When Administrator is invoked from within TIBCO Business
Studio and the default browser is Internet Explorer 8, an error pop-up displays.
Workaround After dismissing the error pop-up, the Administrator login screen
appears and the Administrator UI comes up normally. 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-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-4599
Summary When creating an Administrator server if the username specified in the external database configuration for an Oracle database has DBA privileges the Administrator server creation will fail. Workaround Specify a username that does not have DBA privileges.
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 47
Key TAP-4797
Summary/Workaround
Summary After changing columns displayed in a dashboard gadget or gadget refresh time, sometimes an error dialog will be displayed. In addition there will be an entry in the node log for SystemNode with a stack trace having an ultimate cause of:
Caused by: org.hibernate.NonUniqueResultException: query did not return a unique result: 2.

Workaround The change generally takes effect despite the error message. If not retry the operation.
TAP-4813
Summary When a binding is contained in a logical node, promoting the reference using the binding to the environment is not allowed because the binding is deleted. This is not supported. Workaround Recreate application template without placing the reference binding in a logical node.
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-5596
Summary The Administrator replication script terminates with an out-of-memory error. Workaround If an error is thrown while executing the scripts in the second machine, only targets from the failure onwards should be executed the second time. Increase the max heap size and MaxPermSize values of the Ant environment. Add -Xmx1024m -XX:MaxPermSize=512m to ANT_OPTS and then run ant.
1) If the script fails during admin-full-setup ant target, delete the CONFIG_FOLDER\tibcohost\Admin-amxadmin-instanceOne and run ant again. 2) If the script fails during the deploy-mcr or deploy-commonlogging target, run those targets individually. No folder should be deleted. 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.
48
Release Notes
Key TAP-5669
Summary/Workaround
Summary After wiring a JMS service to JMS reference, click on Manual Binding. Instead of Edit Binding, the Add Binding screen displays. Workaround None.
TAP-5672
Summary When you wire a reference to a service the service binding is listed twice on Target Service page of Manual Binding. Workaround None.
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-6647
Summary If installing a resource instance on multiple node fails, the Administrator UI hangs with the Saving Data message. Workaround Host screen:
After clicking Save and Close button in Resource Template wizard a second dialog should open that list all resource instances can to be installed. If this dialog does not open and you see "Saving Data" for more than 5 seconds close the wizard and continue with normal resource instance installation from host -> Resource Instances. Resource Templates screen: After clicking Save and Install button in the New Resource Instance, the wizard will close if creating and installing was successful. If wizard does not close and you see "Saving Data" for more than 5 seconds close the wizard and continue with normal Resource instance installation from host -> Resource Instances. TAP-6816
Summary If you uninstall a node immediately after installing it without
starting the node causes the install action to fail.

Workaround Click Uninstall again.
If you try and re-install the node instead of clicking Uninstall twice, the node may become unusable and you will have to first delete and then re-create the node. TAP-7423
Summary You may see an Errors in dashboard dialog box when following when using the Dashboard. Workaround Click OK to proceed using the Dashboard. This error message
can be safely ignored.
Known Issues 49
Key TAP-7431
Summary/Workaround
Summary A thread pool resource instance (or any resource instance referenced from a policyset property) is reported as being used by an application even though the application is either undeployed or was never deployed. This prevents the resource instance from being uninstalled. Workaround Use the force-uninstall option to ignore the usage report and proceed to uninstall the resource instance.
TAP-7447
Summary Discrepancies are seen in the Runtime and Action History states of the log service and payload service applications when the platform application is restarted. Workaround For each application, click Start to updated the state.
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-7544

Summary 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 incorrectly populated. Workaround Click Infrastructure > Hosts > hostname > Resource Instances >
All Instances and access the resource instance from the list displayed in the pane on the right side. TAP-7571
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-7577
Summary When you reinstall a resource instance, other resource instances or applications that depend on this resource instance continue to use the older version of the resource instance. Workaround When a resource instance is reinstalled, other resource instances that depend on it must be either reinstalled or the node be restarted for the changes to be applied. Applications that depend on the resource instance must be restarted (not redeployed).
50
Release Notes
Key TAP-7641
Summary/Workaround
Summary Clicking Dashboard-> Infrastructure may give the following
message:
Dashboard Bundle not Available. Please reload the browser. [Object Error]
Workaround Refresh the brower.
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.
TAP-7687
Summary Installing a JMS resource instance for the second time using the Application > Deploy >Resource Instances dependency wizard results in the following error:
[ERROR] org.apache.axis2.engine.AxisEngine - Please provide valid number of resource ids.
Workaround Install the resource instance using the Install option from the Infrastructure > Hosts> hostname > Resource Instances screen.
TAP-7704
Summary The Permissions button in the Admin Configuration > Admin Server > Tranport configuration screen is visible even though only superusers can use that screen. Workaround None.
TAP-7748
Summary The Administrator UI does not timeout after using the Dashboard. Workaround Explicitly log out of the Administrator UI or restart the brower.
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.
Known Issues 51
Key TAP-7778
Summary/Workaround
Summary When importing resource templates from a DAA or creating resource templates with inline credentials, the credentials are not always added to the keystore. In the Administrator UI, the username and password fields for the resource template are empty. Workaround Manually update the resource template with the credentials using the command-line interface or the Administrator UI.
TAP-7781
Summary When an application with an outgoing reference is upgraded, the mapping of the binding to the node is lost. When the application is deployed, the endpoints for the reference are removed. Workaround Follow these steps:
1. Using the Administrator UI, select the application and click the Distribution tab. 2. Select the promoted reference and map it to the runtime node. 3. Save and deploy the application. TRUP-201
Summary If you change the business name through a UDDI server's UI, Administrator does not reflect the change. So the business name in Server or UDDI publication tab will still show the old name, and another business name with that name will be created when service are published. Workaround Only change a business name in Administrator.
TRUP-211
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.
52
Release Notes
Key TRUP-212
Summary/Workaround
Summary If you navigate to Infrastructure > Servers, after your login session expires an empty page displays. Workaround Log out and log in again.
Business Studio Key AMX-6683 Summary/Workaround

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.
AMX-8720
Summary A composite containing a reference with a SOAP/JMS binding
cannot be run in RAD.

Workaround None.
AMX-8723
Summary Topic destinations are not supported for SOAP/JMS bindings but
TIBCO Business Studio does not raise a validation error.

Workaround None.
PER-557
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).
Known Issues 53
Key PER-609 PER-623
Summary/Workaround
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.
PER-632
Summary For proper policy enforcement, every composite containing a web application component must have a different context root. Workaround None.
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. 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.
54
Release Notes
Key SDS-3692
Summary/Workaround
Summary When there are multiple resource template files with the same name in the workspace, removing one of them may clear all references to that name (even if they are in separate workspace). Workaround After removing the resource template, reset the values on properties and other resource templates again.
SDS-3877
Summary If you use a Doc-Lit WSDL file with multipart messages, TIBCO Business Studio shows warning that "Generation of concrete wsdl with Doc-Lit style is not supported, because of multi parts". Workaround This is a warning validation which does not prevent you from continuing. Ignore the warning.
SDS-3890
Summary Sometimes there is an "Unhandled EventLoop Exception" in the
error log.
Workaround None. Ignore the error.
SDS-4174
Summary Virtualization Transacted OneWay Policy configuration (maximum redelivery count, redelivery delay interval, error queue, and list of exceptions to stop redelivery) is ignored on the reference side. Workaround None.
SDS-4870
Summary Administrator CLI script execution will fail if you select a resource instance that is in the Uninstalled or Failed state. Workaround Make sure the resource instance is running before executing the
CLI script. SDS-4934

Summary When it generates Administrator CLI scripts TIBCO Business Studio does not support the auto-resolve option to automatically provision third-party drivers, without which deployment will fail. Workaround If you specify an property of type JDBC resource instance that uses a third-party database, install the third-party drivers on the node before executing a script that creates and installs the JDBC resource instance.
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 should not display a distribution option different from what was originally specified. Workaround Choose the same distribution policy as the original application.
Known Issues 55
Key SDS-4976
Summary/Workaround
Summary Validation for port type with In-Out operation should be done for
JMS Transacted OneWay and Virtualization Transacted OneWay policies when you add a policy as well as when you add an intent. If these policies are applied for an In-Out MEP, runtime behavior is undefined and not supported.
Workaround Always apply an intent before specifying the policy or ensure that you do not specify JMS Transacted OneWay and Virtualization Transacted OneWay policies for In-Out MEPs.
SDS-4994
Summary The Refresh Server action in the Deployment Wizard does not completely refresh the local cache of the server contents. Workaround Refresh using the right-click Refresh menu option on the Deployment server.
SDS-5002
Summary TIBCO Business Studio does not prevent you from specifying an application name that contains special characters (\, /, :, *, ?, ", <, >,|, whitespace, %, #, &, (, ), and comma) not supported by runtime and deployment of an application may fail if the application name has those characters. Workaround Rename the application to avoid use of those characters.
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.
SDS-5023
Summary TIBCO Business Studio does not allow you to set the 'replyTo' inbound destination for a SOAP/JMS binding. Workaround None.
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.
56
Release Notes
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.
Mediation Key MED-14 Summary/Workaround

Summary WSDL files with invalid binding information are not validated when they are added to a mediation flow. Using a WSDL file with invalid bindings can cause problems when creating the mediation flow and the composite. Workaround Make sure you handle all validation problems with the WSDL file before using the file in a mediation flow.
MED-62
Summary Using a JMS/SOAP WSDL whose element contains an attribute which does not appear on the node, results in output data invalid errors. Workaround None at this time.
MED-65
Summary Custom metrics do not seem to work when you have a pass-through mediation in the composite. Workaround Add a task to the mediation flow. For example, a log task with
nothing selected. MED-78

Summary In an XPath Route task if the value of a boolean variable used in a rule is null, org.xml.api.lang.err.FORG0001 errors are generated. Workaround Make sure values are assigned for the variables.
MED-1525
Summary The Generate Mediation Implementation quick fix action creates
an empty mediation flow file with the Create mediation file wizard.
Workaround This generic eclipse shortcut to create the implementation is not supported for mediation.
Known Issues 57
Key MED-1652
Summary/Workaround
Summary The Message type context property does not specify an unbound Message even though the selection list contains all Message elements in the WSDL. An unbound Message is one that is not used for Input, Output, or Fault parts. Workaround Only select unbound Message elements for context properties.
MED-1703
Summary Creating schema using the Create button creates the schema for
CMT model plugin wizard but does not set it.

Workaround Once the schema is created, you can browse and select the schema in the wizard to set it for both Input and Output Schemas in the plugin wizard.
MED-1736
Summary Dragging and dropping a WDSL onto a mediation flow results in

Receive Wrong Transfer data
errors.
Workaround None.
MED-1739
Summary When adding a PortType with many ( about 50+) operations, the validation begins before the mediation flow is fully updated. This causes error markers to appear on the mediation operations when no actual problems exist. Workaround Select Project/Clear from the menubar and the validation will restart. The error markers will disappear, unless there are actual problems that remain.
MED-1827
Summary Deploying a mediation application that uses custom XPath
functions and if the custom XPath function plug-in is not deployed, results in errors at the time of deployment.
Workaround None at this time.
MED-1930
Summary If you set the exchange variables on a mediation operation, the task mapper of any Set Exchange Variable task on the mediation path continues to display No Input Mapping Required after you set the exchange variables once again. Workaround Delete the Set Exchange Variable task and add it back on the mediation path.
MED-2049
Summary Creating a CMT Model plug-in project for the first time in a new workspace results in Extension will be ignored because it contains invalid attributes errors. Workaround None. The errors can be ignored.
58
Release Notes
Key MED-2055
Summary/Workaround
Summary The Transform task does not handle the Byte Order Mark (BOM) in external stylesheet files. Workaround Open the stylesheet in a text editor and save it manually in a format without using BOM.
MED-2109
Summary For a Route task, the string value of variables can not contain '=', '>'
or '<' characters. These values are taken as empty chars

Workaround Use XPath routing.
MED-2229
Summary If the checkbox for UndeclaredFault is checked for the Catch Target Fault path then all the mapping done using the UndeclaredFault as message data on tasks on the CatchAll path are invalid.
If the checkbox for the Mediation Task Fault | Mediation Task Runtime Fault is checked for the Catch Mediation Task Fault path then all the mapping done using Mediation Task Fault | Mediation Task Runtime Fault as message data on tasks on the CatchAll path are invalid.
Workaround If the checkbox for the UndeclaredFault is checked for the Catch Target Fault path in 2.x, after migrating un-check the checkbox for the UndeclaredFault for the mapping to become valid for any task placed on the CatchAll path and provides mapping capability .
Similarly, if the checkbox for the Mediation Task Fault | Mediation Task Runtime Fault is checked for Catch Mediation Task Fault path in 2.x then after 3.x migration, uncheck the checkbox for the Mediation Task Fault | Mediation Task Runtime Fault for mapping to become valid for any task placed on CatchAll path and providing mapping capability .
Known Issues 59
Key MED-2267
Summary/Workaround
Summary The Custom Mediation tasks built in the 2.x environment that include a JDBC shared resource profile model attribute require additional steps for migration. This is due to the fact that the JDBC shared resource profile mechanism has been changed to a property driven mechanism in 3.x. Workaround To migrate a 2.x Custom Mediation task that includes a JDBC shared resource profile attribute/attributes to the 3.x environment follow additional pre-task migration steps before performing steps described in the TIBCO ActiveMatrix Service Grid Java Component Development:
1. Import the CMT model plug-in into the workspace. 2. Open <taskname>MediationTask.ecore file in text editor and remove eStructuralFeatures entries that contain reference to
com.tibco.corona.jdbc.model/model/jdbcConnection.ecore#//JDBC ConnectionProfile.
See the following example:
<eStructuralFeatures xsi:type="ecore:EReference" name="JDBC_Shared_Resource_Profile" eType="ecore:EClass ../../com.tibco.corona.jdbc.model/model /jdbcConnection.ecore#//JDBCConnectionProfile"/>
3. Open the <taskname>MediationTask.genmodel file in text editor and remove the entry for ../../com.tibco.corona.jdbc.model/model/jdbcConnection.genmod
el#//jdbcmodel, ../../com.tibco.corona.sharedresource.model/model/sharedresou rcemodel.genmodel#//sharedresourcemodel,../../com.tibco.neo.s var.model/model/SvarModel.genmodel#//svarmodel, ../../com.tibco.corona.jndi.model/model/jndimodel.genmodel#// jndimodel, ../../com.tibco.corona.security.model/model/securitymodel.gen model#//securitymodel, ../../com.tibco.neo.model.base/model/ComponentJar.genmodel#// componentjar, ../../com.tibco.corona.common.model/model/commonmodel.genmode l#//commonmodel, in GenModel attribute usedGenPackages.
For example:
<genmodel:GenModel xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:genmodel="http://www.eclipse.org/emf/2002/GenModel" modelDirectory="D:/CMT7215_Group.model/./src/." editDirectory="D:/CMT7215_Group.model.edit/./src/."
60
Release Notes
Key MED-2267 (contd)
Summary/Workaround
editorDirectory="D:/CMT7215_Group.model.editor/./src/." modelPluginID="CMT7215_Group.model" modelName="CMT7215_GroupMediationTask" importerID="org.eclipse.emf.importer.ecore" usedGenPackages="../../com.tibco.corona.jdbc.model/model/jdbcCon nection.genmodel#//jdbcmodel ../../com.tibco.amsb.core.mediation.model.ext/model/mediationext model.genmodel#//mediationextmodel ../../com.tibco.corona.sharedresource.model/model/sharedresource model.genmodel#//sharedresourcemodel ../../com.tibco.neo.svar.model/model/SvarModel.genmodel#//svarmo del ../../com.tibco.corona.jndi.model/model/jndimodel.genmodel#//jnd imodel ../../com.tibco.corona.security.model/model/securitymodel.genmod el#//securitymodel ../../com.tibco.neo.model.base/model/ComponentJar.genmodel#//com ponentjar ../../com.tibco.corona.common.model/model/commonmodel.genmodel#/ /commonmodel">
4. Click File > Import >Plug-in Development > Plugins and Fragments. Check the checkbox for the Import from the target platform and import com.tibco.amsb.core.mediation.model.ext and com.tibco.amsb.core.model plug-ins. 5. Add an eReference attribute with the same name as the JDBC shared resource profile attribute that points to com.tibco.amsb.core.model.ComponentType Property type. 6. Delete the imported com.tibco.amsb.core.mediation.model.ext and com.tibco.amsb.core.model plugins from workspace and the file system. 7. Re-generate the Custom Mediation Task model Java code. 8. Re-generate the Custom Mediation Task UI code by running Custom Mediation Task UI wizard against the modified model. MED-2275
Summary Construction functions are not provided after migrating 2.x task
mappings to the 3.x environment. In the 2.x environment the constructor functions were not mandatory to type a XPath expression. In the 3.x environment the mapper validator will generate errors if constructor functions are not provided to decipher the type of the expression.
Workaround To provide constructor functions for migrated mappings use the mapper quick fix mechanism.
Known Issues 61
Key MED-2452
Summary/Workaround
Summary Validation errors present in the 2.x SOA projects are propagated to the 3.x SOA projects. Workaround Fix the validation errors before importing the SOA projects.
MED-2503
Summary When you migrate a 2.x SOA project using the Migrate to ActiveMatrix 3.0 format, you see invalid conversion from anyURI string errors if the project uses a Set Dynamic Reference task. Workaround None.
to
MED-2542
Summary Context properties do not support declared unbound headers with the header message's part referring to type. Workaround For context properties, select the unbound header with the message part of the header referring to an element.
MED-2543
Summary You cannot add and delete a task added to the input path of a mediation flow more than ten times. Workaround None.
MED-2546
Summary When the Validate XML task is configured with Input as WSDL Message and the incoming message data has a message part referring to type, then validation may fail even if the incoming message data is correct and compliant with the WSDL message schema. Workaround Where possible, select Message Data as the Input for the Validate
Message Data task. MED-2587

Summary When a 3.0.1 SOA project contains a mediation flow, in the fault path for the Catch Target Fault task, all the faults are being handled including Catch All. When this SOA project is opened, you may see errors in the fault path in the Catch All transition. The mapping done in the Catch All transition is for an undeclared fault. Workaround Uncheck the checkbox for UndeclaredFault in the Catch TargertFaut task.
62
Release Notes

TIB Amsb3x 3.1.2 Relnotes

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TIB Amsb3x 3.1.2 Relnotes

Загружено:

Авторское право:

Доступные форматы

TIBCO ActiveMatrix Service Bus Release Notes

Software Release 3.1.2 April 2011

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

Table 1 General Typographical Conventions (Contd) Convention

Table 2 Syntax Typographical Conventions Convention

Use An optional item in a command or code syntax. For example:

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

Connecting with TIBCO Resources

How to Join TIBCOmmunity

How to Access All TIBCO Documentation

How to Contact TIBCO Support

TIBCO ActiveMatrix Service Bus Release Notes

| Connecting with TIBCO Resources

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

insert into "classifiergroups"("dtype",E_VERSION,"classifiergroupid","class ifierid") * select 'ClassifierGroups',0,"baseeventformat_e_id","classifier_e_id" from "baseeventformat_classifiers"

insert into "classifierbefmap"("dtype",E_VERSION,"befid","classifiergroup") * select 'ClassifierBefMap',0,"baseeventformat_e_id","baseeventformat_e_ id"from "baseeventformat_classifiers" + group by "baseeventformat_e_id"

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.0.1

contained extra nested comment markers.

2. In the folder BasicCredentialMapping, the file

Runtime Closed in Release 3.1.2

3.1.0 3.1.0 3.1.0

AMRP-2528 AMRP-2682 AMRP-2683

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.1.0 3.1.0

Key AMX-6956 AMX-7143

3.1.2 3.1.2 3.1.2 3.1.2

BJMS-361 BJMS-391 BJMS-400 BJMS-402

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.1.2

3.1.0 3.1.0 3.1.0

BJMS-192 BJMS-207 BJMS-268

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.0.1 3.0.1 3.0.1

Key BJMS-240 BJMS-244 BJMS-247

TIBCO ActiveMatrix Service Bus Release Notes

3.1.2 3.1.2 3.1.2 3.1.2 3.1.2

CL-1773 CL-1816 CL-1818 CL-1820 CL-1822

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.1.2

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.1.2 3.1.2

Key TAP-4771 TAP-4797

3.1.2 3.1.2 3.1.2

TAP-4939 TAP-5665 TAP-5667

TIBCO ActiveMatrix Service Bus Release Notes

Closed in Release 3.1.2 3.1.2 3.1.2 3.1.2 3.1.2 3.1.2

Key TAP-6057 TAP-6085 TAP-6095 TAP-6253 TAP-6573 TAP-660