Why do I get parsing errors with my WSDL URL for Web Services usage

[isathore]

Hi,

I am puzzled with the errors I get when I want to create a Web Service datastore.

Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]

When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)

When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)

My questions:

- Why do I get different parsing errors despite the fact that the XML is the same?

- The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?

- Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication

- What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.

Thanks & Best Regards

Isabelle

[Former Member · Accepted solution]

I don't think DS Webservice Datastore or adapter datastore for webservice supports Policy element, you may have to modify the WSDL the make it work

Webservice Datastore and Adapter Datastore (for webService) provide the same functionality, webservice datastore is available from version 12.0, the difference between the 2 is with Adapter datastore you have overhead of adapter jobserver that manages the communication between the adapter and job

[isathore · Accepted solution]

Hi Manoj,

Thanks for your quick response. Where is this documented in DS? Is there a list of supported and not supported tags? I find it a bit strange that SAP tools cannot be integrated seamlessly. I would expect that the WDSL URL generated by SOAMANAGER is directly usable in DS.

Do you have reference to support this?

Thanks again & Best Regards

Isabelle

[Former Member · Accepted solution]

can you send me the WSDL ?

I remember seeing this issue with WSDL generated from SAP Application not working in DS because of the Policy, there is another error that you mentioned "br" must be terminated by matching tag "/br". Let me check if the WSDL is correct

no there is no details documentation of what is supported and what is not supported for webservices, you may find some of the information in SAP notes.

[isathore · Accepted solution]

Hi Manoj,

URL and file sent.

Best Regards

Isabelle

[isathore · Accepted solution]

Some updates on this issue, which might help others in the community.

- Data Service doesn't support ws_policy.

- SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy

- In most cases, replacing ws_policy with standard in the URL directly, works. It doesn't work with Data Services :(.

- Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

[Former Member]

Hello,

I got the exact same error that Isabelle posted under DS14.2.

faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)

And the issue was I wasn't pointing to the WSDL file, I just had to add "?WSDL" at the end of the URL.