Transfer CFT InstallationGuide Win en

INSTALLATION GUIDE
Transfer CFT
Version 3.2.2
Windows

19 October 2016
Copyright2016Axway
Allrightsreserved.
ThisdocumentationdescribesthefollowingAxwaysoftware:
TransferCFT3.2.2
Nopartofthispublicationmaybereproduced,transmitted,storedinaretrievalsystem,ortranslatedintoanyhumanor
computerlanguage,inanyformorbyanymeans,electronic,mechanical,magnetic,optical,chemical,manual,orotherwise,
withoutthepriorwrittenpermissionofthecopyrightowner,Axway.
Thisdocument,providedforinformationalpurposesonly,maybesubjecttosignificantmodification.Thedescriptionsand
informationinthisdocumentmaynotnecessarilyaccuratelyrepresentorreflectthecurrentorplannedfunctionsofthis
product.Axwaymaychangethispublication,theproductdescribedherein,orboth.Thesechangeswillbeincorporatedin
newversionsofthisdocument.Axwaydoesnotwarrantthatthisdocumentiserrorfree.
Axwayrecognizestherightsoftheholdersofalltrademarksusedinitspublications.
Thedocumentationmayprovidehyperlinkstothird-partywebsitesoraccesstothird-partycontent.Linksandaccesstothese
sitesareprovidedforyourconvenienceonly.Axwaydoesnotcontrol,endorseorguaranteecontentfoundinsuchsites.
Axwayisnotresponsibleforanycontent,associatedlinks,resourcesorservicesassociatedwithathird-partysite.
Axwayshallnotbeliableforanylossordamageofanysortassociatedwithyouruseofthird-partycontent.
Contents
Preface 1
AboutTransferCFT 1
Installationguideoutline 1
Whoshouldreadthisguide 2
TransferCFTdocumentationset 2
Supportservices 2
Accessibility 3
Accessibilityfeaturesofthedocumentation 3
Screenreadersupport 3
Supportforhighcontrastandaccessibleuseofcolors 3
1 Prerequisites 5
Overview 5
Licensekeys 5
EndUserLicenseAgreement 5
Checkyourauthorization 5
Windowsx86operatingsystemprerequisite 6
Systemrequirements 8
AbouttheTransferCFTenvironment 8
DiskspaceandRAMrequirements 8
Java 8
Installerscreenresolution 9
Pre-installation 10
Windowsrequirements 10
Clusterinstallationrequirements 11
Defaultports 13
Certificates 15
2 Install 16
Beforeyoustart 16
Installationpackagecontents 16
Installationfunctions 16
Installationmodes 17
Installeddirectories 17
InstallTransferCFT 18
Starttheinstallation 18
Clustermodescreens 23
Autoimportscreens 23
Multi-nodeoptions 25
Governanceoptions 25
Connectoroptions 26
Installingservicesincommandline 28
UsingNFSv3inanactive/passivearchitecture 28
Silentmodeinstallation 31
Installerfunctions 36
Installerfunctions 36
JREcustomization 40
3 Post-installation 43
Performanupdate 43
Createabasicconfiguration 43
Updatetheprofile 43
UCONF 43
Configuration 44
Licensekey 44
TransferCFTinternaldatafileandconfiguration 44
Userinterfaceconfiguration 44
ConfigurationforServiceMode 45
StarttheTransferCFTCopilotserver 45
StartTransferCFT 45
4 Update 46
UseCentralGovernanceforupdates 46
Installerorproductspatchesandservicepacks 46
Checkproductdetails 46
Windowsupdates 47
UpdateprocedureinGUImode 47
Removeanupdate 48
RemoveupdatesinGUImode 48
Removeupdatesinconsolemode 48
5 Upgrade or migrate 49
Upgradeandmigrationoverview 49
MigratingorupgradingtoenableCentralGovernance 49
Migrationversusanupgrade 49
UpgradeTransferCFT 52
Aboutupgrades 52
Beforeyoustart 52
TransferCFT2.6.4to3.2.2 54
TransferCFT3 .1.3to3.2.2 62
Postupgrade 64
Upgradeamulti-nodeinstallation 64
Prerequisites 65
Importantinformationbeforeperformingamigrationprocedure 65
Installandautoimport 66
Generalprocedure 66
Autoimportinmulti-nodearchitecture 68
Performamanualmigration 69
Prerequisites 69
MigratingfromTransferCFT2.3.2 70
MigratingfromTransferCFT2.4 73
MigratefromTransferCFT2.5or2.6 77
MigratingfromTransferCFT2.6.4SP2or2.7 80
MigratingfromTransferCFT3.0.1or3.1.2 82
ActivateCentralGovernanceconnectivity 86
Overview 86
Automaticallyactivateconnectivity 87
Manuallyactivateconnectivity 88
ConnecttoadifferentCentralGovernancesystem 90
Useformerconfigurationobjects 90
Viewmanagedfeatures 90
Post-migrationprocedure 92
Postmanualmigrationorautoimport 92
Postmanualmigrationonly 92
Postupgrade 93
6 Uninstall 94
AboutuninstallinginWindows 94
7 Deployment packages 96
Createaproductdeploymentpackage 96
InstallatemplateTransferCFT 96
GeneratetheExpressPackage 97
CustomizetheExpressPackage 98
InstalltheExpressPackage 99
Limitations 100
8 Troubleshooting 101
Troubleshootinstallationandregistration 101
Copilotserverissues 101
CentralGovernance 101
TransferCFTserver 102
Applyingalicensekey 103
Obtainalicensekey 103
Applyalicensekey 103
SupporttoolsandcontactingSupport 104
AccessingtheAxwaySupportsite 104
UsingCFT_support 104
Preface

Thisdocumentationprovidesinformationtoaideyouininstalling,upgrading,ormigratingTransfer
CFT.
About Transfer CFT

TransferCFTisthefiletransfercomponentintheAxwayplatform,andprovidesamulti-platform,
high-volume,fileandmessagetransferservice.Thisdocumentationexplainshowtoinstall,
configure,andmanageTransferCFT.
Usingversion3.1orhigher,youcanconfigureTransferCFTandmanageflowsusingAxwayCentral
Governance.CentralGovernancesimplifiesTransferCFTusage,andprovidesservicessuchas
identityandaccessmanagement,certificatemanagement,monitoring,alerting,andaweb
dashboard.
FormoreinformationonAxwayproducts,visitwww.axway.com.
Installation guide outline

ThisguideexplainshowtoperformafullinstallationofTransferCFT.Italsodescribeshowto:
Prepare and plan your installationDescribeswhatyoushouldplanfordeployingand

configuringyoursystemarchitecture,installinganyprerequisitesoftware,andconfiguringother
components.
Install Describeshowtoperformacompleteinstallaswellasapplyaservicepack.
Post installationProvidesinstructionsonhowtocheckiftheinstallationwassuccessfulandset
upTransferCFT.Additionallyitdescribesanytaskstoperformbeforetheadministratorcanlogonto
theproductforinitialconfiguration.
UpgradeInvolvesachangeinproductversionandthereplacementofbinaryartifacts;mayalso
requireconfigurationchange.
MigrateInvolvesachangeinproductversions,suchasfrom2.7.1to3.2.2.Aspartofthis
process,theexistingconfigurationmayneedtobemodifiedorupdatedtobecompatiblewiththe
newversion.Forexample,youmayneedtomodifyconfigurationfilesortheinternaldatafile
schema.Becausemigrationcanbeacomplexprocess,organizationstypicallysetupamigration
projecttostudythenewfeaturesanddeterminetheimpactontheexistingconfiguration,andto
planforthechangesacrossthevariousenvironments.
UninstallDescribeshowyoucanuninstallTransferCFT.
Transfer CFT 3.2.2 Installation and Operation Guide1

Preface
ExpressPackage-Describeshowtocreateaproductpackagethatyoucandeploytomultiple
remotesites.
Troubleshoot the installation or registration processDescribesthedifferenttypesof

troubleshootingerrorsyoucanencounterduringinstallation,upgradeandpost-installation.
Who should read this guide

ThisguideisintendedforenterprisepersonnelinvolvedininstallingsoftwareandAxway
ProfessionalServicespersonnel.FamiliaritywithAxwayproductsisrecommended.
Thisguidepresumesyouhaveknowledgeof:
l Yourcompanysbusinessprocessesandpractices
l Yourcompanyshardware,software,andITpolicies
l TheInternet,includinguseofabrowser
Otherswhomayfindpartsofthisguideusefulincludenetworkorsystemsadministratorsandother
technicalorbusinessusers.
Transfer CFT documentation set

TransferCFTprovidesacompletesetofdocumentation,coveringallaspectsofusingtheproduct.
Thesedocumentsincludethefollowing:
l TransferCFT3.2.2ReleaseNotes
l TransferCFT3.2.2UserGuide(HTML)
l TransferCFT3.2.2LocalAdministrationUserGuide
l AxwaySupportedPlatformsGuide
l AxwayInteroperabilityMatrix
Support services
TheAxwayGlobalSupportteamprovidesworldwide24x7support,subjecttovalidationofyour
licenseagreement.Emailsupport@axway.comor,foryourlocalsupporttelephonenumber,visit
AxwaySupportathttps://support.axway.comandclickContact Axway Support.
YoucanpostcommentsandquestiontotheAxwayuserforumat:forums.axway.com/index.php

Accessibility

AtAxway,westrivetocreateaccessibleproductsanddocumentationforallofourusers.
Thissectiondescribestheaccessibilityfeaturesofthedocumentation.
Accessibility features of the documentation

Theproductdocumentationprovidesthefollowingaccessibilityfeatures:
l Screenreadersupport
l Supportforhighcontrastandaccessibleuseofcolors
Screen reader support

l Alternativetextisprovidedforimageswhenevernecessary.
l ThePDFdocumentsaretaggedtoprovidealogicalreadingorder.
Support for high contrast and accessible use

of colors
l Thedocumentationcanbeusedinhigh-contrastmode.
l Thereissufficientcontrastbetweenthetextandthebackgroundcolor.

Accessibility
4Installation and Operation Guide Transfer CFT 3.2.2

Prerequisites
1
Overview
Axwayp roductsaredeliveredelectronicallyfromtheAxwaysupportwebsite.Awelcomeletter
notifiesyouthatyourproductsarereadyfordownload.
Toinstallperformthefollowingtasks:
1. Checkyourlicensekeyandauthorization.
2. Checkthehardwareandsystemrequirements.
3. Downloadproduct.
4. Installproducts.
License keys
Beforeinstallingorupgrading,makesureyouhaveobtainedalicenseforTransferCFT.Checkthat
thelicensekeyiscorrectforthefeaturesandoperatingsystemyouintendtoinstall.Itisnot
mandatorytoenterthelicensekeyduringtheTransferCFTinstallation,butyoudorequireakeyto
starttheproduct.
Forinformationonapplyingalicensekeypostinstallation,orifyouhaveaproblemwithyour
licensekey,refertotheappropriateTroubleshootingtopic.
Note YourequireasmanykeysasinstancesofTransferCFTrunningatsametime,including
whenrunninginmulti-node.Forexample,twoTransferCFTinstancescannotrunatthe
sametime,onthesameserver,usingthesamelicensekey.
End User License Agreement

YoushouldreadandaccepttheEndUserLicenseAgreement(EULA)priortoinstallingTransferCFT.
TheEULAfileislocatedinthedirectorywhereyoudecompressedtheTransferCFTpackage.
Check your authorization

VerifythatyoucanaccessandlogonAxwaySupportathttps://support.axway.com.Ifyoudonot
haveanaccount,followtheinstructionsinyourwelcomeletter.
Logintodownloadoraccess:

1 Prerequisites
l Theproductinstallationpackage
l Yourproductlicensekey
l Productdocumentation
l Productupdates,includingpatchesandservicepacks
l Productannouncements
l AxwaySupportedPlatformsGuide
l Thecasecenter,toopenanewcaseortotrackopenedcases
Youcanalsoaccessotherresources,suchasarticlesintheKnowledgeBaseand
documentationforallAxwayproducts.
Windows x86 operating system

prerequisite
WhenusingaWindowsx86(32-bit)or(64-bit)system,youmustinstalltheVisualC++
RedistributablePackageforVisualStudio2013toprovidenecessarylibraryfiles(DLL)for
thecompiler:
l Forawin-x86-32targetuse:vcredist_x86.exe
Todownloadtheredistributionpackage,visit:VisualC++RedistributablePackagesfor
VisualStudio2013
Note IftheredistributionpackageisalreadyinstalledonyourWindowssystem,thereis
noneedtoreinstall.

1 Prerequisites
IspoketoEricaboutyourrequest.Hesaidyoushouldwriteupanemailjustificationfortraveland
hewillforwardittomanagementtoseeifAxwaycanpay,atleastforpartofthetravel.IMHO,you
wouldstandabetterchanceofgettingsomereimbursementforanOctobertripthanforoneatthe
endoftheyear.
Inanyevent,neitherhenorIhaveanyissueswithyouworkinginthePuteauxoffice,whetheritsan
Axway-paidtriporonyourowndime.

1 Prerequisites
System requirements
ThefollowingarethesystemrequirementsforTransferCFT.
About the Transfer CFT environment
Supported operating systems and browsers

RefertotheAxwaySupportedPlatformsGuideavailableonAxwaySupportat
https://support.axway.com.
Disk space and RAM requirements

TransferCFThasthefollowinghardwarerequirements:
l Diskspacerequirement
o 1.5to5Gigabyte:minimumdiskspacetoallowforfutureupdates,SPs,andcontinued
performance
l RAMRequirement
o 128Megabyte:minimumdedicatedperhost
Java
TransferCFTisbasedonJavatechnology.ToavoidcompatibilityissuesAxwayprovidesthecorrect
JRE,whichisinstalledduringtheproductinstallationinthe<Axway home>/java/<platform
name>/jreXdirectory,wherejreXrepresentstheJavaversion.
ClientsthatconnecttoCopilotrequireJava8.IfyouintendtoimplementEBICS(UNIX/Windows)or
SecureRelayyoualsorequireJava8.
Java8isdeliveredwiththeproduct,withthefollowingexceptions:
l Java7:linux-s390-32,linux-s390-64,sun-sparc-32,sun-x86-32
l Java6:hpux-parisc-32,hpux-parisc-64,linux-ia64-64
Secure RelayJava installation directory prerequisite
WhenusingSecureRelay,JavamustbeinstalledinthesameenvironmentastheTransferCFT
installation.TheMasterAgentisthusmanaged,whiletheRouterAgentcanbeinanother
environment.

1 Prerequisites
Installer screen resolution

WhentheInstallerisruninGUImode,aresolutionofatleast800x600isrequired.

1 Prerequisites
Pre-installation
ThefollowingaretaskstoperformorissuestoaddressbeforeinstallingTransferCFT.
Windows requirements
TheWindowsinstallationdirectorymustnotcontainanysub-foldersorfilesthatareownedby
anotheruser.
Apply service pack or patch using Central Governance

ToinstallaTransferCFTServicePackorpatchfromCentralGovernance,youmustruntheTransfer
CFTUIasadministrator.
Windows UAC
UserAccountControl(UAC)isavailableinWindowsVista,WindowsServer2008,Windows7,
WindowsServer2008R2,andWindows2012.
ForpreviousWindowsversions,thefollowingmustbeset.YoumustbeintheLogonasaservice
groupandthisisconfiguredin:
1. Start>ControlPanel>AdministrativeTools>LocalSecurityPolicy.
2. Fromthetree,select:LocalPolicies>UserRightsAssignment>Logonasaservice.
WhenyouhaveaWindowsversionthatsupportsUACyoucan:
l DisableUAC.
l IfyouchoosenottodisabletheUAC,theinstallerrequiresadministrationrightsatinstallation.
Youmustbepartofagroupofadministratorsorhaveanadministratoruseraccount.The
installerdetectsthetypeofuserandsendstheappropriatemessage:
l Setupwithadministratoruseraccount:Acceptordeclineifyouwanttomakechangestoyour
computer.
l Setupwithstandarduseraccount:Enteryouradministratorpasswordfirsttocontinue.
Thefollowingtasklistrequiresthatyouhaveelevatedrightsandwillfailifnoneofthetwooptions
areperformed:
l CreateorremoveshortcutsinStartmenuordesktop
l CreateorremoveWindowsservices
l Installingin%SystemRoot%or%ProgramFiles%
l Runningproductscriptsthatrequireelevatedrights

1 Prerequisites
Windows itanium installation

IfyouwanttostarttheinstalleronWindowsitanium,usesetup32.exeandnotsetup64.exe.
Cluster installation requirements

BecauseyoucannotuseaUNCpath(\\address\folder)asashareddirectory,wheninstallinga
TransferCFTclustertheshareddirectorymustbelocatedinamountedshareddrive(u:\folder).
ThisisduetoUNCpathsupportlimitations,suchasthechangedirfunction,whichareneededby
TransferCFTserver.TransferCFTcannotstartupproperlyiftheCFTDIRRUNTIMEenvironment
variableissettoaUNCpath.
Abestpracticetherefore,whenusingTransferCFTclustersinWindows,istoinstallTransferCFTin
clustermodeandpermanentlymapthenetworkshareddirectorytoadrive.Usingthismethodthe
mappeddriveisthenaccessibletotheTransferCFTWindowsServices.Thereisnoneedtomodify
theTransferCFTprofileaftertheinstallation.
Create a mapped drive

TomapnetworksharestoadriveaccessibletoWindowsServices,youmustloginastheNT
AUTHORITY\SYSTEMaccount.
1. DownloadtheSysinternalsSuitefromMicrosoft,andunzipittoadirectory.
2. OpenacommandwindowandstartasessionasAdministrator(Runasadministrator).
3. GototheunzippeddirectorycontainingtheSysinternalsSuiteexecutable:
CD <the_previously_unzipped_directory>
4. LoginastheNTAUTHORITY\SYSTEMaccount:
psexec -i -s cmd.exe
Note Thislaunchesanewcommandwindow.Performthenextstepinthisnewwindow.
5. Inthenewwindow,createthepersistentmappeddrive.
net use Z: \\servername\sharedfolder /persistent:yes
6. Providethecredentialsforauserhavingaccesstothesharedfolder.
7. CreateaStartup script thatcontainsonlythecommandfromstep5(Createthepersistent
mappeddrive),andimplementusingtheinstructionsintheMicrosoftarticle:AssignComputer
Startupscripts.

1 Prerequisites
Remove a mapped drive

