Preparing for Avaya IQ Implementation

Release 5.0 November 2011

© 2010 Avaya Inc.

All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be 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. 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 End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya 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 to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support. Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( “AVAYA”). 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 originally sold by Avaya and ultimately utilized by End User. License types 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 e-mail 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 Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL). End User 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). End User 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 e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. 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, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law.

2

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

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 regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://www.avaya.com/support/Copyright/. 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support/. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks Avaya is a registered trademark of Avaya Inc. All non-Avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support Contact 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 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/ support

Preparing for Avaya IQ Implementation

November 2011

3

com November 2011 .4 Preparing for Avaya IQ Implementation Comments? infodev@avaya.

......................................................................................................................... 41 Chapter 5: Setting up database software........................................................................................... 34 Time synchronization and time zone setup requirements................................................................................................................................................................. 14 Collecting setup data....................................................... 23 Application host software........................................................................................................................................................................................................ 33 Security recommendations................................................................................................................................................................................................................................................. 14 Start of week day.................................................................................................................................................................................................................. 41 Confirming hostname setup............................................................. 33 Event logging.................................................................... 43 Setting up database software checklist.......................................................................................................... 12 Implementation Planning Tool.................................................................. 34 OS and database compatibility...... 23 Database host software....................................... 17 Network requirements.......................... 26 Proactive Contact software.................................................................................................................. 27 Firewall port usage............ 35 Installing the database client software..................... 11 Software-only customer responsibility checklist...................... 36 Specific operating system requirements used during installation....................................................................................................................................................................................................................................................................................................................... 20 Network management and alarm monitoring.........................................Contents Chapter 1: Offers and how they affect planning................................................................................ 9 Software-only offers.............................................................................................................................................................. 11 Customer responsibilities checklists...................................................................................................................................................................................................................................... 15 Licensing........................................................................................................................................................................................................................ 24 Web browser software....................... 34 Firewall port setup....................................................................................... 27 Security certificates............ 9 Turnkey offers...................................................................................................... 20 Language support........................................................................................................... 27 Enterprise directory software........................ 31 Permissive use policy................................................. 28 Administering Proactive Contact ports............................................................................................................................................................................................................................................................................................................... 34 Digital certificates...................................................................................................................................................................................................................................................................... 43 Preparing for Avaya IQ Implementation November 2011 5 .............................................................................................................. 35 User ID requirements......................................................................................................................................... 11 Turnkey customer responsibility checklist................. 25 Communication Manager software.................................................................................................................. 16 User and group IDs created during installation................................................................................................................................................................................................................................................................................................................. 15 Services remote access............................................................................................................................ 36 Language variables...................................................................... 14 OS and database software installation........ 26 Call Management System software............................................................................ 21 Chapter 3: Software requirements..................................................................................................... 19 Active Directory integration.............. 32 Chapter 4: Setting up the operating system........................................................................................................................................... 9 Chapter 2: Implementation planning prerequisites........................

.................................................. 67 Reporting host................................................................................................................................................................................................................................................................................................................................................................................................... 45 Configuring Oracle parameters to improve Avaya IQ performance............................................................................................. 93 Firewall port conflicts worksheet.............................................. 59 Downloading the Configuration Audit Tool.................................. 45 Setting up character sets.................... 96 Voice Portal worksheet......................................................................................................................................................................................... 57 Chapter 7: Using the Configuration Audit Tool.................................. 46 Creating tablespaces....................................................................................................................... 71 Information required to run database tests....... 62 Uninstalling the Configuration Audit Tool............... 63 Test descriptions......................................................................................................................................................................................................................................................................................................... 81 Third-party jars and libraries.................................................. 75 Running a supporting application audit..............................Guidelines for partitioning the OS for the database...................................................................................................................... 74 Running an installation audit........................ 87 Database host worksheets........................ 91 Application host worksheet....... 96 6 Preparing for Avaya IQ Implementation November 2011 ............................................ 53 Sizing Oracle Redo log file................................................................................................................................................................................................................. 87 Data store information...................................................................................................................... 55 Sizing Oracle TEMP tablespace........... 48 Installing the database client software........................................................................................................................................................................................ 78 Appendix A: Distributed third-party software.................................................................................................... 95 Proactive Contact worksheet.............................................................................................................................. 47 Creating database users and applying permissions...................................................................................... 92 Turnkey worksheets.............. 86 Appendix B: Customer information worksheets............................................................................................................ 52 Creating a Net Service Name.................................................................................................... 94 Communication Manager worksheet................... 60 Copying the Configuration Audit Tool package from the installation DVD............................................ 61 Installing the Configuration Audit Tool................................................................................................................................................. 77 Sample input file.................................................................................................................................................................................................................. 63 All Functions host........................................................................................... 57 Proactive Contact software setup requirements............................... 76 Running tests using an input file................................................. 63 Administration host............................................................................................................................................................... 57 Communication Manager software setup requirements................................................................................................ 83 Additional third-party software distributed for turnkey systems.............. 70 Data Processing or Data Collection host....................................... 44 Creating database connections. 73 Test result files............................................................................................................................................................. 88 Tablespace information....... 87 Basic database host information..................................................................................................................................................................... 62 Running the Configuration Audit Tool........................................................................................................... 54 Sizing Oracle Undo Tablespace.................................. 56 Chapter 6: Setting up data sources.................................................................................................................................................................................................................................................................................................................................................................................................... 61 Checking the CAT version................................................................................................................................................................................................................................................................................................................................................................................................ 76 Running an individual audit.......................................................................................................................................

.................................................................................................................................................................. 117 Saving translations (processor ethernet port)................................................................ 114 Verifying the Processor Ethernet port.......... 114 Saving translations (C-LAN)................................................................... 130 Index............................................................................................................................ 107 Setting the reporting adjunct release................................................................................... 128 Troubleshooting ETL application................................................. 112 Adding IP routing (C-LAN)................................................. 117 Appendix E: Proactive Contact link administration...............................................................................................................................................................................................................................................................................................................323....................................................................................... 112 Adding the processor interface channels (C-LAN)............................................................. 124 Adding UCID For CM SIP trunks............................................................ 119 Changing from non-encrypted to encrypted mode...................................... 114 Administering a processor ethernet port connection...... 110 Adding an ethernet data module (C-LAN)...................................................................................... 104 Administering ANI trunk options... 97 Appendix C: Sample database scripts...................................................................................................... 109 Adding node names and IP addresses (C-LAN)................................................ 104 Administering UCID feature options................................................................................................................................................. 110 Adding an IP interface (C-LAN).............................................................................. 106 Verifying the Communication Manager release........................... 103 Administering data collection options....................................... 108 Administering a C-LAN connection............................. 116 Enabling the processor interface channel (processor ethernet port)........................................... 123 Voice Portal link administration.................................................................................................................................................................................................................................................................................................... 129 Verifying records are in Avaya IQ tables.... 123 Synchronizing clock for VPMS.............. 126 Configuring new ETL application...................................................................................................................................................................................................................................... 99 Sample database scripts for creating tablespaces................................... 119 Administering the Proactive Contact link for encrypted mode............................................................................................................................................. 115 Displaying the processor ethernet port........................................................................................................................................................................................................................................ 115 Adding the processor interface channels (processor ethernet port)............................................ 109 Listing IP interfaces (C-LAN)....................................................................................................................................................................... 103 Administering UCID options...... 107 Verifying the customer options..........................................................................................Active Directory worksheet for LDAP integration.............................................. 99 Sample scripts for creating users and tablespace associations............................................................. 105 Administering Avaya IQ and Communication Manager release options. 126 Configuring automatic ETL execution........................................... 121 Appendix F: Voice Portal Link Administration......................................................................................................................................................................................................... 115 Adding node names and IP addresses (processor ethernet port)................................................ 113 Enabling the processor interface channel (C-LAN)............. 100 Appendix D: Administering a link between Communication Manager and Avaya IQ................. 124 Administering UCID for H............................................................................ 104 Administering UCID trunk options............................................................................................................. 131 Preparing for Avaya IQ Implementation November 2011 7 ................................................................................... 125 Administering ETL application source in Avaya IQ OAM.................................................................................................................................................................................... 123 Synchronizing clock for all MPPs with VPMS...................................................................................

8 Preparing for Avaya IQ Implementation November 2011 .

there are a limited number of topics that you must consider and understand before the Preparing for Avaya IQ Implementation November 2011 9 . So. You must read and understand the following prerequisites and requirements: • Implementation planning prerequisites on page 11 • Software requirements on page 23 • Setting up the operating system on page 33 • Setting up database software on page 43 • Setting up data sources on page 57 • Using the Configuration Audit Tool on page 59 • Distributed third-party software on page 81 • Customer information worksheets on page 87 • Sample database scripts on page 99 • Administering a link between Communication Manager and Avaya IQ on page 103 • Proactive Contact link administration on page 119 • Voice Portal link administration on page 123 Turnkey offers A turnkey offer requires limited customer interaction during the initial implementation phase.Chapter 1: Offers and how they affect planning You can purchase the Avaya IQ software either as a software-only or a turnkey offer. Software-only offers The information in Preparing for Implementation of Avaya IQ applies to the software-only offers.

Turnkey worksheets on page 93 .Proactive Contact worksheet on page 96 . host names.Active Directory worksheet for LDAP integration on page 97 • Administering a link between Communication Manager and Avaya IQ on page 103 • Proactive Contact link administration on page 119 • Voice Portal link administration on page 123 10 Preparing for Avaya IQ Implementation Comments? infodev@avaya. You must read and understand the following prerequisites and requirements: • Collecting setup data on page 14 (IP addresses.Communication Manager worksheet on page 95 . specifically the following worksheets: .Offers and how they affect planning system is installed.com November 2011 . and data source information) • Start of week day on page 15 • Services remote access on page 15 • User and group IDs created during installation on page 17 • Network requirements on page 19 • Integrating with Active Directory on page 20 • Network management and alarm monitoring on page 20 • Language support on page 21 • Web browser software on page 25 • Communication Manager software on page 26 • Proactive Contact software on page 26 • Call Management System software on page 27 • Enterprise directory software on page 27 • Setting up data sources on page 57 • Distributed third-party software on page 81 • Customer information worksheets on page 87.

Preparing for Avaya IQ Implementation November 2011 11 . if needed. Activity Install the correct version of the Linux operating system (OS) on all computers where you will install the Avaya IQ application software. 5. 4. collect the information about your current setup. # 1. Schedule Avaya support to readminister your Communication Manager systems to work with Avaya IQ. See 2. you have certain responsibilities that must be done before Avaya or a Business Partner will begin an installation of the Avaya IQ system. software-only or turnkey. 3. See Application host software on page 23 and Setting up the operating system on page 57Avaya IQ. See Database host software on page 24 and Setting up database software on page 57. Customer responsibilities checklists Depending on your offer. See Installing the database client software on page 36. See Setting up Communication Manager software on page 57 and Communication Manager worksheet on page 95. The information in this section outlines the procedures you must do when preparing systems for the installation of Avaya IQ. you must take into account several topics around the planning and preparation of your application hosts and database host. If your configuration includes a Communication Manager system. Install the database client software on the appropriate Avaya IQ hosts. Software-only customer responsibility checklist Use the following checklist to help plan the activities you must do when preparing for an Avaya IQ installation. Install the database server software on the database host.Chapter 2: Implementation planning prerequisites Before Avaya or a Business Partner installs Avaya IQ.

The turnkey hardware consists of one host for the Avaya IQ software and one host for the database software. you must run the Configuration Audit Tool to test your hosts to make sure you have the OS set up properly and that you can communicate between application hosts and the database host. See Start of week day on page 15. and USB mouse for each of the turnkey hosts. Power cords must be provided locally based on local electrical requirements. See Using the Configuration Audit Tool for more information. Turnkey customer responsibility checklist # 1. 10. 12. See Network management and alarm monitoring on page 20. such as 2. 6. collect the required information. collect the information about your current setup. See Setting up Proactive Contact software on page 57 and Proactive Contact worksheet on page 96. Activity Prepare your equipment room for the turnkey hardware. 12 Preparing for Avaya IQ Implementation Comments? infodev@avaya. If you are using a Network Management System (NMS).Implementation planning prerequisites # Activity Setting up Communication Manager software on page 57 and Administering a link between Communication Manager and Avaya IQ on page 103. or you can use a shared resource. If you are integrating your enterprise directory with Avaya IQ. See Firewall port usage on page 28.com November 2011 . Decide if you want the Avaya remote access software installed on your application hosts. You must either provide a dedicated monitor. collect the information about your setup. The turnkey hosts do not come with a monitor. Determine whether you have special firewall port requirements. 7. or mouse. See Active Directory worksheet for LDAP integration on page 97. 11. 8. See Services remote access on page 15. This must be configured during installation and cannot be changed after installation. If your configuration includes a Proactive Contact system. Determine the start of week day for your deployment. keyboard. USB keyboard. 9. After you have installed the OS on the application hosts and the database software on the database host.

If you are using a Network Management System (NMS). tools. See Setting up Communication Manager software on page 57 and Communication Manager worksheet on page 95. 7. direct or indirect. 3. Important: Avaya IQ turnkey customers must not use or leverage the Oracle tools or applications by any method. Collect this information on the Database host worksheets on page 87 and the Application host worksheet on page 92. collect the information about your current setup. See Data backups and database maintenance for a turnkey deployment in Administering Avaya IQ for more information. Determine the start of week day for your deployment. 8. This must be configured during installation and cannot be changed after installation. See Start of week day on page 15. Customers can only access the Oracle database by using the methods. Regular backups of your software and data are critical in case your system must be restored after a system failure. Preparing for Avaya IQ Implementation November 2011 13 . but you must provide a backup resource. 4. 5. See Network management and alarm monitoring on page 20. If your configuration includes a Proactive Contact system. Consult with Avaya provisioning for assistance with setting up the backups. such as another server or storage array where the data can be backed up. and applications provided by Avaya.Customer responsibilities checklists # Activity a KVM switch. You cannot use a PS2 keyboard or a PS2 mouse with USB adapters because the adapters do not work with the turnkey hardware. 10. The turnkey offer provides some basic scripts that will back up your data on a regular basis. if needed. See Setting up Communication Manager software on page 57 and Administering a link between Communication Manager and Avaya IQAdministering a link between Communication Manager and Avaya IQ on page 103. See Active Directory worksheet for LDAP integration on page 97. 6. collect the required information. collect the information about your current setup. Schedule Avaya support to readminister your Communication Manager systems to work with Avaya IQ. Collect the host name and IP address to be used for the turnkey deployment. If you are integrating your enterprise directory with Avaya IQ. collect the information about your setup. See Setting up Proactive Contact software on page 57 and Proactive Contact worksheet on page 96. If your configuration includes a Communication Manager system. 9.

your database on a separate host. These tests are described in Using the Configuration Audit Tool on page 59. OS and database software installation For software-only deployments. set up. you must collect certain data about your setup. with Avaya IQ spread across three or more hosts and your database on a separate host • A Multiple Host deployment.com November 2011 . the Implementation Planning Tool will detail the number of hosts for which you must purchase. This setup data is used by the Avaya or Business Partner provisioning teams when they install Avaya IQ. and install OS and database software. and one or more optional remote Data Collection hosts • A Multiple Host deployment. 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 14 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Your deployment will be one of the following configurations: • An All Functions with Remote Data Collection deployment. and one or more remote Data Collection hosts 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. your database on a separate host. After you install the OS on the application hosts. with Avaya IQ spread across three or more hosts.Implementation planning prerequisites Implementation Planning Tool Your deployment has been determined from inputs to the Implementation Planning Tool. with Avaya IQ software on one host. you must test the installation to verify that it is ready to install Avaya IQ software. Collecting setup data As you set up your application hosts and database host.

From a planning perspective. you must decide which day of week will be your start of week day. inform the provisioning team that you do not want the Access Security Gateway (ASG) software installed on the application hosts. You can also use remote access. If SAC or SAL is installed at your site and configured for use with Avaya IQ. contact your Avaya representative. most contact centers designate one day of the week as their start of week day. You may also choose not to allow Avaya to access your system after initial installation and administration. With SAC or SAL. and working with the software. As part of your preparation for installation. For more information about the remote access offers. you must work with Avaya to provide remote access to your computer when installing. • Web conferencing is the secondary method for remote access. It requires an intermediary computer running on Windows that enables the Avaya personnel to access Preparing for Avaya IQ Implementation November 2011 15 . Once you have decided on your start of week day. This day is used during installation of Avaya IQ and cannot be changed once it has been administered. Related topics: Application host worksheet on page 92 Turnkey worksheets on page 93 Services remote access Avaya personnel require remote access to provide technical support. configuring. If you do not want Avaya to access your system. Avaya services use the following remote access methods to support your deployment: • Secure Access and Control (SAC) or Secure Access Link (SAL) is the primary method of remote access. they may provide additional instructions for remote access. Avaya will not need your assistance to start a remote access session. communicate that information to the Avaya or Business Partner provisioning team using the Application host worksheet. it will be used for initial implementation and ongoing maintenance. if Avaya provides ongoing services support. administering (at an initial level).Start of week day Avaya recommends that you collect all of this information in a word-processing file or copy the information onto the worksheets found in Appendix B: Customer information worksheets. Related topics: Customer information worksheets on page 87 Start of week day For reporting purposes. If an Avaya Business Partner provides support.

16 Preparing for Avaya IQ Implementation Comments? infodev@avaya. .Implementation planning prerequisites your Avaya IQ system during implementation and maintenance. e. d.An approved secure shell command line terminal package. If the sessions disconnect in the middle of a process. Avaya recommends that the customer use one or more of the following tools depending on the process being implemented at the time: . b. The customer gives control of the dedicated computer to the Avaya personnel. You can use this program when you are running command line scripts on the Linux hosts. To make this connection method successful. configure. the Avaya personnel return the control of the personal computer to the customer. The customer logs on to the session from the dedicated computer at the customer site or in the customer network. administer. License files for Avaya IQ are generated and acquired using the Avaya Remote Feature Activation (RFA) process. remote sessions that drop a connection should be able to reconnect automatically. or manage the hosts. For software-only deployments. . PuTTY. When using these programs. Therefore. This method consists of the following procedures: a. for example. Licensing Licensing ensures that customers are permitted to use only the product functionality for which they have purchased and are licensed.com November 2011 . You can these programs when you are running a graphical interface on the Avaya IQ hosts. Avaya provisioning team sets up a Web conferencing session and invites the customer to this session. to ensure a reliable connection. the customer must control the session from an on-site secure shell session that is reliable and not likely to disconnect. When the session is complete.A remote access program such as VNC or Remote Desktop. c.An approved X-Windows package such as Cygwin or Hummingbird Exceed. The Avaya personnel access the host computers from the personal computer to install.Pro is not an approved package. You can use these programs when you are running a graphical interface on the personal computer connecting to the Avaya IQ host. Any programs that are running remotely remain uninterrupted. the installation or upgrade process can become irrevocably broken. Note: Xlite. f. The Web conferencing session ends.

To acquire a license file. This host is where WebLM will be installed. The following table describes the Linux level Avaya IQ users created during Avaya IQ installation in a software-only offer: User ID Groups Home directory Login shell craft cust rasaccess sroot susers susers remote (PPP user) root /home/craft /home/cust /home/ rasaccess /home/sroot /bin/bash /bin/bash /bin/bash /bin/bash Preparing for Avaya IQ Implementation November 2011 17 . If your security guidelines require that you control certain user and group IDs. For turnkey deployments. • SAP order number • Business Partner Tier I and Tier II information. and it is the only host where the license file is installed. The Avaya employee or Business Partner must be certified to use the RFA feature. For information about RFA training. the license file is installed automatically when running the turnkey installation program. 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 at http://support.avaya. an Avaya or Business Partner representative uses the RFA feature. work with the Avaya or the Business Partner provisioning team to remove or recreate any user or group IDs that violate your security requirements. you must provide the following information to the Avaya or Business Partner representative: • Host ID (MAC address or HWaddr) of the host where the All Functions or Administration host function will be installed. You can use the Linux ifconfig command to display the Host ID.User and group IDs created during installation the license file is installed using the Web License Manager (WebLM) tool. and how to acquire a license file. certification.com. the system creates several user and group IDs to support the installation and the operation of the product. if applicable • Customer contact information User and group IDs created during installation When you install Avaya IQ on your application hosts. To acquire a license file.

5.9 /bin/bash /bin/bash /bin/bash /bin/bash /sbin/nologin Linux level database users oracle root2 Oracle root /home/oracle /root /bin/bash /bin/bash The following table describes the Avaya IQ LDAP users creating during Avaya IQ installation for both the software-only and turnkey offers: User ID avaya sroot craft genericldap1 genericldap2 replicator1 tsc 18 Preparing for Avaya IQ Implementation Comments? infodev@avaya.9 /sbin/nologin The following table describes the Linux level Avaya IQ and database users created during Avaya IQ installation in a turnkey offer: User ID Linux level Avaya IQ users Groups Home directory Login shell craft cust rasaccess sroot tomcat5 susers susers remote (PPP user) root tomcat5.com November 2011 . <iqXXusr> opt/ coreservices/ tomcat-5. <iqXXusr> /home/craft /home/cust /home/ rasaccess /home/sroot opt/ coreservices/ tomcat-5. avcertmgmtgrp. avcertmgmtgrp.5.Implementation planning prerequisites User ID Groups Home directory Login shell tomcat5 tomcat5.

