Calling Enterprise Services through xMII Web Service action block

[Former Member]

Hi All,

I'm calling some Enterprise Service through xMII Web Service action block.

After providing URL and user credentials, I'm getting error "SOAP Service could not be loaded: The element type 'p' must be terminated by the matching end-tag '</p>'."

Can anyone point out what might be the reason ?

Thanks,

Sumit

[jamie_cawley]

Also check to make sure that you have the proxy server setup under System Management - System Administration if necessary.

Regards,

Jamie

[Former Member]

I've checked the proxy setting in System Management - System Administration and it is as per the browser setting. In fact, the same error occurs even for wrong url I passed, which I think is the problem with the xMII setup - but don't know exactly.

Can any one throw more light on it ?

Thanks,

Sumit

[Former Member]

Hi,

One reason for this also be that the Server system from which xMII is accessed may not have the access to that particular Web service. Try with some other web service which does not have any restrictions.

Reward if Helpful.

Regards,

Sowmiya.M

[jcgood25]

Sumit,

My guess is that you are not entering valid credentials and are getting a login page challenge of some sort instead of the expected xml schema, since the <p> element would indicate a paragraph in html. Try putting the same URL in a browser window and see what you get back.

Regards,

Jeremy

[Former Member]

Thanks Jeremy,

I've hit the same url through browser - it asks user credentials.

I've provided the same and it opened the wsdl file.

So I think the problem is calling ES through web service action block, it might not be processing and passing proper information to the SAP server.

[Former Member]

If you haven't already, try using the browser from the xMII server machine rather than your own (client).

The error that you recieve usually means that instead of a WSDL an HTML is being returned when you use the WebService action block.

Possible reasons - as Jeremy pointed out - improper credentials or some error with the webservice itself.

Another thing you can possibly try out - use some web service analyser to access the webservice . There's one that goes by the name StrikeIron which is a freeware.Pretty neat tool.

[Former Member]

...or just as likely, a proxy server configuration issue on the xMII server.