Avaya IQ Preparing for Implementation

Transcription

1 Avaya IQ Preparing for Implementation Release 4.0 November 2007

2 2007 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. 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 Avaya Support Web site: License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL). Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Named User License (NU). Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. "Named User," means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a "Named User" may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User s request (see Third-party Components" for more information). Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: 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 is not working on your company's behalf). Be aware that there can be 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 Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: Trademarks Avaya and the Avaya logo <insert specific Avaya product and service marks here> are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. <XYZ> is a trademark of <XYZ Inc.> All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: COMPAS This document is also available from the COMPAS database. The COMPAS ID for this document is Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Support Web site:

3 Contents Implementation planning prerequisites Implementation Planning Tool Installing the OS and database software Collecting setup data Start of week day Services remote access Licensing User IDs created during installation Network requirements Integrating with Active Directory Planning for CMS and OA data migration Software requirements Application host software Database host software Web browser software Communication Manager software Proactive Contact software Call Management System software Enterprise directory software Security certificates Firewall port usage Permissive use policy Setting up the operating system Operating system setup requirements Security Event logging Encryption Firewall port setup Time synchronization and time zone setup OS and database compatibility User ID requirements Installing the database client software Installing the Red Hat Linux operating system Setting up database software Partitioning the OS for the database Avaya IQ Preparing for Implementation November

4 Contents Creating database connections Configuring Oracle parameters to improve Avaya IQ performance Setting up character sets Creating tablespaces Creating database users and applying permissions Installing the database client software Creating a Net Service Name Setting up data sources Setting up Communication Manager software Setting up Proactive Contact software Using the Configuration Audit Tool Running the Configuration Audit Tool Installing the Configuration Audit Tool Uninstalling the Configuration Audit Tool Test descriptions Information required to run database tests Test result files Running an installation audit Verifying application host configurations Running a database audit Running a DBA audit Running individual tests Running tests using an input file Appendix A: Customer information worksheets Database host worksheets Basic database host information Data store information Tablespace information Application host worksheet Firewall port conflicts worksheet Communication Manager worksheet Proactive Contact worksheet Active Directory worksheet for LDAP integration Appendix B: Sample database scripts How to download sample database scripts Sample database scripts for creating tablespaces Avaya IQ Preparing for Implementation November 2007

5 Contents Sample scripts for creating users and tablespace associations Appendix C: Communication Manager link administration Administering a link between Communication Manager and Avaya IQ Administering data collection options Administering UCID options UCID feature options UCID trunk options Administering the Avaya IQ and Communication Manager release options. 83 Verifying the Communication Manager release Verifying the customer options Setting the reporting adjunct release Administering a C-LAN connection Adding node names and IP addresses Listing IP interfaces Adding a C-LAN IP interface Adding an ethernet data module Adding the processor interface channels Adding IP routing Enabling the processor interface channel Saving translations Administering a processor ethernet port connection Verifying the Processor Ethernet port Displaying the processor ethernet port Adding node names and IP addresses Adding the processor interface channels Enabling the processor interface channel Saving translations Glossary Index Avaya IQ Preparing for Implementation November

6 Contents 6 Avaya IQ Preparing for Implementation November 2007

7 Implementation planning prerequisites Before Avaya or a BusinessPartner installs Avaya IQ, you must take into account several topics around the planning and preparation of your application hosts and database host. The information in this section outlines the procedures you must do when preparing systems for the installation of Avaya IQ. This section includes the following topics: Implementation Planning Tool on page 7 Installing the OS and database software on page 8 Collecting setup data on page 8 Start of week day on page 9 Services remote access on page 9 Licensing on page 10 User IDs created during installation on page 11 Network requirements on page 11 Integrating with Active Directory on page 12 Planning for CMS and OA data migration on page 12 Implementation Planning Tool Your deployment has been determined from inputs to the Implementation Planning Tool. Your deployment will be one of the following configurations: A Dual Host deployment, with Avaya IQ software on one host and your database on a separate host A Multiple Host deployment, with Avaya IQ spread across three or more hosts and your database on a separate host When following the instructions in this document, use the outputs from the Implementation Planning Tool to help set up your applications hosts and database host. Avaya IQ Preparing for Implementation November

8 Implementation planning prerequisites Installing the OS and database software The Implementation Planning Tool will detail the number of hosts for which you must purchase, set up, and install OS and database software. Information to help you set up the OS and database software are found in the following sections: Software requirements on page 13 Setting up the operating system on page 21 Setting up database software on page 35 After you install the OS on the application hosts, you must test the installation to verify that it is ready to install Avaya IQ software. These tests are described in Using the Configuration Audit Tool on page 45. Collecting setup data As you set up your application hosts and database host, you must collect certain data about your setup. This setup data is used by the Avaya or BusinessPartner provisioning teams when they install Avaya IQ. This setup data includes the following items: IP addresses Host names Database user names Database tablespaces Data source connection information for Communication Manager and Proactive Contact systems Avaya recommends that you collect all of this information in a word-processing file or copy the information onto the worksheets found in Appendix A: Customer information worksheets on page Avaya IQ Preparing for Implementation November 2007

9 Start of week day Start of week day For reporting purposes, most contact centers designate one day of the week as their start of week day. As part of your preparation for installation, you must decide which day of week will be your start of week day. This day is used during installation of Avaya IQ and cannot be changed once it has been administered. Once you have decided on your start of week day, communicate that information to the Avaya or BusinessPartner provisioning team using the Application host worksheet on page 65. Services remote access Avaya support personnel require remote access to provide technical support. From a planning perspective, you must work with Avaya to provide remote access to your equipment during software installation and configuration, initial administration, and when the system is turned over to you for normal operation. Remote access is also required if Avaya will be providing ongoing services support. Contact your Avaya representative for more information about remote access offers. Briefly, the following two methods are used by Avaya services to support your deployment: Secure Access and Control (SAC): SAC is the primary method of remote access. If SAC has been installed at your site and configured for use with Avaya IQ, SAC will be used for initial implementation and ongoing maintenance. With SAC, Avaya will not need any assistance from you to start a remote access session. Web conferencing: Web conferencing is a secondary method for remote access. This method requires you to designate a dedicated personal computer so that Avaya support can access your Avaya IQ system during implementation and for ongoing maintenance. This method consists of the following steps: 1. Avaya provisioning sets up a Web conferencing session and invites the customer to the session. 2. The customer logs in to the session from the dedicated personal computer at the customer site or within the customer network. 3. The customer gives control of the dedicated personal computer to the Avaya personnel. 4. The Avaya personnel access the host machines from the personal computer to install, configure, and administer the hosts. 5. When the implementation is complete, the Avaya personnel returns control of the personal computer to the customer. 6. The Web conferencing session is ended. Avaya IQ Preparing for Implementation November

10 Implementation planning prerequisites The customer must have the following tools available on the personal computer used for the session: An approved X-Windows package such as Cygwin or Hummingbird Exceed. Xlite-Pro is not an approved package. An approved secure shell command line terminal package, such as PuTTY. Licensing Licensing ensures that customers are permitted to use only the product functionality for which they have paid and are licensed. License files for Avaya IQ are generated and acquired using the Avaya Remote Feature Activation (RFA) process and installed using the Web License Manager (WebLM) tool. To acquire a license file, an Avaya or BusinessPartner representative uses the RFA feature. The Avaya employee or BusinessPartner must be certified to use the RFA feature. For information about RFA training, certification, and how to acquire a license file, see the following documents: Remote Feature Activation (RFA) User Guide Getting Started with Remote Feature Activation (RFA) These documents can be found on the Avaya support site: To acquire a license file, you must provide the following information to the Avaya or BusinessPartner representative: Host ID (MAC address or HWaddr) of the host where the All Functions or Administration host function will be installed. This host is where WebLM will be installed, and it is the only host where the license file is installed. You can use the Linux ifconfig command to display the Host ID. SAP order number BusinessPartner Tier I and Tier II information, if applicable Customer contact information 10 Avaya IQ Preparing for Implementation November 2007

11 User IDs created during installation User IDs created during installation When Avaya IQ is installed on your application hosts, several user IDs are created to support the installation and operation of the product. If your security guidelines require that you limit or control certain user IDs, work with the Avaya or BusinessPartner provisioning team to remove or recreate any user IDs that violate your security requirements. The following user IDs are created during installation: avaya - used for initial administration craft - used by Avaya services personnel cust - default customer user ID genericldap1 - used for internal LDAP processing genericldap2 - used for internal LDAP processing rasaccess - used for remote access tools used by Avaya services personnel replicator1 - used to identify the CUS system being used sroot - used by Avaya services personnel; sroot is identified as ID=0 tomcat5 - used for the web server processing tsc - used by Avaya services personnel installation user ID - used to assign ownership during Avaya IQ installation Network requirements Application hosts at a single site must be connected to a high speed shared TCP/IP local area network (LAN). The LAN must have a minimum bandwidth of 100 Mbps, operating at full duplex. Application hosts at different sites must be connected to a wide area network (WAN). The WAN must have a minimum bandwidth of 2 Mbps. Requirements for this bandwidth and any other issues around latency are provided as a report from the Implementation Planning Tool. Dynamic Host Configuration Protocol (DHCP) is not supported for application hosts. Hosts must be configured with static IP addresses or use reserved IP addresses from a DHCP server. You must make sure that the hosts files (for example, /etc/hosts) are set up properly or performance and functionality will suffer. Avaya IQ Preparing for Implementation November

12 Implementation planning prerequisites Domain name system (DNS) can be used to define IP addresses in the customer network. If DNS is not used, you must use specific IP addresses on every host or set up the /etc/hosts files correctly on every host. If the host files are not set up properly, you may suffer performance penalties or other problems when the OS attempts to do DNS lookups. You must configure your deployment connectivity consistent with your underlying network infrastructure, which may or may not include DNS servers. Network Address Translation is supported by Avaya IQ. This is a feature that allows you to use an internally known IP address and name between hosts, but a different IP address and name are used when exposed externally. Details of your network configuration must be communicated to the Avaya or BusinessPartner provisioning team. Different sites can be separated by firewalls. For more information about ports for firewall configuration, see Firewall port usage on page 17. Integrating with Active Directory Avaya IQ can work with Windows Active Directory on Windows 2000 Server and Windows 2003 Server to integrate enterprise users with the Avaya IQ user management system. This allows you to add administrative and reporting users automatically from your enterprise directory without using separate authentication from Avaya IQ. Avaya provisioning can integrate your enterprise directory during initial implementation, or you can do the integration using the procedures provided in Integrating with Active Directory on page 95. Coordinate this work with the provisioning teams. Use the Active Directory worksheet for LDAP integration on page 73 to collect Active Directory options. Planning for CMS and OA data migration It is best to migrate CMS data as soon as you are confident Avaya IQ is collecting data and operating normally to maximize the amount of data you can migrate. CMS stores a maximum of 62 days of historical interval data, and only CMS interval data can be migrated. This limitation does not exist for OA data. For more information about data migration, see Data Migration to Avaya IQ. 12 Avaya IQ Preparing for Implementation November 2007

13 Software requirements This section lists the software required for client and host computers in a software-only deployment. This section includes the following topics: Application host software on page 13 Database host software on page 14 Web browser software on page 14 Communication Manager software on page 15 Proactive Contact software on page 15 Call Management System software on page 16 Enterprise directory software on page 16 Security certificates on page 17 Firewall port usage on page 17 Permissive use policy on page 20 Important:! Important: The Customer Release Notes and the Implementation Report for Customer from the Implementation Planning Tool documents the latest software versions and takes precedence over any software versions shown in this section. Application host software This section lists the software that you must purchase, install, and configure on the computers being used as application hosts before any Avaya IQ software is installed. Red Hat Enterprise Linux 4, Update 4 or 5, ES or AS, for x86 platforms, 32-bit Important:! Important: Avaya IQ only works with registered versions of Red Hat Linux. Avaya IQ does not work with any Red Hat Linux clone software. Oracle 10G R2 ( plus patch ) client software The Oracle software on the application host is used to make connections to the database host. Install only the client software. See Installing the database client software on page 41 for more information. Avaya IQ Preparing for Implementation November

14 Software requirements Network Time Protocol (NTP) time synchronization client software All application hosts must be synchronized using the same NTP source as all Communication Manager systems and Proactive Contact systems in the deployment. See Setting up the operating system on page 21 for more details about installing and setting up the Red Hat Linux OS. Database host software The host computer where the database software installed must comply with the following requirements: Oracle 10G R2 ( plus patch ) software, Standard Edition or Enterprise Edition, depending on database size The database host can use any OS that supports the required version of the database software. Users and tablespaces must be administered on the database. See Setting up database software on page 35 for more information. Network Time Protocol (NTP) time synchronization client software is recommended, but not required, on the database host. Web browser software Access to the reporting and administration interfaces is done using a Web browser on a user PC. This section describes the minimum software requirements related to the Web browser. Microsoft Windows XP SP2 Microsoft Internet Explorer 6.0 SP2 Microsoft Internet Explorer 7.0 Firefox 2.0 The screen resolution to display the user interface properly is 1024x768 with 16-bit color. Acrobat Reader 4.0 or later for viewing reports saved as Portable Document Format (PDF) Microsoft Excel 2000 or later for viewing reports saved as an Excel spreadsheet Printer installed with proper drivers for printing reports 14 Avaya IQ Preparing for Implementation November 2007

15 Communication Manager software When using a pop-up blocker in a browser, you must configure the pop-up blocker to allow pop-ups from the application host sites. Use the tools setting of your browser to control the allowed sites. When adding an allowed site to the list, use the IP address of the root host machine. Note: Note: You cannot use the browser provided with the Linux OS for administration and reporting. You must access administration and reporting from a browser on a PC. Communication Manager software This section describes requirements for Communication Manager systems used as sources to Avaya IQ. Communication Manager software releases: , plus service pack 13743, service pack 14445, plus Combo Patch or later, plus service pack Note: Note: Avaya IQ does not support using the G3 CSI (Prologix) hardware platform as a source. Expert Agent Selection (EAS) must be enabled Network Time Protocol (NTP) time synchronization client software All application hosts must be synchronized using the same NTP source as all Communication Manager systems in the deployment. Dedicated processor ethernet or CLAN connection for the Avaya IQ link Proper administration of contact center data collection features; see Appendix C: Communication Manager link administration on page 81. Proactive Contact software This section describes requirements for Proactive Contact systems. Proactive Contact SP1 PG230 hard dialer (Avaya IQ does not support the Proactive Contact soft dialer) Patches PC3_739, PC3_740, PC3_747, PC3_766, PC3_792, DST_2007_PC3_824, and PC3_881 must be installed Avaya IQ Preparing for Implementation November

16 Software requirements Already configured to work with a Communication Manager system The Proactive Contact system must be administered with blended inbound and outbound agents No support for standalone systems, outbound-only agents, call blending, or overflow blending Multiple Proactive Contact dialers can be deployed in an administrative group called a pod. The dialers are grouped only for administration purposes and otherwise function independently. Avaya IQ does not directly represent the pod configuration, although Avaya IQ can connect to the individual dialers in the pod. Network Time Protocol (NTP) time synchronization software All application hosts must be synchronized using the same NTP source as all Proactive Contact systems in the deployment. Call Management System software In many deployments, you will continue to use your existing Call Management System (CMS) with Avaya IQ. The following CMS versions are required when used with Avaya IQ: CMS R13.1, versions R13.1da.g and R13.1auxda.g CMS R14, all versions Enterprise directory software Avaya IQ can work with Windows Active Directory on Windows 2000 Server and Windows 2003 Server to integrate enterprise users with the Avaya IQ user management system. This allows you to add administrative and reporting users automatically from your enterprise directory without using separate authentication from Avaya IQ. Avaya provisioning can integrate your enterprise directory during initial implementation, or you can do the integration yourself using the procedures provided in Integrating with Active Directory on page 95 in Avaya IQ Administration. 16 Avaya IQ Preparing for Implementation November 2007

17 Security certificates Security certificates When users access reporting or administration with Avaya IQ, the system uses secure HTTP connections. Users will receive a security warning dialog. They must either accept the dialog every time they access the system or they can permanently install the certificate. To avoid this condition for your users, you can obtain trusted certificates that you can install on the Avaya IQ application hosts. If you obtain these certificates before Avaya or a BusinessPartner installs your system, you can request that they install the certificates for you. The number of certificates you need to obtain depends on your configuration: One certificate for an All Functions host One certificate for an Administration host One certificate for every Reporting host Firewall port usage This section lists all default firewall ports required by Avaya IQ. Give this list of ports to your system administrator to determine if any of the ports being used are not available in your network. In some cases, the default port numbers may conflict with your network. This may be caused by conflicts with other applications you are running, firewall rules, corporate network standards, or other reasons. Document any conflicts in Firewall port conflicts worksheet on page 67. The following definitions describe the headings used in the table. Source Initiator: The device or application initiating a data flow. Source Port: The default port(s) used by the source device or application. Destination Receiver: The device or application receiving a data flow from a source. Destination Port: The default port(s) used at the machine or application responding to an initiator. Source Destination Initiator Ports Receiver Port SSH Client Dynamic, intranet SSH Server (each host) 22 Reporting User Interface Dynamic, intranet SMTP Server (each Reporting host) 25 Avaya IQ Preparing for Implementation November

18 Software requirements Source Destination Initiator Ports Receiver Port Web Browser Dynamic, intranet Apache 80 Linux network time protocol daemon, ntpd (each host) 123 Linux network time protocol daemon, ntpd (each host) 123 User Service (Admin or All Functions host) Dynamic slapd (Admin or All Functions host) 389 Linux network time protocol daemon, ntpd (each host) 631 Linux network time protocol daemon, ntpd (each host) 631 User Service (Admin or All Functions host) Dynamic slapd (Admin or All Functions host) 636 Oracle 1031 DSS DSS 1099 Database clients (Admin, All Functions, or Reporting hosts) Dynamic, intranet Oracle SQL*Net (database host) 1521 Event Manager (Data Processing host) System Mgmt Tomcat (Admin or All Functions host) 5001 CM Adaptor (Data Processing host) Dynamic, intranet Communication Manager 5002 Local managed entities (each host) Child watchd (each host) Dynamic, local host (loopback) Dynamic, local host (loopback) Child watchd (each host) 7010 Parent watchd (each host) 7011 License management client (each host) Dynamic, intranet License management server (WebLM) (Admin or All Functions host) 8080, 8443 License management admin - Web browser Dynamic, intranet License management server (WebLM) (Admin or All Functions host) 8080, 8443 Reporting host Dynamic, intranet Tomcat (Reporting host) 9300 Reporting host Dynamic, intranet Tomcat (Reporting host) 9334 Reporting Application entities (Reporting host) Dynamic Reporting Application Log Server (Reporting host) 9362 Web Browser or command line Dynamic, intranet Tomcat (Reporting host) Avaya IQ Preparing for Implementation November 2007

19 Firewall port usage Source Destination Initiator Ports Receiver Port All peer Service Locators and clients (each host) Service Locator (each host) Web services access to Data Export Web Browser Reporting User Interface PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) Proactive Contact Proactive Contact Proactive Contact Tomcat Service Dynamic Tomcat (Admin or All Functions host) OAM User Web Browser Dynamic, intranet Tomcat (Admin or All Functions host) OAM User Web Browser Dynamic, Intranet Tomcat (Admin or All Functions host) JBoss Jboss Instances Event Mgmt Forwarder (Data Processing host) Network Log Server (Admin or All Functions host) Log client (each host) Historical Fact Recorder (Admin or All Functions host) Alarm Server (Admin or All Functions host) Host Log Server (each host) Host Log Server (each host) Network Log Server (Admin or All Functions host) System Configuration Client, library within services that use SDAS (each host) DSS port for specific service, identified elsewhere in table (Admin or All Functions host) SDAS Lifecycle utilities (each host) Lifecycle Manager (each host) Subsystem Administration (Admin or All Functions host)) Lifecycle Manager (each host) Avaya IQ Preparing for Implementation November

