16-04-2013, 04:02 PM
PROJECT REPORT On MEDIA STREAMING IN MOBILE USING J2ME TOOLKIT
MEDIA STREAMING.pdf (Size: 2.31 MB / Downloads: 71)
ABSTRACT
“Traffic Viewer” is an Internet browser application designed to view traffic web cam images. The application allows the mobile user to see online traffic images from Remote Location .Traffic Viewer proxy server technology gives the user high quality images with much less (General Packet Radio Service)GPRS or Universal Mobile Telecommunication System(UMTS) traffic, so the communication with the web will not be a cost problem at today’s GPRS or UMTS rates.
CLIENT:
The modules has been implemented in J2ME used to connect to the server which is running in web server. The server modules retrieve the images from the webcam and sends to the client for display.
SERVER:
The Server module connects the web cam through the jmf java media framework which in turn connects the web cam for getting the images the images will be displayed for each and every specified delay seconds.
INTRODUCTION
Project Description:
Traffic Information is a J2ME based MOBILE Application that allows the customer to access some current information in the metro city. The main motive of this application to make the users to view the traffic information on the mobile.
If Users selects any of the option then they can retrieve the related information from the server. Traffic information is an optional package that supports on small wireless device. It has been designed to meet the stringent size requirements of small, resource constrained device, as well as challenges inherent in wireless connection: limited band width, traffic, slow connections, and small screen resolution. This API allows simple access information of metro cities.
The presentation tier is designed in J2ME (Java2MicroEdition) through which the users can view the details in the Wireless Tool Kit. The Data Tier is developed in J2EE (Java2EnterpriseEdition).
J2EE (Java2 Enterprises Edition):
Today, more and more developers want to write distributed transactional applications for the enterprise and leverage the speed, security, and reliability of server-side technology. If you are already working in this area, you know that in today’s fast-moving and demanding world of e-commerce and information technology, enterprise applications have to be designed, built, and produced for less money, with greater speed, and with fewer resources than ever before.
To reduce costs and fast-track application design and development, Java 2 Platform, Enterprise Edition (J2EE) provides a component-based approach to the design, development, assembly, and deployment of enterprise applications. The J2EE platform offers a multitiered distributed application model, reusable components, a unified security model, flexible transaction control, and Web services support through integrated data interchange on Extensible Markup Language (XML)-based open standards and protocols.
Distributed Muttered Applications:
The J2EE platform uses a multitiered distributed application model for enterprise applications. Application logic is divided into components according to function, and the various application components that make up a J2EE application are installed on different machines depending on the tier in the multitiered J2EE environment to which the application component belongs. The J2EE applications divided into the tiers described in the following list
•Client-tier components run on the client machine.
•Web-tier components run on the J2EE server.
•Business-tier components run on the J2EE server.
•Enterprise information system (EIS)-tier software runs on the EIS server.
Although a J2EE application can consist of the three or four tiers shown in below. J2EE multitiered applications are generally considered to be three-tiered applications because they are distributed over three different locations: client machines, the J2EE server machine, and the database or legacy machines at the back end. Three-tiered applications that run in this way extend the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage.
Web Clients :
A Web client consists of two parts: dynamic Web pages containing various types of markup language (HTML, XML, and so on), which are generated by Web components running in the Web tier, and a Web browser, which renders the pages received from the server.
A Web client is sometimes called a thin client. Thin clients usually do not do things like query databases, execute complex business rules, or connect to legacy applications. When you use a thin client, heavyweight operations like these are off-loaded to enterprise beans executing on the J2EE server where they can leverage the security, speed, services, and reliability of J2EE server-side technologies.
Application Clients :
A J2EE application client runs on a client machine and provides a way for users to handle tasks that require a richer user interface than can be provided by a markup language. It typically has a graphical user interface (GUI) created from Swing or Abstract Window Toolkit (AWT) APIs, but a command-line interface is certainly possible.
Application clients directly access enterprise beans running in the business tier. However, if application requirements warrant it, a J2EE application client can open an HTTP connection to establish communication with a servlet running in the Web tier.
J2EE Server Communications:
Figure shows the various elements that can make up the client tier. The client communicates with the business tier running on the J2EE server either directly or, as in the case of a client running in a browser, by going through JSP pages or servlets running in the Web tier.
Your J2EE application uses a thin browser-based client or thick application client. In deciding which one to use, you should be aware of the trade-offs between keeping functionality on the client and close to the user (thick client) and off-loading as much functionality as possible to the server (thin client). The more functionality you off-load to the server, the easier it is to distribute, deploy, and manage the application; however, keeping more functionality on the client can make for a better perceived user experience.
Enterprise Information System Tier:
The enterprise information system tier handles enterprise information system software and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems, and other legacy information systems. J2EE application components might need access to enterprise information systems for database connectivity, for example.
J2EE Containers :
Normally, thin-client multitiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multithreading, resource pooling, and other complex low-level details. The component-based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition, the J2EE server provides underlying services in the form of a container for every component type. Because you do not have to develop these services yourself, you are free to concentrate on solving the business problem at hand.