Show TOC

DOE ConnectionLocate this document in the navigation structure

Connections log data includes domain connections for DOE connection types, if enabled. Check the detail pane for additional columns that may be available. Enable Payload to see payload data that may be available.

  • Time – the time and date stamp for the log entry.
  • Application ID – the unique identifier assigned to the registered application. Values may include a number, blank, or HWC, depending on the client type.
  • Application Connection ID – the unique identifier for a user application connection.
  • User – the subscription user for the package.
  • Event Type – the DOE-C event type, such as Acknowledged, Duplicate Ignored, Exclude, No Response (from client or server), Packet Dropped, Registration Response, Resend (from client), Status Request (from client or server), DOE-C Subscription, and DOE-C Data Import.
  • Package – the name of the package to which the subscription belongs.
  • MBO – the mobile business object used.
  • Operation – the MBO operation.
  • Connection – the managed connection used. Its value is DOE for DOE-C logs.
  • Client ID – the identifier for the DOE-C client.
  • Physical ID – the DOE-C generated physical identifier registered with DOE at subscription.
  • Subscription ID – the DOE-C generated subscription identifier registered with DOE at subscription.
  • Logical Device ID – the DOE-C logical device identifier, generated by DOE and provided to DOE-C upon successful subscription.
  • Message Direction – the DOE-C message direction, either client to SAP Mobile Server, or SAP Mobile Server to client.
  • Thread ID – the identifier for the thread used to process the request.
  • Node ID – the server node on which the request is received.
  • Error – the error message if any.
Payload and detail columns:
  • Device ID – the core and administrative (MMS) device ID.
  • Domain – the core and administrative (MMS) domain name.
  • JSON Message Content – the messaging synchronization JSON message (payload). This is the SAP Mobile Platform-specific representation of the incoming DOE XML message in JSON format. DOE-C receives XML the payload from DOE in response, which is then parsed and converted to a JSON string and sent to the client.
  • XML Message Content – the DOE SOAP messages (payload). This represents either an XML request in a format for sending to DOE by DOE-C, or an XML payload response received from DOE as applicable.
  • Endpoint Name – the core and administrative (MMS) endpoint name.
  • DOE server message ID – the SAP DOE reliable messaging server message ID.
  • DOE client message ID – the SAP DOE reliable messaging client message ID.
  • DOE-C server message ID – the DOE-C client-side SAP DOE reliable messaging server message ID.
  • DOE-C client message ID – the DOE-C client-side SAP DOE reliable messaging client message ID.
  • DOE-C method name – the DOE-C method being executed.
  • DOE-C action name – the DOE SOAP action.
  • Push to – the messaging asynchronous response queue.
  • Address – the remote URL of the DOE server for this subscription (for example, http://<saphost>:50015/sap/bc/DOE_ESDMA_SOAP?sap-client=600).
  • Log – the DOE-C subscription-specific log level.
  • Extract Window – the DOE extract window for a subscription. This value determines the maximum number of unacknowledged "in-flight" messages allowed by the DOE reliable messaging protocol.
  • PBI – the messaging synchronization "piggy backed import" setting for the subscription.
  • Boolean property – indicates whether replay after-images can be piggy-backed onto replayResult and replayFailed messages (default is false).