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

Resolved Event in the assembly

  1. How-to
0
Votes
Undo
  1. Sally D
    Sally D
  2. PowerBuilder
  3. Monday, 29 October 2018 06:14 AM UTC

Hi all,

We now could expose the server side function which is deployed to EA server to .net web service. Just one concern, before we use the event, did the event could trigger as web service as well when deployed as .dll .net assembly?

Application freezes when debugging at array bound ...
Rendering to a Powerbuilder print job
Responses (1)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 29 October 2018 13:57 PM UTC
  2. PowerBuilder
  3. # 1

Hello Sally,

a Web Service (WS) provides an object-oriented HTTP-based interface to a database server, thereby it is "straightforward" to move your business logic from EAS service components to WSs: the application was, and will still be, 3-tiers.

Instead, if you deploy the EAS functions as a .NET assembly you have two scenarios:

  1. you need a "frontend" network service that loads the assembly and provides clients with an interface to connect through the wire. Typically a Web Service itself (SOAP or REST), or Appeon PowerServer (which lets you reuse the majority of your PB business logic).
  2. you deploy the .NET assembly on each client along with the PB desktop application. The application connects the .NET DLL via MS COM Interop, but will lose its 3-tier schema.

Needless to say 1) is the best option.

Best,

.m

Comment
Sally D
  1. Sally D
  2. Tuesday, 30 October 2018 02:47 AM UTC
Thanks Marco, we now use .net project to make the webservice about those functions exposed in the EA server before. But before we write some code in the event, such as connect DB. Once we use web service the event could not triggered and exposed with web service. So we couldn't use event any more?
  1. Helpful
Marco Meoni
  1. Marco Meoni
  2. Tuesday, 30 October 2018 07:34 AM UTC
Hi Sally,

from PB, you must create a new Web Service Target (file -> new -> target -> .NET web service) to publish an NVO (i.e. same NVO that you used to deploy to EAS) as a Web Service.

Then you can use any *method* (not *event*) of the NVO that you flag as "public".

You can follow this webcast to learn the howto:

https://www.appeon.com/developers/library/videos/soap-web-service-crash-course.html

Best,

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