Professional Documents
Culture Documents
Mobile Applications Gui Client
Mobile Applications Gui Client
Overview............................................................................................................. 3
Advantages ......................................................................................................... 3
Software updates ............................................................................................... 3
Server Installation/Setup Instructions ........................................................... 4
Optional Server Side Setup.......................................................................... 4
Client Installation/Setup Instructions............................................................ 6
Desktop Client .............................................................................................. 6
On RF Device ............................................................................................... 7
For CrEme JVM....................................................................................... 7
For J9 JVM................................................................................................ 7
For Jeode JVM.......................................................................................... 7
Barcode Scanning.......................................................................................... 8
Capturing Trace Information...................................................................... 8
Page 2
OVERVIEW
Until Applications Release 11.5.10 Consolidate Update 1 (CU1), users could view
the transactions on their mobile devices only in character-mode interfaces. From
Applications Release 11.5.10 Consolidate Update 1 (CU1) release, users can
optionally view all their mobile device transactions in graphical user interfaces. To a
large extent, these GUIs are similar to the desktop windows. The performance
characteristics of the new GUIs are the same as that of the character-mode
interfaces.
To use the GUIs, users need to install a J2ME compatible Java VM and the GUI
client application on their mobile devices. Users can also work with the GUIs on
their desktops for which standard Java support in Windows is sufficient. Network
access requirements for the GUIs are the same as that of the character-mode
interfaces. Similar requirements apply to desktop units. There are no additional
MWA middle-tier requirements. Within an installation, a mix of graphical and
character-mode devices may be used, driven from the same MWA middle-tier
server. In addition, any device that can run the graphical version can optionally
switch to the character mode at any time.
ADVANTAGES
In the GUIs, the read-only and required fields are more visible with a different
background color unlike in the character-mode client.
Users can navigate more easily to the fields/command buttons before or after
the current position in the screen using their mouse instead of tabbing through
fields to get to the desired one in the character-mode client.
SOFTWARE UPDATES
Page 3
A new "GUI Client" entry on the device selection page is seeded with
$MWA_TOP/secure/gui_key.ini file. The following are the newly added GUI
parameters in gui_key.ini files. Optionally these parameters can be
customized/modified if required.
Parameter
mwa.gui.height
350
mwa.gui.width
300
VISIBLE_TEXT_WIDTH
10
mwa.gui.showOracleLogo
TRUE
mwa.gui.showLovIcon
TRUE
mwa.gui.FontSize
12
Page 4
mwa.gui.BackgroundColor
#FFFFFF
mwa.gui.PageTitleColor
#336699
mwa.gui.TableBackgroundCol #F7F7E7
or
mwa.gui.ReadOnlyTextColor #000000
mwa.gui.RequiredTextBackGr #FFFF77
oundColor
mwa.gui.GrayColor
#CCCCCC
mwa.gui.TableBorderColor
#CCCC99
mwa.gui.LogEnabled
FALSE
mwa.gui.logdir
\j2me\log
mwa.gui.SystemLog
system.log
mwa.gui.LogLevel
ERROR
mwa.gui.EnableLogRotation
Yes
mwa.gui.MaxLogFileSize
100000
Page 5
2.
3.
e.g. PATCH_TOP=C:\Temp\4205328
4.
5.
6.
7.
Enter the hostname and port number in the "Connect" window and hit
the "Connect" button. A maximum of 10 connections can be stored.
Optionally the host name and port number can be passed as parameters to
oracle.apps.mwa.awt.client.StartGUI which would directly connect to the
MWA Telnet Server without displaying the "Connect" window to the user.
Page 6
On RF Device
Note: Assuming \Windows\CrEme as the
CrEme JVM installed directory.
Installing GUI Client on RF Device is similar to the setup done for desktop as
described above. GUI Client can be installed on any RF Device that has Java VM
installed with J2ME Personal Profile option.
Perform the following steps to install GUI Client on RF Devices
1.
2.
3.
MWA_GUI_TOP=\mwagui\
%MWA_GUI_TOP%\lib
%MWA_GUI_TOP%\log
Download the Mobile Applications GUI Client patch and unzip it to
C:\Temp (Desktop)
e.g. PATCH_TOP=C:\Temp\4205328
4.
5.
Create a device specific startup script file to run the class file
oracle.apps.mwa.awt.client.StartGUI
6.
Sample content of device specific startup script file to launch the GUI
Client on WinCE RF Device
Page 7
Barcode Scanning
When user performs scan operations on RF device; make sure that scanned value is
pre-appended with DATASTREAMINDICATOR specified in the devices ini file
e.g. $MWA_TOP/secure/default_key.ini
Default DATASTREAMINDICATOR is ASCII 28.
Capturing Trace Information
The debug trace messages will be logged at the client side based on log level.
The log file and log directory will be taken from the .ini file parameters mwa.gui.SystemLog and mwa.gui.logdir. If the logdir parameter is invalid, then the
log file will be generated in the root directory from where the client in invoked.
GUI Client tracing can be captured in two ways.
1. Choosing the log level anything other than None on the clients connect
window. Note: Connect window will be displayed only if the client is started
without specifying the hostname and port in the command line.
2. By specifying the following parameters in the devices ini file on the server e.g.
$MWA_TOP/secure/default_key.ini
mwa.gui.LogEnabled
mwa.gui.logdir
mwa.gui.SystemLog
mwa.gui.LogLevel
Page 8