TIBCO BusinessConnect™ Release Notes

(1)

TIBCO BusinessConnect™

Release Notes

Software Release 6.0.1 May 2012

(2)

SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE

AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

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

TIBCO, The Power of Now, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO BusinessConnect, and TIBCO EDISIM 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.

TIBCO Software Inc. Confidential Information

(3)

Contents

|

ⁱⁱⁱ

Preface

TIBCO BusinessConnect^™ software is a B2B (business-to-business) gateway that allows your company to engage in electronic commerce with your business partners.

Topics

• Related Documentation, page vi

• Typographical Conventions, page viii

• Connecting with TIBCO Resources, page xi

(6)

|

^vii

Enterprise Archive (EAR) for the project. The EAR can then be used by TIBCO Administrator for deploying and running the application.

• TIBCO Runtime Agent™ software: This software suite is a prerequisite for other TIBCO software products. In addition to TIBCO Runtime Agent components, the software suite includes the third-party libraries used by other TIBCO products such as TIBCO Designer, Java Runtime Environment (JRE), TIBCO Hawk^®, and TIBCO Rendezvous^®.

• TIBCO Rendezvous^®: This software enables programs running on many different kinds of computers on a network to communicate seamlessly. It includes two main components: the Rendezvous programming language interface (API) in several languages, and the Rendezvous daemon.

• TIBCO Enterprise Message Service ™ software: This software provides a message service that enables integration of applications within an enterprise based on the Java Message Service (JMS) specifications.

(8)

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions Convention Use

TIBCO_HOME ENV_HOME BC_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is

C:\tibco.

TIBCO BusinessConnect installs into a directory within TIBCO_HOME OR ENV_HOME. This directory is referenced in documentation as BC_HOME. The default value of BC_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\bc\version.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use ^MyCommand to start the foo process.

bold code font

Bold code font is used in the following ways:

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

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

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, ^MyCommand is enabled:

MyCommand [enable | disable]

(9)

Preface

|

^ix

italic font Italic font is used in the following ways:

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

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

• To indicate a variable in a command or code syntax that you must replace.

For example: ^MyCommandPathName Key

combinations

Key names separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d) Convention Use

Table 2 Syntax Typographical Conventions Convention Use

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

For example:

MyCommand [optional_parameter] required_parameter

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

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

MyCommand para1 | param2 | param3

(10)

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair ^param1 and ^param2, or the pair ^param3 and ^param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters.

The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions Convention Use

(11)

Preface

|

^xi

Connecting with TIBCO Resources

How to Join TIBCOmmunity

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

How to Access All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO Support

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

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

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

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.

(12)

(13)

|

¹

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 5

• Deprecated Features, page 8

• Compatibility and Migration, page 9

• Closed Issues, page 15

• Known Issues, page 44

(14)

New Features

This section lists features added since the last major release of TIBCO BusinessConnect^TM.

Release 6.0.1

There are no new features in this release.

Release 6.0.0

In this release, the following functionality has been introduced:

• Unified Gateway Server in the DMZ Zone

— A full Gateway container for pluggable services such as FTP Server, web-based PartnerExpress, as well as for HTTP (HTTPS) and FILE services.

— A secure management port to be monitored by the TIBCO BusinessConnect Administrator UI, as well as by BusinessConnect Interior Servers.

— A running Gateway Server maintains connectivity with TIBCO BusinessConnect Interior Server through heartbeats.

— Secure data streaming all the way to Interior Servers, with no file in rest.

— Detachable Gateway containers that can be assigned to a particular Gateway instances, rather than assigning all services to one instance.

• PGP support for the FTP transport

— Fully functional PGP data signing, encryption, and compression of payload when putting the file on the FTP Server, as well as decrypting, verifying, and uncompressing the payload when retrieving the payload.

— Generation of PGP credentials including ASCII Armor format.

— The FTP Custom Scripts function is supported for PGP as well as with the introduction of the new Java API.

— RSA key pair as well as DSA and Elgamal key types.

• Log Viewer in the TIBCO Administrator UI includes the following enhancements

— A dashboard statistics of how many transactions are processed by each business protocol, as well as a view of Gateway sessions and the Gateway

(15)

New Features

|

³

Instance audit trail for TIBCO PartnerExpress and TIBCO BusinessConnect Plug-in for FTP Server.