Dynamic Host Configuration Protocol (DHCP) is not supported for application hosts. This requirement applies to all application hosts and database host. you may suffer performance Preparing for Avaya IQ Implementation November 2011 19 .iqdpusr (data processing host) . If the host files are not set up properly. If DNS is not used. Avaya recommends that all application hosts at a site be on the same subnet. Hosts must be configured with static IP addresses or use reserved IP addresses from a DHCP server. /etc/hosts) are set up properly or performance and functionality will suffer. The WAN must have a minimum bandwidth of 4 Mbps.Network requirements Users such as tomcat5 and iqXXusr (Avaya IQ installation user) do not have their passwords set. as they are not configured using shells. Avaya recommends that you use autonegotiate for speed and duplex settings based on your customer network and the network port settings. In this configuration.iqdc02 (second data collection host) .iqrpt02 (second reporting host) • Avaya IQ dual-host installation — iqafuser Related topics: User ID requirements on page 35 Network requirements All Avaya IQ hosts used in the deployment at a single site must be connected to a TCP/IP local area network (LAN) from 100 Mbps to 1000 Mbps.iqdc01 (first data collection host) . but it can be on a different subnet. you must use specific IP addresses on every host or set up the /etc/hosts files correctly on every host. You must make sure that the hosts files (for example. Domain name system (DNS) can be used to define IP addresses in the customer network. Requirements for this bandwidth and any other issues around latency are provided as a report from the Implementation Planning Tool. Avaya IQ hosts connected between remote sites must use a wide area network (WAN). The one exception to this recommendation is the Data Collection host. You can assign Avaya IQ host installation user based on the following host functions: • Avaya IQ multi-host installation: . the Data Collection host can be connected via a WAN environment. Avaya recommends that you put the database host on the same subnet as the application hosts.iqadmusr (admin host) . operating at full duplex. which is often on the same subnet as the Communication Manager system from which it is collecting call events.iqrpt01 (first reporting host) .

You must configure your deployment connectivity consistent with your underlying network infrastructure. The Simple Network Management Protocol (SNMP) 20 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Network Address Translation (NAT) is supported by Avaya IQ. NAT can only work when all application hosts are on the same subnet (for example.Ok Related topics: Firewall port usage on page 28 Active Directory integration 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. Avaya provisioning can integrate your enterprise directory during initial implementation.X where X is 1-254) and the same subnet mask. see Firewall port usage. 198. Another issue is when using a dual Network Interface Card (NIC) in a NAT configuration.Implementation planning prerequisites penalties or other problems when the OS attempts to do DNS lookups. Coordinate this work with the provisioning teams. which may or may not include DNS servers. or you can do the integration using the procedures provided in Integrating with Active Directory in Administering Avaya IQ. This routing problem may cause issues when using Data Collection. Use the Active Directory worksheet for LDAP integration on page 97 to collect Active Directory options.Avaya IQ also relies heavily on the router’s routing tables for WAN connections. Network management and alarm monitoring A business can use third party Network Management System (NMS) software to monitor the condition of an Avaya IQ deployment. For more information about ports for firewall configuration. Avaya IQ requires that the primary NAT address (internal to your network site) to be on eth0 and the public address subnet (access to an outside WAN) be on eth1. If the IP address is another NAT address subnet.168. the internal processing of the Avaya IQ synchronization will not register properly when the application host is administered . but a different IP address and name are used when exposed externally. For Avaya IQ. Data Processing. This is a feature that allows you to use an internally known IP address and name between hosts. or Reporting hosts across a WAN.1. This allows you to add administrative and reporting users automatically from your enterprise directory without using separate authentication from Avaya IQ. Different sites can be separated by firewalls. This can affect both administration users and report users when attempting to access the interfaces from a remote location. Details of your network configuration must be communicated to the Avaya or Business Partner provisioning team.com November 2011 .

regardless of the browser or OS setting. Application Operations. portions of the dialogs will display based on the browser language and portions will display based on the OS setting. Because different areas of the administration interface get their language settings from different sources. This is a condition about which you must inform your administration users.The administered reporting group folders display the language based on the OS setting. and User Management folders display the language of the base language of the OS.The Reporting group folders display only in English. Instructions for setting up alarming to an NMS are described in Administering Avaya IQ. . . Language support The administration interface of Avaya IQ supports several languages. • The base language enabled for the operating system. Most of the administration interface gets its language setting from the browser language preference. Those areas of the administration interface that get its language settings from the base language of the OS include the following items under the Enterprise tab: • The Sites and Resources folders will display the language based on the browser language preference. the administration interface uses language settings from two sources: • The browser language preference setting. Preparing for Avaya IQ Implementation November 2011 21 . Roles. • Within the Resources folder. • When you expand the Resources folder. you might have users seeing multiple languages displayed on the same dialog. To support these languages. such as: .Language support feature of Avaya IQ can provide alarm information to the NMS.The All Resources. the language support depends on the folders you display.

Implementation planning prerequisites 22 Preparing for Avaya IQ Implementation Comments? infodev@avaya.com November 2011 .

bit Important: Avaya IQ only works with registered versions of Red Hat Linux. Preparing for Avaya IQ Implementation November 2011 23 . Application host software This topic lists the software that you must purchase. See Setting up the operating system for more details about installing and setting up the Red Hat Linux OS. install. • Oracle 10G R2 client software The Oracle software on the application host is used to make connections to the database host. You can find the interoperability document under the product documentation area for Avaya IQ on the Avaya support Web site: http://support.com. and configure on the computers being used as application hosts before any Avaya IQ software is installed.2.avaya. Verify all software version requirements in the interoperability document before purchasing and install any software. Install only the client software. Avaya IQ does not work with any Red Hat Linux clone software.Chapter 3: Software requirements The Avaya IQ Product Version Interoperability document lists the latest software versions required by Avaya IQ and takes precedence over any software versions listed in this section. Server or Advanced Platform. • Red Hat Enterprise Linux 5. See Installing the database client software for more information. for x86_64 . One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Communication Manager and Proactive Contact systems. • 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.

Standard Edition or Enterprise Edition. When customers use the Enterprise Edition. on the database host. Avaya IQ has the following requirement for Oracle licenses: • One Oracle Named User Plus license is required for each individual person in the organization who is authorized to login to Avaya IQ or access the Avaya IQ database. your corporate infrastructure must use a DBA to administer the Enterprise Edition. and probably includes each instance of a workforce management application.com November 2011 .com should be referenced to determine number and type of Oracle licenses required for the Avaya IQ database server. Customers may use the Enterprise Edition if they need some advanced features of Oracle not supported by the Standard Edition. If you are a Software only customer. • One Oracle Named User Plus license is required for each device accessing data from the Avaya IQ database using Data Export. • The database host can use any OS that supports the database software with future patch updates. and so on. it means that your corporate infrastructure uses the advanced features of the Enterprise Edition. depending on database size Note: Avaya IQ requires the Standard Edition of Oracle.Software requirements Database host software The host computer where the database software installed must comply with the following requirements: • Oracle 10G R2 software. but not required. Two documents to search for and review are: • Discounting Practices on Promotions for the Database Licensing document • Oracle Software Investment Guide provides the Oracle pricing and licensing guidelines. See Setting up database software on page 43 for more information. • Users and tablespaces must be administered on the database. It is the customer's responsibility to work with Oracle or the vendor they are purchasing the Oracle software and licenses from to obtain the correct quantity and recommendation of type of licenses. each Cisco ICM instance. Avaya IQ uses the following Oracle licensing options: 24 Preparing for Avaya IQ Implementation Comments? infodev@avaya. If you want to purchase Oracle licenses based on the number of processors. • Network Time Protocol (NTP) time synchronization client software is recommended. note that the Standard Edition supports a finite number of processors but the Enterprise Edition supports any number of processors. The Oracle Web site www.oracle. This includes each individual wallboard.

not the number of Report User licenses) • Database Administrators • Contact Center Analysts • Data Analysts • Contact Center Management • Wallboard application using Data Export • Workforce Management (WFM) application using Data Export Database pooling or multiplexing does not reduce the need to license each individual user. • Acrobat Reader 4.Web browser software Per User option: One Named User Plus license is required for each individual person in the organization who is authorized to login to Avaya IQ or access the Avaya IQ database. the following examples: • Contact Center Supervisors (administered in Avaya IQ.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 When using a pop-up blocker in a browser. Use the tools setting of your browser to control the Preparing for Avaya IQ Implementation November 2011 25 . Web browser software Access to the reporting and administration interfaces is done using a Web browser on a user PC. but is not limited to. One Oracle Named User Plus license is required for each device accessing data from the Avaya IQ database using Data Export. There appears to be no provision to distinguish between users in different shifts. chip type and server manufacturer. additional Oracle licensing is not required for Avaya IQ. Determination of the number of processors licenses required is determined by Oracle as it may differ based on type of processor. the number of cores. This section describes the minimum software requirements related to the Web browser. you must configure the pop-up blocker to allow pop-ups from the application host sites. so all individual users must be licensed even if they are not all accessing the database simultaneously. The individual users and devices can include. • Microsoft Internet Explorer 6.0 • Firefox 2.0 SP2 • Microsoft Internet Explorer 7.0 • The screen resolution to display the user interface properly is 1024x768 with 16-bit color. For customers that will be utilizing an existing Oracle database that is licensed with Oracle Enterprise Edition. Per Processor option: One Oracle processor license is required per processor.

or later. • 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. One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Communication Manager systems. You must access administration and reporting from a browser on a PC.1. 4.1. • Communication Manager software releases 3. Version 1. Note: You cannot use the browser provided with the Linux OS for administration and reporting. Proactive Contact software This section describes software requirements for Proactive Contact systems: • Proactive Contact software releases 3.x Note: Avaya IQ does not support using the G3 CSI (Prologix) hardware platform as a source.x. 26 Preparing for Avaya IQ Implementation Comments? infodev@avaya. • Proper administration of contact center data collection features as described in Administering a link between Communication Manager and Avaya IQ on page 103. and 5. • PG230 hard dialer (Avaya IQ does not support the Proactive Contact soft dialer) • The Proactive Contact system must already be configured to work with a Communication Manager system. When adding an allowed site to the list. • The Proactive Contact system must be administered with blended inbound and outbound agents. Firmware 26.com November 2011 . use the IP address of the root host machine. • Dedicated C-LAN connection for the Avaya IQ link The C-LAN circuit pack must be TN799D.Software requirements allowed sites. Communication Manager software This topic describes requirements for Communication Manager systems used as sources to Avaya IQ.x and 4.

the system uses secure HTTP connections. The CMS versions that are compatible with Avaya IQ include CMS R13. • Network Time Protocol (NTP) time synchronization software must be installed and operating on the Proactive Contact system. The dialers are grouped only for administration purposes and otherwise function independently. you will continue to use your existing Call Management System (CMS) with Avaya IQ.Call Management System software • There is no support for standalone systems. The procedure is documented in Proactive Contact link administration on page 119.1.x. you must administer the link between the systems. If you obtain these certificates before Avaya or a Business Preparing for Avaya IQ Implementation November 2011 27 . Users will receive a security warning dialog. outbound-only agents. although Avaya IQ can connect to the individual dialers in the pod. • Depending on the Avaya IQ release and the Proactive Contact release. or overflow blending.x. you can obtain trusted certificates that you can install on the Avaya IQ application hosts. or you can do the integration yourself using the procedures provided in Integrating with Active Directory in Administering Avaya IQ. Avaya provisioning can integrate your enterprise directory during initial implementation. call blending. Call Management System software In many deployments. 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. Multiple Proactive Contact dialers can be deployed in an administrative group called a pod. All application hosts must be synchronized using the same NTP source as all Proactive Contact systems in the deployment. To avoid this condition for your users. They must either accept the dialog every time they access the system or they can permanently install the certificate. One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Proactive Contact system. and R15. This allows you to add administrative and reporting users automatically from your enterprise directory without using separate authentication from Avaya IQ. Avaya IQ does not directly represent the pod configuration. R14. Security certificates When users access reporting or administration with Avaya IQ.

intranet 123 Destination Receiver SSH Server (each host) SMTP Email Server (each Reporting host) Apache Linux network time protocol daemon. intranet Dynamic. intranet Dynamic. the default port numbers may conflict with your network.Software requirements Partner installs your system. When using a Proactive Contact system. ntpd (each host) 22 25 80 123 Port User Service (Admin or All Dynamic Functions host) Linux network time protocol daemon.com November 2011 . firewall rules. Give this list of ports to your system administrator to determine if any of the ports being used are not available in your network. you can request that they install the certificates for you. see the additional information in Considerations for Proactive Contact ports. corporate network standards. ntpd (each host) Ports Dynamic. In some cases. Document any conflicts in Firewall port conflicts worksheet. Destination Port: The default port(s) used at the machine or application responding to an initiator. 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. ntpd (each host) 631 389 631 28 Preparing for Avaya IQ Implementation Comments? infodev@avaya. The following definitions describe the headings used in the table. or other reasons. Source Port: The default port(s) used by the source device or application. This may be caused by conflicts with other applications you are running. Source Initiator: The device or application initiating a data flow. ntpd (each host) slapd (Admin or All Functions host) Linux network time protocol daemon. Source Initiator SSH Client Reporting User Interface Web Browser Linux network time protocol daemon. Destination Receiver: The device or application receiving a data flow from a source.

8443 Reporting host Reporting host Reporting Application entities (Reporting host) Dynamic.Firewall port usage Source Initiator Ports User Service (Admin or All Dynamic Functions host) Oracle DSS Database clients (Admin. 8443 License management admin . intranet Dynamic. intranet All Functions. intranet Dynamic. intranet Dynamic Tomcat (Reporting host) 9300 Tomcat (Reporting host) 9334 Reporting Application Log Server (Reporting host) 9362 Web Browser or command Dynamic. or Reporting hosts) Event Manager (Data Processing host) CM Adaptor (Data Processing host) Local managed entities (each host) Child watchd (each host) License management client (each host) Dynamic. Dynamic. intranet 8080. local host (loopback) Dynamic. intranet line All peer Service Locators and clients (each host) Web services access to Data Export Web Browser PC adaptor 10000 10080 18443 Tomcat (Reporting host) 9399 Service Locator (each host) 10010 10080 Reporting User Interface 18443 Varies Varies (need to open Proactive Contact all ports going to PC) Preparing for Avaya IQ Implementation November 2011 29 .Web browser Dynamic. local host (loopback) Dynamic. intranet DSS Destination Receiver slapd (Admin or All Functions host) 636 1031 1099 1521 Port Oracle SQL*Net (database host) System Mgmt Tomcat (Admin or All Functions host) Communication Manager 5001 5002 Child watchd (each host) 7010 Parent watchd (each host) License management server (WebLM) (Admin or All Functions host) License management server (WebLM) (Admin or All Functions host) 7011 8080.

library within services that use SDAS (each host) 31050 Dynamic Dynamic. intranet Dynamic. identified elsewhere in table (Admin or All Functions host) 31050 30 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Intranet Dynamic.com November 2011 . Intranet 50025 Historical Fact Recorder 31001 (Admin or All Functions host) JBoss Instances Alarm Server (Admin or All Functions host) Host Log Server (each host) Network Log Server (Admin or All Functions host) 31002-31049 31050 31050 31050 31050 31050 DSS port for specific SDAS service.Software requirements Source Initiator PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) PC Adaptor (Data Processing host) 31004 31004 31004 31004 31004 Ports Destination Receiver Proactive Contact Proactive Contact Proactive Contact Proactive Contact Proactive Contact Proactive Contact Tomcat (Admin or All Functions host) Tomcat (Admin or All Functions host) Tomcat (Admin or All Functions host) Tomcat (Admin or All Functions host) Port 23120 23121 23200 23201 23260 23261 28005 28080 28443 28444 Adaptor (Data Processing 31004 host) Tomcat Service OAM User Web Browser OAM User Web Browser OAM Certificate Management Event Mgmt Forwarder (Data Processing host) Event Mgmt Forwarder (Data Collection host) Network Log Server (Admin or All Functions host) Log client (each host) Host Log Server (each host) System Configuration Client.

50299 50027 23200 50027 50027 52222 Event Management (Data 50025 Processing host) Historical Fact Recorder (Admin or All Functions host) Historical Dim Recorder (Admin or All Functions host) Many entities (each host) Many entities (each host) ETL PE server (Admin host) 31001 31002 52222 Dynamic. intranet 5432 61616 61617 5432 Related topics: Network requirements on page 19 Administering Proactive Contact ports on page 31 Firewall port conflicts worksheet on page 94 Administering Proactive Contact ports About this task The ports used to collect events from a Proactive Contact system are assigned at random.Administering Proactive Contact ports Source Initiator Lifecycle utilities (each host) Ports 50200 . This makes it difficult for a customer collecting data from a Proactive Contact system to have a firewall. intranet Dynamic. You can administer a rule in the iptables file to allow the use of a firewall on the Avaya IQ system when collecting data from a Proactive Contact system.50299 Destination Receiver Port Lifecycle Manager (each 50000 host) Lifecycle Manager (each 50000 host) Lifecycle Manager (each 50001 host) Historical Event Processor (Data Processing host) PCS Adaptor (Data Processing host) PCS Adaptor (Data Processing host) IRS (Admin or All Functions host) IRS (Admin or All Functions host) ActiveMQ (each host) ActiveMQ ETL Web service client (Admin host) 50025 Subsystem Administration 31050 (Admin or All Functions host) Lifecycle utilities (each host) PCS Adapter (Data Processing host) Proactive Contact 50200 . Preparing for Avaya IQ Implementation November 2011 31 .

6. Save and close the file. Just before the final line of the file. 5. enter the following lines: # PCS Adapter (Data Collection host) -A RH-Firewall-1-INPUT -s IP_Address /255. the REJECT line.Software requirements Procedure 1. Make the new rule effective in your firewall by entering the following command: service iptables restart Related topics: Firewall port usage on page 28 Permissive use policy Avaya may support specific nonstandard Avaya IQ deployments. Delete these lines.com November 2011 .255. Contact your Avaya sales representative or Avaya support for a copy of this policy. 32 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Search for the following lines: # PCS Adapter (Data Collection host) -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 50027 j ACCEPT 3.255 -p tcp -j ACCEPT IP_Address is the address of the Proactive Contact system.255. Enter: vi /etc/sysconfig/iptables 2. 4.

These recommendations include the following practices: • Install the minimum OS configuration allowed that supports Avaya IQ • Install firewalls to protect your network connections.Administrative changes . • Keep your OS updated with the latest security patches. • Locate your equipment in secure locations.System configuration changes . or deletion of installed packages • Once Avaya IQ is installed. • Configure the OS to log the following security related events: . Verify that system hardening steps and security best practices have been followed before you install any application. • Regularly monitor the security events logged by the OS.Addition. For more information about securing your installation.Activities of privileged logins . Security recommendations Your OS must be installed and maintained following the recommendations of the OS manufacturer. monitor the Avaya IQ security events via the Security and Administration Audit categories in the Log Viewer. These requirements only note that certain options must be set.Chapter 4: Setting up the operating system This section provides what facets of the OS must be set up to be compatible with Avaya IQ. see these and other resources that are available on the World Wide Web: • The Center for Internet Security • Security information for the Red Hat Linux OS • The Avaya site for security policies and advisories Preparing for Avaya IQ Implementation November 2011 33 . modification.Account privilege changes . These requirements do not go into any details on how to set the OS options.Logins and logouts .

and Proactive Contact systems in the deployment. 34 Preparing for Avaya IQ Implementation Comments? infodev@avaya.com November 2011 . Time synchronization and time zone setup requirements All application hosts must have NTP client software installed. and working properly. You can specify the IQ servers IP addresses in iptables to restrict this access. signed digital certificates. Avaya IQ uses self-signed certificates and certificates signed by the Avaya CA to support secure communications and secure data storage. Firewall port setup During installation and operation. logins and logouts. configured. Digital certificates A Certificate Authority (CA) is an entity that provides trusted. The NTP time synchronization service must be synchronized from the same NTP source as all hosts. Communication Manager systems. 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. addition. you can use the administration interface to generate and install certificates or you can install certificates that you purchase from other trusted CAs. specific TCP ports are used by Avaya IQ and must be made available. Use the information provided in Firewall port usage to properly configure external firewalls and Linux-based iptables. Though additional certificates are not required to operate Avaya IQ. or deletion of installed packages. modification. One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Communication Manager systems. Product software cannot be installed without the presence of a functioning time synchronization service. and system configuration changes.Setting up the operating system Event logging Configure your OS to log security related events such as account privilege changes. Regularly monitor the security events logged by the OS. Note: Avaya recommends you to restrict access to the IQ database through Avaya IQ servers only.

Many Avaya IQ processes run as this user ID. Related topics: User and group IDs created during installation on page 17 Preparing for Avaya IQ Implementation November 2011 35 . Most installed files will be owned by this user and will be a member of the group with the same name. 2. For example. Unauthorized users can use this information to develop attacks against the OS. Therefore. This user ID does not have login capability. and tsc) are required during implementation and ongoing support. This user ID will appear when you display the permissions of the files. an OS user ID is automatically created and is associated with the Avaya IQ files installed on application hosts. These user IDs are reserved for this use and the customer should not create identical user IDs because they will conflict with the Avaya user IDs. The database host can use any OS that supports the proper version of the database software. craft. OS and database compatibility All application hosts in the deployment must use the same OS version as described in Software requirements. See User and group IDs created during installation for more information about user IDs created during installation. • During installation of Avaya IQ.OS and database compatibility Note: 'The NTP service when enabled provides additional information about the Operating System (OS) to the user. set the firewall to off for the NTP service. as well as when you list the processes that are executing on the host. In iptables. also documented in Software requirements. To disable this feature: 1. but your database host can use Sun Solaris as the OS for the Oracle database software. a number of Avaya services user IDs are installed at the same time. your application hosts must have the proper version of the Linux Red Hat OS. Avaya recommends that you disable the feature to query the NTP service. add the line restrict default ignore. These user IDs (sroot. User ID requirements Adhere to the following user ID requirements: • When Avaya IQ is installed. In the ntp.conf file. so you should not select a user ID that you also want to use as an active login ID.

You can identify the Avaya IQ hosts that correspond to these functions in the Implementation Report for Customer from the Implementation Planning Tool. For assistance on installing the OS.com/docs/manuals/enterprise/. • Reporting on a multiple host deployment. use the OS installation documents at http:// www.Setting up the operating system Installing the database client software Before you begin Before you install the Oracle client software on Avaya IQ hosts. Specific operating system requirements used during installation Information to collect before installation This section describes specific requirements used during the OS installation on each Avaya IQ hosts. 36 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Procedure Follow the instructions documented in the Oracle Database Client Installation Guide when installing the Oracle client software on the Avaya IQ hosts. About this task You must install the Oracle client software on Avaya IQ hosts that are administered with the following host functions: • All Functions on an All Functions host with Remote Data Collection deployment.com November 2011 .redhat. Note: You must use the Administrator installation type. • Administration on a multiple host deployment. • Install the same Oracle client and server versions during Avaya IQ installation and upgrade processes. you must perform the following tasks: • Install the supporting packages required by the operating system to support the Oracle client software. when installing the client software.

