Web services are programmable units that provide specific functionalities and are accessible to a large number of consumers using Internet protocols. The existing server to server web services are not applicable for mobile devices as they suffer from interoperability. The promise of providing interoperability in a heterogeneous world, as well as the possibility of offloading operations that require high processing power, make the mobile phones an ideal target device for accessing web services. Interoperability of Web Services mainly stems from its Extensible Markup Language (XML) based open standards. It uses SOAP protocol, can convey information between services in heterogeneous computing environments. However, despite the fact that the condition of mobile computing has so much in improved recent years, applying current Web Service communication models to mobile computing may result in unacceptable performance overheads. In this paper, we use J2ME web services specification to facilitate development of small, fast, and robust Java platform applications in the wireless marketplace. It provides two XML based optional packages that can be used to develop java web services for small, reduced-memory, handheld devices such as cell phones, PDAs, and pagers. These packages are:
Get your grade
or your money back
using our Essay Writing Service!
• Java API for XML Processing (JAXP)
• Java API for XML-based RPC (JAX-RPC)
Nowadays cell phones are the most popular mobile devices. However, it fails to provide heterogeneity and interoperability. There are some obstacles:
1) Unstable network connection status limiting the mobile phones ability to invoke web services efficiently;
2) Limited bandwidth of mobile communication channels that limits the ability to transmit SOAP messages;
3) Lack of an efficient XML parser used to process SOAP messages on the client.
To implement an asynchronous messaging system through a high performance communication channel to reduce the performance overhead in mobile communication.
Developing web service by using wireless toolkit manager and web technologies. So that, the web service client can runs the web applications on the mobile devices (mobile banking).
To provide context-awareness in mobile banking, this enables both personalization and ubiquity
Support a high-performance communication channel
With the increasing in the development of the technology and the e-commerce the accessing of the web services through the mobile devices have been in demand. Here we are accessing the web services through the mobile devices using J2ME where we are able to access simple service from the handheld devices using the interaction between the server and the customer end. Here we are using the JSR 172 web service architecture is based on the connected limited device configuration (CLDC 1.1). JSR 172 supports SAX (Simple API for XML) 2.0 based JAXP 1.2. It also supports major Web Services specifications, including SOAP 1.1, WSDL 1.1, XML 1.1, and XML Schema. It doesn't include UDDI because the specification focuses on how to consume remote services, not how to provide them. In other words the Web Service API on J2ME is a client-oriented API with a JAX-RPC style runtime environment.
The mobile devices become the client side of the web service, where these devices should have the capability to process in XML information. The JSR 172, which is the specification of the J2ME web service API helps to overcome the problems and supports the web service.
Functions of API: It enables long distance access for the SOAP/XML web services and analyses the capability of XML data. Where these two software packages occupy a memory space package XML-RPC requires 25-30KB space.
These above specifications have helped to support the client side web service and have not moved the web service provider up to the J2ME device capability.
The web service design involves 3 basic steps:
WSA radio device represents the sensation which is an application procedure which contains the JSR-172. The WS network sensation helps to carry the associated JSR 172 check stubs.
The web service carries the service of wireless network, internet, related coding of data, HTTP, SOAP/XML
The web servers provide service behind firewalls. The web server services to the rare application procedure rare end.
Mobile Service Center (MSC)
Always on Time
Marked to Standard
Programming Language : Java JDK6
Java Technologies : J2ME, JDBC, Web Services
Server : Glassfish Server, Tomcat 5.5
Operating System : Windows XP
Database Management System : Oracle / MS-Access
IDE : NetBeans 6.0
The purpose of this article was to show how two of the recently developed, optional Java ME APIs can be used to consume web services in a secure way. Web services are a good way to allow smaller devices and applications to use the processing power available on larger machine. J2ME is a runtime environment for resource-constrained environments. The Java Specification Request 172 (JSR 172) specifies standardized client-side technology to enable J2ME applications to consume remote services. As a result the developer can better focus on the application design and business logic, than to the connections with the Web services.