Consuming XSOData in Lumira

[Former Member]

I created XSOData and I can see the metadata via browser with this URL

http://xyz.com:8000/xyz/hanaprj/ProductODataService.xsodata/$metadata

but when I try to use it from Lumira I get below message

Anyone has experienced this?

[former_member183750 · Accepted solution]

Hi Babu

See if doing a high level trace will help. Attached is a batch file with a doc documenting how to use it. One you have the log, see what it says.

Extract the file from the zip. You will get a .txt file. rename that to .zip and extract to get the bat and doc files.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

enabletracing.txt.zip

[Former Member · Accepted solution]

It appears the xml returned by HANA XS App isn't the expected format for Lumira.

|D1120BCB1C154110BB79B3EA35558E2E12fb|2015 08 06 19:27:59.902|-0500|Error| |>>| | |TraceLog| 8432|  41|qtp332051528-41 | ||||||||||||||||||||CS||EXCEPTION [OData |Generic OData 2.0 |ID:0]com.sap.connectivity.cs.java.ConnectionManager{com.businessobjects.connectionserver.ConnectionManager}.TestConnection: [com.sap.connectivity.cs.java.drivers.CSDriverError: A problem occurred while communicating with the provider. Detailed message: The element type "meta" must be terminated by the matching end-tag "</meta>".

  at com.sap.connectivity.cs.java.drivers.DDKExceptionImpl.convertToCSException(DDKExceptionImpl.java:156)

  at com.sap.connectivity.cs.java.JAVAGenericJob.<init>(JAVAGenericJob.java:75)

  at com.sap.connectivity.cs.java.JAVAJob.<init>(JAVAJob.java:32)

  at com.sap.connectivity.cs.java.JAVAOpenJob.<init>(JAVAOpenJob.java:39)

  at com.sap.connectivity.cs.java.OpenJob.<init>(OpenJob.java:57)

  at com.sap.connectivity.cs.java.ConnectionServer.getJob(ConnectionServer.java:382)

  at com.sap.connectivity.cs.core.ConnectionServer.CreateJob(ConnectionServer.java:73)

  at com.sap.connectivity.cs.core.ConnectionServer.CreateJob(ConnectionServer.java:120)

  at com.sap.connectivity.cs.core.ConnectionManager.TestConnection(ConnectionManager.java:155)

  at com.sap.connectivity.cs.api.trace.ConnectionManagerLogger.TestConnection(ConnectionManagerLogger.java:596)

  at com.sap.hilo.datasource.freehandsql.internal.FreeHandSQLCnxSrv.testConnection(FreeHandSQLCnxSrv.java:453)

  at com.sap.hilo.desktop.datasource.v2.freehandsql.services.CatalogService.execute(CatalogService.java:144)

  at com.sap.hilo.desktop.h5v2.common.service.BaseService.execute(BaseService.java:33)

  at com.sap.hilo.desktop.embeddedserver.httpservice.HTTPAdapter.execute(HTTPAdapter.java:89)

  at com.sap.hilo.desktop.embeddedserver.DispatcherServlet.handleRequest(DispatcherServlet.java:107)

  at com.sap.hilo.desktop.embeddedserver.DispatcherServlet.doPost(DispatcherServlet.java:87)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)

  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367)

  at com.sap.hilo.desktop.embeddedserver.JsonPaddingFilter.doFilter(JsonPaddingFilter.java:80)

  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

  at com.sap.hilo.desktop.embeddedserver.configurator.internal.SecurityFilter.doFilter(SecurityFilter.java:59)

  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

  at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484)

  at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)

  at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)

  at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)

  at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)

  at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)

  at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)

  at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)

  at org.eclipse.jetty.server.Server.handle(Server.java:350)

  at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)

  at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900)

  at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954)

  at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851)

  at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)

  at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)

  at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)

  at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)

  at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)

  at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)

  at java.lang.Thread.run(Thread.java:812)

Caused by: com.sap.connectivity.cs.java.drivers.odata.exception.CommunicationException: A problem occurred while communicating with the provider. Detailed message: The element type "meta" must be terminated by the matching end-tag "</meta>".

  at com.sap.connectivity.cs.java.drivers.odata.helper.XMLHelper.parseXMLtoDOM(XMLHelper.java:65)

  at com.sap.connectivity.cs.java.drivers.odata.ODataDriver.parseMetadataModel(ODataDriver.java:291)

  at com.sap.connectivity.cs.java.drivers.odata.ODataDriver.connect(ODataDriver.java:219)

  at com.sap.connectivity.cs.java.JAVAGenericJob.<init>(JAVAGenericJob.java:71)

  ... 42 more

Caused by: org.xml.sax.SAXParseException; lineNumber: 64; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".

  at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)

  at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347)

  at com.sap.connectivity.cs.java.drivers.odata.helper.XMLHelper.parseXMLtoDOM(XMLHelper.java:47)

  ... 45 more

]

[former_member183750 · Accepted solution]

I'd like to be able to reach the url:

http://xyz.com:8000/xyz/hanaprj/ProductODataService.xsodata/$metadata

But I get an error message when I try:

- Ludek

[Former Member · Accepted solution]

Ludek,

Here is what I get when I run it internally

and here is with $metadata

thanks for looking into this.

[former_member183750 · Accepted solution]

Hi Babu

Well, I was hoping to see an abandoned tag or something - I suspect you knew that

Not seeing anything of much use in those XML files, I wonder if an http sniffing utility like Fiddler will tell us anything. I'm not too expert with Fiddler logs, but I do have someone here who knows the thing inside and out. If you look and don't see much, attach the logs here and we'll take a look.

- Ludek

[lyon_guan]

Hi Babu,

I meet the same problem, Could you tell me if you have solved the problem and how to solve?

Thanks.

BR,

Lyon