Toremovethemappeddrive:
1. LaunchacommandpromptasAdministrator(Runadadministrator).
2. GototheunzippeddirectorycontainingtheSysinternalsSuiteexecutablewithcommand:
CD <the_previously_unzipped_directory>
3. LoginastheNTAUTHORITY\SYSTEMaccount:
psexec -i -s cmd.exe
Note Thislaunchesanewcommandwindow.Performthenextstepinthisnewwindow.
4. Inthenewwindow,deletethemappeddrive:
net use Z: /delete

1 Prerequisites
Default ports
ThefollowinglistcontainsthedefaultTransferCFTportnumbersusedforinstallation.Youcan
checkinadvancethattheseportsdonotconflictwithportsusedbyotherapplicationsonthesame
machine.
Youmayneedtomodifythedefaultportnumbers,dependingonyourconfiguration.
Table 1. Default ports by platform
TheInternetAssignedNumbersAuthority(IANA)reservestheTCPports1761-1768forTransfer
CFT.Formoreinformation,referto:www.iana.org/assignments/service-names-port-
numbers/service-names-port-numbers.
Component Port
PeSIT 1761
SSL 1762
COMS 1765
Copilot 1766
CopilotforCentralGovernance 1767
CentralGovernance 12553
CentralGovernanceSSL 12554
SecureRelayMA
ma.comm_port 6801
SecureRelayRA
ra.comm_port 6811
ra.admin_port 6810
Legend:
l PeSIT(PESITANYprotocol):PeSITinplaintext
l SSL:PeSITprotocoloverSSL/TLS
l COMS:Synchronoustransfers
l Copilot:ProvidesaccesstoTransferCFTCopilotserverfromauserInternetbrowser
l CopilotforCentralGovernance:ProvidessecureaccessforCentralGovernance(mutual

1 Prerequisites
authentication)
l CentralGovernance:UsedtoconnecttoCentralGovernance

1 Prerequisites
Certificates
UsingthedefaultcertificatesthataresuppliedwithTransferCFTisstronglydiscouragedina
productionenvironment.Youshoulduseyourowncertificatestoenhancesecurity.
Type Location Certificate Expires
Secure <Transfer_CFT>/home/distrib/xsr SecureRelayCA.pem November

Relay 2021
SecureRelayMasterAgent.p12 November
2021
Central <Transfer_CFT>/runtime/conf/pki passportCA.pem November

Governance 2019
ForaDERcertificate,thefilemustbecreatedwitharecordlengthequaltothesizeofthecertificate
inbytesthenthecertificatecanbeuploadedtothenewlycreatedfile.
CRTPF FILE(YOURLIB/DER_CERT) RCDLEN(1191)

Install
2
Before you start
AxwayManagedFileTransferispartoftheAxwayfamilyofmanagedfiletransfer(MFT)products.
TransferCFTisatransferexchangesystemthatenablesreliableandsecureinternalfiletransfers
betweenapplications.
IfyouareinstallingTransferCFTaspartofanAxwayManagedFileTransfersolution,youmaywant
tochecktheinstallationorderandprerequisites.Formoreinformation,pleaserefertotheCentral
Governanced ocumentation.
AxwayCentralGovernanceistheAxwaymanagementapplication,whichprovidesasetofservices
foradministeringTransferCFTsusingacohesiveandintuitiveuserinterface.FromtheCentral
GovernanceUIyoucanconfigure,accesslogs,andperformoperationaltasksforyourTransferCFT.
CentralGovernancealsosimplifiesthetaskofcreatingfiletransfersdefinitions,andsupportsmass
deploymentofconfigurationchangestogroupsofTransferCFTs.
DuringtheinstallationprocessyouarepromptedtoselectifyouwanttoenableCentralGovernance.
PleasecheckthatyourlicenseincludesCentralGovernanceandthatyouhavetherequired
information,suchasthesharedsecret,toactivateconnectivity.
Beforeyoustarttheinstallation,youshould:
l DownloadedtheinstallationpackagefromAxwaySupport.
l Uncompressedorunzippedthepackage.
Installation package contents

Theinstallationpackageisaziparchive.Onceyouunzipit,itcontainstheproductandinstaller
programfiles.
Installation functions
Theinstallerisusedtoinstall,configure,updateanduninstallTransferCFT.Youcanrunthe
followinginstallationmodes:
l Install
l Configure
l Update
l Uninstall

2 Install
Installation modes
Locateandrunthesetupfileintherootfolderoftheinstallationpackage.
GUI mode:
l Windows:setup32.exeorsetup64.exe
Console mode:
l Windows:setup32.exe-mconsoleorsetup64.exe-mconsole
Thesetup32.exeisa32-bitbuildexecutableandwillrunona64-bitplatformprovidedthatthe
compatibilitylayerhasbeeninstalled.
Formoreinformation,seeInstallerfunctions.
Installed directories
Onceyouinstallaproduct,thefollowingsub-directoriesareinstalled.
l Configuration:Includestheconfigurationfileforeachinstalledproduct
l Documentation:Userdocumentation
l Installer:Filesusedbytheinstaller
l Java:ThedeployedJREusedbytheinstallerandAxwayproducts
l SilentFile:Includesthesilentfileforeachinstalledproduct
l synInstall:Installerinternalfilesthatareusedtomanagetheinstalledinfrastructure
l Tools:Toolsusedbytheinstallertomanageinfrastructureinstances.Youcanusesomeofthese
forexample,XDBMandSilentFileEditor
Windows x86 operating system prerequisite

RedistributablePackageforVisualStudio2013toprovidenecessarylibraryfiles(DLL)forthe
compiler:
Todownloadtheredistributionpackage,visit:VisualC++RedistributablePackagesforVisual
Studio2013
Note IftheredistributionpackageisalreadyinstalledonyourWindowssystem,thereisnoneed
toreinstall.

2 Install
Install Transfer CFT
Start the installation

YoucanusethistopictoplanandexecuteinstallationofTransferCFT.IfyouareusingAdobe
Reader,youcanaddcommentstodocumentthedatayouneedtoenterafterlaunchingthe
installer.Otherwise,youcanprintthetopic,enterdatamanuallyandusethenoteswheninstalling.
Onceyouhavecompletedplanning,youarereadytoinstall.SeeAbouttheinstallerforhowtostart
theinstallerininstallmode.
ToconfigureTransferCFTforinstallation,performthefollowingprocedure.Notethatpendingyour
licensekeyoptionsandenvironment,youmayhaveonlyasubsetofthefollowingscreenselections
asschematicallyshowninthefollowingdiagram.
This table displays a basic installation, a standalone Transfer CFT, with no options.

2 Install
Screen Description
Welcome ProvideslinkstotheAxwaywebsiteandtheAxwaysupport
site.
License Selectthecheck-box"Iaccept..."tocontinuewiththe
agreement installation.
Installation Selecttoinstalloneitherasinglemachine,oraclustermode
architecture installation.
Note Ifyouselectcluster,additionalscreens
display.
Installation Whereproductfilesanddocumentationwillreside.
directory
AxwayTransfer SpecifythedirectorywhereyouwanttoinstallTransferCFT.
CFT: Bydefault,TransferCFTisinstalledinasub-directoryo fthe
Installation Axway installationdirectory.Usethedefaultdirectory,or
directory specifyanewdirectory.
Directorypathscannotcontainspaces.
AxwayTransfer SpecifythedirectorywhereyouwanttoinstalltheTransfer
CFT: CFTruntimedirectory.
Runtime Bydefault,theruntimedirectoryisinstalledinasub-directory
directory oftheTransferCFTinstallationdirectory.Usethedefault
directory,orspecifyanewdirectory.Aruntimedirectorywill
becreatedifitdoesnotalreadyexist.
AxwayTransfer SpecifyifyouwanttoimportdatafromanexistingTransfer
CFT:Auto CFTbyselectingYesorNo.
Import Youcaninstallandimportconfigurationanddatafrom
v2.3.2,v2.4,v2.5,v2.6,v2.7,v3.0.1,vor3.1.2.
Note IfyouselectYesintheAutoImportscreen,
additionalscreensdisplay.
AxwayTransfer Checkormodifythesuppliedinformationconcertingthe
CFT: TransferCFTinstancename,groupname,andhostaddress.
Identity Anasterisk*denotesthatthesefieldsaremandatory.

2 Install
Screen Description
AxwayTransfer Selecttoenablemulti-nodearchitecture.
CFT:Multi-node Enterthenumberofnodes.Thefirstnodeiszero,andyou
Architecture mayhaveuptofournodes.
Enterthehostnameandaddressforeachnode,uptofour
nodes.Youmustenteratleastonehost.
Note Ifyouenteranumbertoenablemulti-node,
AxwayTransfer EnterthelicensekeyfortheTransferCFTproduct.
CFT: Ifyouhavealicensekeyissuedforapreviousversionof
Licensekey TransferCFT,enteryourlicensekeyintheLicenseKeyfield
andselecttheCheckkeyo ption.
Youcanconfigureuptofourkeys.
DeselectCheckkeytocontinuewiththeinstallationwithouta
key.However,youcannotrunTransferCFTuntilyousupply
thelicensekey.
Note Ifyouareinstallinginmulti-nodeyou
require:
l One(1)validkeypernode
l Amongthekeystheremustbeatleastonevalid
keyperhost
AxwayTransfer EnableCentralGovernanceconnectivity:
CFT: l Yes:InstallCentralGovernanceconnectivity.Fordetails,see
Governance theCentralGovernancetopicsintheTransferCFTUser's
Mode Guide.
l No:InstallsTransferCFTwithoutCentralGovernance.
AxwayTransfer EntertheTCPparametersforthehost,PeSITprotocol,
CFT: catalog,andcommunicationmedia.
Configuration
l Synchronouscommunication:entertheCOMSport
l PESITANY:EnterthePeSITprotocolportnumber
l Selectthedefaultdatabasesize:
o Catalog:Modifythedefaultcatalogfilesize
o CommunicationFile:Modifythedefaultcommunication
filesize

2 Install
Screen Description
AxwayTransfer EntertheTransferCFTUIServervalues:
CFT:User
l ListeningPort:Listeningportforthegraphicaluser
InterfaceServer
interface.ThissetstheportonwhichtheTransferCFTUI
serverlistensforincomingTCPconnections.
l SSLListeningPort:DefinestheSSLconnectionforthe
UIserver,whenCentralGovernanceisselected.
Note:Ifyouenabledmulti-node,youarealsopromptedfortheload
balancerdetails.
AxwayTransfer ForWindowsinstallations,specifywhetheryouwanttostart
CFT:UIServer AxwayTransferCFTmanually,ortohaveWindowsstartand
startupmode stopitasaWindowsservice.Select:
l Normalmode:Youmustmanuallystartandstopthe
TransferCFTserver
l Servicemode:Windowsautomaticallystartsandstopsthe
TransferCFTserver.Ifyouselectthisoption,thenext
installerscreensetstheServiceparameters.
Note:TostartTransferCFTserverusingservicemodefrom
theCopilotserver,itisimperativethatTransferCFTservice
besetupwithaspecificuseraccount(notusingthedefault
systemuser).Iftheuseristhesystemuser,theCopilotwill
notbeabletostartTransferCFTinservicemode.
AxwayTransfer ForWindowsinstallations,specifywhetheryouwanttostart
CFT:UIServer TransferCFTUImanually,ortohaveWindowsstartandstopit
startupmode asaWindowsservice.Select:
l Normalmode:Youmustmanuallystartandstopit.
l Servicemode:Windowsautomaticallystartsandstopsit.If
youselectthisoption,youusethenextinstallerscreento
setServiceparameters.


2 Install
Screen Description
AxwayTransfer IfyouselectedServicemode,entervaluesfortheWindows
CFT:UIServer serviceparameters:
service l ServiceName:EnteraWindowsservicename
l DisplayName:EnteraWindowsservicedisplayname
YoucanacceptthedefaultServicenameso rmodifythem.The
installerusesthesenamestocreateaTransferCFTserviceentry
intheWindowsregistry.
l StartType:Automatic,Manual,Disabled
l ErrorControl:Ignore,Normal,Severe,Critical
l Usespecificaccounttostarttheservice:Enablesyoutouse
alocalaccountinsteadofasystemaccount
l Domain:Enterthedomainname
l Username:Nameofthelocalaccount
l Password:Entertheuserpassword
Note:Inmulti-node,tostarttheTransferCFTserverusing
servicemodefromtheCopilotserver,itisimperativethat
TransferCFTservicebesetupwithaspecificuseraccountand
domain(notusingthedefaultsystemuser).Iftheuseristhe
systemuser,CopilotwillnotbeabletostartTransferCFTin
servicemode.
AxwayTransfer ThisscreenenablesyoutoinstallStartMenushortcuts.
CFT: l Yes:Createsshortcuts
Shortcuts
l No:Doesnotcreateshortcuts
Thisscreenenablesyoutoinstalldesktopshortcuts.
l Yes:Createsshortcuts
l No:Doesnotcreateshortcuts
AxwayTransfer ThisscreenallowsyoutoselectfromthefollowingAxway
CFT: productconnectors:
Connectors l Sentinel
l PublicKeyInfrastructurewithPassPort
l AccessmanagementwithPassPort
Note Ifyouselectanyoftheavailableconnectors,
AxwayTransfer ClickInstall tocompletetheinstallationprocess,or

CFT: Previous toreviewormodifyinstallationoptions.
Readytoinstall

2 Install
Cluster mode screens

Screen Description
Installation Selecteither:
architecture o Single-installsonasinglemachine
o Cluster-onclusternode
Cluster o Firstnode:Youmustinstallonafirstnodebeforeaddingadditional
nodes.
o Additionalnodes:Youmustfirstinstallaninitialnode,before
selectingthisoption.
Installation Specifytherootandshareddirectorieswhereyouwanttoinstallthe
directories productfilesandwherethedocumentationwillreside.
Axway SpecifythedirectorywhereyouwanttoinstallTransferCFT.
Transfer Bydefault,TransferCFTisinstalledinasub-directoryo ftheAxway
CFT: installationdirectory.Usethedefaultdirectory,orspecifyanew
Installation directory.
directory Selectthedirectorythatwillstoreshareddatabetweenthecluster
nodes.
Axway SpecifythedirectorywhereyouwanttoinstalltheTransferCFTruntime
Transfer directory.
CFT: Bydefault,theruntimedirectoryisinstalledinasub-directoryofthe
Runtime TransferCFTinstallationdirectory.Usethedefaultdirectory,orspecifya
directory newdirectory.Aruntimedirectorywillbecreatedifitdoesnotalready
exist.
Auto import screens

IfyouselectYesintheAuto importscreen,thefollowingInstallerpagesdisplay.

2 Install
Screen Description
AxwayTransfer SpecifyifyouwanttoimportdatafromanexistingTransferCFTby
CFT:Migration selectingYesorNo.
YoucanmigratefromV2.3.2,V2.4,V2.5,V2.6,v2.7,v3.0.1or
v3.1.2.
AxwayTransfer Specifythepathtotheprofilefile.
CFT:Migration
AxwayTransfer Thisscreenisonlydisplayedduringamigrationoperation.You
CFT:Migration shouldseetheVersion,SP,Installationdirectoryandruntime
Options directorylistedonthescreen.
Selecttheobjectsthatyouwanttoimport:
ForV2.5.xandhigher:
l Functionalconfigurationobjects(PARM/PART)
l Environmentobjects(UCONF)
l Catalog:CFTCATA
l Communicationmedium:CFTCOM
l LocalPKIbase(sinceV2.5.1-SP2)
ForV2.4.x:
l Environmentobjects(Sentinel:trkapi.cfg)
l Environmentobjects(Copilot:copconf.ini)
l Catalog(CFTCATA)
l Communicationmedium(CFTCOM)
l LocalPKIbase(sinceV2.4.1-SP6)
ForV2.3.2:
l Environmentobjects(Sentinel:trkapi.cfg)
l Catalog(CFTCATA)
l Communicationmedium(CFTCOM)
Youhavetomigratethefollowingobjectsmanually:
l Executables
l Exits
l APIs
Formoreinformationonimportingconfigurationanddata,seeInstallandautoimport.

2 Install
Multi-node options
Screen Description
AxwayTransfer Selecttoenablemulti-nodearchitecture.
CFT:Multi-node Enterthenumberofnodes.Thefirstnodeiszero,andyoumay
Architecture haveuptofournodes.
Enterthehostnameandaddressforeachnode,uptofour
nodes.Youmustenteratleastonehost.
AxwayTransfer EnterthelicensekeyfortheTransferCFTcomponent.
CFT: IfyouhavealicensekeyissuedforapreviousversionofTransfer
Licensekey CFT,enteryourlicensekeyintheKeyfieldandc hecktheCheck
keyo ption.
Youcanconfigureuptofourkeys.Ifyoudonothavealicense
key,youcanselectthecheckbox.
DeselectCheckkeytocontinuewiththeinstallationwithouta
key.However,youcannotrunTransferCFTuntilyousupplythe
licensekey.
Note Ifyouareinstallinginmulti-nodeyourequire:
l One(1)validkeypernode
l Amongthekeystheremustbeatleastonevalidkey
perhost
Backtocoreinstallationscreens(GovernanceMode).
Formoregeneralinformationonusingmulti-nodefeaturesrefertotheTransferCFTUser's
Guide,inthetopicAboutmulti-nodearchitecture.
Governance options
Screen Description
AxwayTransfer EnableCentralGovernanceconnectivity:
CFT:Governance l Yes:InstallCentralGovernanceconnectivity.Fordetails,see
Mode theCentralGovernancetopicsintheTransferCFTUser's
Guide.
l No:InstallsTransferCFTwithoutCentralGovernance.For
details,clickConnectoroptions.

2 Install
Screen Description
CGconnectivity ThisscreenisonlydisplayedifyouenabledCentralGovernance
connectivity.Entervaluesforthefollowingparameters:
l CGHostAddress:Setstheserverhostnameonwhichthe
connectorwillconnect
l CGPort:Setstheportonwhichtheconnectorwillconnect
l SpecifyCustomCertificate:Ifselected,enterthecertificateto
authenticateCentralGovernance.
l SharedSecret
l ConfirmSharedSecret
ForgeneralinformationonCentralGovernance,seetheGovernanceservicestopicintheTransfer
CFTUserGuide.
Connector options
Screen Description
AxwayTransfer Specifytheconnectorsthatyouwanttoconfigureandactivate:
CFT:Connectors l Sentinel
l PKIwithPassPort
l AccessManagementwithPassPort
TransferCFT: ThisscreenisonlydisplayedifyouenabledSentinelconnectivity.
Sentinel Entervaluesforthefollowingparameters:
Connector
l SentinelHostAddress:SetstheSentinelserverhostnameon
whichtheconnectorwillconnectto
l SentinelPort:SetstheSentinelServerportonwhichthe
connectorwillconnectto
Connectorparameters
l LogFilter
l TransferFilter:Selectthelevelofinformation,warning,error
andfatalmessagesyouwanttoreceive:All,Summary,No
l EnableSentinelHeartbeat:Checktoenable

2 Install
Screen Description
TransferCFT: ThisscreenisonlydisplayedifyouenabledPassPortPKI
PassPortPKI connectivity.Entervaluesforthefollowingparameters:
connector l PKIServerHostAddress:SetsthePassPortserverhostnameon
whichtheconnectorwillconnect.
l PKIServerPort:SetsthePassPortPSport(PSsocketserver
port,orPSsecuresocketserverport)onwhichtheconnector
willconnect.
o UseSSL
o PKIserverpubliccertificate
o Copycertificate
o PKIserverlogin
o PKIServerPassword
o ConfirmPKIServerPassword
TransferCFT: ThisscreenisonlydisplayedifyouenabledPassPortAM
PassPortAccess connectivity.Entervaluesforthefollowingparameters:
Management l AMServerHostAddress:SetsthePassPortserverhostnameon
connector whichtheconnectorwillconnect.
l AMServerPort:SetsthePassPortAMserverport(APIserver,or
secureAPIserver)onwhichtheconnectorwillconnect.
o UseSSL
o AMServerpubliccertificate
o Componentinstance
o Domain
o ComponentLogin
o ComponentPassword
o ConfirmP assword

2 Install
Installing services in command line
Windows only
Transfer CFT services

1. ToinstalltheTransferCFTserviceaccesstheTransferCFTdirectory:
cd%TransferCFT_directory%
2. Enterthefollowing:
cscript/nologo\home\bin\cftsrvin.vbsn=CFT310
Wheren=<CFTplusthecurrentversionofTransferCFT>
Copilot services
FromtheTransferCFThomedirectory,run:
copsrv.exe-install<service_name><displayname><cftdirruntime>
Example
ForTransferCFTversion3.2.2Copilotyouwouldenter:
c:\CFT313\Transfer_CFT\home\bin>copsrv.exe-installCFT_Copilot313CFT_Copilot31
c:\CFT313\Transfer_CFT\runtime
Using NFSv3 in an active/passive

architecture
TherecommendationsinthistopicapplytoaTransferCFTactive/passivemono-nodearchitecture
basedonanNFSv3sharedfilesystem.
l RequiredNFSv3mountoptions
l Mountoptionssummary
l Synchronous/asynchronousoptionimpact
Required NFSv3 mount options
Set the hard and nointr options

MountNFSv3usingthehard andnointroptions.

2 Install
Define file locking

Setlockingtothenolock optionsothatTransferCFTcanlockfileslocally,butnotethatsuch
locksprovideexclusiononlyagainstotherapplicationsrunningonthesameNFSclient.Thelocks
arenotpropagatedtotheserver.InthecaseofafailoverTransferCFTcanrestartonthebackup
node.
Caution SincelocksarenotpropagatedtotheNFSserver,donotperformwriteoperationon
TransferCFTdatafiles(UCONFsettings,parametersandpartnersfile,thecatalog,and
thecomfile)fromanotherNFSclientotherthantheonewheretheTransferCFTinstance
isrunning.
Set the cto option

NFSimplementsaweakdataconsistencycalled"CloseToOpenconsistency"orcto.Thismeans
thatwhenafileisclosedonaclient,allmodifieddataassociatedwiththefileisflushedfromthe
server.IfyourNFSclientsallowthisbehavior,becertainthatthecto optionisset.
Mount options summary

ThefollowingtablesummarizestherecommendedNFSv3mountoptions.
Correct option Incorrect option
nolock( default) "lock"
hard( default) "soft"
nointr(notthedefault) "intr"
cto( default) "nocto"
Synchronous versus asynchronous option

Toimproveperformance,NFSclientsandNFSserverscandelayfilewriteoperationsinorderto
combinesmallfileIOsintolargerfileIOs.YoucanenablethisbehaviorontheNFSclients,NFS
servers,oronboth,usingtheasync option.Thesync optiondisablesthisbehavior.
Client
Ontheclientside,usethemount commandtospecifytheasync/syncoption.

2 Install
Async
TheNFSclienttreatsthesync mountoptiondifferentlythansomeotherfilesystems.Ifneither
sync norasync isspecified(orifasync isspecified),theNFSclientdelayssendingapplication
writestotheserveruntilanyofthefollowingeventsoccur:
l Memorylimitationsforcereclaimingofsystemmemoryresources.
l TransferCFTexplicitlyflushesfiledata(PeSITsynchronizationpoints,forexample).
l TransferCFTclosesafile.
Thismeansthatundernormalcircumstances,datawrittenbyTransferCFTmaynotimmediately
appearontheserverthathoststhefile.
Sync
Ifthesync optionisspecifiedonamountpoint,anysystemcallthatwritesdatatofilesonthat
mountpointcausesthatdatatobeflushedtotheserverbeforethesystemcallreturnscontrolto
TransferCFT.Thisprovidesgreaterdatacachecoherenceamongclients,butatasignificantcostto
performance.
Server
Ontheserverside,usetheexports commandtospecifytheasync/syncoption(NFSserver
exporttable).
Async
Theasync optionallowstheNFSservertoviolatetheNFSprotocolandreplytorequestsbefore
anychangesmadebythatrequesthavebeencommittedtostablestorage(thediskdrive,for
example),eveniftheclientissettosync.Thisoptionusuallyimprovesperformance,howeverd ata
maybelostorcorruptedinthecaseofanuncleanserverrestart,suchasanNFSservercrash.
Thispossibledatacorruptionisnotdetectableatthetimeofoccurrence,becausetheasyncoption
instructstheservertolietotheclient,tellingtheclientthatalldatawaswrittentostablestorage
(regardlessoftheprotocolused).
Sync
Enablesrepliestorequestsonlyafterthechangeshavebeencommittedtostablestorage.
Note Formoreinformationontheseoptions,refertoNFSmountandexportoptionsinthe
UNIXmanpages(forexample,here).

2 Install
Synchronous / asynchronous option impact
Client Server Internal data Transferable Performance

data
Sync Sync 1 1 Low
Sync Async 2( securetheNFSserver) 2( securethe Medium

NFSserver)
Async Sync 1( ifcft.server.catalog. 1( whenusing Medium-high

sync.enable=Yes) syncpoints)
Async Async 3 3 High
Legend:
l 1=Secure
l 2=Fairlysecure
l 3=Notsecure
l Internaldata=TransferCFTruntimefiles,suchasthecatalog
l Transferabledata=FilesexchangedusingTransferCFT
Silent mode installation

Note Windowsonly.Ifyouhaveimplementedafirewall,deactivatethefirewallpriorto
installationinsilentmode.
Silentmodeenablesyoutoperformaninstallationorconfigurationinanon-interactivemode.You
donothavetoenteranyparametersintheGUIorconsole.
Tousethismode,youmustinstalltheproductorruntheinstallerprogramandperform
configurationuntiljustbeforeyouclickInstall.Theninyourhomeinstallationdirectoryyouwill
havethesilentfiletemplateyoucanusetoduplicateinstallationsonothermachines.
Silent file concepts

Thepurposeofusingasilentfileistoquicklyduplicateaninstallationonmultiplemachineswithout
runningtheinstallerandenteringthesameparametersoverandoveragain.
Theinstaller'ssilentmodetakesthesevaluesfromexistingorgeneratedsilentfiles.Beforeyoucan
usethisprocedure,youmusthavethenecessarysilentfilesavailable.Youcangeneratethesefiles
byinstallingaproductatleastoncebycompletingthedialogsupuntilthepointofclickingInstall.

2 Install
Creation
Asilentfilecanbecreated:
l Afteraninstallation
or
l AftercompletingtheinstallerdialogsupuntilthepointofclickingInstall
Theinstaller'sSilentFiledirectorycontainsthepropertiesfile(Install_Axway_Installer_
V4.8.0.properties)andtheproductpropertyfilesyoumightneedtoinstall.Youmustnotmodify
anythinginthisfileexcepttheInstallDir,SynchronyLogicalNameandlistofIncludeFiles.The
productpropertyfilescannotbeusedoutsideofthemaininstallerfile.
Location
Thesilentfileiscreatedin:
<<installdirectory>>\SilentFile\<InstallationDateTime_Action>\<Install_ProductShortName_
V<Version>.properties
Where:
l InstallationDateTimecorrespondstoYear_Month_Day_Hour_Minute_Second.
l Actioncorrespondstotheactiondone,forexampleifyouperformedaninstallorconfigure.
Variables
Asilentfileisacollectionofparametersintheformofkey-valuepairs,eachononeline.Thevariable
storesthenameoftheparameter(itisthekey)andthevaluestorestheotherstring.
Thestructureofavariableinsidethesilentfileis:
Variable = Value
Note Theextraspacesaroundthevariablearetrimmed.
Somespecialtypesofvariablescanbeidentified.
Variable.Property = Value
Variable.Default = <LinkToAnotherVariable> | Value
Avariablepropertysignifiesorprovidessomeadditionalinformationaboutthatspecificvariable
(commonlyknownasmetadata;itmightbeusedforvalidationpurposes,forparsingpurposes,
etc.).
Forexample,informationonthecreationdate:
CreationDate = 13-02-2010

2 Install
CreationDate.Format = dd-MM-yyyy
Specifythecreationdateofthesilentfile(currently,thedatethesilentfilewaslastmodifiedbythe
buildtooleffectivelythedateofthebuildusedbythecurrentkit)andbelow,theformatusedto
parsethisdatevariable(theformatusedbythedatevariable).
Ifavalueismissing,theinstallertakesthedefaultvalueinstead.Ifthedefaultvaluelinkstoanother
variable,thelinkisreplacedbythevalueofthelinkedvariable(thisiscalledafeedbacklink).
Encrypted variables
Forsecurityreasons,somevariables(passwords)areencryptedinthesilentcase.Thismeansthe
Formatpropertycontainstheusedencryptionalgorithm(defaultisplain).
l Ifyouwanttochangethevalueofanencryptedvariable,youmustusethesilentfileeditortool
l YoucandisabletheencryptionofthevariablebydeletingtheFormatproperty
Environment variables
Ifyouneedtodeployaproductinstallationonseveralmachines,withonlyafewchangestomake
ontheinstallationparameters,usethesamesilentfile.Inthesilentfileyoucanreplacethe
unwantedparameterswithenvironmentvariablesthatyoudefinedonyourmachinebeforethe
installation.YoucanthenusethesevariablesinsteadoftheVariableValues.
YoucanuseenvironmentvariableswheninstallingorconfiguringinSilentmode(limitedtoSilent
modeonly.)
l InWindows:%env_var%
Therearerestrictionsforcertainvariablesandthereforeyoucannotuseanenvironmentvariablefor
thefollowingparameters:
l Componentproperties
l Variableproperties
l Installervariables(inthefileInstall_Axway_Installer_VX.Y.Z.properties),except
InstallDir,SynchronyLogicalName
Example
YoucanuseanytexteditorortheSilentFileEditortomodifyvariablesinthesilentfile.
Anexampleofchangingtheinstallationdirectory:
InstDir=C:\<installdirectory>\
InstDir.Type=String
InstDir2=C:\<installdirectory>\Composer
InstDir2.default=<InstDir>/Composer

2 Install
Using silent mode

Toruntheinstallerinsilentmode,youneedthefollowingcommands:
Windows:
l setup32.exes<theabsolutepathtotheinstallerSilentFile>
l setup64.exes<theabsolutepathtotheinstallerSilentFile>
Theinstaller'ssilentfileislocatedin<installdirectory>/SilentFile/<DirectoryDate>/after
installationandiscalledInstall_Axway_Installer_V<version>.properties.
TheSilentFiledirectorycontains:
l Installerpropertiesfile(Install_Axway_Installer_V<version>.properties)
l TransferCFTpropertiesfile(Install_Transfer_CFT_V<version>.properties)
l Thecom.axway.installerfolder
YoushouldalwayscalltheAxway_Installersilentfilefromthecommandlineregardlessofthe
numberofproductsyouwanttoinstall.Youcanaddordeleteproductsfromthesilentinstallationif
necessary,aslongastheyexistintheSilentFile.OpentheAxway_Installerpropertiesfileandscroll
totheend.ThereareanumberofIncludeFilesspecifyingthenumberofproductsincludedforan
installation.YoumustnotmodifyanythingelseinthisfileexcepttheInstallDir,the
SynchronyLogicalNameandthelistofIncludeFiles.
Followtheserecommendationsconcerningasilentinstallation:
l Youmustusetheabsolutepathtothesilentfileandnottherelativeone
l Thecommandmustpointtotheinstallersilentfileandnottheproductsilentfile
l Theproductsilentfilesinstalledinsilentmodemustbeinthesamedirectoryastheinstaller
silentfile
l Thecom.axway.installerfolder/directorymustbeinthesamedirectoryasthesilentfiles
Install products silently in a directory with white spaces

InWindows,theinstallersupportsthesilentinstallationinafolder,forexample(c:\ProgramFiles),
withwhitespacesif:
l AllproductsintheSilentFileallowwhitespaces,regardlessoftheotherproductspresentinthe
installationpackage(whicharenotlistedintheSilentFile)
Theinstallerdoesnotsupportinstallationinafolderwithwhitespacesandtheinstallationwillstop
if:
l AtleastoneoftheproductsintheSilentFiledoesnotallowwhitespaces,regardlessoftheother
productspresentintheinstallationpackage(whicharenotlistedintheSilentFile)
Configure product in silent mode

Toconfigureaninstallationinsilentmode,youneedthefollowingcommands:

2 Install
Windows:
l configure32.exes<theabsolutepathtotheinstallerSilentFile>
l configure64.exes<theabsolutepathtotheinstallerSilentFile>
Silent File Editor

UsetheSilentFileEditortomodifyvariablesinasilentfile.Itcanbeusedfromthecommandlineor
theGUI.
Themostcommonvaluesthatyoureplacewhenpreparinganewinstallationusingasilentfileare
theInstallDirandCommonDirvariables.Thevalueofthesefieldsisusedtoconcatenateotherpaths
intheproductssilentfilepropertiesfile.
Location
TheSilentFileEditorisintheinstallationdirectoryinTools/SilentFileEditor.
Note CopyingtheSilentFileEditorfromtheinstallationpackageisnotsupportedbecauseit
usesbinaryfilesfromtheinstaller.
Modifying a silent file using the command line

Tomodifyasilentfileusingthecommandline,run:
l InWindows:SilentFileEditor.bat
TheparametersfortheSilentFileEditorare:
l Thepathtothesilentfilethatyouwanttomodify
l Threeargumentsinthisformat:
o Thefirstargumentisthenameofthevariablethatyouwanttomodify(forexample,DB_
ADMIN_PASSWORD).Eachvariablenamegivenmustexistinthesilentfile
o Thesecondargumentisthevaluethatyouwanttoassigntothevariablegivenasthefirst
argument
o Thethirdargumentiscifthevalueistobeencryptedfirstandthensavedinthesilentfile,
oruifthevaluedoesnotneedtobeencrypted
Youcanhavemorethanonegroupofargumentsasshownintheexamplesbelow.
Example
SilentFileEditor.bat SilentFilePath varName1 value1 c/-u varName2

value2 c/-u varNameN valueN c/-u

2 Install
Modifying a Silent File using the user interface
Starting the GUI

TostarttheSilentFileEditorGUI,runSilentFileEditorGUI.batorSilentFileEditorGUI.shat
<installationdirectory>\Tools\SilentFileEditor.
Using the GUI

TheGUIdisplaysthelistofvariablesandvaluesinthesilentfile.
Use File > Opentoopenthesilentfileyouwanttoedit.
FromtheToolsmenuyoucan:
l EncryptSelected:EncryptstheValuesselectedwiththeAES128algorithm
l UndoSelected:Undoesthechangesmadeonthecurrentselection
l Undoallchanges:Undoesallchangesmadeonthecurrentselection
l Replace:Findsavariableandreplacesitwiththevalueyouselect.InsideoftheReplace
commandthereareotheroptions:
l Replaceall:Replacesallpathsinallthevariablevalues
l Findnext:GoestothenextvalueoccurrenceandifyouclickReplaceitreplacesthevalue
l Encrypt:EncryptsthevalueintheReplaceValuewithfield
Onceyouhavecompletedallthemodifications,useFile>Savetosavethesilentfile,thenFile >
ExittoquittheSilentFileEditorUI.
Installer functions
Installer functions
Thissectiondescribefunctionsyoucanperformwiththeinstaller.
Display command
Thedisplaycommandlistsinformationaboutallinstalledproducts.Thecommandisnamed
display.batonWindowsanddisplay.shonUNIXandLinux.Runitfromtherootinstallation
directory.
Whenrunwithoutparameters,thecommandlistsallinstalledproductsandversionsandallapplied
servicepacks.
Usethenameparametertodisplaytheinstallationhistoryofasingleproduct.Forexample:

2 Install
display -n <product name>
Install product
Tostarttheinstallertoinstallaproduct:
Locateandrunthesetupfileintherootfolderoftheinstallationpackageyoudownloadedfromthe
Axwaysupportsiteanduncompressedorunzipped.
GUI mode
l Windows:setup32.exeorsetup64.exe
Consolemode
l Windows:setup32.exe-mconsoleorsetup64.exe-mconsole
setup32.exeisa32-bitbuildexecutableandwillrunona64-bitplatformprovidedthatthe
compatibilitylayerhasbeeninstalled.
Windows installations
Thesameuserthatdidtheinitialinstallation(oratleastthesametypeofuser)muststartthe
installer.
Servicesmodification
Someproductssupportaninstallationinservicemodewithauserotherthanthedefault(Local
SystemAccount).
Ifthedomainfieldisnotshownintheproductsserviceconfigurationdialog,thenitmustbe
introducedintheusernamefield,usingthisformat:
<domain>\<username>
Ifitisalocaluser(auserthatwascreatedonthelocalmachine)thenthe<domain>fieldcanbe.
orthe<hostname>.
Example
Localuser:user1
.\user1
<hostname>\user1
Networkuser:user2
<domain_name>\user2
Configure product
Thissectiondescribesrunningtheinstallerinconfiguremodetochangeaproduct'sconfiguration.

