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

Resolved PowerBuilder : Exposing API's

  1. New
  2. How-to
0
Votes
Undo
  1. Marc Schmidtmayer
    Marc Schmidtmayer
  2. PowerBuilder
  3. Friday, 5 July 2024 12:06 PM UTC

Hi,

We are going to migrate from PowerBuilder 12.5 to PowerBuilder 2022.
The (urgent) question I have (and sorry if it's already discussed but couldn't find it), is if PowerBuilder 2022 can expose API's?
Calling it, yes... but exposing?

If not possible, what's the "way to go": .NET datawindow, PowerServer?
Any thoughts that could point me out in the right direction?

Thanks for any help,
Appreciated,
Marc.

Scan code tool for PowerBuilder in GitHub
GIT revert fails
Responses (5)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 5 July 2024 18:02 PM UTC
  2. PowerBuilder
  3. # 1

You can use .NET DataStore (non-visual DataWindow) to create REST APIs with the productivity benefits of DataWindow technology: https://www.appeon.com/products/dotnet-datastore

By the way, it is included with your PowerBuilder subscription so nothing extra to buy.

Comment
There are no comments made yet.
Marc Schmidtmayer
Marc Schmidtmayer Accepted Answer Pending Moderation
  1. Friday, 5 July 2024 14:45 PM UTC
  2. PowerBuilder
  3. # 2

Hi Mike,

Thanks for your time.
And indeed, I also found that 3rth party software as an option.
But was looking if it was possible directly from PowerBuilder.
But apparently it is not... but possible via:

  • 3th party software
  • create something "external" (C#) and call it

Thanks again for your input... appreciated.

So the answer is: exposing API's can't be done directly from PowerBuilder 2022.

Thanks agian,
Marc.

 

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 5 July 2024 13:27 PM UTC
  2. PowerBuilder
  3. # 3

if you have NVOs (nothing visual), you can run them using:

you can use Topwiz Software - TopwizWeb (topwizprogramming.com) to create callable PB apis.

you can create an api in c# or something similar and use that to call powerbuilder code

these options allow you to use powerscript.  

 

 

.NET datawindow requires you to rewrite in c# what you have coded in powerscript, but allows you to keep the datawindow itself

powerserver is to enable you to run your full powerbuilder application as a cloud app (run fast/secure on the internet)

 

 

Comment
There are no comments made yet.
Marc Schmidtmayer
Marc Schmidtmayer Accepted Answer Pending Moderation
  1. Friday, 5 July 2024 12:56 PM UTC
  2. PowerBuilder
  3. # 4

Hi Chris,

Thanks for your reply... appreciated.
We're now using API calls (not SOAP because that's already possible) via a 3th party library.
So in terms of calling API's, I think we're ok (keeping the 3th party library or changing to the build-in functionalities of PowerBuilder 2022).

I'm rather looking for the possibilities to expose API's.
People (in our company) thought that this would be possible with the PowerBuilder (classic) 2022 (and already making technical designs) but I couldn't find any info that it is.
And I don't think it is possible, correct?
What are the options then: .NET datawindow or PowerServer?
And if possible, can you briefly explain what this would mean in regard with PowerBuilder (classic) 2022?

Thanks,
Marc.

 

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 5 July 2024 14:23 PM UTC
Hi Marc;

FYI: For the SOAP aspect, you could "optionally" remove the 3rd party product altogether and now use the built-in HTTPClient object class in PB 2022 R3 (if the 3rd party product is just a plain simple Restful "broker" interface").

For creating REST APIs where you would like to use the new .NET DataWindow, you would need to use the SnapDevelop product that comes with PB 2022 Rx "Professional" edition. The SMAP product can create Web API's as Restful web services using the .NET DW. Once built, the Web APIs can be called by any product - even PB apps. If the Restful web API is returning a standard DWO result set as a JSON package, PB also now has a RestClient object class that can broker that for you as well.

HTH

Regards .. Chris
  1. Helpful
Marc Schmidtmayer
  1. Marc Schmidtmayer
  2. Friday, 5 July 2024 14:52 PM UTC
Hello Chris,

For the SOAP calls: we just use standard PowerBuilder (only for the others (http or rest we use a 3th party software).

But then again, it's about exposing API's.

What I think I understand from your answer:

Can we stay in PowerBuilder 2022 (classic) and then need to buy .NET Datawindow and develop there some API's there so we can call them from PowerBuilder 20233 (classic)?

Is that a possibility?

So staying in PowerBuilder 2022 (classic) and do some dev in .NET Datawindow for the part that would need to expose API's?

Let me know if I'm off on this... :-(

Thanks again,

Marc.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 5 July 2024 16:54 PM UTC
For PB 2022 Rx, exposing NVUO's as Web Services you would now use the SnapDevelop product to build & expose your Web API;s.

For PowerScript to C#: https://docs.appeon.com/powerscriptmigrator2022/Working_with_PowerScript_Migrator/index.html

For the PS migrator, you would be migrating NVUO's

For DWO's to .NET DW's: https://docs.appeon.com/dwconverter2019r2/Working_with_DataWindow_Converter/index.html

HTH
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 5 July 2024 12:29 PM UTC
  2. PowerBuilder
  3. # 5

Hi Marc;

  What is / are the API feature (s) that you are using in PB 12.5 that you need replicated in 2022 R3?

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.