tibco activematrix service bus - tibco software€¦ · † tibco activematrix service bus...

TIBCO ActiveMatrix® Service Bus

Release NotesSoftware Release 2.3.2March 2012

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN TIBCO ACTIVEMATRIX SERVICE BUS INSTALLATION) 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.TIB, TIBCO, TIBCO Software, TIBCO ActiveMatrix, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix, TIBCO AutoMediate, AutoMediate, and TIBCO BusinessWorks are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. PLEASE SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2005-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivTIBCO ActiveMatrix® Service Bus Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivThird Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 2.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Migrating from ActiveMatrix 2.3.0 or 2.3.1 to 2.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Migrating from ActiveMatrix 2.2.x to 2.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation, Documentation, Administrator, Business Studio, Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Mediation Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation, Documentation, Administrator, Business Studio, Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

TIBCO ActiveMatrix Service Bus Release Notes

iv | Contents

Mediation Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Migration Tools Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring ActiveMatrix Service Bus to Interoperate with BEA WebLogic and IBM WebSphere JMS Servers . 80Using SOAP/JMS and JMS Bindings with WebLogic JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Using SOAP/JMS and JMS Bindings with IBM WebSphere JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Service Assembly File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


| iii

Preface

Topics

• Related Documentation, page iv

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page ix

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.

TIBCO ActiveMatrix ServiceBus Release Notes

iv | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix® Service Bus DocumentationThe following documents form the TIBCO ActiveMatrix® Service Bus documentation set:

• TIBCO ActiveMatrix Concepts: Read this manual before reading any other manual in the documentation set. This manual describes terminology and concepts of ActiveMatrix. The other manuals in the documentation set assume you are familiar with the information in this manual.

• TIBCO ActiveMatrix Service Bus Installation: Read this manual to learn how to install ActiveMatrix Service Bus.

• TIBCO ActiveMatrix Service Bus Getting Started: Read this manual for a step-by-step introduction to the process of starting ActiveMatrix servers, creating and starting the ActiveMatrix runtime, developing composites, and deploying them to the runtime.

• TIBCO ActiveMatrix Composite Editor User’s Guide: Read this manual to learn how to develop, debug, and package ActiveMatrix composites.

• TIBCO ActiveMatrix Service Bus Mediation Design Guide: Read this manual to learn how to design ActiveMatrix mediation flows.

• TIBCO ActiveMatrix Service Bus Component Developer’s Guide: Read this manual to learn how to create, configure, and implement ActiveMatrix Service Bus components.

• TIBCO ActiveMatrix Administration: Read this manual to learn how to manage the ActiveMatrix runtime and deploy and manage ActiveMatrix services.

• TIBCO ActiveMatrix Service Bus Release Notes: Read the release notes for a list of new and changed features. This manual also contains lists of known issues and closed issues for this release.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO ActiveMatrix® Service Bus

• TIBCO ActiveMatrix® Service Grid


Preface | v

• TIBCO ActiveMatrix® BusinessWorks

• TIBCO ActiveMatrix® Registry

• TIBCO ActiveMatrix® Policy Manager

• TIBCO Enterprise Message Service™

• TIBCO Adapter™

• TIBCO Administrator™

• TIBCO Hawk®

• TIBCO Rendezvous®

Third Party DocumentationTIBCO ActiveMatrix software supports the following standards:

• Service Component Architecturehttp://www.osoa.org/display/Main/Service+Component+Architecture+Specifications

• World Wide Web Consortium web services activityhttp://www.w3.org/2002/ws/

— Simple Object Access Protocol (SOAP) 1.1 W3C Notehttp://www.w3.org/TR/2000/NOTE-SOAP-20000508/

— WSDL 1.1 W3C Note http://www.w3.org/TR/wsdl

• OASIS http://www.oasis-open.org/committees/tc_cat.php?cat=ws

— UDDI Version 3 OASIS Standard http://www.oasis-open.org/specs/index.php#uddiv2


http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications

http://www.w3.org/2002/ws/

http://www.w3.org/TR/2000/NOTE-SOAP-20000508/

http://www.w3.org/TR/wsdl

http://www.oasis-open.org/committees/tc_cat.php?cat=ws

http://www.oasis-open.org/specs/index.php#uddiv2

vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_NAME

ENV_HOME

AMX_HOME

AMX_ADMIN_HOME

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.

• Description Provides information about what the environment contains or is used for.

• Path The directory into which the product is installed. This directory is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO ActiveMatrix installs into a directory inside ENV_HOME. This directory is referenced in documentation as AMX_HOME. The value of AMX_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco\amx\.

TIBCO ActiveMatrix Administrator installs into a directory inside ENV_HOME. This directory is referenced in documentation as AMX_ADMIN_HOME. The value of AMX_ADMIN_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco\amxadministrator\.

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

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname

Key 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 1 General Typographical Conventions (Cont’d)

Convention Use


viii | Typographical Conventions

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical ’OR’ that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } 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 | ix

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity 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 DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor 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 username and password. If you do not have a username, you can request one.


http://www.tibcommunity.com

http://docs.tibco.com/TibcoDoc

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


x | Connecting with TIBCO Resources


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 9

• Deprecated Features, page 11

• Compatibility, page 12

• Migration, page 13

• Closed Issues, page 20

• Known Issues, page 48

• Migration Tools Reference, page 78

• Configuring ActiveMatrix Service Bus to Interoperate with BEA WebLogic and IBM WebSphere JMS Servers, page 80

• Service Assembly File Format, page 86



2 | Release Notes

New Features

This section lists features added since the last major release of the product.

Release 2.3.2There are no new features.

Release 2.3.1There are no new features.

Release 2.3.0• TIBCO ActiveMatrix AutoMediate Command Line is a new tool that uses

existing services as input, specified in a concrete WSDL, to create a fully functional composite application that has pass-through mediation capabilities.

Using AutoMediate Command Line, you can build ActiveMatrix SOA projects without having to use TIBCO Business Studio, AMSB Mediation Flow Editor, or the ActiveMatrix Composite Editor.

The AutoMediate Command Line tool builds ActiveMatrix SOA projects that contain:

— A pass-through mediation flow.

— An ActiveMatrix composite that contains the mediation component wired to services and references, depending on the number of ports specified in the concrete WSDL.

— The ActiveMatrix service assembly and the artifact file for the generated composite application.

• In the mediation flow, you can now

— Access the sub-elements of a Target Interface Fault

— Set the sub-elements of a Mediation Interface Fault

• Supports JRE 1.6.

• checkstatus utility which compares the state of ActiveMatrix runtime objects to an expected state and reports the result.


New Features | 3

• Added support for BEA WebLogic Server and IBM WebSphere Application Server to services with JMS and SOAP/JMS bindings and references with SOAP/JMS bindings.

• Added node property java.property.monitormanage.LoggingDeclaredFaults to enable declared fault logging.

• Added ActiveMatrix Administrator server property java.property.monitormanage.FaultCountExcludeDeclaredFaults to exclude declared faults while counting faults.

• Adding the property java.property.logs.base.dir to the ActiveMatrix Administrator server TRA file will redirect standard out and standard error logs to a specific directory.

• Adding property java.property.com.tibco.policy.ExposeExternalEndpointsQualifier to the ActiveMatrix Administrator server TRA file will further qualify external endpoints for synchronization with Policy Manager.

• Release 2.2.1

• Support for the Oracle OCI driver has been added in this release. It is available only in silent mode, which means that you can create a cluster with OCI driver only with the -silent option, using the createadminserver utility.

• The common logging framework, implementation types, and binding types have been enhanced to enable tracking a message end-to-end. This feature includes these changes:

— The Conversation ID has been added to improve traceability.

— A sortable Conversation ID column has been added to the log display.

— All columns are sortable. Sorting by column is according to all query results, instead of the current displayed results page.

— Query opens a warning if the record count is greater than 20k.

— Export displays the approximate processing time, and notifies users if an export function might take a long time. Logs will not be exported if the log count is greater than 30K, but a warning message is given.

— Copy/paste is now available for log columns and Event Details in LogViewer. Note that the Internet Explorer browser has a problem that affects the copy function for log columns; Mozilla Firefox works correctly.


4 | Release Notes

• The JMS binding type now supports the JMS "Text" message , which processes text messages as xsd:string. This provides the ability to send or receive JMS "Text" messages, which can be non-XML. This support is provided in addition to the JMS "Bytes" message, which can also process strings through the text-to-byte/base64 binary conversion.


New Features | 5

• New system properties for runtime node .tra file have been added. The properties are located at TIBCO_HOME/amx/data/clustername/nodename/bin/nodename.tra:— java.property.com.tibco.matrix.amxframework.messaging.response

.tl=value

This property adds support for time-to-live (TTL) for EMS response messages. The property value is in seconds, and the default is 600 seconds. This property does not affect the behavior if it is not set.

To use this property, add it to the node's .tra file. — java.property.monitormanage.LoggingDeclaredFaults=value

By default only system faults are logged. Set the property to true to enable declared fault logging. This property does not affect the behavior if it is not set, or if it is set to false.

To use this property, add it to the node's .tra file for existing nodes, or edit the .tra file for new nodes.

— java.property.com.tibco.policy.ExposeExternalEndpointsQualifier=value

This property enables further qualification of external endpoints for synchronization with Policy Manager. This new property can take the values All, Service, and Reference, extending the existing All, None, and External options of the Expose Endpoints feature.

If this property is set and the user selects General Information > Expose Endpoints > External in the service assembly, the endpoint synchronization behaves as follows for the property's values:

All All the external endpoints are synchronized with Policy Manager

Service Only external service endpoints are synchronized with Policy Manager

Reference Only external reference endpoints are synchronized with Policy Manager

This property does not affect the behavior if it is not set, or if the user selects All or None from the Expose Endpoints dropdown list.

To use this property, add it to the node's .tra file.

• New system properties have been added for the ActiveMatrix Administrator node .tra file


6 | Release Notes

TIBCO_HOME/amxadministrator/data/admin-cluster-name/admin-noden

ame/bin/admin-cluster-name_admin-node-name.tra:— java.property.monitormanage.FaultCountExcludeDeclaredFaults=va

lue

By default, the Monitor and Management fault count includes both declared and system faults (undeclared). Set the property to true to exclude counting declared faults. This property does not affect the behavior if it is not set, or set to false.

To use this property, add it to the ActiveMatrix Administrator server's .tra file for existing ActiveMatrix Administrator servers, or edit .tra file for new ActiveMatrix Administrator servers.

— java.property.logs.base.dir=redirect_dir

This property enables you to configure the stdOut and stdErr logs, to redirect them to a specific directory.

To use this property, add it to the node’s .tra file.

Release 2.2.0• In the mediation flow, you can now:

— receive message context information and access its values in the mediation path

— set message context data for the input message of the target operation and output message of the mediation operation.

• New Mediation Tasks

— End Mediation: end a one-way (in-only) message exchange pattern for operations.

— Validate XML: validate XML messages against an XML schema.

— Set Context: set HTTP header values or JMS user property values of the target operation.

• Log task: new Use Transform Data option enables mapping for building custom log messages.

• ParseXML and RenderXML tasks: new Validate Input option to enable schema validation of the task input

• Route task: use multiple, nested Route tasks to send a single target in multiple ways.


New Features | 7

• Transform task: new Use External Stylesheet option enables you to specify the transformation mapping in your workspace, outside the mediation flow.

• All mediation flow operations now have an input tab and an output tab, so that you can easily see the operations' input and output message schemas.

• Unlike the previous version, the transport and security context is not available by default in the message exchange of a new mediation flow. The user must explicitly enable this option from the Advanced tab of the properties view of a mediation operation and target operation.

• Mediate an In-Only mediation operation using an In-Out target operation.

•

Release 2.1.0• Dynamic Routing enables users to route incoming requests to a dynamic set of

target endpoints.

• New Mediation Tasks

— Invoke Operation task enables you to invoke web services and return from the middle of a mediation flow, without having to go to the target.

— Generate Reply task provides an option to reply to an incoming request without using the target service. In some situations, you might want to send a reply message to a consumer without invoking the target operation. Using the Generate Reply and Handle Reply tasks, you can bypass the target operation and send reply messages to the consumer directly from the mediation flow.

— Query Database task enables you to look up information in a database by performing a SQL SELECT statement. The task can specify one or more tables in the FROM clause of the SELECT statement, one or more columns to return in the SELECT list, and one or more conditions in the WHERE clause. You can also optionally specify the maximum number of rows to return.

— ParseXML Mediation task produces a tree representation of the XML that can be used by subsequent tasks in the mediation flow. This task can be paired with the Render XML task to convert the parsed XML back into a string or binary field for transmission within a message.

— Render XML Mediation task takes an XML tree for a specified schema and converts it to a string or binary element that contains the XML document. This task can be paired with the Parse XML task to convert the parsed XML back into a string or binary field for transmission within a message.


8 | Release Notes

• Sharing Data Between Mediation Paths

ActiveMatrix Service Bus 2.1 provides the ability to pass information from one mediation path to another, as well as between the input, output, and error mediation flows.

• Security Context Propagation

ActiveMatrix Service Bus 2.1 includes the ability to receive the security context for an operation request and pass that context on to the target operation that is invoked as part of the mediation. This feature allows a mediation to be placed in front of services that are secure.

• JDBC Shared Resource Profile in the Custom Mediation Task Wizard

You can use JDBC shared resource profiles to specify a shared resource—for example, a database connection—that can be used by one or more tasks in a mediation flow.

• Simplified Schema Editor

The simplified schema editor enables you to create basic schemas. It creates and stores the XSD file for the schema you create in your project. Only elements can be created using this editor.

• Inline Input Mapping

Mediation tasks that define their input types can now map the mediation exchange to those types inside of the task.

Release 2.0.2The AIX 5L for POWER Version 5.3 – 64 bit platform is now supported.


Changes in Functionality | 9

Changes in Functionality

This section lists changes in functionality since the last major (2.0.0) release of this product.

Release 2.3.2There are no changes in functionality in this release.



Release 2.2.0

Exchange Variable option moved

The Exchange Variable option is now on the Advanced tab of the properties view of a mediation operation. In previous versions, this option was on the General tab.

Release 2.1.0

Simplified schema for message properties and message context

The schema for message properties and message context has been simplified:

• The SecurityEnvelope element has been moved from MessageContext/Security/UserInfoPrincipal to MessageContext/Security.

The SecurityEnvelope element now contains transport-level (HTTPS or HTTP Basic Authentication) and message-level (WS-Security) security information. In release 2.0, SecurityEnvelope contained only message-level (WS-Security) security info.


10 | Release Notes

• The Principal and UserInfoPrincipal elements have been removed from the MessageContext/Security element.

The information that was part of these elements in release 2.0 is now part of the MessageContext/Security/SecurityEnvelope element.The SecurityEnvelope element schema is unchanged, and contains the SAML assertion element as before.

These changes are visible both in the Mapper and in the Java API.

See TIBCO ActiveMatrix Service Bus Mediation Design Guide for complete information about the schema for message properties and message context.

Release 2.0.1

Drag and Drop from Palettes

The user interface of palettes was slightly different between the Composite Editor and the Mediation Editor. In the previous release, the Mediation Editor only allowed clicking on an item in a palette, then clicking on the location where you want the item to appear in a mediation flow (also known as "click and paste"). Now, the Mediation Editor allows you to drag and drop items from a palette onto an appropriate location in a mediation flow.

Error Markers on Tasks With Incorrectly Typed Expressions

The TIBCO ActiveMatrix Service Bus Mediation Design Guide describes the need to typecast schema components in XPath expressions. In previous releases, untyped schema components did not cause an error. In this release, these errors are flagged on Transform tasks, and you can use the Show Check and Repairs button in the Mapper tab to correct the errors. Your projects created in previous releases may display previously unreported errors for untyped schema components when opened in this release.


Deprecated Features | 11

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.

Support for the following platforms is deprecated:

DBMS Software

• Oracle 9i Release 2

Web Browsers

• Microsoft Internet Explorer 6.0


12 | Release Notes

Compatibility

• The TIBCO ActiveMatrix Binding Type for EJB displays the following incompatibility with TIBCO ActiveMatrix Service Bus 2.3. Service assemblies containing SOAP services and EJB references fail to be invoked when an operation that returns a complex type object is invoked by a SOAP client. To work around this issue, add the following line to the TRA file of the node:

java.property.sun.lang.ClassLoader.allowArraySyntax=true

• TIBCO ActiveMatrix Adapter Service Engine for Database 5.x is not compatible with TIBCO ActiveMatrix Service Bus 2.3. The workaround is to upgrade to TIBCO ActiveMatrix Adapter Service Engine for Database 6.0.0.


Migration | 13

Migration

For information on the tools used in migration tasks, see , , on page 93.

The steps you follow to migrate to ActiveMatrix 2.3.2 differ, depending on your current version:

• If you are upgrading from ActiveMatrix 2.3.0 or 2.3.1 to 2.3.2, follow the steps in , Migrating from ActiveMatrix 2.3.0 or 2.3.1 to 2.3.2, on page 13.

