Outbound File Transport

You can configure File outbound transport to perform these tasks:

  • Rename outbound files according to a mask.
  • Manage file processing using scripts

To make the outbound File transport available for a trading partner, you have to perform the following tasks:

  1. Configuring Outbound File Transport for a Partner
  2. Select this transport for the partner in the Primary Transport field on the Business Agreements > Edit Configurations > Bind Protocol > protocol configuration > Transports.

Configuring Outbound File Transport for a Partner

  1. To configure outbound File transport for a trading partner, perform the following steps:
  2. On Partner Management tile, click Partners.
  3. On the Partners page, click any partner you wish to configure this transport.
  4. In the Edit Partner window, on the Protocol tab, click Edit Configurations for any protocol you wish to configure.
  5. On the protocol configurations page, click add icon.
  6. In the Add Transport dialog box, enter required information in the following fields:
Outbound File Transport
Field Description
Transport Name An identifier for these transport settings.
URL The directory in which the outbound files are to be stored.
File Processing The mechanism for deciding how files are sent to the trading partner. There are two choices:
  • File Mask Choose this option to control file renaming and enter a mask in the File Mask field.
  • Script Choose Script for processing files and specify a script in the Scripts field.
Output File Mask The mask to control file naming. The value entered in the field is used as the name of the file.

For more information, see See Supported File Mask Options .

If no value is entered, Business Connect will generate the outbound request in a pre-defined format.

Scripts Specify a File script. See Appendix B, Scripts for information on how to write scripts and File Specification Dialog for information on how to upload a script.
Scripts Engine The scripts engine that you want to use to execute custom scripts.

You can select one of the items from the list:

  • FESI
  • Nashorn

Note: The FESI EcmaScript engine originally supported by TIBCO BusinessConnect is out of support by the vendor. It is good practice to use the Nashorn script engine as a substitute because the Nashorn script engine is roughly compatible with the FESI EcmaScript engine

Note: On Kubernetes, NFS installation is mandatory, and are required to configure the mount path in mount_path property of deployment.configurations file in config folder of the deployment package.