Configuring the AppServer
Improved MRP performance requires a single AppServer with multiple threads, which is used to execute the programs that process planning data when you run MRP. Use the following instructions to configure that AppServer.
All Installations
Use this procedure to configure an AppServer instance for all QAD installations. If you have an Oracle installation, additional configuration tasks are required.
In the Progress example shown below, the name for the AppServer instance is mt-mrppro. However, you can use any name, as long as all references to the name are consistent.
Add an entry for the required AppServer instance to the ubroker.properties file in the DLC\properties directory. You can copy the following text into the file. Be sure to change the parameters to match your environment.
Note: Parameter changes are described after the sample text.
Note: Separate examples are provided for Progress and Oracle environments.
Progress Example
[UBroker.AS.mt-mrppro]
appserviceNameList=mt-mrppro
brokerLogFile=$WRKDIR/mt-mrppro.broker.log
controllingNameServer=NS1
initialSrvrInstance=12
maxSrvrInstance=20
minSrvrInstance=12
portNumber=50000
PROPATH=/dr05/mfgpro/pro/eb2:/dr05/mfgpro/pro/eb2/us/bbi:
${PROPATH}${WRKDIR}
srvrConnectProc=pxldgbl.p
srvrLogFile=$WRKDIR/mt-mrppro.server.log
srvrMaxPort=50202
srvrMinPort=50002
srvrStartupParam=-c 30 -znotrim -d mdy -yy 1920 -Bt 350 -D 100 -mmax 3000
-nb 200 -s 63 -noshvarfix -pf /dr05/mfgpro/eb2/Production.pf
uuid=fdf73fbf039907:6ce891fc:ec7f530e95:-7eed
Oracle Example
[Environment.mt-mrpora]
ORACLE_BASE=/dr02/apps/oracle/
ORACLE_HOME=/dr02/apps/oracle/8.1.7
ORACLE_SID=mrp
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
NLS_NUMERIC_CHARACTERS=.,
[UBroker.AS.mt-mrpora]
appserviceNameList=mt-mrpora
brokerLogFile=$WRKDIR/mt-mrpora.broker.log
controllingNameServer=NS1
environment=mt-mrpora
initialSrvrInstance=12
maxSrvrInstance=20
portNumber=54000
PROPATH=.:/dr05/mfgpro/eb2:/dr05/mfgpro/eb2/us/bbi:${PROPATH}:${WRKDIR}
srvrConnectProc=pxldgbl.p
srvrLogFile=$WRKDIR/mt-mrpora.server.log
srvrMaxPort=54202
srvrMinPort=54002
srvrStartupParam=-Dsrv svub,1 -c 30 -znotrim -d mdy -yy 1920 -Bt 350 -D 100
-mmax 3000 -nb 200 -s 63 -noshvarfix -pf /dr05/mfgpro/eb2/Production.pf
uuid=59fdf73fbf039907:6302bfc1:ec513ed2fd:-6fd7
The parameters of interest are described below. Parameters not listed should generally not be changed from the values given in the example.
Important: The first line of the entry specifies the name of the AppServer instance. If this is changed from the name in the example, be sure to change all other occurrences of this name in the other parameters.
• BrokerLogFile and srvrLogFile are the two log files for the AppServer instance. They should be appropriately named and located in a convenient directory of your choice.
• PROPATH is the Progress path used to locate code to run. This should reference the r-code directory where the QAD software was installed.
• uuid is a global unique identifier value associated with this AppServer instance. The Progress tool genuuid should be used to generate a value. This tool can be run from the command line and is found in the Progress DLC\bin directory.
Note: If you use the Progress Explorer tool to create the AppServer definition, the uuid will be generated automatically.
• appServiceNameList should match the AppServer instance name that you have chosen, which is listed in the first line of the properties entry.
• portNumber is the port number for the AppServer broker for this instance. Its value can be an arbitrary integer, as long as it does not conflict with any port assignments of other applications running on this machine, including other AppServer instances.
• srvrMinPort and srvrMaxPort specify a range of port values to use for the 4GL engines spawned by the AppServer instance. The range should be large enough to accommodate the maximum number of 4GL engines that can be spawned—specified by the maxSrvrInstance parameter—and should not have any conflicts with ports used by other applications, including other AppServer instances.
• srvrStartupParam specifies the Progress startup parameters to be used by each 4GL engine that is spawned. The specific DB, host, and service names should match the values that correspond to your
QAD Enterprise Applications database installation.
Other values should remain as specified in the examples.
• controllingNameServer specifies the Progress Name Server instance with which the AppServer broker will register its name. The Progress default is NS1.
Since the AppServer broker mt_mrppro is used internally by the system, you must use AppServer Service Maintenance (36.19.1) to define an application server connection master record.
Additional Oracle Tasks
If you have an Oracle installation, you must perform two additional tasks:
1 Add an Environment entry like the example below to the ubroker.properties file:
[Environment.MRP_ORACLE]
ORACLE_HOME=/Oracle/OracleAppServer
ORACLE_SID=YourSystemIdentifier
ORACLE_BASE=/Oracle
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
NLS_NUMERIC_CHARACTERS=.,
Where:
• /Oracle/OracleAppServer is the directory where the Progress AppServer for Oracle has been installed; for example, /dr01/app/oracle/product/8.1.7
• YourSystemIdentifier is the Oracle system ID (SID) for your system
• /Oracle is the base Oracle directory, which contains version-specific subdirectories; for example, /dr01/app/oracle
See the Progress AppServer documentation.
Note: The NLS variables shown are for American English. Be sure to use appropriate values for your language environment.