• If you are upgrading from ActiveMatrix 2.2.x to 2.3.0, follow the steps in , Migrating from ActiveMatrix 2.2.x to 2.3.0, on page 15.

• If you are upgrading from ActiveMatrix 2.0.x or 2.1.x to 2.2.1, refer to the ActiveMatrix 2.2.x release notes for the steps.

Migrating from ActiveMatrix 2.3.0 or 2.3.1 to 2.3.2Installing TIBCO ActiveMatrix Service Bus 2.3.2

1. Shut down all running TIBCO applications.

2. Back up TIBCO_HOME.

3. Extract the installer to a temporary directory.

4. Navigate to the temporary directory.

5. Run the TIBCO Universal Installer, selecting an existing TIBCO_HOME.

Upgrading an Existing Administrator Server Instance to 2.3.2

1. Ensure Administrator server is stopped.

2. In a command or shell prompt, go to the directory: ENV_HOME/tools/bin, and execute the command:

ENV_HOME/tools/bin/tibcommander -f ENV_HOME/amxadministrator/2.3/bin/adminupgradersp1.xml -Dclustername=clustername -Dadminname=servername upgrade_minor_with_tra

Uninstall is not supported, therefore restoring a back up is the only way to return to a previous version.


14 | Release Notes

where clustername and servername are respectively the names of the cluster and Administrator server.

3. Start the database used by Administrator, if it was stopped earlier.

4. Start Administrator server. It will continue upgrading itself during startup.

Reinstalling the Administrator Server Windows Service

The installer upgrades the Administrator server executable but does not upgrade the Administrator server Windows service. To upgrade the Windows service:

1. Change to the directory AMX_ADMIN_HOME/data/clustername/servername/bin/.

2. Run clustername_servername.exe --uninstall.

3. Run clustername_servername.exe --install

Reinstalling the TIBCO Management Daemon Windows Service

The installer upgrades the Management Daemon executable but does not upgrade the Management Daemon Windows service. To upgrade the Windows service:

1. Run TIBCO_HOME\managementdaemon\2.0\bin> mmanagementdaemon.exe --uninstall.

2. Run TIBCO_HOME\managementdaemon\2.0\bin> mmanagementdaemon.exe --install.

Upgrading Existing Nodes to 2.3.2

To upgrade all nodes, run:

ENV_HOME/tools/bin/tibcommander -f TIBCO_HOME/amx/2.3/server/bin/nodeupgrader.xml -Dnodes=all

To upgrade specific nodes, run:

ENV_HOME/tools/bin/tibcommander -f ENV_HOME/amx/2.3/server/bin/nodeupgrader.xml -Dnodes=envname1/nodename1,envname2/nodename2

upgrade_minor_with_tra is a mandatory argument.

On UNIX systems, when you upgrade a node from 2.3.0 or 2.3.1 to 2.3.2, the node binary loses its execute permission and fails to start. You must manually grant execute permission to the node binary and then restart it.


Migration | 15

Migrating from ActiveMatrix 2.2.x to 2.3.0To upgrade ActiveMatrix components from 2.2.x to 2.3.0, perform these tasks in order:

• Task A, Shut down ActiveMatrix processes, on page 15

• Task B, Upgrade the ActiveMatrix Administrator Database, on page 15

• Task C, Upgrade ActiveMatrix Administrator Servers, on page 16

• Task D, Upgrade Management Daemon, on page 17

• Task E, Upgrading Nodes, on page 18

• Task F, Upgrading ActiveMatrix Nodes to Use Rendezvous 8.2.1, on page 19

Task A Shut down ActiveMatrix processes

Shut down all ActiveMatrix processes—Management Daemon, ActiveMatrix Administrator servers, and ActiveMatrix nodes—running on the machine.

At this point you can perform Task C, which will upgrade the ActiveMatrix Administrator database schema and the ActiveMatrix Administrator server.

Or, you can perform Task B, to manually update the ActiveMatrix Administrator database and then Task C which will skip schema upgrade and only upgrade the ActiveMatrix Administrator server.

Task B Upgrade the ActiveMatrix Administrator Database

If you want to manually upgrade the database schema:

1. Start the ActiveMatrix Administrator database.

2. Open a terminal window.

3. Change to the directory AMX_ADMIN_HOME/2.3/bin/.

4. Run dbscriptgenerator –generateupdates. This command determines the difference between the database schema in a previously installed product and the schema for the current product and saves the difference into a DDL file.

The command prompts you to enter the name of the ActiveMatrix Administrator cluster and the name of the ActiveMatrix Administrator server. Type the cluster name and server name.


16 | Release Notes

5. Apply the DDL file to the schema using your database’s SQL tool.

Updating HSQLDB

To update an HSQLDB database:

1. Copy AMX_HOME/hsqldb/bin/sqltool.rc to the user home location. For example, on Windows it would be C:\Documents and Settings\username.

2. Execute the following command at a prompt with the HSQLDB database running:

java -jar ENV_HOME/components/eclipse/plugins/com.tibco.tpcl.org.hsqldb_1.8.100.001/hsqldb.jar urlid AMX_ADMIN_HOME/2.3/scripts/ddl/dbschema.ddl

where urlid is the name of the ActiveMatrix Administrator cluster name and can be found in the sqltool.rc file.

The ddl file to precreate schema generates alter table and the create table statements. You must manually delete all the initial values of alter tables so that the scripts directly starts executing the create table statements.

Task C Upgrade ActiveMatrix Administrator Servers

Running 2.0.x, 2.1, 2.2, and 2.3 ActiveMatrix Administrator servers within a cluster is not supported; you must upgrade all ActiveMatrix Administrator servers to 2.3.To upgrade from 2.2.x to 2.3, use the command:

ENV_HOME/tools/bin/tibcommander -Dadmin.version=2.2 -f AMX_ADMIN_HOME/2.3/bin/adminupgradersp1.xml

To upgrade an ActiveMatrix Administrator server:

1. Ensure that the ActiveMatrix Administrator database server is running.

2. Run the upgrader:

a. Change to the directory ENV_HOME/tools/bin.

b. Run

For known issues and workarounds related to migration when using the Sybase database, see the issues 1-9MN8ZK and 1-9N9MWH in Known Issues on page 48..


Migration | 17

tibcommander -f AMX_ADMIN_HOME/2.3/bin/adminupgradersp1.xml -Dclustername=clustername -Dadminname=servername -Dadmin.version=2.3 -l adminupgrader.log

where clustername and servername are respectively the names of the cluster and Administrator server.

ReinstallWindows service

3. Reinstall the ActiveMatrix Administrator Windows service:

a. Change to the directory AMX_ADMIN_HOME/data/clustername/servername/bin/.

b. Run clustername_servername.exe --uninstall.

c. Run clustername_servername.exe --install -noshell -redirect

4. Start the server. If you run the server startup script (amx_admin) to start the server, run the file in AMX_ADMIN_HOME/2.3/bin/.

5. Clear the browser cache before accessing the ActiveMatrix Administrator UI.

Task D Upgrade Management Daemon

To install 2.3.0 on top of an existing 2.2.x installation and use the Management Daemon process’ existing configuration you must upgrade Management Daemon. To upgrade Management Daemon:

1. Upgrade all ActiveMatrix Administrator servers bound to that Management Daemon.

2. To update from 2.2 to 2.3

a. Change to the directory ENV_HOME/tools/bin/.

b. Run

tibcommander -f ../../managementdaemon/2.0/bin/MDCacheCleaner.xml


3. Reinstall the Management Daemon Windows service:

a. Change to the directory ENV_HOME/managementdaemon/2.0/bin.

b. Run managementdaemon.exe --uninstall.

c. Run managementdaemon.exe --install -noshell -redirect.

tibcommander does not display error messages when you run with the -l option. You should check the log for errors after running tibcommander.

The upgrade utility must have access to the databases for all the clusters to which the Management Daemon is bound.


18 | Release Notes

4. Start Management Daemon.

Task E Upgrading Nodes

To upgrade 2.2.x nodes to 2.3.0:

1. Ensure the ActiveMatrix Administrator database is running.

2. Upgrade nodes:

a. Change to the directory ENV_HOME/tools/bin/.

b. Run

tibcommander -f ../../amx/2.3/server/bin/nodeupgrader.xml -Dnodes=environment1/node1,...,environmentN/nodeN -l nodeupgrader.log

to update node1 through nodeN.


3. If the node was installed as a Windows service, reinstall the service:

a. Change to the directory AMX_HOME/data/environmentname/nodename/bin/.

b. Run environmentname_nodename.exe --uninstall.

c. Run environmentname_nodename.exe --install -noshell -redirect.

You are not required to upgrade 2.2.1 nodes to 2.3.0. They can interoperate with 2.3.0 nodes and be managed by ActiveMatrix Administrator 2.3.0 server.

If you install 2.3.0 on a machine that has 2.2.0, you must upgrade both the ActiveMatrix Administrator server and nodes in order to manage the nodes on the machine. However, 2.2.0 nodes on remote machines that are part of the environment will continue to work and are manageable by the ActiveMatrix Administrator 2.3.0 server.

If you do not upgrade 2.2.0 nodes to 2.3.0, the nodes will become unstable when you deploy/undeploy a service assembly or activate/deactivate a container, possibly causing the node to fail and the SOAP container not to be reactivated after the node is restarted. If you cannot upgrade a node, avoid any deployment/undeployoment or container activation/deactivation on it.

After you upgrade to ActiveMatrix 2.3.0, multiple versions for some containers will exist in nodes, but only the version installed by ActiveMatrix 2.3.0 will be active.

The ActiveMatrix Administrator UI does not prevent you from activating multiple versions of the same type of container. However, you should activate only one version of a container at a time.


Migration | 19

Task F Upgrading ActiveMatrix Nodes to Use Rendezvous 8.2.1

When Rendezvous 8.2.1 is installed, the Rendezvous bin directory containing the Rendezvous DLLs is added to the system path. A node’s configuration file uses the system path to determine from which directories to load required DLLs.

In order to upgrade ActiveMatrix nodes to use Rendezvous 8.2.1, the node’s value for the system path file needs to be updated to get the value containing the path to the Rendezvous 8.2.1 DLLs.

If the node is started from the ActiveMatrix Administrator GUI, the node inherits its system path from Management Daemon, as it is spawned as a child process of the Management Daemon. Therefore, first Management Daemon must be restarted to the get new system path. If Management Daemon was started from a console window, it must be restarted in a new console window. If the Management Daemon is running as a Windows service, the Windows service must be reinstalled as described in Reinstall Windows service on page 17 and then restarted.

The node must be restarted after Management Daemon is restarted. In addition, if a node has been installed as a Windows service, the node’s Windows service must also be reinstalled as described in Reinstall Windows service on page 18 and then restarted.

No migration required for custom mediation tasks created using ActiveMatrix Service Bus 2.2.x.

If you are upgrading from Service Bus 2.0.x or 2.1.x to 2.2.1, refer to the Service Bus 2.2.x release notes for the steps.


20 | Release Notes

Closed Issues

Installation, Documentation, Administrator, Business Studio, RuntimeThe tables in this section list issues that were closed in the named releases. To view defects for a particular feature, see the sections:

• Installation on page 20

• Documentation on page 21

• Administrator on page 22

• Business Studio on page 33

• Runtime on page 36

Closed in Release

Change Request ID Summary

Installation

2.3.2 AMX-8860 Expired Management Daemon certificates have been updated with certificates with an expiration date of August 2110.

2.2.1 1-9OH9C5 The installer now creates the correct folder structure for the Management Daemon when ActiveMatrix Service Bus 2.2.0 is installed on top of TIBCO Service Performance Manager 1.1.1.

2.2.1 1-9ONO6M You can now install a new node after uninstalling the WCF host.

2.2.1 1-9PGWM7 Upgrading an existing node no longer fails after uninstalling a hotfix.

2.1.0 1-8IGF31 You can now cancel an installation once the installation has started by clicking Cancel.

2.1.0 1-8Q8HRC ActiveMatrix Service Grid or ActiveMatrix Service Bus can now be installed on a machine where multiple TIBCO home directories exist.

2.1.0 1-8JOWQD On Windows, silent mode installation now runs in the foreground and give immediate feedback when it completes.

2.0.1 1-8LXES1 The installer now runs managementscript on UNIX platforms. Machines where Management Daemon is running are discoverable.

2.0.0 1-7TS06K The uninstaller on Linux no longer takes over 15 minutes to complete.


Closed Issues | 21

Documentation

2.3.2 AMSG-7942 Service Assembly File Format on page 8 describes the structure of the service assembly file.

2.3.0 1-9O6ZPO The installation instructions for Linux on IBM zSeries are now in the installation manual.

2.3.0 1-9O6QMJ The installation manual reports Red Hat Linux support for versions 4.x and 5.x.

2.3.0 1-9O6QN4 The installation manual indicates that the Design component is not supported on Windows 64 bit platforms.

2.3.0 1-9JNAHY The installation manual now indicates that you must export all packages of ojdbc5.jar when configuring the Oracle native thin driver. If you export only oracle.jdbc.driver, the node will not start up.

2.3.0 1-9O23SP Component Developer's Guide->Chapter 2 Developing Java Components-> Getting and Setting Transport Headers corrects statements about setting and retrieving header properties:

If you set properties in a Java component using the keys REFERENCE_OUTBOUND_TRANSPORT_PROPERTIES and SERVICE_OUTBOUND_TRANSPORT_PROPERTIES you cannot access those properties in a Java component bound to the first Java component.

2.3.0 1-9O7K85 The Component Developer's Guide the description of log file naming for .NET service units now correctly states The AppDomain.CurrentDomain.FriendlyName part of the log file name is constructed from the namespace of the composite and the component name.

2.3.0 1-97AWQF The Composite Editor User’s Guide mentions the different SQL schema files that ship with ActiveMatrix services for SQL server and Oracle, for WS-Eventing and WS-Transfer features.

2.3.0 1-9OAPTJ In TIBCO ActiveMatrix Administration, Appendex A, Section : Keystore/Management Daemon Keystores/ Managing the Trusted Keystore provides the property for the keystore password in the .tra file.

Closed in Release



22 | Release Notes

2.2.0 1-97JZEC The installation manual now has information about how existing Administrator server and runtime nodes can use Sybase-based JDBC shared resources after you install the Sybase drivers.

2.2.0 1-8UI3C7 TIBCO ActiveMatrix Administration now notes that the following resources can have only ASCII names:

File name and directory name of log files

2.1.0 1-8O2R7L The Pre-creating ActiveMatrix Schema section in TIBCO ActiveMatrix Administration now says Copy the create and alter statements and create sequence statement into another file named dbcreateschema.sql.

2.1.0 1-8M7ZQD In TIBCO ActiveMatrix Administration, Chapter 8, Deploying Service Assemblies, Service Assembly Reference, Table 49 now says that the default value for Expose Endpoints is External.

2.1.0 1-8MD8HN TIBCO ActiveMatrix Administration correctly describes how to modify the password for authentication realms.

2.1.0 1-8ME3LN TIBCO ActiveMatrix Administration, Chapter, 9 Monitoring Infrastructure and Services > UDDI Publishing notes that when the UDDI server is down while unpublishing the service, the unpublish action proceeds to completion. In such cases, it is your responsibility to remove the service from the UDDI server when it is available.

2.1.0 1-8TAZW7 While creating a service assembly with the command line tool, if the Explorer is open on the folder where the service assembly is being created, sometimes service assembly creation will fail due to exceptions. Composite Editor User's Guide describes how to use the -clean option when invoking the tool.

2.1.0 1-8SKDNO Composite Editor User's Guide now describes how to change Rendezvous character encoding to another encoding such as ISO-8859-1.

Administrator

2.3.2 TAP-8769 Log in failures no longer occur in Administrator because of password history record getting automatically deleted in some cases.

2.3.2 TAP-8161 An error is no longer reported by a CLI Ant script while setting the LogAppender for a service assembly or a node to the value of JMS.

Closed in Release



Closed Issues | 23

2.3.2 MCR-1532 Administrator no longer runs out of heap memory in a particular case of monitoring statistics from a large number of nodes.

2.3.2 TAP-8946 While using LDAP authentication realm for Administrator, connections to the LDAP server no longer accumulate until garbage collection runs; they are closed immediately.

2.3.2 TAP-7855 An error is no longer thrown while querying with special characters, for example, a group with the name 'Education & Support'.

2.3.2 TAP-7821 The admincmdline utility now retries requests to the server rather than intermittently showing "Invalid Login" errors caused by connections being dropped. The status checker utility also does similar retries as well.

2.3.2 TAP-7822 A node no longer momentarily goes from the running state to the stopped state and back to the running state without any intervention.

2.3.2 TAP-7374 In 60+ node environments, it no longer takes 2.5 minutes for the Administrator UI to report that a node started when in fact it had started much sooner.

2.3.2 TAP-7486 Administrator startup no longer fails when LDAP authentication is used with SLF4J 1.5.

2.3.1 AMSG-7752 Support for Oracle 11g R2 and Oracle 11g R2 RAC