— Flexible preferences with different set of grouping available in the search results.

— Additional 'search within results' easy search to query on the data that has been already queried.

• User Authentication support for External Users from trading partners

— User authentication from TIBCO BusinessConnect database as well as LDAP authentication. Multiple LDAP sources can be added and one of them can be selected for authentication.

— User Authentication for External Users for trading partner users who need access to services from the web-based TIBCO PartnerExpress, TIBCO BusinessConnect Plug-in for FTP Server, and for future services.

• IP Filtering support

— Network IP filtering for the Gateway Server based on the definition of expressions defined in the configuration.

— IP filtering for the Interior Server (available only for the TIBCO

BusinessConnect Plug-in for FTP Server) to accept or deny requests at a trading partner level.

• Inbox transport

A new Inbox transport support to store payload securely in BusinessConnect database that can be retrieved by External Users of the trading partner through TIBCO PartnerExpress or TIBCO BusinessConnect Plug-in for FTP Server

• Additional platforms

— AIX 7 64-bit

— RedHat Enterprise Linux 5.x and 6.1 64-bit

— 32 bit Installers for Windows 2003 R2, Windows 2008 R2, Windows 7

— 64 bit installers for Windows 2003 R2, Windows 2008, Windows 2008 R2, Windows 7

(16)

• Additional databases

— DB2 9.7

— MySQL 5.5

— Microsoft SQL Server 2008 R2 with Type 4 JDBC Drivers

— Oracle 11gR2, Oracle RAC 11gR2

— Oracle RAC 11gR2 TAF support using Oracle Thick-Driver

• SHA-2 Digest Algorithm

SHA-2 Digest Algorithm support has been added for AS2, AS1 and Email transports. SHA-256, SHA-384 and SHA-512 algorithms are currently supported.

• BusinessConnect AppManage command support:

— Additional commands to create and list Gateway Tokens have been added.

• Support is provided to run the Inbound File Poller behind the DMZ firewall along with the Interior Server. This is achieved by creating a FILE Gateway Service and running it inside the firewall.

• The Monitoring tab is added at Application Management>

BusinessConnect> Configuration> Interior Server.par as a part of the service configuration to write any TIBCO Hawk rules.

• Support is added for wildcards in the certificate CN name when bc.security is set to ^HIGH.

• Support for HTTP 1.1 is provided for outbound HTTP (HTTPS) connections initiated by TIBCO BusinessConnect.

• The Email transport provides addresses for TIBCO BusinessConnect to send out emails when there are credentials that are about to expire.

• Import and export functions have been optimized.

• A separate option Request Wait Duration can be set for FILE and HTTP Gateway services, which was not possible in earlier BusinessConnect releases.

• The Interior Server tracing can be controlled dynamically without having to shut down the engines. Changing the tracing levels would not need a restart of the engines.

• TLS and SSLv3 support can be controlled separately for the outbound HTTPS transport.

(17)

Changes in Functionality

|

⁵

Changes in Functionality

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

Release 6.0.1

There are no changes in functionality in this release.

Release 6.0.0

In this release, the following functionality has been changed:

• The following features have been removed:

— Archiver Tools are no longer supported. Users should refer to Database schema definitions to provide for their archiving needs.

— Support for DataDirect drivers has been removed.

— The DMZ Servlets feature that was supported in BusinessConnect 5.3.x is no longer supported.

TIBCO BusinessConnect Gateway Server is the only engine that can be installed and used to communicate with TIBCO BusinessConnect Interior Server.

— FTP transport over HTTP proxy is no longer supported.

— Single Server Mode is no longer supported.

— TAW is no longer supported.

— Charting is no longer supported.

— Asynchronous logging is not available.

— Trading Partner creation wizard that was previously in TIBCO Administrator UI is no longer available.

• The following functionality has been changed:

— Trading partners should start using the HTTP (HTTPS) URI to connect to BusinessConnect and its protocols as follows.

scheme://<host>:port/dmz/<protocol>

where ^scheme is ^http or ^https.

Older BusinessConnect 5.x URI is still supported, but is deprecated:

scheme://<host>:<port>/<protocol>

(18)

• The property bc.ssl.disableSessionCache now controls both outbound HTTPS and FTPS transports. Earlier release of TIBCO BusinessConnect had the property as bc.https.disableSessionCache, which was used only for outbound HTTPS. This property is available in System Settings>Activate Protocol Plug-ins and Properties>BC. Migration of this property from TIBCO BusinessConnect 5.3.3 to 6.0.0 would not occur.

