IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 3 replies
  • Latest Post - ‏2013-07-11T08:02:16Z by DaveN
HBruchey
HBruchey
43 Posts

Pinned topic Upgrade to v5.1.1 from v5.1

‏2013-07-08T20:12:51Z |

We are currently running CICS Explorer v5.1 and would like to upgrade to v5.1.1.  On the CICS Explorer Download site there are 7 scenarios for upgrading where Scenario 7 is applicable for Upgrading CICS Explorer to the latest release.  There is a warning note, however, stating - 'This scenario can be used for upgrading CICS Explorer V5.1.1 to any subsequent V5.1.1.x release, but not for upgrading CICS Explorer V5.1 to V5.1.1.'   What then is recommended method for upgrade for 5.1 to 5.1.1 - I don't see that any of the other Scenarios apply?  Is this then considered a fresh install for upgrading v5.1 to 5.1.1? 

  • DaveN
    DaveN
    71 Posts

    Re: Upgrade to v5.1.1 from v5.1

    ‏2013-07-10T09:21:09Z  

    Hi there,

    Thanks for bringing this to our attention. I think the download pages need a ilttle bit of clarification.

    Explorer 5.1.1 is based on Eclipse 4.2.2, Explorer 5.1.0.x was based on Eclipse 3.6.2. Because of this we are unfortunately unable to support a direct upgrade from Explorer 5.1.0.x to 5.1.1.

    You are correct that the best approach is a fresh install. Do please make sure that you back up your existing workspace because there are some migration steps that will mean you can't move back to 5.1.0.x very easily once you have used 5.1.1.

    Dave

  • HBruchey
    HBruchey
    43 Posts

    Re: Upgrade to v5.1.1 from v5.1

    ‏2013-07-10T17:47:40Z  
    • DaveN
    • ‏2013-07-10T09:21:09Z

    Hi there,

    Thanks for bringing this to our attention. I think the download pages need a ilttle bit of clarification.

    Explorer 5.1.1 is based on Eclipse 4.2.2, Explorer 5.1.0.x was based on Eclipse 3.6.2. Because of this we are unfortunately unable to support a direct upgrade from Explorer 5.1.0.x to 5.1.1.

    You are correct that the best approach is a fresh install. Do please make sure that you back up your existing workspace because there are some migration steps that will mean you can't move back to 5.1.0.x very easily once you have used 5.1.1.

    Dave

    Dave,

     

    Thank you for the response.  Based on what you have said then, we can continue to use the same workspace from v5.1 to v5.1.1, correct?    Also, I read some more on the v5.1.1 installation.  Going forward then, is the intention that this would be more of a seamless upgrade if we are using Installation Manager?

     

    Thank you,

    Heather

     

  • DaveN
    DaveN
    71 Posts

    Re: Upgrade to v5.1.1 from v5.1

    ‏2013-07-11T08:02:16Z  
    • HBruchey
    • ‏2013-07-10T17:47:40Z

    Dave,

     

    Thank you for the response.  Based on what you have said then, we can continue to use the same workspace from v5.1 to v5.1.1, correct?    Also, I read some more on the v5.1.1 installation.  Going forward then, is the intention that this would be more of a seamless upgrade if we are using Installation Manager?

     

    Thank you,

    Heather

     

    You can continue to use the same workspace - but please do take a back-up first.

    The "laws of Microsoft Windows physics" mean that we can't upgrade some components of CICS Explorer (the JRE and some parts of Eclipse) very easily because when CICS Explorer is open some files are locked. Installation Manager should allow us to do much more seamless upgrades. Inevitably there will be times when a reinstall is required, but we would like to reduce them over time.

    Note that with an Installation Manager install, you will stand the best chance of seamless upgrades if you install all tools via IM, rather than using Help, Install New Software from within CICS Explorer.  Using IM exclusively for the installations will be the best option - if you must install tools that don't have IM packages then the traditional p2 approach (Help, Install New Software) is available, but carries a risk that upgrade simplicity might be compromised.

    Hope that's helpful rather than confusing,

    Dave