MWA Setup, Testing, Error Logging and Debugging

This article will explain to you                                                                   
    a. Where the Mobile Web Apps config files are located
    b. MWA Startup and Shutdown Scripts and how those are used
    c. Directory Structure for MWA in both 11i and R12
    d. How to develop and test your pages
    e. Where the log files are created, and tips to debug MWA Applications

Configuration Files

• mwa.cfg: This file has information about the DBC file location, Log Dir Location, Telnet Port no Location, Error Logging Level etc.
  This info will be used by Mobile Applications on runtime.
• default_key.ini: This file is used to map the keys of the mobile device to some specific functionality.
  Use the default file if you don’t want to customize anything.
• deviceIP.ini: This file maps the configuration files and host name with the mobile device

MWA server start-up and shutdown:

• mwactl.sh: This file is used to start/stop the MWA listener on specific port.
  Basically, if you develop and deploy a Mobile page into the instance, you have to bounce the MWA server by
  stopping and starting the Listener at your port to see your changes.
  
  
  Start/stopping Listener
  Start:
  mwactl.sh start  
  
  
  Stop :
  mwactl.sh -login stop_force  
  
  
  
  
  File Location
  Directory Structure in R11
  $MWA_TOP/bin
  $MWA_TOP/secure
  
  
  Directory structure in R12
  $INST_TOP/admin/scripts
  $INST_TOP/admin/install
  
  
  
  (eg)In R12, INST_TOP may look like:
  /u01/appldev/DEV/inst/apps/DEV_w-oraap01
  
  
  
  
  MWA GUI Client Setup
  In order to simulate the Mobile Device on your PC, you have to do the following setup:
  Step 1:
  Create 2 directories say C:\MWA\lib and C:\MWA\log
  Extract the files from the patch 4205328 into C:\MWA\lib
  
  
  Step 2:
  Download jdk1.1.8 from java.sun.com and place it in C:
  
  Step 3:
  Create a batch file say Start_MWA.bat with the following contents
  set MWA_GUI_TOP=C:\MWA\
  set JAVA_TOP=c:\jdk1.1.8
  %JAVA_TOP%\bin\java -classpath %JAVA_TOP%\lib\classes.zip;%MWA_GUI_TOP%\lib\j4205328.zip oracle.apps.mwa.awt.client.StartGUI
  
  
  Step 4:
  Whenever you run this batch file, you must be able to see the GUI client for MWA
  
  
  
  
  Development and Deployment:
  The development of Mobile Applications can be done using any IDE like JDeveloper, Eclipse etc. After that in order to
  test the application, we have to deploy it in the Apps instance say in a directory like $JAVA_TOP/xxx/custom/server.
  
  
  In order to test it, we should have our own function in AOL. This function should refer to the Function Java Class
  name of the Mobile Application
  (eg) xxx.custom.server.CustomTestFunction
  
  
  Read more on Senthilkumar Shanmugam !!!