Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Consuming a published Web API

  1. How-to
1
Votes
Undo
  1. Miguel Alzate
    Miguel Alzate
  2. SnapDevelop
  3. Sunday, 18 October 2020 12:35 PM UTC

Hi all.

I have followed all the steps outlined in the SnapDevelop 2019 R2 documentation to implement a Web API and have successfully consumed the API from PowerBuilder 2019 R2 using the localhost URL (https://localhost:5001/api/sample/load).

Then I have published the API to a remote server with Web Deploy, also successfully. The API has been hosted on a website called api with port 83 and application pool api. The app pool is started.

The initial question is, how should I reference the URL of the remote server API in PowerBuilder to consume it? (the remote server IP is 35.221.9.57).

Thanks in advance for any help.

Snapdevelop api using Informix
stored procedure datawindows convert to C#
Accepted Answer
Marcin Jurkowski
Marcin Jurkowski Accepted Answer Pending Moderation
  1. Monday, 19 October 2020 07:57 AM UTC
  2. SnapDevelop
  3. # Permalink

Hi Miguel,

You should make requests to http://35.221.9.57:83 or http://mydomain.com:83 if you assigned a domain to it (I guess that you don't use https for port 83?).
Also, make sure that port 83 is open on the firewall.

Regards,
Marcin

Comment
Miguel Alzate
  1. Miguel Alzate
  2. Monday, 19 October 2020 15:00 PM UTC
Hi, Marcin.



Thanks for replying! When I browsed my site in IIS got error "HTTP Error 500.21 - Internal Server Error Handler "aspNetCore" has a bad module "AspNetCoreModule" in its module list". I found a solution consisting by changing the web.config entry like this:



<handlers>

<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />

</handlers>



But now I'm getting new error: "HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure "



Any idea to solve this error?
  1. Helpful
Miguel Alzate
  1. Miguel Alzate
  2. Monday, 19 October 2020 15:57 PM UTC
I was able to fix the problem by installing a compatible version of the NET Hosting Bundle (2.1). Thanks a lot.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 20 October 2020 01:51 AM UTC
Thanks for sharing!
  1. Helpful
There are no comments made yet.
Responses (1)


There are replies in this question but you are not allowed to view the replies from this question.