NEC Medical Center System Operations Manual

							NDA-30026   Revision 6Page 29
Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION
Step 7: Java 
Services 
Primary 
ConfigurationThe APM configuration parameters are automatically set during the Java MCMP 
Server installation. Some of the user-defined parameters may need to be modified to 
reflect the installation site’s configuration.
User-Defined Parameters
Parameter Entry
OAI Application N
CRT Application N
Communication Queue N
Application Name JmcmpConnServer
Executable Filename /oai/app/mcs/bin/jmcmpConnServ
Group JMCMP
Response Mode Ignore
Initialization Batch Y
Termination Mode T
Standard Output /dev/null
Number of Restarts 5
User Defined # Default Value Description
12030
(Do not change this 
value unless this port 
number conflicts with 
another listening port.)JMCMP Server Port -
This is the TCP I/P port number 
on which JMCMP Server is 
listening.
2/oai/app/mcs/bin/
jmcmp
(Do not change unless 
this application has 
been renamed.)JMCMP Application Path -
This defines the absolute path of 
the JMCMP process spawned by 
the JMCMP Server when a 
connection is made. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 30NDA-30026   Revision 6
Step 8: 
Mcs_Dbclean 
Control 
OptionsFrom the APM Administration Menu, select Control Options. When the Control 
Options screen displays, select the Applications command. Then, select Mcs
_Dbclean 
and set up the schedule for its execution, as illustrated in the following example:
Initialize:
Minute (0-59): 1
Hour of Day (0-23): 0
Day of Month (1-31): *
Month of Year (1-12): *
Day of Week (0-6): *
When you have entered these choices, select Quit and then type Y to save the data. The 
Applications menu redisplays.
Mcs
_Dbclean automatically ends processing when it has cleaned up the database.
Step 9: 
Mcs_Recluster 
Control 
OptionsFrom the APM Administration Menu, select Control Options. When the Control 
Options screen displays, select the Applications command. Then, select 
Mcs
_Recluster and set up the schedule for its execution, as the sample shows below:
Initialize:
Minute (0-59): 5
Hour of Day (0-23): 0
Day of Month (1-31): *
Month of Year (1-12): *
Day of Week (0-6): *
When you have entered these choices, select Quit and then type Y to save the data. The 
Applications menu redisplays.
Mcs
_Recluster automatically ends processing when it has reclustered the database.
Step 10: 
Mcs_Host_ 
Statistics 
Control 
OptionsFrom the APM Administration Menu, select Control Options. When the Control 
Options screen displays, select the Applications command. Then, select 
Mcs
_Host_Statistics and set up the schedule for its execution, as illustrated in the 
following example:
Initialize:
Minute (0-59): 10
Hour of Day (0-23): 0
Day of Month (1-31): *
Month of Year (1-12): *
Day of Week (0-6): *
When you have entered these choices, select Quit and then type Y to save the data. The 
Applications menu redisplays.
Mcs
_Host_Statistics automatically ends processing when it has generated the 
statistics. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 31NDA-30026   Revision 6
This completes the configuration of MCS in the APM. Now go to the Database 
Requirements on page 32 to prepare its database support. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 32NDA-30026   Revision 6
Database Requirements
MCS requires two APM databases that were installed with default values when the 
software was loaded from the release media. Only one (mcscfg) can be modified. The 
other database (mcsfile) should not be changed at all without first consulting technical 
support. You can change the mcscfg database through the Database Administration 
option on the APM System Administration Menu.
The contents of the mcscfg database are described below. Using instructions provided 
in the APM Operations Manual, enter the APM System Administration Menu and 
change mcscfg database entries as required through the Database Administration 
option. Any messages displayed during these steps are described in the Process and 
Error Messages chapter of the APM Operations Manual.
Note:Remember to process and install mcscfg after any of the following field information 
has been changed through the Build Master Database option.
MCSCFG 
Database 
InformationRemember to configure each additional Server (i.e., Application Configuration.)
Server Base Name = Mcs
_Server#
The name of the Server component. The # marks the position of the actual number 
of the Server process.
Server Ratio = 8
The number of attendants that can be served by any one Server component. This is 
the default value. Given that there are 16 attendants at most, there should be at least 
two Server components configured (Mcs
_Server1 and Mcs_Server2).
Max Number of MCMP’s = 16
The maximum number of attendants this system can handle. Changing this value 
has no effect. The maximum is always 16.
Conversation Monitoring # = 7207
The extension number of the D
term used during a Supervisor Alert operation to 
silently monitor an attendant conversation. If conversation monitoring is not used, 
this field should be left blank.
Parking Number = 7000
The OAI monitored number assigned to MCS. It can be defined on the PBX MAT 
using the command AMNO. The default value should be changed to a monitored 
number defined on the PBX. This value must be assigned correctly or the MCS will 
not go on-line.
Announcement Message # = 0
The number of the announcement trunk (ANT) as configured on the PBX to which 
all parked calls are to be parked. If an ANT is not to be used, this field should be set 
to 0.
Park Call Timeout = 60 seconds
MCS checks the call parking queue periodically. Any call parked for longer than 
this period of time is recalled. 
Note:The caller could stay parked approximately 30 to 45 seconds longer than the Park 
Call Timeout since the database checks are periodic, to avoid excessive system loads. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 33NDA-30026   Revision 6
Park Abandon Timeout = 1800
The amount of time that park records remain in the MCS database after the party 
has been recalled or released. This time period is also measured in seconds and is 
checked in the same way as the Park Call Timeout.
Recall Timeout = 90
This value is used by MCS to determine if a call answered by an attendant has been 
recalled by the PBX. This value should be adjusted according to the value 
configured in the PBX for recalls. It should be roughly equal to the amount of time 
set up for recalls in the PBX plus the amount of time it takes an attendant to answer 
the recall.
MCMP Queue Maximum = 10
The maximum number of messages allowed on the MCS IPC queue at any given 
time. Do not change this value without first consulting an NEC representative.
MCMP Queue Load = 5
The maximum number of messages that can be outstanding for an attendant process 
at any given time.
MCMP Queue Key = 9009 
The IPC queue used by the MCS attendant processes.
Max Stations in Recall List = 100
The maximum number of stations that can be in the circular recall list maintained 
by the MCS. This variable directly affects IPC shared memory structures used by 
the MCS. It should not be changed while the MCS system is running. Do not change 
this value without first consulting an NEC representative.
Max Trunks in Recall List = 200
The maximum number of trunks that are stored in the circular recall list maintained 
by the MCS. This variable directly affects IPC shared memory structures used by 
the MCS. It should not be changed while the system is running. Do not change this 
value without first consulting an NEC representative.
This completes the database support in the APM. Now go to MAT Assignments on 
page 34 to make the necessary MAT assignments. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 34NDA-30026   Revision 6
MAT Assignments
This guide assumes that data settings that affect the operation of all OAI software on a 
system-wide basis have already been assigned on the NEAX Maintenance 
Administration Terminal (MAT). Such settings include system index values and 
assignment of Interface I/O Port Data in the Interface Processor (IP). For more 
information about these system data settings and the MAT commands described below, 
refer to the OAI Module Installation Manual for the NEAX2400 IMS.
AMNO – Assignment of Monitored Number
MCS uses one OAI Monitored Number for use in parking calls. Failure to assign 
this number correctly prevents the MCS from establishing communication with the 
PBX.
ASAT – Assignment of Attendant Data
Each MCS attendant console must be assigned a unique station number. For 
instance, ATT #1 may have 3100, ATT #2 may have 3101, etc. Use this command 
to assign a number to each advanced attendant console.
This completes the MAT assignments. Now go to Attendant Station Preparation on 
page 35 to configure the Attendant Stations. 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 35NDA-30026   Revision 6
Attendant Station Preparation
To Configure 
Attendant 
StationsFrom one of the configured terminals, log into the MCS by entering the login name mcs 
at the SCO UNIX login prompt and press Enter. The following screen displays from 
which you can enter the MCS Main Menu:
Figure 2-17   MCS Login Screen
Press  for the position data. The following error prompt will display at the 
bottom of the screen:
Enter Offline Maintenance Mode? (Y/N)
At the prompt, enter Y and press .
Type MCS in the Login Name field and MCS in the Password field to log in as the 
supervisor. When the MCS Main Menu displays, perform the following tasks in the 
order shown:
1. Select the System Administration option, then the Extension Maintenance op-
tion, and then the Attendant Console Extensions option. This sequence displays 
the Attendant Console Extensions data entry screen for input. Add the extension 
numbers that have been assigned to the attendant consoles through the ASAT com-
mand at the NEAX MAT.
After all of the attendant console extensions have been entered, exit to the MCS Main 
Menu. Select the Database Administration option and then the Attendant Stations 
option, displaying the Attendant Station data entry screen for input of a configuration 
for each attendant. Each record requires the attendant ID (1-16), the extension just 
configured for that attendant (via the MAT and System Administration option), and the 
name of the terminal used by that station. Note that when entering terminal names, /
dev/ preceded the name.
Medical Center System
*** NEC Proprietary ***Tue Aug 17 09:02 am
Login Name:
Password:
 to accept,  to quitPosition: 
						

							SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition
