Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Installation Guide
Release 1.0.8.2
May 2002
Contents
Contents .......................................................................................................................................2
Preface ..........................................................................................................................................3
Intended Audience ....................................................................................................................3
Getting Started............................................................................................................................4
2.1 Mobile Application Server for Industrial Requirements............................................................4
2.2 Using AutoConfig to configure Mobile Application Server for Industrial ...................................5
2.3 Mobile Application Server for Industrial Installation.................................................................5
2.4 Confirming Successful Installation of Mobile Application Server for Industrial Applications ........6
Server Administration...............................................................................................................7
3.1 mwactl script .......................................................................................................................7
3.2 Starting up server ................................................................................................................8
3.3 Shutting down server ...........................................................................................................9
3.4 Running AutoConfig.............................................................................................................9
3.5 mwa.cfg ............................................................................................................................ 10
Troubleshooting.......................................................................................................................17
Dispatcher..................................................................................................................................19
A.1 Dispatcher overview .......................................................................................................... 19
A.2 Starting up dispatcher ........................................................................................................ 20
A.3 Shutting down dispatcher................................................................................................... 20
Server Manager.........................................................................................................................22
B.1 Server Manager Overview ................................................................................................. 22
B.2 Start / Stop Server ............................................................................................................. 23
B.3 Monitor Server .................................................................................................................. 24
B.4 Configure Server............................................................................................................... 27
1
Preface
The Mobile Application Server is available in two forms:
Although the Mobile Application Server for Self-Service and the Mobile
Application Server for Industrial are shipped in the same category, they are two
independent products that only share the same configuration file. Thus, a
customer who intends to run the Industrial Applications only needs to read and
perform the setup in this document. Similarly, a customer who intends to run the
Self-Service Applications does not need to read and perform the setup in this
document.
This manual covers the installation and implementation of the Mobile Application
Server for Industrial Applications. The server will be referred to as the Mobile
Industrial Applications Server throughout this document.
Intended Audience
This manual is intended for people responsible for installing the Mobile Industrial
Applications Server, such as:
Database Administrators
System Administrators
Technical Specialists
2
Getting Started
The Mobile Industrial Application Server is basically a server process that
provides the run-time engine for Industrial Applications such as Warehouse
Management System, Inventory, Work-In-Process, and Quality Assurance. These
Industrial Applications are modules that sit on top of the framework that is
provided by the Mobile Application Industrial Server.
The Mobile Industrial Application Server functions as a middle-tier between the
hand-held devices that function as clients and the database server. The following
diagram shows an overview of the Mobile Industrial Application Server.
Client
Client
WMS
INV
WIP
Mobile Industrial
Application Server
Database
Server
Client
This chapter explains how to install the Mobile Application Server for Industrial
and contains the following sections:
Oracle JDBC
o Refer to the README-Config-JDBC.html document in the patch
for more information.
Note that the Mobile Industrial Application Server does not need Apache server to
run.
To install the Mobile Application Server for Industrial, complete the following 6
steps.
1. Change directory to <APPL_TOP>
2. Run the APPLSYS.env script, located in <APPL_TOP>, to set all the
necessary environment variables. After this step, $MWA_TOP environment
variable has been set to the right directory.
3. Now we are ready to start the server. Go to $MWA_TOP/bin directory and
issue the following command:
3
Server Administration
This chapter contains the following sections:
mwactl script
Starting up server
mwa.cfg
java_config
mwatop
Usage
This parameter is required only if you are shutting
down the server. Use the username and password that has
System Administration responsibility in Oracle
Application.
Used to set java options. For example, you can set the
initial and maximum Java heap size by speficifying "ms" and "-mx" values. The java_config parameter is
optional. If you don't specify it, -java_config
defaults to "-ms64m -mx128m".
Used to specify the location of your Mobile
Applications root directory. For example, if Mobile
Applications is in /d3/mwa, you would specify an mwatop
of "/d3/mwa". This parameter is optional. If you don't
set the parameter here, however, mwactl will look for
[port]
3.5 mwa.cfg
The mwa.cfg file, located in $MWA_TOP/secure, is used to store configuration
information for the server. Note that this file is used by both the Mobile Industrial
Application Server and Mobile Self-Service Application Server. Please also note
that this file is created by autoconfig during installation, and users should not be
editing this file manually.
You can also use a different mwa.cfg file than the one located in $MWA_TOP.
To do this, use the -java_config Dmwa.cfg=<location of the cfg file>. The
-java_config is one of the options in mwactl script. For example, if you like to use
a different mwa.cfg that is located in /tmp directory, you should start the server as
follows: mwactl.sh java_config -Dmwa.cfg=/tmp/mwa.cfg. This still requires
the location of mwatop, but will use the cfg file provided in the java_config
option and not the one located in $MWA_TOP/secure.
If you need to make modifications to this file, you should be editing the
Applications Context File (<TWO_TASK>.xml) and running the AutoConfig
utility to propage these changes as explained in the Running AutoConfig
section. You must do so before starting the server. If you make modifications to
this file while the server is running, you must restart the server in order for the
changes to take effect.
Below is the description of each property in the Applications Context File
(<TWO_TASK>.xml) that is relevant only to Mobile Industrial Application
Server. All properties that are not between the <oa_mwa_server> and
</oa_mwa_server> tags in this file belong to other products and thus, can be
ignored for configuring Mobile Industrial Application Server.
Applications Context File Properties
Tag
Description
mwaPortNo
mwaDropConnectionTimeout
10
mwaStaleSessionTimeout
MwaLogLevel
MwaLogRotate
MwaLogFileSize
mwaDispatcherPort
mwaDispatcherThreadCount
mwaDispatcherClientsPerWorker
MwaJVMb
Some values in the mwa.cfg configuration file are defined with respect to Applications
standards, and should not be changed. Below is the description of these predefined
parameters:
mwa.logdir
mwa.SystemLog
11
mwa.DbcFolder
mwa.DbcFile
mwa.InitialPoolSize
mwa.Dispatcher
mwa.TelnetServer
2325.system.log
Default value: system.log
The directory that contains the dbc files
that are specified in mwa.DbcFile property.
Default value: <FND_TOP>/secure
This property (a string of comma-separated
values) lists all the dbc files that server
should use. Server will find the dbc files
under directory that is specified by
mwa.DbcFolder property.
Default value: <Database Host Name>_<Database
SID>
This specifies the number of database
connections created in the pool at server
initialization.
Default value: 3
This property tells the server where to find
a dispatcher (hostname:port). At any time,
server will always try to connect to the
specified hostname and port to register
itself. This will make the dispatcher truly
plug-and-play.
Default value: <Hostname on which AutoConfig
is started>:<mwaDispatcherPort>
This lists all the instances of Mobile
Application Server for Industrial and the
ports. It is only used by Server Manager tool
to find out all the instances of server that
it should manage. For this reason, the list
should be maintained up-to-date. Otherwise,
Server Manager will not work properly.
Default value: <Hostname on which AutoConfig
is started>:< mwaPortNo>
12
4
Device Configuration
This chapter describes how to perform device configuration to existing devices or
add and register new devices. It has the following sections:
deviceIP.ini
default_key.ini
4.1 deviceIP.ini
The deviceIP.ini file, located in $MWA_TOP/secure, is used to administer all the
different devices that will be used as clients. Server can see your device only if
you register your device through changing the file deviceIP.ini.
Note that, deviceIP.ini file is also managed by AutoConfig, and special care must
be taken to modify this file. Changes should be made only between Begin
customizations and End customizations blocks, otherwise all changes made
might be lost, or successive AutoConfig runs might invalidate this file:
//# ********************
//#
//# Begin customizations
//#
//# ********************
Changes must be made in this area
//# ********************
//#
//# End customizations
//#
//# ********************
13
If you need to make modifications to this file, you must do so before starting the
server. If you make modifications to this file while the server is running, you must
restart the server in order for the changes to take effect.
The file has two sections. The first section marked [devices] maps a device to a
device configuration file. The second section marked [map] maps IP address to
device configuration file. When a server receives a client connection, it tries to
use the client's IP address and the information in the second section to find a
device configuration file for that connecting device. When there is no match, a list
of devices that are stored in the first section of the file will be presented to user
for selection. Below is a description of the two sections of deviceIP.ini.
deviceIP.ini Sections
Description
Section
[device] section
[map] section
4.2 default_key.ini
The default_key.ini, located under $MWA_TOP/secure, is provided as a default
device configuration. You should have one device configuration file for each
different device that you like to customize. Otherwise, the default device
configuration will be used. If you need to make modifications to this file, you
must do so before starting the server. If you make modifications to this file while
the server is running, you must restart the server in order for the changes to take
effect.
There are two parts of configuration in the file. The first part lists key binding that
is used for the device. The second part of the file specifies the characteristics of
the device, e.g. width, height, etc. After a client has connected to a server
successfully, pressing help key (F1) will display the configuration of the device
that is used for that specific client. Below is a description of each property in the
device configuration file.
14
Property
There are two things that need to be done in order to add and register a new
device to the server:
1.
You need to create a device configuration file. You can use default_key.ini as a
template by copying it and modifying it as necessary. Some of the things that are
usually modified in the new device configuration file are as follows:
2.
16
5
Troubleshooting
Q: The server doesnt start successfully.
A: Make sure you have the right environment. Things that should be checked
specifically are:
Q: I dont see any page coming up after I connect to the server. After I press
any key, then the Login Page comes up.
A: Try setting mwa.JVMAvailableBug property in mwa.cfg to TRUE and
restart the server. Note that the value is case-sensitive.
Q: I am having navigation problems. Most of the time, I am stuck and need
to press Ctrl-C to move on.
A: Try setting mwa.JVMAvailableBug property in mwa.cfg to TRUE and
restart the server. Note that the value is case-sensitive.
Q: The server doesnt allow me to connect if X users have already connected.
A: If you are running the server in Unix-flavored system, try increasing the file
descriptor limit.
Q: There is a long response time between the server and the client.
A: Try load balancing (starting multiple Telnet servers and the dispatcher).
17
Q: The server drops my connection to the server if I have been idle for more
than a couple of minutes.
A: Try increasing the "mwa.StaleSessionTimeout" value in the mwa.cfg file.
18
Appendix A
Dispatcher
A.1 Dispatcher overview
If users are facing slow response times, it might be necessary to distribute the load
between servers. This is generally recommended if you have 20 or more clients
connecting to the server.
You can distribute the load merely by starting up a dispatcher and multiple mobile
servers. Multiple servers can be started in a single machine with different ports or
in multiple machines. Just follow the startup instructions to do this. Please
remember when you start up the Mobile Application Server for Industrial with
port n, port n+1 is also taken at that time. So, for example, you will be able to
start two servers on ports 2323 and 2325, but not on 2323 and 2324. Each server
you start effectively starts a different process and uses a different JVM. It is in
this way that loadbalancing is achieved.
In using dispatcher to perform load balancing, clients should be connecting to
dispatcher instead of the individual server. Also note that the dispatcher and the
servers can all be located in different machines. The following is a figure that
shows N clients connecting to a single dispatcher and client requests are
distributed to M Mobile Application Server.
19
<APPL_TOP> should be nfs shared between all the different machines where the
dispatcher and the servers are running. This makes sure that server configuration
file (mwa.cfg) is identical and shared throughout different instances of the server
and the dispatcher.
Make sure there is no collision of log file in the different instances of the server.
One way to avoid this issue is to use different port for different instances or make
the server log into a space that is local at the local machine (not nfs shared).
Typically the system shell has a very conservative limit on the maximum number
of sockets/files that can be open by all its children. Therefore if you run several
Telnet Servers and/or the Dispatcher on the same machine, you should start them
from different shells. In addition before you start up a Telnet Server or
Dispatcher, you should adjust ulimit for that shell to a reasonably high value (for
example "ulimit -n 1024" should be good enough). This holds even in cases when
you just run a single Telnet Server with no dispatcher, since it is VERY easy to
reach the limit of 64 file descriptors---the typical default value. Note also that
some shells might not permit you to set ulimit properly. You might need to switch
to "ksh" before setting the ulimit and running the Telnet Server or Dispatcher (see
example below).
21
Server Manager
This chapter contains the following sections:
Start/Stop Server
Monitor Server
Login to the Self-Service Web applications with a user name that has MWA
Server Manager responsibility.
In the home page after you login, choose "MWA Server Manager" from the "Self
Service" Section.
In the following page, you will be presented with six server manager links,
including three for the Mobile Supply Chain Server, "Start/Stop Server", "Monitor
Server", and "Configure".
22
23
There are two regions in the "Start/Stop" server page. The "Server Dispatcher"
region displays the status of the server dispatcher. If there is a server dispatcher
running, two buttons will be provided to control the server dispatcher. Pressing
"Shutdown" will shutdown the server dispatcher, while pressing "Bounce" will
shutdown and restart the dispatcher.
The "Start/Stop Server" region displays the status of Mobile Application Server
for Industrial and provides controls to stop them. The region contains a pop list of
machine names, a table that summarizes the server status on the selected machine,
and three control buttons.
To view Mobile Application Server for Industrial status on other machines,
choose the machine name from the "Server Host" list and then press the "Change
Server Host" button.
To stop an Mobile Application Server for Industrial on a certain port, simply click
the "Stop Server" link in the corresponding row of the "Server Status" table.
To stop all Mobile Application Server for Industrial on current selected machine,
click the "Stop All Servers" button.
The server manager may ask you to enter a user name and password to perform
the action. Please enter a user/password that have the "Administrator" privilege in
Oracle Applications. This user/password pair may not be the same as the one you
used to login to the server manager. The user name and password will only be
asked once during a session.
Currently, the server manager does not support starting the server dispatcher or
Mobile Application Server for Industrial. Please refer to section Starting up
server (section 3.2) and section Starting up dispatcher (section A.2) of the
document for how to manually start them.
The "Server & Session Information" displays status information about individual
servers and user sessions if there is any. Controls for terminate a user session and
for messaging are also provided in this region. Below is a screen shot of the
region:
The "Server Host" list contains a list of server machines. To view information for
a particular server machine, simply choose the machine name from the list and
click the "Change Server Host" button.
25
The "Server Status" table summarizes the server status on all ports of the selected
machine. The information includes, server uptime, current sessions, total sessions,
total memory, used memory, etc.
The "User Sessions" table shows information about user sessions on the selected
machine and provides controls for messaging and terminating session.
To terminate a user session, click the icon in the "Terminate" column of the
corresponding row in the table. This will lead you to a confirmation page. Press
the "Terminate" button near the page bottom to actually terminate the session,
press "Cancel" to return to the "Monitor" page.
There are three messaging methods provided around the user sessions table:
To post a message to a particular user, click the "Post A Message" link in the
corresponding row of the user sessions table.
To broadcast a message to all user sessions on the selected server machine,
click the "Broadcast to Host" button.
To broadcast a message to all user sessions on all server machines, click the
"Broadcast to All Hosts" button.
In the message page (shown below), enter a short message in the edit box and
click "Submit" to post/broadcast the message. When the Mobile Application
Server for Industrial receives the message from the server manager, it would put
the message in the event queue. When the handling event is called, the message
would be popped on the client screen.
26
The "Database" region allows users to view the contents of dbc files. This region
is made read only because users are not supposed to change dbc files. Select dbc
file name from the "DBC file" list and click "View" will view the content of the
selected dbc file.
After making the changes, press the "Save" button to save the change to your
mwa.cfg file. Please make sure that the file and the directory that contains the file
are writable to the apache user. Press "Cancel" to discard the changes.
28
Creation Date:
Change Number:
Last Saved On:
9/16/2002 4:02 PM
11
9/26/2002 12:38 PM