This discussion is archived
5 Replies Latest reply: Oct 7, 2012 11:04 PM by Gus C RSS

Upgrade Strategy To 4.1

Gus C Journeyer
Currently Being Moderated
We are currently using 3.2 but want to start work on the upgrade to 4.1 or 4.2, if available soon.
We currently have a dev, test and prod environments.
1 database with many schemas.
12 workspaces, each with 1 application and 1 schema.

My boss wants a gradual roll out of the apps not a big bang.
So I will upgrade one app, test and then issue to prod.
Then I upgrade second app, test and issue to prod etc.

My boss still wants the ability to make changes to the 3.2 apps which have not been upgraded yet

What is the reccommended stategy to achieve this

Gus
  • 1. Re: Upgrade Strategy To 4.1
    Matt Ball Newbie
    Currently Being Moderated
    I'm not clear if you have 1 db with a dev ,test and prod env.

    I'm going to assume that you have 3 dbs, one each for dev, test, prod.

    For your Strategy you will need to clone all 3 databases.

    You will need another web server for the 3 apps because the image directory is different unless you can come up with some clever apache config.

    You will need to decide what you mean by upgrade from 3.* to 4.*.
    you could:

    1. import app, test, prod. Unless you have some very clever javascript or highly dynamic pages this should mostly "just work".
    or

    2. import run auto update utilities, (new data picker, IRR changes, etc.), test, prod. This should be as above mostly "just work" but is slightly more risky.
    or

    3. import, change the theme to a "more modern" one, run the upgrade utils, run the "quality" advisors. Check where custom javascript can be replaced with dynamic actions or new component types etc. Do lots of testing and then prod.

    We on the whole did 1 and then revisited the apps to do more of a 3, but that is because we couldn't clone all the dev, test and prod DBs. So we upgraded dev in place, did "unit" test and then upgraded test for system and UAT. Then big bang upgraded prod.

    If we'd had the luxury of multiple environments I think I would have still gone for option 1. Version 4 is a big jump and there are many things to learn and best practices to be developed. Dynamic actions are such a game changer.

    Edited by: Matt Ball on Oct 5, 2012 2:40 PM
  • 2. Re: Upgrade Strategy To 4.1
    jariola Guru
    Currently Being Moderated
    Hi,

    You can run only one version of APEX in one database.
    When you upgrade your instance all applications are upgraded.
    If you upgrade, you can not anymore import your apps to earlier version of APEX.

    My boss wants a gradual roll out of the apps not a big bang.
    So I will upgrade one app, test and then issue to prod.
    Then I upgrade second app, test and issue to prod etc.
    What you mean by upgrade here? Start using APEX 4.x new features like Anychart 5 and dynamic actions or something else

    Regards,
    Jari
    -----
    My Blog: http://dbswh.webhop.net/htmldb/f?p=BLOG:HOME:0
    Twitter: http://www.twitter.com/jariolai
  • 3. Re: Upgrade Strategy To 4.1
    Gus C Journeyer
    Currently Being Moderated
    Yes we have 3 different databases.

    Basically my plan is to review each application in dev and incorporate the new features of apex 4.
    For example, replace as much javascript with dynamic actions.
    I also want to change the theme to a more modern one.

    Gus

    Edited by: Gus C on Oct 5, 2012 6:28 AM
  • 4. Re: Upgrade Strategy To 4.1
    jariola Guru
    Currently Being Moderated
    Hi,

    You say
    We currently have a dev, test and prod environments.
    1 database with many schemas.
    12 workspaces, each with 1 application and 1 schema.
    If I understand correctly you have only one DB. In that db you different workspaces for dev, test and prod.
    When you upgrade, all are upgraded. It means it might lead you production applications break.

    It would be good have at least two different database. One for prod and one for dev and test.
    So you can check how APEX upgrade affect in dev/test and then do production environment upgrade

    Regards,
    Jari
    -----
    My Blog: http://dbswh.webhop.net/htmldb/f?p=BLOG:HOME:0
    Twitter: http://www.twitter.com/jariolai
  • 5. Re: Upgrade Strategy To 4.1
    Gus C Journeyer
    Currently Being Moderated
    No we actually have 3 different databases.
    One for dev, one for test and one for prod

    Gus

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points