cancel
Showing results for 
Search instead for 
Did you mean: 

SAP ERP ORDER STATUS App: Client cannot parse SUP data

Aksel
Participant
0 Kudos

Hi,

I'm trying to bring the standard App ERP ORDER STATUS to work.

On the client I have now the exception in the trace:

"Exception during parsing of data! NoEntitySchema File"

This is the trace in SUP:

2012-06-21 08:15:58.592 INFO PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel

2012-06-21 08:15:58.592 DEBUG PROXY Thread-282 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----

2012-06-21 08:15:58.592 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response body is obtained from BackEnd

2012-06-21 08:15:58.592 INFO PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Read response body from Gateway

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content encoding is ZIP ----------gzip

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content type|encoding|length--------application/atomsvc+xml----gzip----406----

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valuesap-usercontext=sap-language=DE%2f&sap-client=400; path=/

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valueMYSAPSSO2=AjQxMDMBABhBAFcARQAgACAAIAAgACAAIAAgACAAIAACAAY0ADAAMAADABBBADkAMQAgACAAIAAgACAABAAYMgAwADEAMgAwADYAMgAxADAANgAyADEABQAEAAAACAYAAlgACQACRAD%2fAawwggGoBgkqhkiG9w0BBwKgggGZMIIBlQIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBMYIBdDCCAXACAQEwbzBkMQswCQYDVQQGEwJERTEcMBoGA1UEChMTU0FQIFRydXN0IENvbW11bml0eTETMBEGA1UECxMKU0FQIFdlYiBBUzEUMBIGA1UECxMLSTAwMjA0ODE1NDgxDDAKBgNVBAMTA0E5MQIHIBAIGRVFBTAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwNjIxMDYyMTA4WjAjBgkqhkiG9w0BCQQxFgQUEnNUxTcqiMSO6Uup2yfXphkv1DgwDQYJKoZIhvcNAQEBBQAEgYBfL4%2fnizCk8rMnrZoyHCsCXECEtaPDBDE9lEJPAx%21j7ygtvlyc%2fG4OPlTfJ4Yfbr1YVtRCQo8Xy4cE%214ogmg62u94dkjt29jeqVssNdu4aIo%2fBvr03Fxvs8QsphDzUYcntumq1SaC4rGtKyJUmmapTV06W99ImebfjnxbCUvjCuw%3d%3d; path=/; domain=<domain>

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-type          Response header valueapplication/atomsvc+xml

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-encoding          Response header valuegzip

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-length          Response header value406

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyx-sap-odata-extension-version          Response header value0.9

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keydataserviceversion          Response header value2.0

2012-06-21 08:15:58.576 DEBUG PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyserver          Response header valueSAP NetWeaver Application Server / ABAP 702

2012-06-21 08:15:58.576 INFO PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]Response code is HTTP/1.1 200 OK

2012-06-21 08:15:58.576 INFO PROXY MessageChannel Thread-268 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Recieved the response from the gateway

Maybe there is a small missing link??

Regards

Aksel

Accepted Solutions (1)

Accepted Solutions (1)

Aksel
Participant
0 Kudos

Hi,

this issue is now solved.

(before the ticket was handled by SAP)

For others having problems with SAP ERP ORDER STATUS:

I changed the SICF service to client 400. So the addition to the URL - ?sap-client=400 - was not necessary anymore. I also scrapped the addition for the language - sap-language=DE.

So the URL in SUP connection properties for proxy was just like this:

http://<server>:8008/sap/opu/sdata/sap/LWMSD_ORDERSTATUS/

It seemed that the app could not handle additional URL parameters.

Now it's working.

Regards

Aksel

Answers (1)

Answers (1)

rohith_deraje
Advisor
Advisor
0 Kudos
Hi  Aksel,
I suspect you are not passing the metaDataSchema while parsing the  collection/Searchdata.
You should parse in the below way.
Step1. Parse service document xml.
serviceDoc = parseSDMODataServiceDocumentXML(serviceDocxml);

Sample request URL format  "http://<Gateway Host:port>/sap/opu/odata/iwfnd/<ServiceDocName>/"

Step2. parse the metadata using service doc from step1.
metaDataSchema = parseSDMODataSchemaXML(entriesXML,serviceDoc);

Sample request URL format  "http://<Gateway Host:port>/sap/opu/odata/iwfnd/<ServiceDocName>/$metadata"

Step3. parse the collection/Searchdata using  metaDataSchema
Collection = parseSDMODataEntriesXML(entriesXML, "CollectionName", metaDataSchema)

Sample request URL format  "http://<Gateway Host:port>/sap/opu/odata/iwfnd/<ServiceDocName>/<CollectionName>"

You can get the refernce code at below links

ODP-reference Android app available @ https://cw.sdn.sap.com/cw/docs/DOC-146460

ODP-reference BB app available @ https://cw.sdn.sap.com/cw/docs/DOC-146459

ODP-reference iOS app available @ https://cw.sdn.sap.com/cw/docs/DOC-146461 

