The architecture is as follows:
A J2ME MIDP 2.0 application was built and tested using Sun Wireless Toolkit 2.1. The application can be moved to real mobile device using Bluetooth, Infra- red or USB cable etc. The application could also be downloaded from the server using OTA (On The Air) provision. The application is then installed in the mobile device by the Application manager on the device.
This application on demand makes an HTTP/HTTPS connection with the web application server (SAP WebAS, in our case) in order to get the required information. It uses GPRS to make the HTTP connection to the web server.
On the server side, we have a J2EE application, an EAR application deployed, which makes use of JCO to connect to the SAP system and call the respective BAPI or RFC enabled function module in order to obtain the required information.
On SAP, we have standard or customized function module which is remotely enabled. ABAP coding is required for the customization.
In our case, we used the application to extract information like Receivable Dues, Contract Status and Contacts of a particular client. We also tried updating the system for Pending Complaints for a particular client.
J2ME enabled device being a thick client, we could also put some decision making logic on mobile front, provided its not very complex as we are dealing with mobile phones which have limited processing abilities. The whole thing was tried out in simulation form using Sun Wireless Toolkit 2.1. This can also be tested successfully in real environment. Here are some snapshots of the application..
1. Login Page