tib bc release notes - TIBCO Software · 2012-07-03 · SOCKS4/SOCKS5 server and FTP proxy server. TIBCO BusinessConnect Release Notes New Features |7 † Extended proxy support for

TIBCO BusinessConnect™

Release NotesSoftware Release 5.3.3August 2010

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 LICENSE.PDF) 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 Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO BusinessConnect, TIBCO Runtime Agent, TIBCO BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO Rendezvous, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

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

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.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 © 1999-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

Contents | iii

Contents

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

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 5.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Compatibility and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Release 5.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Release 5.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

TIBCO BusinessConnect Release Notes

iv | Contents

Release 5.1.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


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

• Deprecated Features, page 25

• Compatibility and Migration, page 26

• Closed Issues, page 32

• Known Issues, page 62


2 | Release Notes

New Features

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

Release 5.3.3There are no new features in this release.



Release 5.3.0In this release, the following functionality has been introduced:

DMZ Servlet Support on Application Servers

• TIBCO BusinessConnect supports deploying of the DMZ Component as Servlet on the following supported application servers:

— JBoss Enterprise Edition 4.3.0

— IBM WebSphere 6.1 and up

— Oracle BEA WebLogic Server 10.2 and up

• For deployment of the DMZ Component as a .war, a new command -exportDmzAsServlet has been added as part of the Scripted Deployment tool. The exported deployment is a .war file that contains required information for the application server to send BusinessConnect HTTP (or HTTPS/HTTPSCA) messages to the BusinessConnect Interior Servers.

TIBCO BusinessConnect User Access Control and Log View/Report Filter

• TIBCO BusinessConnect User Access Management allows restricting of user access to certain participants, business agreements, log viewer, and reports.


New Features | 3

• Only those TIBCO Administrator users who have access to TIBCO BusinessConnect and its components can be part of TIBCO BusinessConnect User Access Control.

• Finer granular control access is available (such as Read Only, Read/Update or Read/Update/Delete) to certain participants, business agreements, as well as Full Access to ALL participants and business agreements.

• User level restriction is implemented to view runtime transactions based on permission set per participant.

TIBCO BusinessConnect User Access Audit Trail

• This feature audits changes made by users who have permissions to modify participants, business agreements, and operations:

— Audit Log changes made by users who have access to participants and business agreements to either Create, Update and Delete based on the User Access Control permissions.

— Audit Log changes made by users who have Write access to the Operations Editor with TIBCO Administrator.

New Database Support

• TIBCO BusinessConnect now supports the following database versions:

— DB2 UDB 9.5

— Microsoft SQL Server 2008

— Oracle 11g

— Oracle 11g RAC

Native JDBC Driver support

• TIBCO BusinessConnect now supports native JDBC drivers for the following Databases: Oracle, DB2, and Microsoft SQL Server.


4 | Release Notes

New Platform Support

• TIBCO BusinessConnect supports the following new platforms starting from this release:

— Microsoft Windows Server 2008

— Solaris 10 x86 and sparc

— Red Hat Enterprise Linux 5

— Red Hat Enterprise Linux 5.1

— SUSE Linux Enterprise 10 SP1

Support for JRE 1.6.0

• TIBCO BusinessConnect supports running the BusinessConnect runtime engines using JRE 1.6.0.

Support to Export CSV Data Reporting

• TIBCO BusinessConnect now supports exporting both Inbound and Outbound Transactions per Protocol to a CSV file.

Support to Retrieve Emails from Three Concurrent Email Servers

• TIBCO BusinessConnect supports retrieving and processing emails from three different POP3 email servers at the same time.

Support to Retrieve an SSH Public Key from the SSH FTP Server

• TIBCO BusinessConnect provides a UI configuration option to retrieve an SSH Public key from the SSH FTP Server and load it into TIBCO BusinessConnect configuration.

New Properties Added in this Release

• bc.ediint.digestAlgorithmEnabled This property determines whether the AS1 and AS2 transports will default to using the SHA1 message digest algorithm, or whether they will pick up the digest algorithm setting from the Business Agreements/Document Security/Outbound Document Exchange/ Signing Info Settings/Digest Algorithm.

By default, the property bc.ediint.digestAlgorithmEnabled is false and the AS1 and AS2 handlers will always use SHA1 for the message digest algorithm as recommended by their respective specifications


New Features | 5

• ezcomm.notify.email.preserveSubject This property was added for the TIBCO BusinessConnect EZComm Protocol to preserve the email subject.

When sending email messages for EMAIL and AS1 transports, TIBCO BusinessConnect EZComm Protocol will generate the email subject based on operation and transaction IDs. However, it is possible to preserve the subject specified by the user on EMAIL and AS1 transports by enabling the EZComm property ezcomm.notify.email.preserveSubject. By setting this property to true, users can send their own email subject to trading partners.

Release 5.2.1There were no new features added in this release.

Release 5.2.0

New Features for EZComm

In this release, the following functionality has been introduced for the TIBCO BusinessConnect EZComm Protocol:

• Synchronous and asynchronous Request Response operations

• A version subgroup in the operation definition: Category/Version/Operation. This subgroup provides for finer categorization of operation types and allows the users to maintain backward compatibility of tibXML integration with the BusinessConnect 3.x systems

• Support for multiple attachments for Email, AS1 and HTTP/S transports

• Support for duplication detection, both for inbound and outbound messages

• Support for the DTD schema validation

• Support for AS2 Filename Preservation specification

• Message validation that can be enabled and disabled separately for inbound and outbound messages

• File name preservation from public messages to the private process:

— For the inbound MIME-based EMAIL and for the HTTP transport, the content-disposition file name header is extracted and preserved in the private process messages.

— For the inbound FILE and FTP transports, the original file name of the payload is now available in the private process messages.

• tibXML Integration


6 | Release Notes

— EZComm is now interoperable with the tibXML public and private messages on the BusinessConnect 3.x systems.

— Option to enable tibXML packaging on the outbound public messages

— Option to publish private process message in the tibXML formats

— Seamless migration of the tibXML configurations from the BusinessConnect 3.x systems

— tibXML passthrough

• User transaction ID in the audit log for correlation with the private process messages

New Features for BusinessConnect

In this release, the following functionality has been introduced for TIBCO BusinessConnect:

Smart Routing

• Public Smart Routing that prioritizes and distributes inbound messages from trading partners over multiple clusters of load balanced runtime engines

• Activation and deactivation of smart routing rules both for the Private and Public Smart Routing, allowed by BusinessConnect

JMS communications with back-office applications

• Auto detection and recovery of lost connections with JMS server. This detection allows the messages to be re-delivered and consumed, without restarting the BusinessConnect runtime engines and the BusinessWorks runtime engines that host activities from the BusinessConnect Palette.

• Support for secure JMS connections over SSL

• Support for the fault tolerant JMS server group connections

Transport connectivity

• Secure FTP transport over SSH. This transport is used for document exchanges over the secured SSH tunnels that have been established between the BusinessConnect server and the trading partners SSH servers.

• Configurable control of the cipher encryption grade on the secure HTTP transport over SSL

• Extended proxy support for the outbound FTP transport over the SOCKS4/SOCKS5 server and FTP proxy server


New Features | 7

• Extended proxy support for the outbound HTTP transport over the SOCKS4/SOCKS5 server

Runtime engine optimization

• Asynchronous audit logging that separates the audit database access from the message processing. Such logging promotes concurrent processing by maximizing the overall throughput.

• Enhanced concurrent processing of the FTP Get poller, which maximizes throughput for a large number of trading partners.

• Enhanced EMAIL poller processing, with retry and recovery on timeout under high load conditions

Resending Transactions

• History of messages resent to private process that is now viewable from the Resent Log History

• Resend History Log now captures the user initiating the resend activity

• Messages resent to the private process are always re-evaluated for smart routing upon re-transmission. Such re-evaluation is performed to allow for message handling by different back-office applications.

• Resend triggered from the transaction state’s detail view in the Audit Log viewer

Log Viewer

• Global Preferences for configuring the default settings for all log viewers

• Ability to enable and disable available protocols as a search criteria

• Ability to set defaults for protocols, database connections, host name, and transaction status

• Navigation buttons to traverse transactions without escaping back to the transaction summary view

• Transaction details that can be toggled between the table view of states and the state detail view, with navigation buttons on the same page

• Added the operator 'is not equal' for all advanced search criteria

Installation Management

• Protocol deactivation without uninstalling of the protocol


8 | Release Notes

• Progress display for configuration export and import

• Option to preserve access privileges of existing administrator users on configuration data migration from the BusinessConnect 3.x systems

Miscellaneous

• System utility to export the private process schemas for all installed protocols

• Optimized access from the BusinessConnect administrator console in listing large number of trading partners and business agreements

• Option to enforce unlimited strength ciphers level on engine startup

• A database archive tool that now supports filter criteria by time stamp only, without inspecting the completion state as defined by individual protocols

• BusinessConnect Remote Client service that allows processing of a start up request from the BusinessConnect Remote client. Activation and installation of the Trading Community Management product is no longer a prerequisite.

• The default shared and temporary file locations are now residing under the working directory of the deployed runtime location in the folder TIBCO_home/tra/domain/applications/BusinessConnect/working . The following subfolders are created:

— For shared files: tibcobc_shared

— For temporary files: tibcobc_temp

• The default location for the RVCM ledger files is now residing under the working directory of the deployed runtime location in the folder TIBCO_home/tra/domain/applications/BusinessConnect/working/tibcobc_rvcm_ledgers.

• Support for HP-UX 11.31 Itanium has been added.

Release 5.1.3In this release, support was added for the following:

• HP Itanium (64-bit)

— HP-UX 11i v2/11.23

• Oracle 10g R2

• TIBCO BusinessConnect palette running under TIBCO ActiveMatrix BusinessWorks 64 bit on AIX


New Features | 9

Release 5.1.2In this release, support was added for the following:

• Microsoft SQL Server 2005

Release 5.1.1No new features are added in this release.

Release 5.1.0

New Platform Support

Platform that was added in this release:

• Solaris 10, 32 bit only

General Changes

• Support was added for Oracle Real Application Clusters (RAC)

• BusinessConnect Server properties that were added:

— bc.http.threadPool.maximum : Maximum number of threads used for HTTP requests

— bc.tx.resend.messagesPerPoll: Maximum number of messages that BusinessConnect will resend during one polling cycle.

• DMZ Interior Timeout (seconds): A new field for editing application configuration, which specifies the reply-confirmation from DMZ and is a part of message level handshaking to ensure that DMZ has successfully received a reply from the Interior server.

• Configuration fields for the outbound FTP/S transport that were added: Retry Count and Retry Interval (number of retries and time between retries).

• Private process screens have been revised to add TIBCO Rendezvous parameters and the ledger file location.

• Messaging communication between the BusinessConnect engine and private processes now supports JMS.

• BusinessConnect engines now support fail-over, which allows checkpoints to be fault tolerant.


10 | Release Notes

• Import and export of configuration data is redesigned to be metadata driven, which allows more robust migration of data between installations and upgrades.

• DMZ deployment now supports a complete packaged offline deployment.

• SSL session caching was added for outgoing HTTPS connections.

• EZComm now supports fileName override by an incoming message for the HTTP transport, where the target fileName is dictated by the message URL or header.

• EZComm now supports checking of digital signature and encryption for incoming transactions over HTTP.

• EZComm now supports non repudiation for inbound transactions over HTTP.

• A new column was added to display the domain identities belonging to a participant.

• A new property was added to allow a participant to completely disable the use of outbound proxies.

• SMTP server connection now supports that users configure user names and passwords.

• Multiple users can concurrently edit different operations for a protocol without encountering lock conflicts.

• Deployment screens are revised for inter component configurations, allowing a full set of TIBCO Rendezvous parameters to be viewed and edited.

• The inbound File poller now supports fault-tolerant configuration.

• FCP (File Copying) between a DMZ server and a BusinessConnect server now supports IP specific port assignment (host:port).

• BusinessConnect Palette now supports JMS connection.

• BusinessConnect Palette now supports wild card event subscription to de-multiplex all incoming messages to a single BusinessWorks engine.

• Support was added for user to select the style of storage for log messages: compressed or uncompressed.