Regards
Rohith
Aksel
Participant
0 Kudos

Hi Rohith,

I would like to, but it is a Standard SAP Apps, I can't change anything in the coding on the client.

Regards

Aksel

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Askel,

Can you please check your gateway is returning proper metadata?  You can get the metadata by appending $metadata to the service document URL on browser?.

Also you can do the below settings to enable payload logging at SCC. This will help to check URl/request being fired and response returned from gateway.

1. Domain>>DomainName>>Log>>Settings>>New >> Enter a name

2.Select "Application Connection" and chose your User

3. Select "payload" and chose "request response"

4. Select "Enable after creation"

Save the settings.

Change the log level at Server>>Logs>>Unwired Server>>Settings>>Proxy>>Debug.

Fire a new request from your application.

Under Domain>>DomainName>>Log>>General>>Proxy, click on retrive to get the logs.

Check and verify the URL by entering same URL in any browser.

Please share the detailed logs once you follow the above steps.

Regards

Rohith

Aksel
Participant
0 Kudos

Hi Rohith,

the $metadata is working fine, I append it like this:

...sdata/sap/LWMSD_ORDERSTATUS/$metadata?sap-client=400&sap-language=DE

I can't make more logs visible with your steps. They are empty.

Regards

Aksel

Aksel
Participant
0 Kudos

Start of the Metadata xml:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:sap="http://www.sap.com/Protocols/SAPData" Version="1.0">
<edmx:DataServices m:DataServiceVersion="2.0">
<Schema xmlns="http://schemas.microsoft.com/ado/2008/09/edm" Namespace="LWMSD_ORDERSTATUS">
<EntityType Name="Customer" sap:content-version="1">
<Key>
<PropertyRef Name="CustomerNo"/>

</Key>

<Property Name="CustomerNo" Type="Edm.String" Nullable="false" MaxLength="10" sap:label="Debitor"/>

<Property Name="CustomerName" Type="Edm.String" MaxLength="40" sap:label="Name"/>

<Property Name="CustomerStreet" Type="Edm.String" MaxLength="60" sap:label="Straße"/>

<Property Name="CustomerHouseNo" Type="Edm.String" MaxLength="10" sap:label="Hausnummer"/>

<Property Name="CustomerStreetNo" Type="Edm.String" MaxLength="80"/>

<Property Name="CustomerCity" Type="Edm.String" MaxLength="40" sap:label="Ort"/>

<Property Name="CustomerPostalCode" Type="Edm.String" MaxLength="10" sap:label="Postleitzahl"/>

<Property Name="CustomerRegionCode" Type="Edm.String" MaxLength="3" sap:label="Region"/>

<Property Name="CustomerCountryCode" Type="Edm.String" MaxLength="3" sap:label="Land"/>

<Property Name="CustomerCountryCodeISO" Type="Edm.String" MaxLength="2" sap:label="ISO-Code"/>

</EntityType>

<EntityType Name="SalesOrder" sap:content-version="1">
<Key>
<PropertyRef Name="SalesOrderNo"/>

....

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Aksel,

Please recheck the steps and enable logs.It is difficult to troubleshoot without logs.

As I mentioned earlier parsing happens in below steps.

   Step1. Parse service document xml.

  serviceDoc = parseSDMODataServiceDocumentXML(serviceDocxml);

  Step2. parse the metadata using service doc from step1.

  metaDataSchema = parseSDMODataSchemaXML(entriesXML,serviceDoc);

  Step3. parse the collection/Searchdata using metaDataSchema from
step3

  Collection = parseSDMODataEntriesXML(entriesXML,
"CollectionName", metaDataSchema)

By enabling the logs, you can check if the URL getting fired  (For service doc, metadata and collection) and data returned by gateway for each request

If these things are correct, your application should work fine. 

Regards

Rohith

Aksel
Participant
0 Kudos

Hi Rohith,

I tried already all steps you provided to turn on the logs. Nothing appears there.

Something wrong with SUP?

Wishes,

Aksel

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Askel,

If you are not getting domain logs, please check atleast server logs are getting generated.

Under Server>>Logs>>Unwired Server>>General.

Clear all the existing logs using "Delete" button. Try a fresh  request response. Click on "retrieve" button to get the logs.

Regards

Rohith

Aksel
Participant
0 Kudos

Hi Rohith,

the logs did not really change in comparison to the first post:

2012-06-26 13:51:03.300 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel

2012-06-26 13:51:03.269 DEBUG PROXY Thread-371 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response body is obtained from BackEnd

