TIBCO BusinessConnect EDI Protocol powered by Instream 6.7.0 hotfix 1 has been released.

Products	Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream	-
Not Applicable	-

Description

Description:
TIBCO BusinessConnect EDI Protocol powered by Instream 6.7.0 hotfix 1 has been released.

You can download this Hot Fix from the TIBCO Product Support server using your TIBCO Support Central (TSC) username (email address) and password, at

mft.tibco.com

mft.tibco.com supports FTP, HTTPS, and SFTP.

Once you have successfully logged into the server, you will find the hotfix packages under

/AvailableDownloads/BusinessConnect/EDI/6.7.0/hotfix-01

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 6.7.0_HF-001 (This Release)

EDIP-2515

When no Business Agreement existed between the default host and trading partner,

if an inbound request was sent to the non-default host and Business Agreement

existed between this non-default host and trading partner, TIBCO BusinessConnect

EDI Protocol powered by Instream threw an exception for inbound request.

EDIP-2512

TIBCO BusinessConnect EDI Protocol powered by Instream added extra characters

to the beginning of the value of "transactionBody" property in the

RESPONDER.REQUEST message if the size of inbound request was greater than the

value of "Threshold to Use File-based Storage Prior to EDI Processing".

EDIP-2509

TIBCO BusinessConnect EDI Protocol powered by Instream failed to validate non

UTF-8/UTF-16 inbound request that used extended ASCII character as delimiters.

This issue is fixed by adding the following boolean properties to BusinessConnect >

System Settings > Activated Protocol Plug-ins and Properties > tibEDI.

- To make this solution take effect for only one trading partner:

edi.skip.default.encoding.conversion.<TP name>=true

- To make this solution take effect for all trading partners:

edi.skip.default.encoding.conversion=true

EDIP-2508

When TIBCO BusinessConnect EDI Protocol powered by Instream generated logging

files for inbound and outbound request, the file name always contained the

engine name that occasionally caused the file name too long.

By adding the following boolean property to BusinessConnect > System Settings >

Activated Protocol Plug-ins and Properties > tibEDI, TIBCO BusinessConnect EDI

Protocol powered by Instream does not append the engine name to the logging

file name.

edi.add.engine.name.to.logging.file=false

EDIP-2507

TIBCO BusinessConnect EDI Protocol powered by Instream only showed the User Key

value in Audit log and did not show the User Key name.

By adding the following boolean property to BusinessConnect > System Settings >

Activated Protocol Plug-ins and Properties > tibEDI, TIBCO BusinessConnect EDI

Protocol powered by Instream shows both the User Key name and value in Audit logs.

edi.append.UserKeyName.to.audit.log=true

EDIP-2506

When EDI to XML conversion was disabled, if inbound interchanges contained

multiple transactions, TIBCO BusinessConnect EDI Protocol powered by

Instream did not log Raw EDI Segments to File for the transaction level.

EDIP-2488

TIBCO BusinessConnect EDI Protocol powered by Instream generated TA1

acknowledgements with the value of the IEA_01 element being "1".

By adding following boolean properties to BusinessConnect > System Settings >

Activated Protocol Plug-ins and Properties > tibEDI, TIBCO BusinessConnect EDI

Protocol powered by Instream generates TA1 acknowledgements with the value of

the IEA_01 element being "0".

- To make the solution take effect for only one trading partner:

edi.x12.enable.adjustIEACountForTA1.<TP Name>=false

- To make the solution take effect for all trading partners:

edi.x12.enable.adjustIEACountForTA1=false

EDIP-2487

TIBCO BusinessConnect EDI Protocol powered by Instream did not dynamically load

APF files according to the values of the GS02 and GS03 elements.

By adding corresponding lines to the GS0203_guidelines.map file in the

{BC_HOME}/protocols/tibedi/config directory, TIBCO BusinessConnect EDI Protocol

powered by Instream can dynamically load APF files.

The format of added lines are as follows:

APF_<original name>_<GS02>_<GS03> = /<original name>_GS0203_guidelines/<original name>_<GS02>_<GS03>.apf

APF_<original name>_<GS02> = /<original name>_GS0203_guidelines/<original name>_<GS02>.apf

APF_<original name>_<GS03> = /<original name>_GS0203_guidelines/<original name>_<GS03>.apf

For example, the original name is "X12_5010_850.apf", the GS02 element is

"Application Sen", and the GS03 element is "Application Rec", the added lines

are as follows:

APF_X12_5010_850_Application_Sen_Application_Rec = /X12_5010_850_GS0203_guidelines/X12_5010_850_Application_Sen_Application_Rec.apf

APF_X12_5010_850_Application_Sen = /X12_5010_850_GS0203_guidelines/X12_5010_850_Application_Sen.apf

APF_X12_5010_850_Application_Rec = /X12_5010_850_GS0203_guidelines/X12_5010_850_Application_Rec.apf

EDIP-2476

TIBCO BusinessConnect EDI Protocol powered by Instream did not support private

processes to send EDI format transactions as Sync responses. This issue is

fixed. Both XML and EDI format transactions can be sent from private process

as Sync response.

EDIP-2458

When files staged in "Inbox" were accessed by Gateway Services such as SSHFTP,

FTPS, PartnerExpress, and so on, the custom file names generated by TIBCO

BusinessConnect EDI Protocol powered by Instream were not exposed to these

Gateway Services.

Issue/Introduction

TIBCO BusinessConnect EDI Protocol powered by Instream 6.7.0 hotfix 1 has been released.

Environment

BusinessConnect EDI Protocol powered by Instream 6.7.0all platforms

Welcome to "KB Articles"