03/01/2020 MWA Configuration File: Configure mwa.

cfg | Oracle Apps DBA stuff

1st September 2013 MWA Configuration File: Configure mwa.cfg

MWA Dispatcher port number usage: 170939.1
MWA Dispatcher usage and example: 198543.1

[] [] Overview of the Mobile Supply Chain Application Server

The Oracle Mobile Supply Chain Applications Server is a java based mobile server that supports the Telnet Protocol. The
Telnet Server module has two sub-modules:
Telnet Protocol Handler- Functions as the communication module between the client and the rest of the Telnet.
Presentation Manager- Implements the telnet protocol that actually renders the user interface on the connected telnet
client.
The following illustration depicts how a mobile application request is handled:
Mobile Application Request Sequence

The client connects to Telnet Listener over a specified port—protocol negotiation occurs on the first communication.
The Telnet Listener gathers input and waits for an event.
When an event occurs, the presentation manager generates an event and passes it to the controller.
The controller handles this event and modifies the appropriate business objects.
The business object returns an updated session back to the controller.
The controller informs the presentation manager of the updated session.
The presentation manager examines the user session, renders the current page, and returns it to the client.

[] [] MWA Server Setup

The following paragraphs contain information on how to setup the MWA server.

[] MWA Configuration File: Configure mwa.cfg [] []

The following procedure lists the steps necessary to configure the mwa.cfg file.
1. Locate the mwa.cfg file in the $INST_TOP/admin/install directory.
2. Copy the file Mwa_template.cfg to the file mwa.cfg
3. Edit the mwa.cfg file and configure following parameters
a. Set mwa.DbcFolder=full directory of folder containing the .dbc file ending with “/”.
b. Set mwa.DbcFile=dbc file name
c. Set mwa.logdir=full directory of log file
d. Set mwa.TelnetPortNumber=default port#
e. Setmwa.DropConnectionTimeout= no. of minutes
f. Set mwa.StaleSessionTimeout= no. of minutes
g. Set mwa.LogLevel=error or trace

[] Key Mappings: Configure default_key.ini [] []

The following procedure lists the steps necessary to configure the default_key.ini file.

appsdbastuff.blogspot.com/2013/09/mwa-configuration-file-configure-mwacfg.html 1/5
03/01/2020 MWA Configuration File: Configure mwa.cfg | Oracle Apps DBA stuff

1. Locate the default_key.ini file in the $INST_TOP/admin/install directory.

2. Use the default_key.ini file if you do not need to make any changes.
3. If you need to make customizations, create a new file e.g. intermec2415_key.ini
a. Associate Server-Defined actions to Device keys:
== eg. MWA_CLEAR_FIELD=CONTROLK=Clear
b. Specify a device

[] Device IP: Configure Device IP.ini [] []

The following procedure lists the steps necessary to configure the deviceIP.ini file.
1. Locate the deviceIP.ini file in the $INST_TOP/admin/install directory.
2. Copy the deviceIP_template.ini file to the deviceIP.ini file. This file associates a device with a key mapping file.
3. Map the device name and IP address as follows:
a. Mapping by device name: Intermec 2415=intermec2415_key.ini
b. Mapping by IP address: 130.35.112.*=intermec2415.ini

[] [] Verify Environment

To ensure you installed your environment properly, verify the following information:
Verify the telnet port and the next consecutive port is not in use i.e. 2323 and 2324.
The environment was set by sourcing the APPLSYS.env file.
$INST_TOP and $MWA_TOP is set correctly.
The DbcFolder and DbcFile in the mwa.cfg file is set to the location and file name of your Oracle Application .dbc file.
The log directory exists.
The $CLASSPATH includes appsborg.zip and apps.zip.

Note: If APPS.zip is larger than 64k, apply patch 2729622. Follow the instructions in the readme file to apply the patch.
After you apply the patch successfully, update the $CLASSPATCH in replacing /apps.zip by .

[] [] Configure MWA Dispatcher

Use the following procedures to configure and manage the dispatcher to perform load balancing among multiple MWA
servers.

Setup Dispatcher parameters in mwa.cfg [] [] []

The following procedure lists the steps required to setup dispatch parameters in the mwa.cfg file.
1. Specify the port number and machine for running the dispatcher where
mwa.Dispatcher=hostname:port#

Note: The dispatcher uses three consecutive ports for internal control.
2. Specify the dispatcher worker thread count where
mwa.DispatcherWorkerThreadCount=15
3. Specify the dispatcher clients per worker where
mwa.DispatcherClientsPerWorker=10

[] [] Running MWA Server

The following paragraphs describe how to run the MWA server.

Starting the MWA Telnet Server [] [] []

To start the MWA telnet server complete the following procedure (at a UNIX/LINUX prompt):
1. Source the APPLSYS.env

appsdbastuff.blogspot.com/2013/09/mwa-configuration-file-configure-mwacfg.html 2/5
03/01/2020 MWA Configuration File: Configure mwa.cfg | Oracle Apps DBA stuff

2. Enter the following text:

cd $INST_TOP/admin/scripts

3. Enter the following text:

mwactl.sh start [port number]

Shutting Down the MWA Telnet Server [] [] []

To shutdown the MWA telnet server complete the following procedure (at a UNIX/LINUX prompt):
1. Enter the following text:

