Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS

Get PDF Book Print View

Document Information

Getting Started


Using Sample Projects

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Network Monitoring

Monitor Network Traffic

Filter Messages

Sort Messages

Save and Load Network Monitor Information

Clear the Message Tree

Lightweight UI Toolkit

Security and MIDlet Signing

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)

On-device Debugging

Command Line Reference


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSR 180: SIP Communications

JSR 184: Mobile 3D Graphics

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 226: Scalable 2D Vector Graphics

JSR 229: Payment API Support

JSR 238: Mobile Internationalization API (MIA)

JSR 256: Mobile Sensor API Support


Monitor Network Traffic

  1. In the Device Selector window, right-click on a device and choose Properties.
  2. Check the Enable Network Monitor option. When you next run an application on the device, the network monitor opens.

    You can also edit the device.properties file to set netmon.enabled to true. The properties file is located in the device instance directory, as described in File Locations.

  3. Start your application.

    When the application makes any type of network connection, information about the connection is captured and displayed.

    network monitor showing sockets, http and datagrams

    The top frame displays a list of messages. Click a message to display its details in the bottom frame.

    In the Hex View, message bodies are shown as raw hexadecimal values with the equivalent text. To avoid memory issues, the Hex view is currently limited to 16kB of data.

    Note - You can examine messages that are still in the process of being sent. Incomplete messages are indicated by bold highlighting in the message tree.

Related Information