A trading partner is generally defined as a remote service that you want to regularly exchange data with. The only exception is the Local Directory trading partner, which is used to denote a local directory. Trading partner information may be used in triggers when performing scheduled or event based file transfers. The purpose of the trading partner module is to centralize remote host credentials so that they can be reused within trigger actions. Used properly, if a remote host changes their hostname or credentials you only need to update the trading partner details rather than update all trigger actions that depend on this host.
To add a trading partner select the Trading Partners node within JSCAPE MFT Server Manager and click on the Add button.
Figure 142
Select a file transfer protocol for this trading partner.
Figure 237
JSCAPE MFT Server currently supports the following trading partner protocols:
| • | AFTP |
| • | Agent |
| • | AS2 |
| • | Amazon S3 |
| • | Amazon AWS |
| • | Box |
| • | Dropbox |
| • | Google Cloud |
| • | Google Cloud Storage |
| • | Google Drive |
| • | IBM Cloud |
| • | Local Directory |
| • | Microsoft Azure File Service |
| • | Microsoft Azure Blob Service |
| • | Microsoft Azure Data Lake |
| • | FTP |
| • | FTPS implicit |
| • | FPTS explicit |
| • | IMAP |
| • | OFTP |
| • | POP3 |
| • | JSCAPE REST |
| • | SFTP/SCP |
| • | SMB |
| • | SMTP |
| • | WebDAV |
| • | TFTP |
Enter pertinent details for this trading partner.
Figure 143
Basic
Name - A unique name to assign to this trading partner.
Company - The name of the company that this trading partner represents.
E-mail - The primary email address for this trading partner. This field should be filled up if what you're adding is an AS2 trading partner and you wish to use the Email Specification feature.
Connection
Details vary based on the protocol selected.
Tags
Tags - Use tags to limit which administrators have access to this trading partner.
Using trading partners in triggers
There are a number of file transfer related trigger actions that can use certain trading partners in their work. These include the following actions, to mention a few.
Trading Partner Create Directory
Trading Partner Delete Directory
Trading Partner Delete File
Trading Partner Directory Download
Trading Partner Directory Upload
Trading Partner File Download
Trading Partner File Upload
Trading Partner Rename File
Note that, not all trading partners can be used in file transfer-related trigger actions. The following trading partners can be used in file transfer-related trigger actions:
| • | AFTP |
| • | AS2 |
| • | Amazon S3 |
| • | Box |
| • | DropBox |
| • | Google Cloud Storage |
| • | IBM Cloud |
| • | Microsoft Azure File Service |
| • | Microsoft Azure Blob Service |
| • | Microsoft Azure Data Lake |
| • | FTP |
| • | FTPS Implicit |
| • | FTPS Explicit |
| • | REST |
| • | SFTP/SCP |
| • | SMB |
| • | WebDAV |
| • | TFTP |
Similarly, there are other trigger actions that only support other trading partner protocols. For example,
Trading Partner Check Email trigger action will only work with:
| • | IMAP |
| • | POP3 |
Trading Partner Send Email trigger action will only work with:
| • | SMTP |
Trading Partner OFTP Exchange and Trading Partner OFTP File Upload trigger actions will only work with:
| • | OFTP |
Amazon SNS Publish Message, Amazon SNS Publish SMS Message, and Amazon SQS Send Message trigger actions will only work with:
| • | Amazon AWS |
Trading partners that are not supported by a trigger won't appear in the list of trading partners (if there is any) for that particular trigger
See also