Viewing Error Codes in Log Records

You can view any EIS error codes and the logically mapped HTTP error codes in the log record.

For example, you could observe a "Backend down" or "Backend login failure" after the following sequence of events:

1. Deploying packages to Unwired Server.
2. Performing an initial synchronization.
3. Switching off the backend or change the login credentials at the backend.
4. Invoking a create operation by sending a JSON message.

   JsonHeader
   {"id":"684cbe16f6b740eb930d08fd626e1551","cid":"111#My1:1","ppm":"eyJ1c2VybmFtZSI6InN1cEFkbWluIiwicGFzc3dvcmQiOiJzM3BBZG1pbiJ9","pid":"moca://Emulator17128142","method":"replay","pbi":"true","upa":"c3VwQWRtaW46czNwQWRtaW4=","mbo":"Bi","app":"My1:1","pkg":"imot1:1.0"}
   
   JsonContent
   {"c2":null,"c1":1,"createCalled":true,"_op":"C"}

The Unwired Server returns a response. The code is included in the ResponseHeader.

ResponseHeader
{"id":"684cbe16f6b740eb930d08fd626e1551","cid":"111#My1:1","loginFailed":false,"method":"replayFailed","log":[{"message":"com.sybase.jdbc3.jdbc.SybSQLException:SQL Anywhere Error -193: Primary key for table 'bi' is not unique : Primary key value ('1')","replayPending":0,"eisCode":"","component":"Bi","entityKey":"0","code":500,"pending":false,"disableSubmit":false,"?":"imot1.server.LogRecordImpl","timestamp":"2010-08-26 14:05:32.97","requestId":"684cbe16f6b740eb930d08fd626e1551","operation":"create","_op":"N","replayFailure":0,"level":"ERROR","pendingChange":"N","messageId":200001,"_rc":0}],"mbo":"Bi","app":"My1:1","pkg":"imot1:1.0"}

ResponseContent
{"id":100001}