Webservice in MII

Question

Hallo
I try to connect a web service in MII with an action block. There is also set a credential alias.
By testing, I get the following error:
[ERROR] Error Invoking Web Service Action: The element type "p" must be terminated by the matching end-tag "</p>".
By testing the WS in Soapui it still works.
Any suggestions?

Answer 1

Hi,
I am a colleague of Sebastian and since we got new insight in the problem I want to tell you what we found out:
Since we couldn't find the real source of the problem we used the [Fiddler-Webproxy-Tool |http://www.fiddler2.com/fiddler2/] to monitor and log the HTTP traffic as man in the middle
We found out that MII calls HTTP webservices with the HTTP POST method (which is correct) while in HTTPS calls HTTP GET is used (which is wrong by design since all input parameters would have to be URL encoded)
Thus the return value for the webservice is a HTML 404 error page which can't be parsed sometimes.
We also saw that the requesting user agent string is different for HTTP and HTTPS so we assume these are two different libraries that are used by MII
There are a few pitfalls when you try to reproduce the behavior which could also explain why it works for most people.
MII has a special behavior working with Webservices. When you setup the action block you deliver the WSDL address and choose the right webservice action.
When the action block is executed the WSDL is requested again and the endpoint of the WSDL is used(!) for the webservice call.
So even if you request the WSDL over a HTTPS connection it can be that the webservice endpoint in the WSDL is a HTTP one and the webservice call itself will not be secured (and will also not show the above error)
Steps to reproduce the error:
On Netweaver there exists a simple demo webservice called SimpleEchoEJBBean
Go to Single Service Administration and switch this Webservice to HTTPS.
You have to do this so that the endpoint in the WSDL is switched to HTTPS. You can check this by looking at the WSDL in the browser.
Now try to communicate with this webservices via a MII action.
When you let the transaction run it can be that you wont get an error since  MII parses the 404 error page without errors and just delivers no result. So the result of the webservice call will be empty.
When you start the transaction with debug outputs (CTRL+F5) you will see the error directly