Exchanges with Central Governance

In addition to registration, there are other types of recurring exchanges that occur between Transfer CFT and Central Governance.

  • Registration
  • Configuration and flow deployment
  • Heartbeats
  • Certificate renewal
  • Apply SPs and patches


Set the parameters for Central Governance connectivity during your Transfer CFT installation. For conceptual details on the process refer to the Register with Central Governance section.

If you are migrating a Transfer CFT, refer to the Activate Central Governance connectivity section.

Configuration and flow deployment

From Central Governance you can modify Transfer CFT configuration and create flows. Deploying these pushes these modifications (for example, the equivalent of a uconfset command for a configuration change) to the Transfer CFT.


Either Transfer CFT or Copilot sends a unidirectional heartbeat to Central Governance indicating that the server is up and running.

Certificate renewal

Certificate and key renewal can refer to business and/or governance certificates. The request is initiated by the Copilot, and is received by Central Governance.

When Copilot starts the certificates expiration dates in the PKI base are checked, and a renewal request is scheduled.

Note The Transfer CFT must be registered.

Apply SPs and patches

Central Governance can apply updates, including service packs, patches, and version upgrades, remotely to registered Transfer CFTs. Simply download the service pack, patch or upgrade files from Axway Support at, and then upload the files to the Central Governance update repository.

Note Available on Unix and Windows, though this service is not available for multi-node.

Related Links