Customer Portal

Get Involved. Join the Conversation.

Topic

    Pramod Vasudeva Murthy
    What actually is CP migration?Answered
    Topic posted August 27, 2016 by Pramod Vasudeva MurthyBlack Diamond: 60,000+ Points, last edited August 27, 2016 
    257 Views, 4 Comments
    Title:
    What actually is CP migration?
    Content:

    Hi Folks,

    I have done good number of projects and read many documentations primarily to understand CP2 to CP3 migration.

    But I do have few questions left unanswered and would like to know more about this. Please help me with below questions:

    • Is CP 3.2.XX to any higher version is called CP Migration or is it completely different from my understanding?
    • After migrate how do we confirm that site has been migrated? At present, I am assuming that most of us will observe directory changes and folder structure changes(in Cyberduck) and also cross check in /ci/admin. If there are any other checks, please let me know.
    • I understand custom widgets cannot be migrated as is - but wondering what is the importance of "Would you like to copy customised files to version 3? Both options require you to edit your custom code after migration?" and "Yes[If you have significant custom code]" ?
    • Is DynamicformInput and DynamicProductInput deprecated in new version?

    My intension is to be aware of importance and know-how's of CP Migration than of actually migrating.Please help me understand these points.

    - VIP

    Version:
    May 2015

    Best Comment

    Barrilito van Dijk

    Hi Pramod,

    Good to see you have some questions based on interest in the product and the fact that you really want to understand it all, that is for me already a reason to spend some time on it! smiley

    Here are my few thoughts:

    • Is CP 3.2.XX to any higher version is called CP Migration or is it completely different from my understanding?
      It all depends what you define by "migration". I would think a migration is anything that has to be moved from A to B of where everything has to be changed/altered of replaced by something else. But in the end my question to you would be: "what does it matter how it is called?" The process from CP2 to CP3 I would definitely call a migration as lots has changed. And yes, from CP 3.2.XX to higher can have much impact as well. Is it a migration? Perhaps it is, I don't wonder about how to call it. In general I always call it an upgrade, I just look at the differences and try to estimate the time I need and try to upgrade it decently so each upgrade is up-to-date to minimize a next upgrade.
    • After migrate how do we confirm that site has been migrated? At present, I am assuming that most of us will observe directory changes and folder structure changes(in Cyberduck) and also cross check in /ci/admin. If there are any other checks, please let me know.
      When we have migrated / upgraded, you will indeed see file changes. You can always look at the dates etc of the files, and in big upgrades from old to new the entire file structure differs. But in the end it is simple, you do a deploy of the files and if that goes well, and if the logfiles have no errors then you will look first at the deployed customer portal. I think most of the upgrades always have some specific visual change that makes you know that you are looking at the new files. If not, then you should either trust that it has been deployed or perhaps show something new in the content to be sure, but I guess this is always the same issue you have whith each deployment.
    • I understand custom widgets cannot be migrated as is - but wondering what is the importance of "Would you like to copy customized files to version 3? Both options require you to edit your custom code after migration?" and "Yes[If you have significant custom code]"
      Good question!  Personally I am not a fan of the conversion tools. Sometimes it can be handy to look at processed code what is done with it. The questions of the tool are not realy very transparent (perhaps due the translation to the language of your interface). So many times you are doubtful about what options to choose. In the end you keep on editing files. And what has been copied or created is never what I want. Many times I choose to rebuild / rewrite it all or to just copy the old widget, make a "1.0" subdirectory and change some minor things in the logic file and controller file. In an upgrade my advise would be not to develope new things, but if you have a big change from CP2 to CP3 sometimes it is wise to start from scratch and just use the new standard code, it all depends on how much is customized and how well you can update widgets or rewrite them. Especially in the newer releases lots of things change, you suddenly have a result page, new search widgets with new search sources and all is (almost) responsive, etc. So to get back to the question, it does not makes so much sense to me, and I prefer not to wonder to much about it and just rebuild it all or use an older widget that works fine if it is a simple widget that uses basic stuff that will not change for years.
    • Is DynamicformInput and DynamicProductInput deprecated in new version?
      I would not know, not realy familiar with it. I have seen some posts about it, sometimes widgets are suddenly gone...

    In general I would like to add that wether something is a migration or not, or an upgrade or not, there is in practice always more to it then the theory states. And most of it depends (unfortunately) on your own creativity and trust.

    Nice discussion Pramod!

    Regards!

     

     

    Comment

     

    • Barrilito van Dijk

      Hi Pramod,

      Good to see you have some questions based on interest in the product and the fact that you really want to understand it all, that is for me already a reason to spend some time on it! smiley

      Here are my few thoughts:

      • Is CP 3.2.XX to any higher version is called CP Migration or is it completely different from my understanding?
        It all depends what you define by "migration". I would think a migration is anything that has to be moved from A to B of where everything has to be changed/altered of replaced by something else. But in the end my question to you would be: "what does it matter how it is called?" The process from CP2 to CP3 I would definitely call a migration as lots has changed. And yes, from CP 3.2.XX to higher can have much impact as well. Is it a migration? Perhaps it is, I don't wonder about how to call it. In general I always call it an upgrade, I just look at the differences and try to estimate the time I need and try to upgrade it decently so each upgrade is up-to-date to minimize a next upgrade.
      • After migrate how do we confirm that site has been migrated? At present, I am assuming that most of us will observe directory changes and folder structure changes(in Cyberduck) and also cross check in /ci/admin. If there are any other checks, please let me know.
        When we have migrated / upgraded, you will indeed see file changes. You can always look at the dates etc of the files, and in big upgrades from old to new the entire file structure differs. But in the end it is simple, you do a deploy of the files and if that goes well, and if the logfiles have no errors then you will look first at the deployed customer portal. I think most of the upgrades always have some specific visual change that makes you know that you are looking at the new files. If not, then you should either trust that it has been deployed or perhaps show something new in the content to be sure, but I guess this is always the same issue you have whith each deployment.
      • I understand custom widgets cannot be migrated as is - but wondering what is the importance of "Would you like to copy customized files to version 3? Both options require you to edit your custom code after migration?" and "Yes[If you have significant custom code]"
        Good question!  Personally I am not a fan of the conversion tools. Sometimes it can be handy to look at processed code what is done with it. The questions of the tool are not realy very transparent (perhaps due the translation to the language of your interface). So many times you are doubtful about what options to choose. In the end you keep on editing files. And what has been copied or created is never what I want. Many times I choose to rebuild / rewrite it all or to just copy the old widget, make a "1.0" subdirectory and change some minor things in the logic file and controller file. In an upgrade my advise would be not to develope new things, but if you have a big change from CP2 to CP3 sometimes it is wise to start from scratch and just use the new standard code, it all depends on how much is customized and how well you can update widgets or rewrite them. Especially in the newer releases lots of things change, you suddenly have a result page, new search widgets with new search sources and all is (almost) responsive, etc. So to get back to the question, it does not makes so much sense to me, and I prefer not to wonder to much about it and just rebuild it all or use an older widget that works fine if it is a simple widget that uses basic stuff that will not change for years.
      • Is DynamicformInput and DynamicProductInput deprecated in new version?
        I would not know, not realy familiar with it. I have seen some posts about it, sometimes widgets are suddenly gone...

      In general I would like to add that wether something is a migration or not, or an upgrade or not, there is in practice always more to it then the theory states. And most of it depends (unfortunately) on your own creativity and trust.

      Nice discussion Pramod!

      Regards!

       

       

    • Willie Eide

      Barrilito has a great answer above. I'll try to add a bit more color to it.

      • Is CP 3.2.XX to any higher version is called CP Migration or is it completely different from my understanding?
        • When talking about going from one version of CP to another, it is called a migration. It doesn't matter if it is v2 to v3 or v3.2 to v3.3 -- everything is a migration to us. We don't use the word upgrade as that will refer to the CX product.
      • After migrate how do we confirm that site has been migrated? At present, I am assuming that most of us will observe directory changes and folder structure changes(in Cyberduck) and also cross check in /ci/admin. If there are any other checks, please let me know.
        • There were a number of changes in v3 that changed the way directories were utilized and there were yet again some changes in v3.3. When looking at your ci/about or looking in the framework versions page - the information on those pages will tell you which sites are on which version of CP.
      • I understand custom widgets cannot be migrated as is - but wondering what is the importance of "Would you like to copy customised files to version 3? Both options require you to edit your custom code after migration?" and "Yes[If you have significant custom code]" ?
        • Barrilito had a great answer above that I simply cannot improve upon. For some widgets you can migrate over while others might be better to start fro scratch.
      • Is DynamicformInput and DynamicProductInput deprecated in new version?
        • Neither of those were standard widgets. They were part of an example on how to take a standard widget (ProductInput and FormInput) and create custom widgets from them. Neither of those widgets are deprecated.
    • Pramod Vasudeva Murthy

      Thank you - Barrilito and Willie for your valuable answers.

      It's just that CP framework is an Ocean; more you dig, more pearls you get!! yes

      - VIP

    • Barrilito van Dijk

      "the more you fig, the more pearls you get".... nicely put Pramod! wink