2 Install
Thefollowingdescribesrunningtheinstallerinconfiguremode.
GUI mode
l Windows:InWindowsStartmenu,selectAxwaySoftware>Axway[installationname]>
Configure
Console mode
l Windows:
o configure32.exemconsole
Note IfyoudonotwanttouseeithertheGUIorconsolemodestoconfigureyourinstallation,
refertotheSilentmode.
About host name

Hostnamecorrespondstotheobjectassignedtoaphysicalserver.Intheinstaller,hostnameis
requiredforthefollowingreasons:
l Inalicensekeypage,tovalidatethattheenteredkeymatchesthehostname.Inthiscase,enter
onlythehostname(withoutthedomainname)andmakesurenottoconfuseHostnamewith
LogicalServerName.
l Inapagewhereyouconfigurewhichnetworkinterfacetheproductisgoingtolistenforan
incomingconnection.Inthiscase,enteroneofthefollowingvalues:
o Hostname
o Thefullyqualifiedname(hostnameanddomainname)
o IPaddressofthemachine
o Specificstring(0.0.0.0or*)indicatingthatyouwanttheproducttolistenonallnetwork
interfacesifyourmachinehasmorethanone
o LogicalhostnameorIPaddressifyouaredoinganinstallationonamachinethatispartofa
cluster
l Inapagewhereyouconfigurehowyourproductisgoingtoconnecttoanotherproduct.Inthis
case,itisstronglyrecommendedtouseeitherthefullyqualifiednameortheIPaddressofthe
remotemachine.Iftheremotemachineyouareconnectingtoisacluster,thenusethelogical,
fullyqualifiedclusterhostnameorIPaddress.
Using a temporary directory

Theinstallerneedsatemporarydirectorywhenitstartstounzipandpreparetheenvironmentit
requiresforproductorupdateinstallation.Thetemporarydirectoryitusesisthefirst%TMPDIR%,
%TMP%or%TEMP%environmentvariablethatisnotnull.Itisveryimportantthatthevalueofthe
variabledoesnotcontainanyspaces.Ifitdoes,aNullPointerExceptionjavaerroroccurs.

2 Install
Youcanforcetheuseofanothertemporarydirectorybysettingthefollowingenvironmentvariable,
TEMPORARY_DIR.
Ifyoudothismakesurethetemporarydirectoryhas:
l Enoughdiskspace
l Read/writeaccessforstartingtheinstaller
Installation modes
Youcanusethefollowinginstallerinstallationmodes.
l GUImodeissupportedonWindows,UNIXandLinux.However,touseonUNIXplatforms,the
installerrequiresanX-Windowenvironment.TouseanX-Windowdistributedenvironment,you
mustexporttheDISPLAYenvironmentvariable:exportDISPLAY=myhost.mydomain:0.0
l Consolemodedisplaysaseriesofpromptsrequiringuserresponsesoractions.
l Silentmodeenablesyoutoperformaninstallationorconfigurationinanon-interactivemode.
YoudonothavetoenteranyparametersintheGUIorconsole.
Installer functions
TheinstallercommandfilesareforinvokinginstallerfunctionsinGUIorconsolemode.
Beforeinstalling,installistheonlyavailablefunction,invokedwiththesetupfileintheroot
directoryoftheinstallationpackage.
Afterinstalling,theconfigure,updateanduninstallfunctionsareavailable.Thescriptsforthose
functionsareintherootinstallationdirectory.
Function Mode UNIX/Linux Windows
Install GUI setup.sh setup32.exe

setup64.exe
Console setup.shmconsole setup32mconsole

setup64mconsole
Configure GUI configure.sh configure32.exe

configure64.exe
Console configure.shm configure32.exem

console console
configure64.exem
console

2 Install
Function Mode UNIX/Linux Windows
Update GUI update.sh update32.exe

update64.exe
Console update.shmconsole update32mconsole

update64mconsole
Uninstall GUI uninstall.sh uninstall32.exe

uninstall64.exe
Console uninstall.shmconsole uninstall32.exemconsole

uninstall64.exemconsole
Theconfigurefunctionletsyouchangesettingsthatwereappliedduringinstallation.
Theupdatefunctionletsyouapplyorremoveservicepacksandpatches.
Afterinstallingthefollowingfunctionsareavailable:
l Installproduct
l Configureproduct
l UpdateproductandRemoveupdates
l Uninstallproduct
l Transferinstallationpackagesonremotemachines
JREcustomization
ToavoidcompatibilityissuesforaproductbasedonJava,AxwayprovidesthecorrectJRE,whichis
installedduringtheproductinstallation.However,alightweightinstallerdoesnothaveaJRE.You
starttheinstallerwiththeJREalreadyinstalledonyourmachine.Inotherwords,theinstallerruns
withanexternalratherthaninternalJRE.
Theadvantagesarethatitallowsyoumoreflexibilityandsavesyouondiskspacestorage.
Theinfrastructuredependentartifactoftheinstallerisseparatedintotwoartifacts(toolsandjava).
AllAxwayproductscanuseanexternalJRE.ThisisspecificallyusefulforCcodedproductsas
downloadingtheJREsisnolongermandatoryaspartofaninstallationkit.
Installer-dependent deliverables
Theinstaller-dependentartifactsaresplitintwoparts(toolsandjava),nowthatusingastandard
JREisoptional.
Thenamesofthetwoartifactshavenotchangedfromthepreviousonesexcepttheyhavea-tools
and-javasuffix:

2 Install
l TheAxway_Installer_VG.M.m_<platform>-toolsartifactcontainsthenecessarytoolsrequiredby
theinstallerwhichareplatformspecificandarestillmandatoryintheinstallationkit.
l TheAxway_Installer_VG.M.m_<platform>-javaartifactcontainsthestandardJREsdeliveredby
theinstallerwhichareplatformspecificandarenowoptional.
Run the installer using an external JRE

ToruntheinstallerwithanexternalJRE:
l SettheAXWAY_JAVA_HOMEenvironmentvariableorJAVA_HOMEenvironmentvariable.
l TheinstallerstartsinthefollowingorderofprecedencewiththeJREspecifiedinthe:
l InstallationkitintheJava/<platform>folder
l AXWAY_JAVA_HOME
l JAVA_HOME
TheenvironmentvariablesneedtopointtotherootoftheJREinstallation.TheJavainstancewill
runfrom<ENV_VAR_PATH>/bin/java.
Run a product using an external JRE

Thissectiondescribesrunningproductsafterinstallinginvariousmodes.
Normal installation
WhenyouperformacleaninstallationwiththeinstallerusinganexternalJRE,allinstalledproducts
areconfiguredtousetheexternalJRE.Thisalsomeanstheinstallercannotinstallproductsthatdo
notsupporttheexternalJRE.
WhenyouruntheinstallerwitheitheraninternalorexternalJREforthepurposeofmanagingan
existinginstallation(addingadditionalfeaturesorproducts),alltheproductsincludingthenewly
installedoneswillusetheJREconfiguredfortheexistinginstallationandnottheJREconfiguredto
runwiththeinstaller.
Whenyouruntheinstallerinconfiguremode,itdoesnotapplyanychangesonthetypeofinternal
JREused.IftheinstallationisconfiguredtouseanexternalJRE,allproductswillbereconfiguredto
usethenewpathsspecifiedintheenvironmentvariables.
Caution TosettheJRE,theinstallerusesthepathspecifiedintheenvironmentvariableatinstall
time,nottheenvironmentvariableitself.Thismeansthatanymanualchangesyoumake
totheenvironmentvariableswillnotbetakenintoaccount.Ifyouwanttochangethe
externalJREusedbyaninstallationyouneedtofirstchangethevalueofthe
environmentvariableandthenruninstallerinConfiguremodeonthatinstallation.
NotethatsomeproductsdonotcurrentlysupportreconfiguringtheJavapath.Itmeansthatfor
theseproducts,theJavapathcannotbemodifiedusingtheinstallerand,ifnecessary,willhaveto
bedonemanually.

2 Install
Caution Donotmodifyordeletethepathsspecifiedintheenvironmentvariablesusedtosetthe
externalJREafterinstallation.Ifyoumakeanychangestothesepaths,itwilldirectly
affectthefunctioningofalltheinstallationsconfiguredtousethem.Youshouldhandle
anymodificationstotheseenvironmentvariablesandJavapathswithextremecaution.
Silent installation
TheparametersfromsilentfilesusedforspecifyingtheJREtousewillalwaysbeoverwritten
dependingonthecontextoftheinstallation:
ForexampleifyouhavesilentfilesmadefromapackagewhichcontainedJavaandasilent
installationthatisgeneratedwithapackagewithouttheembeddedJava:
l Theinstallerre-computestheJavapathsrequiredbytheproducts,andtransparentlyignoresthe
correspondingsettingsinthesilentfile(ifany)
l Thereversecaseishandledinthesamemanner

Post-installation
3
AfterinstallingTransferCFT,butbeforestartingTransferCFTandtheCopilotserver,youmayneed
toperformthefollowingtasks:
l Performanupdate
l Createabasicconfiguration
Otherwiseyoucangoto:
l StarttheTransferCFTCopilotserveronpage45
l StartTransferCFTonpage45
Forinformationonuserrights,refertothetopicDefininguserrightsUNIXintheTransferCFTUser
Guide.
Perform an update
Ifyouneedtoapplyservicepacksorpatches,refertoUpdateTransferCFT.
IfyouhavealreadystartedTransferCFTorCopilot,stoptheseserverspriortoperforminganupdate.
Create a basic configuration

ThissectiondescribeshowtocreateabasicTransferCFTconfigurationifyoudidnotdosoduring
theinstallationprocess.IfyoustartedTransferCFTorCopilot,stoptheseserversbeforemodifying
theconfiguration.
Update the profile

ToaddenvironmentvariablestoyourTransferCFTprofileeditthefollowingscript:
l Windows:<CFTDIRRUNTIME>\profile.bat
UCONF
TodeterminetheTransferCFTvariablevalueslistthevaluesusingthecommand:
CFTUTIL listuconf

3 Post-installation
Tochangeorupdateavalue,starttheTransferCFTprofileandmakemodificationsusingeitherthe
TransferCFTCopilotUIorcommandlineUCONFtools.
Forexample,tochangetheuserinterfaceport:
CFTUTIL uconfset id=copilot.general.serverport,value=1766
Configuration
BeforeyoucanstartTransferCFTforthefirsttime,TransferCFTmusthaveabasicconfiguration.
Typicallythisiscreatedduringinstallationormigration.
License key
Ifyoudidnotenterthelicensekeyduringinstallation,youcanenteritpostinstallationinacft.key
filein:<CFTDIRRUNTIME>/conf/
Youcanenterasinglekeyoralistofkeysinthisfile.Intheconfigurationdefaultfile,thevariable
<$CFTKEY>representsthecft.keyfile.
Transfer CFT internal datafile and

configuration
Checkthevalues,especiallythekeyvalue,hostname,andportforTCP,inthefollowingfile:
l WindowsandUNIX:<CFTRUNTIME>/conf/cft-tcp.conf
StarttheTransferCFTprofileand,tocreatetheTransferCFTinternaldatafileandupdatethebasic
configuration,execute:
cftinit cft-tcp.conf
Toupdatetheconfigurationatalaterdate,execute:
cftupdate cft-tcp.conf
User interface configuration

ToviewtheCopilotuserinterfacec onfiguration,execute:
CFTUTIL LISTUCONF id=copilot*

3 Post-installation
Tochangethisconfiguration,youupdatethehostnameandlisteningp ortforTransferCFTUIusing
CFTUTILuconfset.
Example
CFTUTIL uconfset id=copilot.general.serverhost, value="127.0.0.1"

CFTUTIL uconfset id=copilot.general.serverport, value="7000"
RefertotheTransferCFTUserGuidefordetails.
Configuration for Service Mode

ThisoptionisonlyavailableonWindowssystemsandmustbeselectedduringtheinstallation
processconfiguration.
Start the Transfer CFTCopilot server

IfyouhaveimplementedCentralGovernance,startingCopilotlaunchestheregistrationprocess.For
moreinformation,seethetopicRegisteringwithCentralGovernanceintheTransferCFTUserGuide
Windows
1. Changed irectorytotheruntime.
2. Executeprofile.bat.
3. TostarttheCopilotserver,enter:copstart
4. TochecktheCopilotstatus,enter:copstatus-v
Start Transfer CFT

IfyouhaveimplementedCentralGovernance,youcanstartandstopTransferCFTviatheCentral
UnifiedFlowManagementuserinterface.Otherwiseperformthefollowingcommandfromthe
TransferCFTruntimedirectory.
Enter:
cft start

Update
4
ThissectiondescribeshowtoupdateTransferCFTwithapatchorservicepack.Youcanmanually
performtheoperation,oruseCentralGovernance.
Formoreinformation,pleaserefertotheCentralGovernanced ocumentation.
Use Central Governance for updates

YoucaneasilyperformTransferCFTupdatesandapplyServicePacksusingCentralGovernance.
PleaseseetheCentralGovernancedocumentationfordetails.Howevernotethatyoucannotremove
SPorpatchesviatheCentralGovernanceinterface.
Installer or products patches and service

packs
Ifyouinstallaservicepackorpatchfortheinstaller,makesureallWindowsservicescreatedbythe
installerarestopped.
StopTransferCFTpriortoinstallingaservicepackorpatch.
Check product details

Tochecktheversion,orproductdetailspriortoupdating,usethedisplaycommand.
Thedisplaycommandlistsinformationaboutallinstalledproducts.
l Runthecommandfromtherootinstallationdirectory.
l Whenyourunthiscommandwithoutparameters,thecommandlistsallinstalledproductsand
versions,andallappliedservicepacks.
Usethenameparametertodisplaytheinstallationhistoryofasingleproduct.
Windows
display.bat
UNIX
./display.sh

4 Update
Windows updates
Thesameuserthatdidtheinitialinstallation(oratleastthesametypeofuser)muststarttheupdate
procedure.
SystemAccount).
<domain>\<username>
orthe<hostname>.
Example
Local user: user1

.\user1
<hostname>\user1
Network user: user2
<domain_name>\user2
Update procedure in GUI mode

1. DownloadproductupdatesfromtheAxwaysupportwebsiteathttps://support.axway.com/to
themachineyouwanttoupdate.
2. Stoptheserversthatyouwanttochange.
3. Runtheinstallerinupdatemode.Usethefollowingcommands:
l Windows:InWindowsStartmenu,selectAxwaySoftware>Axway<InstallationName>>Update
l UsingtheConsole:Changetotheinstallationdirectoryyouwanttoupdateandrunupdate.exe
4. Manageyourupdates.IntheUpdatesManagementpageyouhavethefollowingpossibilities:
l Selectadirectory:Selectthedirectoryorziparchivefilecontainingalltheupdatesyouwanttoinstall.
l Selectfile:Selecttheupdatefileyouwanttoinstall.Thefilecanbea.jarfileoraziparchiveof.jar
files.
Note Theinstallerallowsthe.zipfileformatcontainingtheServicePackstoapplytomorethan
oneproductinthesameinstallationpackage.
l Information:Clicktoopenthereadmefile.
5. ClickNexttocontinue.
6. Reviewtheupdatesyouwanttoinstall.

4 Update
7. Toapplytheupdate,clickUpdate.
8. Awarningmessageappears.ClickYestocontinue.
9. Aftertheupdatesareinstalled,clickNexttoviewthesummary.
10. ReviewthesummaryandclickOKtoexittheinstaller.
11. Viewlogfile.Theinstallationofupdatesaretrackedintheupdates.logfile,locatedinyour
homedirectory.
Remove an update
Thissectiondescribesuninstallingapatchorservicepack.YoucanuninstallupdatesinGUIor
consolemode,dependingonyouroperatingsystem.
Remove updates in GUI mode

1. Runtheinstallerinupdatemode.
IntheWindowsStartmenu,selectAxwaySoftware>Axway<InstallationName>>Update
2. OntheUpdatesManagementpage,SelecttheupdateyouwanttouninstallandclickRemove.
Theupdatechangesfrombluewhenfirstselectedtogray.
3. ClickNexttocontinue.
4. Reviewtheupdatesyouwanttouninstall.Toremovetheupdate,clickUpdate.
5. Aftertheupdateshavebeenuninstalled,clickNexttoviewthesummary.Itdisplaysthelistof
updatesthatwereremoved.
Remove updates in console mode

ForWindowsenvironment:
1. Fromtheinstallationrootdirectory,launchtheinstallerinupdatemode:update32.exemgui
orupdate64.exemguiifrunningona64-bitexecutable.
2. Followtheprecedingstepsforuninstallinganupdate.

Upgrade or migrate
5
Upgrade and migration overview
Thischapterisdesignedtoassistadministratorsoruserswhoaretaskedwithupgradingormigrating
fromanexistingTransferCFTversiontoTransferCFT3.2.2.
TheTransferCFTversionsthatareavailabletomigrateinclude2.3.2,2.4,2.5,2.6,2.7,3.0.1and
3.1.2.
Note IfyouaremigratingfromapreviousversionofTransferCFT,besuretochecktheRelease
Notesfornewfeaturesaswellasdeprecatedfeaturesandsupportedplatformsperrelease.
Migrating or upgrading to enable Central

Governance
CentralGovernancesimplifiesthemanagementofTransferCFTandprovidesidentityandaccess
management,certificatesecurityservices,monitoring,alerting,andwebdashboardservices.Central
GovernancereplacespossibleexistingservicesfromearlierTransferCFTinstallationsthatrequired
implementingandconfiguringmultipleproducts,suchasTransferCFTNavigator,PassPort,
Composer,andSentinel.
IfyouareperforminganupgradeormigrationtoTransferCFT3.2youcanthenusetheActivate
CentralUnifiedFlowManagementconnectivityinformationtoconfigureandregisterwithCentral
Governance.
Migration versus an upgrade
Migration options
TherearethreemethodsavailableforupdatingyourTransferCFTproductversion.
l Upgrade(existing)
l Automaticmigration
l Manualmigration
About upgrades
Anupgradeistheprocessofupdatingtoanewer,enhancedversionofthesoftware.

