How can I migrate from Control-M for Advanced File Transfer  to Control-M Managed File Transfer ?

Version 4
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M Managed File Transfer


    COMPONENT:

    Control-M Managed File Transfer Enterprise


    APPLIES TO:

    Control-M Managed File Transfer Version 9.0.18 ; Control-M for Advanced File Transfer 7.0.00 and higher



    QUESTION:

    How can I migrate from Control-M for Advanced File Transfer (AFT) Version 7.0.00, 8.0.00, or 8.2.00 to Control-M Managed File Transfer (MFT) version 9.0.xx?


    ANSWER:



    Table showing the process of migrating from AFT to MFT

                                                                                                                                                      
    From AFT versionTo MFT version*
     
    Recommended Migration Path
    9.0.18.x9.0.19      
           
    • In place upgrade using the CCM Deployment
    •      
    • Any upgrade to MFT 9.0.19 must be done by first upgrading to MFT 9.0.18.x.
    •     
    7.0.00 or 8.0.009.0.18 and higher      
           
    1. On the Control-M V9.0.18 environment, install a new Control-M/Agent V9.0.18.  One of the requirements for AFT 8.2 is having a 64-bit Control-M/Agent. Since Control-M/Agent V7 is 32-bit, below is general plan to get to MFT V9.0.18.
    2.      
    3. Install AFT V8.0.00 + Fix Pack 1 on the new Control-M/Agent V9.0.18
    4.      
    5. Copy and Move AFT V7 data directory (ctm/cm/aft/data) from the old Control-M/Agent (V7) to the new Control-M/Agent V9.0.18 in the AFT V8 directory (ctm/cm/aft/data).
    6.      
    7. At this point AFT V8 Fix Pack 1 on the new Control-M/Agent can be upgraded to AFT V8.2, this will also convert the AFT accounts file (accounts.dat) to the new format (accounts.xml).
    8.      
    9. Once AFT is at V8.2, use the MFT Deployment in Control-M Configuration Manager V9.0.18 to upgrade AFT V8.2 to MFT V9.0.18 on the new Control-M/Agent V9.0.18)
    10.      
    11. Use MFT deployment to upgrade v9.0.18 to v9.0.19 and higher
    12.     
    8.2.00.xxx9.0.18 and higher      
           
    1. Install Control-M MFT 9.0.18 Deployment Package on Control-M/EM Server.
    2.      
    3. From the CCM, deploy it to the Control-M/Agent with Control-M for AFT 8.2.00.
    4.      
    5. Use MFT deployment to upgrade v9.0.18 to v9.0.19 and higher
    6.     
    7.0.00 or 8.0.009.0.00.1xx      
           
    1. Install Control-M MFT 9.0.00 Deployment Package on Control-M/EM Server.
    2.      
    3. From the CCM, deploy Control-M MFT 9.0.00 to the Control-M Agent with Control-M for AFT.
    4.      
    5. To verify a successful migration to version 9.0.00, you must verify that all connection profiles were loaded and migrated successfully.
    6.      
    7. Install Control-M MFT 9.0.00.100 Deployment Package on Control-M/EM Server.
    8.      
    9. From the CCM, deploy Control-M MFT 9.0.00.100 to the Control-M/Agent with Control-M MFT.
    10.      
    11. To verify a successful migration to version 9.0.00, you must verify that all connection profiles were loaded and migrated successfully.
    12.     
    8.2.00.xxx9.0.00.1xx      
           
    1. Install Control-M MFT 9.0.00 Deployment Package on Control-M/EM Server.
    2.      
    3. From the CCM, deploy Control-M MFT 9.0.00 to the Control-M Agent with Control-M for AFT.
    4.      
    5. Install the Control-M MFT 9.0.00.004 patch on the Control-M/Agent.
    6.      
    7. To verify a successful migration to version 9.0.00, you must verify that all connection profiles were loaded and migrated successfully.
    8.      
    9. Install Control-M MFT 9.0.00.100 Deployment Package on Control-M/EM Server.
    10.      
    11. From the CCM, deploy Control-M MFT 9.0.00.100 to the Control-M Agent with Control-M MFT.
    12.      
    13. To verify a successful migration to version 9.0.00, you must verify that all connection profiles were loaded and migrated successfully.
    14.     
       Notes:
    1. Before you upgrade, check the prerequisites for the relevant Control-M MFT version.
    2. SSL certificates must be manually imported to the cm/AFT/data/SSL/cert/aftkeystore.pfx file. For more information,  see the Control-M Administrator Guide.

      

     


    Article Number:

    000150994


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles