App Connect

 View Only
Expand all | Collapse all

Migration of ACP 7.5.4.0 to ACP 7.5.5.0 docker version

  • 1.  Migration of ACP 7.5.4.0 to ACP 7.5.5.0 docker version

    Posted Thu November 10, 2022 04:51 PM
    We want to plan migration of ACP 7.5.4.0 to ACP 7.5.5.0 docker version on RHEL VM on Azure.

    IBM already commented that upgrade is not possible hence new image and container needs to be created. I think there is no direct path.


    My queries are
    1. IBM has suggested to import and export project via extract from WMC else via par file. Which is better method and also how to get par files? Will it be available in running container?

    2. How setting applied on container running on ACP 7.5.4.0 can be applied to new container?

    3. To backout the changes I think only we need to switch the containers by stopping the new one and starting old one. Is my approach fine?

    Thanks in Advance

    GM

    ------------------------------
    Gaurang Maheshwari
    ------------------------------


  • 2.  RE: Migration of ACP 7.5.4.0 to ACP 7.5.5.0 docker version

    Posted Thu December 01, 2022 12:37 PM

    My Replies to queries are:
    1. IBM has suggested to import and export project via extract from WMC else via par file. Which is better method and also how to get par files? Will it be available in running container? 

    You can export all the project from the WMC - Repository - Configurations    Export the current repository (Up Arrow on Right)

    Then import the repository on new appliance.

    Ref: Exporting A Repository

    Ref: Importing A Repository

    Note: Docker does not have the Setting option on import only projects

    2. How setting applied on container running on ACP 7.5.4.0 can be applied to new container?

    Any settings will have to be manually applied as they were on the 7.5.4 ACP Docker from your command line


    3. To backout the changes I think only we need to switch the containers by stopping the new one and starting old one. Is my approach fine?

    Yes, you are correct. 

    Best option:
    docker restart <container id>



    ------------------------------
    Mark Dowdy
    ------------------------------