• Server identities and credentials of HTTPS inbound public transport has been moved to Gateway> Gateway Service>HTTP Type>Private Key Credential.

Migration from TIBCO BusinessConnect 5.3.3 to 6.0.0 for these credentials would not occur.

• Migration of the default HTTP and FTP proxy from earlier releases to TIBCO BusinessConnect 6.0.0 would not occur.

• Migration of the Client Authentication Identity from BusinessConnect

>Business Agreements > protocol >Transports> Allowed Inbound Transports for Partner >FTPS from earlier releases to TIBCO BusinessConnect 6.0.0 would not occur.

• Migration of the Verification Certificate and Decryption Key from BusinessConnect>Business Agreements > protocol >Operation

Bindings>Partner can initiate>Document Security>Inbound Doc Exchange>

from earlier releases to TIBCO BusinessConnect 6.0.0 would not occur.

• Support for new security providers is available from this release. They are:

SUN JSSE provider (only on non-AIX platforms) and IBM provider (only on the AIX platform).

• Migration is not supported for the public transports HTTP, HTTPS, HTTPS_CA, FILE, and EMAIL that were available in earlier releases under Application Management of the deployment. Users must manually migrate these transports to the Gateway Services and enable them in the screen for the Inbound Public Transport Types.

• Migration is not supported for the FTP, FTPS, and SSHFTP Public Transport type checkbox from earlier releases in the deployment. Users must manually enable these transports at System Settings->Inbound Public Transport Type.

• Inbound Public Transports are moved to BusinessConnect> System Settings> Inbound Public Transport Type.

• EZComm Protocol and BusinessConnect Palette have been moved as a separate installation under TIBCO BusinessConnect Services Plug-in.

(19)

Changes in Functionality

|

⁷

• Support for the following platforms has been removed:

— AIX 5.2 and AIX 5.3

— HP-UX PA-RISC

— HP-UX 11i v2 IA-64/Itanium

— Red Hat Enterprise Linux 4.x

— SUSE Linux Enterprise 9

— Solaris 8 and Solaris 9 on Sparc

— 32-bit support is no longer available for AIX, Red Hat Enterprise Linux and SUSE Linux Enterprise Platforms

— Windows XP Professional (SP2+)

• Support for the following databases has been removed:

— DB2 8.2

— MySQL 5.0 and MySQL 5.1

— Microsoft SQL Server 2000

— Oracle 9i, 10g, 10gR2, Oracle RAC 9i, Oracle RAC 10g

— Weblogic drivers

• DMZ Deployment mode is removed

— TIBCO BusinessConnect 5.x supported DMZ Server deployment as well as the DMZ export. This is no longer supported and instead the new Gateway Server is provided, which is a stand-alone server managed from within TIBCO BusinessConnect UI.

(20)

Deprecated Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a

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

This section also lists features that are removed (if any).

Release 6.0.1

There are no deprecated features in this release.

Release 6.0.0

• BusinessConnect will no longer support TIBCO DataDirect JDBC Drivers starting with the release 6.0.0. If you have JDBC drivers configured from your earlier version BusinessConnect (5.3.x), then you must configure to use Vendor specific JDBC Drivers that are supported.

• Older BusinessConnect 5.x URI is still supported, but is deprecated:

scheme://<host>:<port>/<protocol>

Trading partners should start using the HTTP (HTTPS) URI to connect to BusinessConnect and its protocols as follows.

scheme://<host>:port/dmz/<protocol>, where ^scheme is ^http or ^https.

(21)

Compatibility and Migration

|

⁹

Compatibility and Migration

Upgrading to Release 6.0.1

TIBCO BusinessConnect release 6.0.1 can be installed only after release 6.0.0 has been installed.

To complete the upgrade after installation, do the following:

1. Log on to TIBCO Administrator and click on the BusinessConnect>Manage button. 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 button. Follow the instructions to complete the configuration store upgrade.

3. Verify that the installation has been upgraded.

Click on BusinessConnect>System Settings>Activated Protocol Plug-ins and Properties and ensure that the versions numbers for BusinessConnect Interior Server, BusinessConnect Remote Client Service, BusinessConnect Plug-in for FILE, BusinessConnect Plug-in for HTTP, and BusinessConnect Gateway Management are all pointing to the version 6.0.1.

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.

When performing migration, update all machines using these steps:

1. Uninstall TIBCO BusinessConnect 2. Restart TIBCO Hawk

3. Install the new version of TIBCO BusinessConnect

It is important to do these steps in a sequence one machine after another.

When migrating from TIBCO BusinessConnect version 6.0.0 to version 6.0.1, export the configuration store before starting migration.

(22)

Upgrading to Release 6.0.0

Migration of Trading Partner Management Data

TIBCO BusinessConnect migrates the Configuration Store data as follows:

• Participants

• Business Agreements

• Server configuration

• Public Process transports

• Private Process transports

• Public Process configuration except Advanced configuration

• Private Process configuration

Migration to TIBCO BusinessConnect 6.0.0

To migrate data from TIBCO BusinessConnect 5.3.3 to 6.0.0, perform these steps:

Task A Export the Old Configuration

You can upgrade your TIBCO BusinessConnect installation to the release 6.0.0 only from the release 5.3.3; migration from earlier releases such as 5.3.2, 5.3.1, 5.3.0, 5.2.x and 5.1.x. directly to 6.0.0 is not supported.

If migration from releases prior to 5.3.3 must be performed, you need to first migrate to TIBCO BusinessConnect 5.3.3, and then from version 5.3.3 to version 6.0.0.

While importing a configuration from TIBCO BusinessConnect version 5.3.3 to version 6.0.0, any configuration made in version 5.3.3 under Application Management> BusinessConnect> Configuration> BusinessConnect> Public Process Configuration> Transports will not be imported. Users will have to manually re-configure these settings in the TIBCO BusinessConnect GUI under BusinessConnect > Gateway> Gateway Services and BusinessConnect> System Settings> Inbound Public Transport Types.

JCE jars must be present in order to do a successful upgrade.

(23)

|

¹¹

1. Open the TIBCO BusinessConnect administration panel by selecting BusinessConnect> Manage Installation.

2. Select the Import/Export tab.

3. To protect the exported data, set a password by clicking on the link set..

4. Click on Export Configuration Data.

You will be prompted to confirm the file download and to specify the location where the file InstallationName^.csx will be saved.

The exported configuration is secure and can be imported in TIBCO BusinessConnect 6.0 as outlined in the following steps.

Task B Export the Domain Security Privileges Export the domain security privileges along with ACL.

You will need to perform this step in the following situations:

• TIBCO Runtime Agent or TIBCO Administrator are upgraded, or

• Data is being migrated from one domains to another

See TIBCO Runtime Agent Domain Utility User’s Guide for more information.

If data will reside in the same domain, proceed to Task C, Remove the Old Application.

Task C Remove the Old Application

1. Undeploy any existing TIBCO BusinessConnect application.

To perform undeployment, see TIBCO BusinessConnect Interior Server Administration, Chapter 5 Manage the Interior Server, Remove TIBCO BusinessConnect, Undeploy TIBCO BusinessConnect.

2. Remove TIBCO BusinessConnect

To remove the application, see TIBCO BusinessConnect Interior Server Administration, Chapter 5 Manage the Interior Server, Remove TIBCO BusinessConnect, Delete TIBCO BusinessConnect.

Task D Uninstall Existing Protocols and TIBCO BusinessConnect Stop and then restart TIBCO Administrator and TIBCO Hawk after uninstalling the protocols and TIBCO BusinessConnect application.

(24)

Task E Install and Configure TIBCO BusinessConnect 6.0.

Install TIBCO BusinessConnect 6.0 and appropriate protocols as follows:

1. Install TIBCO BusinessConnect 6.0 as described in TIBCO BusinessConnect Installation and Configuration, Installation.

2. Install the appropriate protocols. Refer to the protocol documentation for more information.

3. Configure the TIBCO BusinessConnect 6.0 installation by following the steps described in TIBCO BusinessConnect Installation and Configuration, Chapter 3, Configuration.

This will upgrade the configuration store database schemas.

4. Once the installation is configured, make sure that protocols are activated.

Task F Import the Previously Exported Domain Security Privileges

If the domain security privileges were exported as in Task B, Export the Domain Security Privileges, import them back.

See TIBCO Runtime Agent Domain Utility User’s Guide for more information.

