Supported flow patterns

Flow Manager supports creating your own patterns via the user interface or REST APIs as described on the Patterns page. Additionally, Flow Manager delivers a list of predefined patterns, that are created when you install or the first time you update the Flow Manager instance (available as of the Flow Manager October 20, 2021 release). 

Axway Repository patterns are obsolete if you are using a Flow Manager that was delivered since August 2021. 

Supported flow patterns

Using the Generate a pattern feature, you can create a pattern having the following characteristics:

  • Source: Partner, Application using Transfer CFT, or Application using Legacy SecureTransport
  • Target: Partner, Application using Transfer CFT, or Application using Legacy SecureTransport
  • Optionally, one or several relays: A relay can be any product available in Flow Manager (Transfer CFT, SecureTransport, or Legacy SecureTransport)
  • Protocols: For each flow, the available protocols are filtered to list protocols supported by each partner. For example, between SecureTransport and Transfer CFT, you can only select only PeSIT

Protocols supported by each flow type and direction for each protocol:

  • Transfer CFT 
    • PeSIT (PUSH/PULL)
  •  SecureTransport
    • SFTP (PUSH/PULL)
    • FTP (PUSH/PULL)
    • HTTP (PUSH/PULL)
    • PeSIT (PUSH/PULL)
    • S3 (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
    • FOLDER (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
    • SMB (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
  • Partner
    • SFTP (PUSH/PULL)
    • FTP (PUSH/PULL)
    • HTTP (PUSH/PULL)
    • PeSIT (PUSH/PULL)
    • S3 (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
    • FOLDER (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
    • SMB  (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
Legacy SecureTransport is deprecated and will be removed in the near future.

Depending on your needs, you can check: 

  • Subscribe source option if the source must be configured at the subscription level
  • Subscribe target option if the target must be configured at the subscription level

You must have at least the source, or the target checked as subscribable.

Predefined patterns

All predefined flow patterns delivered on Marketplace use the Legacy SecureTransport plugin, which is deprecated as of August 2012. Please generate new patterns in order to use the SecureTransport plugin or update to the latest Flow Manager delivery so you benefit from the new predefined patterns.

The predefined flow patterns follow a naming convention that illustrates their use. For example, the P0000_APP_CFT_PESIT_PUSH_CFT_APP flow between 2 applications is based on two Transfer CFTs using the PeSIT protocol in push mode. Flow Manager simplifies visualization with a graphical representation of the flow pattern.

For example, see 0013_APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER.

All flow patterns can create a flow with one partner, while you can use some patterns to create flows with multiple partners or multiple applications as the target. See One flow per multiple subscriptions. Additionally, you can use the patterns 1000, 1001, and 1002 to create subscriptions with groups of Transfer CFT applications. See Subscriptions with Transfer CFT application groups for details.

Flow Manager supports the following predefined flow patterns:

Flow pattern name

ID

APP_CFT_PESIT_PUSH_APP_CFT(*3) P0000
APP_CFT_PESIT_PUSH_ST_SFTP_PUSH_PARTNER(*3)(*4) P0001

PARTNER_SFTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0002

PARTNER_SFTP_PUSH_ST_SFTP_PUSH_PARTNER(*4) P0006
APP_CFT_PESIT_PUSH_CFT_PESIT_PUSH_CFT_APP(*3)(*4) P0009

APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER(*3)(*4)

P0013

APP_CFT_PESIT_PUSH_ST_FTP_PUSH_PARTNER(*3)(*4) P0014

APP_CFT_PESIT_PUSH_ST_HTTP_PULL_PARTNER(*3)(*4)

P0015

APP_CFT_PESIT_PUSH_ST_PESIT_PULL_CFT_APP(*3)(*4) P0017
APP_CFT_PESIT_PUSH_ST_PESIT_PULL_PARTNER(*3)(*4) P0019
APP_CFT_PESIT_PUSH_ST_PESIT_PUSH_CFT_APP(*1)(*3) P0020
APP_CFT_PESIT_PUSH_ST_PESIT_PUSH_PARTNER(*3)(*4) P0022

APP_CFT_PESIT_PUSH_ST_SFTP_PULL_PARTNER(*3)(*4)

P0023

PARTNER_FTP_PULL_ST_PESIT_PUSH_CFT_APP(*4) P0024
PARTNER_FTP_PUSH_ST_FTP_PULL_PARTNER(*3)(*4) P0026

PARTNER_FTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0030

PARTNER_HTTP_PUSH_ST_HTTP_PULL_PARTNER(*3)(*4) P0031
PARTNER_HTTP_PUSH_ST_HTTP_PUSH_PARTNER(*3)(*4) P0033

PARTNER_HTTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0035

PARTNER_SFTP_PULL_ST_PESIT_PUSH_CFT_APP P0039
PARTNER_SFTP_PULL_ST_SFTP_PUSH_PARTNER(*3) P0042
PARTNER_SFTP_PUSH_ST_SFTP_PULL_PARTNER(*3) P0043
APP_CFT_PESIT_PUSH_ST_APP P0046
APP_ST_PESIT_PUSH_CFT_APP(*3) P0047
APP_ST_SFTP_PUSH_PARTNER(*3) P0048

APP_ST_SFTP_PULL_PARTNER(*3)

P0049

APP_ST_FTP_PUSH_PARTNER(*3) P0050
APP_ST_PESIT_PUSH_PARTNER(*3) P0051
PARTNER_SFTP_PULL_ST_APP(*4) P0054
PARTNER_PESIT_PUSH_CFT_APP P0055
PARTNER_PESIT_PUSH_ST_APP P0056
PARTNER_PESIT_PULL_ST_APP P0059

PARTNER_SFTP_PUSH_ST_APP

P0062

APP_ST_PESIT_PULL_PARTNER(*3) P0066
APP_ST_FTP_PULL_PARTNER(*3) P0076
APP_CFT_PESIT_PULL_CFT_APP(*3) P0077
APP_CFT_PESIT_PUSH_PARTNER(*3) P0078
APP_CFT_PESIT_PULL_ST_SFTP_PUSH_PARTNER(*3) P0086
0096_PARTNER_AS2_PUSH_ST_APP P0096
0097_APP_ST_AS2_PUSH_PARTNER P0097
PARTNER_FTP_PUSH_ST_SFTP_PULL_PARTNER(*3) P0112
PARTNER_SFTP_PUSH_ST_HTTP_PULL_PARTNER(*3) P0120
PARTNER_SFTP_PUSH_ST_PESIT_PUSH_ST_SFTP_PUSH_PARTNER P0300
PARTNER_SFTP_PUSH_CFT_PESIT_PUSH_CFT_PESIT_PUSH_APP/CFT P0400
APP_CFT_PESIT_PUSH_CFT_APP_GROUP P1000
GROUP_APP_CFT_PESIT_PUSH_CFT_APP P1001
GROUP_APP_CFT_PESIT_PUSH_CFT_APP P1002
APP_ST_SFTP__PUSH_PARTNER(*4)(*3) P1048
APP_ST_SFTP__PULL_PARTNER(*4)(*3) P1049
PARTNER_SFTP_PULL_ST_APP(*4)(*3) P1054
PARTNER_SFTP_PUSH_ST_APP(*4)(*3) P1062

(*3) When using these patterns, you can subscribe multiple targets to the same flow (broadcast/collect use cases). See One flow per multiple target subscriptions. 

(*4) These patterns support SecureTransport S3 storage definition. 

For an example of how to configure a template for a specific pattern, see Sample: P0013_APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER.

Changelog

  • July '21 Update
    • Added support for patterns with 2 relays 0300
  • June '21 Update
    • Added support for patterns 0096 and 0097 with AS2
  • May '21 Update
    • Added support for pattern 0006
  • March '21 Update:
    • Support for advanced expressions when SecureTransport pulls files.
  • February'21 Update:
    • Support for a SecureTransport S3 connector in the patterns1048, 1049, 1054, and 1062.
  • December'20 Update:
    • Added support for PGP processing steps in all flow patterns with SecureTransport.
    • Reviewed labels, descriptions, and sections for Transfer CFT and SecureTransport specific fields. 
  • October'20 Update: 
    • Added support for processing steps in all flow patterns with SecureTransport (without PGP).
    • Fixed the flow link field: set the default value to empty.


Flow Manager supports creating your own patterns via its user interface or REST APIs. See the Pattern > Generate for details. Additionally, Flow Manager delivers a list of predefined patterns, and you can download MFT flow patterns from the Axway Amplify Repository.

Flow Manager supports creating your own patterns via the user interface or REST APIs as described on the Patterns page. Additionally, Flow Manager delivers a list of predefined patterns, that are created when you install or the first time you update the Flow Manager instance (available as of the Flow Manager October 20, 2021 release). 

Axway Amplify Repository patterns are obsolete if you are using a Flow Manager that was delivered since August 2021. 

Supported flow patterns

Using the Generate a pattern feature, you can create a pattern having the following characteristics:

  • Source: Partner, Application using Transfer CFT, or Application using Legacy SecureTransport
  • Target: Partner, Application using Transfer CFT, or Application using Legacy SecureTransport
  • Optionally, one or several relays: A relay can be any product available in Flow Manager (Transfer CFT, SecureTransport, or Legacy SecureTransport)
  • Protocols: For each flow, the available protocols are filtered to list protocols supported by each partner. For example, between SecureTransport and Transfer CFT, you can only select only PeSIT

Protocols supported by each flow type and direction for each protocol:

  • Transfer CFT 
    • PeSIT (PUSH/PULL)
  •  SecureTransport
    • SFTP (PUSH/PULL)
    • FTP (PUSH/PULL)
    • HTTP (PUSH/PULL)
    • PeSIT (PUSH/PULL)
    • S3 (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
    • FOLDER (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
    • SMB (PULL when the protocol is set after the source, PUSH when the protocol is set before the target) 
  • Partner
    • SFTP (PUSH/PULL)
    • FTP (PUSH/PULL)
    • HTTP (PUSH/PULL)
    • PeSIT (PUSH/PULL)
    • S3 (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
    • FOLDER (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
    • SMB  (PULL when Partner is set as the source, PUSH when Partner is set as the target) 
Legacy SecureTransport is deprecated and will be removed in the near future.

Depending on your needs, you can check: 

  • Subscribe source option if the source must be configured at the subscription level
  • Subscribe target option if the target must be configured at the subscription level

You must have at least the source, or the target checked as subscribable.

Predefined patterns

All predefined flow patterns delivered on Marketplace use the Legacy SecureTransport plugin, which is deprecated as of August 2012. Please generate new patterns in order to use the SecureTransport plugin or update to the latest Flow Manager delivery so you benefit from the new predefined patterns.

The predefined flow patterns follow a naming convention that illustrates their use. For example, the P0000_APP_CFT_PESIT_PUSH_CFT_APP flow between 2 applications is based on two Transfer CFTs using the PeSIT protocol in push mode. Flow Manager simplifies visualization with a graphical representation of the flow pattern.

For example, see 0013_APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER.

All flow patterns can create a flow with one partner, while you can use some patterns to create flows with multiple partners or multiple applications as the target. See One flow per multiple subscriptions. Additionally, you can use the patterns 1000, 1001, and 1002 to create subscriptions with groups of Transfer CFT applications. See Subscriptions with Transfer CFT application groups for details.

Flow Manager supports the following predefined flow patterns:

Flow pattern name

ID

APP_CFT_PESIT_PUSH_APP_CFT(*3) P0000
APP_CFT_PESIT_PUSH_ST_SFTP_PUSH_PARTNER(*3)(*4) P0001

PARTNER_SFTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0002

PARTNER_SFTP_PUSH_ST_SFTP_PUSH_PARTNER(*4) P0006
APP_CFT_PESIT_PUSH_CFT_PESIT_PUSH_CFT_APP(*3)(*4) P0009

APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER(*3)(*4)

P0013

APP_CFT_PESIT_PUSH_ST_FTP_PUSH_PARTNER(*3)(*4) P0014

APP_CFT_PESIT_PUSH_ST_HTTP_PULL_PARTNER(*3)(*4)

P0015

APP_CFT_PESIT_PUSH_ST_PESIT_PULL_CFT_APP(*3)(*4) P0017
APP_CFT_PESIT_PUSH_ST_PESIT_PULL_PARTNER(*3)(*4) P0019
APP_CFT_PESIT_PUSH_ST_PESIT_PUSH_CFT_APP(*1)(*3) P0020
APP_CFT_PESIT_PUSH_ST_PESIT_PUSH_PARTNER(*3)(*4) P0022

APP_CFT_PESIT_PUSH_ST_SFTP_PULL_PARTNER(*3)(*4)

P0023

PARTNER_FTP_PULL_ST_PESIT_PUSH_CFT_APP(*4) P0024
PARTNER_FTP_PUSH_ST_FTP_PULL_PARTNER(*3)(*4) P0026

PARTNER_FTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0030

PARTNER_HTTP_PUSH_ST_HTTP_PULL_PARTNER(*3)(*4) P0031
PARTNER_HTTP_PUSH_ST_HTTP_PUSH_PARTNER(*3)(*4) P0033

PARTNER_HTTP_PUSH_ST_PESIT_PUSH_CFT_APP(*4)

P0035

PARTNER_SFTP_PULL_ST_PESIT_PUSH_CFT_APP P0039
PARTNER_SFTP_PULL_ST_SFTP_PUSH_PARTNER(*3) P0042
PARTNER_SFTP_PUSH_ST_SFTP_PULL_PARTNER(*3) P0043
APP_CFT_PESIT_PUSH_ST_APP P0046
APP_ST_PESIT_PUSH_CFT_APP(*3) P0047
APP_ST_SFTP_PUSH_PARTNER(*3) P0048

APP_ST_SFTP_PULL_PARTNER(*3)

P0049

APP_ST_FTP_PUSH_PARTNER(*3) P0050
APP_ST_PESIT_PUSH_PARTNER(*3) P0051
PARTNER_SFTP_PULL_ST_APP(*4) P0054
PARTNER_PESIT_PUSH_CFT_APP P0055
PARTNER_PESIT_PUSH_ST_APP P0056
PARTNER_PESIT_PULL_ST_APP P0059

PARTNER_SFTP_PUSH_ST_APP

P0062

APP_ST_PESIT_PULL_PARTNER(*3) P0066
APP_ST_FTP_PULL_PARTNER(*3) P0076
APP_CFT_PESIT_PULL_CFT_APP(*3) P0077
APP_CFT_PESIT_PUSH_PARTNER(*3) P0078
APP_CFT_PESIT_PULL_ST_SFTP_PUSH_PARTNER(*3) P0086
0096_PARTNER_AS2_PUSH_ST_APP P0096
0097_APP_ST_AS2_PUSH_PARTNER P0097
PARTNER_FTP_PUSH_ST_SFTP_PULL_PARTNER(*3) P0112
PARTNER_SFTP_PUSH_ST_HTTP_PULL_PARTNER(*3) P0120
PARTNER_SFTP_PUSH_ST_PESIT_PUSH_ST_SFTP_PUSH_PARTNER P0300
PARTNER_SFTP_PUSH_CFT_PESIT_PUSH_CFT_PESIT_PUSH_APP/CFT P0400
APP_CFT_PESIT_PUSH_CFT_APP_GROUP P1000
GROUP_APP_CFT_PESIT_PUSH_CFT_APP P1001
GROUP_APP_CFT_PESIT_PUSH_CFT_APP P1002
APP_ST_SFTP__PUSH_PARTNER(*4)(*3) P1048
APP_ST_SFTP__PULL_PARTNER(*4)(*3) P1049
PARTNER_SFTP_PULL_ST_APP(*4)(*3) P1054
PARTNER_SFTP_PUSH_ST_APP(*4)(*3) P1062

(*3) When using these patterns, you can subscribe multiple targets to the same flow (broadcast/collect use cases). See One flow per multiple target subscriptions. 

(*4) These patterns support SecureTransport S3 storage definition. 

For an example of how to configure a template for a specific pattern, see Sample: P0013_APP_CFT_PESIT_PUSH_ST_FTP_PULL_PARTNER.

Changelog

  • July '21 Update
    • Added support for patterns with 2 relays 0300
  • June '21 Update
    • Added support for patterns 0096 and 0097 with AS2
  • May '21 Update
    • Added support for pattern 0006
  • March '21 Update:
    • Support for advanced expressions when SecureTransport pulls files.
  • February'21 Update:
    • Support for a SecureTransport S3 connector in the patterns1048, 1049, 1054, and 1062.
  • December'20 Update:
    • Added support for PGP processing steps in all flow patterns with SecureTransport.
    • Reviewed labels, descriptions, and sections for Transfer CFT and SecureTransport specific fields. 
  • October'20 Update: 
    • Added support for processing steps in all flow patterns with SecureTransport (without PGP).
    • Fixed the flow link field: set the default value to empty.


Flow Manager supports creating your own patterns via its user interface or REST APIs. See the Pattern > Generate for details. Additionally, Flow Manager delivers a list of predefined patterns, and you can download MFT flow patterns from the Axway Amplify Repository.

Related Links