8
Views
4
Comments
Solved
Using Consumer SOAP with self-signed certificate.
Application Type
Traditional Web
Platform Version
11.9.0.16143

Hi, Everyone.

Let me ask a question.

I want to use the SOAP API of another system on the cloud environment from the system built on my on-premise environment. However, the Consumer SOAP feature does not work well.
I have a self-signed certificate in my on-premise environment, do I need a valid certificate?

mvp_badge
MVP
Rank: #26
Solution

Hi Takeshi,

I've been able to import the WSDL (https://dcj-dev1.outsystemsenterprise.com/TestApp/WebService1.asmx?wsdl) into a test application on my Personal Cloud.

I've called it and it returned a "Success!!" message.

This means that the problem is in your On Premise environment with the Proxy.

You can use the EnhancedWebReferences.SetWebReferenceProxy action, but be aware that this one is marked as deprecated and might not work in the future.

Kind regards,

Remco Dekkinga

mvp_badge
MVP
Rank: #26

Hi Takeshi,

Could you explain a bit more about what you errors you see?

When you expose the SOAP API from a cloud environment, it should be visible/reachable from the World Wide Web. It depends on the security measures you've implemented here how you can consume the API.

When you consume a SOAP API from an on-premise environment, you should make sure that you can reach the end-point from that server. This means that you have to make sure that there is no firewall, virus scanner, or proxy blocking your way.

Kind regards,

Remco Dekkinga

Rank: #45054

Hi Remco.
Thank you for your reply.

The following error is occurring on the on-premise side.
-------
There were no endpoints listening at https://dcj-dev1.outsystemsenterprise.com/TestApp/WebService1.asmx that could receive the message. This generally happens when the address or SOAP action is incorrect. See InnerException (if any) for more information.
--------

The cloud server page can be viewed from a browser(IE11) on Windows2016 Server (with OutSystems installed). The browser is set to a proxy to get out of the network in the organization.
Does IIS need the same proxy settings?

mvp_badge
MVP
Rank: #26
Solution

Hi Takeshi,

I've been able to import the WSDL (https://dcj-dev1.outsystemsenterprise.com/TestApp/WebService1.asmx?wsdl) into a test application on my Personal Cloud.

I've called it and it returned a "Success!!" message.

This means that the problem is in your On Premise environment with the Proxy.

You can use the EnhancedWebReferences.SetWebReferenceProxy action, but be aware that this one is marked as deprecated and might not work in the future.

Kind regards,

Remco Dekkinga

Rank: #45054

Hi Remco.

Thank you for your precise advice.
It was exactly as you pointed out. The SOAP Communication was successful!!

I didn't use the API - "the EnhancedWebReferences.SetWebReferenceProxy action".  By setting proxy to IIS in the on-premise environment, the SOAP communication with the outside is possible.