Connection Log

Connections log data includes domain connections for specific connection types to backend data sources, including DOE, JDBC, REST, SAP, and SOAP, if enabled. Check the detail pane for additional columns that may be available. Enable Payload to see payload data that may be available.

DOE Connection

  • 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 Unwired Server, or Unwired 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.
Note: Payload and detail columns:
  • Device ID – the core and administrative (MMS) device ID (payload).
  • Domain – the core and administrative (MMS) domain name (payload).
  • JSON Message Content – the messaging synchronization JSON message (payload). This is the SUP-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 (payload).
  • 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).

JDBC Connection

  • 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 name of the user associated with the application ID.
  • Stage – the current stage of processing - START or FINISH.
  • 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.
  • 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.
Note: Payload and detail columns:
  • Input Parameters – the parameters used in a JDBC endpoint operation (payload). This will vary by operation.
  • Query – the SQL statement used in a JDBC endpoint operation (payload). This will vary by operation.
  • Device ID – the core and administrative (MMS) device ID (payload).
  • Domain – the core and administrative (MMS) domain name (payload).
  • Endpoint Name – the core and administrative (MMS) endpoint name.
  • Database Product Name – the remote database product name, such as "SQL Anywhere".
  • Database Product Version – the remote database version, such as "11.0.1.2044".
  • Driver Name – the database driver used, such as: "jConnect™ for JDBC™".
  • Driver Version – the database driver version, such as "jConnect™ for JDBC™/7.07 GA(Build 26666)/P/EBF19485/JDK 1.6.0/jdbcmain/Wed Aug 31 03:14:04 PDT 2011".
  • Database User Name – the database user account.

REST Connection

  • 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 name of the user associated with the application ID.
  • Stage – the current stage of processing - START or FINISH.
  • 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.
  • URL – the URL associated with the managed connection.
  • Action – the GET, POST, PUT, or DELETE action.
  • Response Status – the response status code for the invocation.
  • 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.
Note: Payload and detail columns:
  • Response – the message returned by the EIS system in response to a request (payload).
  • Device ID – the core and administrative (MMS) device ID (payload).
  • Domain – the core and administrative (MMS) domain name (payload).
  • Endpoint Name – the core and administrative (MMS) endpoint name.
  • HTTP Header Parameters – "Accept-Encoding: gzip, Accept-Encoding: compress".

SAP Connection

  • 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 name of the user associated with the application ID.
  • Stage – the current stage of processing - START or FINISH.
  • Package – the name of the package to which the subscription belongs.
  • MBO – the mobile business object used.
  • Operation – the MBO operation.
  • BAPI – the SAP BAPI used as the data source.
  • Connection – the managed connection used.
  • Properties – the list of name:value pairs.
  • 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.
Note: Payload and detail columns:
  • Parameters – input that was supplied to the operation; this will vary per request and operation (payload).
  • Device ID – the core and administrative (MMS) device ID (payload).
  • Domain – the core and administrative (MMS) domain name (payload).
  • Endpoint Name – the core and administrative (MMS) endpoint name.
  • SAP Host – the remote system hostname (if available).
  • SAP User – the SAP user for the operation.

SOAP Connection

  • 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 name of the user associated with the application ID.
  • Stage – the current stage of processing - START or FINISH.
  • 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.
  • Service Address – the service address URL.
  • Action – the SOAP action.
  • 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.
Note: Payload and detail columns:
  • Request (payload) – SOAP messages sent to the remote SOAP service.
  • Response (payload) – SOAP messages received from the remote SOAP service.
  • Device ID – the core and administrative (MMS) device ID (payload).
  • Domain – the core and administrative (MMS) domain name (payload).
  • Endpoint Name – the core and administrative (MMS) endpoint name.
  • Connection Timeout – the response timeout window, in milliseconds.
  • Authentication Type – the authentication type, either "None", "Basic", "SSO2", or "X509".
Parent topic: Domain Log Categories