• Obtain IP addresses for every host on which you will install the OS.English . Press Esc or enter the BIOS configuration. and so on as required by Red Hat. use the following table as a guideline. firmware updates. The options described in this section are only for application hosts. set the swap size equal to the size of the RAM.Japanese .Specific operating system requirements used during installation Important: Do not use this procedure to install the OS on the database host. set swap size to 1. see http://hardware. • Install BIOS/CMOS updates. you must perform the following tasks: • Confirm if the hardware is compatible with the Red Hat Linux version. Mount point n/a Type swap Minimum recommend size Use the following recommendations to calculate swap space: • If RAM is 1024 MB or less.5 times the size of the RAM.French . Information used to complete the installation Use the following information to complete the OS installation: • Language Selection: Select the language you want to use for the installation. • Partitioning: Select manual partitioning. Avaya IQ supports the following languages: .U.Brazilian Portugese You must install language packs for any languages that you want to use. . If you do not know this. The asterisk indicates the mount point name and size required for the software.redhat.S.Korean . • If RAM is between 1025 MB and 2048 MB. set swap size to 2 times the size of the RAM. Preparing for Avaya IQ Implementation November 2011 37 .com/hcl/. it should be displayed immediately after power-on. For more information.German . if necessary. • Determine what possible base languages you want to use.Simplified Chinese . • If RAM is 2049 MB or larger. When assigning the size of each partition. • Record the size of the physical memory of each host. The only mount points that have a size required by Avaya IQ are marked with an asterisk (*). Before you begin the installation.

refer to http:// www. • File System Type: Select the appropriate file system type for this partition from the dropdown menu. • Size (MB): Enter the size (in megabytes) of the partition. Set the host name manually using the host name or fully qualified host name. the partition is created as a logical partition.com November 2011 . Network Configuration: The installation program automatically detects any network devices (ethernet ports) you have and displays them in the Network Devices list.Setting up the operating system Mount point Type Minimum recommend size If the swap space is larger than 2 GB. 5120 MB 5120 MB 10240 MB 20480 MB Administer the following options: • Mount Point: Enter the partition's mount point. By using different settings. If a hard disk's box is highlighted.html /* /avaya* /boot /home /opt* /tmp* /u01* /usr /var* ext3 ext3 ext3 ext3 ext3 ext3 ext3 ext3 ext3 5120 MB 8192 MB 512 MB 4096 MB 40960 MB plus any remaining space. if this partition should be the root partition. When editing the ethernet network device. This allows you to keep a certain amount of space free on your hard drive for future use. • Additional Size Options: Choose whether to keep this partition at a fixed size. 38 Preparing for Avaya IQ Implementation Comments? infodev@avaya. to allow it to grow (fill up the available hard drive space) to a certain point. then a desired partition can be created on that hard disk. For example. you must give size constraints in the field to the right of this option.redhat. Enter any gateway or DNS IP addresses if required for your network.com/docs/manuals/enterprise/RHEL-5-manual/ Installation_Guide-en-US/ch04s18s04s02. If it is cleared. enter /. then the partition will never be created on that hard disk. If you choose Fill all space up to (MB). you can have Disk Druid place partitions where you need them. select Activate on boot and enter the IP Address and Netmask for the host. If the box is not checked. • 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. or let Disk Druid decide where partitions must be created. A minimum 100 MB partition will be created if you do not select a larger value. • Allowable Drives: This field contains a list of the hard disks installed on your system. or to allow it to grow to fill any remaining hard drive space available.

German. You can install these RPMs using the standard Linux RPM package installation commands. For more information.log. you can view a log of the installation in /root/install. French. Root Password: Create and confirm the password for root. Preparing for Avaya IQ Implementation November 2011 39 . Select and install the following packages: • X Window System • GNOME Desktop Environment • Graphical Internet • Text-based Internet • Server Configured Tools • Web Server • Administration Tools After the software is installed.Specific operating system requirements used during installation Firewall Configuration: Select the following options depending on the host type: • Enable firewall for all application hosts.2 64-bit installation process. and Brazilian Portuguese. Use the echo $LANG command to determine your setting. the Installation Complete dialog is displayed. • Remote Login for all application hosts. Korean.1. Administration. Additional Language Support: Select a default language and other languages that can be used for the Avaya IQ Administration and Reporting interfaces. Important: Do not enable SMTP or FTP services on any Avaya IQ application host. English. • Web Server for All Functions. Avaya IQ RPMs: You must install the following RPMs on all Avaya IQ hosts. the supported languages are Simplified Chinese. Keep track of this password as the Avaya implementation personnel will need to log in as root for a portion of the software installation. Japanese. Important: Before Avaya IQ is installed. For Avaya IQ Release 5. If the LANG variable is not set. Package Installation: Select Customize software packages to be installed. the default language is English. To see the complete list of the required RPMs. see Language variables on page 41 for the LANG variable for each supported language. The system does not install these RPMs during the standard Linux 5. you must run the Configuration Audit Tool (CAT) tests (see Using the Configuration Audit Tool on page 59). After the system reboots. verify that the value of the LANG variable is what you want as the default language. and Reporting hosts.

x86_64.xorg-x11-xauth-1.rpm .rpm 40 Preparing for Avaya IQ Implementation Comments? infodev@avaya. However.el5.el5. Avaya IQ requires the 7-8 version.3.3.el5_1.1 .2.27-8.el5_1.rpm .3.libtool-ltdl-1.3.2.1.el5_1.rpm is a 32-bit RPM and libXp-1.com November 2011 .i386.gdbm-1.i386.3.compat-libstdc++-33-3.0-8.1.libXp-1.1.1.i386. • Apache requires the following RPMs for the Report Gateway on the Reporting host for libdb-4.2-5.compat-db-4.openmotif22-2.52-5.1.rpm • The standard Linux installation process installs the 7-2 version of the following RPM.openldap-clients-2.openldap-servers-2.Setting up the operating system Note: In the list.libXp-1.x86_64.libtool-ltdl-1.0.7-8.i386.openmotif22-2.rpm .el5.rpm is a 64-bit RPM.0.8.2p1-8.rpm • The GUI version of the Avaya IQ installation program requires the following RPMs: .0-0.i386.2.1.2. • You must ensure that the server and client version of the following packages match the base LDAP package: .openldap-servers-2.2.27-8.so: .5.x86_64.3 (or later) .27-8.x86_64.0-8.27-8.0.22-6.1.1.0-8.x86_64.el5 RPM provides the NTP service.3.openldap-clients-2.i386.rpm (or later) • The Reporting application requires the following RPMs: .1.i386.2-5.x86_64.libXmu-1.0-8.3-18.el5_1.0-26.x86_64.3-18.5.3-61.3 (or later) .0.1-2.1.5.openmotif-2.rpm . the *.compat-db-4.rpm .rpm .rpm • The ntp-4.el5.el5.rpm • The following RPMs build shared libraries: .3.1.2.openldap-2.rpm .rpm indicates 32-bit RPMs and the *.52-5. gamin-0.i386. For example.3 (or later) .el5.rpm (or later) .3. libXp-1.el5_1.rpm (or later) .x86_64.i386.0.i386.27-8.x86_64.0.rpm indicates 64-bit RPMs.i386.libXmu-1.22-6.rpm (or later) .0.1.

ensure that you have installed the supporting packages required by the OS to support the Oracle client software.UTF-8 en_US. NTP: Configure NTP on the host.Language variables Important: Before you install the Oracle client software on the Avaya IQ hosts. For more information about the software requirements. If you have installed a GUI interface. 2.UTF-8 Confirming hostname setup About this task Ensure that the hostname configured at /etc/sysconfig/network and /etc/hosts is localhost.UTF-8 pt_BR. At the command prompt. Your hostname is correctly configured if you get corresponding Echo Reply messages. type ping localhost.UTF-8 de_DE.UTF-8 fr_FR.conf file to set the NTP synchronization source. You can also edit the /etc/ntp.UTF-8 ko_KR. Language variables Language Simplified Chinese English US French German Japanese Korean Brazilian Portuguese Latin American Spanish LANG variable zh_CN. see Oracle Database Client Installation Guide. Procedure 1. use the systemconfig-date command to set your system time and NTP synchronization source.UTF-8 es-CO. Press ENTER. Preparing for Avaya IQ Implementation November 2011 41 .UTF-8 ja_JP.

Setting up the operating system

42

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

Chapter 5: Setting up database software
For a software-only deployment, the customer is responsible for all facets of database setup. These facets include, but are not limited to, the following tasks: • Installing the database server and client software on the database host. • Installing the database client software on certain application hosts before Avaya IQ is installed. When you install Oracle on your database host, make sure that you have installed all supporting packages required by the OS to support Oracle. All software requirements for Oracle can be found in Oracle documentation. Note: CAT verifies the required number of open cursors and the maximum number of processes in historical tablespaces. The required number of open cursor is 2000 and the maximum number of processes is 1000. Important: The Avaya IQ Product Version Interoperability document lists the latest software versions required by Avaya IQ and takes precedence over any software versions shown in this section. Verify all software version requirements in the interoperability document before purchasing and installing any software. You can find the interoperability document under the product documentation area for Avaya IQ on the Avaya Support Web site at http://support.avaya.com/.

Setting up database software checklist
While creating and configuring the database instance on the database host, complete the following procedures: For more information about configuring the database options described in this section, consult your database vendor documentation. See the Oracle Database Installation Guide and Oracle Database Administrator’s Guide on the Oracle documentation Web site at: http:// www.oracle.com/technology/documentation/index.html As you create these required options, tablespaces, and users on the database host, use the Database host worksheets on page 87 to collect this information for yourself and for the Avaya or Business Partner personnel who will install Avaya IQ. To assist you in creating the tablespaces and users, we have provided a set of sample scripts that you can use when building your own scripts. These scripts are found in Sample database scripts on page 99.

Preparing for Avaya IQ Implementation

November 2011

43

Setting up database software

# 1. 2. 3. 4. 5. 6. 7.

Task Partitioning The OS for the database on page 44 Creating database connections on page 45 Configuring Oracle parameters to improve Avaya IQ performance on page 45 Setting up character sets on page 46 Creating tablespaces on page 47 Creating database users and applying permissions on page 48 When installing the database client on the application hosts, complete the following procedures: • Installing The database client software on page 36 • Creating a Net Service Name on page 53

Guidelines for partitioning the OS for the database
Use the following guidelines when partitioning the OS for the database host: • Customers who use a shared enterprise database should not do any special partitioning for the OS. Use these partitioning suggestions only for systems that use a dedicated Linux-based database host. • Follow any recommendations that you get from the Implementation Planning Tool outputs on RAID configurations for the database. • Use outputs from the Implementation Planning Tool to provide the proper amount of space for tablespaces. • Set Shared Memory (SHMMAX, SHMMNI, SHMALL, and so on). • Protecting /tmp from the rest of the hard disk by placing it on a separate partition can ensure that the applications that need to write temporary files in /tmp are capable of completing their processing even if the disk fills up. • FTP and HTTP servers use the /var partition. Denial of service attacks tend to corrupt or fill disk space. If the partition fell under root (/), then the attack is capable of taking down the entire host. • Review Oracle's sizing recommendations for Linux. • Refer to the Oracle Technology Network for more recommendations on disk partitioning.

44

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

The values from the Implementation Planning Tool are a starting point and you must monitor your system to ensure that you have enough database connections for your deployment. there are some parameters you can adjust when installing the Oracle database host software. Preparing for Avaya IQ Implementation November 2011 45 . Initialization parameter pga_aggregate_target sga_max_size sga_target 1400 MB 2200 MB 1600 MB Size 2. you must set up a number of database connections. Procedure Administer the number of database connections based on outputs from the Implementation Planning Tool.Creating database connections Creating database connections About this task When you set up your database. Note: The automatic refresh of materialized view does not work if the Oracle parameter job_queue_processes is set to 0. You may also want to administer the redo logs as 20 groups with a size of 200 MB each. To prepare the Oracle database so that it operates most efficiently with Avaya IQ. Configuring Oracle parameters to improve Avaya IQ performance Procedure 1. or some similar distribution of the log files. Administering these initialization parameters with sizes similar to the ones shown in the following table may improve database performance during materialized view refreshes. The value of this parameter must be greater than 0.

such as those shown in the following list: • kernel. Another performance-related parameter is CURSOR_SHARING. Otherwise.shmall • kernel. 46 Preparing for Avaya IQ Implementation Comments? infodev@avaya. If these kernel parameters are not set properly.shmmax • kernel.sem • fs. Follow the kernel parameter installation recommendations in the Oracle software preinstallation documents. installations and upgrades o fAvaya IQ may not work at all.ipv4. most default settings will be adequate. you must install the correct version of Oracle according to Oracle's recommended procedures. Setting up character sets Procedure When configuring the database instance.core. UTF16. All of these kernel settings are automatically verified by the Oracle installation and auditing tools.com November 2011 . You must enable the following options. or AL16UTF16.file-max • net. AL32UTF8. One exception is when you are configuring the character sets.shmmni • kernel.rmem_default • net.core. This parameter is important for the performance of the reporting software. This parameter must be set to EXACT.wmem_default • net.Setting up database software Administering the redo logs with this setup may help improve the wait time during log file switch operations.core. • The National Character Set must be set to UTF8.ip_local_port_range • net. the transaction load may cause excessive wait times and cause incomplete messages to be written to the log files.wmem_max These kernel parameters help control the readiness of the database host. • The Database Character Set must be set to Unicode AL32UTF8. including any OS kernel parameters.core. 4. When installing your database software. 3.rmem_max • net.

These values are based on your contact center traffic and sizing. These tablespaces are linked to the Avaya IQ software during the configuration phase of implementation. The sizes from the Implementation Planning Tool are a starting point and you must monitor your system to ensure that the tablespaces have enough space for day-to-day operation. fact historical data. and real-time data.Creating tablespaces These character sets are required for the reporting interface. which are inputs to the Implementation Planning Tool. The following table describes the tablespaces used with dimensional historical data. Creating tablespaces About this task You must create a fixed number of tablespaces on your database to store administration and reporting data that is associated with the system and database users you create in Creating database users and applying permissions on page 48. Use the names in this table when you create the tablespaces. index historical data. Purpose One tablespace to store the historical report dimension HDIM01 data Ten tablespaces to store the historical report fact data Name HFACT01 HFACT02 HFACT03 HFACT04 HFACT05 HFACT06 HFACT07 HFACT08 HFACT09 HFACT10 Five tablespaces to store the historical index data HINDEX01 HINDEX02 HINDEX03 HINDEX04 Preparing for Avaya IQ Implementation November 2011 47 . The recommended size of the tablespaces are provided by the Implementation Report for Customer from the Implementation Planning Tool.

Use the names in this table when you create the tablespaces. After you create the tablespaces and database users.avaya. use the scripts in Sample database scripts on page 99 as a guideline when you build scripts to associate the users with the correct tablespaces. If you do not receive any recommended tablespace sizes. Record your tablespace sizes in Database host worksheets on page 87.Setting up database software Purpose Name HINDEX05 One tablespace to store the historical report data One tablespace to store the real-time report data One tablespace to store the System Data Store information One tablespace to store the content data store One tablespace to store the Reporting user interface data USERHIST USERRT USERSDS USERRPT USERUI The following table describes the tablespaces associated with some of the database users created in Creating database users and applying permissions on page 48.com for more information. These users are needed so that the application software can communicate with the database host. Each of the database users require specific permissions so that the application software can access the different 48 Preparing for Avaya IQ Implementation Comments? infodev@avaya.com November 2011 . create all of these tablespaces and give them a starting size of 4 GB each. Refer to the Database Server Configuration Recommendations and Oracle Guidelines document on http:// support. Avaya recommends that you administer at least 5 GB of free disk space in the Oracle TEMP tablespace and at least 8 GB of free disk space in the Oracle UNDO tablespace. Purpose One tablespace to store data related to the default application user One tablespace to store the real-time data One tablespace to store the system data store data One tablespace to store the reporting tool data One tablespace to store the reporting user interface data Name USERHIST USERRT USERSDS USERRPT USERUI Use the autoextend option to allow the tables to grow by an amount acceptable within your available space guidelines. Creating database users and applying permissions About this task You must create several database users on the database host.

use the names shown in the following table: Caution: • Database user names must not exceed 27 characters. Use the names shown in this table to stay within the character limit. You may use the Real-time Data Store user (RPT_RT_USR) for this function or you may create the individual read-write or read-only users. For upgrades from Avaya IQ 4. you can make these users optional. For upgrades from Avaya IQ 4. Purpose User name Additional information Historical Data Store RPT_HIST_OWNER owner _USR Historical Data Store RPT_HIST_RW_US These users are optional depending on your user with read-write R security needs.1. • You must have a dedicated Oracle instance for Avaya IQ. You may use the Real-time Data Store user (RPT_RT_USR) for this function or you may create the individual read-write or read-only users. The Configuration Audit Tool user (CAT_USR) is used by the tool when testing connections to the database. Avaya recommends that you create these new users before the upgrade is applied to your system. These users are optional depending on your security needs.Creating database users and applying permissions data stores. You may use the Historical R permission Data Store owner user (RPT_HIST_OWNER_USR) for this function or you may create the individual read-write or read-only users.1. Avaya IQ appends three characters to the user name and Oracle has a 30 character limit for user names. Avaya recommends that you create these new users before the Real-time Data Store RPT_RT_RO_USR user with read-only permission Preparing for Avaya IQ Implementation November 2011 49 . Real-time Data Store RPT_RT_USR owner Real-time Data Store RPT_RT_RW_USR user with read-write permission These users are optional depending on your security needs. However. When you create these users. You may use the Historical permission Data Store owner user (RPT_HIST_OWNER_USR) for this function or you may create the individual read-write or read-only users Historical Data Store RPT_HIST_RO_US These users are optional depending on your user with read-only security needs.

System Data Store user Content Data Store user Reporting UI Data Store user Configuration Audit Tool user RPT_SDS_USR RPT_CONTENT _USR RPT_UI_USR CAT_USR These users are associated with the tablespaces created in Creating tablespaces on page 47.com November 2011 . Record your user names in the Database host worksheets on page 87. For security purposes. Assign permissions to the Historical Data Store database users as shown in the following table: Permissions Owner CREATE SESSION CREATE TABLE CREATE VIEW CREATE PROCEDURE CREATE TRIGGER CREATE SEQUENCE CREATE ROLE UNLIMITED TABLESPACE TO* Yes Yes Yes Yes Yes Yes Yes Yes Historical Data Store Read-Write User Yes No No No No No No No Read-Only User Yes No No No No No No No 50 Preparing for Avaya IQ Implementation Comments? infodev@avaya. you would not want to assign read-write permissions to a user that requires only read permission. you can make these users optional. After you have created the tablespaces and database users. You should also assign unique passwords to each database user. Depending on your security requirements. However. For example. Another reason to assign different users is when you assign permissions to the different database users. Avaya requires that you assign different user names for access to the different data stores. Be sure to keep track of those passwords as they are required during installation of the Avaya IQ software. the Historical Data Store and the System Data Store database users should not use the same database user name.Setting up database software Purpose User name Additional information upgrade is applied to your system. use the scripts in Sample database scripts on page 99 as a guideline to associate the users with the correct tablespaces. you do not need to set password aging for the database users because they are used only to communicate with Avaya IQ programmatically and are not used for any other purpose.

Creating database users and applying permissions Permissions Owner <each Avaya IQ application database user> CREATE MATERIALIZED VIEW SELECT ANY DICTIONARY Yes Historical Data Store Read-Write User Read-Only User No No No No No Assign permissions to the Real-time Data Store database users as shown in the following table: Permissions Owner CREATE SESSION CREATE TABLE CREATE VIEW CREATE PROCEDURE CREATE TRIGGER CREATE SEQUENCE CREATE ROLE Yes Yes Yes Yes Yes Yes Yes Real-time Data Store Read-Write User Yes No No No No No No No Read-Only User Yes No No No No No No No UNLIMITED Yes TABLESPACE TO* <each Avaya IQ application database user> CREATE MATERIALIZED VIEW SELECT ANY DICTIONARY Yes No No No No No Assign permissions to the System Data Store. Content Data Store. Reporting UI Data Store. and CAT database users as shown in the following table: Preparing for Avaya IQ Implementation November 2011 51 .

52 Preparing for Avaya IQ Implementation Comments? infodev@avaya. you must perform the following tasks: • Install the supporting packages required by the operating system to support the Oracle client software.Setting up database software Permissions CREATE SESSION CREATE TABLE CREATE VIEW CREATE PROCEDURE CREATE TRIGGER CREATE SEQUENCE System Data Store User Yes Yes Yes Yes Yes Yes Content Data Store User Yes Yes Yes Yes Yes Yes No Yes Reporting UI Data Store User Yes Yes Yes Yes Yes Yes No Yes CAT User Yes No No No No No No No CREATE ROLE No UNLIMITED Yes TABLESPACE TO* <each Avaya IQ application database user> CREATE MATERIALIZE D VIEW SELECT ANY DICTIONARY No No No No No No No Yes Installing the database client software Before you begin Before you install the Oracle client software on Avaya IQ hosts. • Install the same Oracle client and server versions during Avaya IQ installation and upgrade processes.com November 2011 .

