Hi Art,

You can create a second IIS site bound to a different port, using a different physical path, and place the new Web API there. Using the same Web API for multiple applications is not recommended.

Regards,
Francisco

Hi Art,

The way I suggest to do this is...

1. On the default IIS Website (port 80) deploy the client apps. When I say client app I mean the PB .EXE portion (not the C# Web APIs).  Each client app would be in a subfolder of this default IIS Website.

2. Then create another IIS Website (must be different port than 80, for example 5099) that will hose the multiple Web APIs.  Again, just like the client app, each Web API needs to be in a distinct subfolder of this Website.  Here are instructions how to do this: https://docs.appeon.com/ps2022/Deploying_multiple_Web_APIs_to_IIS.html

Best regards,
Armeen

Hi Art;

  You would first create a new Website under a new root folder (ie: C:/Inetpub/PSxxxx). Then bind it to the new Port ID of your new PS instance. Then package your new PS instance from the PB IDE's "SnapDevelop" environment. From there, copy that PS deployment to the route folder of the new Website. 

   Repeat the above procedure for further PS new instance App deployments.   HTH

Regards ... Chris 

Follow up question on this topic.

I have deployed two applications on the same server using the method 2 described in docs. I have both Apps deployed to the main site and both web APIs to a second site on a different port. All works.

Looking at the web config on the route of the main web site it contains a line for one  of the applications:

<aspNetCore processPath=".\Othello_cloud_API\ServerAPIs.exe" stdoutLogEnabled="false" stdoutLogFile=".\Othello_cloud_API\logs\stdout" hostingModel="inprocess" />

Everything works and my other application is fine, I just wanted to be clear about this line and why we do not have a line for both applications?

Many thanks

David