20 Software requirements Source Destination Initiator Ports Receiver Port Lifecycle utilities (each host) Lifecycle Manager (each host) PCS Adapter (Data Processing host) Historical Event Processor (Data Processing host) Proactive Contact PCS Adaptor (Data Processing host) Event Management (Data Processing host) Historical Fact Recorder (Admin or All Functions host) Historical Dim Recorder (Admin or All Functions host) PCS Adaptor (Data Processing host) IRS (Admin or All Functions host) IRS (Admin or All Functions host) Many entities (each host) Dynamic, intranet ActiveMQ (each host) Many entities (each host) Dynamic, intranet ActiveMQ Permissive use policy Avaya may support specific nonstandard Avaya IQ deployments. Contact your Avaya sales representative or Avaya support for a copy of this policy. 20 Avaya IQ Preparing for Implementation November 2007

21 Setting up the operating system This section contains requirements and procedures for installing and setting up the operating system (OS) in preparation for Avaya or a BusinessPartner to install Avaya IQ. This section includes the following topics: Operating system setup requirements on page 21 Installing the Red Hat Linux operating system on page 24 Operating system setup requirements This section provides what facets of the OS must be set up to be compatible with Avaya IQ. These requirements do not go into any details on how to set the OS options. These requirements only note that certain options must be set. Some of those options will include, but are not limited to, the following items: Security on page 21 Event logging on page 22 Encryption on page 22 Firewall port setup on page 22 Time synchronization and time zone setup on page 23 OS and database compatibility on page 23 User ID requirements on page 23 Installing the database client software on page 24 Security Your OS must be installed and maintained following the recommendations of the OS manufacturer. Verify that system hardening steps and security best practices have been followed before you install any application. These recommendations include the following practices: Install the minimum OS configuration allowed that supports Avaya IQ Install firewalls to protect your internet connections. Avaya IQ Preparing for Implementation November

