Modular Messaging Web Client For Modular Messaging Release 2.0 Server Installation Issue 1 February 2004
2004, Avaya Inc. All Rights Reserved, Printed in U.S.A. Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. Avaya Web Page The world wide web home page for Avaya is: http://www.avaya.com Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or working on your company s behalf). Be aware that there is a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Fraud Intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call the Technical Service Center s Toll Fraud Intervention Hotline at 1.800.643.2353. Providing Telecommunications Security Telecommunications security of voice, data, and/or video communications is the prevention of any type of intrusion to, that is, either unauthorized or malicious access to or use of, your company s telecommunications equipment by some party. Your company s telecommunications equipment includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, networked equipment ). An outside party is anyone who is not a corporate employee, agent, subcontractor, or working on your company s behalf. Whereas, a malicious party is Anyone, including someone who may be otherwise authorized, who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (time-multiplexed and/ or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of: Utilization (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll-facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company, including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs). Your Responsibility for Your Company s Telecommunications Security The final responsibility for securing both this system and its networked equipment rests with you an Avaya customer s system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to: Installation documents System administration documents Security documents and anti-virus patches Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure your: Avaya provided telecommunications systems and their interfaces Avaya provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Avaya products Avaya does not warrant that this product is immune from or will prevent unauthorized use of telecommunication services or facilities accessed through or connected to it. Avaya is not responsible for any damages or charges that result from either unauthorized uses or from incorrect installations of the security patches that are made available from time to time. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to securityalerts@avaya.com. Federal Communications Commission Statement Part 15: Class A Statement. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Industry Canada (IC) Interference Information This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of Industry Canada. Le Présent Appareil Nomérique n émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A préscrites dans le reglement sur le brouillage radioélectrique édicté par le Industrie Canada. Trademarks All trademarks identified by and are registered trademarks or trademarks of Avaya Inc. All other trademarks are the property of their respective owners. Ordering Information Call: Avaya Publications Center Voice 1 800 457-1235 International Voice +1 207 866 6701 Fax 1 800 457-1764 International Fax +1 207 626 7269 Write: GlobalWare Solutions 200 Ward Hill Avenue Haverhill, MA 01835 USA Attn: Avaya Account Management Email: totalware@gwsmail.com Obtaining Products To learn more about Avaya products and to order products, visit www.avaya.com. European Union Declaration of Conformity The CE mark affixed to the equipment means that it conforms to the referenced European Union (EU) Directives listed below: EMC Directive89/336/EEC Low-Voltage Directive73/23/EEC For more information on standards compliance, contact your local distributor. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language as well as information regarding support for this product, while under warranty, is available through the following web site: www.avaya.com/support.
Contents Introduction 1 Product architecture............................................................. 2 Prerequisites 3 Server hardware prerequisites..................................................... 3 Software prerequisites........................................................... 4 Server software............................................................. 4 Client software............................................................. 4 Voice server prerequisites........................................................ 5 Prerequisite testing............................................................. 5 Installation 7 Overview..................................................................... 7 Install server software........................................................... 7 Installation verification.......................................................... 9 Identify the message servers.................................................. 10 Configure options and settings................................................ 10 Run Install Verify Tool...................................................... 13 Add a user to Modular Messaging Web Client.................................... 15 Removing the server software.................................................... 15 Release 2.0 Issue 1 iii
Modular Messaging Web Client Server Installation Guide Release 2.0 Issue 1 iv
Introduction Introduction This document provides information about installing the Web server software from the product CD onto the PC that will act as the server for the Modular Messaging Web Client. This guide contains the following topics: Topic Introduction on page 1 Prerequisites on page 3 Installation on page 7 Description Explains the basic architecture of Avaya Modular Messaging and the Modular Messaging Web Server Explains prerequisites for the server hardware, software, and voice server that are required for installation Provides step-by-step installation procedures Release 2.0 Issue 1 1
Modular Messaging Web Client Server Installation Guide Product architecture This topic provides a brief introduction to the architecture of Modular Messaging. The Modular Messaging system consists of the following components:! Messaging Application Server (MAS). The system must include at least one MAS, but might include several, depending on system capacity. The MAS software can reside on customer-provided equipment (a PC) or on the Avaya S3400 platform with a Windows operating system.! Message Storage Server (MSS). The system must include one MSS. The MSS software resides on the Avaya S3400 platform with a LINUX operating system. Note: Some Modular Messaging systems use a message store, such as Microsoft Exchange, instead of the MSS on the Avaya 3400 platform. A Modular Messaging system must have an MSS to operate with the Modular Messaging Web Server and Web Client.! Modular Messaging Web Server. The PC acts as the server that supports the Modular Messaging Web Client access. The Modular Messaging Web Server accesses client mailboxes on the MSS through the corporate LAN. See Prerequisites on page 3 for specific software release (version) requirements. Release 2.0 Issue 1 2
Prerequisites Prerequisites This topic describes, at a high level, the prerequisites that must be met before you can install the Web server software from the Modular Messaging product CD. As the installer, you must have an administrative login account and password for the Web server. You must also have a working knowledge of Windows 2000 Server administration. Server hardware prerequisites Verify that the PC to be used for the Web server meets the following PC hardware requirements:! A 2.0 GHz Pentium III or equivalent processor.! 512 MB RAM.! 40 GB of available space (NT file system format) on the hard drive. (Only 350 MB of space is required for the software alone, but 40 GB is required for correct operation of the software in the customer environment.)! A modem.! A CD-ROM drive.! A network interface card (NIC), which is required in the server to connect to the corporate LAN. Before you install the Modular Messaging Web Client server software, the hardware must be installed on the network at the customer site. 3 Issue 1 Release 2.0
Prerequisites Software prerequisites Server software Verify that the following software is installed on the Web server:! Windows 2000 Server, including:! Windows 2000 Server Service Pack 4! IIS 5.0! Internet Explorer 6 with Service Pack 1! Virus protection software with the latest updates (recommended) Caution: Do not use Windows 2000 Advanced Server. Caution: Do not use Terminal Services during this installation. Caution: Avaya strongly recommends that you save an image of the Web server with its network settings and the required Windows operating system, service packs, and other software as described above, before you begin installing Modular Messaging Web Client server software. Then, if it becomes necessary, you can quickly restore the server to its initial configuration. Client software Software requirements for the client PC include the following:! Windows 2000 or Windows XP! One of the following browsers:! Internet Explorer Release 5.5 with Service Pack 2! Internet Explorer Release 6.0! Netscape Navigator Release 7.0 or 7.1 Release 2.0 Issue 1 4
Prerequisites Voice server prerequisites The Modular Messaging system, Release 2.0, must be completely installed and working correctly before installation of the Modular Messaging Web Client server can begin. The following table describes minimum system requirements. Message server type Avaya Modular Messaging system 2.0 Message Storage Server (MSS) 2.0 Minimum release Prerequisite testing Verify that the Message Storage Server (MSS) and the Web Client server are networked correctly. From the server, ping the MSS server: 1. In Windows 2000, click Start and then Run. 2. Type cmd, and press Enter. 3. In the cmd.exe window, type ping <IP address>. Use the IP address or server name of the MSS. Press Enter. 4. If the ping to the MSS fails, see the network administrator. 5 Issue 1 Release 2.0
Prerequisites Release 2.0 Issue 1 6
Installation Installation Overview Install software in the following sequence: 1. Microsoft Posting Acceptor, if it is not already installed 2. Modular Messaging Web Client server software Install server software To begin the installation, either:! Insert the product CD. The first installation dialog box is automatically displayed.! Browse to the Autorun.exe file on the CD and click it. The rest of the installation process is described in the following table, where each row relates to a particular dialog box you see as the installation progresses. The information in each row describes how to complete the fields in that dialog box and then proceed to the next dialog box. Release 2.0 Issue 1 7
Installation Use the following table to complete the Install dialog boxes for copying software from the CD to the server: Dialog box Required actions Notes Read Me file Click Continue. Avaya Modular Messaging Web Client Installation (Welcome dialog box) Software License Agreement Click Next. Click I Agree. Modular Messaging Web Client Installation (Tell Me About dialog box) Modular Messaging Web Client Installation (Select Destination Directory dialog box) Modular Messaging Web Client Installation (Backup Replaced Files? dialog box) Select Program Manager Group After you review the topics of interest, click Next, which is in the body of the dialog box. Then select Continue With Install. Click Next, which is at the bottom of the dialog box. You may accept the default destination folder on the C: drive, or navigate to a different location. Click Next. Select Yes, and then click Next. Leave the default as is, and then click Next. You can view information about the documentation, or you can continue the installation. The directory names cannot have spaces. Avaya recommends that you complete a system backup before beginning the Modular Messaging Web Client installation. Modular Messaging Web Client Installation (Ready to Install dialog box) Click Next. 8 Issue 1 Release 2.0
Installation Dialog box Required actions Notes Installing Modular Messaging Web Client Installation (Installation Completed! screen) Wait for the next dialog box to be displayed. Caution: If you see any messages asking whether you want to overwrite newer files, never overwrite newer files. Click Finish. Click OK to restart the server. After the restart completes, log in again to the server. The system will register several Web Client files. Wait for file registration to complete. Installation verification When you installed Modular Messaging Web Client, all the components needed to run, configure, and monitor the use of Modular Messaging Web Client were installed, including:! Modular Messaging Web Client! Modular Messaging Web Client Administration and Maintenance tools! Modular Messaging Web Client Tools program group Release 2.0 Issue 1 9
Installation Identify the message servers Work with the system administrator to identify and configure message servers: 1. In Microsoft Internet Explorer, enter the following URL: http://<server name>/webmsg/admin (for example, http://uccweb.rnd.avaya.com/webmsg/admin). The Administration and Maintenance logon page is displayed. 2. In the Log On box, type admin. Type the default password, admin1. 3. Click Log On. The Administration and Maintenance page is displayed. 4. Select Message Servers from the Administration list. A blank table, Administration: Message Servers, is displayed. 5. In the MM Message Server Name (or IP Address): box, enter the message server name or IP address. The system verifies connectivity between the Web server and the specified message server. 6. Click Add. 7. Click Submit to add the message server to the server list. 8. Repeat the process for each message server to be configured. Configure options and settings You can work with the system administrator to configure the following parameters on the Options and Settings page now, or you can proceed directly to the section Run Install Verify Tool on page 13 and configure the parameters later. 10 Issue 1 Release 2.0
Installation Options and settings Web Server Timeout Choose Corporate Logo The following table shows default options and settings. Further information about these parameters follows the table. Default Web Server Timeout 20 minutes Avaya logo Edit the Web Link Control Voice Player When Web Client users do not actively use Web Client for the number of minutes configured here, their sessions are dropped and they are logged off. In the Web Server Timeout box, enter the number of minutes to wait before timing out. Choose Corporate Logo Downloaded by user. Enabled Message of the Day IMAP4 Server Disabled (check box not selected) Backup and Restore buttons The user s Web Client logon page can display either the Avaya logo or a customized logo. To specify the corporate logo: 1. Check the appropriate button for the corporate logo you wish to use, either Avaya or Display a custom logo. 2. Click Submit Changes. 3. If you selected Display a custom logo, navigate to the Modular Messaging Web Client directory: <drive>:\program Files\Avaya\webmsg\images\ Release 2.0 Issue 1 11
Installation Note: If you selected a different program directory during installation, then navigate to the images folder within that directory to locate the CustomLogo.gif file. Replace the existing CustomLogo.gif file with a new CustomLogo.gif file that contains the graphics the customer wants to be displayed. For best appearance on the Web page, Avaya recommends that the new logo be approximately the same size (205 pixels long x 58 pixels high) as the logo being replaced. Edit the Web Link Control This feature is optional, and it can be used to provide end users a link to any important Web location that the customer designates. The icon to access this Web location is displayed on each user s Inbox page for Modular Messaging Web Client. When users select this icon, the browser opens the configured Web location. To administer the Web Link Control feature: 1. Type the URL of the Web location in the Assign URL Link box. 2. Type a text label for the URL in the Assign Web Link Label box. 3. Check the appropriate button for the Web Link icon you wish to you use. You can choose to display the standard Avaya icon, a custom icon that you designate, or no icon. 4. Click Submit Changes. 5. If you selected Display a custom button, navigate to the Modular Messaging Web Client directory: <drive>:\program Files\Avaya\webmsg\images\ Note: If you selected a different program directory during installation, then navigate to the images folder within that directory to locate the CustomWebLink.gif file. Replace the existing CustomWebLink.gif file with a new CustomWebLink.gif file that contains the icon the customer wants to be displayed. For best appearance on the Web page, Avaya recommends 12 Issue 1 Release 2.0
Installation that the new icon be approximately the same size (56 pixels long x 56 pixels high) as the icon being replaced. Voice Player Enabling this feature allows users to download the Avaya Voice Player from the Web Client user interface. Message of the Day The system administrator creates this message that users see when they log in. IMAP4 Server Select this check box if the customer wants to allow users to have integrated voicemail and e-mail access as opposed to only voicemail access. Backup and Restore buttons From the Options and Setting page, you can back up and restore the information you have configured. To back up the configured information: 1. Click Backup. You are asked whether to proceed with the backup since doing so removes the information from your previous backup. 2. Click OK. To restore the configured information:! Click Restore. You are asked whether to proceed with the restore operation because restoring overwrites your current settings. Important: If a backup file does not exist and you click Restore, the information is restored to its default values. Run Install Verify Tool Use the Install Verify Tool (IVY) to verify and diagnose the Modular Messaging Web Client installation. The Verify Installation page from the Maintenance Tools page shows Release 2.0 Issue 1 13
Installation an IVY report that is similar to the IVY report generated by the application, but without as many features. The IVY application, which you can access from the Modular Messaging Web Client Tools program group, gives you more flexibility and features and a better graphical interface. You can save and print the IVY report, change the filter for viewing data, and create different baselines for comparisons. The IVY report is a plain ASCII file that you can send as an e-mail attachment. This report is useful for describing problems to technical support personnel. When you open IVY, the tool starts automatically, and the Install Verify Window is displayed. The tool checks each Modular Messaging Web Client file against the database for file name, location, size, date and version, and Windows registry entry. The status bar displays each file name as it is being checked. When the verification is complete, the window displays a row of tabs. If the fields of a selected tab are empty, no errors or warnings are present. The default is to create a report that shows only errors and warnings. You can change the information that is shown by clicking the stoplights on the toolbar. Red shows only errors, yellow is the default that shows both errors and warnings, and green shows all files. Errors appear against a red background, and warnings against a yellow background. The information contained in the IVY database is displayed on the first line for each file, and the information found on the Web server is displayed on the second line. Only information that differs from one database to another is displayed. A blank column on the second line indicates that the information matches. When you review a report, you might notice some differences that do not represent an error or warning that needs to be addressed. For example, a newer version of a system file present on the server is usually not replaced with an older version, but the difference is displayed in the IVY report. You can exclude these differences from future IVY reports when you set the baseline. You can create a baseline of the IVY report either from the Tools menu or from the magnifying glass icon on the toolbar. A baseline file contains information about the IVY database and system differences at the time the baseline was created. 14 Issue 1 Release 2.0
Installation To establish a baseline report: 1. In Windows 2000, click Start > Programs > Avaya Modular Messaging > Web Client Tools > Install Verify Test - Ivy. The system checks the program files. This may take a few minutes. 2. Click each tab in the Ivy window, and verify that no errors (shown in red) exist. 3. From the Tools menu, click Make Baseline. 4. Specify saving the file to the default folder, and click Save. 5. In the Select Output dialog box, select the All Entries radio button and click OK. 6. When you are ready to close IVY, click File > Exit. The baseline file is not used automatically when IVY creates future reports. To view the differences between an IVY report and the baseline, from the Tools menu, click Compare to Baseline. A new report is displayed that shows only the errors and warnings that are not in the baseline file. Add a user to Modular Messaging Web Client Add a user to Avaya Modular Messaging as described in the administration guide. Log into Modular Messaging as that user and verify that the Web Client works correctly. Removing the server software To uninstall Modular Messaging Web Client server software: 1. In Windows 2000, click Start > Settings > Control Panel > Add/Remove Programs. 2. Select Avaya Modular Messaging Web Client. 3. Click Change/Remove. Release 2.0 Issue 1 15
Installation 4. Proceed with the Modular Messaging Web Client software removal as you would to remove any program through Windows. 16 Issue 1 Release 2.0