Transfer CFT 3.6 Users Guide Save PDF Selected topic Selected topic and subtopics All content About governance services In this guide, flow refers to the complete interaction between the source and target applications, more specifically Transfer CFT systems, to enable data exchanges between business applications or partners. Managed File Transfer services Managed File Transfer services, using a blend of Axway products, can centralize flow definition and configuration deployment for Transfer CFT (file transfer) engines. You can use Central Governance in your MFT architecture to easily create and deploy flows. You then trigger your flows at the system level. Note Connectivity may include connection to other or third-party products that are outside of the MFT reference solution. Additional documentation AMPLIFY Supported Platforms Central Governance documentation Flow Manager documentation Governance exchanges The following types of exchanges occur between Central Governance or Flow Manager and the managed Transfer CFTs: Flow management Certificate management Configuration management Update management See Exchanges with Central Governance for more information. Overview and practical considerations Begin by planning your MFT architecture and deployment strategy. After installing Central Governance or Flow Manager, the following steps occur: In the Transfer CFT installation select the Central Governance connectivity option After installing, start the Copilot server (the Transfer CFT server can be running, but this is optional) Registration occurs automatically on Copilot start up From Central Governance or Flow Manager start the Transfer CFT(s) If you migrated or upgraded, you may want to reference the following sections: Manually activate Central Governance connectivityParameter mapping between products Feature support and management Transfer CFTs running under Central Governance or Flow Manager can manage or have support for the following features. Feature Manage using Flow Manager or Central Governance Supported but not configurable using Central Governance or Flow Manager Folder monitoring yes yes Multi-node architecture no yes CRONJOB yes yes Exits no yes Network features IPv6 yes yes pTCP (UNIX/Windows only) yes yes UDT (UNIX/Windows only) yes yes SOCKS no yes Heartbeat embedded yes Interoperability Secure Relay no yes TrustedFile (UNIX/Windows/and z/OS) no yes PassPort AM embedded no (*) PassPort PS no yes Sentinel embedded yes Composer no no Protocols PeSIT yes yes ODETTE no yes SFTP (UNIX, Windows) no yes * If you perform a migration or upgrade from a previous version, you must migrate your PassPort AM. Legacy flows Legacy flows refer to former flow definitions available in migrated Transfer CFT systems. Central Governance or Flow Manager can manage the following use cases: Via the Central Governance or Flow Manager user interface, you can add and manage partners, and use send and receive templates for a given Transfer CFT. You can migrate Transfer CFT flow definitions to the Central Governance or Flow Manager flow-management process. Related Links
About governance services In this guide, flow refers to the complete interaction between the source and target applications, more specifically Transfer CFT systems, to enable data exchanges between business applications or partners. Managed File Transfer services Managed File Transfer services, using a blend of Axway products, can centralize flow definition and configuration deployment for Transfer CFT (file transfer) engines. You can use Central Governance in your MFT architecture to easily create and deploy flows. You then trigger your flows at the system level. Note Connectivity may include connection to other or third-party products that are outside of the MFT reference solution. Additional documentation AMPLIFY Supported Platforms Central Governance documentation Flow Manager documentation Governance exchanges The following types of exchanges occur between Central Governance or Flow Manager and the managed Transfer CFTs: Flow management Certificate management Configuration management Update management See Exchanges with Central Governance for more information. Overview and practical considerations Begin by planning your MFT architecture and deployment strategy. After installing Central Governance or Flow Manager, the following steps occur: In the Transfer CFT installation select the Central Governance connectivity option After installing, start the Copilot server (the Transfer CFT server can be running, but this is optional) Registration occurs automatically on Copilot start up From Central Governance or Flow Manager start the Transfer CFT(s) If you migrated or upgraded, you may want to reference the following sections: Manually activate Central Governance connectivityParameter mapping between products Feature support and management Transfer CFTs running under Central Governance or Flow Manager can manage or have support for the following features. Feature Manage using Flow Manager or Central Governance Supported but not configurable using Central Governance or Flow Manager Folder monitoring yes yes Multi-node architecture no yes CRONJOB yes yes Exits no yes Network features IPv6 yes yes pTCP (UNIX/Windows only) yes yes UDT (UNIX/Windows only) yes yes SOCKS no yes Heartbeat embedded yes Interoperability Secure Relay no yes TrustedFile (UNIX/Windows/and z/OS) no yes PassPort AM embedded no (*) PassPort PS no yes Sentinel embedded yes Composer no no Protocols PeSIT yes yes ODETTE no yes SFTP (UNIX, Windows) no yes * If you perform a migration or upgrade from a previous version, you must migrate your PassPort AM. Legacy flows Legacy flows refer to former flow definitions available in migrated Transfer CFT systems. Central Governance or Flow Manager can manage the following use cases: Via the Central Governance or Flow Manager user interface, you can add and manage partners, and use send and receive templates for a given Transfer CFT. You can migrate Transfer CFT flow definitions to the Central Governance or Flow Manager flow-management process.
About governance services In this guide, flow refers to the complete interaction between the source and target applications, more specifically Transfer CFT systems, to enable data exchanges between business applications or partners. Managed File Transfer services Managed File Transfer services, using a blend of Axway products, can centralize flow definition and configuration deployment for Transfer CFT (file transfer) engines. You can use Central Governance in your MFT architecture to easily create and deploy flows. You then trigger your flows at the system level. Note Connectivity may include connection to other or third-party products that are outside of the MFT reference solution. Additional documentation AMPLIFY Supported Platforms Central Governance documentation Flow Manager documentation Governance exchanges The following types of exchanges occur between Central Governance or Flow Manager and the managed Transfer CFTs: Flow management Certificate management Configuration management Update management See Exchanges with Central Governance for more information. Overview and practical considerations Begin by planning your MFT architecture and deployment strategy. After installing Central Governance or Flow Manager, the following steps occur: In the Transfer CFT installation select the Central Governance connectivity option After installing, start the Copilot server (the Transfer CFT server can be running, but this is optional) Registration occurs automatically on Copilot start up From Central Governance or Flow Manager start the Transfer CFT(s) If you migrated or upgraded, you may want to reference the following sections: Manually activate Central Governance connectivityParameter mapping between products Feature support and management Transfer CFTs running under Central Governance or Flow Manager can manage or have support for the following features. Feature Manage using Flow Manager or Central Governance Supported but not configurable using Central Governance or Flow Manager Folder monitoring yes yes Multi-node architecture no yes CRONJOB yes yes Exits no yes Network features IPv6 yes yes pTCP (UNIX/Windows only) yes yes UDT (UNIX/Windows only) yes yes SOCKS no yes Heartbeat embedded yes Interoperability Secure Relay no yes TrustedFile (UNIX/Windows/and z/OS) no yes PassPort AM embedded no (*) PassPort PS no yes Sentinel embedded yes Composer no no Protocols PeSIT yes yes ODETTE no yes SFTP (UNIX, Windows) no yes * If you perform a migration or upgrade from a previous version, you must migrate your PassPort AM. Legacy flows Legacy flows refer to former flow definitions available in migrated Transfer CFT systems. Central Governance or Flow Manager can manage the following use cases: Via the Central Governance or Flow Manager user interface, you can add and manage partners, and use send and receive templates for a given Transfer CFT. You can migrate Transfer CFT flow definitions to the Central Governance or Flow Manager flow-management process.