This has been resolved as not a product issue. In order to use Oracle 11g R2 as the ActiveMatrix Administrator database, it must be configured to use the Oracle 10g optimizer. One way to accomplish this is to implement an Oracle trigger that is executed whenever ActiveMatrix users make a connection. The trigger can configure the user session to use the 10.2.0.2 optimizer. For more details or examples of triggers, contact TIBCO Global Support.

2.3.1 1-9VOTIS For SPM 1.2.0.(V8.1), the error "JDWRViewerService is undefined" no longer occurs when selecting Run Query > Hint Log Viewer.

2.3.1 1-9VJCQ7 View and Manage Dashboard: Reports are now displayed for AMX, WAS, WCF Services, Operations, Machines, and Service Container.

2.3.1 1-9W630I A class cast exception no longer occurs when BEF events with non-ActiveMatrix ECompIds are logged.

Closed in Release



24 | Release Notes

2.3.1 1-A0RPMN Administrator server no longer runs out of heap memory when running in a cluster with another server instance.

2.3.1 1-ANGTQT The admincmdline utility now allows encrypted values for passwords for keystore creation, in addition to clear text.

2.3.1 1-ARA9Z0 Substitution variables of password type no longer get corrupted when editing values of other variables in the editor.

2.3.1 1-ARJA6J The admincmdline utility no longer causes failures when installing and uninstalling shared resources in a particular sequence.

2.3.1 1-9ZDTGJ Substitution variables of password type now support an empty password.

2.3.1 CL-1584 TIBCO Common Logging no longer causes a large number of database connections.

2.3.1 CL-1340 If a BaseEventFormat (BEF) log had multiple Classifier values, to improve performance, TIBCO Common Logging now provides an extension capability in log service to enable custom persistence of StatsEventFormat (and other BEF extensions).

Closed in Release



Closed Issues | 25

2.3.1 CL-1369 Common logging event logger now logs the full payload when the size of the payload is large. The message column handling has improvements and the message isn't truncated until the moment it's inserted into the database.

By default, the message field of entries logged into a database will be automatically truncated to 2000 bytes. To customize the maximum message length, alter BASEEVENTFORMAT table's schema to increase MSG column's size to the maximum message length desired. Also, add the property java.property.cl.msg.db.maxlength=length in bytes to the end of the file ENV_HOME/amxadministrator/data/clustername/adminname/bin/clustername_adminname.tra. For example: java.property.cl.msg.db.maxlength=3000 sets the the maximum length for log messages to 3000 bytes. Messages that exceed the length will be truncated.

For JMS appender in logger, messages are not truncated. If you want the message be truncated to a specified length, add a parameter to the logging configuration of the JMS appender. Setting the logger with this parameter in the Administrator UI is not currently supported. However, as long as the JMS appender is enabled you can add the maxMessageFieldLength parameter in bootStrap.xml:

<param name="maxMessageFieldLength" value="0"/> means disable this parameter, no limit as default.

<param name="maxMessageFieldLength" value="3000"/> means limit the length to 3000 bytes for each message.

To configure JMS appender in bootStrap.xml of a node:

1. Uncomment the logging configuration for default JMS appender in bootstrap.xml.

2. Specify a value for each parameter in the JMS appender:

<appender class="com.tibco.commonlogging.appender.BEFJMSAppender" name="_amsg230hotfix_longMsgtrucated_appender"> <param name="serverUrl" value="tcp://localhost:7222"/> <param name="maxMessageFieldLength" value="3000"/> <param name="retry" value="1"/> <param name="queueName" value="logservice230"/> <param name="userName" value="admin"/> </appender>

3. Restart the node.

Closed in Release



26 | Release Notes

2.3.0 1-A6MRQO Provides checkstatus utility.

2.3.0 1-A913UE A CLI timeout is now treated as a failure, so the ANT script can be made to terminate with error, using "failOnError" attribute, in case a timeout occurs. This makes scripting more reliable because it will only report success when CLI actions have been completed successfully.

2.3.0 1-A91ET5 A detailed log with stack trace is now logged when Administration CLI fails to execute actions with an error message from XFire.

2.3.0 1-A91ERP The creation of a new Administration server with LDAP realm no longer fails when specifying user_unique_attribute and group_unique_attribute in the createadminserver -silent mode. This is required for the case where "sAMAccountName" attribute of MS ActiveDirectory represents the user's login name.

2.3.0 1-9YXQ5F, 1-9VV1ZU

On Windows, the admincmdline utility no longer fails with NoClassDefFound error due to path length issues.

2.3.0 1-A471TV When multiple concurrent operations (creating environment/nodes....) are being performed by both Administrator command-line scripts and the Administrator GUI, the machine.xmi file no longer occasionally gets deleted.

2.2.1 1-9J574R Support for the Oracle OCI driver has been added. See the New Features section for more information.

2.2.1 1-9BJL27 The ActiveMatrix Administrator did not show the updated concrete WSDL when a modified service assembly was updated.

2.2.1 1-9O7JJD Startup threw a code 404 error for each service started.

2.2.1 1-9OHR26 Service assembly information remained in a BLOB table (used for cache management) after deleting the information from the Administrator.

2.2.1 1-9PGTLU The user name is now case sensitive. It was previously case insensitive, causing issues in permissions for user perspectives.

2.2.1 1-9RV6FZ Performance in the Administrator degraded when multiple services were deployed.

Closed in Release



Closed Issues | 27

2.2.1 1-9M53NC At startup, nodes now acquire locks on jars in this folder: AMX-HOME/data/AMX-Environment/AMX-Node/bundles/eclipse/p

lugins

2.2.1 1-9PYRMT The SOAP/JMS reference was getting the response back on the specified reply destination, but DEBUG message showed the target destination as the reply destination.

2.2.1 1-9QL1B3 The CommonLogging - Correlation ID is now supported, to improve traceability.

2.2.1 1-9QL1BU Spline now supports logging for system errors.

2.2.1 1-9SLUHL The password was visible in the console when you tried to reset the password and did not have MD running.

2.2.1 1-9KSS7G The Administration Server creation failed when the LDAP realm with SSL was used in silent mode (using the -silent option).

2.2.1 1-9PRTB5 The ActiveMatrix Administrator allowed users to access and modify components for which they did nto have the required permissions.

2.2.1 1-9G3VJ1 ActiveMatrix rulebases have been updated.

2.2.0 1-8KRSPN In the Monitor & Manage perspective of the Administrator UI, the tool tip for a service's Start Date no longer displays 12/31/69 if monitoring is not enabled.

2.2.0 1-8LRZLT In the Administrator UI Monitor & Manage perspective, the Start Date tooltip no longer displays "12/31/69 4:00PM" when service or node is stopped.

2.2.0 1-93I98V When a SOAP service unit is mapped to multiple nodes, and send requests to a service on one of the nodes, the hits are now shown only on the node that processes the request.

2.2.0 1-97N4QF When changing the time period for a service unit, the Deployment tab now shows only the nodes in which the service unit is deployed.

2.2.0 1-934JH9 In the ActiveMatrix Administrator, if you select a node under Configuring an environment, discard changes to edits in Shared Resources, and confirm that the changes need to be discarded, an exception is no longer thrown.

Closed in Release



28 | Release Notes

2.2.0 1-958VWM If the service name, reference name, or component name contain double-byte characters, the service name/reference name/component name now appear in the Service Metrics list in the Administrator.

2.2.0 1-8UB2T1 It is now possible to delete a service unit's log file after the service assembly containing the service unit is undeployed.

2.2.0 1-94OYDR Logging now works if you activate and deactivate a container.

2.1.0 1-8UCEBL When logging in to ActiveMatrix Administrator, user names and passwords can now be multibyte characters.

2.1.0 1-8SN7OB When you add a metadata attribute to a published service the status should change to Publish Incomplete and the Publish and Unpublish button now appear in the Action column.

2.1.0 1-8MD8MF If you create an Administrator server on a remote machine, then stop the primary Administrator server by logging into the second Administrator server, the Administrator UI no longer displays node status as Installed /Stopped and service assembly status as Unknown even though they are running on the machine where the first Administrator server was created.

2.1.0 1-8IUB54 For messaging servers and JMS shared resource definitions, the Client ID field is no longer visible.

2.1.0 1-8JRHYH The Adminstrator server creation wizard no longer throws dependency exceptions on its console.

2.1.0 1-8L2SOC When a non-admin UDDI user tries to publish to a business created by the admin UDDI user, the message displayed on the Administrator UI now indicates that the user doesn't have permission to publish to the business.

2.1.0 1-8LDZIB The Administrator UI no longer gets distorted on Internet Explorer when you access the Configure an Environment perspective for the first time and create a node.

2.1.0 1-8LDZJ3 If you enter a node name that contains spaces in the Administrator UI the UI provides feedback that the name is not valid.

Closed in Release



Closed Issues | 29

2.1.0 1-8LNZTR The schema creation script createclusterschema_oracle.sql is no longer missing the statement that allows the ddl user to run the script against the schema of the dml user.

2.1.0 1-8LSTY0 When stopping a running Administrator server, clicking the Stop button stops the server and clicking the Refresh button updates the status from Running to Stopped.

2.0.1 1-8LDWVV On HP Itanium, when configuring TIBCO Administrator realm, the Administrator server creation wizard now creates the Administrator server.

2.0.1 1-7TY9HY When the timeout value is set to 60 seconds JMX discovery now returns Management Daemon instances.

2.0.1 1-8ME3MM When the UDDI server is down and you try to unpublish a service the Administrator UI displays a warning message to inform you that the service has been marked as unpublished and that you need to manually clean up the UDDI server.

2.0.1 1-8MF2YP In the Administrator UI Monitor & Manage perspective > Dashboard, hits are now reported correctly after certain number of hits/period.

2.0.1 1-8LDRFR On Linux, a service assembly with an HTTPS shared resource no longer fails to start with error "URI is not absolute".

2.0.1 1-8LUOET In the Administrator UI Monitor & Manage perspective, Load Balanced Service > Deployment Details screen a huge value with no format is no longer displayed in the Min Response Time and Min Msg Size columns when there are no hits.

2.0.1 1-8LVKQ0 In the Administrator UI Monitor & Manage > Service screen, initial hits on services now display in the Provides & Consumes screen.

2.0.1 1-8LWC3K When running the Administrator UI on Firefox, the Monitor & Manage > Service > Overview screen no longer freezes after a few hours.

2.0.1 1-8M3FGL D2RT Transformation exceptions are no longer displayed if you deploy a service assembly with an endpoint that has been registered by another service assembly.

Closed in Release



30 | Release Notes

2.0.1 1-8M7IV5 In Internet Explorer, while adding or editing a node with the NT Service option set to Yes, the browser no longer throws the exception Failed to edit node - invalid boolean value '-1'.

2.0.1 1-8M7QZX When running the Administrator UI In Internet Explorer, and you select the product home for a node, the home displays correctly in the drop-down list text area.

2.0.1 1-8LNW89 In the Administrator UI Monitor & Manage perspective, an exception is no longer thrown in the Service screen when a search doesn't return any results.

2.0.1 1-8LIMXT If you deploy a service assembly using the command-line interface and choose "Expose Endpoints=None", the SOAP endpoint is no longer available in the Policy Manager console.

2.0.1 1-8LKQKS It is now possible to uninstall a node when the node status is Start Failed or Stop Failed.

2.0.1 1-8LNDPA In the Administrator UI, after uploading a service assembly with Import Shared Resource Definitions checked, all users now see the newly imported shared resource definitions in the Configure Enterprise Assets > Shared Resources Definitions screen.

2.0.1 1-8LE2FM The correct logical component ID now appears when logging service units to a file.

2.0.1 1-8LH4OC In the Administrator UI Monitor & Manage perspective, throughput for the Since Started period is reset when the service is restarted.

2.0.1 1-8LA7ZL After creating an Administrator server from within the Administrator UI, if you log in to the second Administrator server UI you can now stop the first Administrator server.

2.0.1 1-8G1YVB In the Administrator UI, the initial severity and level value are now restored when you click the Cancel button when editing a logging configuration.

2.0.1 1-8KED7L A substitution variable of type password no longer shows in clear text when editing the password after uploading the service assembly.

Closed in Release



Closed Issues | 31

2.0.1 1-8KIH4Z On Linux, clicking the Running link in the Status column of an Administrator server no longer results in a dialog reporting that the Naming Service Port is not free.

2.0.1 1-8JHAYK In the Administrator UI when you click the UDDI Publishing tab an error is displayed only when you select a business.

2.0.1 1-8JRHWZ Deleting a service assembly containing a service that has been published to the UDDI server unpublishes the service from the registry.

2.0.1 1-8KA8JV When you save a JMS shared resource and configure it with a direct connection the Administrator UI no longer displays a spurious error about an empty factory name.

2.0.1 1-8J139I A service unit logging entry no longer appears on the right side of a logging configuration if you only have view permission for the container logging screen and you try to edit the service unit logging configuration.

2.0.1 1-8HFOCD The Administrator UI now prompts to save information when you switch from editing a shared resource definition to creating a new shared resource definition.

2.0.1 1-8IKAFY In Administrator UI is now possible to save the shared resource profiles list even if a shared resource profile is not mapped to a shared resource.

2.0.1 1-8J56A6 In the Administrator UI, you are now advised that you will lose edits when you have edited a substitution variable value in a service unit and then you switch perspectives.

2.0.1 1-8KSWZF When the ActiveMatrix Administrator Server Creation Wizard cannot proceed due to the machine model file being locked, you are now advised to delete the .lck file in TIBCO_HOME/tools/machinemodel/.

2.0.1 1-8L4R97 On HP Itanium, an Administrator server that was created within the Administrator UI now starts when you use the Start operation in the UI.

Closed in Release



32 | Release Notes

2.0.1 1-8L4RTR If you upload a service assembly and import its shared resources, bind the service units to nodes, bind the shared resource profiles to shared resources, the alert box now asks if you want to create shared resources on the nodes.

2.0.0 1-7YIHMN If you start a service assembly containing a SOAP/JMS service unit when the EMS server configured for the service unit is shut down, the service assembly will not start and its endpoint will not be activated.

2.0.0 1-7Y45SF On Linux, shutting down the Management Daemon by using Ctrl+c in the console no longer causes nodes running on that machine to be shut down.

2.0.0 1-79KWQH A service assembly containing an element, shared resource, or WSDL file that has a space in its path can be deployed.

2.0.0 1-7TUMQV The defaultConnector shared resource appears under shared resources when you click a node in the Nodes list.

2.0.0 1-7Z32YQ In ActiveMatrix Administrator the Quality of Service selection for the Messaging Bus now works.

2.0.0 1-7XA9M0 When ActiveMatrix Administrator is started for the first time on an updated build it no longer displays the "typeErr Undefined" error message on Firefox.

2.0.0 1-7TIXU1 If you create a container with same name as another container, an error message is now reported.

2.0.0 1-7Y67XJ The first time you access the UI of a new ActiveMatrix Administrator server instance an "Operation not found" error is no longer displayed.

2.0.0 1-7TYAXX Management Daemon no longer throws an exception when multiple nodes are created using multi-select.

2.0.0 1-7TV58N The following exception is no longer thrown during node creation:

Admin server registration failed for Mgmt Daemon. JMX address is not specified for a management daemon connection java.lang.Exception: JMX address is not specified for a management daemon connection.

2.0.0 1-79KOFW You can now uninstall a container if a service unit is deployed on the container.

Closed in Release



Closed Issues | 33

2.0.0 1-7T6MLL If a node start fails, the cause is now displayed in the ActiveMatrix Administrator UI.

2.0.0 1-7TCK2A On Internet Explorer the ActiveMatrix Administrator UI response has improved.

2.0.0 1-7TOO77 In a JMS shared resource definition, the Client ID property is now correctly marked as optional.

2.0.0 1-7TV64Q A deployment configuration does not proceed when a required shared resource is not installed.

2.0.0 1-7TY9L1 If you edit a JNDI shared resource definition, the changes are now automatically applied to other shared resource definitions that refer to that JNDI definition.

2.0.0 1-7VKS87 Deployment of a service assembly created from an Eclipse project that has a space in the Eclipse project path is now handled correctly.

2.0.0 1-7Y2WPX Node deletion no longer fails with a database constraint violation when service units are still bound to a container in the node.

2.0.0 1-7YJ9UA The node can now be shutdown if you try to start a service assembly that uses an HTTP resource and the HTTP resource's port is already in use by another process.

2.0.0 1-7YWONV The ActiveMatrix Administrator UI now shows an error if you start a node with a port number that is already being used by another node or application.

2.0.0 1-7TYHU0 Late binding of a JMS resource when configuring an Adapter container service unit is now supported.

2.0.0 1-7TD28X The Management Daemon, ActiveMatrix Administrator server, and nodes can now be run as NT services.

2.0.0 1-7XOIUJ Service assemblies containing an active database Adapter request-response service no longer throw an exception and do not start.

Business Studio

2.3.2 AMSG-7976 All WSDLs display when adding a service.

Closed in Release



34 | Release Notes

