0
Votes
Undo
  1. Moshe Tangi
  2. PowerBuilder
  3. Monday, 11 November 2019 08:14 AM UTC

Hi all

 

I have installed a ws on a server and it all worked fine on the sever itself .

But when I want to test the ws from another machine ( on the same Ethernet network ) I am getting the error :

The test form is only available for requests from the local machine

 

any idea why ?

Attachments (1)
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 17:28 PM UTC
  2. PowerBuilder
  3. # 1

Hi Moshe,

What you are trying to use is an obsolete feature.  I don't recommend investing to build new functionalities based on obsolete features.

Use the new REST Web API feature of PB 2019.  It supports .NET Core framework and doesn't have these limitations.  

Regards,
Armeen

 

Comment
  1. Moshe Tangi
  2. Wednesday, 13 November 2019 11:26 AM UTC
Hi Armeen ,

Thanks for your response . I can not agree more.

The thing is :

My app ( client / server ) which has 150 customers ( most of them are 2- 3 users , some its 10-60 users ).

Each customer holds is own DB .

Since I been asked for more and more third party's requests for data I have developed the WS

My dream is to put all customer's databases on one server ( Amazon / Azure , which will function as production / web / sql )

one option is PowerServer - Migrating to WEB - looks like a very very expansive option ( especially for Israel ) , since I want unlimited users .

Second option - migrating to cloud - the APP runs as exe on each user , the DB located on central server ( for all customers ) , the connection is REST API with datastore model ,

Am I wright ?

I would love to hear your opinion .

Thanks
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 13 November 2019 21:11 PM UTC
Yes, you are right that PowerServer is one good option. You say you have 150 customers and most are 2-3 users. So I think all you may need is a 300-500 user session license of PowerServer. That is not so expensive... much cheaper than Citrix licenses.



Yes, you are right that the second option is to migrate your business logic and DataWindows to C# Web APIs so that the EXE on each machine is just purely UI not directly calling the database. PowerBuilder 2019 R2 includes a tool called PowerScript Migrator that helps to automatically convert a lot of PowerScript business logic to C#. This option is more work than PowerServer but then there is no extra licensing cost of PowerServer.

At our annual conference (Elevate 2019 in Philadelphia, USA) we had one customer that did the option #2 you mentioned. Their story is published here: https://www.youtube.com/watch?v=rUqEBFcaseY&list=PL2Eo5uXB4T3m9VjjvyYMDw_6sCzMMSrAi&index=7&t=5s
  1. Helpful
  1. Moshe Tangi
  2. Thursday, 14 November 2019 07:58 AM UTC
Thanks a lot
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 12:53 PM UTC
  2. PowerBuilder
  3. # 2

Hi Moshe;

  The PB Web Service utilizes the .Net "test harness". This feature only works where the IIS local instance is running. Its not a PB limitation but one of the .Net framework.

HTH

Regards ... Chris

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.