Procedure Follow the instructions documented in the Oracle Database Client Installation Guide when installing the Oracle client software on the Avaya IQ hosts. • Administration on a multiple host deployment. you must edit the Oracle tnsnames.ora file on the application hosts.Creating a Net Service Name About this task You must install the Oracle client software on Avaya IQ hosts that are administered with the following host functions: • All Functions on an All Functions host with Remote Data Collection deployment. • Reporting on a multiple host deployment. You must add an entry for the Net Service Name. You can create any value as the Net Service Name. The following is an example of the information you would add to the application host when using a single database instance: Result <Net_Service_Name> (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_host>)(PORT = 1521)) Preparing for Avaya IQ Implementation November 2011 53 . when installing the client software. The entry you add depends on whether you are using a single database instance or a RAC database instance. Note: You must use the Administrator installation type. Creating a Net Service Name About this task To support communications between Avaya IQ reporting software and the database host.ora. This file is typically found at $ORACLE_HOME/network/admin/ tnsnames. You can identify the Avaya IQ hosts that correspond to these functions in the Implementation Report for Customer from the Implementation Planning Tool. you must create a Net Service Name on the application hosts where you have installed the Oracle database client software. This includes the following application hosts in your deployment: • All Functions (All Functions with Remote Data Collection deployment) • Reporting (Multiple Host deployment) Procedure To create a Net Service Name.

com November 2011 . restore strategy. The BHC rate of theAvaya IQ system is the total Busy Hour calls for all administered Communication Manager sources. use the following procedure.Setting up database software (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = <service_name>) ) ) In this example: • <Net_Service_Name> is the Net Service Name that you have chosen • <DB_host> is the name of the single database host • <service_name> is the database service name The following is an example of the information you would add to the application host when using a RAC database instance: Net_Service_Name> = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_hostN>)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_hostN>)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_hostN>)(PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = <service_name>) (FAILOVER_MODE = yes) (TYPE = SELECT) (METHOD = BASIC) (RETRIES = 180) (DELAY = 5) ) ) ) In this example: • Net_Service_Name> is the Net Service Name that you have chosen • <DB_hostN> are the names of each database host in the RAC configuration • <service_name> is the database service name Sizing Oracle Redo log file About this task Redo log files forms a part of a larger database backup. and is important for database throughput. Determining the proper redo log file is important for databases throughput. To determine the redo log file size. 54 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Note: You must know the approximate Busy Hour Call (BHC) rate for yourAvaya IQ system. The size of the Redo logs affects the efficiency of the Oracle LGWR and ARCH background processes.

Procedure 1. Sizing Oracle Undo Tablespace About this task The sizing estimates provided in this procedure relates to Undo Tablespace management and accounts for execution of the Avaya IQ purge data utility. Note: Redo log size modeling does not account for extraneous operations such as data imports and data purges. Use the selected value in the following calculation BHC * BHC multiplier = redo log file size KB.000 (300 MB). Use Oracle Automatic Undo Management. <25K total BHC Per BHC multiplier 12 26-75K total BHC 15 76-125K total BHC 10 8 126-200K total BHC 2.000 * 12 = 300.0.2 to 5. Select the BHC multiplier from the table. an extra redo log sizing considerations can be necessary. 2. You can accommodate backup media sizing efficiencies (for backup of archive log files) by adjusting the recommended size. This accommodatesAvaya IQ data purge operations executed through fact_data_purge utility. Enable undo tablespace AUTOEXTEND option. Example If BHC rate = 25. Note: While upgrading from Avaya IQ 4. If operations of this type occurs regularly.000 then 25. ensure that: Preparing for Avaya IQ Implementation November 2011 55 . Periodically monitor undo size to ensure that maximum has not reached. Set undo table space size to 8 GB.Sizing Oracle Undo Tablespace Procedure 1. Note: If you have disk capacity concerns then set it to MAXSIZE. 3.

56 Preparing for Avaya IQ Implementation Comments? infodev@avaya. • Maximum size is set to unlimited • At least 30 GB of disk space is available for undo tablespace file extents or else increase the undo tablespace size to 30 GB.Setting up database software • AUTOEXTEND option is enabled for undo tablespace. enable AUTOEXTEND option. then set TEMP tablespace size to 10GB. If you are using the data purge utility and BHC is greater than 50K.com November 2011 . Sizing Oracle TEMP tablespace Set the TEMP tablespace size to 5 GB. You can reduce the undo tablespace size after the Avaya IQ upgrade. If space exists for growth.

• The Communication Manager servers 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. Most of these items were probably administered when the Proactive Contact system was originally installed.Chapter 6: Setting up data sources This section contains any critical setup requirements for the sources that provide data to Avaya IQ.0 does not support CM SIP endpoints that use DCET phones. but these must verified before attempting to install Avaya IQ. and Proactive Contact systems in the deployment. These data sources can be any combination of Communication Manager and Proactive Contact systems. See Administering a link between Communication Manager and Avaya IQ on page 103. Verify that all queues and routing points are administered for measuring by Avaya IQ. The actual number of sources will be determined using the Implementation Planning Tool plus other sizing factors. Avaya IQ supports a lower number of data sources for an All Functions with Remote Data Collection deployment compared to a Multiple Host deployment. Most of these items will have been done when the system was originally installed. • Proper administration of contact center data collection features. but these must verified before attempting Preparing for Avaya IQ Implementation November 2011 57 . Proactive Contact software setup requirements The following is a list of setup and administrative requirements for any Proactive Contact system that is a source for Avaya IQ. Communication Manager software setup requirements The following is a list of setup and administrative requirements for any Communication Manager system that is a source for Avaya IQ.One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Communication Manager systems. Note: Avaya IQ 5. • The NTP time synchronization service must be synchronized from the same NTP source as all hosts. verified during implementation. Communication Manager systems. Note: In general. Product software cannot be installed without the presence of a functioning time synchronization service.

and Proactive Contact systems in the deployment. • Routing Points (VDNs) and queues (skills) used by the Communication Manager system for the Proactive Contact system must be measured in both directions. Contact Avaya or Business Partner support to verify that the Proactive Contact system is administered properly. Note that the only two job types (queues) that are currently supported are outbound and managed. • An ASAI (also known as CTI) link must be set up between the Proactive Contact system and its associated Communication Manager system. • You may associate one Proactive Contact system with a single Communication Manager system. You cannot associate a Proactive Contact system to more than one Communication Manager system.com November 2011 . • The Proactive Contact system must be administered for blended agents. you must administer the link between the systems in either non-encrypted or encrypted mode. • Depending on the Avaya IQ release and the Proactive Contact release. One exception to this rule is that a remote Data Collection host can use the same NTP source as its associated Proactive Contact system. These procedures are documented in Proactive Contact link administration on page 119. • The NTP time synchronization service must be synchronized from the same NTP source as all hosts. 58 Preparing for Avaya IQ Implementation Comments? infodev@avaya.Setting up data sources to install Avaya IQ. Communication Manager systems. Product software cannot be installed without the presence of a functioning time synchronization service.

• Confirm connectivity between the reporting software and database.43.rpm Preparing for Avaya IQ Implementation November 2011 59 . or using an input file that contains the required test input answers. and database host is operating normally. Avaya distributes CAT as an RPM package.x86_64. As a result of these tests.15–22. • Confirm connectivity between the application hosts.Chapter 7: Using the Configuration Audit Tool After you install the operating system and Oracle environment on the application hosts. you must run the installation audit test and all tests must pass before you install Avaya IQ. you must run the Configuration Audit Tool (CAT) to test the application hosts and ensure that the operating system and Oracle environment is set up properly. Note: Do not install CAT on the database host. ensure the following additional RPM packages are installed.1.4. CAT creates a file that contains database user names and connection strings that are used during implementation. • Confirm on which application host you are running the CAT tool. • Test connectivity between the application hosts and the database host. • Confirm the maximum number of historical database processes.rpm • expect-5. You can install higher versions if available: • tcl-32bit-8.i386. At a minimum. Before you install CAT. You must install CAT manually on each application host and copy the RPM from the software installation DVD or download the CAT zip file from the product download Web site. Avaya recommends that you check the version on the installation DVD and the Web site and use the most up-to-date version for your release of Avaya IQ. group of tests. You can run individual tests. These are minimum required versions.0–5. You can use CAT to do the following tasks: • Confirm that the application hosts meet the minimum hardware and software requirements to install the Avaya IQ software properly. • Confirm that the users added to the database are administered with the proper privileges. proper character sets are administered. • Confirm that the database host is installed with the correct Oracle software.

Click Download Center.com November 2011 . Go to the Avaya Support Web site at http://support. 60 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Procedure 1.avaya. Downloading the Configuration Audit Tool Before you begin You must have a computer that has SSH copy access to the application hosts. The system downloads the ZIP file to your computer.com. Click Log In. Next steps Perform the following steps after you download the ZIP file on to your computer: 1. The system displays the Avaya SSO Login page. 7. Note: If you are not registered. Click Download My Software. In the Log In box. The system displays the Online Service Manager page. Unzip the package of files onto your computer. 6. Click Download. The system displays the IQ: Download Center page. enter your user name and password in the Login ID and Password fields respectively. Under I. Copy the files from your computer to the /avaya or /tmp directory on every application host in your deployment. 2. 4. 8. Click the latest version of the Configuration Audit Tool.Using the Configuration Audit Tool You can find these RPMs in the CAT zip file. The system displays the Download Center page. register your installation using your Sold To number. 3. 5. click IQ. 2.

Log on as root. Go to the directory where you have copied the RPM files. 4.x86_64. 3.164.Copying the Configuration Audit Tool package from the installation DVD Copying the Configuration Audit Tool package from the installation DVD Procedure 1. Installing the Configuration Audit Tool Procedure 1. Note: You must run the Configuration Audit Tool for each application host. The system unpacks and installs CAT RPM in the /opt/Avaya/CCR/util/CAT directory.rpm Insert the actual version numbers in place of the * variable. <CAT_Package> indicates the name of the CAT package. Insert the installation DVD into your application host disc drive. Repeat this procedure for each application host in your deployment. Enter the following commands: mount /dev/cdrom /mnt cd /mnt cp <CAT_Package> /tmp/ Where. Preparing for Avaya IQ Implementation November 2011 61 . Log on to the operating system as root or a user with root-level privileges. 3.rpm rpm —Uvh Avaya-CAT-*. Enter the following commands in each of the Avaya IQ hosts: rpm —Uvh tcl-*.rpm rpm —Uvh expect-*. 2. 2.x386_64.

/cat.sh: Takes the default file path that is /opt/Avaya/CCR/ipt • .com November 2011 . the system displays a message when you run the commands.Using the Configuration Audit Tool Note: If the RPMs are already installed on the hosts. Enter cd /opt/Avaya/CCR/util/CAT 4. CAT uses this file to verify some of the following components: • RAM • CPU speed • CPU cores (total number of CPU cores) 62 Preparing for Avaya IQ Implementation Comments? infodev@avaya.sh --iptfile=no: Runs CAT with default values and without the IPT file IPT enables you to create a design by providing valid inputs and an output XML file. Copy the IPT output XML file to the /opt/Avaya/CCR/ipt directory./cat. If you copy the XML file to any other location. 3./cat.sh --iptfile=<filepath>: Locates the IPT file that you provide in the <filepath> variable • . Enter one of the following commands based on the Implementation Planning Tool (IPT) output XML file location: • . Checking the CAT version Procedure Run the following command to check the CAT version: rpm -q Avaya-CAT Running the Configuration Audit Tool Procedure 1. you must provide the correct path when you run CAT. Log on to the operating system as root or a user with root-level privileges. 2.

Preparing for Avaya IQ Implementation November 2011 63 . the Configuration Audit Tool displays the following tests and descriptions: 1. LocalHost_Verify: Verifies that the _ (underscore) is not available in the local host name and it is reachable. you can find the tests and descriptions for each application host. 3.Uninstalling the Configuration Audit Tool For more information. Umask: Confirms the Umask requirement. when you select the Individual_Audit option for the All Functions host. the Configuration Audit Tool displays tests and descriptions. OS_Version: Confirms that the operating system version meets the minimum requirement. For example. In this section. the system retains all testing result directories in the /opt/Avaya/CCR/util/CAT directory. 2. the Configuration Audit Tool displays the tests and descriptions specific to that host. 4. Your version of the Configuration Audit Tool can have more or fewer tests. Uninstalling the Configuration Audit Tool Procedure Enter rpm -e Avaya-CAT The system uninstalls the Configuration Audit Tool. You can find the Readme file locations as noted in these tests in the /opt/Avaya/CCR/util/CAT directory. RAM: Confirms that the system memory (RAM) meets the minimum requirement. Test descriptions When you select the Individual_Audit option for an application host. see Planning Avaya IQ Designs document. All Functions host When you select the Individual_Audit option for the All Functions host. Note: Even if you uninstall the Configuration Audit Tool.

RT_DBRW_Connectivity: Confirms the read and write connectivity between the Avaya IQ software and the historical data store.com November 2011 . 6. RT_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the real-time data store. DNS: Verifies the Domain System Name (DNS). 11. RT_DBRO_Connectivity: Confirms the read-only connectivity between the Avaya IQ software and the historical data store. RUI_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the reporting user interface data store. 16. CPU_Cores: Confirms that the CPU cores meet the minimum requirement. 20. 7. CSC_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the content data store. 26. 22. 12. NTPSync: Verifies the Network Time Protocol (NTP) synchronization. 19. CPU_Speed: Confirms that the CPU speed meets the minimum requirement. 25. 14.Using the Configuration Audit Tool 5. Root_Disk_Space: Confirms that the / minimum free disk space is met. SDS_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the system data store. Hist_DBRW_Connectivity: Confirms the read and write connectivity between the Avaya IQ software and the historical data store. 64 Preparing for Avaya IQ Implementation Comments? infodev@avaya. 9. 13. Loopback: Confirms that the local host and the loop back values are available in the /etc/hosts directory. RT_DB_Ora: Checks for the real time database init script. 17. Hist_DBRO_Connectivity: Confirms the read-only connectivity between the Avaya IQ software and the historical data store. Hist_DB_Ora: Checks for the historical database init script. 8. 10. 15. Opt_Disk_Space: Confirms that there is enough free disk space in the /opt directory. 23. 21. Hist_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the historical data store. Tmp_Disk_Space: Confirms that there is enough free disk space in the /tmp directory. OjdbcPerm: Confirms that the proper permissions exist on the/ojdbc directory. 18. 24. Var_Disk_Space: Confirms that there is enough free disk space in the /var directory. TmpPerm: Confirms that the proper permissions exist on the/tmp directory.

You can find the results of this test in the $CAT_HOME\TimeStamp\rpmDependency.Test descriptions 27. 32.RPMs that conflict with the installation. tomcat >= 3. administration host. Hist_DB_User_Privs: Confirms the user privileges for the historical database.RPMs that you must install. 30. • The second section of the file shows all RPMs that are required for Avaya IQ. 33. You can use this test to troubleshoot these operational issues. For example. RT_DB_Char_Set: Confirms the character set for the real-time database. Hist_DBRW_User_Privs: Confirms the read and write user privileges for the historical database. Connectivity: Confirms SSH network connectivity to hosts that are required when running the command.00-67. It also identifies which RPMs can conflict the Avaya IQ installation and must not be installed.2 conflicts with ccrStub-05. 29. . 35.01.3. The output of this test is shown in two sections: • The first section of the output file shows: . Hist_DB_Version: Confirms the Oracle version of the historical database. 36. You can find the results of this test in the $CAT_HOME\TimeStamp\manifest. For example. RPMs: Confirms that the dependent RPM packages are installed. Manifest: Confirms a successful installation of the Avaya IQ software. Hist_DB_Char_Set: Confirms the character set for the historical database. you must install that exact version.0.01.x86_64 If the RPM is shown with >= (greater than or equal to). you can install that version or a more recent version.out file. 31. This test checks the installed Avaya IQ files against a known baseline. and data sources. NICSettings: Verifies the Network Interface Card (NIC) settings on the application host. Network_Information: Displays network interface information for the application host. perl-XML-NamespaceSupport >= 1.1 is needed by ccrStub-05.out file. 28. Preparing for Avaya IQ Implementation November 2011 65 . RT_DB_Version: Confirms the Oracle version of the real-time database.0.x86_64 You must remove these RPMs before installing Avaya IQ.00-119. 37. If the RPM is shown with = (equal to). 34.2.09-1. The test must be run before adding license.

RT_DB_User_Privs:Confirms the user privileges for the real-time database. Hist_DB_DIM_Table_Space: Confirms the historical database user privileges in the historical dimensional tablespaces. The system displays both the required version and the actual version. You must know the account user name. 44. You must know the historical dimensional tablespaces names to run this test. RT_DBRO_User_Privs: Confirms the read-only user privileges for the real-time database. and server name or IP address for the system to display the version information. The system displays both the required version and the actual version. RT_DBRW_User_Privs: Confirms the read and write user privileges for the realtime database. You must know the server name or IP address for the system to 66 Preparing for Avaya IQ Implementation Comments? infodev@avaya. 50. password. Hist_DB_Cursors: Confirms the open cursors in the historical database. RT_DB_Cursors: Confirms the open cursors in the real-time database. VPVersion: Displays version information for any connected Voice Portal systems. 40. Hist_DB_Procs: Confirms the minimum number of historical database processes. 43. 46. 41. Realtime_DB_Temp_Table_Space: Confirms the size of the realtime database temp tablespace. 49. SNMP: Displays the required RPMs to use the SNMP feature and the actual version of the RPMs that are installed. ReportingConn: Confirms connectivity to the Reporting software. 42. Hist_DB_Fact_Table_Space: Confirms the historical database user privileges in the fact dimensional tablespaces. and server name or IP address for the system to display the version information. Realtime_DB_Undo_Table_Space: Confirms the size of the realtime database undo tablespace 51. 53. CMVersion: Displays version information for any connected Communication Manager systems.Using the Configuration Audit Tool 38. 39. Hist_DBRO_User_Privs: Confirms the read-only user privileges for the historical database. PCVersion: Displays version information for any connected Proactive Contact systems. You must know the historical index tablespace names to run this test. You must know the historical fact tablespace names to run this test. 48. 45. password. 47. 52. 54.com November 2011 . Hist_DB_Index_Table_Space: Confirms the historical database user privileges in the index dimensional tablespaces. You must know the account user name.

The system displays both the required version and the actual version. 20) Hist_DBRW_Connectivity: Confirms the read and write connectivity between the Avaya IQ software and the historical data store. 3) Umask: Confirms the Umask requirement. 6) NTPSync: Verifies the Network Time Protocol (NTP) synchronization. 8) CPU_Speed: Confirms that the CPU speed meets the minimum requirement.Test descriptions display the version information. 17) Hist_DB_Ora: Checks for the historical database init script. the Configuration Audit Tool displays the following tests and descriptions: 1) OS_Version: Confirms that the operating system version meets the minimum requirement. Preparing for Avaya IQ Implementation November 2011 67 . 19) Hist_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the historical data store. 5) DNS: Verifies the Domain System Name (DNS). 10) Root_Dsk_Space: Confirms that the / minimum free disk space is met. 2) RAM: Confirms that the system memory (RAM) meets the minimum requirement. 4) LocalHost_Verify: Verifies that the _ (underscore) is not available in the local host name and it is reachable. 18) RT_DB_Ora: Checks for the real time database init script. 12) Tmp_Disk_Space: Confirms that there is enough free disk space in the /tmp directory. 9) CPU_Cores: Confirms that the CPU cores meet the minimum requirement. 15) TmpPerm: Confirms that the proper permissions exist on the/tmp directory. 16) OjdbcPerm: Confirms that the proper permissions exist on the/ojdbc directory. 14) U01_Disk_Space: Confirms that there is enough free disk space in the /u01 directory. 13) Var_Disk_Space: Confirms that there is enough free disk space in the /var directory. 11) Opt_Disk_Space: Confirms that there is enough free disk space in the /opt directory. Administration host When you run the Individual_Audit command for the Administration host. 7) Loopback: Confirms that the local host and the loop back values are available in the /etc/ hosts directory.

RPMs that you must install. For example. 24) RT_DBRO_Connectivity: Confirms the read-only connectivity between the Avaya IQ software and the historical data store.Using the Configuration Audit Tool 21) Hist_DBRO_Connectivity: Confirms the read-only connectivity between the Avaya IQ software and the historical data store.x86_64 You must remove these RPMs before installing Avaya IQ.01.2.2 conflicts with ccrStub-05. This test checks the installed Avaya IQ files against a known baseline.0. 31) RPMs: Confirms that the dependent RPM packages are installed. . You can use this test to troubleshoot these operational issues.0. you can install that version or a more recent version. You can find the results of this test in the TimeStamp\result. 22) RT_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the realtime data store. tomcat >= 3.1 is needed by ccrStub-05. • The second section of the file shows all RPMs that are required for Avaya IQ.RPMs that conflict with the installation. 28) Network_Information: Displays network interface information for the application host.01. The output of this test is shown in two sections: • The first section of the output file shows: . 27) RUI_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the reporting user interface data store. you must install that exact version.3. At initial installation. You can find the results of this test in the TimeStamp\rpmDependency. you can see differences that affect the operation of the software.x86_64 If the RPM is shown with >= (greater than or equal to).00-67.00-119. 23) RT_DBRW_Connectivity: Confirms the read and write connectivity between the Avaya IQ software and the historical data store. If the RPM is shown with = (equal to).out file. 25) SDS_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the system data store. 68 Preparing for Avaya IQ Implementation Comments? infodev@avaya. 30) Manifest: Confirms a successful installation of the Avaya IQ software. 29) NICSettings: Verifies the Network Interface Card (NIC) settings on the application host. during operation when files are changed.com November 2011 .09-1. 26) CSC_DB_Connectivity: Confirms connectivity between the Avaya IQ software and the content data store. However.out file. perl-XML-NamespaceSupport >= 1. For example. you must see no differences.

