SecureTransport as target in flows

When used within an application as the target in a flow, SecureTransport pushes the files received, directly from partners or other relays, to a directory where an internal application has access. SecureTransport can create the directory or rename received files.

You define receive, file processing and send properties in flows where SecureTransport is the receiver.

  • Receive properties depend on the exchange protocol and direction between SecureTransport and the preceding participant in the flow.
  • File processing properties are configured the same as when SecureTransport is a relay.
  • Send properties have information about the directory where files are pushed and settings on possible post-sending actions.

When using flow patterns where SecureTransport is the target, you can have only one application linked to the target SecureTransport. That is, you cannot have multiple applications as the target with SecureTransport.

Business scenario

The following scenario describes a one-to-one flow pattern where SecureTransport is the target. SecureTransport receives from a partner an invoice that must be moved to a folder the invoice application can access.

Picture of a a flow where SecureTransport is the target

Flow definition

  1. Add the invoice application and associate it with SecureTransport.
  2. Add a flow, using the partner as the source and the application invoice application as the target.
  3. Configure SFTP as the protocol between the source and target.
  4. Edit the flow properties for the target.
  5. Save and deploy the flow.

Storage types

Central Governance with SecureTransport supports two types of storage. Folder monitoring is supported by default, whereas SMB, S3, and Syncplicity require an installed connector as described in the following sections.

For information on SecureTransport S3, SMB, and Syncplicity connector fields in flow descriptions, see: Source fields in flows and Target fields in flows.

For SecureTransport corresponding fields, see: Storage for SecureTransport as source in flow and Storage for SecureTransport as target in flow.

Folder monitoring

Use folder monitoring as storage type to create a transfer site on the SecureTransport that push files to a local folder.

SMB

Use Server Message Block (SMB) as storage type to create a transfer site on the SecureTransport that push files to shared files and directories.

To use SMB with SecureTransport, you must first install the SMB Connector on SecureTransport. The SMB Connector and documentation are available at  AMPLIFY Repository > SecureTransport > SMB Connector for Axway SecureTransport.

Central Governance provides support for two versions of SMB, depending on the SecureTransport version. To use SMB v1.0 or 1.2 as local storage, you must install SMB on Central Governance. The SMB installation files and documentation are available at  AMPLIFY Repository > Central Governance > SMBv2.

S3

The Amazon S3 Connector enables SecureTransport to exchange files with Amazon Cloud S3 Buckets or custom S3 provider endpoints. It is deployed as a plug-in to an existing SecureTransport installation, and adds a new Transfer Site named "S3" to the list of available Transfer Sites.

To use S3 with SecureTransport, you must first install the S3 Connector on SecureTransport. The S3 Connector and documentation are available at  AMPLIFY Repository > SecureTransport > S3 Connector for Axway SecureTransport.

Central Governance supports S3 versions v1.0 or 1.5 as local storage installed on Central Governance. The S3 installation files and documentation are available at  AMPLIFY Repository > Central Governance > S3.

Syncplicity

The Syncplicity Connector enables SecureTransport to exchange files using server-initiated transfers with the Syncplicity cloud platform. It is deployed as a plug-in to an existing ST installation and adds a new Transfer Site named "Syncplicity" to the list of available Transfer Sites for user accounts. With this connector, SecureTransport operates as an Application on behalf of managed Syncplicity Account(s).

To use Syncplicity with SecureTransport, you must first install the Syncplicity Connector on SecureTransport. The Syncplicity Connector and documentation are available at  AMPLIFY Repository > SecureTransport > Syncplicity Connector for Axway SecureTransport.

Central Governance provides support for two versions of Syncplicity. To use Syncplicity v1.0 or 1.5 as local storage, you must install Syncplicity on Central Governance. The Syncplicity installation files and documentation are available at  AMPLIFY Repository > Central Governance > Syncplicity.

Azure

The Azure Blob Storage Connector enables SecureTransport to exchange files using server-initiated transfers with the Azure Cloud Blob Storage service, and is deployed as a Transfer Site plug-in for existing SecureTransport installations. Once deployed, a new protocol, Azure Blob Storage, is available in the Add New Transfer Site page for User Accounts. When using this connector, SecureTransport operates as an Application on behalf of a managed Azure Storage Account, or anonymously if connecting to a public Azure container.

Central Governance provides support for Azure Blob Storage using the v1.3 connector. To use Azure as local storage, install Azure on Central Governance. The Azure installation files and documentation are available at AMPLIFY Repository > Central Governance > Azure.

 

Central Governance | Document Directory

Related Links