1. VINOD NAIR
  2. PowerServer
  3. Thursday, 9 March 2023 21:12 PM UTC

I am trying to migrate our PB 2019 application to PB 2022. PB 2019 uses PS 2020 to host our web application. We have a PBL called appeon_workarounds.PBL which consists of lot of functions which is used with in our application. Is there a new version of this PBL with PB 2022 release. If not, there are functions such as AppeonGetClientType (to know if you are running a client-server or web) that we probably need to modify. Is there any documentation of which functions changed and what they have been replaced with etc.? see attached image for the list of functions in the PBL.

Attachments (1)
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 9 March 2023 21:45 PM UTC
  2. PowerServer
  3. # 1

Hi Vinod;

  Unfortunately, you can not migrate the "Appeon_workarounds" PBL as this code was only for PS2020 that supported both the Appeon Web and Appeon Mobile feature applications running under IWA or AWS installed on the target machine.

   PS2020 was fully deprecated after the PB 2019 R3 (see link below) and thus, all the Web & Mobile features. The new PS2022 is based on a totally different architecture & technology stack (Cloud Native). So you would need to refactor your PB2019Rx / PS2020 applications to be totally Client/Server based. Then PB2022 & PS2022 will automatically convert them to N-Tier "Cloud" Apps from there. FYI:  https://www.appeon.com/products/powerserver-tour

   In the mean time, if you need to support Mobile & Web apps - then I would highly recommend that you stay on PB2019 R3 with PS2020. Those are "long term support" (LTS) product versions and will be supported until 2026.01.22. So that would give you some time to switch over technology stacks before your current Web/Mobile App implementations are EOS/EOL.

Starting in PS 2021 ... FYI: https://www.appeon.com/developers/discontinued-features-in-powerserver-2021

Regards ... Chris

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 9 March 2023 21:41 PM UTC
  2. PowerServer
  3. # 2

In the newer versions of PowerServer since it is tightly integrated with PowerBuilder so the features are natively built in PB and no longer need a "workaround" PBL.

Which features do you really need?  For example, you would replace the GetClientType() with IsPowerServerApp() to judge if running as PowerServer and IsPBApp() if running as client/server.    

Comment
  1. VINOD NAIR
  2. Friday, 10 March 2023 19:01 PM UTC
There are a lot of functions that Appeon had used from the appeon_workaround.pbl when they converted our applications to web. So, I am assuming we will need to change all those functions. All the functions are listed in the image I attached in my first comment. It's quite challenging to find out which are the new functions that replaced all the workaround PBL functions and objects. It would nice if there is a documentation that shows the replacement functions.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 10 March 2023 19:24 PM UTC
Hi Vinod;

If you have a Native Client / Server version of your current App(s), then there should be no (or hardly any) re-coding of those type of Apps to have them run as a PB/PS 2022 "Native Cloud" Apps. The PS2022 Toolkit inside the PB 2022 IDE does all the work internally to automatically convert these C/S Apps into Cloud Apps using N-Tier technology.

Regards ... Chris
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 10 March 2023 22:39 PM UTC
Yes, whatever Appeon Workaround PBL functions you used need to be recoded. Some of them no longer make sense in the new cloud-native architecture. Some of them have new corresponding native features added to PowerBuilder. So if any of them are relevant but missing from PowerBuilder and important to your project, please let us know.
  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.