Analyzing SDK traffic and events

You can analyze the SDK traffic and events in the Traffic view. The Traffic view displays events that occur between the SDK and an external entity, such as a gateway simulator or the Internet. (To trace network events that occur in the KVM, see Setting MIDP tracing and speed options

To use the Traffic view:

  1. From the Emulator menu bar, navigate to Tools > Diagnostics. The Diagnostics window appears.

  2. Open the Traffic view by clicking the plus sign next to it.

    The current list of transactions that have occurred while the SDK is communicating is displayed:

The most recent transaction appears at the bottom of the list.

  1. To display specific transaction types, click Monitor and check the transaction categories you want to display. The information about the transactions you do not check is available but not displayed until you check the transaction. These settings are persistent between SDK instance invocations. The categories are:

    Check this To display information about
    Requests Requests that originate in the SDK. For example, when the SDK sends a request to a web server, the transaction is recorded under Requests.
    Content Responses Responses made to the SDK as a result of a request that the SDK made. For example, a website responds to the SDK’s request for the site by loading it on the browser. The transaction is recorded under Content Responses.
    Pushed Messages A transaction that is not a result of a request the SDK made. Examples of these transactions include MMS messages that you can send to the SDK from IDEs, the CLI, or File > Open.
    SMS Sent SMS messages sent, including the size of whole messages and message fragments.
    SMS Received SMS messages received, including the size of whole messages and message fragments.
    TCP/UDP Sent Low-level protocol messages sent.
    TCP/UDP Received Low-level protocol messages received.
    Bluetooth Sent The size of Bluetooth data sent via the simulated Bluetooth connectivity.
    Bluetooth Received The size of Bluetooth data received via the simulated Bluetooth connectivity.

  2. Close the traffic view by clicking the negative sign next to it.

    When the Traffic view closes, the following summary is displayed:

    • Number of HTTP requests and responses.

    • Number of bytes sent and received on the TCP layer.

    • Number of bytes sent and received on the UDP layer.

    • Number of SMS fragments (PDUs) sent and received.

    • Number of bytes sent and received via Bluetooth.

The events are triggered as the content on the SDK changes:

This event Is triggered by
HTTP or HTTPS requests and responses A MIDlet, the browser, or any other built-in phone application sends an HTTP/HTTPS request or receives a response to such a request.
TCP stream data sending and receiving A MIDlet, the browser, or any other built-in phone application sends or receives TCP data.
UDP datagram sending and receiving A MIDlet or built-in phone application sends or receives UDP data.
MMS message sending and receiving A MIDlet or built-in phone application sends or receives an MMS message. This includes:

  • An SDK instance sends or receives an MMS from another SDK instance.

  • The user opens an MMS message using File > Open.

  • An external tool pushes an MMS message to the SDK.
SMS message fragment sending or receiving A MIDlet or built-in phone application sends or receives an SMS message fragment.
SMS message sending or receiving A MIDlet or built-in phone application sends or receives an SMS message.
Bluetooth data sending or receiving A MIDlet or built-in phone application sends or receives data via Bluetooth connectivity. This connectivity is simulated in the SDK, by using the Nokia Connectivity Framework.
© Nokia 2012.