2012-06-26 13:51:03.269 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Read response body from Gateway

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content encoding is ZIP ----------gzip

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content type|encoding|length--------application/atomsvc+xml----gzip----406----

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valuesap-usercontext=sap-language=DE%2f&sap-client=400; path=/

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valueMYSAPSSO2=AjQxMDMBABhBAFcARQAgACAAIAAgACAAIAAgACAAIAACAAY0ADAAMAADABBBADkAMQAgACAAIAAgACAABAAYMgAwADEAMgAwADYAMgA2ADEAMQA1ADYABQAEAAAACAYAAlgACQACRAD%2fAawwggGoBgkqhkiG9w0BBwKgggGZMIIBlQIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBMYIBdDCCAXACAQEwbzBkMQswCQYDVQQGEwJERTEcMBoGA1UEChMTU0FQIFRydXN0IENvbW11bml0eTETMBEGA1UECxMKU0FQIFdlYiBBUzEUMBIGA1UECxMLSTAwMjA0ODE1NDgxDDAKBgNVBAMTA0E5MQIHIBAIGRVFBTAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwNjI2MTE1NjI2WjAjBgkqhkiG9w0BCQQxFgQUcEpQQ6Ky10%2fPZw2EL8RMEvJR0PEwDQYJKoZIhvcNAQEBBQAEgYCGHVc%2fYY%21OIEiHbEmlMLJ%21NdQscHZ3Tq4jdZMWdQbgVHCgeXez3Rty5pZR2ylZcag5t9uPaO%2fQ5wN4vb%2fGm3mwvaZyv%2fKGvkBiLgHgFv8Qm7P51PlNnEJPm9Dcv0YvK7W212OZGXP50lUY4IN0hx2KwEp5H%2faqZzzzh%2fqj28AfKQ%3d%3d; path=/; domain=.c1-group.dom

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-type          Response header valueapplication/atomsvc+xml

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-encoding          Response header valuegzip

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-length          Response header value406

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyx-sap-odata-extension-version          Response header value0.9

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keydataserviceversion          Response header value2.0

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyserver          Response header valueSAP NetWeaver Application Server / ABAP 702

2012-06-26 13:51:03.269 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]Response code is HTTP/1.1 200 OK

2012-06-26 13:51:03.269 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Recieved the response from the gateway

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished firing the request to GW-----------

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Leaving FireRequest Method-----------

2012-06-26 13:51:03.269 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished Execute-----------

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Before Execute-----------

2012-06-26 13:51:02.206 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP: Firing the request to the Gateway

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]----Host request header set is ----<server>:8008

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept    value=application/atom+xml

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Content-Type    value=application/atom+xml;type=entry

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Encoding    value=gzip

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=X-Requested-With    value=SAPDataLibrary-ObjC

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Authorization    value= Not printed for security reasons

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Language    value=de

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy fireRequest()----------

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------About to fire the request to the GW-----------

2012-06-26 13:51:02.206 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----leaving getConnection() of GWCConnectionPoolManager  -Connection is not from pool---

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (2)false

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://<server>:8008/sap/opu/sdata/sap/LWMSD_ORDERSTATUS/?sap-client=400&sap-language=DE/

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.bsuite.erp.ops.orderstatus

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.ops.orderstatus"},{"request":"GET"},{"url":"http://<server>:8008/sap/opu/sdata/sap/LWMSD_ORDERSTATUS/?sap-client=400&sap-language=DE/"},{"Accept-Encoding":"gzip"},{"X-Requested-With":"SAPDataLibrary-ObjC"},{"Content-Type":"application/atom+xml;type=entry"},{"Accept":"application/atom+xml"},{"Accept-Language":"de"}]

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is awe

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.ops.orderstatus"},{"request":"GET"},{"url":"http://<server>:8008/sap/opu/sdata/sap/LWMSD_ORDERSTATUS/?sap-client=400&sap-language=DE/"},{"Accept-Encoding":"gzip"},{"X-Requested-With":"SAPDataLibrary-ObjC"},{"Content-Type":"application/atom+xml;type=entry"},{"Accept":"application/atom+xml"},{"Accept-Language":"de"}]

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :

2012-06-26 13:51:02.191 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:

2012-06-26 13:51:02.191 DEBUG PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------

2012-06-26 13:51:02.191 INFO PROXY MessageChannel Thread-238 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Askel,

This is fine.The above request is for service document.

But there should be 2 more request made by your application. One for $metadata and one for Collection/searchURL. Please check you got the HTTP resoinse 200 for them as well. Also check gateway has returned you the data.

If above things are fine and still you are facing the issue please create a OSS ticket for further inspection.

Regards

Rohith

Aksel
Participant
0 Kudos

Ok,

this is the problem, after this first request there is only the error on the device I stated above "Exception during parsing of data! NoEntitySchema File"

and no further request is done.

I will create a ticket then.

Regards

Aksel

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Askel.

just do a fresh registration and try again. Typically applications fire those request for the first time and catch the metadata and service document. Further they may fire only request for search data. For parsing of search data, they may use servce doc and schema/metadata from catch.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

I am also trying to sync with ERP Order status app with SUP2.1.2.

But i am getting HTTP/1.0 403 Forbidden as response code from NW gateway.

what could be the problem, as i have configured all the configurations in a recommended way on NW GW & SAP Backend.

Please suggest.

regards,

shrikant.