Task G Import the Old Configuration to Trigger Migration To import the saved old installation, perform the following steps:

1. Open the TIBCO BusinessConnect administration panel by selecting BusinessConnect and click on Manage.

2. In the Management section, click on Import.

The Configuration Data Import screen appears.

3. Click ^change to specify where the file InstallationName^.csx was saved.

4. If the configuration was saved with a password, enter that password.

5. Click Import.

The Configuration Import dialog appears asking whether you want to import the component export data.

To perform migration from TIBCO BusinessConnect 5.3.3 to 6.0, the system must contain an identical set of protocols.

(25)

|

¹³

6. Click OK to continue with the import.

The migration process will start and import the Configuration Store data.

Task H Upgrade the Other Database Schemas

There are three other log and runtime databases schemas that require upgrading and that are used for different purposes:

• Audit Schemas Used to store audit information

• Non-Repudiation Schemas Used to store non-repudiation information

• Runtime Schemas Used by the runtime engine while it's running

The migration code will perform upgrade on schemas if all conditions are met:

• Database specified in TIBCO BusinessConnect 5.3.x configuration is up and running

• Username and password are identical

• Old database schemas are not removed

• The audit, non-repudiation, and runtime handles are not different from the configuration store handle

If any of these requirements are not met, create the schema tables manually.

To Manually Upgrade the Other Database Schema Tables

If the requirements for upgrading the other database schema tables have not being met, you should manually update tables for audit logs, non-repudiation logs, or runtime tables in the following way:

1. Select SystemSettings>Audit, Non-Repudiation and Runtime Database Configuration.

2. In the Target Table Type drop-down list, select the table type to upgrade:

— Audit Log

— Non Repudiation Log

— Runtime Data Store

Do not exit the screen while the data import is in progress. It is important to allow this process to be completed properly. If the data import is interrupted for any reason, the system may be left in an unpredictable state. In such case, you need to recreate the installation and to perform a new import.

(26)

3. After the text Drop and recreate the database tables, click Create.

— Click OK to drop and recreate all Audit, Non-Repudiation or Runtime tables. All user data will be deleted and the table will be recreated

Task I Finish the migration process This concludes the migration process.

(27)

Closed Issues

|

¹⁵

Closed Issues

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

Closed CR # Resolution

6.0.1 BC-7423 The field "From" for Credential Alert email can now be configured from the Credential Expiry Alert screen in BusinessConnect>System Settings.

6.0.0 BC-7169 Certain SSH connection related failures, such as SSH_FX_FAILURE signals, were not handled by BusinessConnect when it connects to SSH Servers.

This issue has been fixed.

6.0.0 BC-6218 TIBCO BusinessConnect Server now supports Microsoft SQL Server 2008 for checkpoint Database.

6.0.0 BC-6281 When BusinessConnect FTP-Get command is trying to get files from the partner’s FTP Server, it could occasionally stop pulling files and also polling used to stop. Users had to restart the BusinessConnect servers.

This issue has been fixed

6.0.0 BC-6213 The Read-only TIBCO Administrator users could not navigate the BusinessConnect application under Application Management in earlier release.

6.0.0 BC-6162 In earlier release, if BusinessConnect ConfigStore Management Interface (CMI) protocol was already installed before TIBCO BusinessConnect 5.3.3, the deployed ^.tra file never used to load the CMI protocol’s jar files since it was not included in the extended classpath.

6.0.0 BC-6156 When TIBCO BusinessConnect uses DB2 9.5, a result set closed

exception was thrown when running the Interior Server.

6.0.0 BC-5556 In earlier TIBCO BusinessConnect releases, there were certain indexes missing on BC_HIBERNATION and BC_LOGQUERYBIN tables. This would cause the searches to be slow and, in some cases, caused a deadlock.

(28)

6.0.0 BC-5554 In this release, query names saved in the TIBCO BusinessConnect log viewer can be longer than 15 characters.

6.0.0 BC-5549 Earlier releases of TIBCO BusinessConnect allowed the timeouts to be set only for Passive mode of FTP. As a result, if the BusinessConnect servers were connected to FTP Servers in Active mode and if the FTP Server did not return a reply, the connection would hold on other transactions as well.

With timeouts for Active mode, this issue is fixed