50) SNMP: Displays the required RPMs to use the SNMP feature and the actual version of the RPMs that are installed. 44) Hist_DB_Cursors: Confirms the open cursors in the historical database. You must know the historical index tablespace names to run this test. 46) ReportingConn: Confirms connectivity to the Reporting software. 33) Hist_DB_Version: Confirms the Oracle version of the historical database. You must know the historical fact tablespace names to run this test. 36) RT_DB_Char_Set: Confirms the character set for the real-time database. 47) Hist_DB_DIM_Table_Space: Confirms the historical database user privileges in the historical dimensional tablespaces. 42) RT_DBRO_User_Privs: Confirms the read-only user privileges for the real-time database. You must know the historical dimensional tablespaces names to run this test. 38) Hist_DBRW_User_Privs: Confirms the read and write user privileges for the historical database. 35) Hist_DB_Char_Set: Confirms the character set for the historical database. 43) Hist_DB_Procs: Confirms the minimum number of historical database processes.Test descriptions 32) Connectivity: Confirms SSH network connectivity to hosts that are required when running the command. 37) Hist_DB_User_Privs: Confirms the user privileges for the historical database. Preparing for Avaya IQ Implementation November 2011 69 . 49) Hist_DB_Index_Table_Space: Confirms the historical database user privileges in the index dimensional tablespaces. 39) Hist_DBRO_User_Privs: Confirms the read-only user privileges for the historical database. 41) RT_DBRW_User_Privs: Confirms the read and write user privileges for the real-time database. 48) Hist_DB_Fact_Table_Space: Confirms the historical database user privileges in the fact dimensional tablespaces. 34) RT_DB_Version: Confirms the Oracle version of the real-time database. 40) RT_DB_User_Privs: Confirms the user privileges for the real-time database. 45) RT_DB_Cursors: Confirms the open cursors in the real-time database.

2) RAM: Confirms that the system memory (RAM) meets the minimum requirement. 15) TmpPerm: Confirms that the proper permissions exist on the/tmp directory. 10) Root_Disk_Space: Confirms that the / minimum free disk space is met.out file. 9) CPU_Cores: Confirms that the CPU cores meet the minimum requirement. 17) Network_Information: Displays network interface information for the application host.com November 2011 . You can find the results of this test in the TimeStamp\result. 12) Tmp_Disk_Space: Confirms that there is enough free disk space in the /tmp directory.Using the Configuration Audit Tool Reporting host When you run the Individual_Audit command for the Reporting host. 16) OjdbcPerm: Confirms that the proper permissions exist on the/ojdbc directory. the Configuration Audit Tool displays the following tests and descriptions: 1) OS_Version: Confirms that the operating system version meets the minimum requirement. during operation when files are changed. This test checks the installed Avaya IQ files against a known baseline. 5) DNS: Verifies the Domain System Name (DNS). 8) CPU_Speed: Confirms that the CPU speed meets the minimum requirement. you can see differences that affect the operation of the software. 11) Opt_Disk_Space: Confirms that there is enough free disk space in the /opt directory. However. You can use this test to troubleshoot these operational issues. 7) Loopback: Confirms that the local host and the loop back values are available in the /etc/ hosts directory. 6) NTPSync: Verifies the Network Time Protocol (NTP) synchronization. you must see no differences. 4) LocalHost_Verify: Verifies that the _ (underscore) is not available in the local host name and it is reachable. At initial installation. 18) NICSettings: Verifies the Network Interface Card (NIC) settings on the application host. 13) Var_Disk_Space: Confirms that there is enough free disk space in the /var directory. 70 Preparing for Avaya IQ Implementation Comments? infodev@avaya. 14) U01_Disk_Space: Confirms that there is enough free disk space in the /u01 directory. 3) Umask: Confirms the Umask requirement. 19) Manifest: Confirms a successful installation of the Avaya IQ software.

0.01. perl-XML-NamespaceSupport >= 1.2. you must install that exact version.0.2 conflicts with ccrStub-05. Data Processing or Data Collection host When you run the Individual_Audit command for the Data Processing or Data Collection host.09-1. If the RPM is shown with = (equal to).01.x86_64 If the RPM is shown with >= (greater than or equal to). 22) Hist_DB_Version: Confirms the Oracle version of the historical database. tomcat >= 3. 23) RT_DB_Version: Confirms the Oracle version of the real-time database. 4) LocalHost_Verify: Verifies that the _ (underscore) is not available in the local host name and it is reachable. 25) SNMP: Displays the required RPMs to use the SNMP feature and the actual version of the RPMs that are installed.RPMs that conflict with the installation. .x86_64 You must remove these RPMs before installing Avaya IQ. you can install that version or a more recent version.RPMs that you must install. The output of this test is shown in two sections: • The first section of the output file shows: . 3) Umask: Confirms the Umask requirement. • The second section of the file shows all RPMs that are required for Avaya IQ. For example.out file.3. 5) DNS: Verifies the Domain System Name (DNS).1 is needed by ccrStub-05. 24) ReportingConn: Confirms connectivity to the Reporting software. You can find the results of this test in the TimeStamp\rpmDependency.00-119. the Configuration Audit Tool displays the following tests and descriptions: 1) OS_Version: Confirms that the operating system version meets the minimum requirement. 2) RAM: Confirms that the system memory (RAM) meets the minimum requirement. Preparing for Avaya IQ Implementation November 2011 71 . For example.00-67.Test descriptions 20) RPMs: Confirms that the dependent RPM packages are installed. 21) Connectivity: Confirms SSH network connectivity to hosts that are required when running the command.

For example. during operation when files are changed.01. 12) Tmp_Disk_Space: Confirms that there is enough free disk space in the /tmp directory. 72 Preparing for Avaya IQ Implementation Comments? infodev@avaya.0. 17) Manifest: Confirms a successful installation of the Avaya IQ software. 9) CPU_Cores: Confirms that the CPU cores meet the minimum requirement. You can find the results of this test in the TimeStamp\rpmDependency.3.x86_64 You must remove these RPMs before installing Avaya IQ. You can use this test to troubleshoot these operational issues. However. . 16) NICSettings: Verifies the Network Interface Card (NIC) settings on the application host. You can find the results of this test in the TimeStamp\result. 15) Network_Information: Displays network interface information for the application host.x86_64 If the RPM is shown with >= (greater than or equal to).RPMs that you must install. 8) CPU_Speed: Confirms that the CPU speed meets the minimum requirement.out file.01.RPMs that conflict with the installation.2. you can install that version or a more recent version. 14) TmpPerm: Confirms that the proper permissions exist on the/tmp directory. perl-XML-NamespaceSupport >= 1. If the RPM is shown with = (equal to). you must see no differences. At initial installation.0.00-119.out file. • The second section of the file shows all RPMs that are required for Avaya IQ.09-1. 11) Opt_Disk_Space: Confirms that there is enough free disk space in the /opt directory. The output of this test is shown in two sections: • The first section of the output file shows: . 18) RPMs: Confirms that the dependent RPM packages are installed.com November 2011 . This test checks the installed Avaya IQ files against a known baseline. tomcat >= 3. 10) Root_Disk_Space: Confirms that the / minimum free disk space is met.1 is needed by ccrStub-05. you must install that exact version. 7) Loopback: Confirms that the local host and the loop back values are available in the /etc/ hosts directory. For example.00-67. 19) Connectivity: Confirms SSH network connectivity to hosts that are required when running the command. you can see differences that affect the operation of the software. 13) Var_Disk_Space: Confirms that there is enough free disk space in the /var directory.Using the Configuration Audit Tool 6) NTPSync: Verifies the Network Time Protocol (NTP) synchronization.2 conflicts with ccrStub-05.

supporting application audit. CAT validates the database information before validating the test. You must know the server name or IP address for the system to display the version information. • Port number: Indicates the listener port number that is used to communicate between the Avaya IQ software and the database. You must use the following information when running the database tests: • Configuration Audit Tool user and password: Verifies the privileges of all Avaya IQ users. 22) SNMP: Displays the required RPMs to use the SNMP feature and the actual version of the RPMs that are installed. see Creating a Net Service Name in Preparing for Avaya IQ Implementation guide. • Database service name: Indicates the Oracle Service Name that is administered in the tnsnames. 21) VPVersion: Displays version information for any connected Voice Portal systems. It can be either a single instance or a Real Application Clusters (RAC) instance. or individual audit database tests. The system displays both the required version and the actual version. password. • Database server type: Indicates the type of the database that is installed. Information required to run database tests When you run an installation audit. • Host name or IP address: Indicates the database host name or IP address. and server name or IP address for the system to display the version information. You must know the account user name. You can collect most of this information when the customers set up their database users and tablespaces. This validation process ensures that the Avaya IQ software is installed successfully. and server name or IP address for the system to display the version information. • Database user names and passwords: Indicate the user names and passwords assigned to each of the data stores. see Creating database users and applying permissions in Preparing for Avaya IQ Implementation guide. password. For more information. See Appendix B: Customer information worksheets and reuse any information collected by the customer. For more information. The system displays both the required version and the actual version. you must provide information about the database connections to complete the tests. and so on. The system displays both the required version and the actual version.ora file. You must know the account user name. historical.Information required to run database tests 20) PCVersion: Displays version information for any connected Proactive Contact systems. Preparing for Avaya IQ Implementation November 2011 73 . As you run each of these tests. 23) CMVersion: Displays version information for any connected Communication Manager systems. real-time.

see Creating a Net Service Name in Preparing for Avaya IQ Implementation guide. • dba. • Oracle OS user ID: Indicates the Oracle user ID that is used to log on to the database server. It does not include passwords associated with these connection strings.out: Confirms successful installation of the Avaya IQ software. and install any missing RPMs before you continue with the installation process. • TNS Name: Indicates the Oracle Net Service Name that is administered in the tnsnames. For more information. • timestamp/manifestOutput.out: Contains the most recent results of an installation audit. and RPMs that are missing from the installation. • Oracle client OS user ID: Indicates the Oracle user ID that is used to log on to each application host. • hostinfo.out: Contains the host type for installing the Avaya IQ software. • TimeStamp/result.out: Contains information about the RPMs that conflict with the installation. This file enables the system to automatically populate user names or connection strings while installing the software. This file contains differences against a known baseline.com November 2011 . 74 Preparing for Avaya IQ Implementation Comments? infodev@avaya.out: Is accessible by the Avaya IQ installation program. This file is accessible by the Avaya IQ installation program and it automatically determines the host type that must be run.Using the Configuration Audit Tool • Historical or Real Time database user name to check: Indicates the historical or real-time database user name that is required to check privilege assignments.. You must manually enter the passwords when using the installation program. • Dimensional Tablespace Name: • Fact Tablespace Name: • Index Tablespace Name: Test result files The system saves the following test results in several files in the sub folders of the /opt/ Avaya/CCR/util/CAT directory: • connection. You must remove the RPMs that conflict with the installation.out: Contains every set of test results for every test session.ora file.out: Contains the results of the database components. • TimeStamp/rpmDependency. • install.

recheck your values and run the installation audit again before you exit CAT. 6. database connection string tests.sh: Takes the default file path that is /opt/Avaya/CCR/ipt • . database version tests. During an installation audit. Procedure 1. Preparing for Avaya IQ Implementation November 2011 75 . Enter one of the following commands based on the Implementation Planning Tool (IPT) output XML file location: • . CAT runs the host application tests. The installation audit begins by running tests on the application host. Select Installation_Audit from the CAT main menu. When prompted. then the customer must provide this information. you must perform the following tasks: • Run an installation audit test on every application host. • Ensure that all installation audit tests pass to install the software successfully. you must answer questions for the database connection strings that failed. and Reporting user interface connection tests. enter the database connection information for each of the data stores used with the database.sh --iptfile=<filepath>: Locates the IPT file that you provide in the <filepath> variable • ./cat.Running an installation audit Running an installation audit About this task Before you install the Avaya IQ software. character set tests. select q to exit CAT.sh --iptfile=no: Runs CAT with default values and without the IPT file 3. 4./cat. Correct any failed items and run the installation audit until all the tests pass./cat. Important: If you run the installation audit again without leaving the main menu. You can find most of this information in the Database host worksheets on page 87. Enter cd /opt/Avaya/CCR/util/CAT 2. 5. If this information is not readily available. If any of the database connection strings fail. It saves your time in running the tests. When finished with testing.

During the supporting application audit. database initialization tests. 7.sh --iptfile=no: Runs CAT with default values and without the IPT file 3. 5. Select q to exit CAT. NIC verification tests. Correct any failures and run the audit until the test passes. Procedure 1. Select a test to run and answer any prompts. 6.sh: Takes the default file path that is /opt/Avaya/CCR/ipt • . Enter cd /opt/Avaya/CCR/util/CAT 2. SSH network connectivity tests./cat. Select Supporting_Application_Audit from the CAT main menu./cat. 76 Preparing for Avaya IQ Implementation Comments? infodev@avaya. and third party software version tests. Select b to return to the main menu after CAT finishes the tests. The supporting application audit begins by running tests on the application host./cat. Running an individual audit About this task You can run individual audit tests to troubleshoot the tests that are failing. NTP synchronization tests. 4.Using the Configuration Audit Tool Running a supporting application audit About this task You can run a supporting application audit on an application host to check if the third party software versions and network settings are correct.com November 2011 . CAT runs the DNS tests.sh --iptfile=<filepath>: Locates the IPT file that you provide in the <filepath> variable • . as it saves time when correcting host or database test failures. Enter one of the following commands based on the Implementation Planning Tool (IPT) output XML file location: • .

Select b to return to the main menu after CAT finishes the tests. Procedure 1./cat. Important: CAT overwrites the .input file every time you run a test. Enter cd /opt/Avaya/CCR/util/CAT. Enter cd /opt/Avaya/CCR/util/CAT 2. Enter one of the following commands based on the Implementation Planning Tool (IPT) output XML file location: Preparing for Avaya IQ Implementation November 2011 77 . You can use these saved responses to build input files that emulate running tests manually. CAT displays the list of individual tests. see the Sample input file on page 78 that runs the historical database connectivity test. 2. You can use the input file to run a test repeatedly and determine the correct options without providing the same answers repeatedly. Correct any failures and run the audit until the test passes. 5.sh: Takes the default file path that is /opt/Avaya/CCR/ipt • .input file. 4. The input file contains answers to one or more tests.input file. save a copy of the file so you can edit the responses and adjust the options for any failed tests./cat. Select q to exit CAT.sh --iptfile=<filepath>: Locates the IPT file that you provide in the <filepath> variable • . If you want to save the responses in the .Running tests using an input file Procedure 1. Select a test to run and answer any prompts. Running tests using an input file About this task Every time you run a test. 6. Select Individual_Audit from the CAT main menu.sh --iptfile=no: Runs CAT with default values and without the IPT file 3. CAT saves the keystrokes that contain your test responses in the . Enter one of the following commands based on the Implementation Planning Tool (IPT) output XML file location: • . For more information. 7./cat.

sh: Takes the default file path that is /opt/Avaya/CCR/ipt • .out file. 7.sh --iptfile=no --responseFile=InputFile • . Save the . 8. 4. Check the output of the test in the TimeStamp/result. Note: You must replace **** with the password of your choice./cat. 5.sh --iptfile=<filepath> --responseFile=InputFile Note: You must use the same command that you used in step 2. Edit the saved file.input InputFile. such as an installation audit. # Select main menu(host selection) 1 78 Preparing for Avaya IQ Implementation Comments? infodev@avaya.Using the Configuration Audit Tool • ./cat. Enter one of the following commands: • .input file to another file. Related topics: Sample input file on page 78 Sample input file This is an example of an input file that runs the individual test number 8 and historical database connectivity test. 6. You can add comments to the file as shown in this example./cat. For example. Exit CAT. The tool writes the test results to the screen as if you ran the test manually.sh --iptfile=no: Runs CAT with default values and without the IPT file 3. The blank lines are also valid input commands./cat. Run a test manually. You can change responses as needed to make the tests pass. so do not leave any blank lines unless required by the test.sh --iptfile=<filepath>: Locates the IPT file that you provide in the <filepath> variable • .com November 2011 ./cat. answer the questions as you go through the test. CAT runs the test using the InputFile file./cat. then the test fails.sh --responseFile=InputFile • . If you choose a different command at this step. cp .

iqbeta.com #Pressing Enter to continue #Exit CAT q Related topics: Running tests using an input file on page 77 Preparing for Avaya IQ Implementation November 2011 79 .apac.com 1521 ccr.avaya.avaya.Sample input file # Select Individual Audit(group selection) test 3 1 # Select individual test 19 RPT_HIST_OWNER_USR xxxx<password> 1 iqbeta.apac.

com November 2011 .Using the Configuration Audit Tool 80 Preparing for Avaya IQ Implementation Comments? infodev@avaya.

3.1-AV5 1.3 0.1 2.6 2.0.50 0.0.6 LGPL Sun Microsystems Apache Software License Apache Software License GPL Preparing for Avaya IQ Implementation November 2011 81 . Package name activemq ant ant apr apr-util axis commons-daemon distcache EJBCA httpd httpd-suexec jboss jre mod_jk (aka apachetomcat-integration) mod_ssl mon Version 4.4.5 1.99.52-28.net Red Hat Red Hat Red Hat Sun Apache Red Hat Kernel. 1.2.4-21 1.5.org License type and text Apache Software License Apache Software License Original vendor CodeHaus Apache 2.9.3SP1 1_5_0_15 1.0.4-AV7 1.9.sourceforge.2.0.0.ent.Appendix A: Distributed third-party software This section provides the following information about third-party software for the software-only and turnkey deployments and third-party jars and libraries for the software-only deployment.0.AV2 Apache Software License 4.4.1 1.6.50 Apache Software License Apache Software License Apache Software License Apache Software License LGPL LGPL Apache Software License Red Hat Red Hat Apache Apache Red Hat http:// ejbca.5 0.4-24.5.5-6 3.

2 1.31_1.0 Sun Software License Agreement CDDL v1.51 1.4 2.0 OEM LGPL Apache v1.1 Apache v2.2.1.0 LGPL Sun Community Source License Apache License v2.0 Apache License v2.klake.9-AV7 1.0 Apache License v2.5.3 1.5 1.com Sun SourceForge Sam Stephenson 82 Preparing for Avaya IQ Implementation Comments? infodev@avaya.0 LGPL v2.1 1.0 LGPL Prototype license Cognos SourceForge SourceForge SourceForge Focus Red Hat Apache Apache Apache Apache Sun Sun SourceForge Sun SourceForge Dynarch.6.3 1.1 1.3.5.8 1.0 Apache Acegi Technology Exadel Common Public License Eclipse v1.0 2.1 1.0 OEM Artistic License BSD Apache v2.02-0 20040325 5.1.org http://www.5 1.0.3_01 2.com November 2011 .3 8.0 1.org/~jt/sscep/ Apache Software License Apache License v2.1 1.0 CDDL v1. Tobin.1 1.0 2.5.0.Distributed third-party software Package name perl-gnupg SSCEP tomcat Acegi Ajax4jsf Apache MyFaces JSF library Apache Tomahawk AspectJ Cognos displaytag Dom4j Ehcache Focus Report Central Hibernate Jakarta Oro Jakarta Velocity jakarta-commons jakarta-taglibs javamail JAX-WS Jericho JMX Remote API joda time jscalendar JSTL jtds Prototype Javascript Framework Version 0.6 1. ftobin@cpan.1.1 License type and text Artistic License Original vendor Frank J.6.4 1.1 Apache v2.0.2 1.4 Tomcat 5.2 3.2.

jsf-impl.8.5. asm.jar.1 3.2 1. saaj.jar.jar.1.jar.2.9 2.3 1.6.1. ant-antlr-1. wsdl4j-1.1 Apache License v2.3. ehcache-1.2. xml-sec.jar User Mgt RBAC "hibernate3.7.jar.5.0 Apache v1. All Core Services use the same version of the Jars.2 3 Version Original vendor Apache Sun OpenSymphony OpenSymphony knopflerfish Apache Apache hibernate Scheduler Preparing for Avaya IQ Implementation November 2011 83 .jar jaxrpc.2.3. c3p0-0.1 Apache v1. jdbc2_0-stdext.jar.1 2.6. axis-ant.us Javascript Library Spring Framework Struts Struts Menu XMLBeans Xstream 1.5H3. jta.jar.6.jar 1.jar xml-apis.jar quartz.Third-party jars and libraries Package name Prototype Window Javascript Library Quartz Script. dom4j-1.aculo.1.2.2.5.2 Version License type and text MIT-style license Apache v2.jar.jar.jar. antlr-2. proxool-0.2.jar sitemesh-2.jar.1.jar.5 1.jar.jar jsf-api.4.jar.jar.6.jar.jar.1.jar. asmattrs. standard.jar.1. cglib-2.6 1.5.6.2.0 1.2 1.jar.8.1 2. Module using jar or library All Core Services Modules Jar or library axis.1 1. jaxen-1.jar framework.1. jsftest.1 1.0 BSD Original vendor Sébastien Gruhier OpenSymphony Thomas Fuchs Springframework.jar xerces-2.1beta-4. jstl.0 MIT license Apache License v2.6 2.org Apache Apache Apache CodeHaus Third-party jars and libraries Note: The Jars or libraries listed in this table are common among all Core Services.

3.so.jar .Distributed third-party software Module using jar or library User Mgt RBAC Jar or library "Hibernate3.1 1.jar. commons-el.com November 2011 . commonsbeanutils-core-1.jar.5. activemqoptional-3.jar.jar ocrs12.jar activation.1-407.7.9 5.2. Scheduler "activemq-core-3.1 junit-3.4.4.6.jar jasper-compiler.0.2 10. commonslogging-1. concurrent-1.6 2. commonsdbcp-1.0.0.0.5.jar Logging cppunit-1.jar.0rc4.1rc4.1.10.jar 5.2.jar.4.0.9 5.6.jar orai18n.0. RBAC.jar servlet-api.0 8.jar.4.9 5. geronimo-spec-jms-1.1.10.jar.3.4.1 3.1.jar. commonsdiscovery-0.jar ojdbc14. various commons-beanutils-beanversions collections-1.2.jar libACE.2.0.jar jasper-runtime. geronimospec-j2ee-management-1.jar postgresql-8.0.1-407 1.jar OAM struts-1.1 3.0.2.jar.4.jar. commonsdigester-1.7.knoperfish OSGi xalan-2.jar.0.jar.1.1 1.0.1 10.7.2 1.4.0 10.0 1.hibernate .2 doxytag doxygen LCM framework.1.jar 3 commons-beanutils-1.4 Apache Apache Apache Apache Apache Apache Apache ACE apache source forge apache apache oracle oracle oracle redhat 84 Preparing for Avaya IQ Implementation Comments? infodev@avaya.5.org/ CodeHaus User Mgt.jar.5.jar jakarta-oro. commons-poolcommons-logging-api.6.8.2 Version Original vendor http:// www.jdbc3.8. commonscollections-3.0.0.2 3.2.