22 Setting up the operating system Locate your equipment in secure locations. Keep your OS updated with the latest security patches. Regularly monitor the security events logged by the OS. Configure the OS to log the following security related events: - Logins and logouts - Administrative changes - Activities of privileged logins - Account privilege changes - System configuration changes - Addition, modification, or deletion of installed packages Once Avaya IQ is installed, monitor the Avaya IQ security events via the Security and Administration Audit categories in the Log Viewer. For more information about securing your installation, see the following resources: Security configuration documents and articles at the following Web sites: Event logging Configure your OS to log security related events such as account privilege changes, logins and logouts, and system configuration changes, addition, modification, or deletion of installed packages. Regularly monitor the security events logged by the OS. Encryption A Certificate Authority (CA) is an entity that provides trusted, signed digital certificates. Though additional certificates are not required to operate Avaya IQ, you can use the administration interface to generate and install certificates or you can install certificates that you purchase from third-party vendors. Firewall port setup During installation and operation, specific TCP ports are used by Avaya IQ and must be made available. Use the information provided in Firewall port usage on page 17 to properly configure external firewalls and Linux-based IP tables. 22 Avaya IQ Preparing for Implementation November 2007

23 Operating system setup requirements Time synchronization and time zone setup All application hosts must have NTP client software installed, configured, and working properly. The NTP time synchronization service must be synchronized from the same NTP source as all hosts, Communication Manager systems, and Proactive Contact systems in the deployment. Product software cannot be installed without the presence of a functioning time synchronization service. The hosts must also have their time zone and daylight savings time rules administered properly so that information from the sources match properly and are not shown out of synchronization. OS and database compatibility All application hosts in the deployment must use the same OS version as described in Software requirements on page 13. The database host can use any OS that supports the proper version of the database software, also documented in Software requirements on page 13. For example, your application hosts must have the proper version of the Linux Red Hat OS, but your database host can use Sun Solaris as the OS for the Oracle database software. User ID requirements Adhere to the following user ID requirements: When Avaya IQ is installed, a number of Avaya services user IDs are installed at the same time. These user IDs (sroot, craft, and tsc) are required during implementation and ongoing support. These user IDs are reserved for this use and the customer should not create similar user IDs because they will conflict with the Avaya user IDs. See User IDs created during installation on page 11 for more information about user IDs created during installation. The customer must provide, as part of installation, an OS user ID that can be associated with the installed files. Most installed files will be owned by this user and will be a member of the group with the same name. This user ID will appear when you display the permissions of the files, as well as when you list the processes that are executing on the host. Many Avaya IQ processes run as this user ID. This user ID does not have login capability, so do not select a user ID that you also want to use as an active login ID. Avaya IQ Preparing for Implementation November

