Академический Документы
Профессиональный Документы
Культура Документы
By Gayathri.D
(Revised by Sumeet kabra for MWA in R12)
Mobile Web Applications have changed a bit from 11i to R12 . The changes were made to R12 directory structure, for Security and for Autoconfig Engine For details about MWA in 11i proceed to next slide and about MWA in R12 jump to slide #34 ( type 34 and press Enter )
Set up overview Configuration Options - mwa.cfg file - Key Mappings (device IP.ini and default_key.ini) Starting/stopping Mobile Apps Server Starting Server on Multiple Ports Configuring RF Devices Accessing a Mobile Application.
Oracle Mobile Applications for Inventory Management: Todays demand for accurate, real-time information access, and inventory speed for several industries is forcing mobile applications to Find solutions for industries such as warehousing, manufacturing, Distribution, retailing, logistics, and transportation. MWA will use wireless devices that support Internet Standards, Web Browser, and Telnet client. Technologies involved are Java, XML, TCP/IP, and Oracle 8i. Devices as hand held Radio Frequency (RF), Personal Digital Assistants (PADs), and Internet Phones are examples of mobile devices.
Agenda or this presentation: Overview of Setup This will include a high-level description of all the components involved and how they interact. Configuration Options Before starting the server, its important that youve got the server configured properly. Properties such as log level, the location of your .dbc file (which holds information needed to log into your database), and the port number on which you want to start your server all need to be set before you start the server. You set these parameters in the mwa.cfg file. You might also want to map your devices keys to certain server-defined functions (like erase a line). Key mappings and other device-specific characteristics are set in .ini files. Well then run through how to start and shutdown the server. You might want to start multiple servers for load balancing reasons. We go through how start the server on multiple ports. Next, we explain how to configure RF devices to point to and access the Mobile Supply Chain Applications. We conclude with the procedure to get to an actual mobile application. At each step, well also go over some troubleshooting tips to solve any problems that might come up.
Diagram Overview Typical three-tier Internet architecture. In the back-end is your 11i Applications server with Oracle database. In the middle tier is the Mobile Supply Chain Applications server. This is analogous to the Forms server and HTTP server, but is used to deploy applications to Telnet clients. The client in this context will typically be a mobile RF device running a Telnet client. The RF device communicates with the MSCA server through an access point. You need to do two things to start using Mobile Supply Chain Applications. Start the Mobile Supply Chain Applications Server (after configuring it). Configure your RF devices so that they are communicating with the server.
Most of the server-related configuration parameters are located in the $MWA_TOP/admin/mwa.cfg file. The important properties in this file are: Dbc File Used to connect to database. Stores username, passwd, database port, and other info used to login. Log Directory Sets the location of your log directory. We default to $MWA_TOP/log, but you may want to change this to point to your regular Applications log directory. Telnet Port Number You can set the port number on which you want the Telnet server to run. Important: You should set the port to a number greater than 1024. Anything less will require you to be root. The configuration file defaults to port number 2323.
Environment Verification
Dispatcher Usage
You can map device keys to server-defined functions in .ini files. These are located in $MWA_TOP/admin. There is a default_key.ini file in there already, which can be used as a template for the specific devices you might be using. The server will use the default_key.ini file if it cannot find the appropriate .ini file for your device. The syntax is <Action>=<Key>=<Description> So, for example, killing (or erasing) an entire line in a text field is set to Control+K. You can change this to F9, for example, if Control Keys are not easily accessible on your device. In these .ini files, you can also specify the devices height and width so the server knows how to format the output. The idea is to create a new.ini file for each type of device you have. For example, if your company is using Intermec Trakker 2415s, create an intermec2415_key.ini file that is based off the default_key.ini file, but has height, width, and key settings for the Trakker 2415.
You associate your device witha key mapping file youve created in the $MWA_TOP/admin/deviceIP.ini file. Two ways to do this. First way... If your devices are DHCP, put in a line like: Intermec 2415=intermec2415_key.ini Options on the left of the equal sign will appear before users log in. The user must select the option corresponding to the device he/she is using. Second way...(preferred way) If your devices are on Static Ips, you can specify which IP addresses should be associated with which key mapping file. For example, 130.35.112.*=intermec2415.ini In this case, the options screen is not shown and the user doesnt have to select anything. The server automatically knows which key mapping file to use based on the devices IP.
Development Instance:
Dispatcher port = 30700 Telnet Server ports = 30702,30704,30706
Production Instance:
Dispatcher port = 30000 Telnet Server ports = 30002,30004,30006
Environment Verification
Verify that correct port numbers as per convention has been used
Verify the environment that is set correctly by sourcing the APPS_<sid>.env file Verify $MWA_TOP is set correctly Verify the DbcFolder and the DbcFile in the mwa.cfg file that is set to the location and filename of our Oracle Application .dbc file Verify the log directory that exists
Dispatcher Usage
Two Consecutive ports are needed per one MWA Server. One port is for
listening to RF device. The Other port is for listening to the MWA Server Manager. Three consecutive ports are needed for running the dispatcher. Mobile Users connect to Dispatcher port 30000. Dispatcher distributes mobile users among the three MWA servers.
2) Specify the dispatcher worker thread count. No. of connections per MWA Server.
mwa.DispatcherWorkerThreadCount = 15
3)
Specify the dispatcher clients per worker. No. of MWA servers per Dispatcher. mwa.DispatcherClientsPerWorker = 10
Before starting the server, be sure the following is true: Youve installed Oracle Applications 11i. You have logged onto your Applications machine as user oracle. The mwa.DbcFile parameter is set to the location of your Applications .dbc file. This property is set in your $MWA_TOP/admin/mwa.cfg file. the .dbc file is used for storing all the information the server needs to log into your database (e.g., name of the server, database port, etc.)
MWA_FIELD_DETAIL=CONTROLA MWA_BUTTON_ACCLRTOR=ESC MWA_PAGE_UP=CONTROLD MWA_PAGE_DOWN=CONTROLC MWA_ABOUT_PAGE=CONTROLX MWA_FLEX_POPUP=CONTROLF MWA_FLUSH_INPUT=CONTROLE MWA_DROP_CONNECTION=CONTROLZ INV Function Keys INV_GENERATE=CONTROLG WMS Function Keys WMS_SKIP_TASK=CONTROLS WMS_INVOKE_DEVICE=CONTROLP
deviceIP.ini
deviceIP.ini [device] DEFAULT=default_key.ini SYMBOL=gui_key.ini INTERMEC=intermec.ini
// Wildcard at the end of IP address is supported. [map] 127.0.0.1=default_key.ini
start 30002 & start 30004 & start 30006 & start_dispatcher &
stop_mwa.sh
export PATH = $PATH:/pimoti/applmgr/1159/mwa/11.5.0/bin:/pimoti/applmgr/common/util/jre/1.1.8/bin nohup /pimoti/applmgr/1159/mwa/11.5.0/bin/mwactl.sh -login mobileadm/mobileadm stop_force 30002 & nohup /pimoti/applmgr/1159/mwa/11.5.0/bin/mwactl.sh -login mobileadm/mobileadm stop_force 30004 & nohup /pimoti/applmgr/1159/mwa/11.5.0/bin/mwactl.sh -login mobileadm/mobileadm stop_force 30006 & nohup /pimoti/applmgr/1159/mwa/11.5.0/bin/mwactl.sh stop_dispatcher &
Here are some things to watch out for if the server didnt start up successfully. Log file will look like <port>.<system>.<log> The APPLSYS.env may have been changed to users environment file. (Example: visus02.env)
For load balancing reasons, you may want to start up multiple servers. Remember to start each server on a different port. Also, remember that the Server uses port n+1 when communicating with Server Manager. So, if you start on port 2323, then port 2324 is also taken, and port 2324 will not be able to be used. A dispatcher can be used to route requests to one of the servers. In the mwa.cfg file, modify the parameter mwa.Dispatcher=hostname:port. Set the hostname to the machine on which you want the dispatcher to reside. Set the port here as well. mwactl.sh start_dispatcher to start mwactl.sh stop_dispatcher to stop Notes: If you use the Dispatcher, we do not support the ability to reconnect from a dropped session and still get back to the same screen. You must start the dispatcher from the same MWA_TOP you use to start the Telnet server.
2)
3) 4) 5)
Common Issues
Dispatcher and MWA ports getting reset after refresh or running autoconfig. In Order to avoid autoconfig resetting the ports, we need to have standard ports on context file. Parameters listed above. Some times process doesnt get cleared after the stop command issued. Wait for some time and always, please check netstat i |grep <port #>. If you see port is still listening. Use lsof i |grep <port #>. Identify the process and kill them. When all ports are cleared start the services. Post start service can done from desktop dos prompt or start -> run with telnet <host.domain name> <port #> . Repeate this for all ports including dispatcher to make sure you get login prompt.
Q. The Server doesnt start successfully? Q. The Server doesnt allow me to connect if X users have already connected? Q. There is a long response time between the server and the client? Q. The Server drops my connection to the server if I have been idle for more than a couple of minutes? Q. Setting up of a cronjob for automatic bounce of MWA Servers ( SR # 4098760.999 )
PORTS:
In R12, MWA server startup files are available under $INST_TOP/admin/scripts and MWA server configuration files in $INST_TOP/admin/install
Note : Though the directories under $MWA_TOP continue to exist, the MWA server no longer uses those files.
MWA - References
For MWA Configuration details, please see following metalink notes: . Mobile Applications Technology Stack: 163931.1 . MWA Dispatcher port number usage: 170939.1 . MWA Dispatcher Usage and Example: 198543.1 Important MWA Dispatcher Fix: MWA Dispatcher linking MWADIS executable Bug 2284935 Note.269991.1
http://webiv.us.oracle.com/cgi-bin/cr/getfile.cgi?p_attid=72450.1:285051 MWA Site http://www-apps.us.oracle.com/mwa/ AdvancedBarCodes http://logistics.us.oracle.com/collat/repository/docs/AdvancedBarCodes.pdf MWA Java Docs : http://www-apps.us.oracle.com:1100/mwa/javadocs/MWA1084/
THANK YOU