jar concurrent-1. AdminPE.3 dbunit-2.1.jar httpunit-1.jar cactus-1.9.9. RBAC jsr173_1.1 0.5.2 Preparing for Avaya IQ Implementation November 2011 85 .2 1.jar jsp-api.so.so.jar xdoclet-1.7.3.jar 1.7 Tomcat jdom. xbean_xpath.9.so.7.0.jar xercesImpl.6 1.3.1.9.jar Logging liblog4cxx.jar LifeCycle.0 0.2-RC2 myfaces-api-1.5-snapshot050611. xbean.7 1.1.0 simplesocketserver WebLM mail.ne t apache Apache Software License apache source forge apache SNMP4j apache apache OAM struts-test-2.4a 1.liblog4cxx.jar.3 no version available 2.7 0.1 1.public draft version (part of tomcat 5.7 1.jar liblog4cxx.5 1.jar ajaxanywhere-1.9.9.2-RC2 1.2.2 2.a sitemesh-2.7 0.lai Tomcat Apache Apache Apache Apache Apache Apache Sun liblog4cxx.jar catalina-ant.liblog 0.1.2.3 2.jar tomahawk-1.jar.jar 1.jar snmp toolkit SNMP4j.1.jar OAM myfaces-impl-1.Third-party jars and libraries Module using jar or library Jar or library xjavadoc-1.9.1.jar 0.0api.0.1.5 1.4.3.1.2.5.5) 1 2.5 Version Original vendor 1.31_1.6.5.1.02 1.7 4cxx.1.4 1.jar jstl standard.5 apache SourceForce.1.jar SNMP4j.1.1.

2 Backup Restore DSS libnet msvcp71.0 (64–bit) 10.0.microsoft.0.dll 7.4.jar commons-daemon-1.jboss.Distributed third-party software Module using jar or library Jar or library commons-file-upload.0.4 1.c om Logging.0.log4j-1.c om http:// www.action redhat http:// www.833 3.3. Alarming snmp toolkit User Mgt commons-cli-1.2.8 1.15 (LJ) RBAC UI JBoss Ajax4jsf Open Symphony OSCache 2.2.0.com November 2011 .2.3052.microsoft.1 8.jar 1 1 Version Original vendor Sun Apache Apache Maxware Redhat apache http:// labs.2.10.10 7.2.com/ oscache/ download.jar MaxWare JbossRule 1.2 (64–bit) Original vendor Oracle Oracle Red Hat 86 Preparing for Avaya IQ Implementation Comments? infodev@avaya.1.0.10. WebLM log4j .com/ jbossajax4jsf/ downloads/ http:// www.0 msvcr71.dll 0.3077.10.0.opensymp hony.0 (64–bit) Release 5.2 Logging.4 Additional third-party software distributed for turnkey systems Package name Oracle Server Oracle Client Red Hat Linux Version 10.4.

Database host worksheets Use the worksheets in this section to collect data about the database host. Note: • If you are using a single host for both the application and database. If more convenient. tablespaces. Some of this data must be obtained from the customer and some of this data are provided as an output of the Implementation Planning Tool. using the recommended names will assist Avaya services when troubleshooting the system. Basic database host information Required information Host name IP address Fully qualified service name Net Service Name (also known as service name or global service name) System user password Additional information Setting Preparing for Avaya IQ Implementation November 2011 87 . users. The completed worksheets should be given to your Avaya or Business Partner provisioning team during implementation. • Some of the options are populated with names recommended by Avaya. some of the basic information will be repeated in the application host worksheets.Appendix B: Customer information worksheets This section contains the worksheets that help you collect data about the components used in your deployment. you can collect the information in a word processing file and give it to your provisioning team. Although these names can always be changed as per customer requirements. and data stores.

Required to run the Configuration Audit Tool installation audit. The file that contains the strings is located at /opt/ Required to run the Configuration Audit Tool installation audit. Data store information Required information Content Data Store Database host (IP or FQDN) Database user name Database password Database TCP por (default=1521) Oracle service name Connection string Provided by the Configuration Audit Tool after successfully running the installation audit. RPT_CONTENT_ USR Additional information Setting Avaya/CCR/util/CAT/ connection.Customer information worksheets Required information JDBC driver location Additional information The JDBC driver must have read permissions to at least the owner and the group. Required to run the Configuration Audit Tool installation audit.com November 2011 . Required to run the Configuration Audit Tool installation audit. From Implementation Planning Tool outputs.out. From Implementation Planning Tool outputs. Historical Data Store Database host (IP or FQDN) Database name Database TCP port (default=1521) Required to run the Configuration Audit Tool installation audit. Required to run the Configuration Audit Tool installation audit. 88 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Setting Oracle home location Hardware specs OS version Database version From Implementation Planning Tool outputs.

Required to run the Configuration Audit Tool installation audit. RPT_HIST_RW_U SR Read-write user password Connection string Provided by the Configuration Audit Tool after successfully running the installation audit. Required to run the Configuration Audit Tool installation audit.Database host worksheets Required information Database user Database user password Read-only user Additional information Setting RPT_HIST_OWNE R_USR These users are optional depending on your security needs. RPT_RT_USR Read-only user password Preparing for Avaya IQ Implementation November 2011 89 . RPT_RT_RO_US R Required to run the Configuration Audit Tool installation audit.out. Real-time Data Store Database host (IP or FQDN) Database name Database TCP port (default=1521) Database user Database user password Read-only user These users are optional depending on your security needs. The file that contains the strings is located at /opt/ Avaya/CCR/util/CAT/ connection. You may use the Real-time Data Store user (RPT_RT_USR) for this function or you may create the individual readwrite or read-only users. You may use the Historical Data Store owner user (RPT_HIST_OWNER_USR) for this function or you may create the individual read-write or read-only users. You may use the Historical Data Store owner user (RPT_HIST_OWNER_USR) for this function or you may create the individual read-write or read-only users. RPT_HIST_RO_U SR Read-only user password Read-write user These users are optional depending on your security needs.

The file that contains the strings is located at /opt/ Required to run the Configuration Audit Tool installation audit.out. RPT_SDS_USR 90 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Required to run the Configuration Audit Tool installation audit.Customer information worksheets Required information Read-write user Additional information These users are optional depending on your security needs.com November 2011 . Reporting UI Data Store Database host (IP or FQDN) Database name Database TCP port (default=1521) Database login ID Database password Connection string Provided by the Configuration Audit Tool after successfully running the installation audit. System Data Store Database host (IP or FQDN) Database user name Database password Database TCP port (default=1521) Oracle service name Schema name Schema owner Required to run the Configuration Audit Tool installation audit. The file that contains the strings is located at /opt/ Avaya/CCR/util/CAT/ connection. You may use the Real-time Data Store user (RPT_RT_USR) for this function or you may create the individual readwrite or read-only users. Required to run the Configuration Audit Tool installation audit. Setting RPT_RT_RW_US R Read-write user password Connection string Provided by the Configuration Audit Tool after successfully running the installation audit. Required to run the Configuration Audit Tool installation audit. RPT_UI_USR Avaya/CCR/util/CAT/ connection.out. Required to run the Configuration Audit Tool installation audit.

Database host worksheets Required information Connection string Additional information Provided by the Configuration Audit Tool after successfully running the installation audit. Tablespace information Tablespaces Name Size (From Implementation Planning Tool outputs) Dimension report data Historical fact report data 1 Historical fact report data 2 Historical fact report data 3 Historical fact report data 4 Historical fact report data 5 Historical fact report data 6 Historical fact report data 7 Historical fact report data 8 Historical fact report data 9 Historical fact report data 10 Historical index data 1 Historical index data 2 Historical index data 3 HDIM01 HFACT01 HFACT02 HFACT03 HFACT04 HFACT05 HFACT06 HFACT07 HFACT08 HFACT09 HFACT10 HINDEX01 HINDEX02 HINDEX03 Preparing for Avaya IQ Implementation November 2011 91 . The file that contains the strings is located at /opt/ Setting Avaya/CCR/util/CAT/ connection.out.

Application host worksheet Use a copy of this worksheet to collect data about each of your application hosts.com November 2011 . make as many copies as needed to collect data for each application host.com for more information.avaya. Refer to the Database Server Configuration Recommendations and Oracle Guidelines document on http://support. but Avaya recommends that it be a minimum of 5 GB. Required information Host name IP address Hardware specs From Implementation Planning Tool outputs OS version NTP server IP address Host function From Implementation Planning Tool outputs From Implementation Planning Tool outputs Additional information Setting 92 Preparing for Avaya IQ Implementation Comments? infodev@avaya.Customer information worksheets Tablespaces Name Size (From Implementation Planning Tool outputs) Historical index data 4 Historical index data 5 Historical application data Real-time data HINDEX04 HINDEX05 USERHIST USERRT System data store data USERSDS Content store data Reporting UI data USERRPT USERUI 5 GB minimum Temporary tablespace* TEMP Note: The asterisk indicates that the TEMP tablespace is a standard Oracle tablespace and is not directly associated with Avaya IQ. For a multiple host deployment.

Turnkey worksheets Required information Installation user name Root password Additional information Setting Needed during installation and configuration Needed during installation and configuration Start of week day Install ASG Needed during software (yes or installation and no) configuration Related topics: Start of week day on page 15 Turnkey worksheets Use the following worksheet to collect the networking information required to complete the Red Hat First Boot installation for turnkey.General tab Host IP address Subnet mask Default gateway address Networking .DNS tab Host name (fully qualified domain name) Primary DNS Secondary DNS Tertiary DNS Application host Database host Notes Preparing for Avaya IQ Implementation November 2011 93 . Obtain as much information as you are able and provide this information to the Avaya provisioning team or Business Partner personnel. The Red Hat First Boot installation configures the Linux operating system. Worksheet for Dual host deployment Option Networking .

it cannot be changed without reinstalling Avaya IQ.Hosts tab for application or database host Host IP address Host name (full name) Alias (short name) Networking .com November 2011 .1 localhost 127.0.0.Time Synchronization NTP Server IP address Optional for the database host.Customer information worksheets Option DNS search path (domain name) Application host Database host Notes Networking . Information Deployment type Default value Dual Your value Dual Database host IP address or N/A fully qualified domain name Start of week day Sunday Related topics: Start of week day on page 15 Firewall port conflicts worksheet Based on the firewall ports that Avaya IQ uses as described in Firewall port usage. The most important decision that you must make is the start of week day. Use the following worksheet to record the information used when the Avaya provisioning team or Business Partner personnel install the turnkey system. list any firewall ports that will need to be changed during Avaya IQ implementation. Once this is administered.0. Provide this information to the Avaya provisioning team or Business Partner personnel.0.1 localhost Must use these values Must use these values Networking . Give this information to the Avaya or Business Partner team before they begin your implementation. Firewall port Port: Port: Reason for conflict 94 Preparing for Avaya IQ Implementation Comments? infodev@avaya.Hosts tab for localhost Localhost IP address Localhost name 127.

TCP port: Use display comm proc to show the TCP port for the Avaya IQ link. if administered. See Administering a link between Communication Manager and Avaya IQ on page 103 for more information. Required information Name Description (including model number) IP address (C-LAN) TCP port Release Input ID Additional information Setting Some of this information can be acquired from the Communication Manager system administration interface: IP address: Use list ip-interface all to show the C-LAN IP addresses. All other options must be provided by the customer either before or during implementation. This information is used during initial administration to set up the link from Avaya IQ and the Communication Manager systems. Preparing for Avaya IQ Implementation November 2011 95 .Communication Manager worksheet Firewall port Port: Port: Port: Port: Port: Port: Port: Port: Reason for conflict Related topics: Firewall port usage on page 28 Communication Manager worksheet Use a copy of this worksheet to collect data about each of your Communication Manager sources in your deployment.

Voice Portal worksheet You must perform the following tasks: • Read and check the correct Product Version Interoperability document for required Voice Portal compatibility patches. as MPP is the source of data that is stored in VPMS. and Input ID options can be defined by the customer.com November 2011 . Required information Name Description Proactive Contact System name IP Address Host name Naming service host Naming service port Proactive Contact release Account login Account password Input ID statspmp (default. The customer must submit a trouble ticket to Avaya support and ask for these options in preparation for an Avaya IQ installation.Customer information worksheets Proactive Contact worksheet Use a copy of this worksheet to collect data about each of your Proactive Contact sources in your deployment. • Synchronize all the Voice Portal MPP clocks with the VPMS clock. The Name. • Administer UCID on the Communication Manager system. if never changed) Your setting There is no interface available to the customer to determine most of these options. Source ID. 96 Preparing for Avaya IQ Implementation Comments? infodev@avaya. All the three systems must use the same NTP timing source. This information is used during initial administration to set up the link from the Proactive Contact system and its associated Communication Manager system. Description. • Synchronize the Voice Portal system with the Avaya IQ and Communication Manager systems.

Have your system administrator familiar with Active Directory services work with Avaya or Business Partner to define ADS server. . You must set the Operation Mode to Shared UUI. • Administer UCID on the Voice Portal system.Station button 10 on all the Communication Manager station ports.Active Directory worksheet for LDAP integration Voice Portal requires: .Communication Manager 5. search. Preparing for Avaya IQ Implementation November 2011 97 . Active Directory worksheet for LDAP integration Use the following worksheet to collect information about your Active Directory server so you can synchronize your enterprise directory with Avaya IQ. Transport UCID in shared mode as Yes. Station button 10 is used for non-SIP implementation. Required information Voice Portal database schema name Voice Portal database type Voice Portal version Number of days of Voice Portal data to extract for the initial import Voice Portal URL Voice Portal ETL source name Voice Portal database IP address Voice Portal database post Note: Your setting 5432 is the default port. and filters as needed. These options determine exactly which users will by synchronized from your Active Directory into the Avaya IQ directory. and Generate UCID field to Y.0 or later. Voice Portal database name Voice Portal adaptor name Voice Portal database user name Avaya IQ database user name ETL Crontab download frequency After you fill-in the required details. give this to form to the APS engineer.

Customer information worksheets Note: Not all options are shown in this worksheet. Option Active Directory IP address or DNS name Port number (default is 389.com November 2011 . SSL default is 636) Active Directory user name Active Directory user name password LDAP base node name Search filter Execution Frequency User DN suffix (optional) User DN prefix (optional) Your value 98 Preparing for Avaya IQ Implementation Comments? infodev@avaya.

CREATE BIGFILE TABLESPACE "HFACT01" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT01' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT02" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT02' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. Sample database scripts for creating tablespaces CREATE BIGFILE TABLESPACE "HDIM01" DATAFILE '/u01/app/oracle/oradata/reporting/ HDIM01' SIZE 1G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. You must create the tablespaces first and then the database users. CREATE BIGFILE TABLESPACE "HINDEX05" DATAFILE '/u01/app/oracle/oradata/reporting/ HINDEX05' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO.Appendix C: Sample database scripts This section provides sample database scripts that can be used to create tablespaces and users. CREATE BIGFILE TABLESPACE "HINDEX04" DATAFILE '/u01/app/oracle/oradata/reporting/ HINDEX04' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. and associate the users with the tablespaces. The sizes you will input for the tablespaces are provided in the Implementation Report for Customer from the Implementation Planning Tool outputs. CREATE BIGFILE TABLESPACE "HINDEX02" DATAFILE '/u01/app/oracle/oradata/reporting/ HINDEX02' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HINDEX01" DATAFILE '/u01/app/oracle/oradata/reporting/ HINDEX01' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT04" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT04' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT05" DATAFILE '/u01/app/oracle/oradata/reporting/ Preparing for Avaya IQ Implementation November 2011 99 . CREATE BIGFILE TABLESPACE "HFACT03" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT03' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HINDEX03" DATAFILE '/u01/app/oracle/oradata/reporting/ HINDEX03' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. It enables the application to communicate properly with the database host.

CREATE BIGFILE TABLESPACE "USERRPT" DATAFILE '/u01/app/oracle/oradata/reporting/ USERRPT' SIZE 1G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "USERRT" DATAFILE '/u01/app/oracle/oradata/reporting/ USERRT' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. Sample scripts for creating users and tablespace associations CREATE USER RPT_HIST_OWNER_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERHIST" ACCOUNT UNLOCK. GRANT CREATE SEQUENCE TO RPT_HIST_OWNER_USR.Sample database scripts HFACT05' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT09" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT09' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. 100 Preparing for Avaya IQ Implementation Comments? infodev@avaya. CREATE BIGFILE TABLESPACE "HFACT06" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT06' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. GRANT CREATE ROLE TO RPT_HIST_OWNER_USR. GRANT CREATE MATERIALIZED VIEW TO RPT_HIST_OWNER_USR. GRANT CREATE PROCEDURE TO RPT_HIST_OWNER_USR. CREATE BIGFILE TABLESPACE "USERSDS" DATAFILE '/u01/app/oracle/oradata/reporting/ USERSDS' SIZE 1G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "USERUI" DATAFILE '/u01/app/oracle/oradata/reporting/ USERUI' SIZE 1G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT07" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT07' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "USERHIST" DATAFILE '/u01/app/oracle/oradata/reporting/ USERHIST' SIZE 1G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. GRANT CREATE TABLE TO RPT_HIST_OWNER_USR. GRANT CREATE TRIGGER TO RPT_HIST_OWNER_USR. GRANT CREATE VIEW TO RPT_HIST_OWNER_USR. CREATE BIGFILE TABLESPACE "HFACT10" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT10' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. CREATE BIGFILE TABLESPACE "HFACT08" DATAFILE '/u01/app/oracle/oradata/reporting/ HFACT08' SIZE 2G REUSE AUTOEXTEND ON NEXT 256M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. ALTER USER RPT_HIST_OWNER_USR QUOTA UNLIMITED ON "USERHIST" QUOTA UNLIMITED ON "HFACT01".com November 2011 . GRANT CREATE SESSION TO RPT_HIST_OWNER_USR.

GRANT CREATE SESSION TO RPT_HIST_RO_USR. GRANT CREATE TRIGGER TO RPT_CONTENT_USR. GRANT CREATE PROCEDURE TO RPT_UI_USR. Preparing for Avaya IQ Implementation November 2011 101 . GRANT CREATE VIEW TO RPT_CONTENT_USR. GRANT CREATE SEQUENCE TO RPT_RT_USR. GRANT CREATE TABLE TO RPT_SDS_USR. GRANT CREATE PROCEDURE TO RPT_CONTENT_USR. ALTER USER RPT_CONTENT_USR QUOTA UNLIMITED ON "USERRPT". QUOTA UNLIMITED "HINDEX03". GRANT CREATE SESSION TO RPT_RT_RO_USR. CREATE USER RPT_RT_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERRT" ACCOUNT UNLOCK. GRANT CREATE VIEW TO RPT_SDS_USR. CREATE USER RPT_RT_RW_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERRT" ACCOUNT UNLOCK. GRANT CREATE TRIGGER TO RPT_RT_USR. CREATE USER RPT_CONTENT_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERRPT" ACCOUNT UNLOCK. QUOTA UNLIMITED "HFACT10". CREATE USER RPT_SDS_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERSDS" ACCOUNT UNLOCK. GRANT CREATE VIEW TO RPT_RT_USR. GRANT CREATE PROCEDURE TO RPT_RT_USR. GRANT CREATE TABLE TO RPT_RT_USR. GRANT CREATE VIEW TO RPT_UI_USR. GRANT CREATE TABLE TO RPT_UI_USR. GRANT CREATE TABLE TO RPT_CONTENT_USR. GRANT CREATE TRIGGER TO RPT_SDS_USR. GRANT CREATE MATERIALIZED VIEW TO RPT_RT_USR. QUOTA UNLIMITED "HDIM01". CREATE USER RPT_HIST_RO_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERHIST" ACCOUNT UNLOCK. ALTER USER RPT_RT_USR QUOTA UNLIMITED ON "USERRT". GRANT CREATE PROCEDURE TO RPT_SDS_USR. ON "HFACT02" QUOTA UNLIMITED ON "HFACT03" QUOTA UNLIMITED ON ON "HFACT05" QUOTA UNLIMITED ON "HFACT06" QUOTA UNLIMITED ON ON "HFACT08" QUOTA UNLIMITED ON "HFACT09" QUOTA UNLIMITED ON ON "HINDEX01" QUOTA UNLIMITED ON "HINDEX02" QUOTA UNLIMITED ON ON "HINDEX04" QUOTA UNLIMITED ON "HINDEX05" QUOTA UNLIMITED ON CREATE USER RPT_HIST_RW_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERHIST" ACCOUNT UNLOCK. GRANT CREATE SEQUENCE TO RPT_CONTENT_USR. GRANT CREATE ROLE TO RPT_RT_USR.Sample scripts for creating users and tablespace associations QUOTA UNLIMITED "HFACT04". CREATE USER RPT_RT_RO_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERRT" ACCOUNT UNLOCK. CREATE USER RPT_UI_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> DEFAULT TABLESPACE "USERUI" ACCOUNT UNLOCK. GRANT CREATE SESSION TO RPT_RT_USR. GRANT CREATE SESSION TO RPT_SDS_USR. GRANT CREATE SEQUENCE TO RPT_SDS_USR. GRANT CREATE SESSION TO RPT_HIST_RW_USR. GRANT CREATE SESSION TO RPT_CONTENT_USR. GRANT CREATE SESSION TO RPT_UI_USR. QUOTA UNLIMITED "HFACT07". GRANT CREATE SESSION TO RPT_RT_RW_USR. ALTER USER RPT_SDS_USR QUOTA UNLIMITED ON "USERSDS".