2.3.1 1-ARRNNH Service assembly upload no longer fails when a global variable with XML reserved characters ( < , > , & , ' , " ) are present.

2.2.1 1-9GI4ZO If a BusinessWorks component was renamed and then the Service Assembly Editor was refreshed, two BusinessWorks components appeared—one with the old name and one with the new name.

2.2.1 1-9HB6LF A deadlock during deployment caused the packaging and deploying of the service assembly to fail.

2.2.1 1-9HERN1 This release provides enhancements to clean up the debug node directory if the deployment of a service assembly fails during debug of a composite:

• If a file is locked when a service assembly is being uninstalled, the Console view shows this message: ERROR: AMX_MACHINE-11000: Error deleting bundle [ XXXXXX ]

• When debugging of nodes stops, a message suggests that the user clean the debug node by opening the Project menu and using the Clean debug node option.

2.2.1 1-9NSE44 The ActiveMatrix debugger used a large amout of CPU time, affecting development work.

2.2.0 1-8LUKIR The Resource Picker used for picking a port type for a service or reference now displays all the WSDL files that have been added to the project.

2.2.0 1-97MLVL Opening the composite for a SOA project with a topic definition no longer results in a ClassCastException.

2.2.0 1-97N75B A ClasscastException no longer occurs when the composite service is SOAP over JMS.

2.2.0 1-97PZK3 Changing the implementation of the component to which the composite service refers, and then configuring the Composite service target, no longer throws a null pointer exception.

2.2.0 1-9677IJ In an WS-Eventing SOA project, closing the composite by clicking X on the composite tab no longer throws error dialog saying "An Internal error occured during saving the diagram".

Closed in Release



Closed Issues | 35

2.1.0 1-8RZZBO Default names for objects in TIBCO Business Studio are now localized.

2.0.1 1-8LH4S2 After invoking a composite in the debugger, the composite is now editable and you can invoke right-click menu options.

2.0.1 1-8LO1DT Service assemblies containing SOAP/HTTPS shared resource profiles now work in debug nodes.

2.0.1 1-8LO166 If you try to deploy a composite on debugger node and it fails due shared resource deployment problem (port bind problem for an HTTP shared resource or if a database is not running and a component is using a JDBC shared resource), the composite fails to deploy but subsequent deployments no longer fail.

2.0.1 1-8LHVGB You can now stop the debug node by clicking the red Terminate button in the Console tab.

2.0.1 1-8LNG99 JDBC shared resource profiles defined at the component level are now deployed on the debug node.

2.0.1 1-8KE8ZX It is now possible to wire a component reference to a component service when there is more than one reference in the component.

2.0.1 1-8L7CGN It is now possible to log from a debug node.

2.0.1 1-8L33WS When both the composite and component use a JDBC shared resource with JNDI, after uploading the service assembly into Administrator the mapping of the component shared resource profile to shared resource is no longer lost.

2.0.1 1-8L320R The Cancel button now works in the dialogs displayed by the debug launcher.

2.0.1 1-8KM7E2 In Business Studio, the JDBC Driver field displays correctly when you close and re-open the shared resource.

2.0.1 1-8KSUF1 Business Studio no longer gives an incorrect error message about losing a client connection when you stop a debug session.

2.0.1 1-8KSUI1 Setting breakpoints in the composite while in the debug session no longer throws an error: ERROR 23:22:42 PM- BreakPoint with breakpoint id1does not exist.

Closed in Release



36 | Release Notes

2.0.1 1-8KSUJZ You can now launch the debugger even If a composite has errors and the composite is marked with a red x and displays errors in the Problems view.

2.0.1 1-8KSWYJ When you configure breakpoints for composite services and references, the breakpoint symbol now appears in the canvas.

2.0.0 1-7T8VK0 Updating a partner binding does get reflected the service assembly. Now the service assembly is marked dirty and you can refresh the service assembly.

2.0.0 1-783MWC Partner bindings can now be removed.

2.0.0 1-7T6AIV On Linux, the Binding Editor for shared resources and Substitution Variable Picker for service definitions now displays the second column (respectively Binding column and Value column).

2.0.0 1-7YGFSL On Linux, Eclipse SDK no longer throws continuous exceptions when importing a project.

2.0.0 1-783MWC Partner bindings can now be removed.

2.0.0 1-7U38HL Sometimes while working with a service assembly a NullPointerException was thrown. This occurred only when an existing TIBCO Project that had a service assembly file was imported into the Workspace and the service assembly file was opened and when the archive was built. It didn't happen with new projects.

Runtime

2.3.2 AMRP-3803 SOAP/JMS - Response Message no longer appears PERSISTENT instead of NON_PERSISTENT.

2.3.2 AMRP-3822 A WS Addressing request no longer fails if the request comes through a load balancer and the SOAPAction is set to null.

2.3.2 AMRP-3770 The node reconnect issue in cluster has been addressed.

Closed in Release



Closed Issues | 37

2.3.2 AMRP-3784 Added support for Custom HTTP Header Size in HTTP connector resource. The following system property configures the maximum HTTP header size in all HTTP connectors on the node:

amx.httpconnector.maxHttpHeaderSize = <Value in bytes>

A system property of the following form configures the maximum HTTP header size for a specific HTTP connector:

amx.httpconnector.<CONNECTOR_NAME>.maxHttpHeaderSize = <Value in bytes>

A setting for a specific HTTP connector overrides the node-wide setting.

A sample usage of above properties in a node .tra file would be:

java.property.amx.httpconnector.maxHttpHeaderSize=8192java.property.amx.httpconnector.defaultHttpConnector.maxHttpHeaderSize=8192

2.3.2 AMRP-1646 When a SOAP/HTTP reference fails to deliver a message to partner service (if the partner service is down) and a node displays a socket exception, the message is now transferred back to the system error queue

2.3.2 AMRP-3584 When using a SOAP/JMS service, the namespace already declared deserialization error no longer occurs.

2.3.2 AMRP-3409 The wire format for RPC literal when using a SOAP reference no longer has a missing namespace.

2.3.2 AMRP-3272 Calling "wrapper --start" concurrently from two different processes to start an NT Service no longer causes the second call to hang foreover.

2.3.2 AMRP-3244 JDBC shared resources no longer get installed and connected by default on all the nodes (participating under same cluster/environment) when one of the node has the mentioned shared resource defined.

2.3.2 AMRP-3242 After starting a node registered as a NT service, the Administrator UI no longer shows "start failed".

2.3.2 AMRP-3245 An error is no longer seen on certain nodes when attempting to start up a service assembly. It was found that sometimes Subject validation is failing during inter-node communication.

Closed in Release



38 | Release Notes

2.3.2 AMRP-3247 Management Daemon no longer gradually runs out of memory.

2.3.2 AMRP-3246 A thread leak in Adminstrator has been fixed.

2.3.2 AMRP-3086 The TIBCO Enterprise Message Service client library has been updated to address node 100 % CPU consumption.

2.3.2 AMRP-3093 Nodes no longer crash while undeploying the endpoint that was not registered with the Policy Manager during previous deployment attempt.

2.3.2 AMRP-3094 Signature verification no longer failing due to XML canonicalization issue at XML security layer.

2.3.2 AMRP-3085 Accessing mutual authenticated SSL web service now supported.

2.3.2 AMSG-7996 JDBC shared resources now support login timeout.

2.3.1 AMSG-7714 Now able to retrieve RelatesTo and RelationshipType attribute from WS-Addressing header.

2.3.1 AMRP-2534 Synchronization between Policy Agents and Policy Manager are no longer affected when endpoint custom attributes are missing.

2.3.1 AMSG-7747 JMX access is no longer corrupted if JMX remote access is enabled.

2.3.1 AMSG-7764,AMSB-1492

Sun/Oracle JRE on the Solaris, Windows, and Linux platforms has been upgraded to 1.6.0_20 from 1.6.0_18.

2.3.1 1-A6CV3J JMS bindings now propagate JMSRedelivered in the transport headers to the component implementation. You can filter the redelivered messages by adding a property java.property.jmsbinding.filterredelivered=true in the TRA file of the runtime node.

2.3.1 1-ABYMCR SOAP/JMS transport bindings now propagate JMSRedelivered in the transport headers to the component implementation. You can filter the redelivered messages by adding a property java.property.soapjmsbinding.filterredelivered=true in the TRA file of the runtime node.

2.3.1 1-AMO0U5 A JNDI-based JMS shared resource now correctly loads a custom object factory when used in SOAP or JMS bindings.

Closed in Release



Closed Issues | 39

2.3.1 1-ASSAYG The exception "TIBCO-BT-AMX-801024: No response exchange channel found for exchange" is no longer thrown and correlation between consumer and provider works.

2.3.1 1-AV4QUF When user context info generated by an authentication policy on a SOAP binding is propagated to a mediation component, the SAML attribute received by the mediation component now contains multiple values if the user attribute in LDAP has multiple values.

2.3.1 1-APC1IP,1-AJ4PYR,1-9XF7TL

Install Entrust's JSSE provider, allow to be compatible with JVM's JSSE and work when called from third-party libraries (LDAP, JDBC allow Entrust to be installed last.

2.3.1 AMRP-2358 It is now possible to retrieve RelatesTo and RelationshipType attributes from a WS-Addressing header.

2.3.0 1-9ZIG0Y When a service assembly log level is set to Debug SOAP references no longer move SOAP headers to the SOAP body.

2.3.0 1-9QWGJL Socket time out is no longer reported to the client in IN-OUT scenario when provider node shuts down gracefully during processing of the message.

2.3.0 1-9UB4SC A runtime exception is no longer raised in the node startup console when a service assembly is deployed and undeployed multiple times.

2.3.0 1-9ZDIW9 Interoperability issues using BEA and IBM JMS servers for SOAP over JMS bindings (reference only) and JMS bindings (reference and service) are resolved. For details, see Configuring ActiveMatrix Service Bus to Interoperate with BEA WebLogic and IBM WebSphere JMS Servers on page 3.

2.3.0 1-9UHJZ5 ActiveMatrix no longer raises a null pointer exception if a fault message has an empty detail element. The detail element can be empty according to SOAP 1.1 specification.

2.3.0 1-A27ANJ Components can now set endpoint references for SOAP/HTTP providers at runtime based on business data.

2.3.0 1-A27UQU Service units with SOAP/JMS with static reply queues can now be deployed on multiple nodes for In-Out MEPs. The SOAP/JMS binding will correlate replies coming for multiple clients on the same queue.

Closed in Release



40 | Release Notes

2.3.0 1-A6CV3J JMS bindings now propagate JMSRedelivered header in the transport headers to the component implementation. You can filter the redelivered messages by adding a property "java.property.jmsbinding.filterredelivered=true" in the TRA file of the runtime node.

2.3.0 1-ABYMCR SOAP (JMS transport) bindings now propagate JMSRedelivered header in the transport headers to the component implementation. You can filter the redelivered messages by adding a property "java.property.soapjmsbinding.filterredelivered=true" in the TRA file of the runtime node.

2.2.1 1-91LKYL .NET did not support the attribute element as part of a complex type.

2.2.1 1-9TPA1T View Logs in SPM used the non-default log service to query logs.

2.2.1 1-9T3CF0 The ActiveMatrix SOAP reference component threw a "connection reset" error when the persistent connection between the reference and the server were closed because of a timeout, and both services were running on the same machine.

2.2.1 1-9N2YSP Some logs were lost when a large number of logs that already existed in the EMS queue were written to a database or a file.

2.2.1 1-9PHRK3 Copy/paste is now available for log columns and Event Details in the LogViewer.

2.2.1 1-9QL195 The conversationId attribute has been added to improve traceability. In the CBE format the attribute name is localInstanceId.

2.2.1 1-9QL1AC The number of entries in the reporting component ID table is now correct.

2.2.1 1-9QSSLT The ActiveMatrix Administrator log service component no longer throws deadlock exceptions when there are multiple log services updating the same database.

2.2.1 1-9QSSMU ActiveMatrix Administrator Monitor & Manage component no longer throws an out of memory exception when a large record set is retrieved.

Closed in Release



Closed Issues | 41

2.2.1 1-9P660F The BEFMapConverter class handles scheme = stats correctly. StatsEventFormat messages no longer are reported as RollingStatsEventFormat messages.

2.2.1 1-9RAE1O A warning now notifies the user if a Run Query/Hint record count is greater than (XXX), enabling the user to cancel or continue running a large query.

2.2.1 1-9RAE15 An hourglass now shows when the system is working.

2.2.1 1-9RAE29 When query results display, the query is collapsed.

2.2.1 1-9RAE36 Warning messages have been added to disruptive actions, warning users that changes might clear information.

2.2.1 1-9RAE43 Additional information has been added to include the definition of the model.

2.2.1 1-9SLY13 You can now sort by clicking a column in the log display.

2.2.1 1-9T3BCH Copy/paste is avaliable for log columns and Event Details in the LogViewer

2.2.1 1-9QSLUR A new Java property provides a way to configure the stdOut and stdErr logs, to redirect them to a specific directory: java.property.logs.base.dir=redirect_dir

To use this property, add it to the node’s .tra file.

2.2.1 1-9T3CF0 The ActiveMatrix SOAP reference component threw a connection reset error when the connection between the reference (client) and server was closed because of an idle timeout and both services were running on the same machine.

2.2.1 1-9NX8BR When a provider was not available in a SOAP-over-JMS-Java scenario, messages did not go to the error queue and were lost. Messages sent using pureJMS worked correctly.

2.2.1 1-9LT4LN ActiveMatrix could retrieve a message only if the JMS header contained an exact case match of the property’s name. The selector has been changed to be case insensitive.

2.2.1 1-9OB7RX The ActiveMatrix ServiceProbe did not give valid values for MessageSize when SOAP/JMS was used as the transport for a service.

Closed in Release



42 | Release Notes

2.2.1 1-9P6QYL WS-RM service threw an exception when the service was undeployed then redeployed without any changes.

2.1.0 1-7ZER9J When the type of a fault's message part is specified in an element attribute, a service running on the .NET service engine now receives faults sent by a partner as a TServiceException.

2.0.2 1-8VR1X1 The performance of the Policy Manager console no longer degrades when the number of registered and managed services increases ( > 75 services)

2.0.2 1-8WMYQJ Exceptions are no longer thrown when a policy is set for a node where body-based dispatching is enabled.

2.0.1 1-8L2VSL When you generate a WSDL from a Swift Adapter configuration, the generated XSD schema no longer have multiple schema components with the same name. The generated WSDL that refers to these generated schema components therefore are now valid.

2.0.1 1-8LS0Z5 JMS service In* MEPs and JMS reference Out* MEPS will now handle complex types when the client sends an XML instance element with a complex type without the namespace set.

2.0.1 1-8L7BTF Processing SOAP headers containing an simple element or a complex element no longer throws a NullPointerException.

2.0.0 1-795YAD When you started a node, the exceptions ServiceUnavailableException, NameNotFoundException, and UnsatisfiedLinkErrorException no longer appear in the node log.

2.0.0 1-7WOR4G If you run two services based on the same WSDL file on two different ports, one of the services will no longer override the other one.

2.0.0 1-7XQZNP Logging from a service unit now works correctly. The service unit name is unique for the container.

2.0.0 1-7YAF2N A SOAP over JMS provider binding would not receive a request message when the SOAP Action is not within double quotes. For example: 'soapaction' or soapaction.

2.0.0 1-7UZHJS SOAP headers were not supported in the runtime even though they could be specified as the type of a message part in a binding definition.

Closed in Release



Closed Issues | 43

Mediation Container

Closed in Release


2.3.2 MED-2372 If two XSDs referred from a WSDL import each other, stackoverflow exceptions are no longer thrown.

2.3.0 1-9W2MSC Service assembly deployment no longer hangs in the case of mediation flows referring to a WSDL that define multiple in-line schemas that refer to one another.

2.3.0 1-9Y6G01 In the event of One-way message, if the reference component does not exist or is not running, Mediation now provides mechanism to put the message in the error queue ($sys.undelivered).

2.3.0 1-A0KG0F When a user configures a ThrowFault to throw a declared fault, now a fault path is created with a Catch and a Send for the declared fault.

2.3.0 1-97AW6H When you opened the Coercions dialog box, the Browse button did not appear if the namespace in the XPath field was longer that it did not fit inside the default dialog box.

2.3.0 1-971EXR If the dynamic routing feature was in use when the service assembly started, monitoring showed that the mediation had stopped, although it was still running.

2.3.0 1-9656X7 The Parse XML task did not support EUC-JP-LINUX encoding in binary mode.

2.3.0 1-9146M9 The SSL Server in the ActiveMatrix provider overwrote TIB Crypt if you did not use the default Entrust and define the property in the node.tra file.

2.2.1 1-9P3BRV The dash (-) character in the portType name was incorrectly interpreted.


44 | Release Notes

2.2.1 1-9RJI87 An error during deployment prevented deploying a service assembly with mediation on the AIX platform.

2.2.0 1-8R2ERD There were error marks in the mediation flow editor when you imported an existing project that had no error in the original version.

2.2.0 1-8QEF82 Typographical error in the Route Mediation Task Property. "Dicistion" instead of "Decision".

2.2.0 1-8QKXER Fault element was not generated in the local WSDL when using "copy interface" if the original WSDL included a fault element.

2.2.0 1-8QBV69 On the catch fault's property view, "catch all" could be unchecked when other options were all unchecked.

2.2.0 1-8PDRTH The mediation path created from in-only WSDL became an unknown mediation path after saving and re-opening it.

2.2.0 1-8P72BX The mapper went into an infinite loop after a user right-clicked and selected the "Expand All" option on the left side of the mapper.

2.2.0 1-8P69AN The Throw Fault task was not deletable.

2.2.0 1-8NZOHH When using a schema that had deeply nested repeating nodes on the input and output sides of the mapper, mapping at the lop-level node did not automatically map the nested repeating nodes.

2.2.0 1-8MAZ6G This error was thrown during a refresh: An internal error occurred during: "Changed"

2.2.0 1-8LND9B Only the Throw Fault icon was changed to a large icon after changing the Preferences from the small icon setting to the large icon setting.

2.2.0 1-8LKOYP A null pointer exception was thrown when a user moved the mouse from the mediation flow editor to the error log view.

2.2.0 1-8LA8K0 Design time: When routing a mediation task, the column with the focus lost its value if you set the operator and value for a decision case, then clicked on the Other column, then clicked on a route task in the mediation editor.

Closed in Release



Closed Issues | 45

2.2.0 1-8LA8IB Design time: When routing a mediation task, if you set the decision case for a string type variable using operators such as <, >=, != to start the string value, the current operator was replaced and confused the value.

2.2.0 1-8LA4NP The order of JMS items in the log file was different from that in the mapper.

2.2.0 1-8LA6X3 The composite was serialized with wrong URIs when the user used drag-and-drop for the wire configuration.

2.2.0 1-8KWJOD Design time: When using the Composite Editor to make a composite with multiple services and references, if you clicked on the tags representing the linking point of the components and then hovered the cursor over each of them, the content of the tool tip changed.

2.2.0 1-8KLNQN Exceptions returned by the Mediation container during deployment of a service assembly were not correctly reported in the ActiveMatrix Admin UI.

For example, the Mediation component instance returned an exception on invocation of the init method (com.tibco.sca.runtime.spi.support.AbstractComponentInst

ance.init(..)) but the Admin UI displayed this error message:Unable to deploy service assembly 'TestAssembly1'. Reason: java.lang.reflect.UndeclaredThrowableException, caused by: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: Class Not Found : com.tibco.amsb.core.engine.MediationEngineException (no security manager: RMI class loader disabled), caused by: Class Not Found : com.tibco.amsb.core.engine.MediationEngineException (no security manager: RMI class loader disabled)

2.2.0 1-8KILWN Design-Time: In "properties of mediation", property values were lost if you created serveral named properties, gave them initial values, saved, clicked on the path and back again by clicking on the mediation, select its properties and click on each row, the values.

2.2.0 1-8K449D [G11N] If case name in Route/Xpath Route Task contained the double byte data, the deployed AMSB service was not called in the Business Works client. The deployed service threw the exception.

2.2.0 1-8K6TU9 [G11N] Composite name didn’t support multi-byte characters such as Japanese.

Closed in Release



46 | Release Notes

2.2.0 1-8K4489 [G11N] If routing rule in Xpath Route Task contained double-byte data, the deployed ActiveMatrix Service Bus service was not called in the Business Works client. The deployed service threw the exception.

2.2.0 1-8IKHKD [G11N] If you selected the “Text” message type of transport configuration of service, the ActiveMatrix Service Bus service was not called in the Business Works client when the data contained double-byte data.

2.2.0 1-8HZCLD [G11N] If routing rule contained double- byte data, the deployed ActiveMatrix Service Bus service was not called in the Business Works client. The deployed service threw the exception.

2.2.0 1-8HWCV6 If a WSDL having choice type element when used in the target area and the schema was viewed through a transform task, the choice elements did not appear immediately because of a refresh issue.

2.2.0 1-8HRKQD There was an inconsistency between the ActiveMatrix Service Bus UI and the Composite UI, in the drag-and-drop feature and other Edit features such as deleting an interface.

2.2.0 1-8GVV5L The ActiveMatrix Service Bus UI did not give warning information if you created a composite with the same name as an existing composite by using the Generate Composite option of the right-click popup menu on the mediation flow.

2.2.0 1-8EHUOO There was no horizontal scroll bar when the area of target endpoint and mediation interface were so small that the entire operation names could not appear.

2.2.0 1-8EEDM7 If you re-ordered the target interfaces, the exception "Widget is disposed" was thrown.

2.2.0 1-8EBHRI The buttons on the header row of the mediation interfaces and the target interfaces didn’t appear if the name of the WSDL file was too long.

2.1.0 1-8JH813 Security context information was not properly written to the log file when the transport was HTTPS.

2.1.0 1-8JJZJ4 Transport-level security assertions were not available. For example, HTTPS security context information was not available for use within a mediation flow.

Closed in Release



Closed Issues | 47

2.1.0 1-8JOJF6 Type xsd:any was not supported for ActiveMatrix Service Bus.

2.1.0 1-8LA6X3 Dragging and dropping a wire from a composite service to a mediation component caused the URIs to contain a relative path to the resource (for example, /Service Descriptors/a.wsdl).

2.1.0 1-8MBDUR In Chapter 7, Custom Mediation Tasks in TIBCO ActiveMatrix Service Bus Mediation Design Guide, under the section "Packaging Custom Mediation Tasks", step 4 gave an incorrect example location of where to export your custom task plug-in.

Closed in Release



48 | Release Notes

Known Issues

This section lists known issues in this release.

Installation, Documentation, Administrator, Business Studio, RuntimeTo view defects for a particular feature, see the sections:

• Installation on page 48

• Documentation on page 50

• Administrator on page 50

• Business Studio on page 55

• Runtime on page 64

Change Request ID Summary/Workaround

Installation

1-8REZ3J Summary The localized error message shown in the popup screen during installation of Visual Studio Extensions is garbled.

Workaround None.

1-9T985L Summary An incorrect name in a response message should be handled with an appropriate error.

Workaround Specify the correct fault name in the response message.

1-8J216O Summary On 64 bit Linux the password text box for the database authentication realm screen in the Administrator Server Creation Wizard is not rendered.

Workaround The lack of visibility of the text box does not affect the function. Click the text box and type the password.

1-972JFJ Summary On HP installation with space in the name of the installation directory does not work.

Workaround Install in a directory without a space in the name.


Known Issues | 49

1-972RIR Summary On Hewlett Packard the installer fails to start the database when the user chooses to start the database and launches the Administrator server creation wizard.

Workaround Start the database manually.

1-95TLYR Summary Clicking the Finish button at the end of the installation does not stop the installer when installing ActiveMatrix Service Bus 2.1 on top of ActiveMatrix Service Bus 2.0.2.

Workaround Stop the installer process, but only if the installation is at the post-installation summary panel and the "please wait" message is visible.

If you stop the process before the installer gets to this point, temporary files are not removed:

* On UNIX and Linux, istemp* directories remain in the /tmp directory

-- To stop the installer process on UNIX and Linux, end the process that was running on the specific command prompt by using Ctrl+C.

* On Windows, ismp* directories remain in C:\Documents and Settings\user\Local Settings\Temp.

-- To stop the installer process on Windows, end the process name TIBCOUniversalInstaller.exe.

1-96IX7C Summary It is not possible to uninstall 2.1.0 if you install it over 2.0.x.

Workaround None.

1-8KSW7L Summary While installing only Administrator, the following error (cant find spline plugin) is seen during classpath flattening: # Could not find a bundle description for the plug-in "com.tibco.neo.service.spline".

Workaround Ignore the error.

1-8L2HY3 Summary If you do a custom installation and you go back and forth between the selection screens, the feature dependencies are no longer correct and extra features may be installed. For example, if you select to install ActiveMatrix Service Grid then later go back and select only ActiveMatrix Foundation, ActiveMatrix Foundation and ActiveMatrix Service Bus features will be installed.

Workaround Select the correct features the first time.



50 | Release Notes

1-AFTUL2 Summary Starting 2.2 nodes from a 2.3 Administrator shows "Start Failed" even for nodes that started successfully and "unknown" status for service assemblies that are running on these nodes.

Workaround Upgrade the nodes to 2.3.

1-AH9825 Summary While Installing adFileSE on top of ActiveMatrix 2.3.0, the Installer displays Fatal Error:Failed to load Shared Library:Library Name.

Workaround Copy TIBCOUniversalInstaller.exe from the ActiveMatrix installer folder into the adFileSE Installer folder before installing adFileSE.

Documentation

1-8I0Z4B Summary The Business Studio documentation link Windows All Programs > TIBCO > Business Studio 2.1 > Documentation is not valid because the doc directory is empty.

Workaround None.

Administrator

1-78C06X Summary It is possible to remove a shared resource even if there are running service assemblies using it.

Workaround Stop and undeploy the service assembly before removing the resource.

1-7YGFY6 Summary Substitution variables defined in a service definition can be accessed in all the service units in the service assembly containing the service definition. However, if you configure the substitution variable in the service unit containing the service definition, the updated values do not show up in the other service units.

Workaround None.

1-7YREXS Summary Updates to substitution variables are not used when a service assembly is restarted.

Workaround Undeploy the service assembly and redeploy it.

1-8DKJDD Summary Deployment of a service assembly fails when the service assembly has two components implementing the same port type in the same service unit.

Workaround Split the implementations across multiple service units.



Known Issues | 51

1-8EA3N3 Summary A dialog box with the message "500 Error Code. Operation not found EPR is..." sometimes appears when the Administrator UI is accessed for the first time after the Administrator server is restarted.

Workaround Dismiss the dialog by clicking the OK button.

1-8JL6FR Summary To test JNDI based JDBC connections from Administrator, you must install the database-specific JARs.

However, to simply create the shared resource on a node, you do not need the JARs.

Workaround None.

1-8KAMDV Summary For an HTTP shared resource definition and a node's default connector the following fields are not used by the runtime:

- Enable DNS Lookup

- Redirect Port

- Disable Upload Timeout

Workaround Don't use these fields.

1-8KPCUT Summary On highly loaded systems sometimes the error "org.apache.axiom.om.OMException: SOAPEnvelope must contain a body element which is either first or second child element of the SOAPEnvelope" is displayed in the Administrator UI

Workaround:

1.Go to the directory AMX_ADMIN_HOME\data\admin_cluster\admin_server\config\.

2. Increase the value for <keepalive-timeout-millis> in web-config.xml. By default, the value is 10000 and its unit is milliseconds. Increase it to a higher value, for example 20000.

1-8KVW5F Summary A WSDL file retrieved from the Monitor & Manage > Service screen does not reflect a change in a shared resource definition when you and undeploy and redeploy the service assembly.

Workaround Request the WSDL file from the node. First use the inspection URL http://hostname:defaultconnectorport/inspection.wsil to get list of services. Then use the node WSDL URL. It should be of the format: http://hostname:httpsharedresourceport/servicename?wsdl. For example: http://spiderman:8086/bookstoreservicesoap?wsdl.



52 | Release Notes

1-8M830B Summary JDBC WARN trace statements are seen in the Administrator console when Administrator server is started in command-line mode.

Workaround None. These are harmless and do not affect the product functionality.

1-8M84US Summary When there are multiple installations on the same machine, and hence multiple management daemons (one per installation), then the Administrator started from one of the installations is occasionally unable to create/delete nodes on the management daemon from the other installation (after discovering and binding it). A NullPointerException is observed while deleting the node and it is not possible to delete the node.

Workaround Do not have multiple Administrator or Runtime installations on the same machine. On Windows, the installer does not allow it anyway. So this is really a restriction only for Linux.

1-8SDXP2 Summary If the only change to an already published service is in the metadata section, republishing the service fails to communicate the changed metadata to the UDDI server.

Workaround Unpublish the service and then publish it again.

1-8SW8JV Summary The Administrator UI does not prevent you from starting multiple versions of the same type of container. However, if more than one version of a container is active, the behavior is unpredictable.

Workaround Activate only one version of a container at a time.

1-8U69UN Summary When two service assemblies, both having a Java component with identical packagename-classname combinations, are mapped to the same node, deployment will fail.

Workaround Ensure that all Java components have unique packagename-classname combinations when you are mapping service assemblies to the same node.

1-95OP5W Summary When starting the ActiveMatrix Administrator with the Sybase database the ActiveMatrix Administrator server sporadically reports an error.

Workaround None. The exception is benign and can be ignored.

1-96N2LZ Summary If you attempt to use the command-line interface to uninstall an HTTP resource with SSL configured, an error is thrown.

Workaround Uninstall using the Administrator GUI.



Known Issues | 53

1-97BJ0T Summary If you change the log service, no notification is sent to the node.

Workaround Restart the node to get the log service information.

1-97N4OZ Summary The machine memory is not getting updated in the Monitor and Manage screens.

Workaround None.

1-9KICSK Summary In the Monitor & Manage perspective, a node shows defaultHttpConnector but it is not shown in Configure an Environment > Node > Shared Resources screen.

Workaround None.

1-9LGA22 Summary ActiveMatrix Administrator should throw an exception and ActiveMatrix nodes should log a message when topic-queue bridge creation fails if the EMS Username property is empty for the Message Bus configuration and you try to deploy a publish-subscribe service assembly.

Workaround Create a topic queue bridge manually in the EMS server before deploying the service assembly.

1-9MJE8J Summary The ActiveMatrix Administrator UI does not display on Internet Explorer 6, SP3 running on Windows XP SP3.

Workaround Use Internet Explorer 7 with Windows XP SP3.

1-9MN8ZK Summary If you are using the Sybase database and upgrade nodes from 2.1 to 2.2, or from 2.2 to 2.3, the upgraded nodes fail to start.

Workaround Open the file AMX_HOME\2.3\server\templates\extra-amx-osgi.properties

and locate the following properties:

amx.root.features=com.tibco.tpcl.sybase.jconnectamx.closure.features=com.tibco.tpcl.sybase.jconnect

Open the corresponding file in the 2.3 folder and copy the properties over to the 2.3 file. If the extra-amx-osgi.properties file is not present, copy the file from the older version.

1-9N5EGT Summary The log viewer reports errors when importing log files generated by containers and JMS service units.

Workaround Log to JMS instead of to a log file.



54 | Release Notes

1-9N9MWH Summary On Sybase an incompatible change introduced in the ActiveMatrix Administrator schema causes the script generated by dbscriptgenerator -genupdates to show an error when run.

Workaround Update the DDL generated by dbscriptgenerator -genupdates. In the DDL, look for 'Alter table <tablename> add statements and append ' null' at the end of these statements.

1-9NTN0S Summary Even when the database tables are precreated, the process of creating an ActiveMatrix cluster takes a very long time.

Workaround None.

1-9O23U7 Summary Test Connection passes for a JMS direct shared resource even when the Connection Factory is deleted.

Workaround Close the shared resource and reopen it. The default value for Connection Factory will be populated.

1-9O4D4R Summary The log services are lost when you create a log service whose JMS shared resource contain special characters. For example, if the name of the JMS shared resource is "JMS&d".

Workaround Ensure that the name of the resource does not contain special characters.

1-9O6XQX Summary After enabling monitoring in a cluster starting another Administrator server in the same cluster may cause an exception.

Workaround Restart all the Administrator servers in the cluster.

1-9SHSBX Summary When a log service configuration change involves changing the log service queue name, the change doesn't take effect on the node unless the node is restarted.

Workaround Restart the nodes.

1-AGODNO Summary The Administrator server creation utility fails if you use the native driver for Microsoft SQL Server 2008.

Workaround Use the tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver driver.



Known Issues | 55

1-AHU51D Summary While upgrading the Administrator server from 2.2.0/2.2.1 to 2.3.0, the following error displays:

#Plugin at "<AMX_HOME>/components/eclipse/plugins/com.tibco.matrix.spm.serviceprobe.admin.services.impl_1.0.200.001.jar" is missing a required plugin: com.tibco.security.tibcrypt;bundle-version="[2.12.0,2.13.100)"#

Workaround This is a spurious error and can be ignored.

1-AH0CXV Summary In Administrator, the service unit name does not get refreshed when you click View Service Instance Details.

Workaround Navigate to the Service Unit Details screen from the Dashboard screen.

Business Studio

1-9DSVOO Summary When associating a ActiveMatrix BusinessWorks project containing a service resource with a BW Component, closing of the ActiveMatrix BusinessWorks project throws a NullPointerException in the workspace log.

Workaround None.

1-9SGFET Summary After installing 2.2.1 on top of 2.2.0 the SOAP container is not activated on an existing node that is not upgraded.

Workaround Upgrade the all nodes on the machine where 2.2.1 is installed. If you cannot upgrade the node, do not do any new deployment on that node.

1-9TSLXN Summary If a substitution variable is used in the Key Store and Entry Alias fields, the identity shared resource produces an error. This is harmless and can be ignored.

Workaround None.

1-9U6DVJ Summary If a substitution variable is used in the Certificate Store field, the SSL Client shared resource produces an error. This is harmless and can be ignored.

Workaround None.

1-9TVO0I Summary The debugger throws the error Getting NoClassDefFoundError.

Workaround None. You can ignore the error, as it is harmless.



56 | Release Notes

1-8BI6NJ Summary When you rename a composite and press the OK button, the canvas gets closed.

Workaround Double-click the composite to open it.

1-8D1JLJ Summary If you move a component that is connected by a wire to another component, the wire is not routed correctly.

Workaround Move the components further apart.

1-8GM3DE Summary If you rename a composite that is open in an editor, and double-click on the renamed composite file, the renamed composite opens in the editor, but the composite also remains opened with the old name.

Workaround Close a composite before renaming it.

1-8GP9AX Summary If you have a composite open, rename the Composites folder, and then open composite in the new folder by double-clicking it, opens a second composite of same name in the editor. The same behavior is observed when you rename the project.

Workaround Close the first composite before renaming the folder.

1-8K65ED Summary It is possible to wire in-only services to in-out references.

Workaround Only wire services to references with a matching MEPs.

1-8T2VKO Summary Changes made to a composite being debugged are not reflected in the debug session.

Workaround Restart the debugger node.

1-95TLWQ Summary When a composite has an error, sometimes the error marker is shown in the Project Explorer, but not in the Composite Editor.

Workaround None.

1-97GYZ9 Summary When you create a WS-Transfer project using WS-Transfer SOA Project Wizard, an error is reported on the Java component in the composite.

Workaround Do a clean build by selecting Project > Clean....

1-9J1KKY Summary The TIBCO Business Studio debugger throws a null pointer exception in the node console even though the node starts successfully.

Workaround Ignore the exception.



Known Issues | 57

1-9LQD67 Summary When a WSDL file is refactored and moved to a new location, the composite does not get updated with the new location.

Workaround None.

1-9MXVCT Summary On Linux the Service Import Wizard the does not import the XSD referenced in the WSDL file.

Workaround Copy the XSD to the SOA project.

1-9O0H47 Summary After modifying the SOAP action field for the SOAP service, clicking the Generate WSDL button does not generate the concrete WSDL or display an error message.

Workaround None.

1-95J80G Summary Unable to generate WSDL in BS with Generate WSDL button when a shared resource uses substitution variables.

Workaround None.

1-7XQZ5W Summary On Linux, if you change the port of an HTTP shared resource in a TIBCO project, the endpoint URI is not updated.

Workaround Do not change the port number at design time in the HTTP Shared Resource while designing TIBCO Projects on Linux machines. At deploy time, bind a HTTP resource with the desired port.

1-8EN60S Summary If you update the value of the URL in an HTTP server shared resource referenced by a service, the WSDL generator does not pick up the modified URL.

Workaround Recreate the shared resource, rebind the service to the shared resource, and regenerate the WSDL file.

1-8HRM6X Summary When Business Studio starts up, error messages of the following format appear in the PDE runtime error log: Could not install bundle plugins/xxx_yyy.jar Bundle "xxx" version "yyy" has already been installed from: update@../components/eclipse/plugins/xxx_yyy.jar

Workaround Ignore the messages.



58 | Release Notes

1-8IO95B Summary In Business Studio a validation error is reported after generating the Adapter WSDL for Rendezvous Reliable and JMS shared resources

Workaround Open the shared resource and select any of the fields (for example, Daemon). Business Studio will launch the substitution variable dialog. Select the Daemon variable and click OK.

1-8K29TP Summary Shared resources that use substitution variables becomes dirty when you open the shared resource.

Workaround None.

1-8KSU55 Summary Upon debugger node startup you might see some SQL errors in the debugger node console.

Workaround Ignore the errors.

1-8L2VWB Summary When you change the Style field at the operation level for a SOAP service, a NullPointerException shows in the error log.

Workaround Ignore the exception as it is harmless.

1-8LHH9H Summary Sometimes a save failed dialog appears when you save a composite. This sometimes occurs when building is in progress or when some process in the workspace is using the WSDL files or shared resources the composite references.

Workaround Ignore the error, wait a few seconds and press save again.

1-8MA3CO Summary Command line utility to create a service assembly archive fails to create a new archive when an archive with the desired name and location already exists.

Workaround Ensure that a service assembly archive with the desired name and location does not exist.

1-8UC9UR Summary The debugger uses the value of TIBCO_HOME from the environment variables before using the value from the Debug Launch Configuration. The TIBCO_HOME set in the Debug Launch Configuration should have higher precedence than the environment variable.

Workaround None.



Known Issues | 59

1-9BIRMT Summary When a WSDL file having an uppercase .WSDL extension is imported it is not visible for configuring the composite service and reference and component service and reference.

Workaround Rename the file to have a lowercase .wsdl extension.

1-9JC5FB Summary The exceptions javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found and NoClassDefFoundError appear in the node console when running the debugger.

Workaround These exceptions do not effect any functionality and can be ignored.

1-9N0YZ5 Summary In the composite editor when a mediation component has dynamic routing enabled in the mediation flow, the dynamic symbol or icon does not appear on the mediation component.

Workaround None.

1-9NK2C5 Summary After you install ActiveMatrix Service Performance Manager 1.1.1 TIBCO Business Studio cannot be started.

Workaround Start TIBCO Business Studio with the -clean option.

1-94R2Z9 Summary When a shared resource or mediation referenced from a composite is modified, the composite is not updated to reflect the change.

Workaround Close and reopen the composite to see the changes.

1-95GEQ1 Summary On Linux platform, when you try to add a service or a reference for a Java component in TIBCO Business Studio, the resource picker does not list all the previously imported projects in the workspace to pick up the WSDL.

Workaround Restart TIBCO Business Studio.

1-97N6NU Summary When you click "Verify Keystore Alias Password" in an Identity shared resource an error message displays suggesting the password typed in for the keystore or the key is invalid, even if you supply the right value.

Workaround Confirm that the password is correct and ignore the error message.

1-98OBOZ Summary If you rename a composite when the corresponding service assembly file is open, an exception displays in the console.

Workaround Close the service assembly file before renaming the composite.



60 | Release Notes

1-8HFOIQ Summary If a component/binding that has a validation error is deleted and a new component/binding is added with the same name, validation errors will be seen.

Workaround The errors will go away after you save the composite.

1-8HSTCH Summary The composite canvas is not painted properly on a Linux terminal. There are several blacked and greyed out areas on the canvas as you try to add components and edit. This is a problem when using Hummingbird Exceed or similar tool to access the Linux machine.

Workaround Log directly in to the terminal's machine.

1-9BDKU8 Summary The debugger in Business Studio does not work after Service Performance Manager is installed on ActiveMatrix Service Bus 2.1.0 or ActiveMatrix Service Bus 2.2.0 + ActiveMatrix BusinessWorks Service Engine 5.7.0.

Workaround

1. Ensure Business Studio is closed.

2. Delete the lower version of Features and Plug-ins for the following plug-ins in TIBCO_HOME/components/eclipse/features and TIBCO_HOME/components/eclipse/plugins. Only the following versions of Features and Plug-ins should be in your installation.

Feature: com.tibco.tpcl.org.dom4j.feature_1.6.1.001

Plug-ins: com.tibco.tpcl.org.dom4j_1.6.1.009

Feature: com.tibco.tpcl.org.apache.commons.pool.feature_1.3.0.001

Plugins: com.tibco.tpcl.org.apache.commons.pool_1.3.0.011

3. Restart Business Studio with the -clean option.

1-8E05WH Summary Renaming the general project into which a Designer project has been imported is not supported.

Workaround None.

1-961S1Y Summary WSDL generation fails in the SOAP service > Binding tab if the HTTP shared resource in Shared Resource Profile uses substitution variables for the Host property.

Workaround None.



Known Issues | 61

1-7A0YBJ Summary During Adapter binding definition creation, WS-I compliance warnings regarding the WSDL file generated are displayed in the Problems tab.

Workaround Ignore the warning.

1-7SX3QN Summary The concrete WSDL generation option in a SOAP provider binding definitions doesn't support some forms of imported schemas contained in the abstract WSDL. If the abstract WSDL needs to refer to an imported schema, the following are the different ways to do so:

1. Using a wsdl:import statement:

<wsdl:definition?><wsdl:import namespace=http://myschema location=?./myschema.xsd?/><wsdl:types>

2. Using an xsd:import in an embedded schema, where the embedded schema has no namespace:

<wsdl:definition?><wsdl:types><xsd:schema><xsd:import namespace=http://myschema schemaLocation=?./myschema.xsd?/></xsd:schema>

3. Using an xsd:include in an embedded schema, where the embedded schema has the same namespace as the included schema:

<wsdl:definition?><wsdl:types><xsd:schema targetNamespace=?http://myschema?><xsd:include schemaLocation=?./myschema.xsd?/></xsd:schema>

Workaround The WSDL Editor in Eclipse SDK doesn't support 1., and this form is not recommended by WS-I basic profile. The WSDL Editor generates the import as in 2., but the concrete WSDL generator doesn't support this form. The WSDL editor can generate 3. if you edit the source view. This form is supported by the concrete WSDL generator.

1-8J5473 Summary The port type resource picker for JMS services and references allows you to pick a port type that has operations containing fault messages with complex types. However, these messages are not supported in the runtime.

Workaround Only choose port types with fault messages that use simple types or elements.



62 | Release Notes

1-87M3RT Summary The Adapter container does not support duration strings having years and months.

Workaround Only duration strings without years and months should be used. For example: [-]PnDTnHnMn[.m]S

1-8LDSPV Summary Designer Project validation is not successful, if you import an Adapter WSDL or XSD, into a Designer project that contained the original Adapter configuration from which these WSDL or XSD files were generated.

Workaround Do not import the generated WSDL or XSD into the project that contains the Adapter configuration. Use a different project.

1-8LDSRC Summary Concrete WSDL generation fails when an adapter configuration contains RPC client services.

Workaround Use an Adapter configuration that does not any RPC client services or delete the port type operations and corresponding bindings from generated for RPC client services from the WSDL generated for the Adapter configuration.

1-8MAS7V Summary The Style and Encoding fields at the operation level are not overriding the Style and Encoding settings at the port type level. This causes a problem when generating the concrete WSDL file.

Workaround If any of the operations has multiple parts, the Style and Encoding fields have to be set at the port type level for Generate WSDL functionality to work.

1-8MF2X3 Summary It is not possible to download from any update site.

Workaround Select Help > Software Updates > Manage Configuration and disable the TIBCO XData RT Feature and then download.

1-8EXNFE Summary WSDL file generation fails when the WSDL message has a part that refers to a type or element defined in an external schema file.

Workaround Add another element inside the schema section which has the type from the imported schema and use the element in the message.

1-8H9DK6 Summary Generate WSDL generates WSDL files with errors for WSDL file that import the SOAP envelope schema. The schema is converted to an inline schema and causes a conflict with the binding SOAP schema.

Workaround None.



Known Issues | 63

1-8HEXXD Summary The WSDL validator reports errors for a SOAP/JMS binding because the binding is not defined in the WST WSDL validator. The binding type is defined by the TIBCO SOAP/JMS specification and is correct.

Workaround Ignore the errors.

1-8DLUX3 Summary Sometimes a JMS shared resource has two scrollbars when displaying the endpoint node configuration in the Binding tab.

Workaround Scroll both scrollbars to see the full configuration.

1-8J544V Summary ActiveMatrix components do not support faults with complex types but at design-time SOAP service and references do not validate the WSDL and display an error message that indicates the problem with the WSDL file.

Workaround Only use faults with simple types.

1-9MDZVG Summary If you delete the connection factory for a JMS shared resource with Direct connection type, Business Studio incorrectly allows you to save the resource.

Workaround On closing and reopening the resource the default value is correctly displayed.

1-95S3EL Summary If you change the value of substitution variables that are bound to HTTP server shared resource properties, and then reinstall the HTTP shared resource, the new property values are not used.

Workaround Create and install a new HTTP shared resource that references the updated substitution variables.

1-8KLA5W Summary For both simple types and complex types, the XMLBeans marshaller should not add an extra wrapper element if the xmloject already has a wrapper element.

Workaround Create the parameters using the factory method rather than reusing the input parameter received. For example://create a new outparatmeter.XmlBase64Binary outparameter = XmlBase64Binary.Factory.newInstace();//set the value of the paramter.outparameter.setBinaryValue().//return the outparameterreturn outparameter;]



64 | Release Notes

1-9NFKSL Summary If 6.0 version of any one of the following ActiveMatrix Adapter Service Engines- SAP, ADB, Files or MQ - is installed, then Adapter WSDL generation functionality for the older versions of the remaining does not work.

Workaround Install the latest 6.0 version of TIBCO ActiveMatrix Adapters for which WSDL generation is desired.

Runtime

AMRP-3898 Summary Enabling secure connections between nodes and ActiveMatrix Administrator servers fails with following error : javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure .

Workaround Add the following property in the node’s TRA file:

java.property.com.tibco.security.EntrustLast=true

Restart the node.

1-97BJ0T Summary If you change the log service configuration, common logging is unable to send a notification to the node side.

Workaround Re-start the node to get log service information.

1-9HQDLV Summary After upgrading Business Works 5.6.4 to 5.7.0, deploying a service assembly on a 5.6.4 node fails with the error "Agent could not start an OSGi bundle for the release unit member at file location".

Workaround None.

1-9NPLSP Summary An ActiveMatrix Administrator node created with Oracle/SQLServer database fails to sava query as default one in log viewer. The error will occur on the Administrator console.

Workaround None.

1-9RA7QT Summary In Log Service, if an EMS server has a different name in the Shared Resource, the same queue can be used for different log services. This means that log messages will accumulate in the EMS queue when these log services are running, eventually shutting down the EMS server.

Workaround Do not name an EMS server something different in the Shared Resource.



Known Issues | 65

1-9TT6YS Summary In the Log Viewer, the log content displayed in the result list cannot be copied with the Internet Explorer browser.

Note: The log content in Log Detail works fine with Internet Explorer.

Workaround None

1-9TAZ7B Summary In the Log Viewer, the text boxes in Log Detail should not be available to edit.

Workaround None

1-9N9N9N Summary When you stop a service assembly containing a JMS binding configured with a durable subscription that uses the SonicMQ JMS server the service assembly throws java.lang.InterruptedException and TimeOut exception.

Workaround None.

1-9O877V Summary When using a JNDI or SSL shared resource for the log service, ssl_trusted_certs are configured. When the certificates location path is "\t, \n" such as "c:\tibco\folder\..", ssl_trusted_certs can not be found and no log entries can be sent to Enterprise Message Service queue.

Workaround Replace "\" with "/".

1-9OAQFT Summary JMS/SSL: When an Enterprise Message Service user has the same password as the Client Certificate password, the Enterprise Message Service user’s password is used.

If the Client Password field is blank, the "Test Connection" passes for the Messaging Bus. It should throw error instead.

Workaround Make sure the Enterprise Message Service user password and the Client Certificate password are different.



66 | Release Notes

1-9M5FJ9 Summary At startup, nodes based on the Oracle JDBC thin driver throw an exception similar to the following in the log:

Feb 14, 2009 10:22:02 AM oracle.jdbc.driver.OracleDriver registerMBeansSEVERE: Error while registering Oracle JDBC Diagnosability MBean.javax.management.MalformedObjectNameException: Invalid character '' in value part of property...

Workaround Update your Oracle driver. See: http://forums.oracle.com/forums/message.jspa?messageID=2152565#2152565

1-775NFT Summary The SOAP binding engine will not accept requests for endpoints named with a host property set to a DNS name and localhost.

Workaround To create an endpoint that accepts requests for a DNS name or IP address, create an HTTP resource with the host property set to an IP address or DNS name.

To create an endpoint that accepts requests for "localhost" or "127.0.0.1" create an HTTP resource with the host property set to "127.0.0.x" or "localhost".

To create an endpoint that accepts requests for all addresses, create an HTTP resource with the host property set "0.0.0.0".

1-7TIG1O Summary A WSDL message part that refers to a complex-type having attributes is not yet supported for document style operations.

Workaround Define the type with an element and refer to the element in the WSDL part.



Known Issues | 67

1-7TLMA7 Summary Fault messages with a part referring to an xsd type is not supported. For example:

<wsdl:message name="FaultMessage"> <wsdl:part name="faultMessagePart" type="xsd:string" /> </wsdl:message><wsdl:operation name="OperationThatCanThrowFault"> <wsdl:input message="tns:InputMessage"/> <wsdl:output message="tns:OutputMessage"/> <wsdl:fault message="tns:FaultMessage" name="myFaultMessage" /></wsdl:operation>

Workaround Define the type with an element and refer to the element in the "FaultMessage" For example:

<xsd:element name="mystring" type="xsd:string"></xsd:element><wsdl:message name="FaultMessage"> <wsdl:part name="faultMessagePart" element="tns:mystring" /> </wsdl:message><wsdl:operation name="OperationThatCanThrowFault"> <wsdl:input message="tns:InputMessage"/> <wsdl:output message="tns:OutputMessage"/> <wsdl:fault message="tns:FaultMessage" name="myFaultMessage" /></wsdl:operation>

1-7YAF2N Summary A SOAP over JMS provider binding does not receive a request message when the SOAP Action is not within double quotes. For example: 'soapaction' or soapaction.

Workaround When your client sends the SOAP request, the SOAP Action should be in double quotes. For example: "soapaction".

1-96N2O1 Summary When you start a node the following error is thrown in the node console:

2008 Aug 06 11:40:57:492 ERROR: Could not load module policies. Using default values.

Workaround Ignore the error.

1-8GISG6 Summary Creation of shared resources fails if the IP address of the machine changes after the node is created.

Workaround Restart the node.



68 | Release Notes

1-8HY7AS Summary An invalid keystore error is returned when starting a service assembly whose keystore is referenced with a relative path.

Workaround Specify an absolute path to the keystore.

1-8YSNHB Summary WS-Addressing: When you send an anonymous message to a SOAP service (which has Anonymous off and Addressing on), a response is not returned to the replyTo address or to the client.

Workaround Check the Anonymous flag for SOAP Service or Reference.

1-9CE2MR Summary The client gets "output data invalid" error when invoking a SOAP/JMS service that uses a WSDL containing an element that has an attribute.

Workaround None.

1-95IRBM Summary WS-Transfer-Attempting to delete a row for a key that is not present, does not cause an error to be thrown.

Workaround None.

1-95JHSX Summary WS-Enumeration-Renewal of released enumerations does not have correct behavior. It does not currently update the database nor is the renew operation prohibited.

Workaround None.

1-95LYLX Summary WS-Transfer-Attempting a Put operation for a resource that does not exist does not return a fault. Instead the Put reply for a successful Put operation is received.

Workaround None.

1-96H1F0 Summary If you set the hostname of the HTTP shared resource used by the SOAP reference enabled for WS-Reliable Messaging to localhost, reliable messaging does not work.

Workaround Set the hostname to 0.0.0.0.

1-96ZB2N Summary WS-Transfer-The only table column types currently supported are char, varchar, bigint, long, and integer.

Workaround None.



Known Issues | 69

1-97PZU4 Summary WS-Addressing: Soap-Java-Soap scenario doesn't work if WS-Addressing flag is enabled at both Soap Service and Soap Reference. WS-Addressing works between Soap-Java and Java-Soap individually.

Workaround None

1-8KM7TJ Summary AEScalar 'any' not supported by the Adapter container.

Workaround None.

1-8KPMT7 Summary When consuming services implemented by a Java component and the WSDL part refers to a simple or complex type, generic data such as XMLstring or XML int sent by a SOAP reference is not understood by BusinessWorks clients.

Workaround Always send the XML message as a document fragment for complex and simple types. This can be achieved by always using Factory.newInstance() for creating the XML objects.

1-8K3SKT Summary An Exception in MessageListener error is reported when a client sends a message to a service and there was a previously deployed service with the same queue name and different SOAP action.

Workaround Restart the node.

1-8J5MOS Summary When a node starts with default connector failure (for example connector initialization fails due to port bind problem), the SOAP container status shows as Error.

Workaround Ensure that the default connector configuration for all nodes running on a machine have unique port numbers.

1-8HRSQJ Summary A null value returned from a service is not automatically wrapped in an ActiveMatrix specific exception.

Workaround None.

1-8GLVTV Summary If you bind a machine to two Administrator servers and both servers have the same cluster name, the Management Daemon may run out of memory over a period of time.

Workaround Unbind from one of the servers or change the name of one of the clusters.



70 | Release Notes

1-8GSMXL Summary If the session count per service is exhausted, message exchanges to the service will not complete and the client that has initiated the message exchange will stop getting responses.

Workaround Increase the session count property in the node's tra file.

1-8F7N35 Summary A SocketException is observed when you stop a node after having deployed and run a service with a SOAP/HTTPS binding.

Workaround None.

1-8GBFQF Summary The JMS container does not validate messages. Thus if a message is sent to a JMS queue, the message is passed thorough the JMS binding even if a JMS application sends a message that does not match the message expected by a service.

Workaround None.

1-96252X Summary The node downgrader does not work correctly. For example, downgrading from 2.1 to 2.0 should activate the containers for 2.0 instead 2.1, but the instead latest version of containers are used.

Workaround None:

1-8L2UGL Summary Management Daemon takes 2 minutes to shut down on UNIX platforms.

Workaround None. It takes a long time but does shut down accurately.

1-9L19MC Summary When you use SonicMQ for In-Out and Out-In MEPs sometimes a response is generated multiple times from JMS references and services.

Workaround None.

1-9N9NA6 Summary When you start a service assembly containing an Out-only JMS binding configured with a durable subscription that uses the SonicMQ JMS server the service assembly intermittently does not start and throws progress.message.client.EUserAlreadyConnected error.

Workaround None.

1-9N60DF Summary When you test a JMS-JNDI connection to a SonicMQ server, the test passes even for an unauthorized user.

Workaround None.



Known Issues | 71

1-97H4L5 Summary When you activate older versions of containers they do not use the older version of the underlying infrastructure.

Workaround None.

1-A8WUER Summary When using WebSphere MQ, on undeploying a service assembly, the message Exception in JMS Resource Adapter. Exception message is [JMSCC0020: This session is closed..? displays.

Workaround None.

1-A8WUFN Summary On WebSphere MQ and WebLogic when service assemblies with different message formats (XML, Text, Bytes) are run consecutively a node goes in a loop throwing "unsupported message type" error.

Workaround Purge the message queue and restart the node.

1-AAJ7TN Summary If there are messages in queue which could not be successfully processed because of exception thrown in a Java component, the node keeps re-delivering these messages till such messages in the queue are purged.

Workaround Before starting the service assembly, purge all the pending messages to be delivered in the queue. You can filter the redelivered messages by adding a property "java.property.jmsbinding.filterredelivered=true" in the TRA file of the node.

1-AAJ7VR Summary A node fails to reconnect to a WebLogic JMS server if the server is restarted. The node goes into loop throwing "IlegalStateException: [JMSClientExceptions:055088]The consumer is closed".

Workaround Redeploy the service assembly with the JMS service or reference.

1-AAJ7WZ Summary A node fails to reconnect to a WebSphere JMS server if the server is restarted. The node goes into loop throwing "IlegalStateException: [JMSClientExceptions:055088]The consumer is closed".

Workaround Redeploy the service assembly with the JMS service or reference.

1-AAXX2X Summary JMS shared resources (JMS-JNDI connection) that interoperate with WebLogic and WebSphere JMS servers (File and LDAP based) do not authenticate a user. Test Connection passes for JMS even for an unauthorized user.

Workaround None.



72 | Release Notes

Mediation Container


1-A71O9Z Summary The AutoMediate Command Line tool doesn’t generate a project when running via telnet.

Workaround The X-Windows client application is required for the AutoMediate Command Line to run on a telnet session. You can use a tool such as XWin32 or Exceed to access a remote server via telnet.

1-A6I9Y5 Summary The AutoMediate Command Line tool does not work if the default workspace is compromised—for example, if you tried to close Business Studio while the AutoMediate Command Line tool was still running.

Workaround Delete the default Business Studio workspace and run the AutoMediate Command Line tool again.

1-A46CDD Summary The AutoMediate Command Line tool does not guarantee the validity of concrete WSDL provided as an input. It is possible that an invalid concrete WSDL could be generated into a composite application, resulting in an error marker on the composite.

Workaround Re-configure composite component that shows error markers, and re-generate the service assembly.

1-A7RMCO Summary If the project is created from multiple WSDL files that use the same port name, there is a conflict with shared resource files.

Workaround Do not use same port name in WSDLs if you plan to use multiple WSDLs with the -projectName option.

1-96MUNN Summary If you add a logging policy on the mediation component and a logging and security policy on the SOAP reference, authentication fails on the SOAP reference. A fault is generated and the SOAP service throws a null pointer exception when responding to a request.

Workaround Put an authentication policy on the mediation component.

1-9NTN7N Summary If two mediation flows in different projects use the same WSDL, the message InvalidType appears in MessageData in an Invoke property view.

Workaround Close projects that use duplicate WSDLs and XSDs.


Known Issues | 73

1-9NVKAX Summary If Catch Fault and Send Fault use the same schema, an error marker appears on the Send Fault task that sends an Invoke task.

Workaround Use a Transform task to avoid the validation error.

1-93P4P3 Summary A service assembly cannot be uploaded if the shared resource property target of the component is empty.

Workaround Fix the component in the composite and set the shared resource property to the correct value.

1-8JE3WH Summary The Service Import wizard cannot import imported XSD schemas when the WSDL file is imported from a URL.

Workaround Locate all references to WSDL and XSD files, manually import them in the project, then fix all the <import> statements to point to the new resources.

1-8FIEGP Summary It is possible to set the default name of the mediation flow with invalid characters in ActiveMatrix Service Bus preferences, thus creating incorrect mediation flow files.

Workaround Use valid numeric characters only.

1-8J1K7J

1-8J1KNI

Summary Faults declared with a Type attribute are not supported.

Workaround None at this time.

1-8J8TIB Summary When a custom mediation task is deployed and imported into a workspace in the same environment as the ActiveMatrix SOA project where the task is used, the output schema may display boxes instead of names of elements. This can be caused by namespace collisions.

Workaround Do not create workspaces that are used to:

(a) Register the pre-compiled custom mediation tasks plug-ins as an extension location.

(b) Import the sample custom mediation task source project.

(c) Import or create a project intended to create mediation flow scenarios.

You should create workspaces that either perform (a) and (b) (for users who develop custom mediation tasks) or perform (b) and (c) (for users that use custom mediation tasks within mediation flows). Also, check the namespaces of any imported schemas in your output schema for namespace collisions.



74 | Release Notes

1-8KL43R Summary The security components of the MessageContext element of the mediation exchange are not updated on output and fault paths.

Workaround These components will be updated in a future release of the product. For the current release, they appear in tasks on the output and fault paths, but they are empty.

1-8L4RAG 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 to handle all validation problems with the WSDL file before using the file in a mediation flow.

1-8RWJBJ Summary The minus sign in an XPath expression must be surrounded by spaces (for example, xsd:int(y - x) instead of xsd:int(y-x)) because it can be a valid part of an identifier (for example, purchasing-totals-by-day).

Workaround Surround any minus signs in XPath expressions with spaces so that the statement does not confuse the expression with an identifier. In this release, the error message returned might be confusing because it indicates that an invalid identifier has been encountered.

1-92J56Z Summary At run-time, mapping "Date" to "DateTime" fails when attempting to convert an object in the transform task (error "org.gxml.api.lang.err.FORG0001").

Workaround Manually resolve this by adding "xsd:dateTime(xsd:date(actual_mapping))" in the mapper.

1-964WI8 Summary ActiveMatrix Service Bus uses String as the datatype for all unknown types

Workaround Cast the string value to the appropriate XML type when the value is mapped to a new schema. NOTE: Binary types or other structured data types are not supported; an alternate workaround is to set the column type to a suitable SQL type that is supported, and the cast might not be required. In all cases the actual value from the database will be preserved.

1-9BW0MR Summary The client gets an "output data invalid" error when using a JMS/SOAP WSDL whose element has an attribute, and the attribute does not appear on the node.

Workaround: None at this time.



Known Issues | 75

1-9EC2E5 Summary Custom metrics do not seem to work when we have a pass-through mediation in the composite.

Workaround Put a task on the mediation flow. This can be a log task with nothing selected, or any other task.

1-9HAEXX Summary Unable to inspect all types of SOAP request headers in the mediation flow.

Workaround Only the declared headers that are bound to an abstract WSDL operation signature are supported in the mediation flow.

1-9IVLYX Summary When a transform task is used on the mediation flow, it throws an SWT error. Business Studio SWT 3.2.2 on 64 bit Red Hat 5.x Linux OS is only compatible with Mozilla 1.7.12 shared libraries. Default installation of Red Hat 5.x 64-bit Linux uses higher versions of the Mozilla/Firefox browser, making it incompatible with SWT 3.2.2.

Workaround To have design time for AMSB work on 64-bit RedHat Enterprise 5.x, perform these steps:

4. Install or copy 64 bit Mozilla 1.7.12 to /usr/lib64

5. Set environment variables:

a. export MOZILLA_FIVE_HOME=/usr/lib64/mozilla1.7.12

b. export LD_LIBRARY_PATH=/usr/lib64/mozilla1.7.12

1-9J2F4H Summary In the Mediation Flow Editor, an error results if an in-only WSDL and an in-out WSDL using the same namespace are used on both sides of the mediation flow.

Workaround None—this is not supported. Multiple WSDLs cannot have the same target namespace but have different structures. The two WSDLs must use different namespaces.



76 | Release Notes

1-9MFZ4Z Summary If the value of the XPath Route task’s boolean rule variable is null, the error org.xml.api.lang.err.FORG0001 results.

Workaround Supply a value for the boolean rule variable. For example:

1-9N981V Summary A service assembly that was implemented by a WSDL that imported another WSDL cannot be deployed, and a java.lang.NullpointerException is thrown.


1-9NDPW9 Summary In the Transform XML task, some XSLT files and the corresponding input XML files of a BusinessWorks XSLT project produce an error (org.gxml.api.lang.err.FOER0000: err:FOER0000).

Workaround None at this time—the XML document created by BusinessWorks is invalid.

1-9NHTAD Summary When using external XSLT in the transform task, the mediation flow will encounter deployment/runtime errors if the XSLT uses a wildcard to map any type in an XPath expression, or if the output of the stylesheet does not contain a root element.

Workaround To work around this issue:

• When mapping any element use XSD constructors to type cast instead of wildcard.

• The output of the stylesheet must have a root element.

1-9NP7EY Summary Difficulty mapping error messages on the Catch All mediation path. This happens with undeclared faults, declared faults, the MediationTaskFault, and the MediationTaskRuntime fault when these faults are under Catch All.




Known Issues | 77

1-9NZWIT Summary When the Transform task uses an External Style Sheet, deployment fails if an XSL file contains a byte-order mark (BOM) for UTF-8.

Workaround Remove the BOM and declare the encoding in the XML file.

1-9NZWKT Summary When the Transform task uses an External Style Sheet, multibyte characters in XML files are garbled in the transformed output.

Workaround Use dynamic mode.



78 | Release Notes

Migration Tools Reference

Table 3 Migration Tools Reference

Tool Description

flattener Updates TRA files with newly installed plug-ins. It checks for any new (plug-in) installations, versions, and their dependencies and updates the TRA file. This is normally run against the template TRA files (for example, createadminserver.tra) and against the ActiveMatrix Administrator server TRA file after hotfix installations.

flattener is run on all the template TRA files by the installers.

The TRA files of the exisitng ActiveMatrix Administrator server and existing run time nodes are flattened by the corresponding upgrade scripts. flattener starts from the root level plug-ins specified in the property tibco.flattener.roots and walks through the complete dependency graph, constructs the class path, and updates the TRA file.

tibcommander A tool to execute Ant scripts. In general the tools packaged in ActiveMatrix Service Bus are instances of a wrapper launched with a TRA file or an Ant script launched by tibcommander. For example, nodeupgrader.xml.

SyncInstallation Used to update the machine.xmi file with the latest version of the (plug-ins and features) installed by the installers or custom features installed by user.

This utility is run by the installers at the end of installation to keep the machine.xmi synchronized with the installed release units. Run this utility run when a custom feature such as a database driver is added to the environment so that runtime nodes and ActiveMatrix Administrator servers pick up this newly added plug-in.

PlatformXMLUpgrader Used to update TIBCO Business Studio. It checks if there are any new features added in the installation setup, under TIBCO_HOME\components\[plug-ins | features] folder and updates platform.xml in the Business Studio home directory. This file is used by Business Studio during the startup to load the plug-ins in design time.

TIBCO_HOME\Business Studio\configuration\org.eclipse.update


Migration Tools Reference | 79


80 | Release Notes

Configuring ActiveMatrix Service Bus to Interoperate with BEA

WebLogic and IBM WebSphere JMS Servers

This section describes how to configure ActiveMatrix Service Bus to interoperate with BEA WebLogic and IBM WebSphere JMS Servers when using JMS and SOAP over JMS bindings.

Using SOAP/JMS and JMS Bindings with WebLogic JMS

Creating wlfullclient.jar

1. From the WebLogic installation, go to the directory WL_HOME/server/lib (for example, C:\bea\weblogic_10.3\wlserver_10.3\server\lib)

2. Create wlfullclient.jar using the command: java -jar wljarbuilder.jar. wlfullclient.jar will be created in the WL_HOME/server/lib directory.

Packaging and Installing wlfullclient.jar

Follow the steps in Packaging and Installing Native Database Drivers in TIBCO ActiveMatrix Service Bus Installation and package wlfullclient.jar as a feature.

1. In step 4.a., replace com.tibco.tpcl.jdbc.drivers with com.tibco.neo.resource.adapter.jms.

2. In step 5, import wlfullclient.jar.

Follow the steps under Configuring Existing ActiveMatrix Administrator Servers and ActiveMatrix Nodes for installing wlfullclient.jar into existing Administrator servers and nodes.

Creating the JMSUserExit Plug-in for SOAP/JMS Interoperability with WebLogic

Follow the steps in Appendix A – SOAP/JMS Interoperability in TIBCO ActiveMatrix Composite Editor User’s Guide.


Configuring ActiveMatrix Service Bus to Interoperate with BEA WebLogic and IBM WebSphere JMS Servers | 81

Configuring WebLogic JMS Variables in JMS and JNDI Shared Resources

JNDI Shared Resource Configuration

JNDI Context Factory = weblogic.jndi.WLInitialContextFactory

JNDI Context URL = t3://weblogichost:7001 (that is, t3://WEBLOGIC_HOST:WEBLOGIC_PORT)

JNDI Username = weblogic

JNDI Password = weblogic

By default the JNDI username and password are weblogic.

JMS Shared Resource Configuration

JMS Username =

JMS Password =

By default the JMS username and password are empty.

Connection Factory = weblogic.examples.jms.QueueConnectionFactory

An existing QueueConnectionFactory, obtained from the WebLogic UI: wl_server->Services->Messaging->JMS Modules->examples-jms. You can follow this and create a different QueueConnectionFactory and use it.

Creating a Client for the WebLogic Service

Get the WSDL file from the WebLogic service and use it as it is to creating a SOAP/JMS reference. ActiveMatrix will detect that the WSDL is a third-party WSDL.

Destination Queue Name in References

The destination queue name in a reference (that is, the one pointing to the WebLogic queue) should be the local WebLogic JMS queue name and should use the following format:

JMS_SERVER_NAME/JMS_MODULE_NAME!DESTINATION_NAME

For example:

examplesJMSServer/examples-jms!helloWorldFaultQueue

JNDI lookup is supported only for connection factories and not for the destinations.


82 | Release Notes

The destination queue name should include server name followed by a /, module name, exclamation symbol and then the destination queue name. The queue should have a ‘sub deployment’ chosen during the creation of the queue and a JNDI name.

Using SOAP/JMS and JMS Bindings with IBM WebSphere JMS

Packaging and Installing WebSphere Client JARs

Follow the steps in Packaging and Installing Native Database Drivers in TIBCO ActiveMatrix Service Bus Installation.

1. In step 4.a., replace com.tibco.tpcl.jdbc.drivers with com.tibco.neo.resource.adapter.jms.

2. In step 5, import following WebSphere client JARs:

— com.ibm.mq.jar

— com.ibm.mq.jmqi.jar

— com.ibm.mq.soap.jar

— com.ibm.mqjms.jar

— connector.jar

— dhbcore.jar

— fscontext.jar

— jta.jar

— ldap.jar

— providerutil.jar

3. In step 6a, after exporting packages, import the following package with a version range 1.0.1 and 2.0.0:

— javax.transaction

Follow the steps in Configuring Existing ActiveMatrix Administrator Servers and ActiveMatrix Nodes for installing the WebSphere client JAR into existing Administrator servers and nodes.

ActiveMatrix inbound requests on WebLogic topics are not yet supported. Use a WebLogic topic to queue messaging bridge to accomplish this. Refer to the WebLogic help for creating messaging bridge, section ->Creating messaging bridge instances.


Configuring ActiveMatrix Service Bus to Interoperate with BEA WebLogic and IBM WebSphere JMS Servers | 83

Creating the JMSUserExit Plug-in for SOAP/JMS Interoperability with IBM WebSphere JMS

Follow the steps in Appendix A – SOAP/JMS Interoperability in in TIBCO ActiveMatrix Composite Editor User’s Guide. A sample extension for WebSphere is available in ACTIVEMATRIX_ADMIN_HOME/2.3/samples/amx/SOAP-Interop.

To interoperate with WebSphere, modify the implementation of SoapJmsExtension.onRequest() method as follows:

public void onRequest (Port port, String operationName, Map<String,String> messageProperties) {messageProperties.put("targetService", "name of the service");}

Configuring WebSphere MQ JMS Variables in JMS and JNDI Shared Resources

JNDI Shared Resource Configuration

JMS Shared Resource Configuration:

JNDI lookup is supported only for connection factories and not for the destinations.

Lookup Type Properties

File-based JNDI Context Factory= com.sun.jndi.fscontext.RefFSContextFactory

JNDI Context URL = file:/C:/IBM_Bindings (path for the Bindings Directory)

LDAP-based JNDI Context Factory= com.sun.jndi.fscontext.RefFSContextFactory

JNDI Context URL = ldap://host:port/distinguished name

JNDI Username and Password: as per your installation.

Lookup Type Properties

File-based ConnectionFactory: QueueConnectionFactory (/ as per your installation)

LDAP-based ConnectionFactory: cn=QueueConnectionFactory (/ as per your

installation)

JMS Username and Password: as per your installation.


84 | Release Notes


| 85


86 | Release Notes

Service Assembly File Format

The service assembly archive ZIP file has the following format:

\\META-INF\META-INF\MANIFEST.MF\someJar1.jar\someJar2.jar...\someJarN.jar

There is one JAR generated for each service unit, one JAR for each Java bundle packaged in the file, and one JAR for the packaged composite. The JAR corresponding to the packaged composite is identified in the MANIFEST.MF file.

The MANIFEST.MF file has an entry like: ServiceAssembly-Bundle: someJar2.jar

The JAR corrsponding to the composite has the following structure:

\\META-INF\\META-INF\MANIFEST.MF\gvars.substvar\serviceassembly.saf\YourSoaProjectName\\YourSoaProjectName\<packaged resources for your SOA project>typically:\YourSoaProjectName\Composites\\YourSoaProjectName\Composites\YourCompositeName.composite\YourSoaProjectName\Service Descriptors\YourWsdls.wsdl\YourSoaProjectName\Shared Resources\yourSharedResource1.sharedXXXX\YourSoaProjectName\Shared Resources\yourSharedResource2.sharedXXXX...

Inside the MANIFEST.MF file for the JAR corresponding to the component (For example, \someJar2.jar#\META-INF\MANIFEST.MF ), is an entry:

Bundle-Name: YourCompositeName

This indicates the composite that was packaged. There is no easy way to locate this composite other than to parse the serveiceassembly.saf file, although it will typically be in the Composites folder (For example, \someJar2.jar#YourSoaProjectName\Composites\YourCompositeName.composite ), but this cannot be assumed.

Extracting Svars

1. Use an XML parser (For example, stax, DOM, etc) to parse the gvars.substvar file in the JAR of a composite (for example,\someJar2.jar#\gvars.substvar).


http://www.omg.org/XMI

http://xsd.tns.tibco.com/corona/models/sharedresourcemodel





http://schemas.tibco.com/amx/2.0/composite

http://schemas.tibco.com/amx/2.0/composite

http://www.osoa.org/xmlns/sca/1.0



http://xsd.tns.tibco.com/corona/models/transport/httpmodel







http://xsd.tns.tibco.com/matrix/serviceassembly/serviceassemblymodel




http://xsd.tns.tibco.com/corona/models/jdbcmodel



Service Assembly File Format | 87

2. For each substitution variable there is one entry in the following XPath expression:

/repository/glabalVariables/globalVariable

Inside such an element are these sub-elements of interest (there are a few others)

<name></name>

<value></value>

<type><type>

<description></description>

The name will contain the full workspace-relative path of the svar where the last segment of it is the actual variable name. The previous segment is the name of the Svars file without the extension.

For example, <name>/YourSoaProjectName/Shared Resources/SubstitutionVariables/YourVariableName</name>

The type will contain one of the following: String, Boolean, Password, or Integer.

The value subelement contains the variable's value. For password types the value is encrypted and cannot be read without access to functionality in TIBCO's security libraries.

The description subelement contains the description value.

Extracting Service Unit Names and Types

1. Use an XML parser (For example, stax, DOM, etc) to parse the serviceassembly.saf file in the jar of the composite (For example,\someJar2.jar#\serviceassembly.saf). Make sure the parser does not attempt to download schemas for validation of the elements in the different namespaces listed.

2. The root XML element of this file will be ServiceAssembly in namespace xmlns:serviceassemblymodel="http://xsd.tns.tibco.com/matrix/serviceassembly/serviceassemblymodel"

For example,

<serviceassemblymodel:ServiceAssembly ...>

Inside this ServiceAssembly element there will be an element called "composite". For example,

<composite href="/YourSoaProjectName/Composites/AreaComposite.composite#/"/>

(you will need that for Extracting Shared Resource Profiles on page 88).


http://xsd.tns.tibco.com/corona/models/transport/jmsmodel




http://xsd.tns.tibco.com/corona/models/transport/rvmodel



mailto:/PingArea/Composites/AreaComposite.composite%23//@providerBindingDefinitions.0



mailto:/YourSoaProjectName/Composites/YourCompositeName.composite%23//@resourceProfiles.0

mailto:/PingArea/Composites/AreaComposite.composite%23//@resourceProfiles.0


mailto:/YourSoaProjectName/Composites/YourCompositeName.composite%23//@resourceProfiles.3





88 | Release Notes

Inside the ServiceAssembly element, for each service unit packaged there will be a subelement called serviceunits. For example,

<serviceunits xsi:type="serviceassemblymodel:BindingServiceUnit" componentName="com.tibco.matrix.container.soapbinding.runtime" minComponentVersion="2.0.0.0" maxComponentVersion="3.0.0.0"><identification name="SOAP" version="1.0.0"/><providerBindingDefinitions href="/PingArea/Composites/AreaComposite.composite#//@providerBindingDefinitions.0"/><resourceProfiles href="/PingArea/Composites/AreaComposite.composite#//@resourceProfiles.0"/></serviceunits>

When the service unit is for a binding type it will have this type attribute:

xsi:type="serviceassemblymodel:BindingServiceUnit"

When the service unit is for an implementation type it will have this type attribute:

xsi:type="serviceassemblymodel:EngineServiceUnit"

The specific binding or implementation type can be determined from the componentName attribute:

• SOAP: com.tibco.matrix.container.soapbinding.runtime

• JMS: com.tibco.matrix.container.jmsbinding.runtime

• Java: com.tibco.matrix.container.javase.runtime

• Adapter: com.tibco.matrix.container.adapterbinding.runtime

• Mediation: com.tibco.amsb.container.mediation.runtime

• DotNet: com.tibco.matrix.container.dotnetse.runtime

Also inside the serviceunits element, is a subelement called identification. The name of the service unit can be read from the name attribute on this subelement. For example,

<serviceunits xsi:type="serviceassemblymodel:EngineServiceUnit" componentName="com.tibco.matrix.container.javase.runtime" minComponentVersion="2.0.0.0" maxComponentVersion="3.0.0.0"><identification name="Java" version="1.0.0"/>....</serviceunits>

Extracting Shared Resource Profiles

1. Use an XML parser (For example, stax, DOM, etc) to parse the serviceassembly.saf file in the jar of the composite (For example,\someJar2.jar#\serviceassembly.saf ). Make sure the parser does not



attempt to download schemas for validation of the elements in the different namespaces listed.

2. The root XML element of this file will be ServiceAssembly from namespace xmlns:serviceassemblymodel="http://xsd.tns.tibco.com/matrix/serviceassembly/serviceassemblymodel".

For example,

<serviceassemblymodel:ServiceAssembly ...>

Inside this element there will be an element called composite. For example,

<composite href="/YourSoaProjectName/Composites/AreaComposite.composite#/"/>

This is the composite that is packaged in this SAF file.

Use an XML parser (again, non-validating), to parse that composite file from the composite JAR. For example,

\someJar2.jar#YourSoaProjectName\Composites\YourCompositeName.composite

Parsing the composite file provides all the shared resource profiles declared within. However, some may not be referenced. To isolate only the shared resource profiles that are referenced by the application, read the "resourceProfiles" sub-element of the "serviceunits" element in the serviceassembly.saf file. This is an optional element so it will not always be present. For example,

<serviceunits ...>...<resourceProfiles href="/YourSoaProjectName/Composites/YourCompositeName.composite#//@resourceProfiles.0"/>href="/YourSoaProjectName/Composites/YourCompositeName.composite#//@resourceProfiles.3"/>....</serviceunits>

Each resourceProfiles element refers to a shared resource profile that exists in the composite referenced. There is an index at the end of the href values. For example, href="....//@resourceProfiles.3. The 3 in the above example indicates that it refers to the 4th shared resource profile declared in the composite (since indices start at zero).

Parsing the composite file reveals zero or more sharedResourceProfile elements. These are under the amx namespace while the composite is under the sca namespace: xmlns:amx="http://schemas.tibco.com/amx/2.0/composite" xmlns:sca="http://www.osoa.org/xmlns/sca/1.0". For example,

<sca:composite ...>....<amx:sharedResourceProfile>


90 | Release Notes

<httpmodel:HTTPConnectionConfigurationProfile name="httpServer" xmi:version="2.0" xmlns:httpmodel="http://xsd.tns.tibco.com/corona/models/transport/httpmodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile>...</sca:composite>

The types of the shared resources depend on the sub-element that is nested under the sharedResourceProfile element. There is just such subelement. These come from different namespaces. Regardless of the type they all have a name attribute. Here is the list of the types you may find:

<amx:sharedResourceProfile><httpmodel:HTTPConnectionConfigurationProfile name="httpsrp" xmi:version="2.0" xmlns:httpmodel="http://xsd.tns.tibco.com/corona/models/transport/httpmodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile><amx:sharedResourceProfile><jdbcmodel:JDBCConnectionProfile name="jdbcsrp" xmi:version="2.0"xmlns:jdbcmodel="http://xsd.tns.tibco.com/corona/models/jdbcmodel" xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile><amx:sharedResourceProfile><jmsmodel:JMSConnectionConfigurationProfile name="jmssrp" xmi:version="2.0" xmlns:jmsmodel="http://xsd.tns.tibco.com/corona/models/transport/jmsmodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile><amx:sharedResourceProfile><rvmodel:RVConfigurationSharedResourceProfile name="rvsrp" xmi:version="2.0" xmlns:rvmodel="http://xsd.tns.tibco.com/corona/models/transport/rvmodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile><amx:sharedResourceProfile><httpmodel:HTTPConnectionConfigurationProfile isHttps="true" name="httpssrp" xmi:version="2.0" xmlns:httpmodel="http://xsd.tns.tibco.com/corona/models/transport/httpmodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceProfile><amx:sharedResourceValue><sharedresourcemodel:SharedResourceBinding profileName="jdbcsrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/> </amx:sharedResourceValue><amx:sharedResourceValue>



<sharedresourcemodel:SharedResourceBinding profileName="httpsrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceValue><amx:sharedResourceValue><sharedresourcemodel:SharedResourceBinding profileName="jmssrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceValue><amx:sharedResourceValue><sharedresourcemodel:SharedResourceBinding profileName="rvsrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceValue><amx:sharedResourceValue><sharedresourcemodel:SharedResourceBinding profileName="httpssrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/></amx:sharedResourceValue>

The sharedResourceProfile elements are only the shared resource profiles as listed in the composite. Notice in the above XML fragment that there are also elements of type sharedResourceValue. These provide the actual value to the shared resource profile. The name attribute inside the sub-element of the sharedResourceProfile element matches the profileName attribute of the corresponding "sharedResourceValue". That is how they are related. It is always a 1-to-1 mapping.

In cases where the sharedResourceValue is set on the composite, when configured, it would be pointing to an actual shared resource file. For example,

<sca:composite ...>...<amx:sharedResourceValue><sharedresourcemodel:SharedResourceBinding profileName="httpsrp" xmi:version="2.0" xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel"xmlns:xmi="http://www.omg.org/XMI"/><sharedResourceConfiguration href="/YourSoaProjectName/Shared Resources/yourHttpSR.sharedhttp#/"/></amx:sharedResourceValue>

There can also be shared resource profiles in components. In such cases you will find a sharedResourceValue element inside the component element in the composite.


92 | Release Notes

For example,

<sca:composite ...><sca:component ...><amx:sharedResourceValue>...

In this case, the sharedResourceValue can be pointing to a shared resource file (as in the case for when sharedResourceValue is in the composite). Alternatively, when set in a component, a sharedResourceValue can be pointing to a shared resource profile defined in the composite. In such case, this reference is established with a sharedResourceBinding element inside the sharedResourceValue element. For example,

<sca:composite<sca:component ...>...<amx:sharedResourceValue><xmi:XMI xmi:version="2.0" xmlns:jdbcmodel="http://xsd.tns.tibco.com/corona/models/jdbcmodel"xmlns:sharedresourcemodel="http://xsd.tns.tibco.com/corona/models/sharedresourcemodel" xmlns:xmi="http://www.omg.org/XMI"><sharedresourcemodel:SharedResourceBinding profileName="SharedResourceProfile0" source="@SharedResourceProfile.jdbcsrp"/><jdbcmodel:JDBCConnectionProfile name="jdbcsrp" xmlns:xmi="xmi" xmi:id="@SharedResourceProfile.jdbcsrp"/></xmi:XMI></amx:sharedResourceValue>

where profileName specifies the name of the sharedResourceProfile in the composite.


| 93


94 | Release Notes