5 Upgrade or migrate
AxwayprovidesUpgradePacksforproductstosimplifytheprocessofupdatingfromaprevious
version.Whenupgrading,youruntheAxwayInstallertoapplytheUpgradePackusingaprocedure
thatissimilartoupdatinganAxwayproduct.Formoreinformation,gotoUpgradingTransferCFTor
UpgradingTransferCFTinmulti-nodearchitecture.
Thismodehasthefollowingadvantages:
l Allowsyoutoupdateinthesamelocation
l YoucanperformthisautomaticallyusingtheInstaller,andyoucanreverttopreviousstateif
needed
l ScriptsandAPIsremainintactandonlyrequirearecompilationfortheAPIs
Thismodehasthefollowingrestriction:
l Youmustuninstalltheupgradepackifyouneedtorollback.
l Youcannotupgradeonversionsolderthanversion2.6.x.
About migrations
AmigrationmeansthataninitialTransferCFTisinstalledinadirectorythatisnotremovedor
overwrittenbytheprocedure.YoucanusetheOS-appropriateinstallationkittoinstalltheTransfer
CFT3.2.2inanewdirectory,andselecttheinstallationoptiontomigratetheexistingconfiguration
tothisnewversion.Youareonlyrequiredtoprovidethep athoftheTransferCFT(n-1)versionto
retrievethisoldconfiguration.
Aboutinstallandautomaticimport
YoucanuseanautomaticinstallationproceduretomigratefromyourcurrentversionofTransfer
CFTtoTransferCFT3.2.2.Thisauto-migrationprocedureoccurswhenyouperformtheTransfer
CFT3.2.2installation.
l Thenewinstallationoccursinanewlocation,andexistingconfigurationelementsanddatacan
beautomaticallyimported
l Youcaninstallandautoimportfromversionsolderthanversion2.6.x.
l Youcanchoosetouseeitheroftheversions,ifneeded,incaseofanissuewithoneofthe
installations
Note Configurationanddata,suchasthecatalog,areintwoseparatelocationsanddataarenot
shared.
Thismodehasthefollowingrestriction:
l YoumustcopyscriptsandAPIsfromthepreviousversiontothenewinstallation.
About manual migrations

Amanualmigrationprocedure,alsousedformigratingyourexistingTransferCFTtoTransferCFT
3.2.2,isavailableanddescribedinthisdocument.

ThegeneralprocedureformigratingfromapreviousversionofTransferCFTtoTransferCFT3.2.2is
asfollows:
1. Exportexistinginformationfromthepreviousversion.Detailsvarydependingonthe
existingTransferCFTversion.
2. ImporttheexportedinformationintoTransferCFT3.2.2.
l Becauseitismanual,youcancustomizeasneeded.
l Youcanmanuallymigratefromversionsolderthanversion2.6.x.
Check product details

Tochecktheversion,orproductdetailspriortoupdating,usethedisplaycommand.
Windows
display.bat
UNIX
./display.sh
More information
IfyouencounterissueswhenmigratingTransferCFT,contactAxwaySupportat
https://support.axway.com.

Upgrade Transfer CFT

ThissectionexplainshowtoupgradeanexistingTransferCFTfrom2.6.x,2.7.x,3.0.1,3.1.3toa
TransferCFT3.2.2.Itbeginsbydetailingtheprerequisitesforastandalone(nonmulti-node)
upgrade.Fordetailsonupgradingamulti-nodeinstallation,seeUpgradeamulti-nodeinstallation
onpage64.
About upgrades
TransferCFT3.1.3introducedtheCUP,CompositeUpgradePackage,feature.Thisfunctionality
enablesyoutoupgradeboththeinstallerandtheproductsimultaneously.
Before you start

Beforebeginningtheupgradeprocedure:
l YourequiretheproductandInstallerversionnumberandSPlevelinordertochoosethe
appropriateprocedure.SeethesectionDeterminetheInstallerandproductversion.
l DownloadtheTransferCFTUpgradePack,availableonAxwaySupportat
https://support.axway.com.TheTransferCFTUpgradePacknamehasthegeneralformat
Transfer_CFT_3.2.2_UP****-from-3.1.3_*****_BN*****.zip,where**istheUP
number.
l StoptheTransferCFTserverandtheTransferCFTGUIserver,byentering:
o cftstop
o copstop-f
l DetermineyourAxwayinstallerandproductversions.Theversiondictateswhichofthe
followingTransferCFTupgradeproceduresiscorrectforyou.
Note Windows:Whenupgrading,thesametypeofuserthatdidtheinitialinstallationmust
starttheinstaller.
Determine the Installer and product version

YoushoulddeterminetheproductandInstallerversionandSPlevelpriortoupgrading.Youcanuse
thefollowingprocedureonanyversionoftheAxwayInstaller.FormoreinformationontheInstaller,
seealsoInstallerfunctionsonpage36andJREcustomizationonpage40.
StarttheAxwayInstaller.ThecommanddependsontheInstallerversionandyourOS,asfollows:
l Versionslowerthan4.5.x:
o Windows:setupwin32.exeupdate
o Unix:update.shupdate

l Version4.5.xorhigher:
o Windows:update32/64.exe
o Unix:update.sh
AcceptthelicenseandclickNext tocontinue.IntheProduct list,checkthe:
l AxwayInstallerversionandthemostrecentlyinstalledSPlevel
l TransferCFTversionandthemostrecentlyinstalledSPlevel
Display product information

Windows
display.bat
UNIX
./display.sh
Windows Application Experience recommendation

The"ApplicationExperience"serviceshouldbeenabledwhenusingTransfer
CFT.Otherwiseyoumayencounterissuesinaccessingfileswhen
installing/upgradingtheproduct.

Transfer CFT 2.6.4 to 3.2.2

Preconditions: Minimum versions for this procedure
Thisupgraderequiresthatyourcurrentinstallationisatleastattheversionlevelslistedbelow.Read
theBeforeyoustartp riortobeginningthisprocedure.
l TransferCFTversion:2.6.4_SP7
l AxwayInstallerversion:4.3.1_SP2
l EmbeddedJREversion:1.5.0_15
Note Remembertoupdatetheproductkeybetweenversions(aftercompletingtheupgrade).
Step 1: Upgrade to Axway Installer 4.4.0 SP8 or the latest SP
RuntheAxwayInstallerinupdatemode.Hereitisshowninthedefaultinstallationdirectory.
1. StarttheAxwaySynchronyInstallerinupdatemode,shownhereinthedefaultinstallation
directory:
Windows:C:\Axway\Synchrony\setupWIN32.exeupdate
Unix/Linux:***Axway/Synchrony/setupUNIX.shupdate
2. ApplytheSynchrony_Installer_4.4.0_UP7-from-4.3.1_win-x86-64_BN16272.jar.
3. StarttheAxwaySynchronyInstallerinupdatemode.
Windows:setupWIN32.exeupdate
Unix/Linux:setupUNIX.shupdate
4. ApplytheSynchrony_Installer_4.4.0_SP8_allOS_BN25804.jar.
Step 2: Upgrade to JRE 160
UsetheAxwayJREUpdateTooltoupgradetoJRE1.6.ThisAxwaytoolisavailableontheAxway
Supportsite.
1. UnziptheJREUpdateTool_4.4.0_Utility_*****_BN1205240348.zip.
Where*****representstheplatform
Example:JREUpdateTool_4.4.0_Utility_win-x86-64_BN1205240348.zip
2. UpgradetoJava1.6usingtheappropriatecommand:
Windows:<JRETOOLS_DIRECTORY_WITHOUT_BLANKS>\updatejre.bat
C:\Axway\Synchrony\
Unix/Linux:<JRETOOLS_DIRECTORY>/updatejre.sh/ home/user/Axway/Synchrony/
Step 3: Upgrade to Axway Installer 4.5.0 SP4 or the latest SP
RuntheAxwayInstallerinupdatemode.
1. StarttheAxwaySynchronyInstallerinupdatedmode:

2. ApplytheSynchrony_Installer_4.5.0_UP1-from-4.4.0-4.4.1_allOS_BN1204251050.jar.
3. StarttheAxwaySynchronyInstaller.
Note The program commands change in this step!

Windows:update32.exeo rupdate64.exe
Unix/Linux:update.sh
4. ApplytheAxway_Installer_4.5.0_SP4_allOS_BN22715.jar.
Step 4: Upgrade to JRE 160 update 37 using the JREUpdateTool
UsetheAxwayJREUpdateTooltoupdatetheJRE.
1. UnziptheJREUpdateTool_4.5.0_Utility_*****_BN1211090726.zip
Example:JREUpdateTool_4.5.0_Utility_win-x86-64_BN1211090726.zip
C:\Axway\Synchrony\
S tep 5: Upgrade to Axway Installer 4.8.0
1. StarttheAxwayInstaller.
2. ApplytheAxway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_*****_multiOS_BN2.jar.
Example:Axway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_win-x86_multiOS_
BN2.jar
Step 6: Upgrade to Transfer CFT 3.1.3
2. ApplytheTransfer_CFT_3.1.3_UP1-from-2.6.2-2.6.3-2.6.4-2.7.0-2.7.1-3.0.1-3.1.2_*****_
BN8294000.jar

Example:Transfer_CFT_3.1.3_UP1-from-2.6.2-2.6.3-2.6.4-2.7.0-2.7.1-3.0.1-3.1.2_
win-x86-64_BN8294000.jar
Step 7: Upgrade To the latest Transfer CFT 3.1.3 Service Pack
UsetheAxwayinstallerinupdatemode.
1. StarttheAxwayInstaller:
2. ApplytheTransfer_CFT_3.1.3_SP*****.zip
Where*****representstheSPlevelandthep latform
Forexample,Transfer_CFT_3.1.3_SP3_aix-power-64_BN8712000.zip)
Note Inthisstepyouareworkingwithazipfile(notajarfileasinearlierInstallerversions).Do
NOTunzip/uncompressthezipfile.
3. AddtheTransferCFT3.xlicensekeyintheconf/cft.keyfile.
Step 8: Upgrade to Transfer CFT 3.2.2 Upgrade Pack
UsetheAxwayInstallerinupdatemode.
2. ApplytheTransfer_CFT_3.2.2_UP****-from-3.1.3_*****_BN*****.zip.
Forexample,Transfer_CFT_3.2.2_UP1-from-3.1.3_aix-power-32_BN9815000.zip


Thisprocedurerequiresthatyourcurrentinstallationbeatleastatthelevelslistedbelow.
l TransferCFTversion2.7.1_SP10
l AxwayInstallerversion4.4.0_SP8or4.4.1_SP3
l EmbeddedJREversion:160
Note Remembertoupdatetheproductkeybetweenversionsafterupgrading.
Step 1: Upgrade to JRE 160
UsetheAxwayJREUpdateTooltoperformtheJREupdate.
Forexample,JREUpdateTool_4.4.0_Utility_win-x86-64_BN1205240348.zip
2. UsethefollowingcommandtoupgradetoJava1.6:
C:\Axway\Synchrony\
Unix/Linux<JRETOOLS_DIRECTORY>chmod755*.sh/updatejre.sh
/home/user/Axway/Synchrony
Step 2: Upgrade to the Axway Installer 4.5.0_SP4 or the latest SP
RuntheAxwayinstallerinupdatemode.
1. StarttheAxwaySynchronyInstaller:
2. ApplytheSynchrony_Installer_4.5.0_UP1-from-4.4.0-4.4.1_allOS_BN1204251050.jar.
Note The program commands change in this step!
4. ApplytheAxway_Installer_4.5.0_SP4_allOS_BN22715.jar.
Step 3: Upgrade to JRE 160 update 37
UsetheAxwayJREUpdateTooltoupdatetheJRElevel.

Forexample,JREUpdateTool_4.5.0_Utility_win-x86-64_BN1211090726.zip
C:\Axway\Synchrony\
Step 4: Upgrade to Axway Installer 4.8.0
2. ApplytheAxway_Installer_4.8.0_UP**-from-4.5.x-4.6.1-4.7.0_*****_multiOS_BN2.jar
Where**istheUPnumber,and*****representstheplatform.
Forexample,Axway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_win-x86_multiOS_
BN2.jar
BN8294000.jar
Forexample,Transfer_CFT_3.1.3_UP1-from-2.6.2-2.6.3-2.6.4-2.7.0-2.7.1-3.0.1-
3.1.2_win-x86-64_BN8294000.jar
Step 6: Upgrade to the latest Transfer CFT 3.1.3 Service Pack

Forexample,Transfer_CFT_3.1.3_SP3_aix-power-64_BN8712000.zip
Note Inthisstepyouarenowworkingwithazipfile(itwas.ajarinpreviousInstallerversions).
DoNOTunzip/uncompressthezipfile.



Thisprocedurerequiresthatyourcurrentinstallationisatleastatthelevelslistedbelow.
l TransferCFT3.0.1_SP9
l Installer4.5.0_SP4
l EmbeddedJREversion:JRE160
Note Remembertoupdatetheproductkeybetweenversions(aftercompletingtheupgrade).
UsetheAxwayInstallerinupdatemode:
2. ApplyAxway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_*****_multiOS_BN2.jar
Forexample,Axway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_win-x86_multiOS_
BN2.jar
2. ApplytheTransfer_CFT_3.1.3_UP**-from-2.6.2-2.6.3-2.6.4-2.7.0-2.7.1-3.0.1-3.1.2_*****_
BN8294000.jar
Where**istheUPversionand*****representstheplatform.
win-x86-64_BN8294000.jar

Example:Transfer_CFT_3.1.3_SP3_aix-power-64_BN8712000.zip
Note Inthisstepyouareworkingwithazipfile(itwasajarinpreviousInstallerversions).Do


Thecurrentinstallationmustbeatleastatthelevelslistedbelow.
l TransferCFTversionis3.1.3
Note Remembertoupdatetheproductkeybetweenversions.
RuntheAxwayinstallerinupdatemode:
2. ApplytheAxway_Installer_4.8.0_UP**-from-4.5.x-4.6.1-4.7.0_*****_multiOS_BN2.jar
Where**istheUPversionand*****representstheplatform.
Example:Axway_Installer_4.8.0_UP2-from-4.5.x-4.6.1-4.7.0_win-x86_multiOS_
BN2.jar)
BN8294000.jar
win-x86-64_BN8294000.jar
1. LaunchtheAxwayInstaller
Example:Transfer_CFT_3.1.3_SP3_aix-power-64_BN8712000.zip

Note Inthisstepyouareworkingwithazipfile(andnotajarasinearlierInstallerversions).Do

Post upgrade
Aftercompletingtheupgradeprocedure,yourTransferCFT3.2.2theexecscriptsareoperational.
However,youmustrebuildbothyourexitsandAPIprograms.
Checking the new version

TochecktheTransferCFTversion,aswellasthelicensekeyandsysteminformation,enterthe
command:CFTUTILABOUT
Upgrade a multi-node installation

ThissectiondescribeshowtoupgradeTransferCFTfrom3.0.1or3.1.3multi-nodearchitecture
withmulti-hoststoTransferCFT3.2.2.
Prerequisites
l TransferCFTUpgradePackavailableathttps:\\support.axway.com
l StoptheTransferCFTserverandtheTransferCFTGUIserver,byentering:
o cftstop
o copstop-f
l YourequireAxwayInstaller4 .10orhigher
Procedure
ToupgradeTransferCFT3.0.1or3.1.3,installanUpgradePackusingthesameprocedureasfora
patchorservicepack,onehostatatime.SeetheversionspecificinstructionsintheUpgrade
section.
ForTransferCFTtheUpgradePacknamehasthegeneralformatTransfer_CFT_3.1.3_UP2-
from-2.6.2-2.6.3-2.6.4-2.7.0-2.7.1-3.0.1-3.1.2_linux-x86-64_BN8294001.jar.
YourTransferCFT3.2.2,execscripts,APIs,andExitsarenowoperational.OnceTransferCFThas
beenupgradedonahostyoucanstartthatinstance,thereisnoneedtowaituntilTransferCFTis
upgradedoneveryhost.
Check the new version


Prerequisites
Important information before performing a

migration procedure
l YoumustupdateyourTransferCFTtothemostrecentservicepackversion.
l UpgradetheAxwayInstallerto4.10,ifyouarenotatthisversionorhigher,priortoupgrading
yourTransferCFT3.2.2.
l Ifneeded,youcanuninstallanUpgradePack.Doingsorollsbacktothepreviousversionbefore
theupgrade,butalltransfersandconfigurationmodificationsthatwereperformedsincethe
upgradearelost.
l BackupTransferCFTbeforebeginninganupgradeormigrationprocedure.
l BeforebeginningtheupgradeormigrationprocedurestoptheexistingversionofTransferCFT
andtheGUIserver.
Caution ForversionspriortoandincludingTransferCFT2.6.4SP1,thereareexportissuesifyou
areusingintermediatecertificatesthathaveadifferentID.AfixwasdeliveredinTransfer
CFT2.6.4SP2andin2.4.1SP11tocorrectthisPKIexportissue.However,forTransfer
CFT2.5.1youmustuseyouroriginalPKIconfigurationandcorrespondingcertificates,
andmanuallyimporttheseintotheTransferCFT3.2.2PKIdatabase.
About license keys

Yourequireanewlicensekeyifyouaremigratingfromaversion2.xTransferCFTtoaversion3.x.
Note YourequireasmanykeysasinstancesofTransferCFTrunningatsametime,including
whenrunninginmulti-node.Forexample,twoTransferCFTinstancescannotrunatthe
sametime,onthesameserver,usingthesamelicensekey.
Windows x86 operating system prerequisite

RedistributablePackageforVisualStudio2013toprovidenecessarylibraryfiles(DLL)forthe
compiler:
Todownloadtheredistributionpackage,visit:VisualC++RedistributablePackagesforVisual
Studio2013
Note IftheredistributionpackageisalreadyinstalledonyourWindowssystem,thereisnoneed
toreinstall.

Install and auto import

TheinstallandautoimportoptionallowsyoutopreformanewTransferCFTinstallationandimport
configurationfilesanddatafromaexistingTransferCFTinstance.Duringtheprocedure,youcan
selectoptionsforyournewinstance,andadditionallycanselectwhichoftheavailabletypesofdata
andconfigurationelementsthatyouwanttoimport.
Note Previousversionsthatareavailableforautoimportingtheconfigurationdatainclude
v2.3.2,2.4,v2.5,v2.6,v2.7,v3.0.1andv3.1.2.
Yourequireanewlicensekeyifyouaremigratingfromaversion2.xTransferCFTtoaversion3.x.
General procedure
Inthisprocedure,runtheinstallertoperformanewTransferCFTinstallation.Duringthisprocess
youarepromptedwiththeoptionofimportingexistingdataandconfiguration.
Start your installation