Sample database scripts GRANT CREATE TRIGGER TO RPT_UI_USR. 102 Preparing for Avaya IQ Implementation Comments? infodev@avaya. GRANT CREATE SESSION TO CAT_USR.com November 2011 . GRANT SELECT ANY DICTIONARY TO CAT_USR. GRANT CREATE SEQUENCE TO RPT_UI_USR. CREATE USER CAT_USR PROFILE "DEFAULT" IDENTIFIED BY <user_password> ACCOUNT UNLOCK. ALTER USER RPT_UI_USR QUOTA UNLIMITED ON "USERUI".

Appendix D: Administering a link between Communication Manager and Avaya IQ
In preparation to install Avaya IQ, you must coordinate link administration on your Communication Manager systems. Share this information with your Avaya or Business Partner service personnel. Before you associate the Communication Manager systems with your hosts (Creating and associating sources in Implementing Avaya IQ), you must administer the links from the Communication Manager systems to the hosts. You must do the procedures in this section for every Communication Manager system that is used as a data source for the Avaya IQ system. Important: Avaya IQ requires that additional switch features be enabled to ensure that contact center events are properly captured. Verify that administration has been completed as described in this section.

Administering data collection options
Procedure
1. You must administer the following data collection options on every Communication Manager system in the deployment: • Enable measurements for hunt groups (skills), trunk groups, and VDNs in the deployment. Measuring these resources means that reporting data will be sent to Avaya IQ. The measurement option can be set to either external or both. Do not allow any hunt groups (skills), trunk groups, or VDNs to go unmeasured. • Administer Universal Call ID (UCID) for all trunk groups that might possibly be used to transport calls in or out of the Communication Manager system. 2. You can optionally administer path replacement for trunk groups that are used to transport calls in or out of the Communication Manager system. The need for path replacement depends on your network switch configuration. For more details about these data collection options, see the following sections of Avaya Aura TM Call Center Automatic Call Distribution Reference: • Best Service Routing

Preparing for Avaya IQ Implementation

November 2011

103

Administering a link between Communication Manager and Avaya IQ

• Implementing the Time of Day Clock Synchronization feature • Information Forwarding • Look-Ahead Interflow • Reporting Adjuncts (this section is named Call Management System in the R3.1 version of this document) • Universal Call ID

Administering UCID options
UCID parameters must be administered for all trunk groups that might possibly be used to transport calls in or out of the Communication Manager system. For more details about these UCID options, see Avaya Aura TM Call Center Automatic Call Distribution Reference.

Administering UCID feature options
Procedure
Using the change system-parameters features command, administer the following options: • Create Universal Call ID (UCID): Set this option to y. • UCID Network Node ID: Enter a unique number that can be used to identify UCID messages from this Communication Manager system. Each Communication Manager system that connects to Avaya IQ must use a unique ID number. This number is used when troubleshooting error messages collected by the Avaya IQ system. The valid range is 1-32767. • Send UCID to ASAI: Set this option to y for Proactive Contact and Voice Portal applications and the call path replacement between Private Branch Exchanges (PBXs).

Administering UCID trunk options
About this task
UCID must be enabled for every ISDN trunk group that carries contact center calls.

104

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

Administering ANI trunk options

Procedure
Using the change trunk-group command, administer the following options: • UUI IE Treatment: Set this option to shared. • Maximum Size of UUI IE Contents: Set this option to a value between 32 and 128. The default is 128. • Send UUI IE: Set this option to y. • Send UCID: Set this option to y. • Universal Call ID (UCID): Set this option to a priority value of 1 to ensure that the UCID messages are transported properly.

Administering ANI trunk options
About this task
You must administer calling number information on all measured ISDN trunks so that Automatic Number Identification (ANI) information is displayed in Avaya IQ reports. This information is for the party’s extension on the trunk that originates the call and shows as Party in the Contact - trace report.

Procedure
1. Using the change trunk-group command, administer the following options on Page 3: • Send Calling Number: Set this option to y on the Communication Manager from which the call originates. • Format: Set the options as follows: - If the format is set to public, you must add the caller extensions using the NUMBERING - PUBLIC/UNKNOWN FORMAT form. - If the format is set to private, you must add the caller extensions using the NUMBERING - PRIVATE FORMAT form. 2. Using the change public-unknown-numbering command, add the caller extensions that you want to pass ANI digits. For example, if you want to pass ANI for all 5-digit extensions that start with the number 4 you would set the following options: • Ext Len: 5 • Ext Code: 4 • Trk Grp(s): The trunk groups for which you want to pass ANI

Preparing for Avaya IQ Implementation

November 2011

105

x R13. For example. For example.x or 15.1 Communication Manager 4. and Reporting Adjunct release based on the software release of the Communication Manager. or 4. Software release Licensed customer options* G3 Version Communication Manager 3.1 Communication Manager 5. add the caller extensions that you want to pass ANI digits. and still operate properly with 106 Preparing for Avaya IQ Implementation Comments? infodev@avaya.0 4.0 5.com November 2011 .0.1 R13.1 or R14. the Call Center Release may be up to two versions older if the customer decides not to purchase the latest call center features. 3. Administering Avaya IQ and Communication Manager release options The following table reflects the recommended settings for the G3 version.0 4.1 or R14. See Administrator Guide for Communication Manager for more information. if a system is being upgraded to a new G3 Version.0 System parameter feature options Reporting Adjunct Release IQ (CCR) N/A 4.x Communication Manager 5.0. You can set the administration options to an earlier version.0. if you want to pass ANI for all 5-digit extensions that start with the number 4 you would set the following options: • Ext Len: 5 • Ext Code: 4 • Trk Grp(s): The trunk groups for which you want to pass ANI • Total Len: 5 Other options can be set on these numbering forms.1 or R14.Administering a link between Communication Manager and Avaya IQ • Total CPN Len: 5 3. the Call Center Release can be set to 2.x R13. Call Center release.0 4.0 4. if a customer upgrades the system to G3 Version V14.x Note: The asterisk indicates that.0 CMS R13.2 V13 V14 V14 V15 Call Center Release 3.0 or 5. Using the change private-numbering command. but you cannot access all the features of the recommended release.

you must apply a new license file that has the correct version.For Communication Manager 3.01.4.737.1. this option must be set to V14. .00. this option must be set to 3.0 for new installs or 11.1.01.0.For Communication Manager 5.3.4 means Release 4. . confirm that the following options have been enabled: • G3 Version: If the software version is not correct. . you must apply a new license file that has a valid release. this option must be set to V13. This procedure is documented in Creating Communication Manager sources in Implementing Avaya IQ. load 415.0 for an upgraded system.x.Administering Avaya IQ and Communication Manager release options Avaya IQ.For Communication Manager 5.4. this option must be set to V14.1. • Call Center Release: If the release number is not valid.02.2.0. For a new installation. Procedure To accurately administer the Communication Manager release.1. load 642.415.1.1 means Release 5. Preparing for Avaya IQ Implementation November 2011 107 .1.642. the Call Center Release must match the G3 Version as shown in this table. load 737. Verifying the Communication Manager release About this task The Communication Manager release number must be administered when you create the Communication Manager data sources on Avaya IQ.For Communication Manager 4.0 means Release 5. use the list configuration software-versions command to display the software installed on the Communication Manager system. The software release numbers are interpreted as shown in the following examples: • R013x.2 Verifying the customer options Procedure Using the display system-parameters customer-options command.1. .3.1 • R014x.1 means Release 3.1 • R015x.For Communication Manager 3. .1.4 • R015x. or 3. this option must be set to V15. 12.

0 for new installs or 3.For Communication Manager 4. Software release Communication Manager 3.0. .0 for new installs or 12.0.1.1.0 4.0 for an upgraded system. .1.0 CMS (appl CMS) R13.0 for an upgraded system.com November 2011 .0 4.0. 108 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Setting the reporting adjunct release Procedure Using the change system-parameters features command.x 5.1 R13. or 5. or 5.2 Avaya IQ 4.x R13. set the Reporting Adjunct Release option. you must apply a new license file that has this option enabled. or 4.1. • Business Advocate and Dynamic Advocate: These options must be set to y if the customer is using the percent allocation call handling preference or the reserve critical and reserve behind target skill levels.For Communication Manager 5.0 for an upgraded system. • EAS-PHD: This option must be set to y. If these options are not enabled. this option must be set to 5. If this option is not enabled. If this option is not enabled.x. you must apply a new license file that has this option enabled.0 Reporting Adjunct Release IQ (appl CCR) N/A 4. you must apply a new license file that has these options enabled.0 .1 or R14.0 5. 3. 4. or 5.1.Administering a link between Communication Manager and Avaya IQ . 4.x Note: A companion CMS is not required in all configurations. 4.x R15. this option must be set to 4. or 5.0 4. See the Release option in Creating Communication Manager sources for the interactions of these options. 4.2. 4.1 5.0 or 5. or 5.0. • Expert Agent Selection (EAS): This option must be set to y.2.0 or 5.0 5.0.2.0 for new installs or 3. or R14. The option names and settings are different based on the Communication Manager software installed on the system.For Communication Manager 5.1 4.2. this option must be set to 4.

it is automatically updated on the other forms. data module. The names are displayed in alphabetical order the next time the form is displayed. The node names can be entered in any order. Administer the following options: • Name: Enter the host name of the Avaya IQ All Functions host (for All Functions with Remote Data Collection deployments). Adding IP routing on page 113 6. Saving translations on page 114 Important: The C-LAN circuit pack must be TN799D. These names are also used in the IP interfaces. Enabling the processor interface channel on page 114 7. If you change the node name in this form. The default node name entry is display-only and is not used for this application. and any gateway hosts used in the network. See About sites. Version 1. IP routing. hosts. Firmware 26. and other forms. use the Avaya IQ host name as defined when you set the host function. Complete the procedures in the following order: Procedure 1.Administering a C-LAN connection Administering a C-LAN connection About this task Use the procedures in this section to administer a TCP/IP connection to a C-LAN circuit pack. For consistency. and sources for more information. Adding a C-LAN IP interface on page 110 3. Adding an ethernet data module on page 112 4. Data Collection and Data Processing hosts (for Multiple Host deployments). Preparing for Avaya IQ Implementation November 2011 109 . or later. Adding the processor interface channels on page 112 5. Adding node names and IP addresses on page 109 2. Adding node names and IP addresses (C-LAN) Procedure Use the change node-names ip command to assign the name and IP address of the Avaya IQ host.

110 Preparing for Avaya IQ Implementation Comments? infodev@avaya. All Functions host (for All Functions with Remote Data Collection deployments). In this example. do not change the administration. • Type: Enter C-LAN. • Node Name: Enter the Communication Manager node name assigned on the Node Names form. you must add a new C-LAN board. Caution: If the IP interface is already administered. You can use an existing C-LAN interface if available. taken from the IP Node Names screen.Administering a link between Communication Manager and Avaya IQ Caution: Plan out the network before you assign any IP addresses. • IP Address: This field is display-only. based on the node name entered. and any required gateways. Listing IP interfaces (C-LAN) Procedure Use the list ip-interface all command to list all existing IP interfaces. Adding an IP interface (C-LAN) Procedure Use the add ip-interface <Board_Location> command to assign a C-LAN circuit pack as an IP interface. Data Collection and Data Processing hosts (for Multiple Host deployments). • IP Address: Enter the IP address of the Avaya IQ. enter voicehost.com November 2011 . • Slot: Enter the equipment location of the C-LAN circuit pack. Changing the administration could cause failure with IP telephones and other adjunct links. The same node name cannot be assigned to two different IP interfaces. • Code/Suffix: This is a display-only field that shows the designation number of the circuit pack installed in the specified slot. If no interfaces are available. Any future changes that require a change to IP addresses will cause a service disruption.

triggers a warning message to be sent to the error log. • Enable Ethernet Port: Enter y to indicate that the Ethernet port associated with the TN2602AP circuit pack is in service. a warning alarm is generated.Administering a C-LAN connection • Subnet Mask: Identifies which portion of an IP address is a network address and which is a host identifier.248 media gateways (G700. • Receive Buffer TCP Window Size: Enter the threshold for the number of sockets used by this C-LAN.323 Endpoints: This field controls whether or not IP endpoints can register on the interface. • Target socket load and Warning level: Enter the maximum number of sockets targeted for this interface. or check with the LAN administrator on site if connecting through the customer LAN. • Duplex: Enter full.323 Endpoints is y and the Communication Manager server is a main server or an LSP. or when the standby has been disabled. This field does not display on an ESS server. • Allow H. • Net work Region: For a C-LAN IP interface. This field allows a priority to be set on the interface. and a gateway address is administered. Enter n in this field before you make changes to the screen. • Speed: Enter 100Mbps. a gateway is not required. If the application goes to points off the subnet. • VLAN: Enter y if this is on a virtual LAN or n for a standard LAN. If using ethernet only. which when reached. If the Communication Manager and Avaya IQ host are on the same subnet. • Link: This display-only field shows the administered link number for an Ethernet link. This affects where the interface appears on the gatekeeper list.248 Gateways: This field controls whether or not H. G250) can register on the interface. • Gatekeeper Priority: Appears only if Allow H. If this is an active board. The default is 400. set to n only when there is no standby. • Gateway Address: Enter the address of a network node that will serve as the default gateway for the IP interface. If the number of sockets exceeds the targeted number. the gateway address of the router is required. Use the default entry. G350. • Auto: Specify y for auto-negotiation or n for manual speed and duplex settings based on your customer network and the network port settings. Preparing for Avaya IQ Implementation November 2011 111 . • Allow H. no IP routes are required. use 1.

Therefore. always use circuit 17 (for example. • Appl: Enter mis for Communication Manager 3. • Gtwy To: Leave blank. Use the default if the private network contains only Avaya systems and adjuncts. Important: Communication Manager 5. Administer the following options: • Proc Chan: Select a processor channel for this link. 112 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Enter n only if the network includes non-Avaya systems that use the 0s method of forming broadcast addresses. Enter ccr for Communication Manager 4. The default is yes (all 1s). For the ethernet link.0 and later. to set up an Avaya IQ link. • Enable: Enter n when adding the channel.1 and earlier. This name will display when you list the assigned data modules. the interface link setting must correspond to the C-LAN Ethernet link.com November 2011 . • Network uses 1’s for Broadcast Address: This sets the host portion of the IP address to 0s or 1s. • Type: Enter ethernet. Administer the following options: • Data Extension: Enter an unassigned extension number or next on the command line. • Port: Enter the equipment location of the C-LAN circuit pack (TN799). • Name: Enter a name for the data module. Adding the processor interface channels (C-LAN) Procedure Use the change communication-interface processor-channels command to assign the processor channel attributes.Administering a link between Communication Manager and Avaya IQ Adding an ethernet data module (C-LAN) Procedure Use the add data-module <extension> command to assign the Ethernet port of the C-LAN circuit pack. • Link: Enter a TCP/IP link number (1-33).2 does not support IP or an Ethernet Data Module. 01A0317). This entry corresponds to the Interface Link option on the Processor Channel form.

Administering a C-LAN connection • Mode: Enter s for server. This is either the local C-LAN port of the first intermediate node between the C-LAN port and the final destination. depending on your configuration. Procedure Administer the following options: • Route Number: If you are going through a router. • Gateway: Enter the node name of the gateway by which the destination node is reached for this route. • Subnet Mask: Enter a subnet mask. Preparing for Avaya IQ Implementation November 2011 113 . • Session Local/Session Remote: Use 1 for both the local and remote port assignments. For example. • Mach ID: Not used. Adding IP routing (C-LAN) About this task Use the add ip-route command to set up the IP routes from the Communication Manager to the Avaya IQ host. You would typically enter the node name for the Avaya IQ host or a router. • Destination Port: Use the default of 0. • Interface Link: Enter the TCP/IP link number used on the ethernet data module form. • When a Gateway Address is not administered for the C-LAN IP interface. This is required when: • The Communication Manager and the Avaya IQ host are on different subnets. if there were one or more routers between the C-LAN port and the final destination node (the Avaya IQ host). the gateway would be the node name of the first router. • Destination Node: Enter the node name of the Avaya IQ host as assigned on the Node Names form. • Interface Chan: Enter the TCP channel number (5000-64500). • Network Bits: Enter a value from 0-30. • Destination Node: This field represents the node name of the destination for this route. you must set up IP route 1 from the Communication Manager to the router and set up IP route 2 from the Communication Manager to the Avaya IQ host.

Complete the procedures in the following order: Procedure 1. Adding the processor interface channels on page 116 114 Preparing for Avaya IQ Implementation Comments? infodev@avaya. See Administration for Network Connectivity for more information about using this field.Administering a link between Communication Manager and Avaya IQ • C-LAN Board: Enter the equipment location of the C-LAN circuit pack that provides this route. Verifying the Processor Ethernet port on page 115 2. Displaying the processor ethernet port on page 115 3. Saving translations (C-LAN) About this task Use the save translation command to save these translations.com November 2011 . Adding node names and IP addresses on page 115 4. It is possible to have more than one C-LAN circuit pack. Enabling the processor interface channel (C-LAN) Procedure Enter change communication-interface processor-channels and set Enable to y to enable the channel. but most configurations will only have one C-LAN. A metric value of 1 is used only on a Communication Manager that has more than one C-LAN circuit pack installed. Enter 0 if there are no intermediate nodes between the C-LAN port and the ethernet port on the Avaya IQ host. • Metric: Specifies the complexity of this IP route. Administering a processor ethernet port connection About this task Use the procedures in this section to administer a network connection when connected to a processor ethernet port.

Administer the following options: • Name: Enter the host name of the Avaya IQ host and any gateway hosts used in the network. Caution: In most cases. Changing the administration could cause failure with IP telephones and other adjunct links. The Processor Ethernet option is listed in the Optional Features pages. The names are displayed in alphabetical order the next time the form is displayed. The default node name entry is display-only and is not used for this application. Displaying the processor ethernet port Procedure Use the display ip-interface procr command to display the IP address to the processor ethernet port. If the processor ethernet port is not enabled.Administering a processor ethernet port connection 5. the IP interface is already administered. Adding node names and IP addresses (processor ethernet port) Procedure Use the change node-names ip command to assign the name and IP address of the Avaya IQ host. Enabling the processor interface channel on page 117 6. The node names can be entered in any order. Do not change the administration. Preparing for Avaya IQ Implementation November 2011 115 . Saving translations on page 117 Verifying the Processor Ethernet port Procedure Use the display system-parameters customer-options command to verify that the processor ethernet port is enabled. you must apply a new license file to the Communication Manager that has this option enabled. Use this form to verify that the IP interface has been administered.

These names are also used in the IP interfaces.1 and earlier. • Interface Link: Enter the TCP/IP link number. • Gtwy To: Leave blank. Adding the processor interface channels (processor ethernet port) Procedure Use the change communication-interface processor-channels command to assign the processor channel attributes.Administering a link between Communication Manager and Avaya IQ For consistency. hosts.com November 2011 . • Session Local/Session Remote: Use 1 for both the local and remote port assignments. • IP Address: Enter the IP address of the Avaya IQ host and any required gateways. • Destination Node: Enter the node name of the Avaya IQ host as assigned on the Node Names form. and other forms. data module. 116 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Administer the following options: • Proc Chan: Select a processor channel for this link. it is automatically updated on the other forms. • Mode: Enter s for server. Any future changes that require a change to IP addresses will cause a service disruption. • Appl: Enter mis for Communication Manager 3. See About sites. • Destination Port: Use the default of 0.0 and later. Caution: Plan out the network before you assign any IP addresses. • Interface Chan: Enter the TCP channel number (5000-64500). and sources for more information. • Mach ID: Not used. use the Avaya IQ host name as defined when you set the host function. • Enable: Enter n when adding the channel. If you change the node name in this form. Enter ccr for Communication Manager 4. IP routing.

Preparing for Avaya IQ Implementation November 2011 117 . Saving translations (processor ethernet port) Procedure Use the save translation command to save these translations.Administering a processor ethernet port connection Enabling the processor interface channel (processor ethernet port) Procedure Enter change communication-interface processor-channels and set Enable to y to enable the processor channel.

com November 2011 .Administering a link between Communication Manager and Avaya IQ 118 Preparing for Avaya IQ Implementation Comments? infodev@avaya.

0 release. Procedure 1.0 with Proactive Contact 4. so that Avaya IQ reporting can determine that this is an acquire call.1 server as admin.Appendix E: Proactive Contact link administration For Avaya IQ to report on Proactive Contact (Hard Dialer) effectively.sroot Preparing for Avaya IQ Implementation November 2011 119 . The Proactive Contact acquired VDN and inbound VDN must be measured in both directions on the Communication Manager. Auto-in allows the Proactive Contact agent to hear a ring tone of the incoming call. Enter the following commands to stop the system: stop_pds stop_mts 3. instead of the call to acquire the agent remaining connected. This must be administered by Avaya services personnel in preparation for the installation of Avaya IQ 5. the link between the Proactive Contact and Avaya IQ systems must be administered in an encrypted mode. Avaya IQ has to be configured to interrupt the reason code. When the agent is released to inbound. However. Agent Blending: The only difference with agent blending is that after an agent is acquired for outbound calling. the work mode is changed to Auto-In for the agent is able to take inbound calls. Administering the Proactive Contact link for encrypted mode About this task When using Avaya IQ 5. Avaya IQ supports Proactive Contact Blended mode for both Predicitive and Managed Dialer jobs. you must have Multiple Call Handling (MCH) turned off on the Communication Manager and Proactive Contact agents require Agent Blending and Auto-In on the hard phone set. Enter the following command to log in as sroot: su . Log in to the Proactive Contact 4.1. A reason code can be sent with the change of the work mode. Note: Intelligent Call Blending is not supported. the agent work mode is changed to AUX and the call is disconnected. 2.

