1. Kalpana Snehi
  2. PowerBuilder
  3. Monday, 16 December 2019 17:56 PM UTC

We are having a SOAP Connection build in PB12.5 for a webservice but in PB2019 its not getting connected giving error, what should I need to do? 

Kevin Ridley Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 20:39 PM UTC
  2. PowerBuilder
  3. # 1

You should probably mention if you are having trouble in the IDE or deployed exe.  As Chris mentioned, you need the newer pbwsclient190.pbd or import the same name .pbx file into a pbl, althought they may migrate up into PB2019 ok.  You definitely need the pbwsclient190.dll with your deployment.  As Armeen mentioned, the preferred current method is to use the HTTPClient, or even better, if the web service provider offers a REST service for this same function, there's lots of options for that as well.

 

Kevin

Comment
  1. Kalpana Snehi
  2. Tuesday, 17 December 2019 07:42 AM UTC
Hi Kevin,



I am having problem in code itself not yet deployed.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 19:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi Kalpana;

   When you migrated to PB 2019 from PB 12.5.x, did you replace the SOAP Web Service library "pbwsclient125.pbd" with the PB2019 equivalent - "pbwsclient190.pbd"?

Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 19 December 2019 17:45 PM UTC
Hi Kalpana;

I am a bit confused ... you do not need the "pbrestclient190" DLL if you are building a .Net SOAP based web service App. That DLL would only be required if you are converting over to a RESTFul based web service App.

Regards ... Chris
  1. Helpful
  1. Ricardo Jasso
  2. Thursday, 19 December 2019 18:30 PM UTC


Kalpana,



You must make sure that pbwsclient190.pbd is included in the PBCLTRT190.msi. The installer builder is including the pbrestclient190.dll most probably because it is an integral part of PowerBuilder in the form of a DLL whereas the pbwsclient190.pbd is an optional extension.



Regards,

Ricardo
  1. Helpful
  1. Kalpana Snehi
  2. Thursday, 26 December 2019 07:30 AM UTC
After migration We can see (soapexception and soapconnection) in pbl So I have not imported (pbsoapclient190.pbx and pbwbsclient190.pbx) into the PBL , after Importing PB Extensions in PBL it started accepting soap connection.

This issue is resoled now.

  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 18:38 PM UTC
  2. PowerBuilder
  3. # 3

Do you mean you are calling a SOAP service or you are creating a SOAP service with PowerBuilder?

If you are calling a SOAP service, the obsolete SOAP client is still in PB 2019, it is just an "obsolete" feature so customers should migrate away from it.  At a minimum, it poses a security risk since it doesn't support TLS 1.2.

You can use the new HTTPClient object to act as a SOAP client.  This article may be useful: https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object

Anyway, the obsolete client should still work.  You would need to provide more info so we can try to help troubleshoot.

Comment
  1. Kalpana Snehi
  2. Tuesday, 17 December 2019 07:40 AM UTC
We are creating a SOAP services with PB , I will check these documents.
  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.