Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (2)

Resolved Client-server to the Cloud and beyond

  1. How-to
0
Votes
Undo
  1. Ian Wells
    Ian Wells
  2. PowerBuilder
  3. Sunday, 30 May 2021 15:50 PM UTC

Hi All,

Going to try to move this over 50 year old, exclusively client-server, PB Developer into the cloud/multi-tier/web-service world, basically because my customers are forcing me to ;-)

OK, so my development environment consists of a Macbook Air running Windows 10 under VMWare Fusion. I have a daytime job where I prefer the Apple ecosystem. The PB work is a side gig, so don't really need an impressive development rig. 

The first customer I want to move (eventually) to their app running via the "cloud" (hope I'm using that term correctly) is currently running running a native PB app (using PFC) with SQL Server database connected via ODBC. I know old school right? They have been very happy with the situation so far - no need for a large tech-savvy IT org to support this app (will get to this point later).

 

So the plan I have in my mind is:

  1. Move to PowerClient - to address the need to deploy the PBDs/EXE.
  2. Move to PowerServer - they have a future need to create some APIs to allow other applications to access the business logic.

So for PowerClient step:

  1. Can I install Microsoft IIS Express on my VMWare Mac to test the PowerClient deployment (local server).
  2. How do I instruct  a "non-server" savvy (like me actually) IT department to create a Web Server?

I've read a lot of PowerClient docs, white papers and tutorials, but maybe I've missed some?

Thanks in advance for all your help.

 

  1. Client/Server
  2. Migration
  3. PowerBuilder
  4. PowerClient
Retrieve DATAWINDOW
Re: Theme - different background coloring for each...
Responses (2)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Sunday, 30 May 2021 18:36 PM UTC
  2. PowerBuilder
  3. # 1

Hi Ian,

PowerClient is still client/server and the Web server is simply serving up static files so you can use any Web server you want.  For example, Apache, IIS, IIS Express, Nginx, etc.

PowerServer is cloud architecture and the middle tier uses .NET Core framework.  So for PowerServer you need an app server capable of running .NET Core, such as IIS or Kestrel.

With that said, I don’t see the point of doing PowerClient if you want to move to the cloud.  PowerServer has all the benefits of PowerClient plus cloud architecture.  So I would skip PowerClient and go straight to PowerServer 2021.

Best regards,

Armeen

Comment
Ian Wells
  1. Ian Wells
  2. Sunday, 30 May 2021 18:57 PM UTC
Thanks for the response Armeen.



I guess I just want to take it in small steps. I need to bring the customer's IT dept. along with me.

I'll go simple with PowerClient then move to PowerServer when their IT Dept (and myself) are comfortable.



Again, right now, my development environment is a Macbook Air running Window 10 in a VM. Perfect for my client-server development needs on the road (i.e, plane journeys, hotels) but not good for full-blown multi-tier development.



Am I the only one still developing PB apps this way? ;-)



Cheers

Ian
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 31 May 2021 04:03 AM UTC
Tons of customers are developing client/server apps, and deal with headaches of deploying them manually since PowerClient didn't exist until just recently. So you are definitely not alone! :-)

I understand your point of doing a stepped approach... first taking care of the the client app deployment with PowerClient and then moving the app from client/server to cloud with PowerServer. The only thing I would suggest is for the Web server use something compatible with .NET Core so then when you move from PowerClient to PowerServer you don't have to change Web servers.

With that said, it would probably be simplest just to go with IIS (not IIS Express). Only if you expect thousands of users or it is important to run on a Linux server, then I would look into fancier configs using a reverse proxy along with Kestrel. Here is info from Microsoft about this: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/when-to-use-a-reverse-proxy?view=aspnetcore-5.0

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Sunday, 30 May 2021 16:37 PM UTC
  2. PowerBuilder
  3. # 2

Hi Ian;

 FWIW: PowerClient is still C/S and can run (deploy) from various web servers. However, PowerClient is IIS based only. So my suggestion would be to focus on deploying PC via IIS and then your all setup for an easier transitioning to PS. Food for thought.

Regards ... Chris

Comment
Ian Wells
  1. Ian Wells
  2. Sunday, 30 May 2021 17:35 PM UTC
Chris,

So I should install Microsoft IIS full version on my VM just to do the Power Client install testing? Could I (for now) just use IIS Express for the PowerClient testing. When I move to testing the PowerServer I could buy a separate physical server, create a home LAN and install Microsoft IIS (full) and the PowerServer app?

I'm trying to do this in easy steps so I can learn along the way.

Thanks

Ian
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Sunday, 30 May 2021 17:52 PM UTC
Hi Ian;

The full IIS is now included with all versions of W10. So I would go with that version. The Express version of IIS is now hardly used.

Regards ... Chris
  1. Helpful
Ian Wells
  1. Ian Wells
  2. Sunday, 30 May 2021 18:49 PM UTC
Thanks Chris. I'll read up how to start up IIS on my Windows 10 VM



Cheers

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