24 Setting up the operating system Installing the database client software You must install the Oracle database client software on the application hosts in your deployment that will be administered with the following host functions: All Functions on a Dual Host deployment Administration on a Multiple Host deployment Reporting on a Multiple Host deployment You can identify which application hosts correspond to these functions on the Implementation Report for Customer from the Implementation Planning Tool. When you install the Oracle client software on the Avaya IQ hosts, make sure that you have installed all supporting packages required for by the OS to support the Oracle client software. All software requirements for Oracle can be found in Oracle documentation. Use the instructions found in Oracle Database Client Installation Guide when installing the Oracle client database software on the application hosts. When installing the client software, you can use either of the following installation types: Administrator Runtime Installing the Red Hat Linux operating system This section contains a high-level procedure to assist you when installing the Linux OS on a host where you will be installing the Avaya IQ software. For assistance when installing the OS, use the OS installation documents. You can view the documents at the following Web site: x8664-multi-install-guide/! Important: Important: Do not use this procedure to install the OS on your database host. The options shown in this section are only for application hosts. Before you begin the installation, collect the following information: Confirm that your hardware is compatible with Red Hat Linux Version 4, Update 4 or 5. See the following Web site: Obtain IP addresses for every host where you will install the OS. 24 Avaya IQ Preparing for Implementation November 2007