BeginatypicalinstallationusingtheTransferCFT3.2.2installationinstructionsthatcorrespondto
youroperatingsystem.
Importing configuration and data

PendingtheexistingversionofTransferCFT,theinstallerwillproposeavailableimportoptions.
Auto import screens

Atthispointyoucanselecttomigrate.TheInstallerpageasksifyouwanttoimportdatafromyour
existingTransferCFTinstance.Inthefollowingscreenyoucanselectwhichtypesofdatayou'dlike
toimport.
1. SelectYes toperformanautomaticmigration.ClickNext.
2. Enterornavigatetothepathfortheexistingprofilefile(profile.batorprofile.sh)forversion2.5
andhigher.TheprofilefileshouldbelocatedintheruntimefolderoftheexistingTransferCFT
installation.
3. Clicktoselectconfigurationelementsandobjectsthatyouwanttoimportfromtheexisting
TransferCFTinstance.Youmustmanuallymigrateexecs,exits,andAPIs.

Identity
1. Youarepromptedtoconfirmthelocalinstancedetails.Modifyifnecessary,andclickNextto
continue.
2. Checkthelicensekey.
Post auto import

IfyouusedtheinstallandautoimportprocedurewithyourexistingTransferCFTtoTransferCFT
3.2.2,attheendoftheinstallationanewdirectorycalledmigrationiscreatedintheruntime
directory.Thisdirectorystoresalloftheinformationusedduringtheautoimportprocess.Youcan
modifytheextractedfilesand/ordirectory,andmanuallyre-importthisdataatanytime.
ThecontentsofthisAuto import directoryaredescribedinthefollowingtable.
File Directory Description of extracted data
cftcat.xml Catalogfile.
cftcom.xml Communicationmedia.
cft-conf.cfg TransferCFTgeneralconfiguration,whichisappliedto
thenewinstallation(containedinCFTPARM/CFTPART
internaldatafiles).
cft-conf- Containsfilepathdeclarationsfromthecft-conf.cfgfile
warning.txt thatwereusedintheformerTransferCFTenvironment
andthatcannotbeimportedintothenewinstallation.
cft-pki.cfg ThePKIconfigurationthatisappliedtothenew
installation(asofversion2.4).
PKIdirectory ContainsextractedSSLcertificates(pendingversion).
cft-uconf. Contains:
(sh/bat)
l UCONFparameters(asofV2.5.1)
or
l Sentinelparameters(TRKAPI.cfg-
V2.3.2andV2.4.x)
and/or
l Copilotparameters(copconf.ini-
V2.4.x)
ThisfileisusedtosetthenewinstallationUCONF
parameters.

cft-uconf- ContainsUCONFparameterssetbytheuserintheformer
warning.txt TransferCFTenvironmentandthatcannotbeimported
intothenewinstallation.
migration. Containsinstructionsonhowtore-importthecollected
(sh/bat) dataintoanewinstallation,andincludesthePKI,
generalconfiguration,UCONFparameters,catalogand
communicationmediafiles.
Auto import in multi-node architecture

ThissectiondescribeshowtoproceedtouseautoimportforTransferCFT3.0.1or3.1.2multi-node
inmulti-hosts.
Procedure
TheautomaticimportisperformedduringtheTransferCFT3.2.2installation.Duringthe
installation,dialogboxesletyouselectconfigurationdatafromtheexistingTransferCFTtoimport.
Whileinstallingfirstnodeonclusterarchitecture,youshouldopttoimportdatafromtheprevious
TransferCFTversion.Executetheprocedureasdescribedhere.Duringinstallationofadditional
nodes,theoptionofimportingdatafrompreviousversionofTransferCFTshouldnotbeselected.
IfyouchoosetomigrateyourexistingTransferCFTto3.2.2usingtheautomaticimportmethod,at
theendoftheinstallationanewdirectorycalledauto_importiscreatedintheruntimedirectory.
Thisdirectorystoresalloftheinformationusedduringtheinstallationandautoimport.Youcan
modifytheextractedfilesand/ordirectory,andmanuallyre-importthisdataatanytime.
IfyouareinstallingandperforminganautoimportfromaTransferCFTwithmulti-nodearchitecture
enabled,thecontentsoftheAuto importdirectoryareasfollows.
cftcatXX.xml Catalogfiles.XXrepresentsthenodenumber,from00
toTotal_Number_of_Nodes-1.
cftcom.xml Communicationmediafornodemanager.
cftcomXX.xml Communicationmediafornodes.XXrepresentsthe
nodenumber,from00toTotal_Number_of_Nodes-1.
cft-conf.cfg TransferCFTgeneralconfiguration,whichisappliedto
thenewinstallation(containedinCFTPARM/CFTPART
internaldatafiles).

cft-conf- Containsfilepathdeclarationsfromthecft-conf.cfgfile
warning.txt thatwereusedintheformerTransferCFTenvironment
andthatcannotbeimportedintothenewinstallation.
cft-pki.cfg ThePKIconfigurationthatisappliedtothenew
installation,asofversion2.4.
PKIdirectory ContainsextractedSSLcertificates(pendingversion).
cft-uconf. Contains:
(sh/bat)
l UCONFparameters(asofV2.5.1)
-or-
l Sentinelparameters(TRKAPI.cfg-
V2.3.2andV2.4.x)
-and/or-
l Copilotparameters(copconf.ini-
V2.4.x)
ThisfileisusedtosetthenewinstallationUCONF
parameters.
cft-uconf- ContainsUCONFparameterssetbytheuserinthe
warning.txt formerTransferCFTenvironmentandthatcannotbe
importedintothenewinstallation.
migration. Containsinstructionsonhowtore-importthecollected
(sh/bat) dataintoanewinstallation,andincludesthePKI,
generalconfiguration,UCONFparameters,catalogand
communicationmediafiles.
Perform a manual migration
Prerequisites
Install Transfer CFT 3.2.2

PerformaTransferCFTinstallation,asdescribedintheOS-specificinstallationsection.
Note DonotusetheInstallandautoimportoptionavailableintheInstaller.
AfterperformingaTransferCFT3.2.2,youshouldupdatethetothemostrecentservicepack.

Load the environment

Beforebeginningthemanualmigrationprocedure,youmustloadtheoldTransfer
CFTenvironment.
Windows procedure
Transfer CFT 2.3.2 and 2.4

ThereisnoprofilefileforTransferCFT2.3.2or2.4inWindows.
Toexecuteacommandyoumustbeinthecorrectdirectory.Therefore,beforestartingthe
migration,changethedirectorytotheversion-appropriateTransferCFTinstallationdirectory.
Transfer CFT 2.5 and higher

Fromtheconsole,changethedirectorytotheTransferCFTruntimedirectoryandexecutetheprofile
fileusingthecommand:profile.bat
Afterloadingtheprofile,youcanexecutecommandsfromanywhere.
Migrating from Transfer CFT 2.3.2

ThistopicdescribeshowtomigrateTransferCFT2.3.2to3.2.2.
Migrating the configuration
Migrating the main configuration

MigratePARM,PART,IDFandotherstaticconfigurationobjects.
1. LoadtheTransferCFT2.3.2environment.SeethePrerequisitesonpage69fordetails.
2. ExportyourstaticconfigurationobjectsusingthecommandCFTUTILCFTEXT.Enter:
CFTUTIL CFTEXT type=all, fout=cft-extract.conf
3. Opentheextractconfigurationfiles,cft-extract.conf,andupdatethefilepathswith
thoseoftheTransferCFT3.2.2installation.
4. LoadtheTransferCFT3.2.2environment.
5. Importyourstaticconfigurationobjectsusingthecftinitcommand.Enter:
cftinit cft-extract.conf

Migrating trkapi.cfg file parameters

1. Inthetrkapi.cfgfile,selecttheparametersyouwanttoimportinto3.2.2.
2. Createascriptfile,forexample:
o Windows:trkapi-import.bat
3. Foreachparameteryouselect,addaUCONFcommandlinetoyournewscriptfile
usingtheformat:UCONFSETid=<parameter_id>,value=<value>
4. UsetheparametermappingbetweentrkapiandUCONF,aslistedinthefollowing
table,tospecifythecorrectparameterid.
Parametermappingbetweenthetrkapi.cfgfileandUCONF
Parameter in trkapi.cfg Parameter names in UCONF
TRACE sentinel.trktrace
TRKGMTDIFF sentinel.trkgmtdiff
TRKIPADDR_BKUP sentinel.trkipaddr_bkup
TRKIPPORT sentinel.trkipport
TRKIPPORT_BKUP sentinel.trkipport_bkup
TRKLOCALADDR sentinel.trklocaladdr
TRKPRODUCTNAME sentinel.trkproductname
XFB.BufferSize sentinel.xfb.buffer_size
XFB.Log(UNIX) sentinel.xfb.log
XFBLOG(Windows) sentinel.xfb.log
XFB.Sentinel sentinel.xfb.enable
XFB.Trace sentinel.xfb.trace
XFB.Transfer sentinel.xfb.transfer
LoadtheTransferCFT3.2.2environment.
5. ImporttheselectedUCONFparametersusingthecommandCFTUTIL.Replace<script_
filename>withthenewscriptfilepath:CFTUTIL<prefix_character><script_
filename>
Example
l Windows:CFTUTIL#trkapi-import.bat

Migrating PKI certificates

ExportingPKIcertificatesfromTransferCFT2.3.2isnotsupported.Forthisreason,youmustcreate
anewPKIdatabaseintheTransferCFT3.2.2runtimeusingthePKIUTILPKIFILEcommand.Next
importeachcertificateusingthePKIUTILPKICERcommand.
Formoreinformation,refertotheTransferCFT3.2.2User'sGuide,sectionsUsingthePKIFILE
commandandUsingthePKICERcommand.
Migrating the runtime environment
Migrating the catalog

2. ExportthecatalogusingthecommandCFTMI230:
CFTMI230 MIGR type=CAT, direct=FROMCAT, ifname=<catalog_2.3.2_

filename>, ofname=catalog_output.xml
3. ImportthecatalogusingthecommandCFTMI.Replacethe<catalog_filename_new_
installation>withthecorrespondingenvironmentalvariable:
o Windows:$CFTCATA
CFTMI MIGR type=CAT, direct=TOCAT, ifname=catalog_output.xml,

ofname=<catalog_filename_new_installation>
Migrating the communication media files

2. ExportthecommunicationmediafileusingcommandCFTMI230:
CFTMI230MIGRtype=COM,direct=FROMCOM,ifname=<com_2.3.2_filename>,ofname=com_
output.xml
3. ImportthecommunicationmediafileusingcommandCFTMI.Replacethe<com_
filename_new_installation>withthesystem-specificenvironmentvariable:
o Windows:$CFTCOM
CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput.xml, ofname=<com_

filename_new_installation>

Migrating from Transfer CFT 2.4

ThistopicdescribeshowtomigratefromTransferCFT2.4toversion3.2.2.Beforestartingthis
migrationprocedureyoumustperformthestepsdescribedinBeforeyoustart.

1. LoadtheTransferCFT2.4environment.SeethePrerequisitesonpage69fordetails.
2. ExportyourstaticconfigurationobjectsusingthecommandCFTUTILCFTEXT.
Enter:CFTUTILCFTEXTtype=all,fout=cft-extract.conf
thoseoftheTransferCFT3.2.2installation.
Migrating trkapi.cfg file parameters

MigratetheparametersfromtheTransferCFT2.4trkapi.cfgfile.
1. Inthetrkapi.cfgfile,selecttheparametersyouwanttoimportin3.2.2.
o Windows:trkapi-import.bat
3. Foreachparameteryouselect,addaUCONFcommandlinetoyournewscriptfile
usingtheformat:
UCONFSET id=<parameter_id>, value=<value>
UsetheparametermappingbetweentrkapiandUCONF,aslistedinthefollowingtable,tospecify
thecorrectparameterid.
Table 2. Parameter mapping between the trkapi.cfg file and UCONF
TRACE sentinel.trktrace

TRKGMTDIFF sentinel.trkgmtdiff
TRKIPADDR_BKUP sentinel.trkipaddr_bkup
TRKIPPORT sentinel.trkipport
TRKIPPORT_BKUP sentinel.trkipport_bkup
TRKLOCALADDR sentinel.trklocaladdr
TRKPRODUCTNAME sentinel.trkproductname
XFB.BufferSize sentinel.xfb.buffer_size
XFB.Log(UNIX) sentinel.xfb.log
XFBLOG(Windows) sentinel.xfb.log
XFB.Sentinel sentinel.xfb.enable
XFB.Trace sentinel.xfb.trace
XFB.Transfer sentinel.xfb.transfer
5. ImporttheselectedUCONFparametersusingthecommandCFTUTIL.Replace<script_
filename>withthenewscriptfilepath.
CFTUTIL <prefix_character><script_filename>
Example
l Windows:CFTUTIL#trkapi-import.bat
Migrating copconf.ini parameters

MigrateparametersfromtheTransferCFT2.4copconf.inifile.
1. Fromthecopconf.inifile,selecttheparametersyouwanttoimportintoversion3.2.2.
o Windows:copconf-import.bat
3. ForeachselectedparameteraddaUCONFcommandlineinyournewscriptfileusing
theformat:
UCONFSETid=<parameter_id>,value=<value>

UsetheparametersmappingbetweencopconfandUCONFaslistedinthefollowingtabletospecify
thecorrectparameterid.
Table 3. Parameter mapping between copconf file and UCONF
Parameter in copconf.ini Parameter name in UCONF
BatchList copilot.batches
CFTCOM copilot.cft.com
CFTMEDIACOM copilot.cft.mediacom
ChildProcessTimeout copilot.misc.childprocesstimeout
HttpRootDir copilot.http.httprootdir
MinNbProcessReady copilot.misc.minnbprocessready
NbProcessToStart copilot.misc.nbprocesstostart
NBWAITCFTCATA copilot.cft.nbwaitcftcata
ServerHost copilot.general.serverhost
ServerPort copilot.general.serverport
SslCertFile copilot.ssl.sslcertfile
SslCertPassword copilot.ssl.sslcertpassword
SslKeyFile copilot.ssl.sslkeyfile
SslKeyPassword copilot.ssl.sslkeypassword
TcpTimeout copilot.misc.tcptimeout
TIMERWAITCFTCATA copilot.cft.timerwaitcftcata
TrcMaxLen copilot.trace.trcmaxlen
TrcType copilot.trace.trctype
wlogComment copilot.batches.wlog.comment
wlogParams copilot.batches.wlog.params
WsiComplience copilot.webservices.wsicomplience

5. ImporttheselectedUCONFparametersusingthecommandCFTUTIL.Replacethe
<script_filename>withthenewscriptfilepath.
Example
l Windows:CFTUTIL#copconf-import.bat

YoumustbeatTransferCFT2.4.1SP5orhigherbeforeperformingthisprocedure.
1. LoadtheTransferCFT2.4environment.
2. ExportyourPKIcertificatesusingthecommandPKIUTILPKIEXT:
PKIUTIL PKIEXT fout=pki-extract.conf
3. LoadthenewTransferCFT3.2.2environment.
4. CreateanewPKIinternaldatafileusingthecommandPKIUTILPKIFILE.Replace<pki_
database_filename>withtheappropriatevariable:
o Windows:TheabsolutepathvaluefortheCFTPKUenvironmentvariable
PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE
5. ImportyourPKIcertificatesintoTransferCFT3.2.2usingthecommandPKIUTIL.
Replacethe<script_filename>withthenewscriptfilepath.
PKIUTIL <prefix_character><script_filename>
Example
l Windows:PKIUTIL#pki-extract.conf

1. LoadtheTransferCFT2.4environment.
CFTMI240 MIGR type=CAT, direct=FROMCAT, ifname=<catalog_2.4_filename>,

ofname=catalog_output.xml

installation>withthecorrespondingenvironmentvariable:
o Windows:$CFTCATA


1. LoadtheTransferCFTV2.4environment.
CFTMI240 MIGR type=COM, direct=FROMCOM, ifname=<com_2.4_filename>,

ofname=com_output.xml
3. LoadTransferCFT3.2.2environment.
4. ImportthecommunicationmediafileusingcommandCFTMI.Replace<com_
filename_new_installation>withthecorrespondingenvironmentvariable:
o Windows:$CFTCOM

Migrate from Transfer CFT2.5 or 2.6

ThistopicdescribeshowtomigrateTransferCFT2.5or2.6toversion3.2.2.
Migrate the configuration

1. LoadtheformerTransferCFT(2.5or2.6)environment.SeethePrerequisitesonpage
69fordetails.
thoseofthenewTransferCFT3.2.2installation.

5. Importyourstaticconfigurationobjectsusingthecftinitcommand.
6. Enter:
Migrating UCONF parameters

1. LoadtheformerTransferCFT(2.5or2.6)environment.
2. DisplayyourUCONFparametersusingtheCFTUTILLISTUCONFcommand.Enter:
CFTUTILLISTUCONFscope=user
3. SelecttheUCONFparametersthatyouwanttoimportintothenewTransferCFT3.2.2.
4. Createascriptfilesuchas:
l Windows:uconf-import.bat
5. Foreachparameteryouselect,addalinetothenewscriptfileintheformat:
UCONFSET id=<parameter_id>, value=<value>
7. ImporttheselectedUCONFparametersusingthescriptfileandtheCFTUTIL
command.Replacethe<script_filename>withthenewscriptfilepath:
Example
l Windows:CFTUTIL#uconf-import.bat

ForTransferCFT2.5,youmustbeatTransferCFT2.5.1SP2orhigherbeforeperformingthis
procedure.ForTransferCFT2.6.4,youmustbeatTransferCFT2.6.4SP2orhigherbefore
performingthisprocedure.
1. LoadtheformerTransferCFTenvironment(2.5or2.6).
2. ExportyourPKIcertificatesusingthecommandPKIUTILPKIEXT:PKIUTILPKIEXT
fout=pki-extract.conf
database_filename>withtheappropriatevalue:PKIUTILPKIFILEfname=<pki_
database_filename>,mode='CREATE
l Windows:TheabsolutepathvaluefortheCFTPKUenvironmentvariable