6.0.0 BC-5547 Successful return of the BusinessConnect ^AppManage commands on UNIX platforms now results in a ^returnCode of 0.

6.0.0 BC-5515 Adding and removing private process smart routing issue from TIBCO Administrator UI resulted in contention issues in a running

BusinessConnect server.

6.0.0 BC-5511 An SSH private key from the BusinessConnect host in previous releases could not be exported from the TIBCO Administrator UI.

6.0.0 BC-5488 In earlier releases, TIBCO BusinessConnect would throw an exception when an HTTP request with multiple cookies was received at the DMZ Server.

6.0.0 BC-5421 When setting up a trading partner with TIBCO BusinessConnect

installation that used the SSHFTP transport, it would always pic the HTTP proxy as the preferred proxy.

6.0.0 BC-4877 Business agreement import into new environment was not migrating the Scheduler information correctly for TIBCO BusinessConnect.

6.0.0 BC-4868 The field "From" used for the Credential Alert Email can now be configured from the Credential Expiry Alert screen in BusinessConnect> System Settings.

(29)

Closed Issues

|

¹⁷

6.0.0 BC-4866 Saved Query values were not updated in the log viewer's web search form in TIBCO BusinessConnect after Execute Saved Query action was

performed.

6.0.0 BC-4840 When the Advanced Search settings had some data that was searched in the log viewer, the values were not cleared if a user would close the screen and then open it again.

6.0.0 BC-4706 The Client IP address is now logged in the Gateway Server logs for the incoming HTTP requests for the TIBCO BusinessConnect Server.

6.0.0 BC-4666 When a BusinessConnect ^.tra file was set with a Java thread stack size from the deployment of TIBCO Administrator, the values were not set properly in the deployed^.tra file.

6.0.0 BC-4058 Earlier releases of TIBCO BusinessConnect servers did not allow multiple IP addresses or binding of a specific NIC address to be tied to a DMZ Server.

With the new architecture, TIBCO BusinessConnect Gateway Servers can be bound to a specific NIC address and can be tied to multiple IP addresses as well.

6.0.0 BC-4031 TIBCO BusinessConnect now retains the configurations that were previously deployed. Users do not need to re-enter the deployment configuration in the tab Application Management> BusinessConnect>

Configuration for redeployment.

6.0.0 BC-3341 Earlier releases of TIBCO BusinessConnect 5.x used to have references to JDBC parameters at the DMZ Server.

With TIBCO BusinessConnect Gateway server architecture changes, the JDBC parameters at DMZ Server are not saved any more in the TIBCO BusinessConnect Gateway server.

6.0.0 BC-3222 In earlier releases of TIBCO BusinessConnect, when GUI was resized the log viewer screen needed constant scrolling for the Execute button to show.

This issue is fixed with the new log viewer design.

(30)

5.3.3 BC-5528 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.

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

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.

(31)

Closed Issues

|

¹⁹

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 TIBCO 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.

5.3.0 1-9OB7K3 When the Send/Request activity from the TIBCO 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.

This has been fixed.

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.

(32)

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.

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-9C1MO3 The TIBCO BusinessConnect palette, using JMS transport, would serialize decimal values as floats in the lexical space instead of properly using xpath1.0.

(33)

Closed Issues

|

²¹

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^.trafile 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/m sh/network=<nic>;<multicast group>

tibco.clientVar.gatewayProperties/transports/Intercomponent/b mh/network=<nic>;<multicast group>

tibco.clientVar.gatewayProperties/transports/Intercomponent/d mz/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.

(34)

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

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

(35)

Closed Issues

|

²³

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-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).

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.

(36)

5.3.0 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-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-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-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.

(37)

Closed Issues

|

²⁵

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.

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.

(38)

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.

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:

...

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

...

Schema after migration to release 5.2:

...

<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 ^fixupXSDto migrator.bat (sh) in the directory

TIBCO_HOME/^bc/5.2/bin to prevent the migration utility from adding Closed CR # Resolution

(39)

Closed Issues

|

²⁷

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

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.

(40)

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. This has been fixed.

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.

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 Closed CR # Resolution

(41)

Closed Issues

|

²⁹

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.

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.

(42)

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.

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.

(43)

Closed Issues

|

³¹

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 honored for incoming FTP-Get messages;

for example, the message will be published as data if its size is below the skip content threshold.

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.

TIBCO BusinessConnect™ Release Notes