25 Installing the Red Hat Linux operating system Record the size of the physical memory of each host. If you do not know this, it should be displayed immediately after power-on. Press Esc or enter the BIOS configuration if necessary. Install BIOS/CMOS updates, firmware updates, and so on as required by Red Hat. Check the physical memory using the following commands: type free cat /proc/meminfo To install the operating system: 1. Insert the boot media and reboot the system. Your BIOS settings may need to be changed to allow you to boot from the disc or USB device. After a short delay, a screen containing the boot: prompt should appear. The screen contains information on a variety of boot options. Each boot option also has one or more help screens associated with it. To access a help screen, press the appropriate function key as listed in the line at the bottom of the screen. As you boot the installation program, be aware of two issues: Once the boot: prompt appears, the installation program automatically begins if you take no action within the first minute. You can press Enter to start the installation. If you press a help screen function key, there is a slight delay while the help screen is read from the boot media. The CD Found dialog is displayed. 2. Select Skip. The Welcome dialog is displayed. 3. Select Next. The Language Selection dialog is displayed. 4. Select the language you want to use for the installation. For Avaya IQ Release 4.0, the only supported language is English. Note: Note: This is not the locale being used during run time. 5. Select Next. The Keyboard Configuration dialog is displayed. 6. Select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default. If an existing installation of the OS is found on the host, the Upgrade dialog is displayed. 7. Select New Install. Avaya IQ Preparing for Implementation November