• A new JDBC connection bc-checkpoint-db was added to support check points fail over.

• Support was added to cancel a pending transaction if a protocol supports canceling of transactions.


New Features | 11

Clearing the Checkbox “Parse XML Payload”

When designing private processes, you can now create the event sources Responder Request and Initiator Response by clearing the checkbox Parse XML Payload for the following resources in the BusinessConnect Palette:• Receive Request/Notification

• Receive Response

These event sources can receive messages with any operation name assuming that they belong to the same business protocol. This is possible because, in case of parsing or parse/validation, different operations with different payloads would require different schemas to be configured at the same time.

If parse/validation is required for messages that are received on these wild card listeners, a parse validate task can be used. No such support exists for event sources receiving miscellaneous messages, as these messages may have different AE schemas or message header structures, which couldn't be validated on the same event source.

Once the checkbox Parse XML Payload is cleared, the event sources will list an “*” entry in their dropdown list. You can select this wild card entry in order to start receiving multiple operations on the given event source instance.

Allow override of filename via HTTP parameter

On the Initiator side, there is a new checkbox for the partner. If this checkbox is selected and a file reference is being passed to the Responder, then the name of the file is passed on to the Responder in an HTTP header.

On the Responder side, each partner has a check box named Allow override of filename via HTTP parameter . If this checkbox is selected and there is a fileName field in the HTTP message header or a QueryString (in that order), the message will be written to a file with fileName, which will be created in a shared directory under the partner name directory.

If the fileName field is found in the header or query string, the file is written to the shared directory/<TpName> regardless whether the file is small or large.

This is not supported for AS2 transports.

Disabling Session Caching for Outgoing HTTPS Transports

HTTPS (SSL) transport endpoints (HTTPS, AS2-HTTPS) use an internal SSL transport cache to significantly improve the performance of negotiating security parameters while establishing trusted connections.


12 | Release Notes

In some situations, problems may arise when third party server implementations are not able to properly handle cached sessions or renegotiation of security properties at the beginning of each application level communication session. For example, the Initiator always wants to ensure that the peer's credential is the one that is trusted and hasn't changed during any cached session.

The cache usually holds successfully negotiated security parameters for about 20 minutes, which means that large numbers of transactions between the Initiator and any given trading partner will require a credential renegotiation in approximately 20 minutes.

In order for BusinessConnect to enforce the renegotiation of the peer's credentials, the Disable Session Cache checkbox can be selected for any individual outgoing transport.

When selected, each time when BusinessConnect has business data to be delivered to the corresponding trading partner, the peer's credentials are requested and reverified.

Release 5.0.0The following are the main new features in this release:

Administration

• Unified configuration and administration within TIBCO Administrator

• Single sign-on to TIBCO administration domains

• Process management and deployment within TIBCO Administrator

• System and protocol properties configurable within the BusinessConnect console

• Management of metadata configuration—domain types, roles, partner classification codes, supply chain codes—within the BusinessConnect console

Security

• Credential alerter providing proactive notification of key and certificate expiration

• Ability to associate a “shadow” key/certificate to handle the overlap of new and due-to-expired keys/certificates

Disabling session caching for outgoing HTTPS transports can significantly degrade performance and should only be used if there are known problems with the third party server application's handling of SSL session caching.


New Features | 13

• Enhanced certificate management - key store

• Enhanced CSR (Certificate Service Request) wizard

Logging and Reporting

• Enhanced and optimized message logging

• Built-in support for non-repudiation

• Basic statistical reporting enabling users to graphically visualize overall transactions details

• Ability to store personalized queries in log viewer for repeated usage

Hosts and Trading Partners

• Support for multiple hosts in one single BusinessConnect installation

• Ability to copy and paste a participant

• Wizard to provide a quick and simple way to create a participant

• Ability to export and import a selection of participants

Transports

• Support for AS1, AS2, and Secure FTP as public transports

• Support for SOCKS4 and SOCK5 outbound proxies

• New, simple transport level built-in protocol—EZComm—which allows basic data transfer to and from your trading partner

• Ability to assign a preferred outbound proxy for a participant

• Ability to use flat files as a transport between BusinessConnect and private process

• Smart Routing facilitating better control over the communication channels with private processes

Business Agreements

• Introduction of business agreements to better model the business relationship between host and partner

Transaction Handling

• Built-in support for handling large sized messages


14 | Release Notes

• Ability to group resend transactions

• Ability to visualize resend histories of transactions

Databases

• Support for MySQL

• Archive tool for managing message logs. Archive and purge using native database vendor tools


Changes in Functionality | 15

Changes in Functionality

This section lists changes in functionality since the last major release.

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



Release 5.3.0

Oracle Drivers

• The older Oracle Native JDBC drivers such as classes12.zip, classes12.jar, ojdbc14.jar shipped with Oracle 9i are no longer supported for the Thin driver type.

• The Oracle driver ojdbc5.jar should be used for the Oracle Native JDBC driver (Thin and OCI) for JRE 1.5.0, and ojdbc6.jar should be used for JRE 1.6.0.

Other required accompanying jars that come with the Oracle database should be used in consultation with the Oracle recommendation.

TIBCO BusinessConnect Scripting Deployment

• Behavior for following commands in Scripted Deployment has changed:

— -createInstallation This command now requires that only a TIBCO Administrator Super User can perform this task.

— -importConfigRepo This command now requires that only a BusinessConnect Super User can perform this task.


16 | Release Notes

• The command structure for -importConfigRepo has changed:

— There is a new addition that requires users to pass in the TIBCO Administrator domain as well as the user and password information of that domain where import of the .csx file occurs.

To keep in sync with the current domain usage syntax, the following syntax is introduced for this command:-domain <domain name> -user <domain user> -pw <domain password>

— Previously, the -pw command line argument denoted the password for the .csx file to be imported.

To keep in sync with the domain usage syntax (domain user/password syntax), in this release a new command line argument -csxpw was introduced for the password of the .csx file.

The updated syntax is:

-domain <domain name> -user <domain user> -pw <domain password> -csxpw <password>

Migrator Script

• The Migrator script, used to automate migration of TIBCO BusinessConnect from releases 3.x to 5.x, cannot be used any more with TIBCO BusinessConnect version 5.3.

For more information, see Compatibility and Migration on page 26 and TIBCO BusinessConnect Server Administrator’s Guide, Chapter 5, Migration.

Include Messages in Log Entries

• When the option “Include Messages in Log Entries” was unchecked before, TIBCO BusinessConnect and its protocols were logging messages in the table BC_RESEND_BIN.

If this option is unchecked in this release, resending of messages does not happen for any protocol since there are no entries inserted in BC_RESEND_BIN.

Release 5.2.1No changes in functionality are introduced in this release.

Non-repudiation logging has not been changed and its behavior remains the same as in previous release.



Release 5.2.0

Disable Session Cache

The property Disable Session Cache under the outbound HTTP/S transport has been moved to the location BusinessConnect>System Settings>Installed Protocols>BuasinessConnect Server>Disable Session Cache for

Outbound HTTPS.This property is cleared by default, which means that SSL caching is performed. The property becomes effective immediately after its value is changed and applies to every outbound HTTP/S transport. It should be selected only if there are trading partners using web applications that are proven to be unable to properly handle cached SSL sessions. Disabling the SSL session caching can result in degraded performance due to the frequent re-negotiation of security properties during establishment of the subsequent SSL sessions.

BusinessConnect Server Properties Removed

The following two BusinessConnect server properties have been removed:

• bc.hibernation.enabled

• bc.task.scheduler.enabled

They were located in BusinessConnect>System Settings>Installed Protocols>BusinessConnect Server.

Directory Structure for Local, Temporary, and Large Files

Temporary file systems for local, shared, and large files and the RVCM ledger for file location are not provided with the whole directory path. Users need to put the following instead: ./ (period, slash)

Error Handling for the Asynchronous Request Response Operation

For this operation, the error handling behavior on the Responder side is different on a BusinessConnect 5.2 system compared to a BusinessConnect 3.x system. When an error occurs on the Responder side, BusinessConnect 3.x would forward the error to the trading partner (Initiator), while BusinessConnect 5.2 simply ends the transaction and the Initiator eventually times out.

Smart Routing and message resend

When a user changes the smart routing configuration, such as adds or changes trading partners, the Smart Routing functionality will automatically be changed and messages will be resent using the new configuration.


18 | Release Notes

MIME Content-Disposition Header Change

In previous versions of BusinessConnect, the MIME Content-Disposition header for the outbound document was added at the outer MIME message level for signed messages.

The Content-Disposition header has been moved to the body part, which actually contains the outbound document.

Changes between tibXML and EZComm 5.2.0

The following are changes in behavior between EZComm 5.2 and tibXML:

• Duplicate detection Inbound duplicate detection is not enabled by default as it was in tibXML.

• Error codes, audit states Both the error codes and audit state field values have been changed compared to tibXML .

• Behavior change of the RESPONDER.ACK advisory In the tibXML protocol running with BusinessConnect 3.x, the RESPONSER.ACK advisory was always published to the private process when an error was encountered during processing of an inbound request for the REQUEST.RESPONSE operation.

This behavior has been changed for the TIBCO BusinessConnect EZComm Protocol running with BusinessConnect 5.2. The RESPONDER.ACK advisory is only published when a response is successfully sent back to the trading partner. If there is an error during the inbound request processing, no response will be sent back to the trading partner.

• Incoming passthrough messages EZComm 5.2 generates audit logs for the incoming passthrough messages, which was not available in tibXML.

• Outgoing passthrough messages EZComm 5.2 validates the outgoing passthrough messages, which was not available in tibXML.

• Error status codes not in 200-299 range If the Initiator receives an error status code that is not in the 200-299 range, EZComm 5.2 simply sends an error advisory and generates an audit log for the message, while no Initiator response message will be sent. In a similar situation, tibXML sends both the error advisory and the Initiator Response messages.

tibXML Features No Longer Supported

The following tibXML features are no longer supported in TIBCO BusinessConnect EZComm Protocol:

• Document security override at the operation binding level

• Retry at operation level



• Sending to multiple partners using one request

• Scheduling of transactions

• File name properties for outbound requests using File or FTP transports:bc.tibxml.<file | ftpput>.fileNamePattern

The values of the properties should hold a hyphen-separated list of one or all of the following key words (in any order): tpName, tid, opName, and shortOpName

• Support for FILE and FTP transports; for example, TIBCO BusinessConnect EZComm Protocol 5.2 cannot use the FILE or FTP transports to communicate with a tibXML system.

Changes between EZComm 5.1.0 and 5.2.0

The following are changes in behavior between EZComm 5.2 and 5.1:

• XML document validation In EZComm 5.2, validation can be done using an XSD or a DTD schema, and based on the direction of messages.

In the previous version of the TIBCO BusinessConnect EZComm Protocol, the XML document validation option was used to validate both the outbound and inbound messages. In TIBCO BusinessConnect EZComm Protocol 5.2, this option is divided to support the inbound and the outbound XML schema validation, where messages are validated based on their direction.

• Signing and encryption The checkboxes Require Digital Signature and Require Encryption, which were previously available in the Operations tab, have been moved into the Request Action tab. As a result, these values cannot be overridden for the operation binding in the Partner can Initiate section (for example, an incoming response cannot be overridden). Signing and encryption of a message can be done either for a request or for a response.

• Populating transaction related information The transaction related information (such as operationID, fromTP, and so on) is now populated on the HTTP URL, while in EZComm 5.1 this information was populated in the HTTP headers.

• Replacing values in the HTTP URL Any values specified in the HTTP URL and GUI (such as fromTp, toTp, operationID and filename) now are replaced with the values coming from the private process.

In EZComm 5.1, the HTTP URL entered in GUI was not updated and was sent as is.

• OperationID structure The OperationID structure has changed and now contains three levels as follows: Category/Version/OperationID. EZComm 5.1 has two level operation: Category/OperationID.


20 | Release Notes

• EZComm files location All files are now being written to the directory BC_SharedDir/PartnerName/Date. In EZComm 5.1, files have been written to different directories, depending on how they were created.




Release 5.1.0

Supported Platforms

Platforms that are no longer supported starting from this release:

• Solaris 7