5. ImportyourPKIcertificatesintothenewTransferCFT3.2.2usingthecommand
PKIUTIL.Replacethe<script_filename>withthenewscriptfilepath:PKIUTIL
<prefix_character><script_filename>
Example
l Windows:PKIUTIL#pki-extract.conf

2. ExportthecatalogusingthecommandCFTMI240.

l Windows:$CFTCATA
Table 4. Example


CFTMI240 MIGR type=COM, direct=FROMCOM, ifname=<com_2.5_filename>,

o Windows:$CFTCOM

Table 5. Example

Migrating from Transfer CFT 2.6.4 SP2 or 2.7

ThistopicdescribeshowtomigrateTransferCFT2.6.4SP2,orhigher,or2.7toversion3.2.2.
Migrating the main configuration and UCONF

parameters
YoucanmigratethePARM,PART,IDF,otherstaticconfigurationobjectsandUCONFparametersas
follows:
1. LoadtheformerTransferCFTenvironment.SeethePrerequisitesonpage69for
details.
2. ExportyourstaticconfigurationobjectsusingthecommandCFTUTILCFTEXT.
Enter:

1. LoadtheformerTransferCFT(2.6.4or2.7)environment.
2. ExportyourPKIcertificatesusingthecommandPKIUTILPKIEXT.Enter:
database_filename>withtheOSappropriatevalue:
l UNIX:$CFTPKU

l Windows:TheabsolutepathvaluefortheCFTPKUenvironmentvariable:
PKIUTILPKIFILEfname=<pki_database_filename>,mode='CREATE
5. ImportyourPKIcertificatesintothenewTransferCFT3.2.2usingthecommand
PKIUTIL.Replacethe<script_filename>withthenewscriptfilepath:
PKIUTIL <prefix_character><script_filename>
Examples
Windows:PKIUTIL#pki-extract.conf

1. LoadtheformerTransferCFT(2.6.4or2.7)environment.

l Windows:$CFTCATA
Example


1. LoadtheformerTransferCFT(2.6.4or2.7.0)environment.
CFTMI240 MIGR type=COM, direct=FROMCOM, ifname=<com_2.7.0_filename>,

l Windows:$CFTCOM

Example

Migrating from Transfer CFT 3.0.1 or 3.1.2

ThistopicdescribeshowtomigrateTransferCFT3.0.1or3.1.2toversion3.2.2.Itisdividedin2
sections,thefirstsectiondescribesmigrationforasinglenodearchitecture,andthesecondsection
multi-nodearchitecture.Lastlythereareinstructionsexplainingwhatwouldbeneededtomigrate
fromsinglenodearchitecturetomultinodearchitecture.
Single node architecture
Migrating the main configuration and UCONF parameters

MigratePARM,PART,IDF,otherstaticconfigurationobjectsandUCONFparametersasfollows:
1. LoadformerTransferCFT3.0.1or3.1.2environment.SeethePrerequisitesonpage
69fordetails.

1. LoadformerTransferCFT3.0.1or3.1.2environment.
2. ExportyourPKIcertificatesusingthecommandPKIUTILPKIEXT.Enter:

database_filename>withtheappropriatevalue:theabsolutepathvalueforthe
CFTPKUforWindows.Enter:
Replacethe<prefix_character>basedonyoursystem,@forUNIXand#for
Windows.
Enter:
PKIUTIL <prefix_character>pki-extract.conf

2. ExportthecatalogusingthecommandCFTMI.Replacethe<catalog_filename>with
thecorrespondingenvironmentvariable,_CFTCATAforUNIXor$CFTCATAfor
Windows.Enter:
CFTMI MIGR type=CAT, direct=FROMCAT, ifname=<catalog_filename_former_

cft>, ofname=catalog_output.xml
4. ImportthecatalogusingthecommandCFTMI.Replacethe<catalog_filename>with
thecorrespondingenvironmentvariable,_CFTCATAforUNIXor$CFTCATAfor
Windows.Enter:
CFTM MIGR type=CAT, direct=TOCAT, ifname=catalog_output.xml,

ofname=<catalog_filename_new_cft >

2. ExportthecommunicationmediafileusingcommandCFTMI.Replacethe<com_
filename>withthecorrespondingenvironmentvariable,_CFTCOMforUNIX,or
$CFTCOMforWindows.Enter:
CFTMI MIGR type=COM, direct=FROMCOM, ifname=<com_filename_former_cft>,


filename>withthecorrespondingenvironmentvariable,_CFTCOMforUNIXor
$CFTCOMforWindows.Enter:

filename_new_cft >
Multi node architecture
Migrating the main configuration and UCONF parameters

MigratePARM,PART,IDF,otherstaticconfigurationobjectsandUCONFparametersasfollows:

2. ExportyourPKIcertificatesusingthecommandPKIUTILPKIEXT.Enter:PKIUTIL
PKIEXTfout=pki-extract.conf
database_filename>withtheappropriatevalue,$CFTPKUforUNIXortheabsolute
pathvaluefortheCFTPKUforWindows.Enter:

Replacethe<prefix_character>basedonyoursystem,@forUNIXand#for
Windows.Enter:
PKIUTIL <prefix_character>pki-extract.conf

2. Exportallcatalogs(onepernode,namedascftcataXX,whereXXisthenodenumber
withrangefrom00to<numberofnodes-1>)usingthecommandCFTMI.Foreach
catalog.Enter:
CFTMI MIGR type=CAT, direct=FROMCAT, ifname=<catalog_

filename_former_cft_for_node_<node>>, ofname=catalog_output_
<node>.xml
4. ImportallcatalogsusingthecommandCFTMIforeachofthem.Usethesamenode
numberonboth<node>oncommand.Enter:
CFTM MIGR type=CAT, direct=TOCAT, ifname=catalog_output_<node>.xml,

ofname=<catalog_filename_new_cft><node>

2. Exportallcommunicationmediafiles(cftcomandcftcomXX,whereXXisthenode
numberwithrangefrom00to<numberofnodes-1>)usingthecommandCFTMI.
Foreachcommunicationmediafile.
l Enter:CFTMIMIGRtype=COM,direct=FROMCOM,
ifname=<com_filename_for_node_manager_on_
former_cft>,ofname=com_output.xml
l Foreachnode,enter:CFTMIMIGRtype=COM,
direct=FROMCOM,ifname=<com_filename_for_
node_<node>_on_former_cft>,ofname=com_
output_<node>.xml

4. ImportallcommunicationmediafilesusingcommandCFTMIforeachofthem.Usethe
samenodenumberonboth<node>oncommand.
l Enter:CFTMIMIGRtype=COM,direct=TOCOM,
ifname=com_ouput.xml,ofname=<com_filename_
for_node_manager_on_new_cft>
l Foreachnode,enter:CFTMIMIGRtype=COM,
direct=TOCOM,ifname=com_ouput_<node>.xml,
ofname=<com_filename_for_node_<node>_on_
new_cft>
Single node architecture to Multi node architecture

Theonlydifferencebetweenmigratingfromsinglenodetomultinodearchitectureandmigrating
fromsinglenodetosinglenodearchitectureisthecatalogmigrationstep.Sincethereisnocatalog
namedcftcatainmulti-node,youshouldimportthecatalogexportedfromsinglenodearchitecture
tothecatalogofanyofthenodesinthemulti-nodearchitecture.
Activate Central Governance connectivity

CentralGovernancesimplifiesthemanagementofTransferCFTandprovidesidentityandaccess
management,certificatesecurityservices,monitoring,alerting,andwebdashboardservices.Central
GovernancereplacespossibleexistingservicesfromearlierTransferCFTinstallationsthatrequired
implementingandconfiguringmultipleproducts,suchasTransferCFTNavigator,PassPort,
Composer,andSentinel.
Youcanperformthisactivationprocedureonlyaftercompletinganupgradeormigrationto
TransferCFT3.2.
Overview
TherearetwowaystoactivateTransferCFTtoCentralGovernanceconnectivityfollowingan
upgradeprocedure:
l Automaticallyactivateconnectivityonpage87
l Manuallyactivateconnectivityonpage88
Additionalinformationandtasks:
l ConnecttoadifferentCentralGovernancesystemonpage90
l Useformerconfigurationobjectsonpage90
l Viewmanagedfeaturesonpage90

Automatically activate connectivity

UNIX/Windows
The automatic activation is only available in UNIX/Windows. Please refer to the

Manually activate connectivity on page 88 below for z/OS or IBM i instructions.
ThissectiondescribeshowtoruntheinstallerinconfiguremodetoenableCentralGovernance
connectivity.
Note IfrunninginWindows,thesameuserwhoperformedtheinitialinstallation(orsametype
ofuser)muststarttheinstaller.
Prerequisite
(missingorbadsnippet)
Procedure
1. StopTransferCFTandCopilot.
2. Starttheinstaller'sconfiguremode.
GUI
l UNIX:configure.shmgui
l Windows:InWindowsStartmenu,selectAxway Software > Axway [installation

name] > Configure
Console
l Windows:
3. Intheinstallerscreen,selectConfigure your existing installation.
4. Enterthelicensekeyifrequired.
5. AcceptormodifytheUIserverandservicemodescreenvalues.
6. IntheGovernance Modescreen,selectCentralGovernance.
7. IntheCG connectivityscreen,entertheCentralGovernancevalues.
8. ClickNext andcompletetheconfigureprocedure.
9. OncecompletedstartCopilot,whichautomaticallycompletestheregistrationprocess.
YoucancheckinCentralGovernancetoseethattheTransferCFTdisplaysintheProduct List.

Manually activate connectivity

All OS
ThissectiondescribeshowtomanuallymodifytheTransferCFTconfigurationtoenableCentral
Governanceconnectivityincommandline.
Prerequisites
1. StopTransferCFTandCopilotifrunning.
2. EnablingCentralGovernancec onnectivityafteranupgradeimpliesreplacinganystandalone
connectors.Therefor,priortoconnectingtoCentralGovernancedeactivateallpreviously
activatedconnectors,forexamplePassPortAM,PassPortPS,andSentinel.
CFTUTIL uconfunset id=am.type

CFTUTIL uconfunset id=sentinel.xfb.enable
CFTUTIL uconfset id=pki.type, value=cft
Note Whenrunninginaz/OSenvironmentyoumustadditionallysettheam.passport.superuser
withtheuserthatwillstarttheCopilotserver.
3. EnsurethatallUCONFvaluesusedtoidentifyaTransferCFTinstancearedefined.These
parametersinclude:
l cft.full_hostname
l cft.instance_id
l cft.instance_group
Usetheformat:
CFTUTIL uconfset id=cft.instance_id, value=<cft_id>
(missingorbadsnippet)
Procedure
Themanualprocedureconsistsofthefollowingsteps,whicharedetailedbelow:
1. IncludecertificatesinthePKIdatabase.
2. SettheUCONFparametervaluesforCentralGovernance.
3. EnableCentralGovernance.
4. StartCopilot.

Include certificates
YoumustincludethecertificateauthoritythatisusedtovalidatecommunicationwithCentral
GovernanceinthePKIdatabase.YoucanpersonalizethiscertificateontheCentralGovernanceside,
sobesuretousethecorrectiname inthepkicer command.
YoucanuseanyIDforthiscertificate.TransferCFTusesthecertificateIDdefinedinUCONFto
communicatewithCentralGovernance.
Note Modifythefilenamesyntaxtoaccommodateyourspecificplatform.
PKIUTIL pkicer id = 'CG_CA',

iform = 'PEM',
iname = '$CFTPKIDIR/passportCA.pem',
itype = 'ROOT',
pkifname = '$CFTPKU',
pkipassw = 'CFT',
state = 'ACT',
mode = 'CREATE'
AfterinsertingthecorrectcertificateinthePKIdatabase,definetheUCONFvariablecg.ca_cert_id.
ThisvalueisrequiredsothatTransferCFTknowswhichcertificatetousewhencommunicatingwith
CentralGovernance.
CFTUTIL uconfset id=cg.ca_cert_id, value='CG_CA'
Set UCONF values

UsetheCentralGovernanceinstallationvaluesforthefollowingUCONFsettings.TransferCFTuses
thesevaluestoidentifyCentralGovernance.
l cg.host
l cg.port
l cg.mutual_auth_port
l cg.shared_secret
Usetheformat:
CFTUTIL uconfset id=cg.host, value=<host_value>
Enable Central Governance
CFTUTIL uconfset id=cg.enable, value=yes

Register
StarttheTransferCFTCopilottotriggeranautomaticregistrationwithCentralGovernance.
YoucancheckintheCentralGovernanceProduct Listtoconfirmthattheregistrationwas
successful.
Connect to a different Central Governance

system
IfTransferCFTwaspreviouslyregisteredonaCentralGovernancesystembutyounowwantto
registeritonadifferentone,performthestepsinManuallyactivateconnectivityandasafinalstep,
priortostartingCopilot,resettheCentralGovernanceregistrationid.
CFTUTIL uconfunset id=cg.registration_id
Use former configuration objects

InCentralGovernanceyoucanusetheLegacy Flowsfeaturetoviewanduseanimported
configuration.Formoreinformation,pleaserefertotheCentralGovernancedocumentation.
View managed features

AftersuccessfullyupgradingandactivatingCentralGovernanceconnectivity,youcanmanagethe
followingTransferCFTfeaturesfromCentralGovernance.The"Supportedbutnotconfigurable"
columnlistsfeaturesthatyoucanretain,thoughyoucannotmanagethemfromtheCentral
Governanceinterface.
Feature Manage using Supported but not

Central Governance configurable using
Central Unified Flow
Management
Foldermonitoring yes(1) yes
Multi-nodearchitecture no yes
CRONJOB no yes
Exits no yes

Feature Manage using Supported but not

Central Governance configurable using
Central Unified Flow
Management
Network features
IPv6 yes yes
pTCP(UNIX/Windowsonly) yes yes
UDT(UNIX/Windowsonly) yes yes
SOCKS no yes
Heartbeat embedded yes
Interoperability
SecureRelay no yes
TrustedFile no yes
(NotavailableonIBMi)
PassPortAM embedded no(2)
PassPortPS no yes
Sentinel embedded yes
Composer no no
Protocols
PeSIT yes yes
ODETTE no yes
EBICS no yes
1. IBMiandz/OSonlysupportfoldermonitoringonUNIXfilesystems.
2. Ifyouperformamigrationorupgradefromapreviousversion,youmustmigrateyourPassPort
AM.

Post-migration procedure
Post manual migration or auto import

Ifyouperformedaninstallandautoimportoramanualmigration,youmustmanuallyimport
compiledobjectsandexecscriptsfromtheoldconfiguration.TherearenoTransferCFTcommands
toimportthesecompiledobjectsandexecscripts,andtheyarenotincludedintheautoimport
process.
Note Aftercompletinganupgradeoramigrationprocedure,youmustupdatetothemostrecent
SP.
Compiled objects:APIs and Exits

TomanuallymigrateyourAPIandexitbinaryfilesaftermigrating,copyyourprogram'ssourcecode
tothenewTransferCFT3.2.2runtimedirectoryandcompilethem.
1. CopytheAPIsourcecodeto<new_TransferCFT_3.2.2_installation_
dir>/runtime/src/capiandcompile.
2. CopytheExitsourcecodeto<new_TransferCFT_3.2.2_installation_
dir>/runtime/src/exitandcompile.
Exec scripts
Copytheexecscriptsto<new_TransferCFT_3.2.2_installation_dir>/runtime/exe.Itisimportant
thatyouupdateanypathsthatyouwereusingintheexecscriptstoreflectthenewinstallation
directory.
Post manual migration only
Migrating UCONF parameters from a previous Transfer

CFT version
YoumustmanuallymigrateUCONFparametersforversionspriortoTransferCFT2.5.1.TheUCONF
configurationreplacesthefollowingconfigurationfiles:
l Sentinelconfigurationfile(trkapi.cfg,trkapi.conf,andsoon...)
TheparametersintheSentinelfileareintegratedinUCONFassentinel.FORMER-PARAMETER-
NAME.Forexample,TRKTNAMEbecomessentinel.TRKTNAME.

l Copilotinifile( copconf.ini)
Thisfilenolongerexists.AllformerCopilotparametersarenamed
copilot.SECTION.PARAMETER-NAMEintheUCONFinterface.Forexample,theparameter
ServerPort,locatedinthegeneralsection,isnowcopilot.general.serverport.
l Theprofilefile,formerlyENV_CFTorcft.ini,nowusesUCONFtosettheenvironmentvariables.
Post upgrade
Ifyouperformedanupgrade,youneedonlyrecompileyourAPIsandExits.

Uninstall
6
ThistopicdescribeshowtouninstallTransferCFT.IfyouuninstallaTransferCFT,youwilllosethe
completeTransferCFTc onfiguration.Toavoidthis,saveyourenvironment(sample,exit,)before
removingtheTransferCFT.
About uninstalling in Windows

Thesameuserthatdidtheinitialinstallation(oratleastthesametypeofuser)muststartthe
uninstallprocedure.
SystemAccount).
<domain>\<username>
orthe<hostname>.
Example
Localuser:user1
.\user1
<hostname>\user1
Networkuser:user2
<domain_name>\user2
Beforeyoubeginuninstalling,youmuststoptheserversyouwanttouninstall.
1. YoucanruntheinstallerinuninstallmodeusingGUIorconsolemodeasfollows.Enter:
IfyouinstalledproductsonWindowsinservicemode,theinstallerremovestheservice.
GUI mode
Windows:IntheStartmenu,selectAxwaySoftware>Axway[installationname]>Uninstall
Console mode

6 Uninstall
Windows:
l uninstall32.exemconsole
l uninstall64.exemconsole
3. ClickUninstallwhenprompted.Awarningmessagedisplays;clickYes tocontinuewiththe
uninstall.
4. ClickNext toseetheuninstallsummary,andFinish toexit.

Deployment packages
7
Create a product deployment package
AproductdeploymentpackageinTransferCFTiscalledanExpressPackage.
TheExpressPackagesectiondescribeshowtocreateareusableanddistributableTransferCFT
packagetosimplifyandeasethetaskofinstallingandconfiguringTransferCFTsonmultipleservers
ofthesamearchitecture.
Note YoucanonlyinstallaTransferCFTExpressPackageonthesameplatformastheoneon
whichitwasgenerated.Forexample,aTransferCFTExpressPackagethatisgeneratedon
linux-x86-64canonlybeinstalledonalinux-x86-64platform.
Theprocedureconsistsof:
l InstallingatemplateTransferCFT3.2.2
l Configuringasrequiredtomeetyourbusinessneeds
l GeneratinganExpressPackagethatisbasedontheconfiguredtemplate
l OptionallycustomizingtheExpressPackage
l DeployingandinstallingtheExpressPackage
Install a template Transfer CFT