26 Setting up the operating system 8. Select Next. The Disk Setup dialog is displayed. Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. If you are not sure how you want your system to be partitioned, read Appendix D An Introduction to Disk Partitions in the Red Hat installation document for more information. You can choose to perform automatic partitioning or manual partitioning using Disk Druid. 9. Select Manually partition with Disk Druid. 10. Select Next. You must tell the installation program where to install Red Hat Enterprise Linux. This is done by defining mount points for one or more disk partitions in which Red Hat Enterprise Linux is installed. You may also need to create or delete partitions at this time. 11. Select Next. 12. If there are any partitions on the hard drive select them and delete them. To delete a partition, highlight it in the Partitions section and select Delete. A confirmation message is displayed. 26 Avaya IQ Preparing for Implementation November 2007

27 Installing the Red Hat Linux operating system 13. Confirm the deletion when prompted. 14. To add a new partition, select New. The Add Partition dialog is displayed. When assigning the size of each partition, use the following table as a guideline. The only mount points that have a size required by Avaya IQ are marked with a footnote. Mount point Type Minimum recommend size n/a swap Use the following recommendations to calculate swap space: If RAM is 1024 MB or less, set swap size to 2 times the size of the RAM. If RAM is between 1025 MB and 2048 MB, set swap size to 1.5 times the size of the RAM. If RAM is between 2049 MB and 8192 MB, set the swap size equal to the size of the RAM. If RAM is more than 8192 MB, set swap size to 0.75 times the size of the RAM. If the swap space is larger than 2 GB, you should split the required swap space into several swap partitions of 2GB each to improve performance. / ext MB /avaya 1 ext MB /boot ext3 512 MB Avaya IQ Preparing for Implementation November

