Hi Jakub.
Don't know , if this helps:
In your file based wsdl, there should be a port binding definition at its end. this section defines the url endpoint of this SOAP service.
Usually, if you take the service url and append a "?wsdl" the service will respond with its wsdl. and this might be parsed by pam wsdl explorer.
Sure it might be, that your service is not reachable, but then you wouldn't be able to do any tests anyway.
Regards
...Michael
------------------------------
Regards
....Michael
------------------------------
Original Message:
Sent: 09-03-2021 04:29 AM
From: Jakub Kolacny
Subject: CA PA - Invoke Soap Method operator - load local wsdl
Team,
I need to connect to an external SOAP WS API. So far I've always used the standard "Invoke SOAP Method" operator and the WSDL wizard that loads all the definitions. But in this case, I have only a WSDL definition file stored locally on the server.
Is there a way to load the file using the wizard? I've tried to put the file path, but it didn't work.
The WSDL definition seems to be OK - I can use it with SoapUI without any problems.
Thank you for your suggestions,
Jakub