1. Pauline Aubertin
  2. PowerBuilder
  3. Tuesday, 6 April 2021 20:27 PM UTC

In PowerClient, if my organization prevents doing the deployment automatically, the documentation says that we can produce a .msi. Is this correct?

Thanks,

Pauline

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 6 April 2021 22:21 PM UTC
  2. PowerBuilder
  3. # 1

Hi Pauline,

PowerClient automates the install and updates of your client/server app from a Web server using a client agent.  The client agent is what is available as an .MSI so that your IT Admin can pre-install for all the users.  Alternatively, the user can install it by themselves (no Admin rights required) the first time they try to run your app.

I recommend you go through this brief feature tour to better understand how PowerClient works, and the benefits it provides: https://www.appeon.com/products/power-client

Maybe my view is so simple, but I think every PowerBuilder customer should either use PowerClient or PowerServer. I don't think it makes sense to manage app deployment yourself, especially there are things we can do that customers themselves cannot do, such as incrementally updating the app at an individual object level, encrypting the PBD files, checking the app integrity before allowing execution, etc.

Just to clarify about the difference between PowerClient and PowerServer, in a nutshell you use PowerClient if you want your app to remain client/server and use PowerServer if you want cloud-native architecture deployed over WAN/Internet.  PowerServer has additional security benefits over PowerClient because it is cloud-native architecture (e.g. no SQL on the client side, no direct access to DB, token security, etc.).

Best regards,
Armeen

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 6 April 2021 20:51 PM UTC
  2. PowerBuilder
  3. # 2

Hi Pauline;

    If you cannot use the new PowerClient feature as documented in PB2019R3 within your organization then the only MSI you would be referring to would be the one that we've been using for many generations of PowerBuilder - aka the PB Packager utility. That MSI of course would only package the PB runtime and not your application.

   The new PowerServer feature packages both the App & runtime files into it's own format and then places these files on a Web Server in its own format. Then part of the PB App's web server interaction and deployment is to interact with the new Cloud App Launcher feature of R3 that coordinates the installation of the PB App & its runtime files from the web server onto the User's PC (or VM) via a web browser interaction.  HTH

Regards ... Chris

Comment
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.