I would like to discuss two issues here - I think it will be self explaining why I am relating the two...
We have a PB11.5 application using the Easy Soap engine for web services. We have enabled HTTPs communications. When connecting to a specific web service in that configuration, we encounter an error that the service could not be reached. (Non HTTPs communication can connect without error)
So I built a new web service proxy with the "Use .Net Engine" checkbox checked. Once I generate the project, I see a newly created dll, along with two extra dlls that got copied in automatically (Sybase.PowerBuilder.WebService.WSDLRemoteLoader.dll and Sybase.PowerBuilder.WebService.WSDL.dll) in my path. When I deploy my changes to use the new nvo, along with these 3 dlls, the API connection works fine. When I delete the above 2 dlls (leaving the generated dll as well as the regular webservice dlls intact,) I get an error when trying to connect.
Reading through the PB Runtime Packager documentation, it seems that the above two dlls are not included by the packager for any of the selection options, but it indicates that files required by both the Easy soap engine as well as the .net engine are in the included dlls.
So my first question is, are there any known scenarios that require these two dlls to be included?
The second question is, would there be any licensing issues preventing me from deploying the above dlls with our product, even though the PB Runtime Packager does not bundle these?
Thank you very much for your patience reading through this, and any response is hugely appreciated.