Mobile Phone Application rewrite

I have an existing mobile-device & server application that was written using J2me (mobile) and java servlet (server). I have a recent version of the server source but the mobile will require writing from scratch. ## Deliverables This application has the following core features: 1. A Mobile app that will run on Nokia 6230 (and later) and Samsung D500 (and later), using MIDP2 / CLDC1.0 2. The mobile must connect to the current server servlet using persistent socket connection, with no PDP context expiry. There is an auto-refresh parameter (in minutes) that can be set so the mobile automatically re-submits the data request. The mobile must detect active connection, and reconnect if necessary. 3. There is an active instruction menu that operates as follows: 3.1 There is a common 'Device List' (see [a] below) that can be user-entered (i.e. 831234567~User245~MyTest) or selected from a check-list (see [a] below). 4 different Data-Posts can be made to the server; 3.(a) List - receives a list from server, allow multiple select from the list, OK submits the list to MapLocate [b], 3.(b) MapLocate - receives image from server. Scrollable. Press (*) on keypad to close map, (#) to show date of image (provided in return data from server), (5) displays all other keys scroll 3.(c) Information - Same as MapLocate except the return is text. 3.(d) NEW - Instruct - text input area that submits mobile-entered chars (up to 120) to the server. 4. Each time the Mobile submits a request for data to the server, it includes the following parameters. 4.(a) The relevent instruction (from 3 above) 4.(b) List - if user has selected using check-select in 3.(a) then all checked items submitted together with (~) seperator 4.(c) UserID. Mobile-unique identity specified/created when the application is installed, and cannot be changed. This keeps control over what data each user may access. 4.(d) Days past (0 = today) and hour of day (0 = current) 4.(d).i) There must be a way to specify the day/hour of interest. The current app has such an entry screen. 4.(e) Each MapLocate request must include a Map Resolution parameter (0 to 9) and a Map Detail parameter (0 to 9). Again, a screen must exist to allow the user to adjust 5.1 The server IP/URL must be stored on app installation (editing of this is optional) 5.2 There is a code element that checks the data has arrived before initialising a new request. /*****************************/ Sample of data returned to mobile _<[login to view URL]>_ <[login to view URL]> /*****************************/ 1)(a) Complete and fully-functional working program(s) in installable form as well as complete source code (documented within reason) of all work done. 1)(b) We currently have the server component in a WAR file that automatically extracts under Tomcat 1.5, and this WAR file includes the Downloadable Mobile JAR/JAD files. 1)(c) The Mobile downloadable must record each instance of the download, as well as the UserID used for the download (this is part of the server code - make sure it functions) 1)(d) The Mobile must prompt for the Mobile Number the first time the user attempts to run it, and must successfully submit this (as an [Information] request, along with the UserID) to the server before the mobile app is allowed to operate. 2) Deliverables must be in ready-to-run condition: a) The Mobile Download file(s) must be provided with setup/install instructions for Windows 2003 Server running Tomcat 1.5.028, and Linux (FreeBSD) running on a SUN Netra (Solaris 7 OS but emulating Linux). b) Mobile installation options for Nokia 6230, 6630, 6680, and Samsung D500 are required. Additional mobiles requested are Nokia 6600 & SonyEricsson Z800 (but not required at this stage). 3) The Server App (if recompiled - suspect that is required) must a) Manage incoming (mobile) socket connections individually, timing the sockets out if inactive for more than 10 minutes and re-using expired sockets, b) connect to SQL Server 2000 - no connection pooling required at this stage c) contain instructions for changing the Server IP/user/password (the Tomcat component may not necessarily run on the same machine as the SQL Database) 4) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Server is to be capable of running on Windows 2003 Server, and on a Linux FreeBSD server. The designer will be expected to recommend a preferred server (hardware and operating system) because the system will go live on a new server. Mobile app must run on any (within reason) Nokia from the 6230 onwards, and Samsung D500 (or later). The Mobile must also be runnable within a PC framework (specifically for testing but also for some users who prefer to (or wish to) work from a PC)