Preserving inbound original filenames when using the EZComm protocol.

Preserving inbound original filenames when using the EZComm protocol.

book

Article ID: KB0093016

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect Services Plug-in -
Not Applicable -

Description

Description:

When BusinessConnect processes an inbound AS2 message using HTTPS and sends it to the private process, the original filename is not preserved. It is sending the filename as "smime.p7m" to a private process as seen in the Receive Request/Notification BC receiver activity and subsequent processes.


Issue/Introduction

Preserving inbound original filenames when using the EZComm protocol.

Resolution

Under the trading partner EZComm protocol properties, there is a checkbox named "Allow override of filename via HTTP parameter".  If this property is checked, BC will use the filename in the HTTP header as the value to pass to the private process. If the AS2 message is encrypted and signed, the filename will be embedded in the payload which means that this property must be unchecked for the correct filename to go to the private process.  

Additional Information

TIBCO BusinessConnect Services Plugin User's Guide