本科生毕业设计（论文）英文翻译毕业设计题目：基于全球卫星定位系统GPS的软件开发学 院： 专业班级： 学生姓名： 指导教师： 2008年 4月 7日Deploying Wireless Java Applicationsby Qusay H. MahmoudOctober 2002 Developers usually build, test, and evaluate an application on a platform similar to the one on which it will be deployed and run. Development of wireless Java applications is more challenging because they typically are developed on one platform (such as Solaris or MS Windows) but deployed on a totally different one (such as a cell phone or PDA). One consequence is that, while emulators enable developers to do some of their testing on the development platform, ultimately they must test and evaluate the application in the very different environment of a live wireless network. The aim of this article is to show you the different ways you can download local and network applications to J2ME-enabled devices, for both testing and final deployment. After a brief review of wireless Java applications and their development life-cycle, the article shows you how to: Deploy wireless applications remotely Download local and remotely deployed applications Download applications over the air Wireless Java ApplicationsWireless Java applications fall into two broad categories: Local applications (also called stand-alone applications) perform all their operations on a handheld wireless device and need no access to external data sources through a wireless network. Examples include calculators and single-player games. Network applications consist of some components running on a wireless device and others running on a network, and thus depend on access to external resources. An example would be an email application, with a client residing on a wireless phone that interacts with a Simple Mail Transfer Protocol (SMTP) server to send messages. Although these two types of applications are different, they are deployed in the same way. The big difference shows up later: Local applications are easier to test than network applications. For example, a calculator application can run on a wireless phone even when it is not connected to any network, but an email client wont work without a connection to the SMTP server that actually transmits the messages. Wireless Java Applications Development LifecycleThe development life-cycle of MIDlets and other wireless Java applications comprises three steps: Write the application. Use your favorite wireless application development environment and tools to develop the application. My favorite is the J2ME Wireless Toolkit. It has a simple and intuitive user interface that makes it easy to start developing wireless applications. More importantly, it includes several emulators for testing your applications. (Some of what follows will assume you use this toolkit too. If you use another development environment, youll have to adapt what you read here to that environment.) Test the application in an emulation environment. Once the application compiles nicely, the best place to begin testing it is an emulator. The J2ME Wireless Toolkit comes with several, including Motorola i85s, PalmOS device, and RIM Blackberry. It is important to note, however, that these emulators do not simulate perfectly all of the features of the corresponding devices. They are merely skins with the appropriate dimensions, so the following step is crucial.Download the application to a physical device and test it. Once you are happy with the applications performance on one or more emulators, download it to a real device and test it there. If its a network application, test it on a live wireless network to ensure that its performance is acceptable. This articles focus is on that last step: deploying and testing the application on a physical device. Deploying and Running Remote ApplicationsThe J2ME Wireless Toolkit enables you to run your local wireless application from within the development environment; the JAD and JAR files are available on your own system (if youre using the J2ME Wireless Toolkit, in /apps/YourProject/bin). If you wish to market your wireless applications, however, you need to deploy them where users from all over the world can access them. Remote DeploymentTo deploy your wireless applications remotely: Upload your application files (JAD and JAR) to a remote web server. If your project is named games, for instance, upload the files: and from the bin directory of your project home (for example, /apps/games/bin). Note that the two files must end up in the same directory on the server.Reconfigure the web server so that it recognizes JAD and JAR files: For the JAD file type, set the file extension to .jad and the MIME type to . For the JAR file type, set the file extension to .jar and the MIME type to application/java-archive. How you configure the web server de