You must be able to convey the user name and password administered in this procedure to the person administering the Proactive Contact data source on Avaya IQ.support_ssl=on option to jacorb.Proactive Contact link administration 4. 6. Save and close the file. 7. Save and close the file. Enter: exit 10.security. Edit the file /opt/avaya/JacORB/etc/jacorb.support_ssl=on. Change the jacorb. Enter the following command to add the login used by Avaya IQ to the system: useradd -c "Avaya IQ Interface" -g pds_system statspmp 14.properties. Change the SSLIOP option to SSLIOP:YES. 13. Change the password to zbtq4tsn or the password to be used in administering the Proactive Contact data source on the Avaya IQ system. Enter the password for sroot. 5.com November 2011 . 8.sroot 12.security. Enter: exit 17. Enter the password for sroot. Enter the following commands to reconfigure and restart the system: start_mts start_pds 11. Edit the file /opt/avaya/pds/etc/master. Enter the following command to log in as sroot: su . 16. 9. 120 Preparing for Avaya IQ Implementation Comments? infodev@avaya. Note: Other scripts may be required to configure the Proactive Contact system to operate in non-secure mode. Log out of the Proactive Contact server.cfg. Enter: passwd statspmp 15. Contact Avaya support concerning this procedure and any other scripts that may need to be implemented.

Log in to the Proactive Contact 4. 5. 8. it should be done out of hours. 9.properties.security. Preparing for Avaya IQ Implementation November 2011 121 . To upgrade the link for non-encrypted mode: Procedure 1.support_ssl=on. Change the jacorb. 2. not just the ones used by Avaya IQ. 6. Log out of the Proactive Contact server. then check on the health of all components by running the following commands: check_dbcheck_mtscheck_pds 12.cfg. Enter the password for sroot. Edit the file /opt/avaya/pds/etc/master. Save and close the file. 7. Enter the following commands to reconfigure and restart the system: mtsconfigurestart_mtspdsconfigurestart_pds 11. Enter: exit 10.support_ssl=off option to jacorb.1 server as admin. Change the SSLIOP option to SSLIOP:YES.Changing from non-encrypted to encrypted mode Changing from non-encrypted to encrypted mode About this task This procedure shows how to change a Proactive Contact 4. Edit the file /opt/avaya/JacORB/etc/jacorb. Because this procedure stops the Proactive Contact system.1 system from non-encrypted to encrypted mode.security. Enter the following command to log in as sroot: su .sroot 4. Enter the following commands to stop the system: stop_pdsstop_mts 3. Wait a few moments. Caution: This change effects all connections with the Proactive Contact system. Save and close the file.

122 Preparing for Avaya IQ Implementation Comments? infodev@avaya.1 system is in encrypted mode.cfg and jacorb.properties files to check if the Proactive Contact 4.com November 2011 .Proactive Contact link administration Tip: You can check the value assigned to the SSLIP variable in the master.

process the information. • All Voice Portal MPPs must have their clocks synchronized with VPMS clock. Clock synchronization • The voice portal clocks must be synchronized with Avaya IQ and Communication Manager. The information is eventually displayed as Voice Portal data on Avaya IQ reports. the time data displayed in your reports will not line up between the sources. It displays the following two lines: server ntp. Log on to /etc directory and open /etc/ntp. you must install and configure the ETL application on a system where Avaya IQ is running. An ETL application connects to the Voice Portal database and establishes a link that retrieves information from the Voice Portal database and stores it in ETL tables. The processes running in Avaya IQ retrieve information from the ETL tables. It will also be difficult to make sense out of the reports that combine data and understand how Communication Manager is working in conjunction with Voice Portal.avaya. UCID administration The UCID must be turned on and working between Voice Portal and Communication Manager.com Preparing for Avaya IQ Implementation November 2011 123 . To establish the Voice Portal link. and display it in Avaya IQ reports. One source will show the call ending and the other will show it continuing. Synchronizing clock for VPMS Procedure 1. This section describes the prerequisites for installing the ETL and the procedure for installing and configuring the ETL application.dr. because MPP is the source of the data that is stored in VPMS.conf file. If the clocks are not synchronized. You need to administer UCID both on Voice Portal and Communication Manager.Appendix F: Voice Portal Link Administration Voice Portal link administration Voice Portal database stores all the Voice Portal information.

Voice Portal Link Administration

restrict ntp.dr.avaya.com mask 255.255.255.255 nomodify notrap noquery 2. Specify the same NTP server that you have your time on as your IQ and CM synchronized with in two places on the bottom two lines of the ntp.conf file. 3. Save the configuration. 4. Restart the service.

Synchronizing clock for all MPPs with VPMS
Procedure
1. Log on to /etc directory and open /etc/ntp.conf file on MPP. 2. Replace the IP address with IP address of the VPMS. 3. Save the update. 4. Restart the service.

Administering UCID for H.323
About this task
For Avaya IQ 5.0 to be able to track a call that transfers from Communication Manager to Voice Portal as the same call, the same UCID must pass from Communication Manager and used in Voice Portal. Use the following procedure to set up UCIDs for calls first handled by Communication Manager followed by Voice Portal through an H.323 IP station port (virtual 7434ND). Calls can be transferred from the Communication Manager to Voice Portal using a converseon vector step or a route to hunt group/skill destination. An agent or a station user on Communication Manager can also directly dial the hunt group/skill.

Procedure
1. On the CM Station form, administer button 10 on every virtual 7434ND (VP port) with a new button type: ucid-info.

124

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

Adding UCID For CM SIP trunks

This new button type is visible to administration but not expected to be assigned to stations with human users. The following points need to be noted: • The ucid-info can be assigned to virtual 7434ND stations, other H.323 stations including IP Agent, and to DCP stations that support CM defined feature buttons. • The ucid-info can be assigned to virtual 7434ND stations, other H.323 stations including IP Agent, and to DCP stations that support CM defined feature buttons. • The ucid-info is not supported on BRI or SIP endpoints or analog station interfaces, including Lineside T1. • Always assign this to the same virtual 7434ND button number 10 so that Voice Portal need not download button assignments. 2. On Voice Portal, set the Operation Mode to Shared UUI. 3. Set ‘Transport UCID in shared Mode’ to ‘y’ for each VP application. With these settings, Voice Portal automatically does a push of button 10 on each new call via H.323 signaling to obtain the UCID in the display returned to Voice Portal.

Adding UCID For CM SIP trunks
About this task Procedure
1. Log on to switch using SAT or ASA 2. Run the command:
Change Trunk-Group <sip trunk number>

3. Open Page 3 and enter the following values: a. In ACA Assignment enter N. b. In Maintenance Tests enter Y. c. In Measured enter both. d. In Numbering Format enter public. e. In UUI Treatment enter shared. f. In Maximum size of UUI Contents enter 128. g. In Replace Restricted Numbers? enter N. h. In Replace Unavailable Numbers? enter N.

Preparing for Avaya IQ Implementation

November 2011

125

Voice Portal Link Administration

i. In Send UCID enter Y. j. In Show ANSWERED BY on Display enter Y.

Administering ETL application source in Avaya IQ OAM
Procedure
1. Log on to OAM. 2. Under Tasks tab, select Connection Management > Administer Connections . The system displays All Connection Types window. 3. Click ETL Source link listed in All Connection Types window. The system displays the Connection Resources window. 4. Click Add to add a new ETL source. The system displays the Add Resource window. 5. Enter the voice portal resource name in Name field. This name must be same as the name used in Adapter Name on IQ field of ETL application configuration. 6. Enter a description for your voice portal source in Description. 7. Select Source Type as Voice Portal. 8. Click Next. 9. Click Finish on the confirmation message. The ETL source connection is now established and appears on the Connection Resources window.

Configuring new ETL application
Use this procedure to administer ETL application for Voice Portal data. It is important to understand how to determine the value for the Initial Import Days before proceeding with the administration. This represents how much historical data to capture when run for the first time.

126

Preparing for Avaya IQ Implementation
Comments? infodev@avaya.com

November 2011

Run the following command to retrieve Voice Portal configuration: . 3./vpconfig. The source name used when you add the ETL application in Avaya IQ Administration. Avaya IQ properties Field name VP ETL Source Name (As configured in IQ OAM) IQ Database Connection String (In the form of <DBHost>:<DBPort >:<DBName>) IQ database User Name IQ database user password Voice Portal properties Field name VP Adapter name VP database Connection String (In the form of <DBHost>:<DBPort >:<DBName>) Description Hard coded Voice Portal name. DB Port: Port number of the Avaya IQ database host. DBPort: Port number of the Postgress Voice Portal database DBName: Voice Portal database name to connect to Description Name given to the Voice Portal system in OAM. 4. Enter the appropriate Avaya IQ user ID and password. DBName: Avaya IQ database schema name to connect to. DBHost: IP address of fully qualified name of the Avaya IQ database host.sh <configuration name> The system prompts for a valid Avaya IQ administrator user ID and password for creating or updating Voice Portal ETL configuration. Connection string used to connect to the Voice Portal database.sh 2. Enter appropriate values based on the description provided in the configuration document. Log on to the Linux console of Avaya IQ administration host and run the following command: . Avaya IQ database password./opt/Avaya/CCR/etl/Avaya/ETLApps/VoicePortal/Configuration/vpconfig. Avaya IQ historical database user name. Connection string used to connect to the IQ database. String used to connect to the Voice Portal application and database. Preparing for Avaya IQ Implementation November 2011 127 . This name must match the name given to the ETL application added in Avaya IQ Administration. The system authenticates the user credentials and asks for configuration values. DBHost: IP address of the Voice Portal database host.Configuring new ETL application Procedure 1.

Voice Portal Link Administration VP database User Name Voice Portal database user name created when Voice Portal is installed. After all values are entered. Voice Portal database password when Voice Portal is installed. crontab is a standard Unix and Linux 128 Preparing for Avaya IQ Implementation Comments? infodev@avaya. This value will apply to all the ETL configurations. make sure that the user exists in the Voice Portal database. Example ETL configuration example: Enter VP ETL Source Name (As configured in IQ OAM): Enter IQ Database Connection String (In the form of <DBHost>:<DBPort>:<DBName>): Enter IQ Database User Name: Enter IQ Database User Password: Re-enter IQ Database User Password: Enter VP Adapter name: Enter VP Database Connection String (In the form of <DBHost>:<DBPort>:<DBName>): Enter VP Database User Name: Enter VP Database User Password: Re-enter VP Database User Password: Enter Number of Minutes to Capture: Configuring automatic ETL execution Before you begin The customer must create a crontab entry in the Avaya IQ Administration server to run the ETL application on a regular and scheduled manner. however. The default VP Database Name is VoicePortal.com November 2011 . the command prompt is displayed and the ETL configuration is complete. You can put whatever user name you want. User name used by ETL application to connect to the Voice Portal database. The maximum value is 62. VP Database User Password Other parameters Number of days of data to capture for the initial import The number of days of historical Voice Portal data to capture for the initial ETL import.

Minimal.20 * * * /opt/Avaya/CCR/etl/Avaya/ETLApps/VoicePortal/<ETL application name>/Scripts/VoicePortal. ETL application logs are written to: $CCR_HOME/etl/Avaya/ETLApps/VoicePortal/Logs You can use logs to diagnose whether ETL was able to connect to your VP database and IQ database. In this example. it enables the system to catch up with the current activity. and Rowlevel. If you want to learn more about the crontab command and operation.4.12. Enter the following command to create a crontab entry and to run the ETL application periodically: crontab –e 0 0.sh Where. Detailed. you must enter the following command to create a crontab entry and to run the ETL application every 4 hours: crontab –e 0 0. Logs also display the row level imports. equivalent to the interval set in Number of Minutes to Capture.Troubleshooting ETL application command. the logs are appended. ETL application log level can be changed by editing VoicePortal. 2. The other levels are Error. About this task When you set up the Voice Portal ETL application for the first time and if you have a large amount of data.16. Preparing for Avaya IQ Implementation November 2011 129 . Enter the following command to verify the crontab entry: crontab –l Example If the Number of Minutes to Capture value is 240 (equivalent to 4 hours). When the data in Avaya IQ reports appear to be current. Procedure 1. This section provides limited explanation about the crontab command.20 * * * /opt/Avaya/CCR/etl/Avaya/ETLApps/VoicePortal/<ETL application name>/Scripts/VoicePortal. you must run the ETL application at least every 4 hours.sh Troubleshooting ETL application Every time the ETL application is run. The default level is Basic.bat.4. you can search on the Internet. <ETL application name> is the name administered for the ETL source. If you run the ETL application earlier than 4 hours.8.12. This accelerates the process of retrieving all the current data from Voice Portal. Debug.8.16. you must first set the crontab entry to a time interval lesser than Number of Minutes to Capture. you can set the crontab entry to a longer time interval. Nothing.

Voice Portal Link Administration For information on logging levels refer to http://wiki. where x is the unique ID or the Tomcat container. you can use the Tomcat logs located at: /var/log/Avaya/CCR/TOMCAT_x. Tomcat log level can be changed by modifying /opt/Avaya/CCR/data/TOMCAT_x/ log4j. 1. This table also shows the last date and time when the report was run. Verifying records are in Avaya IQ tables You can use these steps if the Avaya IQ tables are not getting populated with the correct data as expected from the Voice Portal tables. You must view these tables before they are purged.pentaho. 130 Preparing for Avaya IQ Implementation Comments? infodev@avaya.properties. 4.com November 2011 . some transformation may not appear as expected. This table shows the last date and time when the report was run. Connect to the Avaya IQ database and schema used to import data . You can view the Avaya IQ tables before going to the logs to resolve the error and also verify whether the import was really successful. 3. 2. To diagnose this problem. Open the BATCHIMPORTREQUEST table to see when the last successful import occurred. These tables provide a view of what data came from the ETL application.com/display/EAI/Kitchen+User +Documentation For information on the transformation when VP data is transferred to the ETL tables. Open ETLVPIMPORTTRACKING table to see when the last import occurred. and eventually into reporting tables. For more detailed report. open the ETLPROCESSFLOWFACT table that has row for each transformation that is processed by the transformer.

................................................................................................................................. 103.11 software-only customer responsiblity ............11 customer responsibility .....................109. 112........................... setting up ...........53 creating tablespaces ..........................................125 auto ETL execution .....................................................................................................................61 running ............109 adding the processor interface channels .............................20 adding ..................................................................................................................................................................................112 IP routing (C-LAN) .......................46 checking ..........................................................................................................106 saving translations ...................107 customer responsibility checklists .........................................103 Administering release options .........................................................................................................41 creating ..... 62 installing ....103 verifying the release ...........104.114 UCID feature options ......................................................................................................... checking ............. 110. 115.......107 worksheet ...........................105 data collection options ..............104 ANI trunk options............115 processor interface channels (C-LAN) .61 running ...........................................................11 checklists .......................................................... administering ...............................31 Proactive Contact ports ................................................27 CAT ...............59–63 copying the package from the installation disc ...........61...103–105.....................................................................................................................................................................100 sample scripts ..............127 configuring Oracle parameters .................................................................................................. 119 ANI trunk options ........... 61 downloading ...62 CAT version ........... 116 C-LAN IP interface ..................57 Configuration Audit Tool ................................................126 configuring new ETL application .......................45 confirming ................................................................109 node names and IP addresses (processor ethernet port) ......................................................... 113..........................................................................................................................................110 adding an ethernet data module ...............114 listing IP interfaces .........113 node names and IP addresses (C-LAN) .......62 uninstalling .......87 customer options ................................11 C C-LAN ...................................53 Net Service Name .......................... 114...............95.......................................62 checklist ...112 processor interface channels (processor ethernet port) .......................................................110 ethernet data module (C-LAN) ...........62 character sets..............104 administering link between Communication Manager and Avaya IQ .........................................................106 adminstering ...........................62 CAT version.......... 107 administering link between Communication Manager and Avaya IQ ....................................112 adding IP routing ..................................................................................................104 UCID options ....................................................... 109 C-LAN connection ........................... 112–114 adding a C-LAN IP interface ......95 Communication Manager software ..............................................................112 enabling the processor interface channel ....99 creating users and tablespace associations ............................................................23 authenticating UCID ...........................................105 application host software ...116 additional third-party software distributed for turnkey systems ................................................................60 installing ...............................103 Proactive Contact link for encrypted mode ...............99 sample scripts ....................128 automatic ETL execution ...31 administering ................................................................................................................................113 adding node names and IP addresses .......................................109 UCID trunk options .............86 administer ................109...................110 Preparing for Avaya IQ Implementation November 2011 131 .............................Index A Active Directory .............119 processor ethernet port connection ............................................................................................................................. administering ...............................................................107 verifying ............. 110...26 Communication Manager software setup requirements .............63 using .............................................114 C-LAN connection......................14 Communication Manager .......100 customer information worksheets ........59 configuring ETL application .........................11 collecting setup data ..............................................................128 Avaya IQ and Communication Manager ....41 hostname setup ............................109 Call Management System software .................................

............................21 language variables ..........25 prerequisites ..... running tests using ..114 enterprise directory .................14 individual audit ............34 N Net Service Name ...........................76 information required to run database tests ..............................63 test descriptions.....36..14 G guidelines for partitioning the database OS ...................87 database scripts ...........................................................99 database users ......55 OS and database compatibility ...................................53 network management .........................................................................75 installing .................................................................... Data Collection host .....................................................................................................................................................................................................................................36............ Reporting host ..................................... 52 database connections ...........71 test descriptions.............................115 processor ethernet port .........................................56 Oracle Undo Tablespace ........ 70.........................41 licensing ..11 Implementation Planning Tool .................73 input file ................................................................................................................................11 Implementation planning ..................33 Oracle TEMP Tablespace ...........................................35 OS and database software installation ............9 turnkey ...................................48 digital certificates ............60 test descriptions.... Data Processing host ..........................................................123 I implementation planning prerequisites .........................117 processor interface channel (processor ethernet port) ................................................45 database host software ...............................................119 listing IP interfaces (C-LAN) ...............................................11 prerequisites for voice portal integration .......................61 Configuration Audit Tool .......................103 data sources ................................... 52 installing ................................................................20 enterprise directory software ............... 67..................................9 operating system requirements .......................................................................................................................................................................36 integrating Voice Portal with Avaya IQ ....78 input file................................................................................................16 link adminisration ............... 71 test descriptions..27 event logging ....117 enabling the processor interface channel (C-LAN) ..................94 O offers .....................34 disk partitioning .......................24 database host worksheet ...............78 sample ............... confirming .................................................................................................123 Prerequisites for VP integration ... Administration host .................33 setting ..............................................................................................................................71 test descriptions.....88 database client software .......................70 individual audit.......................... running ........................................................................61 CAT .................................123 L language support ........D data collection options ..................77 installation audit..110 E enabling ...60 Configuration Audit Tool .. running ...19 F firewall port setup ..........................................................................................................................................................................................................................................32 pop-up blocker settings .................28 firewall ports worksheet .......................................................................41 P permissive use policy ...........................................................................................................................36 displaying .........................................57 data store information ..................................................................................................................44 H hostname setup........................................................119 Proactive Contact ....61 installing Red Hat Linux ..............................9 software-only ....63...................34 firewall ports .............................67 132 Preparing for Avaya IQ Implementation November 2011 ................................................................. All Functions host ......81 downloading ................................................................20 network requirements .......................115 distributed third-party software ............................................................

..............99 for creating tablespaces ..........................................................................76 installation audit ....115–117 adding .................63........................................................74 third-party jars and libraries .........................................................27 security recommendations ...................................................................................................................................31.. 96.........................................................................................................35 user permissions .........................78 sample scripts ............ 56 software requirements ......107.........................57 running ..........124 for all MPPs with VPMS .............................................57 Communication Manager setup ............................................130 Voice Portal .....................................................107 Processor Ethernet port .......................23 software-only ........................................................................104 uninstalling .........11 U UCID feature options................. 103....................114 software-only offers ............117 saving translations .........................................................................67 All Functions host ............... administering ..........................................................................................86 additional distributedthird-party software .................................9 offers ...........................................................................................................................96 Proactive Contact software ........129 ETL application ..............................................71 Data Processing host ..................................115 adding the processor interface channels .....................................81..............................................................Proactive Contact .....................................................................15 requirements .............................................62 Configuration Audit Tool ........... 75............................................................................76 synchronizing clock ..... 76 CAT ..........................................86 time synchonization and time zone setup requirements ........................................57 Proactive Contact software setup ...............43 sizing ......117 processor ethernet port .............................103 administering ports ................................117 saving translations (C-LAN) .............................................................................................................63 user and group IDs created during installation ........................... administering ...........................77 S sample database scripts .........31 Administering the link for encrypted mode ........................................................71 Reporting host ..............34 troubleshooting ...................................................................................................46 setting up database software .........119 worksheet .......................................................................62 individual audit .........104 UCID trunk options.........100 for creating users and tablespace associations ...........62......43 setting up database software checklist ........................................................................................................................9 start of week day ..................................55.. 70............. running ........................................86 R remote access requirements ................................107 customer options ...... 119 administering link between Communication Manager and Avaya IQ .............................................................115 enabling the processor interface channel .................47 test descriptions ........................................................ 115 Communication Manager release ...........................124 synchronizing clock for VPMS ..........................................104 UCID options .............................................................................................70 test file results ..................................................... 57 processor ethernet port .....33 setting the reporting adjust release ..................114 security certificates ............................................76 running test using an input file ..................... 100 saving translations .....................115 Verifying records are in IQ tables ..9 turnkey systems ................................................................................................................ administering .......................119 link administration .48 V verifying ............................. 67.......................................... 71 Administration host ......116 displaying ....................................117 processor ethernet port connection.......................................63 Configuration Audit Tool .....................................................................................26 Proactive Contact software setup requirements ......................................123 T tables not getting populated ........................... 86 additional software distributed for third-party systems ....75 supporting application audit ..................108 setting up character sets ................................129 turnkey ....11 customer responsiblity checklist ..........................17 user ID requirements .........96 Preparing for Avaya IQ Implementation November 2011 133 ....................................130 tablespaces .......................................99 sample input file .............63 Data Collection host ...................................15 supporting application audit...83 third-party software ..................................................

......................94 Proactive Contact ...................................worksheet ..................92 Communication Manager .123 VP-IQ integration ....................................................................... 92..........87................................25 worksheet ...............................................................................................................95 customer information .........................................................................96 Voice Portal integration ............................................................................................96 134 Preparing for Avaya IQ Implementation November 2011 ....................................................................... 94–96 application host ...............................................96 worksheets .96 Voice Portal ..........87 firewall ports .........87 database host ..........................123 W web browser software ...............................................