• HP-UX 11.0

Third-Party Software

Software version that are supported starting from this release:

• MySQL 5.0 (minimum)

• Microsoft SQL sp4+

Software versions that are no more supported in this release:

• MySQL 4.1.0

• Microsoft SQLsp2+

BusinessConnect Server Properties

• When the value of bc.ediint.streamSize is modified under System Settings>Installed Protocols>BusinessConnect Server, the new setting will



take effect when the button Save is selected. Previously the new setting would not take effect until BusinessConnect was restarted.

Configuring Proxy Settings

The following two settings have been removed:• HTTP_PASSTHROUGH

• SMTP_PASSTHROUGH

These preconfigured proxy settings were available by selecting BusinessConnect>System Settings>Outbound Proxy Settings. They were available at the business agreement level so that users could override the configured outbound SMTP and HTTP proxies.

In this release, SMTP and HTTP proxy settings are configured as follows:

• For a host Add, remove, or select an SMTP or HTTP proxy using the dialog Edit System Settings>Outbound Proxy Settings.

• For a participant Select an SMTP or HTTP proxy previously added for the host using the dialog Edit Partner Participant>Proxy Settings.

You can also allow/disallow the use of proxies for that participant by selecting or clearing the checkbox Use Proxies.

General Changes

• GUI was previously verifying whether the uploaded custom scripts were syntactically correct. This functionality is no longer available.

• CM Application Name prefix: This string token is used as a prefix to the final RVCM name, which is constructed as follows:{ CM Application Name Prefix }-{Protocol}_{engineinstance}

for example:ACME-PPCM-EZComm_host1-Single-Server

where

— {ACME-PPCM} is the CMApplication name

— EZComm is the protocol

— host1-Single-Server is the engine instance name

• CM Ledger File Name postfix: This string token is used as a suffix to the final ledger file name, which is constructed as a combination of the final CM name as above, suffixed with this Ledger postfix as follows:{Final CM Name}__{CM Ledger File Name Postfix}


22 | Release Notes

for example:ACME-PPCM-EZComm_host1-Single-Server__PPCM.ldg

where

— {ACME-PPCM-EZComm_host1-Single-Server} is the final CM name

— {PPCM.ldg} is the ledger file name Postfix

• The functionality provided under Application Management> BusinessConnect> Configuration>

BusinessConnect> Advanced> Runtime Variables has been removed from deployment as is no longer required

• The functionality provided under Application Management> BusinessConnect> Configuration>

BusinessConnect> Advanced Settings has been moved to a new location under Application Management> BusinessConnect> Configuration>

BusinessConnect> Component Settings>InterComponent Advanced. Local Temporary Directory was also moved to this new location.

• The field in the outbound poller configuration Ignore Files that Exist on Start of Polling has been removed. Its functionality is now supported as explained in the issue <LiveLink>1-6NBYHZ on page 46.

• A redundant runtime system property bc.message.size.threshold has been removed from the BusinessConnect System properties.

Release 5.0.0• Co-Located Private Processes The co-located private processes are not

supported by the BusinessConnect 5.x infrastructure and this functionality has been removed.

• Configuration Data Read-only access to configuration data is not supported.

• File Pollers