BeginbyinstallingaTransferCFTinstance,andconfigureasrequiredtomeetyourbusinessneeds.
ThisconfiguredTransferCFTservesasthetemplatefortheExpressPackageyouareabouttocreate.
Configurethe:
l Staticconfiguration,suchasprotocols(CFTPROT),networks(CFTNET),UCONFparameters,and
soon
l Partners(CFTPART,CFTTCP)
Note:Ifyoucreatepartnerstoexport,DONOTusetheNSPARTparameterintheCFTPART
definition.ThetargetTransferCFTwillinsteadusetheCFTPARMPART/NPARTvalues.
l Flows(CFTSENDandCFTRECV)
l SSLcertificates
l ProcessingscriptsandEXITs
l AdditionalAxwaycomponentsthatyouusewithTransferCFT,suchasCentralGovernance

7 Deployment packages
Note YoucanembedthecontentsoftheCFTDIRRUNTIME/binandCFTDIRRUNTIME/exec
directoriesinthegeneratedExpressPackage.
Generate the Express Package

TogenerateanExpressPackagefromthetemplateTransferCFT:
1. StoptheTransferCFTinstance.
2. NavigatetotheAxwayinstallationdirectoryofthetemplateTransferCFT,andruntheInstaller
inconfigurationmode.
Windows:ThedefaultAxwayinstallationdirectoryisC:\Axway.
Runtheconfigure32.exeorconfigure64.exeexecutabledependingon
theplatform.
3. TheInstallerwizarddisplays.IntheWelcome pageselectNext.
4. IntheConfiguration Typepage,selectCreate an Express Package.ClickNext to
continue.
5. SpecifythefilenameoftheTransferCFTinstallationpackagethatyouusedtoinstallthe
TransferCFTtemplate.
ThepackagenameformatisTransfer_CFT_<version>_Install_<platform>_
BN<buildNumber>.zip.
6. Optionally,specifythefilenameoftheservicepackand/orpatchtoembedintheExpress
Package.
o TheformatoftheservicepacknameisTransfer_CFT_<version>_SP<SPNumber>_
<platform>_BN<buildNumber>.jar.
o TheformatofthepatchnameisTransfer_CFT_<version>_
Patch<PatchNumber>_<platform>_BN<buildNumber>.jar.
7. EnterthepathtothelocationwhereyouwantthenewExpressPackagetobesavedonce
generated.
8. ClickNext tocontinue.
9. SelecttheconfigurationelementsthatyouwanttoincludeintheExpressPackage,suchasthe
partnersandparametersdatabase,theUCONFparameters,andthelocalPKIdatabase.Click
Next tocontinue.
Note 1:IfyouareusingCentralGovernance,youshouldonlyincludetheUCONFparameters
andthelocalPKIdatabase.TheotherconfigurationelementsaredeployedbyCentral
Governance.
Note 2:Ifyouselectedtheauto importfeatureduringtheTransferCFTtemplateinstallation,

youcanonlyincludetheCFTDIRRUNTIME/binandCFTDIRRUNTIME/execcontents.
10. IntheConfiguration confirmationpage,clickConfigure togeneratetheExpressPackage.

Results
TheExpressPackage,Transfer_CFT_<version>_ExpressPackage_<platform>_
<timestamp>.zip,isgeneratedandlocatedinthedirectoryyouselectedintheprevioussteps.
Customize the Express Package

YoucancustomizetheTransferCFTExpressPackagepriortodeployingandinstallingit.The
TransferCFTExpressPackageisnearlythesameastheTransferCFTInstallpackage,theonly
differencebeingtheadditionalExpressPackagedirectory.IfyouarenotcustomizingtheExpress
Package(forexampletheinstallationdirectories),youc anskipthissection.
TheExpressPackagedirectorycontainsthe:
l data directory:ThisdirectorycontainsthedataexportedfromtheTransferCFTtemplate.
o bin directory:ThisdirectorycontainsallfilesretrievedfromCFTDIRRUNTIME/bin.
o exec directory:ThisdirectorycontainsallfilesretrievedfromCFTDIRRUNTIME/exec.
o pki directory:Thisdirectorycontainsallexportedcertificates.
o cft-parm.cfg:Thisfilecontainsalloftheparameterdatabaseobjects( CFTPARM,CFTCAT,
CFTLOG,CFTSEND,CFTRECV,andsoon).
o cft-part.cfg:ThisfilecontainsalloftheexportedTransferCFTp artnerdatabaseobjects
(CFTPART,CFTTCP,andsoon).
o cft-cftparm.cfg:ThisfilecontainsonlytheCFTPARMobjectstobeimportedduringthe
ExpressPackageinstallation.
o cft-uconf.cfg:ThisfilecontainsanyUCONFparametersthatwereconfiguredinthe
templateTransferCFT.
o cft-pki.cfg:ThisfilecontainsallofthePKICERcommandstobeexecutedduringthe
TransferCFTExpressPackageinstallation.
l expressPackage.properties:Thisfilecontainsalloftheinstallationparametersthatcanbe
overwritten.Allparametersaredocumentedwithinthisfile.Topersonalizeanyofthese
parameters,uncommenttherespectivelineandaddthenewvalue.
l install executable:TheexecutabletoinstalltheExpressPackage.
TocustomizetheExpressPackagebeforedeployingit:
1. Unzipthepackagetoatemporarydirectory,forexampletempdir.
Windows
Unzipthepackageusingyourfavoriteziptool.
2. EdittheexpressPackage.propertiesfilelocatedintheExpressPackagedirectory,for
exampletempdir/ExpressPackage.Customizeinstallationparametersasneeded.

3. Rezipthepackage.
Windows
BrowsetotheExpressPackagedirectory,andzipallcontainedfilesintoapackage
namedTransfer_CFT_<version>_ExpressPackage_<platform>_
<timestamp>_new.zip (excludingtheoriginalzipfile).
Example: Install Transfer CFT in a different directory

Inthisexample,theTransferCFTtemplatewasinstalledinthe/home/cft/Axway/Transfer_CFT
directory.
ToinstallTransferCFTinadifferentdirectoryonthetargetserver,editthe
expressPackage.propertiesfile,uncomment,andsettheAxway_InstallDir,CFT_InstallDir,andCFT_
RuntimeDirparameters.
Axway_InstallDir = /opt/Axway
CFT_InstallDir = /opt/Axway/Transfer_CFT
CFT_RuntimeDir = /opt/Axway/Transfer_CFT/runtime
Example: Install Transfer CFT in the home directory of

different user accounts
Inthisexample,theTransferCFTtemplatewasinstalledonserver0 bytheuseraccounttest,inthe
/home/test/Axway/Transfer_CFTdirectory.
YoucaninstalltheTransferCFTonatargetserverinthehomedirectoryofdifferentuseraccountsin
agenericwayusingenvironmentvariables.EdittheexpressPackage.propertiesfile,uncomment,
andsettheAxway_InstallDir,CFT_InstallDir,andCFT_RuntimeDirparametersasfollows.
WINDOWS
Axway_InstallDir = %USERPROFILE%\axway
CFT_InstallDir = %USERPROFILE%\axway\cft
CFT_RuntimeDir = %USERPROFILE%\axway\cft\runtime
Install the Express Package

Note Windows only.Ifyouhaveimplementedafirewall,deactivatethefirewallpriorto
installation.
TodeployandinstalltheExpressPackage:

1. UploadthegeneratedTransfer_CFT_<version>_ExpressPackage_<platform>_
<timestamp>.zipfiletothetargetserver.
2. Unzipthepackage.
3. BrowsetotheExpressPackagedirectorylocatedwithintheunzippedpackage.
4. Runtheinstall executable.OnWindowsplatforms(7/2008/2012)youmustruntheinstall
executablewithadministratorrights.
Note Ifyouruntheinstall withoutanargument,theinstallexecutableusesthe

expressPackage.propertiesfile,intheExpressPackagedirectory,asthecustomizationfile.
IncommandlineyoucanspecifyadifferentfilenameusingthefollowingOS-specific
syntax.
Windows
install.exe <file name>
Limitations
l TransferCFTExpressPackagedoesnotsupportclustermodeinstallations.
l TransferCFTExpressPackagecannotembedaTransferCFTupgradepack.

Troubleshooting
8
Troubleshoot installation and registration
Thissectionlistssomepossiblepost-installationissuesalongwithcorrespondingcorrectiveactions
whenapplicable.Ifcorrectiveactionsdonotremedytheissue,checktheSupport toolssectionfor
moreinformation,orcontactAxwaySupportathttps://support.axway.com.
Copilot server issues
Copilot doesn't start

l Checkthattheportisnotalreadyusedbyanotherapplication.
l Closeallactivesessions,usethesyntax:copstop-f
l Checkthattherearenoorphan"cop*"processes.Ifthereare,manuallykilltheseprocesses.
Central Governance
Troubleshoot the registration

IfCopilotstarts,buttheTransferCFTeitherdoesnotdisplayintheCentralGovernance Product
Listorregistersinerror:
l VerifytheCentralGovernanceIPaddress(orFQDN)usedintheTransferCFTconfiguration.
l OnthecomputerrunningTransferCFT,checkthatyoucanreachCentralGovernanceattheIP
addressusedintheTransferCFTconfiguration.
l CheckthattheTransferCFTappearsintheCentralGovernancelogs.Ifnot,typicallythisis
becausetheTransferCFTisunablecontactCentralGovernance.
l InCentralGovernancecheckAdministration > ServicestoensurethatCentralGovernanceis
correctlystarted.
l VerifythesharedsecretforCentralGovernanceusedintheTransferCFTconfiguration.
Note SeetheCentralGovernancedocumentationforadditionalinformationanddetails.

8 Troubleshooting
Registration fails after installing in service mode when

using a firewall
Windows only, firewall enabled
TransferCFTcannotregisterinCentralGovernancewheninstallingCopilotinservicemode.
l Preventivemeasure:Deactivatethefirewalltoperformtheregistration.
l Workaround:Ifyouencounterthiserror,performthefollowingstepstoregister:
1. StoptheCopilotWindowsservice.
2. ManuallystarttheserviceinaDOSBOXtoregister.
3. AccepttheauthorizationfromtheWindowsfirewall.
Re-register with Central Governance

WhenCentralGovernancesendstheSSLcertificatestoTransferCFT,theuconf:cg.registration_id
parameterissettoapositiveinteger.Ifanerroroccurs,theregistrationprocessendsinerror.To
repeattheregistration,performthefollowingsteps:
1. StopTransferCFT.
2. StopCopilot.
3. Settheuconf:cg.registration_idtoitsdefaultvalue(-1)usingthecommand:
CFTUTIL uconfunset id=cg.registration_id
4. StarttheTransferCFTCopilot.Copilotstartstheregistrationprocess.
More information
FormoreinformationonCentralGovernance,refertotheCentralGovernance1.1.2documentation.
Transfer CFT server
Cannot start my Transfer CFT

l CheckmyTransferCFT'sloginCentralGovernance
l FromthelocalTransferCFTruntime,trytomanuallystarttheserver
o Ifyoucannotmanuallystarttheserver,refertoSupporttoolsSupporttoolsintheTransfer
CFTUserGuide.

8 Troubleshooting
Applying a license key

Windows
YouneedtoapplyavalidlicensekeytoTransferCFTinthefollowingsituations:
l YouperformaninitialTransferCFTinstallation.
l Toreplaceanexpiredlicensekey(typicallyafterayear).
Obtain a license key

1. InstallTransferCFT.YoucaninstallTransferCFTwithoutalicensekey,andenterthekey
afterward.
2. Aftercompletingtheinstallation,orforanexistinginstallation,usethec ommandcftutil
abouttoretrieveyoursysteminformation.
3. ContacttheAxwayFulfillmentteamattheappropriateemailaddress,andprovidethehostname
andsysteminformation.
l ForaUSkey,contact:fulfillment@us.axway.com
l ForanEMEAorAPACkey,contact:product.key@axway.com
Apply a license key

Toapplythelicensekey(s)fromtheAxwayFulfillmentteam,enterthepathtotheindirectionfile.
Placea#characterbeforethepath,forexampleKEY=#conf\cft.key.
l Thefilecancontainoneormultiplelicensekeys,butitmusthaveonekeyperline.
l Onstartupthefirstvalidkeyisused.
Example
UsetheCFTUTILutilitytoexecutetheaboutcommandtofindtheCPUID.
Cftutil about
* model =
* hostname = ITEM-12345
* cpuid = 000000000000E01A
Inthisexample,theCPUIDis 0E01A.Yourhostnameandcpuidwilldifferfromthe
example.

8 Troubleshooting
Support tools and contacting Support

Thissectiondescribesthetoolsavailabletohelpyoucollectinformationandcontactsupportifyou
areunabletotroubleshootanerrororissue.
Accessing the Axway Support site

FromAxwaySupportathttps://support.axway.com,clicktoselectContact usfortheemail
addressandphonenumberofyournearestAxwaysupportsite.
Opening a Support case

BeforecontactingCustomerSupport,wesuggestthatyoustartbyusingtheAxwayonlinepatch
librarytoseeifthereisapatchavailableforyourproblem,orbysearchingforasolutioninthe
KnowledgeDatabase.IfyoustillneedtocontactSupport,havethefollowinginformationavailable
ifpossible:
l Productversion
l Operatingsystem
l Cft_support
TosubmitaSupportrequest,youcandothefollowing:
l SubmitandtrackyourrequestthroughtheAxwaySupportsiteatsupport.axway.com.
l Eachtimeyousubmitasupportrequest,thatrequestisassignedauniquenumber.Usethis
specificnumberwhenyoucontactCustomerSupportconcerningthatcase.
l YoumusthaveauseraccounttosubmitaSupportrequest.
Using CFT_support
Thecft_supporttoolcollectsalloftheneededinformationfromthecustomer'sTransferCFT
installationenvironment,includingthestaticconfiguration(PARM/PART),UnifiedConfiguration
parameters(UCONF),cataloginformation,communicationmediafilestatus(CFTCOM),logfiles,
executionenvironment(variables),diskspace,andsoon.Thisinformationisthenpackagedintoa
archivefilecalledcft-support-<date>(.tar.gz|.zip).
Note Whenusingthecft_supporttoolonotherOperatingSystems,refertotheOS-specific
guideforthecorrectsyntax.
Using Copilot
FromtheUI,clickthe debugicon.ThereportissavedintheTransferCFTruntimedirectory,after
whichyouarepromptedtodownloadthereporttoyourdesktop.

8 Troubleshooting
Using command line
UNIX/Windows
Incommandlineenter:cft_support collect
Activating Transfer CFT traces when a problem occurs

during the transfer
Note ATMtracesareavailableonlywhenusingTransferCFTLocalAdministration.However
CentralGovernancemanagedTransferCFTistherecommendedversion.
TransferCFTtracesaremanagedbytheAdvancedTraceManager( ATM)component.ATMisa
problemresolutionassistancetoolthatisusedtosaveTransferCFTinformation,andretrieve
previouslysavedTransferCFTinformation.
YoumayneedtoinitiatetracinginordertoassistTransferCFTSupportserviceifanerroroccurs.
TheTransferCFTSupportservicecananalyzethetracestobetterhelpyouresolvetheissue.

Transfer CFT InstallationGuide Win en

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Transfer CFT InstallationGuide Win en

Încărcat de

Drepturi de autor:

Formate disponibile

INSTALLATION GUIDE

About Transfer CFT

Installation guide outline

Prepare and plan your installationDescribeswhatyoushouldplanfordeployingand

Transfer CFT 3.2.2 Installation and Operation Guide1

Troubleshoot the installation or registration processDescribesthedifferenttypesof

Who should read this guide

Transfer CFT documentation set

Transfer CFT 3.2.2 Installation and Operation Guide2

Accessibility features of the documentation

Screen reader support

Support for high contrast and accessible use

Transfer CFT 3.2.2 Installation and Operation Guide3

4Installation and Operation Guide Transfer CFT 3.2.2

End User License Agreement

Check your authorization

Transfer CFT 3.2.2 Installation and Operation Guide5

Windows x86 operating system

Transfer CFT 3.2.2 Installation and Operation Guide6

Transfer CFT 3.2.2 Installation and Operation Guide7

About the Transfer CFT environment

Supported operating systems and browsers

Disk space and RAM requirements

Secure RelayJava installation directory prerequisite

Transfer CFT 3.2.2 Installation and Operation Guide8

Installer screen resolution

Transfer CFT 3.2.2 Installation and Operation Guide9

Apply service pack or patch using Central Governance

Transfer CFT 3.2.2 Installation and Operation Guide10

Windows itanium installation

Cluster installation requirements

Create a mapped drive

net use Z: \\servername\sharedfolder /persistent:yes

Transfer CFT 3.2.2 Installation and Operation Guide11

Remove a mapped drive

net use Z: /delete

Transfer CFT 3.2.2 Installation and Operation Guide12

Table 1. Default ports by platform

Transfer CFT 3.2.2 Installation and Operation Guide13

Transfer CFT 3.2.2 Installation and Operation Guide14

Type Location Certificate Expires

Secure <Transfer_CFT>/home/distrib/xsr SecureRelayCA.pem November

Central <Transfer_CFT>/runtime/conf/pki passportCA.pem November

CRTPF FILE(YOURLIB/DER_CERT) RCDLEN(1191)

Transfer CFT 3.2.2 Installation and Operation Guide15

Installation package contents

Transfer CFT 3.2.2 Installation and Operation Guide16

Windows x86 operating system prerequisite

Transfer CFT 3.2.2 Installation and Operation Guide17

Install Transfer CFT

Start the installation

Transfer CFT 3.2.2 Installation and Operation Guide18

Transfer CFT 3.2.2 Installation and Operation Guide19

Transfer CFT 3.2.2 Installation and Operation Guide20

Transfer CFT 3.2.2 Installation and Operation Guide21

AxwayTransfer ClickInstall tocompletetheinstallationprocess,or

Transfer CFT 3.2.2 Installation and Operation Guide22

Cluster mode screens

Auto import screens

Transfer CFT 3.2.2 Installation and Operation Guide23

Transfer CFT 3.2.2 Installation and Operation Guide24

Transfer CFT 3.2.2 Installation and Operation Guide25

Transfer CFT 3.2.2 Installation and Operation Guide26