In order to get these OTA Tools provisioned on Reliance handsets developers are requested to send an email to rdp.query@relianceada.com giving details of Reliance IndiaMobile Number (RIM No), access plan (post paid or pre-paid), Reliance Handset Model and brief description of application developed / under development.

       WAP OTA Tool

       Reliance Developer Programme OTA Tool

       Client Side implementation for testing Server Side applications

    Testing applications through WAP OTA Tool

1. Place the .jad and .jar files at the proper location in developer environment and give the link in .wml file for testing application using WAP OTA Tool

2. Create .wml page and host the .wml page on the public domain IP.

3. Launch the RWorld/MoreServices/Tools/DADP/WAPOTATool. Enter the URL to access the .wml page. Select go option for list of uploaded Apps to be displayed on the menu. Select the appropriate application and launch the application. Once the application is launched the necessary checks can be done.

Sample .wml page
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="Reliance Communications" title=" Reliance Communications ">
<p><a href="http://IPAdress/MyApp/MyApp.jad">MyApp</a></p>
<p><a href="http:// IPAdress /JR/JungleRescue.jad">JR</a></p>
</card>
</wml>

In the .jad file "MIDlet-Jar-URL" should be pointed at the location where the .jar file is uploaded for ex: -
MIDlet-Jar-URL: http://IPAdress/MyApp/MyApp.jar"

Check 'MIDlet-Jar-Size' in the jad file (Corresponding to the actual jar size of the client application.

   Testing applications through Reliance Developer Programme OTA Tool

1. Register with 3-6 character user name (the same user name will be used for testing the uploaded application on the handset) for Reliance Developer Programme OTA Tool through Web Admin from the link below for uploading the .jad and .jar files. Reliance Developer Programme OTA Tool Web Admin link

2. Password will be sent through SMS. Password can be changed from the Web Admin Interface

3. Once the Registration is successful. Upload the .jad and .jar files through Web Admin Interface. If any problems in Registration please send email to dadp.query@relianceada.com

4. Launch the RWorld/MoreServices/Tools/DADP/DADPOTATool and enter the Username and Password. Select the option for download. List of uploaded Apps will be displayed on the menu. Select the appropriate application and launch the application. Once the application is launched the necessary checks can be done.

   Client Side implementation for testing Server Side applications

1. Add DADPRequest.java to your src folder. For example, if your application name is MyApp then typically it will look like: C:\wtk104\apps\MyApp\src\DADPRequest.java

Implementation of DADPRequest in MyApp
try {
originalURL=this.getAppProperty("_rapurl");
DADPURL=this.getAppProperty("DADPURL");
DADPRequest dadpReq=new DADPRequest(originalURL,"GET");
pscreen = new ProgressScrn(display);
pscreen.start();
display.setCurrent(pscreen);
RAPRequest req = new RAPRequest(DADPURL,1);
dadpReq.addParam("reqID",reqID); //Request ID if more than 1 request to Server
dadpReq.bundle();
req.addParam("originalURL",dadpReq.getOriginalURL());
req.addParam("originalMethod",dadpReq.getOriginalMethod());
if (!originalMethod4RAP.equals("GET")) {
req.addParam("paramString",dadpReq.getParamString());
}
RAPAsyncConn conn = RAPSystem.getConn();
conn.send(req,this,true);
} catch(Exception e) {
showErr("Unable to connect. Try again.");
}
System.gc();
}
2. Compile the project with wireless toolkit. (Also involves preverify)

3. Create Package for that project. (This will create respective jad and jar files in bin folder). Typically it will look like: C:\wtk104\apps\MyApp\bin\MyApp.jad, C:\wtk104\apps\MyApp\bin\MyApp.jar

4. Include DADPRequest.class and RelianceUI.jar (if Used) in the Package (for e.g. inside MyApp.jar)

5. Remove the unnecessary files from the jar file (For example, Reliance LOC APIs, sun package etc)

6. Edit the parameter 'MIDlet-Jar-Size' in the jad file (Corresponding to the actual jar size of the client application.

7. Place the .jad and .jar files at the proper location in developer env and give the link in .wml file for WAP OTA Tool or upload the executables from Reliance Developer Programme OTA Tool Web Admin Interface

Sample MyApp.jad file
DADPURL: http://dadp.wdsap.ricinfo.com/dadpgateway/DADPServlet
MIDlet-1: MyApp, MyApp.png, com.reliance.myapp.MyApp
MIDlet-Jar-Size: 26240
MIDlet-Jar-URL: http://IPAdress/MyApp/MyApp.jar (for WAP OTA Tool) (or) MyApp.jar (for DADP OTA Tool)
MIDlet-Name: MyApp
MIDlet-Vendor: Reliance
MIDlet-Version: 1.0
_rapsvc: 4.41
_rapurl: http://Domain Name or IP address/myappcontext/MyAppServlet

8. Deploy the Server side application (.ear file) on the public domain or IP on Port No: 80. Outbound access for the following port has been opened at Reliance's end
If the Server side part is deployed other than this port the application cannot be accessed

Changes to be done at the client code after testing the application
Once the application testing is completed. Remove the DADPRequest.class from the MyApps.jar and implementation of the DADPRequest in the application instead of passing the DADPURL in the RAPRequest. Pass _rapurl in the RAPRequest
_rapurl = this.getAppProperty("_rapurl ");
RAPRequest req = new RAPRequest(_rapurl,reqId);
instead of
DADPURL=this.getAppProperty("DADPURL");
RAPRequest req = new RAPRequest(DADPURL,1);
Submit the changed Executables including the Server side components to Reliance for taking the application live.