1. VINOD NAIR
  2. PowerServer
  3. Saturday, 7 December 2024 00:08 AM UTC

I want to know if there is a best practice document to install PowerServer 2022 R3 build applications and web APIs. We have 5 applications with 5 WEB APIs. How should we install this in IIS so it runs smoothly. 

As an example I created a site for 2 application and 2 Web APIs as shown in the attached image. 

I created 2 sites - one for the set of applications and one for the set of APIs 

site 1 : mpssuite has 2 applications both of which has the same application pool

site 2 : webapis has 2 apis and each of the apis has its own application pool 

When I launch the application, the CloudAppPublisher link points to the a folder in the mpssuite root folder and not within the application. So, I had to manually copy the CloudAppPublisher folder under c:\inetpub\wwwroot folder. Not sure why the link is not pointing to the CloudAppPublisher folder within each of the application folder.

Looking for advice on what is the best practice for installing multiple applications and web apis. 

Attachments (1)
VINOD NAIR Accepted Answer Pending Moderation
  1. Monday, 9 December 2024 15:54 PM UTC
  2. PowerServer
  3. # 1

Hi Francisco,

Thank you. I was able to setup multiple applications and running it locally on the server as shown in attached IIS (iis setup.jpp). I have few issues right now.

1. When running locally on the server, the cloudapplauncher was not launching automatically and when I clicked on the Download link in the 2nd image (CloudAppPublisher.jpg) it doesn't find the cloudapplauncher folder. As you can see it is looking for CloudAppPublisher under c:\inetpub\wwwroot\ and not where the application is installed which is c:\inetpub\wwwroot\standardspro. so I had to manually copy the folder to c:\inetpub\wwwroot. What is causing this issue?

2. The application launches successfully locally on the server but when I launch it remotely from another machine it get the attached error. (ps auth error).  I followed the guideline on this link https://stackoverflow.com/questions/76241133/net-core-7-error-405-http-verb-used-to-access-this-page-is-not-allowed 

<system.webServer> <modules runAllManagedModulesForAllRequests="false"> <remove name="WebDAVModule" /> </modules> </system.webServer>

but that didn't fix the issue.

Attachments (3)
Comment
  1. VINOD NAIR
  2. Tuesday, 10 December 2024 13:39 PM UTC
Hi Logan,

1st issue - the link you sent gives an example of 2 applications residing in the same sub-folder. Not sure how it would work since web.config for each application will be overwritten. The setup we are using is as follows:

c:\inetpub]wwwroot\application1folder\applicaton 1 and web api sub folders reside here

c:\inetpub]wwwroot\application2folder\applicaton 2 and web api sub folders reside here

So, when you launch application 1 then it is looking for CloudAppPublisher folder under neat c:\inetpub\wwwroot and not under c:\inetpub\wwwroor\aaplication1folder\ so it doesn't launch CloudAppLauncher.



2nd issue - I deleted the Roaming\PBApps folder and re-ran the application and it worked.
  1. Helpful
  1. Logan Liu @Appeon
  2. Wednesday, 11 December 2024 03:37 AM UTC
Hi Vinod,

If you are using the IIS sub-app the web.config under the Web API folder will be used to start the Web API, the web.config generated by the PowerServer project is not required. Refer to: https://docs.appeon.com/ps2022r3/Is_web.config_mandatory.html

You can configure the apprun,json file for your app to decide where to download the Cloud App Launcher. Refer to: https://docs.appeon.com/ps2022r3/Concepts_Client_app.html

Regards, Logan
  1. Helpful
  1. VINOD NAIR
  2. Wednesday, 11 December 2024 13:42 PM UTC
Hi Logan,



Thanks for the quick response and the links. This helps.
  1. Helpful
There are no comments made yet.
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Monday, 9 December 2024 15:29 PM UTC
  2. PowerServer
  3. # 2

Hi Vinod,

It's recommended that Web APIs have each their own application pool. The Cloud Apps can all share the same site/pool since they're just static files. The Cloud App Launcher should also be kept separate, in case you want to upgrade one of your applications to a version that requires a new Cloud App Launcher, but you don't want to be forced to upgrade the other one.

 

Regards,
Francisco

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.