— In previous versions of TIBCO BusinessConnect, you were required to specify the level of the directory to be polled, for example, if you specified C:/B2B/InboundFiles/*/*.*, BusinessConnect polled files in the subdirectory two levels down from C:/B2B/InboundFiles.

With this release, BusinessConnect polls files within all subdirectories at all levels under the specified directory. For example, if you specify



C:/B2B/InboundFiles/*.*, BusinessConnect polls files in all subdirectories of C:/B2B/InboundFiles.

— In previous versions of TIBCO BusinessConnect, file matching using the asterisk character (*) was not exact. For example, *.* would match both cat and cat.xml even though cat does not include a dot character (.). BusinessConnect now uses strict filename matching; do not use a dot in a matching string if the desired file does not include a dot.

• BusinessConnect Palette for BusinessWorks BusinessConnect Palette for BusinessWorks is now included in BusinessConnect. It does not have a separate installer and platform support and prerequisites are the same as for BusinessConnect Server. Furthermore, in previous releases of BusinessConnect Palette for BusinessWorks you were required to deploy protocol-specific jars (for example ediclient.jar for EDI and rosettanet_api.jar for RosettaNet) with the BusinessWorks processes.

This is no longer necessary as this functionality has been incorporated into the configuration store.

• AS2 Identifiers

— The restriction on the use of the (“) and (\) characters in AS2 identifiers no longer applies. Therefore, it is no longer necessary to enter " to represent the double-quote character or enter &bslash; to represent the backslash character.

— For inbound AS2 messages, AS2 Identifiers from the messages are only matched against the 'AS2 Identifier' field for the host or trading partner. If the AS2 identifier is not found in the 'AS2 Identifier' field, BusinessConnect does not try to match the identifier with the host or trading partner name.

• Properties The only way to access BusinessConnect properties is through the System Settings > Installed Protocols > BusinessConnect Server area of BusinessConnect console. Properties from earlier releases of BusinessConnect that don’t appear in BusinessConnect console are not supported.

• Shared secrets Shared secrets are not supported.

• Credentials The file reference mechanism for uploading credentials is no longer supported. Downloading of credentials is no longer supported. The replacement is the credential export feature.

• Uploading files The only way to upload a file is through a file reference. Other mechanisms, such as LDAP, FTP, tibcr:, HTTP, are no longer supported.

• Utilities All of the utilities provided in previous releases are no longer supported. The only utilities provided in this release are the database archiver and the migration scripts.


24 | Release Notes

• Database schema The database schema used in this release is substantially different from the one used in previous releases.

• Transaction states Many new transaction states have been introduced in this release. Therefore the states that you observe in the transaction detail view of the audit log will be different from those in previous releases.

• Transports TrustAct Advanced transport is no longer supported so configuration data won't be migrated from previous releases.

• Custom scripts

— The BusinessConnect console does not verify that uploaded scripts are syntactically correct.

— The job.list functionality is no longer supported.


Deprecated Features | 25

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 5.3.3There are no deprecated features in this release.

Release 5.3.2• Database archiving tool has been deprecated from this release.

Release 5.3.1There are no deprecated features in this release.

Release 5.3.0• TIBCO DataDirect JDBC drivers are deprecated from this release.


26 | Release Notes

Compatibility and Migration

Release 5.3.3

Upgrading to Release 5.3.3

TIBCO BusinessConnect release 5.3.3 can be installed only after release 5.3.0 has been installed.

To complete the upgrade after installation, do the followings:

1. Log on to TIBCO Administrator and click on the BusinessConnect>Manage Installation link. Enter and save the JDBC settings to connect to your previous configuration store. You will be logged off automatically when settings are saved.

2. Re-log on to TIBCO Administrator and click on the BusinessConnect>Manage Installation link again. Follow the instructions to complete the configuration store upgrade.

3. Verify that the installation has been upgraded.

Click BusinessConnect>System Settings>Installed Protocols and ensure that the versions numbers for BusinessConnect Server, BusinessConnect Remote Client Service and BusinessConnect EZComm Protocol are all pointing to the version 5.3.3

When upgrading TIBCO BusinessConnect to a major or a minor version, the process of Create Installation is used; when upgrading with a service pack, use Save to save the changes.

If you have not already installed a particular component of release 5.3.0 (such as the BusinessConnect palette for TIBCO ActiveMatrix BusinessWorks), you will not be able to install it after installing release 5.3.3. Make sure all release 5.3.0 components are installed before proceeding to install release 5.3.3.


Compatibility and Migration | 27

Release 5.3.2







Click BusinessConnect>System Settings>Installed Protocols and ensure that the versions numbers for BusinessConnect Server, BusinessConnect Remote Client Service and BusinessConnect EZComm Protocol are all pointing to the version 5.3.2.

Release 5.3.1






28 | Release Notes






Release 5.3.0

Smart Routing Migrator and Migrator (CData migration) are not supported from this release on. Users who want to migrate from TIBCO BusinessConnect 3.x release must follow the migration procedures to migrate first to TIBCO BusinessConnect 5.2.x release and then to TIBCO BusinessConnect 5.3.0 release.

For more details, see TIBCO BusinessConnect Server Administrator’s Guide, Chapter 5, Migration.

Release 5.2.1




From this release on, users won’t be able to migrate their TIBCO BusinessConnect configuration data from 3.x releases.

If you have not already installed a particular component of release 5.2.0 (such as the BusinessConnect palette for TIBCO BusinessWorks), you will not be able to install it after installing release 5.2.1. Make sure all release 5.2.0 components are installed before proceeding to install release 5.2.1.







Release 5.2.0

Migration to BusinessConnect 5.2.0 depends on the version that is currently installed on your machine:

• Version 3.x For migrating from a version 3.x to any version 5.x (5.0, 5.1, or 5.2), see the TIBCO BusinessConnect Server Administration Guide, Chapter 5 Migration, section “Migrating from BusinessConnect 3.x to BusinessConnect 5.x”.

• Version 5.0 There is no direct migration path from the version 5.0 to the version 5.2. If you currently have the version 5.0, you first need to migrate to the version 5.1, and then to the version 5.2.

See the following manuals:

— TIBCO BusinessConnect Server Administration Guide Version 5.1, Chapter 5 Migration, section “Migrate from BusinessConnect 5.0 to BusinessConnect 5.1", and

— TIBCO BusinessConnect Server Administration Guide Version 5.2, Chapter 5 Migration, section “Migrate from BusinessConnect 5.1 to BusinessConnect 5.2"

TIBCO Runtime Agent 5.5.3 is required to run BusinessConnect 5.2.0.

This service pack addressed a security issue applicable only to the BusinessConnect runtime engine; it is not required for the BusinessConnect palette installation.

Apply the service pack before running BusinessConnect 5.2.0.


30 | Release Notes

• Version 5.1 For migrating from the version 5.1 to the version 5.2, see TIBCO BusinessConnect Server Administration Guide version 5.2, Chapter 5 Migration, section “Migrate from BusinessConnect 5.1 to BusinessConnect 5.2”

Release 5.1.3







Click BusinessConnect>System Settings>Installed Protocols and ensure that the versions numbers for BusinessConnect Server and BusinessConnect EZComm Protocol are all pointing to the version 5.1.3.

Release 5.1.2











Click BusinessConnect>System Settings>Installed Protocols and ensure that the versions numbers for BusinessConnect Server and BusinessConnect EZComm Protocol are all pointing to the version 5.1.2.


32 | Release Notes

Closed Issues

The table in this section lists closed issues in this release.

Closed CR # Resolution

5.3.3 BC5528 If the TIBCO BusinessConnect engine was stopped or crashes while there are protocol transactions being processed, the restarted transactions did not complete when the engine was restarted.

This issue has been fixed.

5.3.3 BC-5472 When connecting to Oracle RAC, connections to the configuration database could not be restored and did not show the correct URL.


5.3.1 1-ALR47R The file license.pdf shipped with TIBCO BusinessConnect 5.3.1 precedes any previous licenses that have been shipped with TIBCO BusinessConnect 5.3.0. Users should look for licenses in the document license.pdf.

5.3.1 1-A6DISB Repeating of the 'Accept' header fields was not supported on the incoming HTTP(S) requests.


5.3.1 1-ACBBQZ When running multiple TIBCO BusinessConnect engines, the poller would seem to be running on all engines, rather than only on the scheduler.


5.3.1 1-ACB0FD BCRemote 5.0 could not be started when the AS2_HTTPS transport was selected under Business Agreements->Primary Transport for a particular Protocol Binding.


5.3.1 1-ACAI92 When searching for a participant from the Participant List, TIBCO BusinessConnect would not allow searching by the fields shown in that list.

This issue has been fixed. Search now matches the values in any of the visible columns in the Participant List.


Closed Issues | 33

5.3.1 1-ABAA9P An administrator needed a long time to login in when LDAP with several thousand users was enabled for TIBCO BusinessConnect 5.3 User Management.


5.3.1 1-A7VAS9 When multiple engines were deployed for TIBCO BusinessConnect interior servers, BCRemote would fail on startup.


5.3.1 1-A6F1C6 While using a Microsoft vendor-specific JDBC driver, TIBCO BusinessConnect was unable to fetch BIN messages from the audit log when using sqljdbc 1.2 and sqljdbc 2.0 even when connected correctly.


5.3.1 1-9N1IBC TIBCO Business Studio would throw an internal server error when the BusinessWorks project referenced by a BusinessWorks component used the TIBCO BusinessConnect palette.


5.3.0 1-L4GP5 Schema is now loaded correctly for Receive Request Activity in the BusinessConnect palette when the operation name contains EDI-specific transaction modifiers.

5.3.0 1-IFZAN TIBCO BusinessConnect release now allows auditing of user level changes made through TIBCO Administrator UI for trading partners, business agreements, and operations.

5.3.0 1-EBFG8 TIBCO BusinessConnect release 5.3.0 now supports managing of User Access Control permissions on the trading partner level, as well as filtering of the Log Viewer based on particular user's privilege for the trading partner.

5.3.0 1-9Q71RQ When the option “Include Messages in Log Entries" was unchecked, TIBCO BusinessConnect and its protocols were logging the messages in the table BC_RESEND_BIN.

This issue is fixed and the behavior is changed from the previous release. If this option is unchecked, resend of messages does not happen for any protocol since there are no entries inserted in BC_RESEND_BIN.



34 | Release Notes

5.3.0 1-9P3HQ5 On an existing successfully deployed system in Dual Firewall DMZ deployment mode, if additional Interior engines were added and deployed without clicking on Save in the Application Management> BusinessConnect, the new Interior engines that were added would never receive messages from the DMZ Server.

This has been fixed.

5.3.0 1-9OZONZ In TIBCO BusinessConnect Trading Partner Administration Guide, Appendix A, Database Archiving Tool, a correction has been made to list JRE 1.5.0 as supported.

5.3.0 1-9OB7K3 When the Send/Request activity from the BusinessConnect palette was used with a TIBCO ActiveMatrix BusinessWorks group that had auto confirmation disabled in the BusinessConnect connection settings, the BusinessWorks confirm task would fail in confirming the Send/Request activity.


5.3.0 1-9LR529 Emails received from the POP3 server were incorrectly rejected even though a valid email address was present among multiple other email addresses in the To or CC fields.

In these cases, messages were not properly identified as email messages to be consumed by TIBCO BusinessConnect.

This has been fixed. Now the email address specified either in the To field or in the CC field is correctly processed.

5.3.0 1-9KAFVN Receiving an inconsistent/erroneous reply from some SSH servers occasionally resulted in unexpected stopping of the SSH/FTP poller.

This problem has been fixed.



Closed Issues | 35

5.3.0 1-9JZP35 This issue addresses and clarifies the usage of shadow vs. original credential usage during the overlay period. For more details, see TIBCO BusinessConnect Trading Partner Administration Guide, Chapter 1, TIBCO BusinessConnect Participants, section Shadow Credentials.

When the original credential has a shadow credential added for stand-by, the Outbound messages that are signed or encrypted would use the shadow credential during the overlay period for the plain Email/AS1/AS2 transports.

When messages from the plain Email/AS1/AS2 transports are received from the trading partner, the shadow credential is used first to either authenticate or decrypt the message. If it fails, the original credential will be used during the overlay period.

5.3.0 1-9FI3U1 Fixed an issue where the AS2 handler was not looking at the HTTPSCA settings when returning async MDNs via HTTPS.

5.3.0 1-9CVW59 TIBCO BusinessConnect EZComm Protocol was not sending payload as file reference on Responder.Request Message for FTP Get protocol.

A new property ezcomm.interior.pp.threshold is now added to the EZComm protocol. If the payload size (in bytes) is above the value specified in this property, payload is sent as a file reference to the private process.

This behavior is only applicable to the FTP-Get transport protocol.

If this property is not specified, it defaults to the value “Skip Content Threshold" specified in the tab Application Management>Business Connect>Configuration>Intercomponent Advanced.

Users can add this property in the configuration UI at BusinessConnect> System Settings> Installed Protocols>

EZComm. They need to add an integer property named ezcomm.interior.pp.threshold and enter a threshold value.

5.3.0 1-9C1MO3 The TIBCO BusinessConnect palette, using JMS transport, would serialize decimal values as floats in the lexical space instead of properly using xpath1.0.




36 | Release Notes

5.3.0 1-9B1IT3 Fixed an issue where no peer changes from the configuration UI would occur when Administrator and BusinessConnect engines are on different machines with different network interface names. The Intercomponent network setting in the deployment UI was used by the Administrator machine to send peer change to the BusinessConnect engine. BusinessConnect engine network settings must be overridden at each instance of the BusinessConnect Engine in the .tra file after deployment to receive the updates from the Administrator machine. This setting can be found under Application Management>BusinessConnect>Configuration>Component Settings> Intercomponent Communication>Interior Settings .

Following properties must be added if there are network interface name differences between Administrator and BusinessConnect machines along with multicast group to each BusinessConnect engine .tra file. The value entered as part of the network interface name in the .tra file is the NIC name pertaining to the machine and the “multicast group” must be the IP address specified in the Intercomponent network settings for Interior engines under deployment. These properties must be added and configured appropriately for BusinessConnect engine .tra files:

tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/network=<nic>;<multicast group>tibco.clientVar.gatewayProperties/transports/Intercomponent/bmh/network=<nic>;<multicast group>tibco.clientVar.gatewayProperties/transports/Intercomponent/dmz/network=<nic>;<multicast group>

Note: If there are more than two different network settings, but same “Service” ports in any of the deployment configuration, then the second TIBCO Rendezvous transport would not initialize due to RV and IP Protocol limitation. (Refer to TIBCO Rendezvous documentation for a complete explanation).

If the private process uses TIBCO Rendezvous for communication, then if the “Service” value is the same as the one set in InterComponent Communication>Interior Settings, either the “Service” value must be changed to something different, or the same Network value (<nic>;<multicast group>) must be specified in the deployment section for the TIBCO Rendezvous transport to start. The file BusinessConnect engine .tra should also be modified for this property:

tibco.clientVar.gatewayProperties/transports/backoffice/RVCMQ/network=<nic>;<multicast group>

Bus.User.<rv parameters> and Bus.Default.<rv parameters> parameters in the .tra file may also be needed to change if the service parameter is the same as the one in the Intercomponent Interior engine settings in the deployment section.



Closed Issues | 37

5.3.0 1-95OZX0 When using custom scripts for the SSHFTP transport, the API getLastMod() occasionally did not return the file modification time correctly.


5.3.0 1-95MC0G When importing a TIBCO BusinessConnect configuration from a .csx file, some schema references were removed in the Operations Editor.


5.3.0 1-923S0Q When exporting and importing back participants, the SSHFTP scripts were not migrated for the business agreement EZComm protocol binding under the option “Allowed Inbound Transports".


5.3.0 1-910VEO Explicit instructions have been documented in TIBCO BusinessConnect Server Administrator’s Guide, Chapter 5, Migration, on whether to uninstall the previous version of the TIBCO BusinessConnect software.

5.3.0 1-90UV9N The TIBCO BusinessConnect palette using JMS transport can duplicate inbound events if the flow limit for the given eventsource is set to a low (non-zero) value.


5.3.0 1-90UL3X Searches on existing business agreements may return fewer than expected results.


5.3.0 1-90RA2H When receiving a zero-length file from an FTP or SSHFTP transport using the EZComm protocol, TIBCO BusinessConnect was not able to process these messages.

This has been fixed

5.3.0 1-8ZDNLG In a high-volume scenario where two or more BusinessConnect engines are running on the same machine, duplicate AS2 message IDs were generated by the javamail package provided by Sun Microsystems.

This issue has been resolved by packaging the defect fix from a later version.



38 | Release Notes

5.3.0 1-8Y8S7V When scripted deployment in TIBCO BusinessConnect 5.2.1 Add-On pack was used with BusinessConnect EDI Protocol 5.3.0, the bcappmanage tool was not able to connect to the domain when commands were executed. This was due to a conflict with the version of jars shipped with TIBCO BusinessConnect EDI Protocol.

This issue has been fixed in TIBCO BusinessConnect release 5.3.0.

5.3.0 1-8XORN1 Retry and Dispatching timeout properties for the EMAIL transport specified in the BusinessConnect public transport deployment were not working.


5.3.0 1-8XMBZE Attachments sent using EMAIL transport for the EZComm protocol did not work as expected when the trading partner name contained spaces.


5.3.0 1-8X085T When running the MySQL database on a UNIX operating system, creation of Audit and Runtime tables was not successful.


5.3.0 1-8W5AFQ When importing operations that have two levels at BusinessAgreement> Protocol Operation Bindings, the operation bindings were not imported.


5.3.0 1-8UI3Y9 The SSH tunnels, which were unused/deactivated due to receiving sporadic SSH_FX_FAILURE signals from the SSH server, can hold on to extra threads after several hours of operation. These threads should be terminated so that system resources can be freed.


5.3.0 1-8T1UL4 The resend poller can raise a NullPointerException with business protocols where the interaction type is not defined for some private process messages.


5.3.0 1-8SHAOI

1-7TV748

If there was an existing server identity associated to a hostname that was already loaded in the configuration GUI, a new identity could not be associated when creating a new key through Certificate Signing Request (CSR).




Closed Issues | 39

5.3.0 1-8QQGU9 When user authorizations were enabled in TIBCO Administrator with the Read access permissions, there were use cases where the Save button was enabled for the Read Only User.


5.3.0 1-8H55U1 If leaf certificates did not have encryption bit enabled, the BusinessConnect Certificate Store in the configuration UI used to throw a Servlet Exception when clicking on System Settings>Certificate Store.


5.3.0 1-8B9F7E, 1-8B9F6F, 1-8B9F37

The BusinessConnect protocol installers (such as EDI, SOAP, RosettaNet, and TCM) were unable to detect that the BusinessConnect engine component is not already installed, although it was required for all BusinessConnect protocol installations.

This would happen when only the BusinessConnect document component was installed.


5.3.0 1-89DKIL When using the asynchronous Request Response transactions in the current version of TIBCO BusinessConnect EZComm Protocol, if the Responder would send an asynchronous response in the tibXML format (which is possible by setting /tibXML in url/subject), the Initiator treated it as a new request coming in and rejected the transaction.


5.3.0 1-846H0M TIBCO BusinessConnect 5.3.0 now supports managing of the BusinessConnect application using scripted deployment.

Please refer to TIBCO BusinessConnect Scripting Deployment User’s Guide for various command details.

5.3.0 1-7ZCCST This defect is closed by adding a section called “Data loss caused by low database performance parameters in DB2” to TIBCO BusinessConnect Server Administration Guide, Appendix A, Troubleshooting Migration.



40 | Release Notes

5.3.0 1-75PGBC The digest algorithm employed in calculating the MIC value for the MDN receipt for an inbound AS2 request was always based on the document security settings configured under the business agreement. This would occasionally cause problems with the receipt verification on the trading partner end when the digest algorithm used in the incoming request did not match the same setting in the business agreement configuration.


5.3.0 1-70NQ5O In TIBCO BusinessConnect release 3.6.0 and earlier, the Username and Password for the proxy server could not be saved on a Windows server.

This is no longer an issue with TIBCO BusinessConnect 5.x releases.

5.3.0 1-6Q5KSE TIBCO BusinessConnect 5.3.0 supports TIBCO Administrator 5.6.0, which started using Tomcat version 5.5. Therefore, possibility of encountering Denial of Service is no longer an issue.

5.3.0 1-6AS56P In TIBCO BusinessConnect release 3.6.0 and earlier, when initiating an HTTPS connection BusinessConnect did not check if the trading partner’s leaf certificate from the Server was the same as the one that was configured.


5.3.0 1-5YYIFA When there were failures to acquire the DB lock, the BusinessConnect trace would show failures as an ERROR role; however, this failure should be shown as a DEBUG role.


5.3.0 1-4ORV96

1-4A7TML

Ability to perform flow-control on the property Max Jobs for Gateway/DMZ/From-Partners/FILE/Receiver process was requested.

With TIBCO ActiveMatrix BusinessWorks being the underlying engine of BusinessConnect, there are finer granular controls to throttle the Inbound File Poller at the DMZ engine.

5.3.0 1-2D6O8E TIBCO BusinessConnect 3.5.x release would not save tibXML messages received from a trading partner.

This has been fixed. The state RECEIVED_FROM_TP now stores bin messages.



Closed Issues | 41

5.3.0 1-1WPX4J TIBCO BusinessConnect DMZ engines on a Windows operating system now allow the engine to be started automatically after the machines have been rebooted if the DMZ engines are installed to run as a automatic service.

5.3.0 1-1UWGXT TIBCO BusinessConnect now provides an option for selective export of trading partners.

5.3.0 1-175BY3 When receiving messages from a trading partner using any transport, the original filename that is specified in the transport headers or on the FTP server is now reflected in the BusinessConnect Audit Logs.

5.2.1 1-8PFO18 CSX files could not be imported into MySQL if the business agreement had a start or end date at or above year 2038.

This has been fixed, but make sure to perform these steps:

1. Export the existing CSX file

2. Upgrade the installation to BusinessConnect 5.2.1

3. Perform again the step Create Installation

4. Import the file exported CSX file

Without steps 1-4, migration from BusinessConnect version 5.2.0 to version 5.2.1 will not succeed.

5.2.1 1-8OO04J The transactionID generated in the MDN alert did match the ID present in the actual outbound request as BusinessConnect was generating its own internal transactionID.


5.2.1 1-8OGLGB When the FILE transport with a script for the outbound transaction was used, the transactionID returned by the file script’s job.get (transactionID) was different from the transactionID passed by the private process and the BusinessConnect generated transactionID was displayed as documentID in the audit log.


5.2.1 1-8NZ8XI BusinessConnect was adding the EZComm field information to the URI, such as fromTp, Tp, operationID, and operationType. This information should be added only when posting to an /EZComm URI.

This has been fixed. The EZComm specific URI information will be added only when “/EZComm” is used.



42 | Release Notes

5.2.1 1-8ME915 For tibXML RESPONDER.ACK message to the private process, the aeClass path under the “^prefixList^” RV message field was incorrectly output for EZComm instead of tibXML. This caused an java ClassNotFoundException on the custom subscribing application for back office integration developed on SDK.


5.2.1 1-8LX1HM On migration from version 5.1.3 to version 5.2.0, BusinessConnect failed to detect the existence of audit/nr/runtime tables upon new installation creation against a database that contains existing audit/nr/runtime data specifically from version 5.1.3 and caused the tables to be dropped and recreated. All the existing data was removed inadvertently.


5.2.1 1-8LWDAS If the connection to the database is unavailable during the uninstallation of BusinessConnect and its protocols, an exception is generated. When this occurs, the uninstallation process remains incomplete and the plugin is not unregistered from the TIBCO Administrator.




Closed Issues | 43

5.2.1 1-8L9GED The migration utility in BusinessConnect release 5.2 adds an import line into all schemas migrated from the release 3.x with “xsd” as the namespace prefix, causing the migrated schemas to be invalidated; for example:

<abc:schema xmlns:abc ="http://www.w3.org/2001/XMLSchema" ...Schema after migration to BC52:<abc:schema xmlns:abc ="http://www.w3.org/2001/XMLSchema" ... <xsd:import namespace="http://www.w3.org/XML/1998/namespace"/> ...

This has been fixed. The added import line now uses the predefined schema namespace; for example:

Schema in release 3.x:

<abc:schema xmlns:abc ="http://www.w3.org/2001/XMLSchema" ...

Schema after migration to release 5.2:

<abc:schema xmlns:abc ="http://www.w3.org/2001/XMLSchema" ... <abc:import namespace="http://www.w3.org/XML/1998/namespace"/> ...

By default, the migrator will always fix the schemas when migrating.

If you don’t want to fix up the schemas, you can now add a new Java property called fixupXSD to migrator.bat (sh) in the directory TIBCO_HOME/bc/5.2/bin to prevent the migration utility from adding the import line to the schema files.

To do this, add the following to migrator.bat (sh):

-DfixupXSD=false (it is true by default, which is set internally)



44 | Release Notes

5.2.1 1-8KS6YT Some SSH servers don't return the file size in SSH_FXP_ATTRS when the file is opened for read. This causes the receiving application to return with 0 bytes transferred.


5.2.1 1-8J217A Export of all trading partners spanned across multiple pages used to fail due to an error.


5.2.1 1-8HSR0H For tibXML private process messages, the tracking information in the RV AEMsg was not interpreted and published. This created a backward compatibility issue with legacy private processes that rely on the tracking information for back office integration.

The tracking information is now processed and published in the “^tracking^” RV message field for all tibXML private process messages.

5.2.1 1-8HSQYI For outbound EZComm email and AS1 notify request, BusinessConnect 5.2 always dynamically generates the email subject based on the operation and the transaction ID. This created a backward compatibility issue with request generated from BusinessConnect 5.1 where user can specify any subject and is sent to trading partner as is.

This issue has been fixed by configuring the following Boolean property to preserve the configured email subject that reverts back to the BusinessConnect 5.1 behavior: ezcomm.notify.email.preserveSubject.

Add the property in TIBCO Administrator as follows:

1. Go to BusinessConnect->System Settings

2. Select Installed Protocols | EZComm plugin

3. Add a Boolean property: ezcomm.notify.email.preserveSubject

Note: This property will not be exported on configuration export (CSX). It will have to be explicitly re-configured upon importing on new BusinessConnect installation.

5.2.1 1-8H2M11 Fixed a problem in EZComm where inbound files were getting renamed even though AS2 filename preservation was enabled. Problem occurred when an inbound AS2 file exceeded the large file size threshold and the MIME headers of the message did not contain the MIME-version header.



Closed Issues | 45

5.2.1 1-8GI9YV The private key credential leaf was not returned if the leaf's key was capable only of signing. This problem would also be manifested in the credential view showing only an error or stacktrace.


5.2.1 1-87VILE An operation was deleted when it was used in a business agreement and tried to delete the operation in the operation editor.


5.2.0 1-8DSEMY The original file name of the message downloaded from the FTP-Server was not preserved when the processed message was passed to the private process.

This has been fixed. The original file name now can be passed to the private process for an incoming message via the FTP or FILE transport.

5.2.0 1-8CCLR5 A message ERROR.RECEIPT.RECEIVED was displayed when a signed receipt was requested for an AS1 encrypted message. The audit log was showing ERROR_SIGNED_RECEIPT_MISMATCH_MIC.


5.2.0 1-8A396N The FTP-Get poller intermittently missed the cycle of invocation to retrieve inbound requests from the FTP servers. These servers belonged to the trading partners configured with multiple business agreements, which were associated with multiple trading hosts, and where different FTP server connection settings were used.

This has been fixed

5.2.0 1-8A3965

(EZComm)

The FTP script variables srcFileName and srcFilePath were not available for the request generated from the outbound EZComm File poller when the payload size was below the large file threshold setting.


5.2.0 1-894N1L On some FTP server implementations, the BusinessConnect server would experience indefinite excessive high CPU utilization when the FTP control connection with the trading partner’s FTP server was abruptly or prematurely terminated.




46 | Release Notes

5.2.0 1-86Q4E6 There was an enhancement request to pass the field value Content-Disposition:>filename to the private process for the transactions received over the AS2 transport.

This support has been added.

5.2.0 1-859A3D It was not possible to dynamically set the MIME subject for AS2 transmissions.

This has been fixed. The AS2 transport will now use the MIME subject specified by the private process.

5.2.0 1-8495GT With large number of participants and business agreements, navigation of the administrator screens for the list of participants and for the business agreement was becoming significantly unresponsive. The reason was repeated access to the configuration store database each time the screens were refreshed.

This has been addressed with internal caching and optimization.

5.2.0 1-81KVU1 There was an error UnsupportedEncodingException while processing an XML file for the outbound request. The specified encoding value of the XML file was in single quotes, which was not recognized by BusinessConnect.

Now the encoding value specified in single quotes will be interpreted correctly.

5.2.0 1-81HO7M

(EZComm)

The user defined transactionID in the outbound EZComm Initiator Request was not accessible in the FTP script context. The FTP script job variable FTPClient.TRANSACTION_ID would return a machine generated unique ID instead.


5.2.0 1-810TXZ BusinessConnect was unable to install in silent mode without the BusinessConnect palette component when BusinessWorks was not already installed on the same machine.


5.2.0 1-80YCTD A security exception was thrown when migrating an outbound transport from the BusinessConnect 3.x configuration export (.cdata) that contained a password.




Closed Issues | 47

5.2.0 1-80H6R3, 1-7173ST

The library file bcplugin.jar of the BC palette was installed incorrectly under the folder TIBCO_home\bw\plugins\lib\bc .

This is now corrected and the file is installed in the folder TIBCO_home\bw\plugins\lib\palettes.

5.2.0 1-7Z6CM6, 1-7Z6CMS, 1-7Z6CO0

The FTP transports over HTTP, SOCKS4, and SOCKS5 proxy servers were not working.


5.2.0 1-7W44SS The content-disposition file name field in the outbound Initiator Request on the AS2 transport was ignored when the message was encrypted. The resulting MIME message headers would always output with a content disposition filename set as smime.p7m.

An encrypted document should have the content-disposition header with a filename set to smime.p7m as per SMIME specification RFC3851. However, when the encrypted document was decrypted, the content-disposition header was missing from the MIME body part that contained the outbound document.

The value of the content-disposition filename field in the outbound Initiator Request is now correctly used as the filename value in the content-disposition header of the MIME body part that contains the unencrypted outbound document.

5.2.0 1-7VOUJZ

(EZComm)

The message Responder.Request was populating binary data on the Plain Request node.

Now, when the Initiator.Request message has the binaryPayload field populated, the message will be packaged as binary data.

5.2.0 1-7TSQXT The extra CR/LF characters were added to the XML payload for plain EMAIL or for the AS1 request.


5.2.0 1-7TL5FK Software requirements for configuring a DMZ server were missing in the TIBCO BusinessConnect Server Administrator’s Guide.




48 | Release Notes

5.2.0 1-7TJ6TS Hidden protocol properties migrated from the BusinessConnect 3.x configuration export (.cdata) were not displayed in the BusinessConnect 5.x administrator console.


5.2.0 1-7IGT8D For the Single Server deployment, payloads received from the inbound File poller were incorrectly deleted upon successful processing when the payload size was below the large file threshold and the option to delete file was disabled.


5.2.0 1-7H2KA7 In order to properly set databases and connections, a user needed to have information about Oracle RAC URLs in the TIBCO BusinessConnect Server Administration Guide.

This information is now provided in the TIBCO BusinessConnect Server Administration Guide, Chapter 2 Pre-Deployment Configuration, section “Configure Oracle”.

5.2.0 1-7GFLLS Lists of JMS topics and queues and of the RV subjects for private process messages were not documented.

This has been added in the documentation.

5.2.0 1-7BEYG2 The Resend History log did not capture the user that initiated the resend activity.

Also, the history of messages resent to private process was not viewable in the Resend History log.

Both issues have been fixed.

5.2.0 1-7AJR28

(EZComm)

An inbound EZComm message received from the FTP-Get poller was previously always published as a file reference in the Responder Request message to the private process, regardless of the message size threshold setting.

The skip content threshold is now honoured for incoming FTP-Get messages; for example, the message will be published as data if its size is below the skip content threshold.



Closed Issues | 49

5.2.0 1-7A96HV Fault tolerant setting parameters for the inbound File poller were not configurable from the BusinessConnect administrator console.

The activation interval and heartbeat are now available when configuring the inbound File poller. See TIBCO BusinessConnect Trading Partner Administration Guide, Chapter 14 for more details.

5.2.0 1-799G1U No configuration options were available to control the cipher encryption strength level on an outbound HTTP request over SSL.

The following cipher suite grade options are now available when configuring an outbound HTTP/S transport:

• Only Stronger Than Export Policy

• Only 128-bit and Stronger

• Only Stronger than 128-bit

• Only 256-bit and Stronger

5.2.0 1-77OMFV

(EZComm)

Error advisory was published on an incorrect subject INFO.RECEIPT.SENT that the Initiator, upon failure to process the synchronous signed receipt, received from the Responder.

Advisory is now properly published on the subject ERROR.RECEIPT.SENT.

5.2.0 1-77FRE9 Shared secrets credentials were not migrated from the configuration export in BusinessConnect 3.x systems.

This has been fixed

5.2.0 1-77ASAT

(EZComm)

Incoming plain AS2 binary EZComm messages that were not signed and not encrypted were incorrectly published on the plainRequest field to the private process, instead of on the binaryRequest field on the Responder.Request.


5.2.0 1-74LN6P For an outbound Email encrypted message sent as an attachment requesting a signed receipt, BusinessConnect failed to process the returned signed receipt, resulting in a MIC MISMATCH error.




50 | Release Notes

5.2.0 1-73R9BX Access privileges for existing administrator users were ignored during the configuration data migration from BusinessConnect 3.x systems.

This has been fixed. Permissions of the existing administrative domain users will now be migrated.

Note This is not the default. The switch is exposed and explained in the migrator script.

5.2.0 1-732SFW The ledger file location was not handled properly during the BusinessConnect configuration export and import.


5.2.0 1-6ZVEDT Access to the Manage Installation configuration panel was not controlled when a user with the read-only access privilege was logged in.


5.2.0 1-6Z1BY7 BusinessConnect was unable to recover from a lost JMS server connection during runtime. Private process messages would not be delivered and consumed until the engine was restarted to resume the JMS server connection.


5.2.0 1-6QI9HF When an implicitly signed email (whether it was only signed or signed and encrypted) was received from the mail server by BusinessConnect, the message was not verified and was not processed. An error message with the description “Error parsing email request from Trading Partner. MIME Content Error“was reported in the audit log and advisory.

This has been fixed. The inbound email messages that are implicitly signed are now supported. However, implicitly signed outbound email messages are supported for tibXML only. It is by design that the MIME based transports of BusinessConnect support use of multipart/signed for all other outbound MIME messages.

5.2.0 1-6P5QSO, 1-7471BQ

Under high volume scenarios on a Dual Firewall DMZ mode deployment, the temporary files containing the prefix BW_ATTACHMENT were not cleaned up in the locations for HTTP large and shared files for the inbound messages that exceeded the Skip Content Threshold setting.




Closed Issues | 51

5.2.0 1-6NMAVV All proxy screens did not check that correct information was entered into the host, port, user name, and password fields.


5.2.0 1-60IBD7 When executing the BusinessConnect Palette tasks Send Misc. Msg, Send Response, and Send Request, output was reflected on the error tab even on successful completion.


5.2.0 1-1SWU6H, 1-6Z368G

Schemas containing the nested schemas were not imported in the BusinessConnect Palette.


5.1.3 1-81EISX Error advisory is now published upon post failures on outbound request to a trading partner using the AS2 transport.

5.1.3 1-80OOPP Import would fail for the configuration exports (.csx) that contained participants with the FTP or FILE transport scripts previously created from the Copy operation.


5.1.3 1-80OICE All operation schemas and transport scripts were erased from the configuration store database for a protocol when a script was removed and reloaded within a single TIBCO Administrator session.

Note: This defect did not occur when the script removal and reloading was done consecutively within the corresponding transport setting panel.


5.1.3 1-807LEV The BusinessConnect runtime engine reported that the FTP transport was not enabled when it was done by selecting the option “FTPS transport only“under the transport panel of the business agreement.


5.1.3 1-7ZPCBV Processing of an outbound message using the FTP transport script would hang when the JavaScript execution encountered an unexpected exception unrelated to the FTP server connection.




52 | Release Notes

5.1.3 1-7YUIVV An “Index out of bound" exception was caught during the private process smart route processing when the smart route rule was configured with an operation ID that did not match the number of levels defined for the protocol; for example, a smart route rule with OperationID = */*/*/* for the EDI-X12 protocol caused the exception since an EDI-X12 operation is defined as <InterchangeVersion>/<GroupVersion>/<Transaction> that contains only 3 levels.


5.1.3 1-7YCHGU Under a high volume message scenario using JMS as the back-office communication with the BusinessConnect palette, the SendRequest activity intermittently would fail to synchronously receive the response messages when the configuration option Don’t Wait for Response was cleared.

Note: This defect did not occur when the ReceiveResponse activity was configured to process the response asynchronously for a request sent from the SendRequest activity.


5.1.3 1-7Y6RRK Special characters in file names were incorrectly replaced by the corresponding hex representation for documents received through the FTP-Get transport.

This has been fixed. The following set of characters embedded in the file name is now properly handled: %, $, #, &, @, !, +

5.1.3 1-7XUTLP The Audit archive tool would fail to work properly for the DB2 database server on an AIX platform.


5.1.3 1-7XUOZ0 The business agreement settings Scheduler Dates were not recoverable from the configuration export (CSX). The dates were not exported properly into the CSX.

To migrate scheduler settings, regenerate the CSX export after applying the fix.



Closed Issues | 53

5.1.3 1-7XUOXG Overridden Document Security settings of Operation Bindings under Business Agreement were not recoverable from configuration export (CSX). The overridden settings were not exported properly into the CSX.

To migrate document security settings, regenerate the CSX export after applying the fix.

5.1.3 1-7WSD5J BusinessConnect 3.x migration shell scripts would fail to start when TIBCO Runtime Agent was upgraded to version 5.5 and the previous version 5.4 was uninstalled.


5.1.3 1-7TUJNH The uploaded script files for FTP or FILE transports were not copied when a participant was created using the Copy operation.


5.1.3 1-7TM2W6 The Audit log viewer would fail to fetch correctly for query against the transaction status of Any Errors.


5.1.3 1-7HVF3K Schema validation failures were encountered when the validating XML contained elements or attributes that belonged to a nested schemas but were not explicitly referenced in the parent schema definition.


5.1.3 1-79MPNZ Limited cipher algorithms were exposed in the inbound HTTPS transport, which prevented usage of high cipher strength encryption algorithms (such as the 256 bit based AES256-SHA algorithm) during an SSL handshake for inbound requests.


5.1.3 1-793QHW

(EZComm)A vulnerability existed for ‘code injection’ for inbound EZComm messages containing the ‘OperationID’ header field that could be populated with JavaScript. This script would get executed when displayed in the administrator log viewer.




54 | Release Notes

5.1.3 1-77DUH7 Binary files sent through the outbound file poller for TIBCO BusinessConnect EZComm Protocol were corrupted when the file size was less than the value Skip Content Threshold specified in the deployment configuration. The default threshold is 10 Mb.


5.1.3 1-76RRTN Incorrect version information was displayed in both the runtime engine trace log and in the installed protocols section under the System Settings in the BusinessConnect administrator console.


5.1.3 1-750VDP Protocol plugin properties were not recoverable from the configuration export (CSX). The plugin properties were not exported properly into the CSX.

To migrate protocol plugin properties, regenerate the CSX export after applying the fix.

5.1.2 1-7GF295 The Override HTTP Failure Retry Settings was not migrated for configuration data of RosettaNet protocol version 2.6.


5.1.2 1-7FQKH1 Excessive time was taken in preprocessing large outbound XML request initiated from the RosettaNet protocol for certain operation types when outbound validation was enabled.


5.1.2 1-7EY58N Exporting configurations with large number of host business agreements took a long time.

This has been fixed. Export cache optimization, similar to CR 1-7D3E9F, has been provided.

5.1.2 1-7D3E9F Importing configurations with large number of host business agreements took a long time. A caching problem caused unnecessary delays in processing host business agreements.


5.1.2 1-7CGU48 TAW log was not rolling over to a new file when the max size was exceeded.




Closed Issues | 55

5.1.2 1-7CGU30 TAW log was not providing debug level tracing.


5.1.2 1-7BY602 Error description was insufficient when an user attempted to delete an operation that was bound to any existing Business Agreements. The partners of the constraining Business Agreements cannot be identified.


5.1.2 1-7BP4GU Sorting of the expiration date column was not proper under the System Settings > Certificate Store panel.


5.1.2 1-7AH2HB Migration tool was updated to recognize the version 3.x operation property RNIFVersion for RosettaNet and migrated those values correctly into 5.x installations.

5.1.2 1-7AGSTN Smart-routed incoming JMS messages for different operation types from trading partners may have not been processed by the BusinessConnect palette activity when deployed separately in multiple BusinessWorks engines.


5.1.2 1-7A44SB The string fields content within RVMSG was not properly XML-escaped prior to its reconstruction into the XML document, which caused malformed XML validation exceptions.

Handling of outbound transactions initiated by a private process with parsed payload (RVMSG) has been fixed.

5.1.1 1-74YV0P Non-overridable protocol property values were saved with defaults even though proper values were entered in the configuration GUI after a business agreement was created. This affected the interior runtime server, which would not pick the correct values that were entered by users in the Participant protocol properties screen.


5.1.0 1-710FGF When an HTTP transport URL was empty, the migration tool would create an associated transport and using it as the default, instead of dropping it.




56 | Release Notes

5.1.0 1-710FEV BusinessConnect and BusinessConnect RosettaNet: There was a request to allow Intel's legacy BusinessConnect 3.x private processes to use RvMsg format for their request/response. Currently, these applications sending INITIATOR.REQUEST or RESPONDER.RESPONSE will fail with an error: PIP terminated - Message error: Unsupported source object


5.1.0 1-6YVEHF In TIBCO BusinessConnect RosettaNet 2.6.0, users had permissions to trading partner settings, which included the RosettaNet activity bindings. After migration to TIBCO BusinessConnect RosettaNet 5.0, users were getting access only to participants and not to business agreements.

This has been fixed. After migration all users have access to business agreements by default.

5.1.0 1-6Y6727 There was a request to prevent possible user mistakes and typos by providing a dropdown list for selecting document encoding (UTF-8).

This has been provided by making UTF-8 to be the default.

5.1.0 1-6Y45TZ There was a request to review global variables used by the BusinessConnect framework, and to expose them in the GUI and/or in documentation (nomenclature).

This has been fixed. Most of the properties have been documented.

5.1.0 1-6XY049 XML validator whereby the pattern below will not detect an alphabetic character in a field which is defined as <xsd:pattern value=

"([-]?[0-9]{0,13}([-]?))([.]([-]?)[0-9]{0,7}[-]?)?"/>


5.1.0 1-6XEYKV There was a request to allow the inbound File poller to pick up existing files.

This has been provided.

By default, all the files that are present in the inbound and outbound File poller now will be picked up when the BusinessConnect engine starts.



Closed Issues | 57

5.1.0 1-6X95WF

(EZComm)When transmitting a large file (1 GB) via BusinessConnect EZComm, the BusinessConnect servers are timing out and sending timeout errors to both private processes and to the Initiator server. The timeout parameter was not configurable via the GUI.

This has been fixed. This parameter is available in the GUI as DMZ-Interior timeout .

5.1.0 1-6WR1DA

1-6Y3GYQ The BusinessConnect engine was not starting up when the used TIBCO Rendezvous parameters were not default. This was happening for intercomponent and private processes communications.


5.1.0 1-6WJGR3

1-6WJGRJOne user editing a protocol using the protocol editor was effectively preventing another user to edit the same protocol.

When trying to edit the protocol, users were prompted with the following error:

Grammar in use: Time checked out (locked) by another user:

username, time of check out: dateAndTimeStamp"

This has been fixed. Multiple users can now concurrently edit different operations for a protocol without encountering lock conflicts.

5.1.0 1-6VYYP5 When receiving an inbound file using FTP-Get, users were prompted with the following error:Failed to move temporary FTPGet file <filename> to shared location.

This has been fixed and this error message does not show up any more.

5.1.0 1-6VTTB1

(EZComm)For EZComm, it was requested that BusinessConnect has ability to send a file with both name and content.

This issues has been fixed and explained in the section New Functionality under <LiveLink>Allow override of filename via HTTP parameter on page 8.



58 | Release Notes

5.1.0 1-6VOQJF It was requested that BusinessConnect provides ability to configure the following load balancing parameters:

• BusinessConnect CMQ name

• TIBCO Rendezvous transport parameters: network and daemon

• CMQ specific properties (scheduler, worker properties) to be configurable differently for each instance if needed

This has been fixed and provided in BusinessConnect 5.1.0.

5.1.0 1-6U7EHH There was a request that the BusinessConnect documentation provides explanation about the supported certificate types .

This has been provided and the following information is available in the documentation for BusinessConnect 5.1.0:

BusinessConnect supports X509 certificates versions 1, 2, and 3.

All digital certificates used in BusinessConnect must be compliant with the PKIX standard RFC #3280, which described on the following website:

http://www.ietf.org

5.1.0 1-6SUSS9 When an EDI document was received over the AS2 transport, BusinessConnect would send an MDN back. If MDN sending failed, BusinessConnect did not retry it even though the properties bc.httpRetryCount and bc.httpRetryWait were set.

This has been fixed. Please refer to TIBCO BusinessConnect Trading Partner Administration Guide, Table 5, Edit Protocol Bindings: Transports Tab, AS2 MDN Async Reply Transport.

5.1.0 1-6QG0CB Shared directory paths of the form //hostname/baseDir/... or //ipaddress/baseDir/... did not work for any of the File poller paths (inbound or outbound).


Note: On Windows, if a user specifies a shared directory or a large files directory using the Universal Naming Convention (UNC), such as \\servername\foldername, then the user has to ensure the following:

1. The folder is shared correctly

2. The user has secured his network access to that servername, and he can log onto that server and access the specific folder. Usually, the user can do that by mapping the drive to that folder.



Closed Issues | 59

5.1.0 1-6Q5LAG When an Initiator request would come from the private process that was sent on a file reference (not a complete data), and if the reference was not found, an error without any error advisory would be displayed.


5.1.0 1-6Q2P1I Email transport that can send or receive messages from Netscape email clients was not supported in the previous release.

This has been provided.

5.1.0 1-6PZUQ2 The error advisory was not generated if files using the inbound File poller transport were not dropped in the appropriate folder as dictated by the protocol.


5.1.0 1-6PZUOG

(EZComm)For EZComm, overriding of schema files under Business Agreement> Protocol Binding> Action Settings>

Override Action Settings did not work. Documents were always validated against the schema files loaded in the Operations Editor.


5.1.0 1-6PZUMX

(EZComm)For EZComm, inbound transactions were not verified for signing or encryption. Whatever came in was accepted.


5.1.0 1-6PZSJC The outbound File poller failed to move the files from its directory into the error directory for failed transactions when the file with the same name already existed in the error directory.


5.1.0 1-6PF2ZA The BusinessConnect build number shown in the BusinessConnect plug-in uploaded in the TIBCO Administrator was incorrect showing the month and date for the plug-in instead of the build number.


5.1.0 1-6P8RUA The protocol checker was not enabled for the Participant Wizard and users could create an incompletely specified participant when using the wizard.




60 | Release Notes

5.1.0 1-6OZQRP It was requested that BusinessConnect has a facility to activate/deactivate the proxy server at a trading partner level, or to bypass the proxy for certain trading partners.

This has been resolved as follows:

• A property has been added to the proxy settings (under Participant) to allow a BusinessConnect user to explicitly disable the use of a proxy for any outgoing traffic with a specific trading partner. If it is disabled, no proxy will be used at all. If it is enabled (by default), then the user can optionally choose a “preferred” proxy to be used with this trading partner. By selecting None, the BusinessConnect user is indicating that there is no preference, and whatever is defined on the system level should be used.

• A special case for SMTP is that even if the BusinessConnect user disables the use of proxy for a specific trading partner, the system level SMTP proxy will still be used to send email due to the nature of SMTP.

5.1.0 1-6OVEM9 When the value of bc.ediint.streamSize was modified under System Settings>Installed Protocols>BusinessConnect,

the new setting would not take effect until BusinessConnect was restarted.

This has been fixed. The new setting will take effect when the button Save is selected. This change is also documented in Changes in Functionality, BusinessConnect Server Properties on page 16.

5.1.0 1-6OUYFD For migrated users, permission to access business agreements were missing. It was necessary to manually give permissions to migrated users to access the business agreements area after migration.


5.1.0 1-6O3PXH There was a request to provide support for Oracle RAC.

Support for Oracle RAC is now provided in BusinessConnect release 5.1.0.



Closed Issues | 61

5.1.0 1-6NBYHZ A field in the outbound poller configuration called Ignore Files that Exist on Start of Polling was invalid and its functionality was not supported.

This option has been removed.

This functionality is now provided in the following way:

• By default, all File pollers (inbound or outbound) will pick up existing files when the engine starts up.

• It is advised in general that users select the checkbox Delete Files after Processing in order to have files removed properly after processing has been done.

5.1.0 1-631Q41

(EZComm)The BusinessConnect console did not prevent the deletion of the BC/Notify operation that comes as default with EZComm.


5.1.0 1-61D0U1 A redundant runtime system property bc.message.size.threshold has been removed from the BusinessConnect System properties.

5.1.0 1-2GROK3

(EZComm)In TIBCO BusinessConnect EDI Protocol, support was not provided for uploading a custom FTP script as a file reference.

This has been fixed. Now both EDI and EZComm protocols support this feature.

5.1.0 1-1HYBGV The GUI's trusted CA tool used not to indicate the expiration of the CA certificates and the certificate check tool could not recognize the expired CA certificates.




62 | Release Notes

Known Issues

The table in this section lists known issues in this release.

CR Summary/Workaround

1-ALQRF7 Summary TIBCO BusinessConnect engine won’t start on the AIX platform with JRE 1.6.0. It throws an “Unsatisfied link” error due to the newly introduced path from JRE 1.6.0.

Workaround Add JVM_LIB_DIR/../lib/ppc to tibco.env.LIBPATH so that the new JRE 1.6.0 path is loaded by AIX.

1-ALGR8J Summary If the Email page under Deployment is not clicked on and saved while performing the deployment steps for TIBCO BusinessConnect, then the TIBCO BusinessConnect server does not pick up emails from the Email server.

Workaround Make sure to click Save on the Email page every time before deploying TIBCO BusinessConnect servers.

1-9ULVUH Summary When deploying DMZ as a servlet, the log level always outputs the DEBUG level even if it is set to INFO or any other level.

Workaround None

1-9ULVGG Summary When receiving Synchronous Requests from a trading partner for the TIBCO BusinessConnect EZComm protocol and if the MaxJobs are set for the TIBCO Rendezvous Receiver process, then the BusinessConnect engine cannot process more than the specified MaxJobs even though synchronous responses are returned back successfully.

Workaround Do not set MaxJobs and let the non-harmful inbound jobs to eventually time out.

1-9U6Y9Z Summary BusinessConnect Audit Trails are shown in the User Access Audit Trail when Inbound transports are disabled at Application Deployment>Public Transports, even though they are not shown in the business agreement.

Workaround None

1-9U0V0A Summary BusinessConnect configuration UI: When users try to export the transactions for the reporting component for Data Reports with space as a delimiter and none as the text qualifier, the data that is exported in the CSV format could not be imported into Microsoft Excel spreadsheet.

Workaround Use a different delimiter, and a text qualifier other than “none”.


Known Issues | 63

1-9SPEGG Summary When importing the file .csx for operation or participants , User Access Audit Trail does not work.

Workaround None

1-9SKHH4 Summary When receiving EZComm or tibXML messages from a trading partner, if the host and partner information is interchanged the BusinessConnect engine does not throw an error.

Workaround None

1-9SGBI9 Summary When using the AS2 transport to compress an outbound message on AIX and Solaris x86 machines, you may see the following stack trace when the compressed content object is being cleaned up by setting its content to null:

setContentSEVERE: java.io.IOException: Stream closedThrowable occurred: java.io.IOException: Stream closed at java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:146) at java.io.BufferedInputStream.fill(BufferedInputStream.java:230) at .......................................

Workaround None. The stack trace is not harmful and can be ignored.

1-9RZQGG Summary In the User Access Audit Trail available under BusinessConnect > Systems Settings, the property name for Default Domain Identity is logged as Default Interchange Qualifier ID.

Workaround None

1-9RZEYB Summary Advanced search fields for the User Access Audit Trail in BusinessConnect> System Settings are case sensitive.

Workaround None

1-9RS74X Summary When using TIBCO Runtime Agent versions prior to 5.6.0, if the Document Security Digest Algorithm is set to MD5 the micalg value in the content-type of signed messages is always sha1,

Workaround Upgrade to the latest version of TIBCO Runtime Agent.



64 | Release Notes

1-9QPG6V Summary The NT Service of the bcengine cannot be started if you first deploy the BusinessConnect server and then upgrade JRE version from 1.5.0 to 1.6.0.

Workaround To deploy the BusinessConnect engine and start the NT services successfully, do the following:

1. Upgrade JRE to version 1.6.0

2. Make sure that the file bcengine.tra in the directory $BC_HOME/bin has JRE pointing to 1.6.0.

1-9PI7KR Summary When using TIBCO DB2 drivers for DB2 9.5 and viewing System Settings>CertificateStore, the SQL Exception “No more data available to read" shows in the TIBCO Administrator UI and displays a reduced number of private keys.

Workaround This issue does not exist when using the native IBM Universal Type 4 driver for DB2.

1-9OLMGM Summary The sample files bcfilemodifier.bat and bcfilemodifier.shell located under BC_HOME/samples/bc/ftpscripts are not updated for the JRE path when JRE 1.6.0 is used.

Workaround Update the path manually even after running the tool replaceJRE.

1-9NX3FN Summary If a BusinessConnect user other than the Super User is given Read/Delete permissions for the default Host participant, and if this user logs and deletes the default Host, the UI for that user will suggest that the default Host was deleted. However, the default Host has never been deleted due to other constraints.

Workaround If the users logs out and logs back in, they will be able to see the default Host that was presumably deleted.

1-9NT70N Summary When using DB2 9.5 with TIBCO JDBC drivers, some of the host’s private keys under System Setting->Certificate Store are not migrated.

Workaround Users should use IBM Universal Type 4 drivers.

1-8RBKG6 Summary The database archiver tool does not support migration of audit, non-repudiation, and runtime data archived from a previous version of a BusinessConnect installation, such as 5.1.x to 5.2.x. Exception will be thrown when a user attempts to import from an archive export generated from an earlier version of BusinessConnect.

Workaround Manually upgrade the database schemas. For details, see TIBCO BusinessConnect Server Administrator’s Guide, section To Manually Upgrade the Other Database Schema Tables.



Known Issues | 65

1-8QKX9I Summary If <network>;<multicast group> is provided in the Network field of the Rendezvous transport, DMZ throws exception after deployment.

Workaround Add manually the following properties in the .tra file on the DMZ server:

Bus.Default.Network=192.168.4.3;239.255.1.1Bus.Default.Daemon=tcp\:8900Bus.Default.Service=8900

These properties need to be added to the .tra file after the deployment.

1-8NOC45 Summary EZComm: For synchronous transactions, if the response filename contains a space, the synchronous response results in an error being passed to the private process.

Workaround None

1-8DPPAF Summary EZComm: The message content of the binary payload downloaded from the transaction audit state SEND_TO_PP is corrupted for inbound transactions.

Workaround To retrieve the binary payload content, download the message content from the transaction state UNPACKAGE_MSG state.

1-8DPPAF Summary For the binary content messages on inbound, the message stored in the audit log SEND_TO_PP is incorrect.

Workaround None

1-8DPP5P Summary EZComm: For the outbound sign and encrypt request, the description in the error advisory issued for an unrecognized content-type specified in the private process request is not informative enough to identify the cause.

The following generic information is described: “Failure to encrypt S/MIME message. Please check the Outbound Doc Exchange/Encryption Info Settings under the Document Security tab

for the Business Agreement.“

Workaround None

1-8DPP5P Summary Transactions fail when a user specifies the incorrect content-type in the Send Request activity.

Workaround None



66 | Release Notes

1-8DOOYO Summary When the nested schemas containing the include closures are imported into the BusinessConnect palette, the closures will be imported and created but the root schema will need to be associated with the closure after the import. When clicking on the root schema (such as rootElement) in the folder /BCSchemas/protocol/operation, the dialog will ask which closures the schema should be associated with.

Workaround If you have a root schema with a few include closures, select the closure objects (rootElement_closure1, rootElement_closure2, and so on) until TIBCO Designer indicates that the schema is complete.

1-8DOOXJ Summary Use of different schema components in the schemas with the same root element on the same operation is not supported in the BusinessConnect palette.

Workaround None

1-8DKZSH Summary EZComm: When working with the EZComm tutorial with the Send Notify Request process, after importing configuration from the database the Input tab of the activity SendRequest will have two body elements.

Workaround Delete both body elements and map the field textContent of the Read File activity to the field StringData of the body element.

1-8D2OTM Summary EZComm: For the EZComm inbound RESPONDER.REQUEST and INITIATOR.RESPONSE messages the inclusion of the message contents that enables the resend from the log viewer is always enabled, regardless of the setting “Include Message in Log Entries” that is available in system settings for the JDBC configuration. All messages, including INITIATOR.REQUEST, INITIATOR.RESPONSE, and RESPONDER.REQUEST, should not be resendable when the checkbox “Include Message in Log Entries” is cleared.

Workaround None

1-8D2ORH Summary EZComm: For EZComm synchronous operations, an incoming synchronous response is not denied and a proper permission is not enforced based on the settings that are configured under the Response action of the operation using the checkboxes Signed and Encrypted. For example, an incoming plain synchronous response is incorrectly accepted when the checkboxes Signed or Encrypted are selected for an incoming synchronous response.

Workaround None



Known Issues | 67

1-8CRWY3 Summary For plain inbound multi-part emails, the first body part is skipped and processing starts from the second body part.

Workaround Prepend a text/plain body part which can be safely ignored; or add a Content-Name header to the second body part and use a name other than segment1.

The Content-Name header has the following syntax: Content-Name:name value

1-8CRAVN Summary EZComm: A proper Initiator.Response with an error status is not generated for an outbound EZComm request upon failure to process the outgoing request or the incoming response.

Examples for error conditions include schema validation errors, invalid credentials, and missing operation bindings. An error advisory is issued, but the Initiator.Response is not available. As a consequence, if the Initiator.Request is generated from the BusinessConnect palette activity sendRequest on BusinessWorks, this activity will time out waiting for the Initiator.Response in case it is configured to wait for the response from BusinessConnect.

Workaround None

1-8CR68H Summary In tibXML email messages on the inbound, the binary message in the state of the audit log UNPACKAGE_MSG has garbled text.

Workaround None

1-8CFMLD Summary EZComm: When an incoming synchronous request fails due to an invalid certificate or a key, the Responder should send an error back to the Initiator and terminate the transaction properly. Instead, the Responder currently simply sends an error advisory and terminates the transaction.

Workaround None

1-8C68WQ Summary When using TIBCO Designer, “Business Connect Connection” field in the JMS tab, if the secured check box is selected and then a user clicks on the button “Update from Configuration Store” to fetch a non-secured JMS configuration, the secured check box is not cleared.

Workaround None



68 | Release Notes

1-8B9F6W, 1-8B9F4F

Summary The BusinessConnect installer incorrectly allows uninstallation of the components BusinessConnect engine or BusinessConnect Palette when there are existing installations of BusinessConnect protocols such as EDI, SOAP, RosettaNet, and TCM.

Individual protocol installations no longer function without the BusinessConnect engine component, therefore such uninstallation should not be allowed.

Workaround Before uninstalling the components BusinessConnect engine or BusinessConnect Palette, first uninstall all protocol installations.

1-8B4JTH Summary A protocol plugin released before BusinessConnect version 5.2 could contain example scripts that are pointing to the file commons-lang-2.0.jar and that would have problems running when installed under BusinessConnect 5.2.

Workaround Update the example scripts to point to the file common-lang-2.2.jar, which in BusinessConnect 5.2 has replaced the previous commons-lang-2.0.jar file.

1-89YSTN Summary The BusinessConnect server plugin property bc.maxAuditLogEntriesPerView does not take effect immediately in all log viewers.

Workaround Log out and then log back in the TIBCO Administrator console.

1-89U3B1 Summary The Scheduler Heartbeat and Scheduler Activation settings are not migrated when importing from a configuration export.

Workaround None

1-89TKMH Summary Sorting of the lists Participant and Business Agreement in the list view is not available.

Workaround Use the search facility to narrow down the list of returning participants and business agreements.

1-89AAEF Summary BusinessConnect always creates SMIME signatures with the SHA1 digest algorithm, even if the signature's digest algorithm was configured to be MD5. This should cause no problems during verification as long as the verifier implements SHA1.

Workaround None



Known Issues | 69

1-89A5YG1-732H23

Summary For the TIBCO BusinessConnect and protocols on HP-UX and HPItanium, Uninstallers are not found. The directory _uninst does not contain the Tibuninstall.bin executable.

Workaround Manually start the uninstaller by executing the following commands:

For BusinessConnect:

$ cd TIBCO_HOME/bc/version/_uninst$ java -cp uninstaller.jar run

For Protocols:

$ cd TIBCO_HOME/bc/version/protocols/protocol/_uninst$ java -cp uninstaller.jar run

1-888H7N Summary EZComm: In the inbound EZComm request and response operations, incomplete transactions may occasionally fail to recover and be unable to complete processing. This happens when the backup runtime engine is activated under a fault tolerant (FT) group after the primary engine stops abnormally. As a result, BusinessConnect fails to respond to the trading partner who initiated the request.

Workaround None

1-87V4MR Summary EZComm: For the synchronous request, the DMZ component waits for the response from the interior Business Connect server. If the interior server does not send a response due to some errors, the DMZ component times out and throws the timeout advisory with the status code of 0 (zero)

Workaround None

1-87OVK5 Summary EZComm: In the Dual Firewall DMZ mode, the Responder cannot send a response if the interior component has a file reference as a message. The same failure can occur when the message size exceeds the value of the BusinessConnect property bc.ediint.streamSize.

Workaround None

1-87G69P Summary Duplicate detection is not correct when the BusinessConnect engine is killed in and then restarted. There is a possibility of wrong detection of inbound duplicates on engine restart.

Workaround None



70 | Release Notes

1-86MS2F Summary EZComm: Interface export of tibXML from the BusinessConnect 3.6 systems is not supported. Import of tibXML configuration data is only supported using the BusinessConnect 3.x migration tool.

Workaround None

1-86AT20 Summary EZComm: For the outbound EZComm messages requesting an asynchronous receipt, the receipt timeout advisory fails to honor the private process Smart Routing rule when the conditions are met.

Workaround None

1-853EIN, 1-853OW9

Summary Under the advanced search settings of all log viewers, the underscore character '_' is not recognized and could yield incorrect search results in the query.

Workaround None

1-84PQ2W Summary EZComm: The default EZComm operation BC/1.0/Notify is preloaded on each new BusinessConnect installation creation and cannot be removed. Updated attributes of this operation, such as uploaded schema files, will not be migrated when performing a full import from a CSX import.

Workaround None

1-81GFKL Summary The creation date and expiration date for MAC under the partner for TIBCO BusinessConnect cXML Protocol are reset when users first work in the partner screen and then follow other links and save outside this screen.

Workaround None

1-81DZWH Summary The service patch installer for BusinessConnect 5.1.3 incorrectly installs BusinessConnect runtime engine files when the BusinessConnect installation contains only the BusinessConnect Palette component.

Workaround None



Known Issues | 71

1-7U58M4 Summary User permissions do get lost after applying hotfixes or service packs that include fixes in user interface (specifically, when the new bcwebadmin.war file is shipped). Therefore, users would either loose the ability to see the BusinessConnect link, or to see BusinessConnect in the read only mode.

Workaround To fix the problem, log into TIBCO Administrator and do the following:

1. Click User Management

2. Click the Users console

3. Click the user on the user list

4. Click the Permissions tab and open up permissions associated with BusinessConnect

5. Grant appropriate permissions

6. Click Save.

1-74J69H Summary Import-export feature has an issue which causes the inbound File poller parameters not to be handled properly and the values stored in previous configurations to become lost.

Workaround Users need to reset these values once the BusinessConnect 5.1 configuration has been imported.

1-74J664 Summary Exporting configuration from BusinessConnect 5.1 has an issue which causes the following user specific values not to be exported:BusinessConnect>Configuration>BusinessConnect>component Settings>Intercomponent Advance Settings


1-747C4Y Summary The current non repudiation log search is not working properly for the Status field. Each selected status is showing the same number of transactions.

Workaround Status field is not used for non repudiation log search and should be ignored. This field will be removed in the next release.

1-73OKIM Summary When new roles and services are added to the PIP.exp file and the file is imported, new roles and services are added to the metadata configuration but the same are not reflected in the Operations Editor until the user logs out and in again.

Workaround None



72 | Release Notes

1-732SGF Summary Import-export feature has an issue which causes the fault tolerance parameters not to be handled properly and the values stored in previous configurations to become lost.


1-732GEA Summary In HP-UX, TIBCOInstallationManager.bin can't find JRE automatically. Users need to use -is:javahome to specify JRE path manually.

If JRE is installed in a non-standard location, the installation manager may not find it in the search path. On TIBCO Runtime Agent 5.4.0, the install packages JRE 1.5.0, which also may not be included in the installation manager launcher search path.

Workaround None

1-72IZX9 Summary Clicking on the button Reset to Default in the Advanced tab during process configuration results in a new processes.

Workaround None. Refrain from using the button Reset to Default in the Advanced tab.

1-71MREC Summary EZComm: EZComm does not support Cancel transaction functionality.

Workaround None. EZcomm currently does not support cancellation of transactions, such as MDN. Users will not be able to select and cancel any pending transactions.

1-71EXRB Summary Exporting configuration from BusinessConnect 5.1 has an issue which causes the following user specific values not to be exported: BusinessConnect>Configuration>BusinessConnect>Private Process

Configuration>TIBCO Rendezvous> CMQ Name


1-705JJ0 Summary If DMZ export is done using a wrong fileName, an error will show up in the small browser window and not on the main browser. Users cannot read that error in the small browser window.

Workaround Look at the TIBCO Administrator log file to check the error.

Make sure that the bcengine.tra file provided is a valid file from a BusinessConnect 5.1 installation.



Known Issues | 73

1-6QFLAS Summary FTP and FTPS inbound transport creation does not throw an error message if any of the following information is missing.

• Username

• Password

• Certificate and key (for FTPS only)

Workaround Ensure that all the fields are appropriately filled along with appropriate certificates wherever required.

1-6Q5SC2 Summary Sorting of audit log entries by clicking the column heading currently does not work.

Workaround None

1-6PPS4D Summary When receiving a message on an HTTP-based transport, there is a problem reading the HTTP and MIME headers when a message arrives specifying charset=UTF-16 in the content-type header.

Workaround Remove charset=UTF-16 from the content-type header before sending UTF-16 files to BusinessConnect using HTTP or AS2 as the transport.

1-6OVEMO Summary Some .tmp files are not removed when the Message Size Threshold specified by the system property bc.ediint.streamSize is exceeded.

Workaround Periodically remove old .tmp files from the shared file directory.

1-6MJ4RZ Summary A UTF-16 XML document sent on the RESPONDER.REQUEST private process message is garbled rather than having a proper XML payload.

Workaround This problem occurs when UTF-16 files are sent across platforms (for example, from Windows to UNIX). Convert to using UTF-8 XML files, if possible.

1-6LX793 Summary After saving the password for the private key, when a user types another (wrong) password the system first gives an error, but it allows the password change.

Workaround Editing private keys requires a user to set both the password and the key file at the same time. If you need to change the password, delete the existing key and add a new key with the new password.



74 | Release Notes

1-5SH7Q1 Summary A large file request that is sent through the inbound or outbound file poller may be occasionally picked up incorrectly for processing while the file is still in the process of copying from the source location. This causes a file access exception during processing by the BusinessConnect runtime engine.

Workaround First copy the request file to a temporary directory and then move it or rename it in the monitoring directory of the file poller.

1-5KYJEG Summary If the process starter for HTTPS or HTTPSCA fails because of a missing credential or HTTP, HTTPS, or HTTPSCA fail due to unavailability of a required port, all the HTTP* process starters will fail to start.

Workaround Determine which process starter(s) are failing and correct them.

