Resources | Resources |




The Simulator utilizes Target Manager to create and maintain "targets", or simulated devices based on provided device templates, called profiles. The following image is a graphic representation of the major components of the Simulator.


A platform is designated by its version (for example, Brew MP 1.0.0, 1.0.1, 1.0.2). Each platform has a defined directory structure. A profile may reference platform files using a combination of platform version and location (path) within the platform. Every external release of the Brew MP SDK will result in a new set of platform files. The platform provides all the device/target related components for a single version of Brew MP.


A device profile is all the data that describes a commercial Brew MP device and its simulation runtime. Device profiles provide relevant device information, and contain the information and files required to create accurate simulation targets.

The relevant information is captured in an XML file, which is the core of the device profile. This XML file also contains information required for the construction of accurate simulation targets by referencing files associated with the device profile.

A profile includes the following:

  • XML metadata file
  • SWF file containing the device skin.
  • Any number of custom files for placement in the target
  • A directory structure within the profile's main directory


A simulation target is an isolated execution environment with its own directory on the PC. The target runtime binaries and settings match the actual device. The Target Executor is the process that loads the target.

Target Manager

Target Manager displays profiles for browsing. You can use Target Manager to create and delete targets, start targets and launch the Simulator UI. It reads device profiles, and copies the files from platform and profile to create a target (virtual machine). TM.exe is the command-line version of Target Manager.

Target Executor

Target Executor acts as the Win32 host process for a simulation target. When Target Executor starts up, it is analogous to powering on the physical handset and running Brew MP. It contains no UI, yet it is capable of running any simulation target, regardless of version. Each simulation target has a Brew MP version-specific target.dll and a1Host.dll. Target Executor loads these DLLs, creates the process and runs the simulation target. Target Manager also prevents conflicts in memory and in the file system during target execution. So Target Manager organizes and administers, and Target Executor resides in memory as a process (simtargetexecutor) on the PC.