Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Procedure to upgrade PowerServer (PB) 2019 from [APPEON for PowerBuilder 2015]

  1. How-to
0
Votes
Undo
  1. Chung Hing Charlie Wong
    Chung Hing Charlie Wong
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 16 November 2020 02:42 AM UTC

Dear All,

 

Background,

Due to EOSL issue on APPEON for PowerBuilder2015, we purchased license of APPEON PowerBuilder 2019r2, in order to migrate current programs to PowerServer version with maintenance.

When we prepare development environment for code migration and test, we learnt we cannot upgrade PowerServer by installation, and both version cannot be co-existed. So we have to remove current setup with APPEON for PowerBuilder 2015, and then install the PowerServer (PB) version, and apply license and deploy all the programs.

 

Problems,

How to perform upgrade and license transfer between the versions in our situation? And is rollback plan available?

 

Consideration,

Since it is production environment, we would perform the upgrade during non-office hours, to minimize service impact.

(added) We do not have spare server on production environment to allow the versions co-existed, for e.g. DEV server cannot be used for the purpose as it was limited from accessing production DB. It would be a BIG project if we have to negotiate with security team.

 

So may we have your advices and experience sharing with our situation? Thanks in advance.

 

Best Regards,

Charlie Wong

  1. License
  2. PowerBuilder
  3. PowerServer
How to find chrome installation path and open chro...
Any plan for smaller license pack for PowerServer?
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 November 2020 03:24 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Charlie;

  I would create a completely new Dev / QA / IT .... Prod environments. Starting first with PB2019R2 version that includes PS2020. Install PS2020 locally with your PB IDE.

   Next, migrate your older PB Apps to PB2019R2 & then deploy them to the local PS2020 and unit test there. Once the Apps unit test OK, then deploy them to QA. Then QA to IT, etc and onwards.

   In production, create a parallel PS using 2020 on a separate server. Then publish your fully QA'ed Apps from PB2019R2 to the new PS2020 server & then redirect your App users to the new PS. Once all your Apps are working on PS2020, then decompression the old PS.

Regards ... Chris

Comment
Chung Hing Charlie Wong
  1. Chung Hing Charlie Wong
  2. Monday, 16 November 2020 03:33 AM UTC
Thanks Chris for your sharing. Our situation, we do not have a spare server/environment, so we cannot enjoy the grace period after license deactivation.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 16 November 2020 04:28 AM UTC
Then I recommend...

1. Practice doing the upgrade on one of your development licenses first.

2. Test VERY VERY carefully. There have been significant changes between PowerServer 2015 and 2020.

3. Create a backup image of the entire hard drive of the production server.

4. Perform the upgrade on the production server over the weekend when nobody is using the system.

5. Do a brief test of the production server, if problems restore the backup image.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.