28 Setting up the operating system 15. Administer the following options: Mount point Type Minimum recommend size /home ext MB /opt 1 ext MB plus any remaining space /tmp 1 ext MB /u01 ext MB /usr ext MB /var 1 ext MB 1. Mount point name and size required for Avaya IQ. Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter /. File System Type: Using the pull-down menu, select the appropriate file system type for this partition. Allowable Drives: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is not checked, then the partition will never be created on that hard disk. By using different settings, you can have Disk Druid place partitions where you need them, or let Disk Druid decide where partitions should go. Size (MB): Enter the size (in megabytes) of the partition. A minimum 100 MB partition will be created if you do not select a larger value. Additional Size Options: Choose whether to keep this partition at a fixed size, to allow it to grow (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard drive space available. If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. Force to be a primary partition: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. 16. Select OK to create the partition. 17. Repeat Steps 14 through 16 to add all the partitions. 18. Once you have created all partitions on the disk, select Next. The Boot Loader Configuration dialog is displayed. 28 Avaya IQ Preparing for Implementation November 2007

29 Installing the Red Hat Linux operating system 19. Do not make any changes to this dialog. Select Next. The Network Configuration dialog is displayed. The installation program automatically detects any network devices (ethernet ports) you have and displays them in the Network Devices list. The only network device you should activate is eth0. Avaya IQ Preparing for Implementation November

30 Setting up the operating system 20. Select the eth0 network device and select Edit. The Edit Interface dialog is displayed. 21. Select Activate on boot and enter the IP Address and Netmask for the host. 22. Select OK. The Network Configuration dialog is displayed. 23. Set the host name manually using the host name or fully qualified host name. Enter any gateway or DNS IP addresses if required for your network. 30 Avaya IQ Preparing for Implementation November 2007

31 Installing the Red Hat Linux operating system 24. Select Next. The Firewall Configuration dialog is displayed. Important: 25. Select the following options depending on the host type: Enable firewall for all application hosts. Remote Login for all application hosts Web Server for All Functions, Administration, and Reporting hosts Enable SELinux Active for all application hosts! Important: Do not enable SMTP or FTP services on any Avaya IQ application host. 26. Select Next. The Additional Language Support dialog is displayed. 27. Select a default language and any other languages that may be used for the administration and reporting interfaces of Avaya IQ. For Avaya IQ Release 4.0, the only language you can select is English. Avaya IQ Preparing for Implementation November

32 Setting up the operating system 28. Select Next. The Time Zone Configuration dialog is displayed. 29. Select your location on the map or from the drop-down menu. 30. Select Next. The Set Root Password dialog is displayed. 31. Create and confirm the password for root. Keep track of this password as the Avaya implementation personnel will need to log in as root for a portion of the software installation. 32. Select Next. The Package Installation Defaults dialog is displayed. 33. Select Customize software packages to be installed. 34. Select Next. The Package Group Selection dialog is displayed. 32 Avaya IQ Preparing for Implementation November 2007