LOCATION :
SIGNIFICANCE :
IMPORTANT POINTS :
FILE :
#########################################################################################################
###################################################################
# MWA Configuration File Template
###################################################################
#
# ###############################################################
#
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink document
# 165195.1 for assistance.
#
# ###############################################################
#
##################################################################
# This template allows the Rapid Install process to make an appropriate
# instance of the mwa.cfg file dependant upon environment variables at the
# install site.
# These are the variables that rapid install should fill in to
# instantiate an mwa.cfg file:
# 1) mwa.dbcFolder
# 2) mwa.dbcFile
# 3) mwa.logdir
#
# Replace the variable [MWA Server Machine] with the machine
# where the Applications Middle tier is installed and used for
# running mobile apps.
##################################################################
# $Header: mwa.cfg 115.121.11510.2 2005/08/16 05:58:40 ajohnson ship $
################## Database Configuration #######################
# Directory where the DBC Files are located. Typically
# they are located under $FND_TOP/secure
mwa.DbcFolder=/eb_rao1_q/applmgr/qatappl/fnd/11.5.0/secure/
# List of ',' separated DBC File names. The DBC files should
# be listed without their extension. For eg.
# mwa.DbcFile = ap505dbs_dom1151, ap100dbs_tst115
mwa.DbcFile=qat
# Number of DB Connections created in the pool
# at server initialization
mwa.InitialPoolSize=3
################## Logging ######################################
# Log directory. Should be pointing to the standard
# application log directory
mwa.logdir= /eb_rao1_q/applmgr/qatcomn/admin/log/qata_tneda06n
# System Log file name.
mwa.SystemLog=system.log
# LogLevel: Different log levels can be set for obtaining
# more debug information.
# Possible values include: fatal, error, warning, debug, trace
mwa.LogLevel=error
# Enable log rotation of files based on size (Yes/No)
mwa.EnableLogRotation=Yes
# If log rotation is enabled, then rotation occurs
# when log file exceeds MaxLogFileSize
mwa.MaxLogFileSize=10000000
################## MSCA Server ####################################
# MSCA Server Port Number, The port number on which
# MSSA Server is started. To start multiple MSCA Servers
# specify a ',' separated list of port numbers.
mwa.TelnetPortNumber=2413,2513
# MSCA Server allows a client that was disconnected to reconnect
# within the time mentioned below in minutes.
mwa.DropConnectionTimeout=5
# MSCA Server disconnects a client after the client is idle
# for mwa.StaleSessionTimeout minutes.
mwa.StaleSessionTimeout=60
# Dispatcher: Used for loadbalancing MSCA Servers
# Specify the port number and machine for running the dispatcher
# For eg. mwa.Dispatcher = ap100sun:2300
mwa.Dispatcher=tneda06n.adr.corp.com:2313
mwa.DispatcherWorkerThreadCount=35
mwa.DispatcherClientsPerWorker=10
# Specify whether available() bug exists in the JVM used.
# Symptom of the bug is when server seems 'hanging' and
# user can only continue after pressing a key.
# Allowed Values: TRUE or FALSE
mwa.JVMAvailableBug=FALSE
# Specify whether user would like to retain old LOV behavior,
# i.e. LOV will be activated by ENTER or not.
# Allowed Values: TRUE or FALSE
mwa.ActivateLOVByEnter=TRUE
# Specify whether Change Responsibility and Change Organization
# menu items should appear on submenus; if TRUE, then these menu items
# will appear on the main menu and submens; if FALSE, then
# these menu items will only appear on the main menu; the default
# is FALSE
# Allowed Values: TRUE or FALSE
mwa.SubmenuChangeOrgResp=FALSE
#Use this if server should only start on a specific ip interface.
#Note format should be as shown in the example.
#mwa.IpInterface=127.0.0.1
################## Server Manager ####################################
# MSCA Servers that need to be monitored by the server manager.
# For multiple servers to be monitored specify a comma separated list
# For eg. mwa.TelnetServer = ap189sun:2323, ap121sun:2323
# If multiple servers are run on different ports of the same host, then
# the ports should be listed immediately following the host name in a
# semicolon separated list.
# For eg. mwa.TelnetServer = ap189sun:2323;2423,ap121sun:2323
mwa.TelnetServer=tneda06n.adr.corp.com:2413,2513
# mwa.WapHost is the machine on which the MSSA server is running on
# mwa.WapPort is the port number on which the MSSA server is listening
# mwa.WapURI is the MSSA Server's uri (such as /mobile/start)
# Example:
# if your MSSA startup URL is http://ap100sun.oracle.com/mobile/mobile
# the value for the following three lines should be
# mwa.WapHost = ap100sun.oracle.com
# mwa.WapPort = 8080
# mwa.WapURI = /mobile/mobile
mwa.WapHost = tneda06n.adr.corp.com
mwa.WapPort = 8013
mwa.WapURI = /mobile/start