1. Brett Weaver
  2. PowerBuilder
  3. Monday, 13 February 2023 20:13 PM UTC

Hi There

Apologies if I have missed this somewhere;

What do I give the infrastructure guys as a definition of the Web Server I need for internal PowerClient Distributions?

I'm guessing the Web Server can be pretty small, but what is the recommended for say, 800 users?

What ports need to be open?

 

Can I use the same Web Server to trial Power Server?

 

Regards

Brett

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 13 February 2023 20:32 PM UTC
  2. PowerBuilder
  3. # 1

Hi Brett;

  Since PC is only for new App downloads or updated Apps, this only needs to be a small server as once the Apps reside on the App users PC, HTTP traffic would be only at App Start-up mostly. So one web server should easily handle 800 users IMHO.

  Yes, your current WS should support PC as well.  ;-)

Regards ... Chris 

Comment
  1. Brett Weaver
  2. Monday, 13 February 2023 20:36 PM UTC
Thanks Chris - what about ports to open in the internal firewalls?
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 13 February 2023 22:06 PM UTC
Standard HTTP / HTTPS ports as per your Web Server support team recommendations. ;-)
  1. Helpful
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Monday, 13 February 2023 21:08 PM UTC
  2. PowerBuilder
  3. # 2

Hi.

Powerclient can be hosted in almost any web server (IIS, Apache, Nginx)... It doesn't require lot of resources. Web server will do the following:

  • Install the application on a new computer
  • Update the application (depending on project settings)

That said, a powerclient application can be executed even when there is no connection to webserver when:

  • Project is set to update when connected or never
  • Download options was "Download all the app files at app startup"

Webserver will host the application and required runtime. This can be a large amount of data to transfer. How often your application will be updated? How often a new pc should get your application? How many computers will have to do that concurrently?

It's hard to answer all of the above. What I can tell you is that PowerClient isn't to heavy. Most of its job is to transfer files. In the past I did setup Powerclient in an Apache running on a Raspberry Pi 4 with 2 GB of memory (it's still working). It was fine for up to 5 computers. I even tried to install the application through web without any problem. I'm sure it could serve more than that but I never tested. That said, a modern server with IIS or Apache can do the job.

Andreas.

Comment
  1. Chris Pollach @Appeon
  2. Monday, 13 February 2023 23:42 PM UTC
No, PC does NOT use FTP. It only uses HTTP/HTTPS protocols like any other Web App.
  1. Helpful
  1. Thomas Rolseth
  2. Monday, 20 November 2023 23:34 PM UTC
Chris, are you sure? The PC documentation regarding IIS talks about creating and setting up an FTP site.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 21 November 2023 04:29 AM UTC
Sorry Brett;

PowerServer dropped the FTP option in 2022 R2 but PowerClient still has it.

However instead, I would go through creating a deployment package route & let the production team deploy the PC App & CAL as per their Web Server production rules.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Brett Weaver Accepted Answer Pending Moderation
  1. Monday, 13 February 2023 21:31 PM UTC
  2. PowerBuilder
  3. # 3

I have decided to go with:

The Web Server Configuration

A small web server is all that is required, certainly 16GB RAM and 200GB disk should allow us to implement PowerClient.

Normal Web ports will need to be open to internal LAN attached PC’s only

No database access is required

Developers will want to have FTP access to the server to automate delivery and deployment

 

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.