Message Care installation procedures
Purpose
This section contains information on how to install the Message Care 4.5 software. Before installing the messaging software, ensure that you have met the hardware and software prerequisites (see Prerequisites).
You must have Microsoft SQL Server 7.0 with Service Pack 1 installed before you can install the messaging software.
Contents
This section contains the following information:
Required installation information
The following table lists the information that you are required to know before you install the Message Care software.
Item Default Value Value to use in the install Message Care Installation Directory�this is the directory that contains the executable files and web pages. C:\Program Files\Avaya\MessageCare Message Care Log File Directory�this is the directory that contains all of the Message Care and Maintenance Monitor log files. C:\Program Files\Avaya\MessageCare\logs SQL database user name and password�this user name and password will be used in setting up the ODBC System DSNs and the SQL database access security. None Customer supplied ICM directory�this is the directory where the ICM software was installed. C:\Program Files\Avaya\icm Distinct License Key Extension Number�this value is supplied with the messaging software and documentation. None Distinct License Key Extension Key�this value is supplied with the messaging software and documentation. None Performance recommendations
Recommendations for the messaging software are listed below:
Virtual memory� the virtual memory setting on your Message Care server should be set to physical memory plus 12MB. Therefore, the virtual memory setting would be 268 MB for 256MB of physical RAM. In addition, set the virtual memory on the same drive running the messaging software be set to 2-4 MB, with the remaining bulk of the virtual memory on a different drive.
The virtual memory does not have to be on the same disk as the database. If the server has two physical drives, place the virtual memory and the database on two different physical drives.
NT Application Performance Boost�to insure that sufficient system resources are available for the messaging software processes, set the NT Application Performance Boost to None.
To set the NT Application Performance Boost to None, do the following:
From the NT server desktop, right click on the My Computer icon, and then select the Properties item.
From the System Properties dialog box, select the Performance tab.
Adjust the Application Performance Boost to None.
SQL Memory Usage�to insure sufficient memory for SQL, set the SQL Memory Allocation to 128MB (set up SQL to use dynamic memory allocation with a maximum of 128MB). If your system has more than 256MB of RAM, then setting the SQL Memory Allocation to half of the systems memory could improve SQL performance. For example, if your system has 512 MB of RAM, then set the SQL Memory Allocation to 256MB.
To set the SQL Memory Allocation to 128MB, do the following:
Open the Microsoft SQL Enterprise Manager.
Right click on the Message Care server icon.
Select the Memory tab, and then set the maximum memory usage to 128MB.
IIS Logs�if you enable logging on the IIS server, you should not store them on a drive used by the messaging software since they can grow quite large.
To see if logging is enabled, do the following:
Open the Internet Service Manager, and then open the Message Care server.
Right click on the default Web Site, and then select the Properties item.
The Web site tab shows if logging is enabled and allows you to choose the location in which you want to store the log files.
The server must have an NTFile System (NTFS).
To see what type of file system your server is using, do the following:
Right-click the C: drive (on which Winnt is running), select Properties, and then select the General tab.
If the file system type is FAT, you can change it to NTFS by using the convert utility if your PC is an x86 (not RISC) NT system. To change to an NTFS, use the MS-DOS command window.
The ICM software must be installed on the Message Care server even if the ICM will run from a different server. This is because the messaging software utilizes ICM library files. If this is the case, the ICM service must be stopped on the Message Care server, and the Startup Type of the ICM service must be changed from Automatic to Manual.
Copyright © 2001
Avaya Inc.
All rights reserved.
Modified: March 19, 2001![]()