1. Jason Frost
  2. PowerServer
  3. Friday, 18 February 2022 00:51 AM UTC

Hi, this is my situation: I have a PB app that I'm trying to deploy to remote cloud server.  The server is only available through DNS record which is re-routed so it only responds to https.  I compile and package the application and APIs and ship them to the server where I unpack manually.

Let's say I access the application at https://server5.s2.foo.com/fooapp  and I can download the app through the browser, so the application is installed in a folder fooapp in the root of IIS.  The APIs are installed under a folder foo_api in the root of IIS.

My question is: what should the Web API URL be in the Web APIs tab of the deployment project?  I have tried not specifying a port, using 5000 with http, using 5009 with https, adding the /foo_api to the url.  All seems to fail with 'Session creation failed.'

It takes a couple of hours to compile and deploy each time because of the security on my server, so any pointers would be gratefully received.


Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 February 2022 01:51 AM UTC
  2. PowerServer
  3. # 1

Hi Jason,

First, if you want to modify the Web API URL there is no need to recompile and redeploy the app.  You can directly modify the files deployed to the Web server following these instructions: https://docs.appeon.com/ps2021/Change_the_Web_API_URL_for_an_application.html

Second, make sure you have upgraded your PowerBuilder to build 1506 and redeployed using that version.  There are important bug fixes in this latest build.

Third, you should verify with your security team that the Web server is permitted to contact the Appeon licensing server.  Please refer to the documentation: https://docs.appeon.com/pb2021/appeon_license_user_guide/ch04s02.html

Lastly, you should exactly step-by-step follow this doc and setup the Web APIs on IIS accordingly: https://docs.appeon.com/ps2021/Hosting_Web_APIs_in_IIS.html  The Web API URL would be https://server5.s2.foo.com:PORT... port # would be what you configure in IIS for this Web API and no subfolder. 

Best regards,

  1. Jason Frost
  2. Friday, 18 February 2022 02:28 AM UTC
Thank you, I will check all of that. Can I just clarify a couple of things:

1. The Hosting_Web_APIs_in_IIS document, if you follow the path about packaging the APIs in a zip file (which is what I have to do), at the end it just says 'copy all files from the publish folder to the server'. No details about where on the server or other configuration required. Can you expand on that bit?

2. Can the APIs be under the same web root as the application i.e. port 80/443, or do I need a completely separate site/application pool in IIS?
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 18 February 2022 06:24 AM UTC
1. This section of the doc I provided before explains how to deploy to IIS https://docs.appeon.com/ps2021/bk04ch03s09.html

2. You should do a completely separate site/pool. The Web APIs use .NET Core framework.
  1. Helpful
  1. Tracy Huang @Appeon
  2. Monday, 21 February 2022 08:26 AM UTC
Hi Jason,

"No details about where on the server or other configuration required. Can you expand on that bit?"

The information at the end of this page: https://docs.appeon.com/ps2021/Packaging_the_PowerServer_Web_APIs.html maybe also helpful to you, or refer to https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-6.0&tabs=visual-studio#publish-and-deploy-the-app.


  1. Helpful 1
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.