Outbox and inbox virtual folder structure is not matching when using the FTPS Server and SSH Server plugins with BusinessConnect.

Outbox and inbox virtual folder structure is not matching when using the FTPS Server and SSH Server plugins with BusinessConnect.

book

Article ID: KB0087777

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
Description:
============
When using the SSH Server or FTPS Server plugings for BusinessConnect (BC), the operation folder structure is not seen in outbox than appears in the inbox.  The inbox folder structure mimics the operation definition in the Operations Editor.

Environment:
============
TIBCO BusinessConnect 6.x
TIBCO BusinessConnect EDI Protocol powered by Instream 6.x

Cause:
======
With EDI transasctions, BC does need the full operation folder structure for inbound (outbox) transactions. It just wants to know what the protocol is. BC will analyze the inbound transaction to identify the operation. One inbound transaction may include many different types of X12 or EDIFACT transactions.  

BC is designed to use the folder “/X12/EDI/Inbound/Interchange” operation to receive all inbound transactions. This is the reason we do nott display other operations in “outbox”.

Resolution:
===========
Trading Partners(FTP clients) should upload files into /outbox/X12/EDI/Inbound/Interchange for sending inbound the transaction to BC.

Issue/Introduction

Outbox and inbox virtual folder structure is not matching when using the FTPS Server and SSH Server plugins with BusinessConnect.