Page 36NDA-30026   Revision 6
This Page Left Blank. 
						

							NDA-30026   Revision 6Page 37
Medical Center System Operations Manual - JAVA Edition JAVA MCS CLIENT INSTALLATION
Chapter 3 JAVA MCS CLIENT INSTALLATION
Overview
This chapter provides step-by-step procedures to install and configure the JAVA 
MCS Client application. Descriptions and step-by-step instructions are found in the 
following sections of this chapter: 
The JAVA MCS Client software can be installed on the workstations used by 
JAVA MCS agents to assist them in processing calls. This element can be installed 
on any workstation that is networked and connected to the JAVA MCS Server.
Installing the JAVA MCS Client
Use the following steps to install the JAVA MCS Client software:
1. Access the NEC UNIX OAI Applications site from your web browser. The 
address for your NEC UNIX OAI Application site consists of your UAP name 
and your domain name.
For example
, if your UAP name is “myuap” and your domain name is 
“mydomain.com”, then enter “myuap.mydomain.com” to access the UNIX 
OAI Applications Page, as shown in Figure 3-1.
Figure 3-1   NEC UNIX OAI Applications Installation Page 
						

							Page 38NDA-30026   Revision 6
JAVA MCS CLIENT INSTALLATION Medical Center System Operations Manual - JAVA Edition
2. Select Download Java1.2.2 Runtime Environment from the “Getting Help” 
section to install the Java Runtime Environment on your workstation. Follow 
the prompt to install the Java Runtime Environment. Run the program from its 
current location, then select Ye s. After the Java Runtime Environment 
installation is complete, the NEC UNIX OAI Applications Installation Page 
(Figure 3-1) is again displayed.
3. Select the JAVA MCS Client from the “Install OAI Apps From Web” section 
to begin installing the JAVA MCS Client. A security warning message will 
display, click Ye s to continue. The Java Virtual Machine option dialog box 
(Figure 3-2) is displayed.
Figure 3-2   Java Virtual Machine option dialog box