cd $INST_TOP/admin/scripts

2. Enter the following text where xxx is application user id with system administrator responsibility or a valid database
user and yyy is the application user password.

mwactl.sh-login xxx/yyy stop [port number]

Additional Information
You can use the following information while running the MWA server.
For NT servers, use mwactl.cmd script to start/stop MWA servers
Use appropriate OS commands to ensure the MWA server continues running after the current connection closes (usually
nohup, and/or &)
You can use the following command to find currently running MWA servers: ps-ef|grep mwa

[] [] Starting/Shutting down the MWA Servers and Dispatcher

You can use the MWA Dispatcher to balance user load across many MWA Servers. Users connect to a single dispatcher port.
The Dispatcher then re-directs each connection to one of the available servers associated with that dispatcher.

Starting the MWA Servers and Dispatcher [] [] [] [] [] [] []

To start two MWA servers and the MWA Dispatcher complete the following procedure (at a UNIX/LINUX prompt):
1. Source the APPLYSYS.env.
2. Enter the following text:

cd $INST_TOP/admin/scripts

3. Enter the following text to start the server:

mwactl.sh start 2310 (or any port number)

4. Enter the following text to start the server:

mwactl.sh start 2320 (or any other port number).

5. Enter the following text to start the dispatcher:

mwactl.sh start_dispatcher

appsdbastuff.blogspot.com/2013/09/mwa-configuration-file-configure-mwacfg.html 3/5
03/01/2020 MWA Configuration File: Configure mwa.cfg | Oracle Apps DBA stuff

You connect to the Dispatcher port 2300. The dispatcher distributes mobile users between the two MWA servers. You
can select control-X to view the MWA server port#, host name and other connection information.

Shutting Down the MWA Servers and Dispatcher [] [] [] []

To shutdown the MWA servers and the MWA Dispatcher complete the following procedure (at a UNIX/LINUX prompt):
Source the APPLYSYS.env.
1. Enter the following text:

cd $INST_TOP/admin/scripts

2. Enter the following text where xxx is application user id with system administrator responsibility or a valid database
user, yyy is the application user password, and 2310 is the port number of the first server.

mwactl.sh-login xxx/yyy stop 2310

3. Enter the following text where xxx is application user id with system administrator responsibility, yyy is the application
user password, and 2320 is the port number of the second server.
4. mwactl.sh-login xxx/yyy stop 2320
5. Enter the following text:

mwactl.sh stop_dispatcher.

Note: The MWA server terminates only when all mobile users are disconnected. New users cannot sign-on when the
server is stopped. If you want to terminate the server while users are connected, you can use the stop_force command
in place of the stop command to stop the server immediately.

[] [] Alternating MWA Servers and Dispatcher

You can establish a rotation of multiple MWA servers managed in conjunction with the dispatcher to avoid impacting daily
operations. For Example: You can use one Dispatcher to manage to sets of MWA Servers (MWA Servers Set A and MWA
Servers Set B respectively). You can set the rotation as follows:
Servers
MWA Servers Week 1 Week 2 Week 3

MWA Servers Set A 12:00am start 12:05 am stop 12:00am start

MWA Servers Set B 12:05 am stop 12:00am start 12:05 am stop

You can adjust the times and numbers of servers to match you shift schedule and volume of users.

[] [] Accessing MWA Server

You can use a telnet client to access the Oracle Applications Mobile User Interface. Connect to the machine where the MWA
server is running on the port number where the server has been started or on the port number of the dispatcher.
For example, if the MWA server was started on mwa.oracle.com on port 2323, then you use a telnet client access to the
Oracle Applications UI to connect to mwa.oracle.com on port 2323. To access the UI from a mobile device, you configure
the telnet client on the device to access the IP of the machine on the appropriate port. To access the UI from a desktop
computer, you can use a compatible telnet client to connect to the appropriate machine and port number.
Note: The default telnet client that ships with Windows 2000 and later is not compatible with character mode User
interfaces using the telnet protocol, which includes the Oracle Applications Mobile UI. Refer to the Microsoft Knowledge Base
Article #253918 (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q253918) for more information. As per the
instructions on this support note, to use a GUI based telnet client on a Windows 2000 machine, it is necessary to copy the
telnet client that shipped with Windows NT or obtain a third party telnet client software.
[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

appsdbastuff.blogspot.com/2013/09/mwa-configuration-file-configure-mwacfg.html 4/5
03/01/2020 MWA Configuration File: Configure mwa.cfg | Oracle Apps DBA stuff

After you complete the change recommended in the knowledge base article, you can access the mobile UI. Launch the
following executable from a command prompt where server.mwa.com represents the machine, and 2323 represents the
port number: telent32.exe ap100.mwa.com 2323.

Posted 1st September 2013 by Unknown

1 View comments

rajeev October 5, 2019 at 2:41 PM

Oracle Apps R12 and Fusion Cloud Self Paced Training Videos by Industry Experts. Please Check
https://www.oracleappstechnical.com
Reply

Enter your comment...

Comment as: jeffersonarruda

Sign out

Publish Preview Notify me

appsdbastuff.blogspot.com/2013/09/mwa-configuration-file-configure-mwacfg.html 5/5